https://bugzilla.novell.com/show_bug.cgi?id=848902 https://bugzilla.novell.com/show_bug.cgi?id=848902#c1 --- Comment #1 from ton rev 2013-11-04 22:25:44 UTC --- I forgot to say that the tested PC has a Windows 8 preinstalled OS. The same problem occurs in an older, 32 bit, MBR, BIOS, dual boot (W.Vista + OpenSUSE 12.2) PC using OpenSUSE 13.1 RC2 Live USB KDE 32 bits, so it seems it is not related with 32/64 bits, MBR/GTP or BIOS/UEFI. It must be something related with the option 'boot from Hard Disk' from the live USB. -- 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=848902 https://bugzilla.novell.com/show_bug.cgi?id=848902#c3 --- Comment #3 from ton rev 2013-11-05 15:07:02 UTC --- (In reply to comment #2)

Tested here and works well.

Can you exit the graphical interface when booting the live media and boot manually? Perhaps you can spot some error then...

Sorry, I am not a big expert. Can you say me how do I exit the graphical interface when booting the live media and then boot manually? Are there some log files in the USB live media to attach? -- 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=848902 https://bugzilla.novell.com/show_bug.cgi?id=848902#c5 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsrain@suse.com, | |snwint@suse.com AssignedTo|jsrain@suse.com |mchang@suse.com --- Comment #5 from Jiri Srain 2013-11-07 08:17:18 UTC --- OK, this finally says something. I'm not entirely sure whether it tries to boot directly from network instead of local disk, or after reading the disk fails. Michael, since it refers to uEFI, can you check? -- 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=848902 https://bugzilla.novell.com/show_bug.cgi?id=848902#c7 --- Comment #7 from ton rev 2013-11-13 22:13:16 UTC --- I have found the problem in the 64 bits Live USB GRUB. I hope it could be included in the final 13.1 version, I have had to investigate a lot. The definition of the "Boot from Hard Disk" option (in file /EFI/BOOT/grub.cfg) is: menuentry "Boot from Hard Disk" --class opensuse --class os { set root='hd0,1' chainloader /EFI/BOOT/bootx64.efi } where hd0,1 is the first partition (1) of the first hard disk (0), but as the system is booting from the live USB, it seems that the first hard disk is the USB itself and the PC's hard disk is the second, so 'hd0,1' is the USB itself. Changing this entry in /EFI/BOOT/grub.cfg to: menuentry "Boot from Hard Disk" --class opensuse --class os { set root='hd1,1' chainloader /EFI/BOOT/bootx64.efi } boots from the PC's hard disk. Another good idea would be to add to the GRUB menu another pair of options to reboot or power off the system, its only adding two more menuentries menuentry "System restart" { echo "System rebooting..." reboot } menuentry "System shutdown" { echo "System shutting down..." halt } I suppose that the problem with the 32 bit live USB will be similar but the 32 bit version uses syslinux instead of GRUB to boot and I have not had time to investigate yet. -- 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=848902 https://bugzilla.novell.com/show_bug.cgi?id=848902#c8 Michael Chang changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |jcheung@suse.com --- Comment #8 from Michael Chang 2013-11-14 04:14:04 UTC --- Hi ton, Thanks for your report and efforts to investigate this problem. By the way could you confirm you have the problem on legacy bios as well ? (from your report it did ..) I think we need to sort out the problem as how the grub device is mapped to UEFI device path and how they are ordered. If I remember correctly, it's by the order of device list returned by querying firmware about devices that supports blokio protocol, which could be rather dependent on firmware(bios) IMHO. That is to say I think it's possible on some other hardware your booted USE device is (hd1) and your hard disk device is (hd0), so the "Boot from Hard Disk" works on those hardware. I'm now away from my UEFI work environment and will do the work once I can (it would be next week ...). Jeffrey, please help me, to verify that "Boot from Hard Disk" function on live USB on the UEFI laptops we have ? Thanks. -- 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=848902 https://bugzilla.novell.com/show_bug.cgi?id=848902#c10 --- Comment #10 from ton rev 2013-11-14 18:41:30 UTC --- (In reply to comment #8)

Hi ton,

