You are not logged in.
Pages: 1
i have a arch on a Dell Precision 7530 which is stuck at 800Mhz when doing a fresh boot. when i open a shell and do a watch grep \"cpu MHz\" /proc/cpuinfo i see every cpu at 800Mhz and not more. But when i do a suspend and a resume, all breaks are released!
my settings do not change. after a fresh boot and after the resume the settings are:
❯ uname -a
Linux usc-precision 5.9.12-arch1-1 #1 SMP PREEMPT Wed, 02 Dec 2020 16:14:56 +0000 x86_64 GNU/Linux
❯ LANG=en cpupower frequency-info
analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: Cannot determine or is not supported.
hardware limits: 800 MHz - 4.80 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 800 MHz and 4.80 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 830 MHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yesbut as a said: doing a fresh boot, the upper limit (4.8GHz) does not work, everything stucks at 800Mhz although the output of "cpupower" looks like it should work.
so my workaround after a fresh boot is not to login but to do a suspend from the login screen. then resume and then login.
i'd like to know how to release the breaks without resuming. if it is a BIOS setting: why does this change after a resume?
i've also posted this problem at Reddit some time ago but no one had a solution.
a few days ago there was a new dell firmware release and i hoped it would be better but ... no.
it would be really great to know what the problem is. and how to solve it :-). or at least have a better workaround like a one-shot command which can be entered to "release the breaks". the only thing which works is to suspend/resume which is a little annoying.
Offline
Dells seem to be weirdly susceptible to this issue and the only fix I've seen floating around is to completely cut the power, including disconnecting the battery for a few seconds (... and updating your BIOS/UEFI)
Last edited by V1del (2020-12-10 16:18:13)
Online
for anyone reading this posting: the problem is fixed on my system since the kernel
❯ uname -a
Linux usc-precision 5.9.14-arch1-1 #1 SMP PREEMPT Sat, 12 Dec 2020 14:37:12 +0000 x86_64 GNU/Linuxwas released. i did not have to do anything with the battery
Offline
Pages: 1