Summary: | (U)EFI-supported install media | ||
---|---|---|---|
Product: | Gentoo Release Media | Reporter: | BRULE Herman <alpha_one_x86> |
Component: | All ISO | Assignee: | Gentoo Release Team <releng> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | bkohler, grknight, pacho, rentorbuy, sven.koehler, vamp898-gentoo, viklevin2, zerodaylinuxm, zmedico |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
00-rework-uefi-support.patch
01-grub-uefi-config-generator.patch 02-no-bundle-kernel-in-efibootimg.patch |
Description
BRULE Herman
2011-06-06 20:29:24 UTC
do not add arches by yourself. Thanks. We need more info. What "platform" are you talking about? What version of the installcd did you try? Did you try passing some kernel options? If the boot failed, where did it stop and what messages did you get? I'm talking about UEFI 2.3 platform on hardware AMD 64 -> then UEFI x86_64
I have try all:
gentoo-livedvd-amd64-multilib-11.0.iso
gentoo-install-amd64-minimal-20110421.iso
and all variant version.
> Did you try passing some kernel options?
No because it not detect cd as bootable, then no efi compatible bootloaded is loaded (I have see elilo, but it not detected)
It's say:
Boot Failed. EFI DVD/CDROM
I need to get grub2 into the new cdtar used by catalyst. *** Bug 507684 has been marked as a duplicate of this bug. *** Currently UEFI is supported in the beta of the livedvd which will be finalized in the coming weeks, after which time we will work into getting this EFI boot images into the catalyst builds. If you wish to use a gentoo media with UEFI now, you should test the images at #gentoo-ten and report back your boot success. I can start testing at earliest on 23.04. when im back at work. Will try and give back results. *** Bug 537016 has been marked as a duplicate of this bug. *** I can report success on booting livedvd-x86-amd64-32ul-20140826.iso on my Asus Laptop via UEFI. I'm really happy that I can now progress with my UEFI install of gentoo on my new Laptop. Problem with many other UEFI bootable ISOs was that they either wouldn't boot (systemrescuecd: screen remains black) or the kernel's ahci driver has issues with my Samsung XP941 SSD. Now please port the UEFI support from the livedvd to the install and the admincd ISOs please - pretty please with sugar on top. We are getting more requests on UEFI installs in #gentoo. Currently, we are forced to tell them that sysrescuecd or the Gentoo LiveDVD or create a vfat, USB drive with grub-2 installed are their only options to install. The minimal just won't work without being able to boot in EFI mode and having EFI vars available (either CONFIG_EFI_VARS or the new EFIVAR_FS. Please expedite any work on the minimal ISO. I can test any medium created. *** Bug 609284 has been marked as a duplicate of this bug. *** At this point, if the minimal install CD can't support (U)EFI for whatever the reason then maybe it would be a good idea to clearly say so in the official handbook. A user who follows the handbook gets the impression that the Minimal iso should be used by default for any installation, including UEFI. The handbook could also suggest how to check if the install media was truly booted with EFI (otherwise, things like grub-install --target=x86_64-efi --efi-directory=/boot/efi won't work) as the BIOS/UEFI firmware might skip to the "next bootable device" without the user noticing (eg. check for /sys/firmware/efi). The DVD image is rather big for an installation so many users now prefer to use SysRescCD as it's practically the same size as the Minimal ISO. It might be interesting to see if UEFI support can be backported from SysRescCD to Gentoo Minimal. I haven't checked the Minimal's kernel config options but is it just an issue with enabling CONFIG_*EFI* options or is there more? (In reply to Vieri from comment #12) > I haven't checked the Minimal's kernel config options but is it just an > issue with enabling CONFIG_*EFI* options or is there more? That's only part of things (and should already be on). What has to change is the building of the ISO to include the new syslinux and config files to support it. Possible a bit more too. I've been told these are in progress. I will be moving this implementation forward in the near future as this should have been already supported on our catalyst build long ago and I apologize for those that have been waiting patiently. I will MAKE time to get this done once and for all. Thank you all for your patience! *** Bug 641754 has been marked as a duplicate of this bug. *** Created attachment 513168 [details, diff]
00-rework-uefi-support.patch
I've been working on a set of patches to add (working) amd64 UEFI support to catalyst. My main testing has been with grub2 but the catalyst code is flexible enough to support others. Here is the first patch fixing general amd64 UEFI building.
Created attachment 513170 [details, diff]
01-grub-uefi-config-generator.patch
This patch adds a config generator for grub2. This will create a basic 2-entry boot menu. Alternatively one could supply a fancier premade grub.cfg in their grub2-enabled cdtar.
Created attachment 513172 [details, diff]
02-no-bundle-kernel-in-efibootimg.patch
This patch makes a more efficient build by eliminating a duplicate copy of the kernel/initramfs in the embedded EFI system partition (using only the one in the iso's /boot instead)
This isn't strictly required for a successful UEFI boot but will save space on the generated iso.
Use this script/project to generate a new cdtar including grub2, which will work with the above catalyst changes: https://github.com/benkohler/cdtar-grub2 If you do not want to use this particular cdtar format or don't want grub2, just build your own cdtar with a /boot/efi or /boot/EFI or /gentoo.efimg file inside, and this will activate the amd64 UEFI code in catalyst. Testing & feedback of these changes would be appreciated, and FYI you can find me on freenode #gentoo-releng & other places if you want realtime discussion. Thanks This should be working now in install-amd64-minimal-20180823T214504Z.iso (and all future builds), please reopen this bug if you still have problems. |