I think if you start with political positions of bigtech companies...
Just buy used
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
I think if you start with political positions of bigtech companies...
Just buy used
Buy Intel used so that you're not directly contributing?
Other than that or AMD, your only other option is ARM.
Can you go and buy an ARM CPU and build a desktop system with it?
Yes.
Not many, but they exist. I think most of them come soldered to the board like laptops.
I have a Zen 2, Zen 3+ and a Zen 4 system and they all work well very with various Linux distros (Arch, Fedora) and recent kernels.
It's very likely that your bug is specific to early Ryzen CPUs/chipsets. A couple of folks on those reports mentioned their issues went away after a motherboard/BIOS upgrade. So I think you'll be fine if you went for a more recent AMD CPU+mobo.
I've heard that newer Ryzens play nicer with Linux.
Yeah, my 5800X3D works perfectly; absolutely zero issues. I'm guessing it's making use of the 3DvCache too since I don't notice any performance degredations compared to Windows.
Yeah First Gen Ryzens definitely had a Linux lock up bug. My x1700 had it all the time and could never fix it.
This is pointless. Your tax dollars are doing MUCH more for Israel than what products you buy. Boycotts are a capitalist distraction from the real systemic issues.
His point wasn't to find a CPU, it was to make a political post in a tech community.
I agree. We need more of these!
Buhruh! Why not just stop voting since "your vote is only a drop in the ocean" or "it only legitimises a broken system"?
Every action towards progress counts. It's better than nothing, which is what people do if you ask them to change the world in one go. Change is gradual, change is slow, change can be achieved by the small actions of many. Not everybody has the time to "tackle the systemic issues" you perceive to be true nor does everybody agree that those are the core issues.
Belittling action, no matter how small, is discouraging and counterproductive.
Not when there's an organised boycott, called for by Palestinians. You can do multiple things at once. Not buying something takes 0 hours of your time lol
I have a system with a Ryzen 1700 with the same issue and have found the only reliable way to run it is by installing and enabling the disable-c6-systemd package from the AUR. The other fixes provided in the wiki article you linked are correct but aren't sufficient on my system, the CPU keeps reenabling the C6 state on its own and the disable-c6-systemd package works to counter that. The reason it works on Windows is they've disabled the C6 state by default for the CPU.
This is amazing to find out now after 7 years:) I actually adjusted voltage manually on my Ryzen R5 1600, and it became 100% reliable, apparently the fix you mention prevent voltage below 1v at idle. I wondered why my CPU wasn't reliable unless I made manual OC with some voltage tweaks?
I never looked it up, because my OC solved the issue, but I always thought it was a bit weird.
Ah, thanks. I'm using runit not systemd (although this was happening on systemd when I was on systemd too) but I saw amd-disable-c6
in the AUR so I've installed that now, fingers crossed it works (the fixes in the Arch Wiki article haven't fixed it for me, it just happened again rip)
Edit: nvm, looks like that package is a systemd service
The package is just a systemd unit to run the command python zenstates --c6-disable
so if you install the zenstates-git package and get runit to run that command at startup it would be equivalent.
Thank you!!
Edit: Tried running that, I'm getting the error that /dev/cpu/0/msr
doesn't exist. dev/cpu
doesn't seem to exist at all on my machine. Hm
Edit 2: You need to run sudo modprobe msr
. All good now :)
Ah, that sounds a bit unfortunate. I've run AMD CPUs on Linux desktops with Bulldozer / Piledriver / Ryzen 7, my current laptop is a Ryzen 7 as well, never run into that at all. Hopefully the Arch wiki will sort you out. If not that, the third option would be 'install Linux on an M-series Mac' - don't know how feasible it is at the moment, and paying the 'Mac premium for hardware and software integration and then overwriting the software' doesn't make a lot of sense to me.
I have has zen2 and zen3 systems and haven't run in to that either. So Zen2+ systems should be mostly fine.
If you get an M1 or M2 mac it should mostly work. If you need thunderbolt(WIP) or vulkan(WIP) then you will have to wait. Otherwise accelerated desktops work and audio is working now. Honestly if you compare performance to competing systems, they end up pretty similar in pricing.
Well, that brings to light why I had an issue with my 3900x. Couldn't find it on google to save my life, but then it shows up randomly here, lol.
If it means anything, my 7800x3D doesn't have that bug. I've been using it now for about 3 months without issue. So maybe the rest of the 7000 series is good to go?
EDIT: I'd also like to mention that I'm heavily biased against Intel processors for that long line of severe security issues that they had on their processors a few years ago. I don't trust them at all.
I've never had any issues with Ryzen, but I never had first gen. If you don't want Ryzen, and Intel is unethical, maybe you could try a Epyc /s?
Buying used Intel stuff might also be an option. No more money would go to Intel, and using used stuff is good on the e-waste front.
Print your own
...in 10 years
I never managed to fix this bug with my first gen Ryzens. Worth upgrading to something newer for sure.
Ah. I'm getting this answer a lot actually. I might try a newer Ryzen then if a lot of people are saying the newer Ryzens work
Newer ryzens are better, especially because they get frequent updates to their microcode that fixes a lot of the issues you're experiencing.
I have this same bug on the same platform! It was infuriating to track down. I was able to get around this by disabling c-states in the bios. I've heard that updating your aesga firmware also helps, but I can not confirm that.
Here I was hoping we would get a breakdown on the companies making ARM processors ... Still an informative comments section.
My Ryzen 5700u work great with Debian, so as others said, consider upgrade CPU on your am4 motherboard, better buy apu since it always feels good to have backup gpu in your system in case main gpu breaks
Modern Ryzen are fine on Linux. Not sure where they're declaring it happens for "all Ryzen" from.
As I understand, early ryzen processors are generally more buggy. I run 5800x on my desktop and a 5600(x?) in my server. You could try a newer ryzen and see if it works. I would recommend shopping around for a decent warranty.
RK3588 is used in many Linux devices, but I'm not sure if Rockchip is in the BDS list. I don't know which factory was RK3588 from.
Get another AMD chip, you've just been unlucky. I've had AMD running Linux for 5 years with no issues.
What kernel version are you seeing that lockup bug on? I have a similar bug on Ryzen 5 2600x with kernel versions >= 6.7. 6.6 is fine.
More directly: Buy used. Lots of reputable sellers on eBay and their returns policy for defective products is unbeatable.
I had a similar problem with a Ryzen 5 1600, at first it worked flawlessly when I did a manual OC, then when I made a reset, I didn't care to OC again, and it began to occasionally freeze, usually when idle. When I made my manual OC again including upping voltages a bit for CPU and RAM it worked flawlessly again???
Weird since motherboard defaults aught to be stable IMO, but apparently they aren't always.
I've been using this CPU for 7 years now, and it still runs like a champ, as long as I don't use the motherboard defaults. I can't remember last time it crashed or froze.
EDIT:
I just found out the package "disable-c6-systemd" mentioned in your link, is exactly to prevent voltage drop below 1v at idle, which sounds exactly like the bug I had. which is funny to learn 7 years later. ;)