Summary: | Version bump: sys-boot/efibootmgr | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Chris Gianelloni (RETIRED) <wolf31o2> |
Component: | New packages | Assignee: | Gentoo Developers for the x86 Architecture <x86> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 120341 | ||
Attachments: | efibootmgr-0.5.3.ebuild |
Description
Chris Gianelloni (RETIRED)
2006-01-25 13:44:06 UTC
Created attachment 78103 [details]
efibootmgr-0.5.3.ebuild
# efibootmgr
Fatal: Couldn't open either sysfs or procfs directories for accessing EFI variables.
Try 'modprobe efivars' as root.
I guess I should have added this to the last post, too.
Works fine on IA64; cookie++ I've added this to the tree, it's up to the x86 team to add their keyword I don't think anyone on the x86 team has the hardware to test this right now. I am working to get access to the hardware now. If someone else can get access to a machine, or get me access to a machine, that would be great. I can verify that the software works insofar as it compiles/runs, but I am unable to verify that it can actually talk to EFI on x86 without an EFI-capable motherboard/system. efibootmgr does nothing on an x86 mac, because the efi boot manager isn't used as described in EFI 1.10 specs. equery l efiboot [ Searching for package 'efiboot' in all categories among: ] * installed packages [I--] [ ~] sys-boot/efibootmgr-0.5.3 (0) execute efibootmgr: hotzenplotz thomas # efibootmgr hotzenplotz thomas # as you see nothing happens. thee current mactel-linux patch has two small changes for efivars (replaces unsigned long with u64; field DataSize), see http://mactel-linux.org As far as i understand, no efi variables are existent: $ ls /sys/firmware/efi/vars/ del_var new_var so efibootmgr compiles, but is completley useless for x86 macs. OK. So the bug is "fixed" then with regards to it being bumped. There's nothing else to be done, since it isn't necessary for Intel-based Mac machines. Thanks for the info, Thomas! |