I have tried Linux as a DD on and off for years but about a year ago I decided to commit to it no matter the cost. First with Mint, then Ubuntu and a few others sprinkled in briefly. Both are “mainstream” “beginner friendly” distros, right? I don’t want anything too advanced, right?
Well, ubuntu recently updated and it broke my second monitor (Ubuntu detected it but the monitor had “no signal”). After trying to fix it for a week, I decided to wipe it and reinstall. No luck. I tried a few other distros that had the same issue and I started to wonder if it was a hardware issue but I tried a Windows PC and the monitor worked no problem.
Finally, just to see what would happen I tried a distro very very different than what I’m used to: Fedora (Kinode). And not only did everything “just work” flawlessly, but it’s so much faster and more polished than I ever knew Linux to be!
Credit where it’s due, a lot of the polish is due to KDE plasma. I’d never strayed from Gnome because I’m not an expert and people recommend GNOME to Linux newbies because it’s “simple” and “customizable” but WOW is KDE SO MUCH SIMPLER AND STILL CUSTOMIZEABLE. Gnome is only “simple” in that it doesn’t allow you to do much via the GUI. With Fedora Kinode I think I needed to use the terminal maybe once during setup? With other distros I was constantly needed to use the terminal (yes its helped me learn Linux but that curve is STEEP).
The atomic updates are fantastic too. I have not crashed once in the two weeks of setup whereas before I would have a crash maybe 1-2 times per week.
I am FULLY prepared for the responses demanding to know what I did to make it crash and telling me how I was using it wrong blah blah blah but let me tell you, if you are experienced with Windows but want to learn Linux and getting frustrated by all the “beginner” distros that get recommended, do yourself a favor and try Fedora Kinode!
edit: i am DYING at the number of “you’re using it wrong” comments here. never change people.
It’s not a RAM problem lmao it rarely crashed on Windows and it’s not crashed with Fedora either.
If you did a full memtest and it came out good then OK.
I’m just saying don’t discount hardware issues. Bad RAM blocks are notoriously hard to diagnose by use alone because there’s not just one symptom you can point at, and they can manifest themselves wildly differently on different apps and different OS depending how large the blocks are and how they are spread.
Luckily there’s a very simple and straightforward test you can make to put it out of your mind.
That doesn’t mean anything. I once had an issue where every few hours, a random application would crash on Arch Linux, but not on e.g. Debian or Windows. But this wasn’t an Arch issue per se, but was instead related to an UEFI overclock setting (which defaulted to on). After turning it off, everything worked fine.
So while it seemed like an Arch issue, it was actually hardware/overclock related, it’s just that the other OS wouldn’t run into the trigger for the crash.
Curiously that’s not as accurate as you might think. Different systems use memory differently, even just between different Ubuntu flavors or customizations. 1-2 crashes a week is not normal, unless it was consistently happening when you did something specific. Also, what exactly do you mean by crashing? Did you get a black screen with some error or the computer would just freeze or reboot?
That being said I don’t think this is likely to be a hardware issue. One thing that comes to mind is maybe swap, did you had swap on Ubuntu and do you have swap on Fedora now? If Linux runs out of memory it freezes, having swap prevents it from doing so, so if you have low enough memory it’s possible that it would get filled up and freeze your system without swap (Windows has the equivalent by default)
Crashes aren’t normal even in Windows. Rare crashes mean a hardware problem 99.7% of the time. Typically RAM as others have pointed out. The only way to figure that out is 4 passes of Memtest86+ without red. Yes 4 because the the first pass is a short one made to spot obviously bad RAM quickly. Less bad RAM might need more. I’ve had a case of 4 sticks that each pass on its own. Every two passed on their own. All 4 failed on the third or fourth pass. And if you think I tested for shits and giggles, I did not. I was see checksum errors on my ZFS pool every other day. No crashes. Nevertheless, if it wasn’t for ZFS I’d have corrupted files all over my archive.