Bug 459408

Alexey, do you know that your laptop has a UEFI or EFI BIOS?

Oh, yes! I have macbook pro. They support EFI and hdd formated as gpt. I have two os installed OS X and Fedora 9.

ok, then I need a full dmesg dump from your system (/var/log/dmesg would be good) to see the EFI firmware signing on.  Also, what does:

ls -al /proc/efi/vars/
ls -al /sys/firmware/efi/vars/

show?  Are they present?

[axet@axet-laptop ~]$ ls -al /proc/efi
ls: cannot access /proc/efi: No such file or directory
[axet@axet-laptop ~]$ ls -al /sys/firmware/efi
ls: cannot access /sys/firmware/efi: No such file or directory
[axet@axet-laptop ~]$

Created attachment 315015 [details]
dmesg

now, i'm under kernel f10 but i have same issues under fedora 9 kernel

was there ever a time when it did work?

your dmesg doesn't show any EFI sign-on, like it should, meaning the kernel doesn't think you have an EFI-enabled BIOS, so nothing which uses that (e.g. efivars and thus efibootmgr) will work either.

I know little of macbooks, so I'll have to defer to pjones.

Never, that is first time when i tried to play with efi under linux. That was first experement to switch from refit to grub loader...

I've also got a MacBook and can't use efibootmgr, but I hopse this could help to get around an annoying "white-screen" at boot-time when EFI scans the bootdevices.

Is there a way to help?

Any news on this - as this might be realted to the F11 EFI Features?

~Attention~

This bug appears to pertain to an important F11 feature, EFI, which the Fedora Community will be testing in an upcoming Fedora Test Day. Your participation in the action would be greatly appreciated!

More information:
https://fedoraproject.org/wiki/QA/Test_Days/2009-04-09
https://fedoraproject.org/wiki/Features/EFI

Actually there were no changes to efivars.c within the last year (and a couple of months) so I don't see a reason why there shall be changes ...
Using a rawhide kernel /sys/firmware/efi does not show up.

This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

So. A fresh install of Fedora 11 on a MacBook and the issues is still open and can be reproduced.

It is very anoying, as the boot-time is increased by 20secs or so ...

Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Same problem here. I've got a Macbook Pro as well, running Fedora 11.

In older releases of Fedora, I had to simulate a traditional BIOS MBR in order to be able to install and boot into Fedora. I don't know if this is still required for Fedora 11 as it should be EFI aware.

I just wonder if this fake BIOS MBR somehow confuses the system to believe it's looking at traditional BIOS hardware.

I would also love to see this issue fixed so I can fully manage my EFI boot configuration from linux.

This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.