4:32 a.m.
I'd need to report this issue but I don't know which component to file it on.
Basically, I upgraded my MacBook Pro 11.1 from Fedora 29 to Fedora 31,
but the EFI boot manager now has both entries (Fedora and Macintosh)
pointing to OSX.
If you also have ideas about how to proceed and fix it it would be
most useful :D
Cheers
G.
--
Gianluca Sforna
9:12 a.m.
Hi!
For what is worth:
I had issues with UEFI mode. F28 or 29 work fine, but F31 hangs and doesn't
boot let alone installing or updating.
Regards,
Silvia
FAS: Lailah
On Mon, 30 Dec 2019 at 13:33, Gianluca Sforna <giallu(a)gmail.com> wrote:
I'd need to report this issue but I don't know which
component to file it
on.
Basically, I upgraded my MacBook Pro 11.1 from Fedora 29 to Fedora 31,
but the EFI boot manager now has both entries (Fedora and Macintosh)
pointing to OSX.
If you also have ideas about how to proceed and fix it it would be
most useful :D
Cheers
G.
--
Gianluca Sforna
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
1:57 p.m.
On Mon, Dec 30, 2019 at 3:33 AM Gianluca Sforna <giallu(a)gmail.com> wrote:
I'd need to report this issue but I don't know which component to file it on.
grub2, efibootmgr, efivars, or possibly the kernel - it really is
complicated what might have gone wrong.
Basically, I upgraded my MacBook Pro 11.1 from Fedora 29 to Fedora
31,
but the EFI boot manager now has both entries (Fedora and Macintosh)
pointing to OSX.
If you also have ideas about how to proceed and fix it it would be
most useful :D
First it's necessary to collect evidence for the autopsy. Fixing it
destroys the evidence of what's wrong and makes it impossible to
figure out how it got into the wrong state in the first place, so that
a proper fix can happen rather than just a one off work around after
the problem has already happened.
If you can manually boot off a USB stick with a Fedora install image
on it, post the following to the bug report:
efibootmgr -v
ls -l /sys/firmware/efi/efivars
Mount the ~200MiB hfsplus volume with label 'Fedora' that Fedora uses
on Macs as the EFI System partition. Usually this is /dev/sda3 these
days, but you should check with 'lsblk -f' e.g.
[chris@fmac mnt]$ lsblk -f
NAME FSTYPE FSVER LABEL UUID
FSAVAIL FSUSE% MOUNTPOINT
sda
├─sda1 vfat FAT32 EFI 67E3-17ED
├─sda2 apfs 9bb9a8cd-acb8-43cf-b89e-4c4561e562de
├─sda3 hfsplus Fedora c0c132b1-666c-38d9-9cc0-3f003a2998dd
175M 13% /boot/efi
├─sda4 btrfs fedora b8e290d5-1dc5-429f-8201-10ca5b2c0b95
88.3G 15% /mnt
├─sda5 ext4 1.0 e2a8c0dc-f591-431b-b8e3-50d19610522f
743.1M 39% /boot
└─sda6
Once that's mounted, locate and attach to the bug report:
EFI/fedora/grub.cfg
EFI/fedora/grubenv
Next mount the /boot volume which is typically a plain ext4 volume
~1GiB in size. Locate and attach to the bug report:
loader/entries/*.conf
At least post one of those conf files but maybe attach all of them.
And last, mount the / volume. Locate and attach to the bug report:
etc/default/grub
Needless to say, bootloading is complicated.
--
Chris Murphy
4:50 p.m.
On 12/30/19 11:57 AM, Chris Murphy wrote:
If you can manually boot off a USB stick with a Fedora install image
on it, post the following to the bug report:
efibootmgr -v
This would be the most important information to start with. From the
description, grub is not getting loaded. So the question is, what
happened to the EFI entry? Is it somehow pointing to OSX or did
something happen to grub and the BIOS is falling back to the other
available option after failing to boot it?
5:33 p.m.
On Mon, Dec 30, 2019 at 3:51 PM Samuel Sieb <samuel(a)sieb.net> wrote:
On 12/30/19 11:57 AM, Chris Murphy wrote:
> If you can manually boot off a USB stick with a Fedora install image
> on it, post the following to the bug report:
> efibootmgr -v
This would be the most important information to start with. From the
description, grub is not getting loaded. So the question is, what
happened to the EFI entry? Is it somehow pointing to OSX or did
something happen to grub and the BIOS is falling back to the other
available option after failing to boot it?
Ahh I missed the part where it's not getting to GRUB.
In that case, a short term work around is to hold down the option key
before the boot chime ends, and the firmware's built-in boot manager
should appear, and display more than one boot option - hopefully
obviously one of them is Fedora (or at least not macOS).
There is a mechanism in shim.efi for adding itself as a boot entry in
NVRAM, if it doesn't exist. So it might turn out doing this solves the
problem and leaves no trace of why the trouble began in the first
place. But I'm content with that outcome, and assuming it all worked
out as designed. :-D
--
Chris Murphy
1588
days inactive
1588
days old
4 comments
4 participants
participants (4)
-
Chris Murphy -
Gianluca Sforna -
Samuel Sieb -
Silvia Sánchez