-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
Minimum GPU and VRAM clock adjustments not working #385
Comments
Setting minimum clocks can indeed be iffy, though I have not seen this happen before with GPU clock, only with VRAM. A few more questions:
|
I believe the GUI changes both values when you enable the advanced configuration, doesn't it? As the VRAM slider will also be available.
The values doesn't seem to be applied anywhere, it just stays in the default minimum.
Yes, but they are displayed incorrectly as in the screenshot.
Here it is: LACT-sysfs-snapshot-20241016-050352.tar.gz
I will try and report you back. |
The problem persists with |
I've just tested this on a Sapphire 6900 XT and unfortunately I wasn't able to reproduce any of the issues you're having. Editing both the GPU and VRAM min clock worked correctly via GUI, config file or manually via /sys. |
i don't know if its the same issue but if i try to limit the clock speeds on my 7900xt it just gets ignored if try to set max clock to 1800mhz then the "do you want to save current settings" windows comes up but if i press yes it jumps back up to 2013mhz same for vram just all the way up to 2500mhz also it somehow applied after a bit of trying but that didn't prevent the card from boosting to 2016mhz |
Checklist
Bug description
I encountered two issues related to minimum GPU and VRAM clock adjustments while using LACT:
When changing either the minimum GPU clock or the VRAM clock through the LACT GUI, the GPU experiences severe instability. The GPU fan immediately ramps up to maximum speed. Video output gets glitchy, exactly as described in Feature request: Minimum GPU clock #129.
When I attempt to set a new minimum GPU or VRAM clock limit by manually editing the configuration file, the daemon appears to ignore the new limit. After restarting the daemon, the configured limits are not applied, and the clocks remain unchanged.
Debug Snapshot: LACT-sysfs-snapshot-20241015-234520.tar.gz
System info
The text was updated successfully, but these errors were encountered: