[Bug 755093] Review Request: mactel-boot - boot tools for Intel Apple hardware

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=755093

--- Comment #17 from Mads Kiilerich <mads@xxxxxxxxxxxxx> 2011-11-24 09:39:37 EST ---
Resetting PRAM and NVRAM makes no difference - except that I now have
[root@fladmast ~]# efibootmgr -v
BootCurrent: 0000
Timeout: 5 seconds
BootOrder: 0080
Boot0080* Mac OS X
ACPI(a0341d0,0)PCI(1f,2)03120a00000000000000HD(6,17716800,5000,aa0b2ede-b4b7-4105-aafa-09b6daeb8fa6)
BootFFFF* 
ACPI(a0341d0,0)PCI(1f,2)03120a00000000000000HD(1,28,64000,34b7e09a-8a76-42fd-8cad-6a2aaa332fff)File(\System\Library\CoreServices\boot.efi)

But still, OS/X blessing through a symlink makes 'bless --info' report the
target file but the firmware will skip it and boot something else (the
unblessed boot.efi on ESP).

Another possible difference could be that I am using a file system created by
hfs-mkfs which thus doesn't have any UUID. That could perhaps prevent the
firmware from making an exact match on the blessed efi and make it fall back to
some other mode.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
package-review mailing list
package-review@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/package-review



[Index of Archives]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]