After 1.4.0 frequencies don't go beyond 3499 #123
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Please confirm
Extra details
pt_oc.jsonfilelimits_cache.jsonfileExpected Behaviour
with previous versions my frequencies clocked up to 3850 MHz when set to 4000 maximum.
Actual Behaviour
I updated to 1.4.0 and frequencies don't go beyond 3499 MHz even if I manually set them higher
Steps To Reproduce
Anything else?
worked fine on 1.3.1, just updated to 1.4.0 and no longer works
Version
1.4.0
Platform
SteamDeck
OS
SteamOS 3 (Stable)
I reverted back to 1.3.2 and didn't work either... out of options now maybe steam 3.4.10 messed something up
worth noting that GPU frequencies work beyond 1600mhz with the edited pt_oc.json
CPU frequencies are the problem
I was under the impression that setting GPU and CPU values above stock never worked properly in PowerTools.
It never clocking above stock is likely related to the fix for #107 though. PRs are welcome if anyone is willing to OC their Deck to fix the bug (and test).
It does for GPU right now :)
I'm on an OC deck but I don't know how to code :( if you update PowerTools I can test a new version to see if CPU clocks can go higher than stock again.
i have same problems, even without setting any speeds in powertools not seeing my overclocked speeds. 3.5Ghz must be set as max somewhere. Im trying this next as a fix:
https://github.com/badly-drawn-wizards/vangogh_oc_fix/tree/master
will report back.
and btw, after uninstalling powertools now I see speeds above 3.5Ghz again. On Steam OS 3.4.10.
Nope doesnt help. Frequencies still stuck at 3.5Ghz even when using said kernel module to change values in the APU driver. Also noticed 1.4.0 doesnt use my pt_oc.json at all. Not even seeing my changes Max Frequeny in the UI (slider max 3500) downgrading to 1.3.2 and my sliders reflect pt_oc.json settings.
I solved the issue with pt_oc.json not working on 1.4.0:
I believe is produced because the new pt_oc.json @ line 7 reads
"extra_readouts": falseand old versions of pt_oc.json don't have that line, the fix is to download a new pt_oc.json again from this repo and manually edit the values again. It will allow the slider to go over 3500 again but changes above 3500 won't work as it is bugged currently.
I don't know what I did differently this time but now frequencies go up to 3900 MHz 😁
I changed between different PowerTools versions, deleted extra .json files where pt_oc.json was located, undid my undervolt settings on BIOS, booted to Windows 10, updated Mesa from Discover and now clocks go beyond 3499 MHz.
Currently on version 1.4.0 with the new modified pt_oc.json.
Leaving this here if anyone encounters the same problem.
I was playing around with PowerTools settings, pressed "Defaults" and now the bug is back.
I'm on the exact same settings as when clocks reached 3900 MHz, but clocks refuse to go above 3499 MHz the only change I did was pressing "Defaults" and then re-applied previous 3900 MHz settings.
Didn't work, now I'm stuck with the 3499 MHz bug again.
okay thx for sharing. Downloading a new pt_oc.json now and see if I get ut working with the oc fix kernel module to change clocks past 3500Mhz.
I got it working after using new pt_oc.json from 1.4.0 repo and changing my max values. Could set my max CPU to 3700 or lower and have seen the clock speeds in Gamescope. GPU to 1700 worked as well but as soon as I go above 1600 GPU my CPU clocks goes down massively. Only tried it with the OC fix kernel module so far. Guess I need more TDP to get both oc'ed at once. But temps are really bad, 85 at full FAN speed at 3700Mhz CPU and 1600Mhz GPU.
@tweakbsd I tried the kernel OC fix you linked, now my clocks go over 3499 MHz again and they don't revert even if I press [Defaults]
The steps to install it on SteamOS 3.4.10 are:
sudo steamos-readonly disableand type your root passwordsudo pacman -S base-develand confirm withy+ Entermake buildmake buildagainsudo make installRun it in the current boot with
sudo modprobe vangogh_oc_fix cpu_default_soft_max_freq=<freq in Mhz>In my case for a 4000MHz OC
sudo modprobe vangogh_oc_fix cpu_default_soft_max_freq=4000Run it every boot with
sudo make install-conf MODULE_FREQ=<freq in Mhz>In my case for a 4000MHz OC
sudo make install-conf MODULE_FREQ=4000also you will need to runsudo modprobe vangogh_oc_fixto run for the current bootsudo steamos-readonly enableand you are done, no need to mess with it until a new SteamOS update.Now my clocks go up to 3900 MHz and temps don't go over 80c thanks to a ptm7950 repaste
@PDI great write up. Exactly what I did too. I guess need need thermal paste or that pad you're using myself.
When I type "Make build", it says "command not found".
I know absolutely nothing about Linux. All I can do is follow instructions.
@Falkentyne try these commands:
and
and if
make buildstill doesn't work try withthat should fix it, and if it still doesn't you should try googling your error
Hi, I tried your commands, (after setting steamos readonly disable) but there were a bunch of errors.
It basically said "var/cache/pacman/whatever is corrupted (invalid or corrupted package (PGP signature)., "Do you want to delete it?", for literally every line (after sudo pacman -Syu)
This was after the proceed with installation prompt(y/n).
The sudo pacman -S make obviously failed also (since the first command failed).
In the command sudo pacman -Sy base-devel, after "proceeding with installation"
it said var/cache/pacman/pkg/m4-1.4.19-3-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature),
same for "autoconf" and automake, bison, etc etc ....(many many other lines after that).
@Falkentyne try running "sudo pacman-key --init"
then run "sudo pacman-key --populate archlinux holo"
then try again
This doesn't seem to do anything for me. Still stuck at 3500.
Anyone got this to work on Steamos 3.5?followed the steps but didnt work.
@toppit for steamos 3.5 you need to follow different steps, check https://github.com/badly-drawn-wizards/vangogh_oc_fix/#how-to-add-support-specific-kernels you need to manually add support for your kernel if your kernel starts with
6.*.*To check your kernel version type
uname -rSorry I've let the vangogh_oc_fix bitrot, as I realized I wasn't too keen on maintaining it. I've made an upstream issue which seems to have some traction going, so there may be hope of my module becoming obsolete.
@badly-drawn-wizards Thanks for your fix, I'm using it on SteamOS 3.4.11 and works wonders 💯
I don't see Valve themselves fixing OC problems anytime soon so I'll rely on your module until it stops working 🫡
Hey guys. I finnaly jumped ship (Steam OS 3.4.11, BIOS 110) and went to 3.5.7 and BIOS 116. Everything still working fine if you can build the vangogh_oc_fix kernel module.
https://github.com/badly-drawn-wizards/vangogh_oc_fix/#how-to-add-support-specific-kernels
I had lot of trouble getting it to build on 6.1.52-valve9, even though I'm a UNIX guy coming from FreeBSD and Darwin. But if you get through that step overclocking and PowerTools still work nicely together on that System for me. Let's hope a way to get OC to work in latest BIOS 118 and 119 will be found soon. But I think that still won't solve the problem with the hardcoded 3500Mhz in Valve's VanGogh's kernel code.
There's also https://github.com/ryanrudolfoba/SteamDeck-vangogh_oc_fix-installer