You are not logged in.
I recently purchased an NVMe drive and decided to go clean with a new, fresh install of Arch. Following the instructions on the Wiki of course I set everything up like my old install opting for Systemd boot. I shut down cleanly then cracked the case open to remove the old drive (to prevent booting the old install) then booted up. Well my PC hangs at the bios splash so I thought I messed up a step so I plugged in the installer USB I had made, that won't boot either. So I then reconnected by old known working SSD that contains my old Arch install, guess what? Nothing. My Bios will just hang at the splash screen and boot overriding to that drive or any other drive results in nothing but a black screen, no indication of disk activity at all it just gives up! Both the old drive and the installer USB will boot on other PCs just fine. Here are some hardware details
CPU: Core i7-8700k
Mobo: MSI Z370 SLI Plus
NVMe drive: Samsung 970 Evo
EDIT: Removing the CMOS battery to clear settings worked, I had already attempted this before posting but I guess there was still a residual charge that kept the CMOS settings in the time I plopped the battery out and back in.
Last edited by Ryaniskira (2020-08-16 15:22:27)
Offline
I know this problem's marked as solved now, but it sounds like a problem with your motherboard firmware's UEFI implementation and I thought I'd share some input on the issue.
I had this problem on other distributions, including OpenSuse, Ubuntu, and even distributions based on Arch (particularly Antergos when that was still around). Oddly enough I never had it on pure Arch. If the boot entries were seemingly overloaded for any reason, the motherboard would just hang at the logo as well, and I had to remove the CMOS battery to fix it. My motherboard was a Gigabyte GA-Z97-D3H.
If people are having issues like OP's, I'd advise them to keep the amount of UEFI boot entries stored on their motherboard to a minimum, or keep an eye on the ones labelled blank or "UEFI OS". On that motherboard, those entries came from my USB drive and kept duplicating which led me to believe the lockup was due to overloading. I think some distributions' bootloaders did that too, actually.
Inactive.
Offline
You can boot into a UEFI Shell and delete your unneeded entries. You might find some rogue entries there as well. And of course CMOS reset will wipe everything clean.
Offline
I know this problem's marked as solved now, but it sounds like a problem with your motherboard firmware's UEFI implementation and I thought I'd share some input on the issue.
I had this problem on other distributions, including OpenSuse, Ubuntu, and even distributions based on Arch (particularly Antergos when that was still around). Oddly enough I never had it on pure Arch. If the boot entries were seemingly overloaded for any reason, the motherboard would just hang at the logo as well, and I had to remove the CMOS battery to fix it. My motherboard was a Gigabyte GA-Z97-D3H.
If people are having issues like OP's, I'd advise them to keep the amount of UEFI boot entries stored on their motherboard to a minimum, or keep an eye on the ones labelled blank or "UEFI OS". On that motherboard, those entries came from my USB drive and kept duplicating which led me to believe the lockup was due to overloading. I think some distributions' bootloaders did that too, actually.
You can boot into a UEFI Shell and delete your unneeded entries. You might find some rogue entries there as well. And of course CMOS reset will wipe everything clean.
The thing is though I don't think this had anything to do with rogue entries, even if I entered by UEFI setup (which I could still do) and manually selected a known working boot device it would just refuse to boot that device, it would just hang at a blank screen. The funny part is the same issue has made an appearance randomly, and not even clearing CMOS will fix it. I think I'm just going to smash this board and get a new one, that last Arch install bricked it and it won't even boot into the built in UEFI shell anymore.
It's not that huge of a deal, I can just a Z390 out of my stock (since it's compatible with 8tth gen CPUs), and after some looking I think I am going to avoid MSI products from now on.
Last edited by Ryaniskira (2020-08-18 02:19:24)
Offline