Thanks for your report and efforts to investigate this problem. By the way could you confirm you have the problem on legacy bios as well ? (from your report it did ..)

Yes, I have the same problem with the "Boot from Hard Disk" option on two different legacy bios 32 bit PC (a six years old notebook and a two years old netbook) in this case obviously using the 32 bits Live USB. In the 32 bits case I think the "Boot from Hard Disk" option launchs the command (taken from file syslinux.cfg) "localboot 0x80" but I still have not investigate syslinux options so I have no idea how to change it. If at least the options to reboot or halt the system where added to the final version Live USB, people with problems like me would be able to exit the Live USB menu without having to use the hardware power button that is never recommended. Cheers. -- 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=848902 https://bugzilla.novell.com/show_bug.cgi?id=848902#c15 Michael Chang changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |snwint@suse.com --- Comment #15 from Michael Chang 2013-11-22 10:07:23 UTC ---

I tried on both UEFI and non-UEFI machine, "Boot from Hard Disk" option fail and thus I think that the problem is not related to UEFI.

Checked with legacy bios with isolinux bootloader. In "Boot from Hard Disk" the 'Disk' is your primary hard drive define by bios with id 0x80. When booting off from USB, the primary hard drive is the USB disk itself as it's the booted device thus got assigned id 0x80. So if you "Boot from Hard Disk" it boots to itself again. I'm not sure, we'd better check with Steffen how to handle such case properly. Maybe we have to use 0x81 to boot secondary disk. About the efi, I'm looking for the hardware to test. -- 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=848902 https://bugzilla.novell.com/show_bug.cgi?id=848902#c17 --- Comment #17 from ton rev 2013-11-22 10:55:13 UTC --- (In reply to comment #15)

About the efi, I'm looking for the hardware to test.

From my tests (Comment 7) in UEFI the "Boot from Hard Disk" option (in file /EFI/BOOT/grub.cfg) boots: root='hd0,1' chainloader /EFI/BOOT/bootx64.efi where hd0,1 in GRUB2 is the first partition (1) of the first hard disk (0), but as the system is booting from the live USB, it seems that the first hard disk is the USB itself and the PC's hard disk is the second, so it boots to itself. It´s the same problem as in legacy bios but with GRUB2 commands involved.

Changing this entry to: set root='hd1,1' chainloader /EFI/BOOT/bootx64.efi booted from the PC's hard disk in my case but I don´t know if it´s the cleaner solution or there is a better way. -- 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=848902 https://bugzilla.novell.com/show_bug.cgi?id=848902#c19 --- Comment #19 from Michael Chang 2013-11-28 07:58:50 UTC --- (In reply to comment #16)

You can use '-2' instead of 0x80 to boot the 'next' disk. Seems I

Cool. Don't know that syslinux could specify 'next' disk. :) I think 0x81 is not reliable as it's not necessary be the 'next' disk . So using -2 is really the best idea. -- 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=848902 https://bugzilla.novell.com/show_bug.cgi?id=848902#c21 --- Comment #21 from ton rev 2013-12-15 21:14:59 UTC --- (In reply to comment #20)

I'm testing this config and it seems to work for me, although it looks quite scary.

But as far as I understand it this script only works with UEFI systems, not with 64 bits non UEFI systems. There is a script in /etc/grub.d/30_os-prober that is used to detect any OS (32 and 64 bits, UEFI and non UEFI) and add that OS entry to the GRUB configuration file grub.cfg. I suppose it will be launched during the installation process. I don't fully understand it, so I am not sure, but could be possible to use it or a modified version in our "Boot from Hard Disk" case to detect and launch the proper hard disk OS? It's just an idea. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=848902 --- Comment #24 from ton rev --- I have tested KDE Live 13.2 RC1 32 bits on a legacy BIOS 32 bits PC and last year bug in 13.1 is still present in 13.2. It's a pity because in comment 16 of this bug Steffen Winterfeldt proposed a workaround for this problem, changing in the syslinux.cfg file the entry "localboot 0x80" for "localboot -2" but unfortunately this has not been implemented in 13.2. I hope someone does it in time for the release. This time I can't test an EFI machine but as I read in John Hudson comment the solutions proposed for this case have neither been implemented. -- You are receiving this mail because: You are on the CC list for the bug.