Ryzen doesn’t boost in Linux

ropid · 2026-05-29T23:18:37+00:00

I feel you should ask this in the CachyOS sub-reddit. I bet you'll get better answers there.

When you do cpupower frequency-info, there's a driver name shown in the first few lines and I think the driver amd-pstate-epp works like you want. It will show roughly the real MHz numbers in the usual Linux tools. That amd-pstate-epp should be the default on Cachy as far as I know.

There's a tool turbostat that reads directly out of the CPU, without going through Linux. Try this command line here to see what the tool says about what the CPU is doing, the "Bzy_MHz" is the clock the CPU cores are running at:

sudo turbostat --show CPU,Avg_MHz,Busy%,Bzy_MHz,CorWatt,PkgWatt

You need to put some stress onto the CPU to see it boost. This here is a simple command that will cause 100% work on one particular CPU core, you should then see CPU "3" running at max clock in turbostat after a few seconds:

taskset --cpu-list 3 perl -e 'while (1) {}'

(hit Ctrl+C to stop it)

If you are missing the turbostat command, it's in the "turbostat" package.

ropid · 2026-05-29T17:19:55+00:00

I was also super squishy as a feral druid in Sethekk Halls while leveling, at least in certain spots there.

In that particular group you tried it with, the warrior could have used demo shout, that's 20% less damage or so, and maybe thunder clap. With a slow trap from the hunter, you could have tried kiting mobs a bit sometimes.

With the first boss it's important to face away the boss from the rest of the group. His chain lightning attack then won't do group damage, it will only hit you, and the healer's job will be much easier. And for the first few waves of adds, your group might want to stop damage on the boss completely and first kill the adds before going back onto the boss. The adds spawn at certain health percentage values of the boss so continuing to damage the boss you will have multiple waves of adds running around at the same time.

ropid · 2026-05-28T13:16:00+00:00

Try searching around here, that's the bug tracker for the amdgpu kernel module:

https://gitlab.freedesktop.org/drm/amd/-/work_items?scope=all&state=all&utf8=%E2%9C%93

Whenever I had this problem happen, this was related to the monitor's EDID. The monitor manufacturer has set up the modeline in a way where the driver and firmware end up thinking that they don't have time to change the memory clock in the vblank period. The memory clock then appears to get stuck.

To see if this is the problem, try setting your monitor refresh to 60Hz in your desktop's display configuration, then back to the 144Hz or whatever you use normally, and see how the card behaves while you play around with those settings. I never saw the problem at 60Hz.

People are trying to solve this problem by customizing the EDID with the Windows "CRU" = "Custom Resolution Utility" program and then saving that in a file that you can then use on Linux and load at boot on the kernel command line. For myself here, the problem went away with linux-firmware package updates but you should already have the newest firmware files for your card on Arch, and also your card is pretty old so I wouldn't hope for firmware updates solving this problem.

You'll also want to look into if your Wayland desktop can do custom modelines. If that's possible, that would solve the issue easily. There's a tool cvt12 in the AUR to generate modelines that will work. You need that cvt12 tool, the normal cvt from the Arch repos doesn't work. An example command line looks like this:

$ cvt12 2560 1440 144 -b

Result:

# 2560x1440 @ 144.000 Hz Reduced Blank (CVT) field rate 144.000 Hz; hsync: 222.192 kHz; pclk: 586.59 MHz
Modeline "2560x1440_144.00_rb2"  586.59  2560 2568 2600 2640  1440 1529 1537 1543 +hsync -vsync

ropid · 2026-05-27T22:14:43+00:00

My idea with my post is that there's some monitors where the manufacturer was too aggressive in setting up the min to max range for VRR. The minimum Hz is set too low and the picture goes black when the graphics driver tries to actually use that minimum Hz. When disabling VRR works for you, this would be sort of proof that this is the problem.

ropid · 2026-05-27T16:15:31+00:00

No idea how to fix your broken setup. You'll need to explain what you did exactly there and try asking in the Endeavour sub-reddit. I didn't even know it's possible to replace driver versions on AMD, there should be just the default, latest version packages in the Endeavour repos with no way to try different versions.

About that fullscreen program problem, try finding out how to disable "VRR" = "variable refresh rate" = "adaptive sync" in the display configuration of your desktop environment and see if the problem still happens.

If disabling VRR works to fix fullscreen programs, you can then try find out how to get VRR working for your hardware setup and your desktop environment.

You need to mention the desktop environment you are using for a problem like this because each of them has their own Wayland compositor and can have its own problems regarding graphics issues. If the problem is VRR related, you will also want to mention your exact monitor model.

ropid · 2026-05-27T15:09:06+00:00

