Thanks @Xavier_Jiang, I’m familiar with some of the Windows utilities but was interested in similar tools for Linux. Greatly appreciated.
Yep stays at 36-38W with a 130W Dell charger. They likely changed it to the 180W.
Note that s-tui is not a benchmark, it merely tasks the CPU with as many workloads as possible (you can choose type). As opposed to Cinebench, which is a benchmark
Update: the kb acted strange for awhile then stopped working completely, after removing it, and inspecting, turns out a ribbon cable shorted, caught fire, and burned a hole though the ribbon cable, also connector for ribbon missing a pin entirely from burning damage, and other pins burnt from shorts as well…![]()
![]()
![]()
![]()
this is solve with BIOS 4.03:
Hi, i’ve read the entire topic, maybe my issue is related? I am getting limitations also with 4.03 BIOS.
Did you use s-tui to monitor the CPU power while performing those steps? We attempted to replicate your process but were unable to trigger a PROCHOT event. Additionally, after running glxgears, the dGPU did not enter sleep mode as expected. Could you also clarify which OS power profile you were using during your testing? Balanced, Performance?
Yes I used s-tui. But once the dGPU is woken up while s-tui is running, s-tui will hold it awake so you have to close it to let is sleep.
I’m assuming you have s-tui open while trying this. Close s-tui and the dGPU will sleep again.
The revised “steps to reproduce” I put in the issue over here are a little better. Just keep in mind s-tui will hold the dGPU awake.
I try to keep it on performance for any of the tests. U usually have it set to performance from the KDE power management. Checking from console also shows performance:
# powerprofilesctl
* performance:
CpuDriver: amd_pstate
PlatformDriver: platform_profile
Degraded: no
balanced:
CpuDriver: amd_pstate
PlatformDriver: platform_profile
power-saver:
CpuDriver: amd_pstate
PlatformDriver: platform_profile
I’m not sure how this is possible. Pretty much any unplugging/plugging of power seems to trigger it and then it stays active until a sleep/wake cycle. I have the Ryzen 9 7940HS just in case that could possibly matter in tracking down this issue.