You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is the issue: For some reason, I cannot get throttled to run at the full tdp of 44 watts. Monitoring with throttled.py --monitor shows consistent power levels that do not exceed 20 watts under any circumstances. I have tlp installed, the Intel-rapl driver is in active mode and have tried many many combinations of powersave/performance/balance_performance etc. Even disabling tlp completely. Also, I have cross-checked readings with powerstat -Rc.
In throttled.conf settings, I have tried both HWP True and False; I have tried different undervolting and also no undervolting. I tred disabling BDPROCHOT or leaving it commented out. Always the machine never goes more than 20W.
Interesting thing is that throttled's --monitor and --debug both show no things are wrong. When I manually check the machine register with rdmsr, everything is as it should. While running stress and s-tui, I notice that temperature never reaches 80C. It always goes to 77, 78 and stays there. The .conf file sets the max temperature at 95 degrees. Strangely, the frequency does not drop during the stress tests. It is at 3.4GHz the entire test. I have run it for 1 minute, and also for 3 and 4 minutes. Same thing--never reaches 80C and power never goes above 20W.
Also, I used throttled happily for 2 years in Ubuntu 18.04 and Debian 11, no issues whatsoever! My tdp level reached up to 44W every time it was tested, and also the cpu temperature got as high as low 90's. Edit: forgot to say that I tested this with kernel 5.10.191 as well with same results.
I am at a loss; does anybody know what may be wrong or have any suggestion? Any insight would be appreciated; I really want this to work.
The text was updated successfully, but these errors were encountered:
Hi, and first, thank you very much for this project!
System: Thinkpad T480 (US version, integrated Intel graphics)
CPU: core i5 8250U
Thunderbolt 3: 1 port
Bios revision: 1.49
Embedded Controller Version: 1.22
Thunderbolt 3 Firmware: 23.00
Operating System: Debian 12 Bookworm
Kernel version: 6.1.0-12-amd64 (6.1.52-1)
Desktop: Gnome 43
No thermald installed; removed the native gnome applet that allowed changing governor
Here is the issue: For some reason, I cannot get throttled to run at the full tdp of 44 watts. Monitoring with throttled.py --monitor shows consistent power levels that do not exceed 20 watts under any circumstances. I have tlp installed, the Intel-rapl driver is in active mode and have tried many many combinations of powersave/performance/balance_performance etc. Even disabling tlp completely. Also, I have cross-checked readings with powerstat -Rc.
In throttled.conf settings, I have tried both HWP True and False; I have tried different undervolting and also no undervolting. I tred disabling BDPROCHOT or leaving it commented out. Always the machine never goes more than 20W.
Interesting thing is that throttled's --monitor and --debug both show no things are wrong. When I manually check the machine register with rdmsr, everything is as it should. While running stress and s-tui, I notice that temperature never reaches 80C. It always goes to 77, 78 and stays there. The .conf file sets the max temperature at 95 degrees. Strangely, the frequency does not drop during the stress tests. It is at 3.4GHz the entire test. I have run it for 1 minute, and also for 3 and 4 minutes. Same thing--never reaches 80C and power never goes above 20W.
Also, I used throttled happily for 2 years in Ubuntu 18.04 and Debian 11, no issues whatsoever! My tdp level reached up to 44W every time it was tested, and also the cpu temperature got as high as low 90's. Edit: forgot to say that I tested this with kernel 5.10.191 as well with same results.
I am at a loss; does anybody know what may be wrong or have any suggestion? Any insight would be appreciated; I really want this to work.
The text was updated successfully, but these errors were encountered: