Bug 754281 - Boot fails on Apple hardware with EFI
Summary: Boot fails on Apple hardware with EFI
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: syslinux
Version: 16
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-15 23:18 UTC by Matt Hirsch
Modified: 2013-02-13 21:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 21:12:29 UTC
Type: ---


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 633983 0 None None None Never

Description Matt Hirsch 2011-11-15 23:18:08 UTC
Description of problem:

Booting Fedora x86_64 media on a Intel Mac Pro fails. I have attempted to boot the following types of media on an Intel MacPro2,1:

On a DVD:
Fedora-16-x86_64-DVD.iso
On a CD:
boot.iso from /images on a mirror, retrieved today.

On a USB disk:
efiboot.img
efidisk.img

In all cases, I get the following message:

--------------
1.
2.

Select CD-ROM Boot Type :
--------------

No keyboard input is available at this menu, so I have to reboot the system using a long-press of the power button.

I have tried booting both using rEFIt, (attempting to load a BIOS boot image), and using the option key to select the CD or USB disk directly.

Steps to Reproduce:
1. Boot any of the above media on a MacPro2,1

Additional info:
This seems like a recurrence of bug: 527443

There is another open bug about F16 not booting on mac: 751147. I have filed a new one, since that seems like a video problem, and this occurs before the kernel is loaded.

Comment 1 Matt Hirsch 2011-11-15 23:21:53 UTC
Here is a link to the old bug, since I can't update the See Also field.

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

Comment 2 Adam Williamson 2011-12-07 18:31:36 UTC
pjones: does your comment from 527443:

"This is a firmware bug in the CSM on your platform, and there's nothing we can
do about it while still supporting UEFI on systems with working firmware. #c21
has a workaround."

apply to this case too?



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 3 Fedora End Of Life 2013-01-16 16:58:12 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

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

Comment 4 Fedora End Of Life 2013-02-13 21:12:33 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.


Note You need to log in before you can comment on or make changes to this bug.