Ryzen Linux users. My 1700 won't go faster than 3000 MHz

H

hondaman

The OG Hondaman
Joined
Jul 31, 2004
Messages
79
Currently using Ubuntu Mate 17.04. With 100% load using "stress --16" none of my cores ever go faster than 3000 MHz. In Windows 10 it works fine.

Has anyone else observed this behavior and how did you fix it?

Asrock Taichi with 2.0 bios, Ryzen 1700, EVGA ram @ 3200 and Corsair 115i AIO
 
Maybe you need a more recent kernel. I know that 4.10 has fixes specifically for ryzen.
 
Maybe disabling the cpufreq stuff (power management) will help, or at least point you somewhere (like pstate overclocking in the bios).
 
I'll check mine tomorrow when I get home, I didn't even think to look as I haven't had much time to use it. I had a hell of a time getting the 4.10 (non-rc) kernel working with my Nvidia card and haven't had a chance to do anything else.
 
I have updated to the latest mainline kernel, 4.11 and disabled cool and quiet. It still won't go faster than 3000 MHz
 
hondaman said:
Currently using Ubuntu Mate 17.04. With 100% load using "stress --16" none of my cores ever go faster than 3000 MHz. In Windows 10 it works fine.

Has anyone else observed this behavior and how did you fix it?

Asrock Taichi with 2.0 bios, Ryzen 1700, EVGA ram @ 3200 and Corsair 115i AIO
Click to expand...

I got my Ryzen running at 3750 stock voltage in Gentoo Linux with the gcc-6 compiler using -march=znver1 no problems. I am currently moving voltage up to see where my wall is.
 
Reporting of actual processor speed is incorrect when certain features are enabled in bios (think power management?), when overclocking via bclk (iirc). Same happens on Windows if you open task manager's performance tab.

If your performance in benchmarks improved then the overclock held fine, it's just not being detected properly.
 
Nobu said:
Reporting of actual processor speed is incorrect when certain features are enabled in bios (think power management?), when overclocking via bclk (iirc). Same happens on Windows if you open task manager's performance tab.

If your performance in benchmarks improved then the overclock held fine, it's just not being detected properly.
Click to expand...
I'm not overclocking. I'm using (mostly) stock bios settings. Only things I've changed is turning on stuff like IOMMU, virtualization and such. All the power management and clock settings are stock.
 
hondaman said:
I'm not overclocking. I'm using (mostly) stock bios settings. Only things I've changed is turning on stuff like IOMMU, virtualization and such. All the power management and clock settings are stock.
Click to expand...
I realized that after posting, thus my second post (above). If you load all cores on your 1700 you'll only get 3.0GHz, or 3.5GHz if you have a 1700x. You'll need to oc if you want all cores at 3.7GHz under full load.
 
Nobu said:
I realized that after posting, thus my second post (above). If you load all cores on your 1700 you'll only get 3.0GHz, or 3.5GHz if you have a 1700x. You'll need to oc if you want all cores at 3.7GHz under full load.
Click to expand...
Why then do I get burst speed to 3700 under windows 10, but not in linux?
 
hondaman said:
On any core. One core. As observed in cpu-z
Click to expand...
With something running on all cores? Sounds like it's working in windows, yeah.

How are you observing the core frequency in Ubuntu? "cat /proc/cpuinfo | grep MHz" or similar?
 
You must log in or register to reply here.
Back
Top