-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Boot/Bootloader issues #9
Comments
Hey @mikeeq thanks for the awesome work! I quickly tried this out last night and wasn't able to get it to boot past GRUB (black screen after a few initial messages). Given the timing of the black screen, I'm pretty sure it's a graphics issue. I'm going to try again tonight by blacklisting the Radeon Pro drivers, but would be awesome to know if anyone else has experienced this issue on a similar model. Specs Update: installing in basic graphics mode fixed the issue. First boot after install was successful without requiring basic graphics. Now if only I could get it to boot with WiFi working 😞 |
Do not consider an issue but I just want to share my experience... at some point in time, maybe after updating kernel to v5.6.13, my grub menu with the latest 3 kernels disappeared and my mbp was booting automatically in v5.6.13 (which has a problem with displaying Function keys). After a lot of searching and trying various useless solutions...I found out this command that solved it:
|
@andyrichardson I have the same issue, It said something about wifi set to 1, then nothing happened and the text is stuck on the screen. I tried all the boot options but they all gave me the same thing. I have a 2019 macbook air. |
Same on a macbook pro 2015 15' |
I cannot unlock the disk with the laptop keyboard, only by adding an external usb one. Once booted the laptop keyboard works fine. I reported this bug to fedora previously but it was fixed somehow |
@kenfallon I'm not sure why you've raised a bug on Fedora's bugzilla for that. Are you using my build of Fedora - mbp-fedora? What model of Macbook do you have? I'm using LUKS encrypted OS partition on my Macbook 2021 with my build everything works as it should - internal keyboard on grub and next on LUKS screen where you need to type your password. This line is responsible for making sure that you have hid_apple and apple_bce drivers available on boot - https://github.com/mikeeq/mbp-fedora/blob/f36/fedora-mbp.ks#L50 Make sure that you have those in dracut config and rebuild dracut. |
First, thanks for the pre-built Fedora images! I would have simply not bother trying anything without them. Everything worked fine except one really nasty issue that took me many hours to understand and fix: my 150MB What made things super confusing is Linux could still successfully mount /boot/efi ! While neither the macOS chooser nor To solve this I reformatted and restored the /boot/efi partition from Linux. |
Sorry was away with life issues. To clarify I was running native Fedora before, and it got fixed. Then I installed where the issue cropped up.
I tried to understand how to do that when I had the issue on native Fedora. I there a how to somewhere that I could follow ? |
I just wiped the disk. Reinstalled everything from scratch with the latest OSX and installed the latest version I encrypted the disk with luks and got the same issue. Namely the laptop keyboard is not working to decrypt the drive. I can decrypt the drive with an attached usb keyboard. The laptop is reported by lshw as a MacBookPro14,2 *-core After install this is what was in /etc/dracut.conf.d/apple_bce_install.conf Following your tip from above I tried the following without success.
|
Macbook Pro early 2019 1st boot lands me at the grub cli. If I reboot and pick the second EFI drive, it seems to go straight to the final stage for crpysetup. Tried to reinstall, but this version not seeming usable on this Macbook Pro. Thanks for the work, may try this on a different older Macbook I have later. |
Please post any boot related issues here.
Most of them should be fixed in v5.4.8-f31 release.
Historic issues:
The text was updated successfully, but these errors were encountered: