Repository navigation
GPU stuck throttled at 300MHz clock speed - cannot load accurate clock tables or overclock settings #29
Description
I'm running linux mint t2 install on a mac pro tower, 2019, 7,1, with an AMD W5700x.
I found the fan patch, now fans work well. CPU utilization is great. My GPU is fucked and I can't use it. Checking utilization while running games, gpu is constantly at 99% no matter what is on screen, and CPU is sitting comfortably.
The available clock speed table is always:
0: 300Mhz
1: 300Mhz
I tried downloading the physical bios file of the GPU. I tried adding a grub to inject the BIOS to the OS on boot.
The GPU is locked down and won't let me use it.
Googling/searching/asking AI hasn't found threads on how to fix this issue. Does anyone know what to do?
Activity
[-]GPU stuck throtted at 300MHz clock speed[/-][+]GPU stuck throttled at 3000MHz clock speed[/+][-]GPU stuck throttled at 3000MHz clock speed[/-][+]GPU stuck throttled at 3000MHz clock speed - cannot load accurate clock tables or overclock settings[/+][-]GPU stuck throttled at 3000MHz clock speed - cannot load accurate clock tables or overclock settings[/-][+]GPU stuck throttled at 300MHz clock speed - cannot load accurate clock tables or overclock settings[/+]Dustin-rpg commentedon Sep 25, 2026
I have a solution.
BASICS OF ISSUE:
It seems Navi10 GPUs don't store much useful info in their firmware, and always report and/or choose the mare minimum specs. Mac OS always writes specific settings directly to the GPU via the driver to get it to run at its actual capabilities.
Also, current amdgpu drivers do not have overdrive options for Navi10 GPUs.
FIX:
USE AT YOUR OWN RISK. I am not a programmer. I only know how to install linux and run basic terminal commands. So I argued with several AIs over several days, providing files and documentation, and running tests, until claude made a script that fixed my issue.
Attached is the script which you need to build and install. It will modify your drivers and create new GPU commands for your console. The readme and the script are both created by Claude, so I cannot take credit OR blame.
GTHR-README-v2.0.md
gthr-kit.sh
Also, for anyone else gaming on a t2 mac with linux, I found the following settings very helpful"
Permanently set CPU governer to performance with config file:
echo 'w /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor - - - - performance' | sudo tee /etc/tmpfiles.d/cpu-governor.conf
sudo systemd-tmpfiles --create /etc/tmpfiles.d/cpu-governor.conf
Permanently set energy setting to performance with config file:
echo 'w /sys/devices/system/cpu/cpu*/cpufreq/energy_performance_preference - - - - performance' | sudo tee /etc/tmpfiles.d/cpu-epp.conf
sudo systemd-tmpfiles --create /etc/tmpfiles.d/cpu-epp.conf
Permanently disable split_lock with config file:
echo 'kernel.split_lock_mitigate=0' | sudo tee /etc/sysctl.d/99-gaming.conf
sudo sysctl --system
Install Proton GE (instead of experimental or a standard steam version)
Then write steam launch settings to juice your CPU and cover your bases. For this, you need to figure out your CPU core layout, whichever are physical cores and with are virtual. On mine, sequential cores from 0-23 are all physical. I dedicate 10 cores to the game, have wine report those 10 cores to the game, and a handful of other boot commands that may or maynot help. Here is what I run:
WINE_CPU_TOPOLOGY=10:2,3,4,5,6,7,8,9,10,11 PROTON_PRIORITY_HIGH=1 AMD_PRIORITY=1 PROTON_USE_NTSYNC=1 PROTON_USE_XALIA=0 gamemoderun mangohud taskset -c 2-11 %command%
NTSYNC was a huge help for me, as was the WINE_CPU_TOPOLOGY command. bBe careful about disabling XALIA cuz it might break your steam inputs.