You are not logged in.
Pages: 1
Hey friends, I've installed Arch on all manner of computers and have run into a real head-scratcher this time.
The basic premise is that I can't fully boot the Arch ISO. I'm using the one I downloaded yesterday, 31 August, burned to a USB using 'dd'.
The freeze happens during boot 100% of the time but at various places nondeterministically. I've tried nomodeset, disabling bluetooth, not really sure where else to look. When the system freezes, naturally I can't look at any logs or anything.
Of note is the hardware, all of which is rather new:
- Gigabyte Aorus Elite x870 (with latest firmware, f7)
- AMD Ryzen 9950x3d processor
- NVIDIA RTX 5090 Ti
I do notice a message at boot from nouveau where it says it can't figure out what the GPU is. Could it be possible that this is the core of the issue? Since it's not booting into any sort of graphical user mode, and nomodeset doesn't work, I don't believe this to be the case but throwing it out there.
My sneaking suspicion is that this is related to the motherboard somehow...
Thanks. Please let me know what I can provide - maybe a couple video clips I can put on YouTube or something?
Edit - the hardware ultimately failed, however I am iffy on whether or not it is actually supported right now anyway.
Last edited by cloverskull (2025-09-07 19:05:38)
Offline
burned to a USB
Well, there's your problem. USB keys aren't heat tolerant, you should not burn them ![]()
Check the UEFI settings, make sure to use the most conservative RAM timings, increase the voltage to the CPU, disable PBO and try to boot w/ "maxcpus=1"
If it was nouveau, this would consistently fail at the kms switch and not when booting "nomodeset".
Do you get any error messages w/ "nomodeset" and https://wiki.archlinux.org/title/Genera … l_messages ?
Offline
This is a tough one. I'm not finding any pattern. It's really frustrating. I am starting to think my mobo isn't supported. I came across this post in reddit where someone was complaining about the mobo freezing as well: https://www.reddit.com/r/linuxhardware/ … s/mo8ka9d/
I've got two nvme drives. One already has Windows installed (yuck) but I'm not really sure where to begin insofar as what to do for a next step. I'm going to keep trying to see if I can pick up on any sort of pattern, though. My intuition tells me that the kernel doesn't support this hardware...but I really have no idea.
Offline
My intuition tells me that the kernel doesn't support this hardware
Phoronix got good results from that processor: https://www.phoronix.com/review/amd-ryz … 0x3d-linux
Perhaps you should answer seth's querstions. They are pretty good at getting things working when the OP cooperates.
Jin, Jîyan, Azadî
Offline
I've got two nvme drives. One already has Windows installed
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
Edit:
Check the UEFI settings, make sure to use the most conservative RAM timings, increase the voltage to the CPU, disable PBO and try to boot w/ "maxcpus=1"
Do you get any error messages w/ "nomodeset" and https://wiki.archlinux.org/title/Genera … l_messages ?
Any updates itr?
Last edited by seth (2025-09-05 07:24:13)
Offline
Thanks for the help, Seth and HoaS. I did follow all of Seth's instructions and it still kept locking up nondeterministically. I've given up on this motherboard because now it's decided it will no longer communicate with my GPU (it BETTER not be the GPU lol) and I have been reading horror stories about Gigabyte's products and their support. I'm getting an Asus mobo tomorrow and will hopefully confirm it was an issue with the Gigabyte hardware all along.
Offline
Have you tried an older iso, say 6 months ago, or Ubuntu 24.04 LTS? Also, run memtest.
Offline
I did not, however this mobo no longer boots at all. It's just a piece of crap (consistent with what I've been reading about Gigabyte of late
)
Offline
To those curious, the mobo was crap. I replaced it with an Asus 870e-plus wifi 7 and everything (literally everything) works out of the box. It all turned out great. Avoid Gigabyte!
So...this is technically not solved...but maybe I should put [OBE] in the title?
Offline
"[HW failure]" or "[broken HW]" - you might have to shorten/rewrite the present subject.
Offline
Pages: 1