It's not that stupid a question.
The behaviour of UEFI shell is very counterintuitive here. The fact that it permits you to use forward-slashes for cp but not for executing an application is completely bonkers, and guaranteed to cause confusion.
On 23 April 2014 12:27, Fu Wei fu.wei@linaro.org wrote:
Hi Leif,
Thank you very much for correcting me. And sorry for that stupid question : For "(1)I can not execute the grub stored in /EFI/grub/grubaa64", that is the "/" and "" problem.
On 04/23/2014 06:27 PM, Fu Wei wrote:
Hi Leif, I have tested the linaro-edk2 and grub-install in latest leg image, report is below:
For linaro-edk2(http://snapshots.linaro.org/components/kernel/linaro-edk2/12)
Because this version of uefi need to work with Turstzone Firmware0.3, so we need to wrap it, can not test directly in LAVA. I wrap it locally, and upload to linaro for testing: http://people.linaro.org/~fu.wei/LAVA/test/UEFI/Bug-1281123/
Test: https://staging.validation.linaro.org/scheduler/job/46616
But in local test, I found some problems:
(1)I can not execute the grub stored in /EFI/grub/grubaa64, but once I copy it to / or /EFI/BOOT/, that can be executed either by FS1:/EFI/grub/grubaa64.efi and EFI\BOOT\grubaa64.efi , the log is below:
Shell> FS1:/EFI/grub/grubaa64.efi 'FS1:/EFI/grub/grubaa64.efi' is not recognized as an internal or external command, operable program, or script file. Shell> FS1: FS1:> ls EFI/grub/* 04/17/2014 14:43 <DIR> 2,048 . 04/17/2014 14:43 <DIR> 2,048 .. 04/17/2014 14:50 124,416 grubaa64.efi 1 File(s) 124,416 bytes grub 2 Dir(s)) 0 bytes
FS1:> EFI/grub/grubaa64.efi 'EFI/grub/grubaa64.efi' is not recognized as an internal or external command, operable program, or script file.
FS1:> cp EFI/grub/grubaa64.efi EFI/BOOT/ Copying FS1:\EFI\grub\grubaa64.efi -> FS1:\EFI\BOOT\grubaa64.efi
- [ok]
FS1:> EFI\BOOT\grubaa64.efi Welcome to GRUB!
GNU GRUB version 2.02~beta2Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions.
grub> exit FS1:> FS1:\EFI\grub\grubaa64.efi Welcome to GRUB!
GNU GRUB version 2.02~beta2Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions.
grub> exit FS1:> EFI/grub/grubaa64.efi 'EFI/grub/grubaa64.efi' is not recognized as an internal or external command, operable program, or script file.
FS1:> rm EFI/BOOT/grubaa64.efi Deleting 'FS1:\EFI\BOOT\grubaa64.efi' Delete successful
FS1:> FS1:\EFI\grub\grubaa64.efi Welcome to GRUB!
GNU GRUB version 2.02~beta2Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions.
grub> exit FS1:> grubaa64.efi 'grubaa64.efi' is not recognized as an internal or external command, operable program, or script file.
FS1:> grubaa64 'grubaa64' is not recognized as an internal or external command, operable program, or script file.
FS1:> FS1:\EFI\grub\grubaa64.efi Welcome to GRUB!
GNU GRUB version 2.02~beta2Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions.
grub> exit FS1:> cp EFI/grub/grubaa64.efi . Copying FS1:\EFI\grub\grubaa64.efi -> FS1:\grubaa64.efi
- [ok]
FS1:> grubaa64.efi Welcome to GRUB!
GNU GRUB version 2.02~beta2Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions.
grub>
*Is that the normal behavior???*
(2)Got "Synchronous Exception:", once I exit from uefi shell and reenter the shell, the log is below:
FS1:> exit [1] Linaro disk image on virtio - VenHw(C5B9C74A-6D72-4719-99AB-C59F199091EB)/Image - Arguments: console=ttyAMA0 earlyprintk=pl011,0x1c090000 debug user_debug=31 loglevel=9 root=/dev/vda2 - FDT: VenHw(C5B9C74A-6D72-4719-99AB-C59F199091EB)/fvp-base-gicv2-psci.dtb - LoaderType: Linux kernel with Local FDT [2] pxe - MAC(201201041000,0x1) - LoaderType: EFI Application
Global FDT Config - VenHw(C5B9C74A-6D72-4719-99AB-C59F199091EB)/fdt.dtb
[a] Boot Manager [b] Shell [c] Reboot [d] Shutdown Start: b
Synchronous Exception:
Synchronous Exception: ......
(3)grub did not get the config file in /grub/grub.cfg
Test log: https://staging.validation.linaro.org/scheduler/job/46613/log_file#L_131_0 https://staging.validation.linaro.org/scheduler/job/46613/log_file#L_155_2
Could you help me, Thanks!
-- Best regards,
Fu Wei Enterprise Server Engineer From Red Hat LEG Team Linaro.org | Open source software for ARM SoCs Ph: +86 186 2020 4684 (mobile) IRC: fuwei Skype: tekkamanninja Room 1512, Regus One Corporate Avenue,Level 15, One Corporate Avenue,222 Hubin Road,Huangpu District, Shanghai,China 200021