Description of problem: Live media for EFI systems could be created using the livecd-iso-to-disk tools, but now the EFI folder is missing on the livecd and livecd-iso-to-disk fails if run with the --efi option. Version-Release number of selected component (if applicable): alpha How reproducible: always Steps to Reproduce: 1. Download named image. 2. Run livecd-iso-to-disk --format --efi $ISO $DEV 3. Actual results: livecd-iso-to-disk fails with ERROR: This live image does not support EFI booting Expected results: efi bootable disk is created Additional info: As noted above the efi folder is missing on the live cd ..
The RC3 still can not be used with livecd-iso-to-disk and --efi - any progress on this?
The F15-live can be used with the livecd-iso-to-disk --efi commandline and can be booted on a efi system. Some versions: - Fedora 15 with all updates-testing. - Fedora-16-RC3 x86_64 image as of today. $ rpm -q livecd-tools livecd-tools-15.8-1.fc15.x86_64 $ sudo livecd-iso-to-disk --format --efi Fedora-16-Beta-x86_64-Live-Desktop.iso /dev/sdg Verifying image... /home/fabiand/Downloads/Fedora-16-Beta-x86_64-Live-Desktop.iso: 266d2136cde77ee390f5e4f1ba033d7c Fragment sums: 511daddc795156378fbaecd488c2d75b7b28c2a35c67eddc920f6aae9c16 Fragment count: 20 Press [Esc] to abort check. Checking: 100.0% The media check is complete, the result is: PASS. It is OK to use this media. WARNING: THIS WILL DESTROY ANY DATA ON /dev/sdg!!! Press Enter to continue or ctrl-c to abort wipefs: WARNING: /dev/sdg: appears to contain 'gpt' partition table Waiting for devices to settle... mkdosfs 3.0.11 (24 Dec 2010) ERROR: This live image does not support EFI booting Cleaning up to exit...
Fabian, can you confirm that you were using the Fedora 16 beta RC3 livecd from: http://dl.fedoraproject.org/pub/alt/stage/16-Beta.RC3/Live/x86_64/Fedora-16-Beta-x86_64-Live-Desktop.iso If so, the build logs for the livecd are in koji: http://koji.fedoraproject.org/koji/taskinfo?taskID=3380695
livecd-creator needs the grub.efi file in order to build images with EFI support. A grub-efi package that doesn't conflict with grub2 is needed.
(In reply to comment #3) > Fabian, can you confirm that you were using the Fedora 16 beta RC3 livecd from: > http://dl.fedoraproject.org/pub/alt/stage/16-Beta.RC3/Live/x86_64/Fedora-16-Beta-x86_64-Live-Desktop.iso > > If so, the build logs for the livecd are in koji: > > http://koji.fedoraproject.org/koji/taskinfo?taskID=3380695 Yes I used exactly that file.
(In reply to comment #4) > A grub-efi package that doesn't conflict with grub2 is needed. Note that grub (which includes efi) and grub2 only conflicts because the spec says so - there is no real conflict. (There is however a bug in grubby that prevent it from working correctly when both packages are installed - see bug 725185.)
Updating bug: pjones wants to create an EFI-specific grub-efi package which will not conflict with grub2, so I've filed a bug for that, and am making this a bug for spin-kickstarts to use that package once it exists, to render the live images once again EFI-capable. Proposing as NTH for F16 Final.
*** Bug 743972 has been marked as a duplicate of this bug. ***
Discussed at 2011-10-07 NTH review meeting. agreed we need to know exactly what change is needed to make the live images bootable again to make a decision on NTH status: if it's just putting grub-efi into the ks, then that's fine, if there's any changes needed to livecd-creator, we might not want to do that during a freeze.
*** Bug 744386 has been marked as a duplicate of this bug. ***
I've verified that just building the live image with grub-efi added to fedora-live-base.ks (and a grub-efi package available from a side repo, obviously...) is enough to make an image that boots successfully both via EFI and BIOS. So as soon as the updated grub goes stable we can change fedora-live-base.ks and close this.
Great. So if grub2 pulls in grub-efi it will solve the issue for us. :)
(In reply to comment #12) > Great. So if grub2 pulls in grub-efi it will solve the issue for us. :) I doubt it will do that. I hope it doesn't. We might be able to specify grub and instead get both grub-efi and grub2, but specifying explicitly what we want instead of relying on magic would IMHO be a better solution. (Or was it a joking smiley?)
commit 3c72e9eae4ed169f7f8c756c0fafdd0f24fe4b01 Author: Kevin Fenzi <kevin> Date: Thu Oct 13 09:20:03 2011 -0600 Add grub2, grub-efi and efibootmgr for EFI install/booting. Fixes bug #735023 grub2 and grub-efi don't depend on each other... I've added them to the ks files. They are also no longer in comps. This should hopefully do the right thing here.
that's correct, AIUI. it's not really right for grub2 to depend on grub-efi. if we had some sort of virtual 'bootloader' provides it could require both grub2 and grub-efi, but we don't, so just pulling them both in explicitly is the right thing to do.
the necessary change has been commited to spin-kickstarts: closing.
Thanks --efi install works for me on latest nightly F16 Live images.
does not work for me. i can put fedora 16 onto a stick with the --efi option, but only a grub promt appears when efi-booting it.
Works for Me WORKS WITH SoaS v5 Coconut and SoaS v6 Pineapple Command: sudo livecd-iso-to-disk --format --efi --overlay-size-mb 300 --home-size-mb 175 --delete-home --unencrypted-home Fedora-15-x86_64-Live-SoaS.iso /dev/sd(x) (x)=device name Ref: http://wiki.sugarlabs.org/go/Community/Distributions/Fedora-SoaS#MacBook_Persistent_SoaS_v5_and_SoaS_v6_EFI_Boot_USB
"does not work for me. i can put fedora 16 onto a stick with the --efi option, but only a grub promt appears when efi-booting it." Then it worked. Or else you wouldn't have seen a grub prompt. Clearly, you have *another* issue, but it's not this bug. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
its a grub command promt. anyway, you do not seem interested to solve it which i find disappointing. well, then lets leave it that way
(In reply to comment #21) Please note the component, and the bug description. This bug is about making *live images* EFI capable again, not about subsequent boot problems from the resulting stick. A GRUB prompt means it's not finding grub.conf so you need to find out why that might be. Maybe one wasn't created? Maybe it's empty or truncated? Maybe it's looking for it in the wrong location due to some EFI weirdness? [grub.efi and grub.conf get renamed to bootx64.efi and bootx64.conf on the resulting stick, so that .conf file is what you're looking for] Does the stick fail in the same way on a different EFI system? If you do find a fully intact grub.conf that looks properly formatted then you need to do some grub command line work to see why it might not be finding the grub.conf...no one else can do these things on a system having this problem except you. And yes of course it's going to have to go in a different bug report because it's a completely different problem than what's described in this one. If you need help poking GRUB with a stick I suggest the installation help forum at fedoraforums.org with a clear subject like "GRUB-EFI boot fail, only get a grub prompt".
chris, thanks for your help. ive found a post on fedoraforums.org which did not get any reply and represents my issue. this is why i filed bug 772505 . lets see if it will work with fedora 17.
see 1-) http://wiki.sugarlabs.org/go/Community/Distributions/Fedora-SoaS#MacBook_Persistent_SoaS_v5_and_SoaS_v6_EFI_Boot_USB Run "yum install livecd-tools" so it installs all the required dependencies and then use livecd-iso-to-disk script: sudo livecd-iso-to-disk --format --efi --overlay-size-mb 300 --home-size-mb 175 --delete-home --unencrypted-home Fedora-15-x86_64-Live-SoaS.iso /dev/sd(x) (x)=device name And: 2-)http://wiki.sugarlabs.org/go/Community/Distributions/Fedora-SoaS#MacBook_Pro_i7_CD_Boot Works fine for me as CD (64 bit) or USB built with script