http://bugzilla.opensuse.org/show_bug.cgi?id=902982 Neil Rickert changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nrickert@ameritech.net --- Comment #2 from Neil Rickert --- Since noticing this bug report, I have tried booting the live KDE (for RC1), with the live image written to USB. It booted without problem on a Lenovo TS 140 (secure-boot disabled), and on a Dell Inspiron 660 (secure-boot enabled). I don't have a USB-based CD/DVD reader, so I could not test that.

From your description, my best guess would be that your problem has to do with how you prepared the USB. For example, it is well known that using "UNetbootin" to prepare a boot USB does not work well with opensuse.

I prepared my USB with a raw copy of the image over the USB device: dd_rescue openSUSE-13.2-KDE-Live-Build0019-x86_64.iso /dev/sdd The tricky part of UEFI is getting the boot process started. If you got as far as the grub2 command prompt, then you already got past that stage. This suggests to me that grub2-efi is running, but is failing on its search for the install media, which it searches for using UUID. (Just my two cents). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=902982 Aidan Collier changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #4 from Aidan Collier --- Sure! I'll be be sure to attach the screenshot. But I just would like to let you know that the USB based DVD drive (the LG slim portable DVD writer) did interface as a USB device, but it seems to interface very well with the UEFI bootloader, and even printed out the DVD device name alongside its own device name in the boot options. Given that, wouldn't think any drivers would be the issue, because when I used the LG drive with both Fedora 20 and Ubuntu Live Media the drive worked as it should, properly booting up with the live distro and so on. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=902982 Andrei Borzenkov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arvidjaar@gmail.com --- Comment #8 from Andrei Borzenkov --- (In reply to Michael Chang from comment #7)

But for the installer which looks up most of it's files and contents in iso9660 fs that become a problem as it's case sensitive.

As far as I know ISO9660 is case insensitive? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=902982 Stefan Quandt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |squan@web.de --- Comment #12 from Stefan Quandt --- Created attachment 636944 --> http://bugzilla.opensuse.org/attachment.cgi?id=636944&action=edit Attempt to boot USB from tumbleweed-DVD-i586-Snapshot20150603 Just struggled with this problem (and other problems with regular 13.2 KDE Live image) the last days: Hardware: Asus UX501 with Win 8.1 on internal Micron SSD. BOOT settings: CSM disabled, secure boot enabled. Booting USB stick with current Tumbleweed DVD image (created with imagewriter) stops at the "grub>" command prompt. The "set" command reveals prefix=(hd0,msdos1)EFI/BOOT root=hd0,msdos1 (for details see screenshot attached). Issuing the commands prefix=(hd0,msdos1)EFI/Boot normal makes the system boot into linux. I.e. no problem with case sensitivity here. Please note just the slash i inserted in the prefix path before 'EFI'. Could you please tell the impact of this bug? I.e. in which situations booting SUSE live images is compromised (and since when)? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=902982 --- Comment #14 from Andrei Borzenkov --- (In reply to Stefan Quandt from comment #12)

Please note just the slash i inserted in the prefix path before 'EFI'.

Likely fixed by commit 7e7293d745ef7c0a13d8cbf12f474843edfdd0ab Author: Vladimir Serbinenko Date: Sat Jan 18 16:41:47 2014 +0100 * grub-core/kern/efi/efi.c: Ensure that the result starts with / and has no //. Still it would be helpful to verify that it does fix your problem. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=902982 --- Comment #16 from Stefan Quandt --- Created attachment 636946 --> http://bugzilla.opensuse.org/attachment.cgi?id=636946&action=edit Attempt to boot USB from tumbleweed-DVD-i586-Snapshot20150603 (In reply to Andrei Borzenkov from comment #13)

Are you sure you attached the right picture? Oops, attachment 636944 was a completely wrong file :)

Both strings you show are exactly the same. Pardon, just a typo. What I observe from the "set" command is prefix=(hd0,msdos1)EFI/BOOT It lacks the'/' before EFI as in original attachment 612574.

And of course for booting properly i use prefix=(hd0,msdos1)/EFI/Boot normal

Apparently information returned by firmware lacks leading slash. Ah, did not know that "EFI/BOOT" comes from the firmware.

I don't know if the Dell XPS 13 9333 has the same UEFI firmware as my Asus UX501, but its the same bug. The BIOS/UEFI utility of my UX501 is Aptio Setup Utility 2.15.1236 from American Megatrends. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=902982 --- Comment #18 from Andrei Borzenkov --- (In reply to Stefan Quandt from comment #16)

Created attachment 636946 [details] Attempt to boot USB from tumbleweed-DVD-i586-Snapshot20150603

OK so it confirms 64 bit EFI boot. Would you test grub version with proposed fix? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=902982 Andrei Borzenkov changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(squan@web.de) --- Comment #26 from Andrei Borzenkov --- (In reply to Stefan Quandt from comment #25)

1) the problem occurs using an image of the openSUSE-13.2 KDE live CD (current release) and

Could you please attach screenshot of failed boot?

2) the problem does not occur with a recent KDE live CD image from http://download.opensuse.org/tumbleweed/iso/

As far as I know Live images do not even support EFI boot and your original report was for full DVD, not for Live.

I.e. the latter boots fine into KDE, but in KDE i could not run the yast

How is it related to GRUB inability to find its configuration?

After modifying the USB stick as described it properly boots into KDE (problem resolved).

Sorry, I am not convinced these tests actually tested the problem. You should have used the same image as in comment 16 to be sure we test the same problem. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=902982 --- Comment #29 from Stefan Quandt --- (In reply to Andrei Borzenkov from comment #26)

(In reply to Stefan Quandt from comment #25)

...

1) the problem occurs using an image of the openSUSE-13.2 KDE live CD (current release) and

Could you please attach screenshot of failed boot? I did not state this clear enough in comment 19, but the screenshot attachment 636945 is in fact from booting the openSUSE KDE live CD (from USB).

...

2) the problem does not occur with a recent KDE live CD image from http://download.opensuse.org/tumbleweed/iso/

As far as I know Live images do not even support EFI boot and your original report was for full DVD, not for Live. The tumbleweed-DVD-i586-Snapshot20150603 was one of the images i downloaded, but of coure it is not for x86-64 and therefor did not boot at all.

...

After modifying the USB stick as described it properly boots into KDE (problem resolved).

Sorry, I am not convinced these tests actually tested the problem. You should have used the same image as in comment 16 to be sure we test the same problem. In fact i did use the same image. As said it fails to boot without adjusting the '/' in the prefix path. And after applying the patch attachment 637068 to /EFI/BOOT/grub.efi (see instructions in comment 20) it boots into KDE without intervention.

-- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=902982 Michael Chang changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #31 from Michael Chang --- Thanks Andrei, close as resolved fixed. -- You are receiving this mail because: You are on the CC list for the bug.