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
After boot, CPU frequency scaling initially works as expected, with idle frequency around 1GHz and idle temperature at 50C. As soon as I close the lid, wait for sleep and reopen, the CPU frequency gets stuck at max (avg core freq. ~3.3GHz) at idle without any load. Idle temperature stays around 70C. Frequency only comes down under high CPU load for throttling purposes. Already tried replacing CPUFriendDataProvider.kext and disabling CPUFriend.kext altogether. CPU frequency scaling does seem to change accordingly, but nevertheless it always gets stuck at max after waking from the first sleep.
Additional but perhaps irrelevant observation is that Bluetooth does not work sometimes after wake from sleep, but if I close the lid and reopen, the problem seems to go away.
Hardware:
Thinkpad T480
Intel i7 8550U
Integrated Intel 620 Graphics
Non touch FHD screen
32GB RAM
Software
Mac OS Ventura
valnoxy / t480-oc release 1.3.0
The text was updated successfully, but these errors were encountered:
After boot, CPU frequency scaling initially works as expected, with idle frequency around 1GHz and idle temperature at 50C. As soon as I close the lid, wait for sleep and reopen, the CPU frequency gets stuck at max (avg core freq. ~3.3GHz) at idle without any load. Idle temperature stays around 70C. Frequency only comes down under high CPU load for throttling purposes. Already tried replacing CPUFriendDataProvider.kext and disabling CPUFriend.kext altogether. CPU frequency scaling does seem to change accordingly, but nevertheless it always gets stuck at max after waking from the first sleep.
Additional but perhaps irrelevant observation is that Bluetooth does not work sometimes after wake from sleep, but if I close the lid and reopen, the problem seems to go away.
Hardware:
Software
The text was updated successfully, but these errors were encountered: