Bug 1426751 - macos startup disk panel doesn't show Fedora as a boot option
Summary: macos startup disk panel doesn't show Fedora as a boot option
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: mactel-boot
Version: 26
Hardware: x86_64
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Matthew Garrett
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-24 18:21 UTC by Chris Murphy
Modified: 2018-05-29 11:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-29 11:33:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
macOS startup panel, F23 (86.78 KB, image/png)
2017-02-28 03:04 UTC, Chris Murphy
no flags Details

Description Chris Murphy 2017-02-24 18:21:51 UTC
Description of problem:

In macOS, System Preferences > Startup Disk panel doesn't show Fedora anymore. The firmware boot manager does show it.


Version-Release number of selected component (if applicable):
macOS 10.12.3
mactel-boot-0.9-13.fc24.x86_64

How reproducible:
Always with these versions


Steps to Reproduce:
1. macOS installed > Fedora installed (both default installations)
2. boot macOS
3. System preferences > Startup disk panel

Actual results:

Only macOS shows up as a boot option.


Expected results:

macOS and Fedora should show up as boot options.


Regression testing:
Problem doesn't happen with:
Fedora-Live-Desktop-x86_64-20-1.iso
Fedora-Live-Workstation-x86_64-23-10.iso

Problem first appears with Fedora-Workstation-Live-x86_64-24-1.2.iso and persists in Fedora 25 and Rawhide.

Comment 1 Chris Murphy 2017-02-28 03:04:35 UTC
Created attachment 1258247 [details]
macOS startup panel, F23

macOS 10.12.3 (Sierra) and Fedora 23. Screenshot shows that macOS sees the F23 ESP, however apparently something is new in macOS where it doesn't actually like something about it (no real kernel, and no way to build boot cache, functionally the same thing as initramfs on Linux). And NVRAM is not modified to boot Fedora as a result.

Comment 2 Fedora End Of Life 2017-02-28 12:26:19 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 3 Fedora End Of Life 2018-05-03 09:04:27 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 EOL if it remains open with a Fedora  'version'
of '26'.

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.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 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  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

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.

Comment 4 Fedora End Of Life 2018-05-29 11:33:25 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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.