https://bugzilla.novell.com/show_bug.cgi?id=819631 https://bugzilla.novell.com/show_bug.cgi?id=819631#c Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|coolo@suse.com |snwint@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=819631 https://bugzilla.novell.com/show_bug.cgi?id=819631#c3 Tim Hardeck changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Component|Bootloader |Bootloader Version|Final |13.1 Milestone 2 InfoProvider|thardeck@suse.com | AssignedTo|snwint@suse.com |jsrain@suse.com Product|openSUSE 12.3 |openSUSE Factory --- Comment #3 from Tim Hardeck 2013-05-14 09:20:08 UTC --- The firmware provides the path (cd0)/EFI/Boot which doesn't match with the one on the DVD. To my knowledge the EFI specification requires upper case. Possible workarounds for future releases might be to use a static path in Grub2 EFI instead of the one provide by the firmware. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=819631 https://bugzilla.novell.com/show_bug.cgi?id=819631#c5 --- Comment #5 from Michael Chang 2013-05-16 11:04:50 UTC --- As you have pointed out the mess could come from we use $prefix which determined by firmware and it's value floating (as firmware don't think that matters) .. use that path together with grub2's iso9660 fs driver which could be case sensitive lead to the failure .. I'm afraid we have to provide an alternate grubcd.efi with hardcoded $prefix to fix the problem .. which is not possible now. :( Another possible solution is to patch grub2 to test the path ... like Tim's suggestion in comment#1 .. That's my two cents and could be wrong .. Steffen knows better and if we force to go the solution (patching grub2) I could do that .. just let me know what's best to us. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=819631 https://bugzilla.novell.com/show_bug.cgi?id=819631#c8 --- Comment #8 from Richard Hamilton 2013-05-16 15:18:00 UTC --- Workaround for HP below: Steps to Reproduce: 1. Go to F10 to System Configuration 2. Select Boot Options then Boot Mode 3. Change from Legacy to UEFI Native ( Without CMS) Save and reboot 4. Install SSUSE Sled11sp2Gm from DVD and go through the installation process 5. System completes install OS and reboot 6. Get stuck on the Post " No bootable image found, notebook will be shutdown." 7. Hit enter “OK” system just goes to black screen 8. To WORKAROUN 9. Power on the Unit and Hit F9 10. Select Boot From EFI File 11. Navigate to the EFI partitions and select efi> Select SUSE>Select elilo.efi 12. Then it boot to the OS Once in OS. open terminal and type `su` at the prompt and enter password. Enter efiboormgr at the prompt again and see boot entry was sucessfully added to BIOS as: BootCurrent: 0000 Timeout: 5 seconds BootOrder: 0000 Boot0000* SUSE Linux Enterprise Desktop 11 SP2 HD(1,800,xxxxx.......xxxxxxx)File(\efi\SuSE\elilo.efi) The BIOS will never boot or display this boot entry unless entry is set to next boot. For any Linux OS. UEFI boot loaders are at the following location: RHEL /efi/RedHat/grub.efi SUSE /efi/SuSE/elilo.efi Ubuntu /efi/Ubuntu/grubx64.efi BIOS needs to display these boot entries and boot to the default boot order set by efibootmgr. So as Tim suspected, it is a path issue. From what I've found out, in native mode there is no issue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.