Dr. Hax's avatar
Dr. Hax Dr.Hax@hax0rbana.org 2 years ago
A quick update: 1. Thank you to all who shared, zapped, offered suggestions or offered help in other ways. The community response was large, wonderful and unexpected. 🫶 2. A new CPU didn't fix it. I was skeptical, but it was too easy of a fix to not try it. On the bright side, it might be cheaper than I was expecting. 3. I ordered a new motherboard from newegg (they take bitcoin) and it'll arrive by Friday. The #Qubes hardware compatibility list tells me it'll work. I really hope it'll work without having to reinstall the O/S. 🤞 I'm going to try to stop stressin' and relax for the rest of the night. Next week, I plan on #building. View quoted note →
↑ Parent

Replies (6)

Dr. Hax's avatar
Dr. Hax Dr.Hax@hax0rbana.org 2 years ago
New motherboard arrived and I have confirmed that was the problem. Wouldn't boot into the existing M.2 drive, after many attempts at rescuing it (grub2-install, copying over .mod files, etc.), I got it almost restored. If I manually load the grub2 config file, enter the FDE password, it gets right up to when X would normally load and then it resets. I'm not sure if it's some driver causing a fault or what.
1 replies ↓
Dr. Hax's avatar
Dr. Hax Dr.Hax@hax0rbana.org 2 years ago
I had a fairly recent proper backup, and I've copied some files to an external drives. So a full reinstall won't be too terrible if it comes to that. I shouldn't lose more than a week's worth of work at the most. I have one more trick up my sleeve that might work, and then a last ditch effort that will require borrowing or buying some hardware. It'll probably be until early next week before I am back up and running.
↑