You are not logged in.
I have 3 NVME M.2 SSDs in my system running software raid (mdraid) with LVM on top.
Yesterday I apparently reset my BIOS by accident (I must have hit the reset CMOS button on the motherboard or something), so I decided I may as well update my BIOS now since I have to reconfigure everything anyway. I updated my BIOS to version F31e (see https://www.gigabyte.com/Motherboard/X5 … t-dl-bios)
Then I tried to boot my system and realized the EFI boot entries for my Arch install was gone.
After panicking for a little bit I made an Arch install USB stick and booted from it. I found my RAID and LVM partitions, all working as they should. I mounted all my partitions under /mnt as I did when first installing Arch, "arch-chroot"-ed into /mnt and re-ran the GRUB install command:
grub-install --target=x86_64-efi --efi-directory=/esp --bootloader-id=ArchThis restored the EFI boot entry and gets me into GRUB, but when I try to boot I just get here:
https://i.imgur.com/cg12pbT.jpg
I'm frozen here and can't get any further.
I did a cold boot just in case and the "Hardware Error" lines no longer show up, but I still freeze at the same spot. I also tried "nomodeset" in desperation, no difference.
Any ideas on how to proceed?
Mod note: Replaced oversized image with URL. Please read the code of conduct and adhere to the image posting guidelines.
Last edited by Hubro (2020-11-05 21:41:42)
Offline
Have you tried switching to e.g. TTY2? Do you get access to a getty instance there?
Assuming you don't, see https://wiki.archlinux.org/index.php/Ge … t_problems notably the debug output.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Have you tried switching to e.g. TTY2? Do you get access to a getty instance there?
Assuming you don't, see https://wiki.archlinux.org/index.php/Ge … t_problems notably the debug output.
Ah, thanks a lot for that link, that will come in handy in the future.
Luckily I figured out the issue shortly after posting the question. Turns out my "Initial display output" was set to PCI-1 by default, and I have that GPU bound to vfio-pci as per this guide: https://wiki.archlinux.org/index.php/PC … ng_the_GPU
I set the initial display output to PCI-2 and now my PC boots as it should. All the weird errors are still there though, but after some googling it turns out those are to be expected after updating to the newest AGESA...
Offline