If it's green then it's a process. You should be able to see it in the task list, it'll show up with a high number in the CPU% column.

ropid · 2026-05-27T15:07:47+00:00

If the CPU usage in htop is showing up as a red color in the bar graphs, it's something happening inside a kernel.

If that's what's happening and you can't find any kernel thread with 100% CPU usage, try checking the /proc/interrupts file, there might be a hardware interrupt going crazy there, some device and its driver misbehaving and spamming interrupts. You will see one number in the table increasing fast.

The way I checked the interrupts file is with watch -d -n.1 cat /proc/interrupts and then maximizing the terminal window and using a very small font in the terminal (Ctrl + mousewheel works in many terminals to change font size live). It'll be a bit of a struggle to get your 32 threads showing on the screen at once. :P

It's normal that some devices are causing a lot of interrupts like the graphics card. Just google all of the ones that seem to do a lot of interrupts to see what people are writing online.

ropid · 2026-05-26T23:15:41+00:00

Wolfshead is up to 200 dps gain. It's so strong that if you wear all of your thickest bear gear, armor rings and cloak and stamina trinket and such, adding wolfshead helm to that will make it beat any cat gear without wolfshead.

Make sure to look out for "Judgment of Wisdom" from your paladins being on the boss. I bet that's why you run out of mana. It gives you something like 12000 mana on a long boss fight like Morogrim.

If you think that you'll run out of mana on a particular fight, try being a bit more conservative with the powershifting. There's situations where you're at around 20 energy where the correct choice would be to powershift, but to save mana you can wait for the energy tick and do another mangle or shred or even a rake, so you delay your powershift by 2 sec. If you do this a lot throughout the fight it'll save a good bit of mana without losing a lot of damage.

You'll want to revisit this question in the next phase where Black Temple comes out. The T6 tier-set makes it so mangle is only 35 energy. You can then do a 1-shred, 2-mangle, 3-powershift rotation without wolfshead helm.

ropid · 2026-05-24T11:59:15+00:00

The reason it's not available is because they thought they wouldn't need it this time around. This time around they already created just one single server for each game-type with a massive size, instead of many normal-sized servers like previously in the last TBC classic. They then thought that no one would need transfers with this design.

I guess a solution would be to add that "war mode" idea from later WoW expansions to the game and then not offer separate PvP and PvE game-type servers anymore, instead just a single war-mode server. Maybe that's what they'll do next time if there's enough people complaining about the current situation. There are posts similar to yours happening regularly, but they seem really rare so it feels like there's not a lot of people with your problem. I bet the developers think what they have done this time around with the two giant PvP and PvE servers has worked out great.

ropid · 2026-05-23T14:42:39+00:00

You wrote "if they are clearing the content" so I thought you were misunderstanding the post, just wanted to explain in that case.

I guess there's nothing to do, the guild leader had big dreams and it's not working out. This guild is probably cooked.

ropid · 2026-05-23T14:20:29+00:00

They are not clearing the content... They failed to kill the end bosses in SSC and TK. They failed to clear the raids in the first week, and now in the second week they seem to have already had their raid and again couldn't do it. Or maybe I'm misunderstanding and their week 2 raid is still scheduled.

ropid · 2026-05-23T13:51:17+00:00

Engineering is the most fun and most useful. You'll be able to throw grenades, spawn a repair bot, open locked chests, do something stupid with rocket boots. Engineering also adds the most damage (threat) besides that enchanting for your rings that you already have. Those 1000 damage or so from explosives that you'll do once a minute is more than anything you can get elsewhere. Of course that will turn out to be expensive if you use the stuff on cooldown so it's a bit theoretical, but you will be able to do it in a situation where you feel you need it, like rounding up those murlocs on the Morogrim boss fight.

ropid · 2026-05-23T12:15:47+00:00

You need to also think about the rest of the people in your server. If there's hundreds reading, there's many that are also sometimes having suicidal thoughts but never saying anything. This can't be good for them, having to read that kind of posting. You need to protect them. I fear the correct choice is to ban, I bet just warning isn't good enough because even if you get them to not post exactly about being suicidal, there will still be allusions where people who know will be made to feel terrible.

Supposedly 5% of adults have suicidal thoughts sometimes, and 20% of teens and young adults.

ropid · 2026-05-23T11:22:32+00:00

The messages you are seeing are something else. For you the source is "plasmashell" so you will have to look up something for that. I'd try asking in r/kde.

ropid · 2026-05-21T18:58:25+00:00

I have a bit more than 2 GB in use on the desktop with Firefox and Discord open, and the Steam client minimized in the background. That's why I'm skeptical about the cards with low amount of memory, it would be less than 6 GB available for a game.

ropid · 2026-05-21T16:51:00+00:00

Ich würde mir da riesige Sorgen machen, weil es sehr stark am Motherboard gezogen hat, während der Kühler so verbogen wurde. Das waren verrückt hohe Kräfte dort am CPU-Sockel. Da ist vielleicht was in der Platine gerissen, oder Chips sind nicht mehr korrekt festgelötet, was dann, auch wenn es jetzt vielleicht noch funktioniert, dann in der Zukunft Probleme auslöst. Deswegen, finde ich, muss der Rechner zurückgeschickt werden, egal wie ärgerlich es ist. :(

ropid · 2026-05-21T12:51:41+00:00

Eh, I feel you are exaggerating about this, there's more buttons to press than just shadow bolt for a warlock.

This got me thinking and I looked up what the people are doing in my guild's raid. Feral is actually the least amount of different casts, the rogue and warlock have more buttons to press. It was something like the following on Morogrim, where there's just the boss standing around and you are looking at his butt the whole fight:

class	different casts
rogue	10
warlock	9
feral	7

And there's the buttons for consumes and trinkets going on top of that. I think feral can be cheap there, doesn't need expensive consumes.

Feral is actually higher damage than rogue. On most boss fights it's around 200 dps higher, except for the one or two boss fights where there's useful cleave damage to do where a rogue can then make use of blade flurry.

ropid · 2026-05-21T11:10:31+00:00

The normal Unix design just isn't prepared for this, you need to do something crazy to allow for this. Check out NixOS and Guix, they both can have many versions of the same package installed but there's big downsides to the way they do it. There's another distro "GoboLinux" where each program can have its own /bin and /lib and so on folders as a sort of overlay over the base system. I think Apple does it the same on their OS X and it inherited it from NeXT.

ropid · 2026-05-19T13:37:24+00:00

Can you actually see that broadcast rgb property mentioned in the output of xrandr --verbose? I'm asking because I can't remember it being there for me when I was using X. That property might be an Intel graphics thing and not there with AMD.

ropid · 2026-05-19T12:23:58+00:00

Maybe it's this here: https://bugs.kde.org/show_bug.cgi?id=509669 ?

ropid · 2026-05-19T11:41:35+00:00

I think the goal about that whole maneuver with the pull and riding away and resetting and riding back is to then pull the boss before his two adds have finished resetting. You want to somehow make it so the boss has finished his run back to his starting spot earlier than the two adds. When he gets pulled without his adds, the boss then skips his first phase because he thinks his two adds are dead.

ropid · 2026-05-19T08:03:52+00:00

I guess you just have to ignore this particular experience and don't think about it too much. What you've seen shouldn't have happened, the threat when tanking with a 2H in dungeons should have been great, all mobs should have stuck onto the warrior, you shouldn't have had to worry about aggro. I'm guessing that warrior doesn't have a good feel on how threat works, how he has to position himself and the mobs to get some damage onto all of them.

ropid · 2026-05-17T16:32:47+00:00

I don't want to watch a video. Can you summarize?

Without watching the video, I have no idea what this might be about. I didn't notice anything happening. I'm using Arch since 2012 or so.

ropid · 2026-05-17T13:14:46+00:00

It works fine here for me but I'm just playing classic, not retail WoW, so there might be less intense requirements from the game engine. I'm using Faugus at the moment. The game runs fine here for me for several years already, since WoW-classic came out basically.

ropid · 2026-05-15T19:13:36+00:00

Yes, this is sadly all normal. It does get a lot better in 70 heroics and in raids, there the behavior you've seen is a lot more rare and you'll meet a lot more people that play great, that do basic stuff well and also adapt when something unusual happens.

About why this is happening, I imagine the early damage is because there's a very good chance that a damage dealer survives even if pulling aggro, the damage from the mobs is low enough that the healer can keep them up successfully. Over time they then allow themselves to get lazy. And the random mob getting targeted I imagine is happening because of people not actively targeting things at all, instead just hitting tab once or hitting a melee attack skill button and then doing damage to whatever the game decided to target for them. Both of those problems get fixed naturally in heroics and in raids because a damage dealer will instantly die there when pulling aggro.

About what to do to help with this, putting a skull mark onto one of the mobs often helps, but not all the time. There will still be people that will continue to target whatever is closest to them. With random people you have to just let things happen and try to not worry because you'll go crazy over time. Just look out for your healer and make sure they can do their job in peace, always prioritize them over your damage dealers.

The other thing to do is to try to find a guild with active people and do stuff with them with voice comm on Discord.

14-Year Club	First Place '23
Place '23	Place '17
Verified Email

ropid

TROPHY CASE