BIOS update failed to boot Linux, while Windows starts normally.
BIOS update failed to boot Linux, while Windows starts normally.
Motherboard: Gigabyte Z790 AERO G (version 1.0) CPU: Intel i9 13900K GPU: Gigabyte RTX 4080 16GB GAMING OC Previous BIOS version: F8 Current BIOS version: F12e (latest, on their support page for the mobo) Bootloader: GRUB OS1 : Windows 11 (separate nvme drive) OS2 : Arch Linux (separate nvme drive) SECURE BOOT STATUS: OFF Steps before symptoms: I downloaded the update from the mobo support page Extracted the contents of a compressed folder Copied the extracted folder to a flash drive (formatted fat32) Restarted the PC, entered BIOS → Q flash utility Started the flashing process It finished without errors (as shown) The PC restarted three times before booting normally—displayed the motherboard logo and loaded GRUB (I’m unsure if ‘reboot’ is the right word here, but it seems how Gigabyte handles flashing) Symptoms after BIOS update and first boot: I pressed the ‘Enter’ key when ‘Arch Linux Linux’ appeared in GRUB. It started booting normally. When it asked for the password to unlock my encrypted volume (encrypted LVM), I began typing and the system stopped. I heard a relay-type switching sound and the machine rebooted. I think it’s the power supply making that noise, not the board itself. I attempted to boot into Arch Linux again, same outcome. Tried using the Linux-zen kernel as a backup; same issue—switching noise, then reboot. When I selected Windows 11 in GRUB, it launched properly and I logged into Windows without issues. The main problem is that after updating BIOS, Arch Linux fails to load properly. Symptoms include: after entering the password prompt for my encrypted drive, the system shuts down, followed by a relay sound and another reboot. I suspect the power supply is responsible for this behavior. I explored online solutions, found similar troubleshooting steps on Reddit and Arch Linux forums suggesting a BIOS reinstall after updates. To fix this, I tried chrooting into the installation media using an Arch Live USB, but it kept rebooting. I also attempted to switch to integrated graphics in BIOS and connected monitors via the motherboard for integrated mode. Eventually, I re-enabled XMP in BIOS settings and restarted, but the installation environment still wouldn’t boot. I tried using Ubuntu Live ISO as a test, but it also failed to load. I noticed my RAM clock speed wasn’t correct, so I re-enabled XMP, which resolved the issue. However, the problem persisted even after that fix. I’m unsure how to proceed further and feel stuck without a clear path forward. I’m open to reinstalling Arch if needed, but the dual-boot option is no longer viable. Thanks for your help!
Your BIOS will revert to standard settings once the update completes. You previously disabled secure boot, but most BIOS now defaults it back on. For reference, I currently enable secure boot on all systems. After updating, I usually run a command like sudo update-secureboot-policy --enroll-key. This also simplifies dual-boot configurations.
Consider reverting to the previous firmware release. The newest update might have introduced issues with essential Linux compatibility. On their support site, they mention microcode updates and security fixes. Have you installed the latest Intel Ucode package in Arch?
I only set up Arch on this device recently and transferred the configuration from my laptop. I turned off Secure Boot during installation and didn’t finish enrolling keys afterward. After updating the BIOS and encountering this issue, I verified Secure Boot was OFF—possibly the default setting. I think it might have been enabled by mistake, but I’m not certain anymore. I only disabled it briefly.
The issue is that the system keeps restarting even when I attempt to load the arch installation media or a live Ubuntu ISO on a flash drive. I think the relay switching noise comes from the power supply unit, so when something other than W11 loads, the PSU might switch off and then turn back on. I need to identify which process is generating this signal. I checked the wiki page but didn’t pay much attention. I wish I had followed that advice. Installing the previous firmware might also revert the microcode. I’m considering trying it out. Perhaps reaching out to Gigabyte support would help too. It’s hard to find much discussion about the latest firmware online.