Open kalrykh opened 1 year ago
Oh no!!! I just ran into that issue as well. I wonder if it's related to a recent btrfs-progs
update.
Let me check.
There has been no btrfs-progs update in a while (the next one won't land for another 12 hours and isn't changing any code that would affect this). The logs look like the pcie controller driver broke somehow.
Thanks. It's related to installing the latest stock 6.2.7
Fedora kernel. I'll provide instructions on how to recover from that in a sec.
Ok, here's how to recover from that.
boot into macos
sudo diskutil mount /dev/disk0s4
mv /Volumes/EFI-FEDORA/m1n1/boot.bin.old /Volumes/EFI-FEDORA/m1n1/boot.bin
sudo diskutil unmount /dev/disk0s4
(shutdown)
boot Fedora, and choose any kernel except for the first one
# remove the stock fedora kernel (this command is just an example -- adjust as needed)
dnf remove $(rpm -qa | grep kernel | grep -v asahi | grep 6.2.7)
Update:
Run the following to update the asahi-linux.repo
config -- which now has a priority value assigned to it.
This will prevent Fedora kernels from being installed.
curl https://leifliddy.com/asahi-linux/asahi-linux.repo --output /etc/yum.repos.d/asahi-linux.repo
vi...maybe I could convince you guys to package nano in for us non hacker types :P Thanks for the quick assistance.
Here's a better solution. Instead of using exclude
statements in the fedora repos, simply perform the following
curl https://leifliddy.com/asahi-linux/asahi-linux.repo --output /etc/yum.repos.d/asahi-linux.repo
This repo config now has a priority
value assigned to it -- which will prevent this from happening again.
[asahi-linux]
name=Asahi Fedora $releasever - $basearch
...
priority=1
The image has been updated.
Did a fresh install this morning of minimal, connected to wifi and ran dnf update and rebooted. Reinstalled again just to make sure it wasn't a one off, and it repeated. It tries to drop me into emergency mode but the keyboard doesn't work to try anything.