-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error if Power Limit Isn't Set #350
Comments
I have exact same error, and similar usecase. @notstarboard like I said, I have exact same usecase, I just want to undervolt, and I can confirm, the undervolting part works despite of the errors (I am sure it works, because when I set some absurdly high values like -200mV and I apply it, my laptop instantly freezes). So if you still can't undervolt with that tool, the problem should be somewhere else. |
Am third person. I don't need to undervolt (can't, not supported) but need to set cTDP state because it is limited to 1200mhz if you turn turbo off. The solution was to just copy those values from corefreq and set them stock. Now it runs. You can leave the trip temperature commented out. Without values service never ran. Check systemctl status throttled |
I've been having no success using georgewhewell/undervolt to undervolt my laptop and I stumbled upon this project as a possible alternative. I have no interest in anything other than undervolting, so I put together a relatively sparse config file aimed at doing just that:
This configuration causes an exception to be thrown by the service:
The issue seems to be that regs[power_source]['MSR_PKG_POWER_LIMIT'] is never set on line 625 because none of PL1_Tdp_W, PL1_Duration_s, PL2_Tdp_W, and PL2_Duration_s are set in my config file. power_thread is always called in main(), and then within power_thread it tries to use regs[power_source]['MSR_PKG_POWER_LIMIT'], which has not been set.
A conditional should probably be added to avoid this. I don't think power_thread needs to be called at all unless the user attempts to change related settings in the config file.
The text was updated successfully, but these errors were encountered: