Thanks for the TL;DW, I can go about my Arch updates without fear now…
Thanks for the TL;DW, I can go about my Arch updates without fear now…
Never heard of it, but still, sad to see something ending… seems like it was a good learning resource.
It does seem like a hardware issue to me too…
It might be a driver issue… Windows does have the resources to test them more than Linux community, so - kinda hardware related - but Framework should be able to help here.
And as others have said, try memtest, I did on a laptop with similar issues to yours and found the RAM was the culprit. Personally, I recommend using this version, not the passmark version: https://memtest.org/
It’ll boot from a USB stick
It will take hours.
For Linux use ‘sudo journalctl -xe’ (from memory) - it’ll explain the issues it finds, as best it can. You’ll probably see something in there
If you’re dual booting with Windows open the event log viewer and check under System (from memory) and see if there’s any red X warning logs… esp. Hardware ones.
On the up-side, at least you have a chance of fixing it… If that happened on a Windows box, you’d be reaching for the gun / installation media by now
Similar here.
MythTv + Firefox + VLC - all on Arch
Used to be easier when Myth was in the main repos, now I have to compile from AUR, but it’s still ok