Created attachment 368198 [details] patch for above After generating a USB live key using livecd-iso-to-disk, I had to edit /EFI/boot/bootx64.conf to change the LABEL of the device to use. By default the label used will be that of the ISO, instead of either LIVE (as used by the script), or the UUID from the script. Untested change attached.
I applied this patch and tried with F12 i686 RC.4. livecd-iso-to-disk --reset-mbr --format --efi foo.iso /dev/sdb1 The resulting disk neither Linux nor MacOS X can read. Booting the Mac holding down the Option button doesn't see the USB stick. Any suggestions?
(In reply to comment #1) > I applied this patch and tried with F12 i686 RC.4. > > livecd-iso-to-disk --reset-mbr --format --efi foo.iso /dev/sdb1 > > The resulting disk neither Linux Linux can read it, but it won't be mounted by default. Launch the "Disk Utility" and you'll be able to mount the partition. > nor MacOS X can read. MacOS X sucks. > Booting the Mac holding down the Option button doesn't see the USB stick. That's probably worse though. > Any suggestions? Did you boot this on a i686-only mac? If it has x86-64 (which most newer hardware does) then you'd need to use the x86-64 version of the ISO. Or maybe your USB stick is broken...
> Did you boot this on a i686-only mac? If it has x86-64 (which most newer > hardware does) then you'd need to use the x86-64 version of the ISO. Is there any reason the /EFI/boot/bootx64.conf can't be updated on both 32 and 64 live images? There shouldn't be any reason a 32 bit distro can't boot on 64 bit and Sugar on a Stick tends to push 32 bit so that the 'stick' will work with any machine.
(In reply to comment #3) > > Did you boot this on a i686-only mac? If it has x86-64 (which most newer > > hardware does) then you'd need to use the x86-64 version of the ISO. > > Is there any reason the /EFI/boot/bootx64.conf can't be updated on both 32 and > 64 live images? There shouldn't be any reason a 32 bit distro can't boot on 64 > bit and Sugar on a Stick tends to push 32 bit so that the 'stick' will work > with any machine. As it currently stands, you need to have a kernel+grub that matches the bitsize of your EFI implementation. It is certainly feasible to implement booting of 32bit EFI kernels from 32bit EFIgrub from 64bit EFI hardware, but no one has done the work
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Updating to rawhide as its still an issue
How will the 32-bit kernel react to seeing 64-bit SAL entry points? I suspect this won't trivially work, but I don't have a system handy to test on for a few weeks.
Adding linux-bugs, because I don't know that we've looked at booting a 32-bit kernel from 64-bit UEFI, but we'd like that to work if it doesn't. For RHEL6, we don't intend to offer 32-bit RHEL, just like for SLES 9 and 10 we never offered the 32-bit flavors. However, we know users who do run the 32-bit versions regardless, so it should work, albeit not a configuration for sale.
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This appears to be working: kernel /EFI/boot/vmlinuz0 root=live:UUID=E866-9B76 /dev/sdd1: LABEL="LIVE" UUID="E866-9B76" TYPE="vfat" As for booting 32bit on 64bit, I don't think that's really a livecd tool issue, and if it is it needs its own bug.