Skip to content
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

Core/Mem Freq not restored after suspend or written to Json by GUI #41

Closed
Big-FG opened this issue Aug 11, 2021 · 5 comments
Closed

Core/Mem Freq not restored after suspend or written to Json by GUI #41

Big-FG opened this issue Aug 11, 2021 · 5 comments
Labels
bug Something isn't working

Comments

@Big-FG
Copy link

Big-FG commented Aug 11, 2021

Ive noticed that on my 5700xt the values for core/mem freq arent restored by the daemon upon returning from system suspend state. The power limit and fan curves work as desired but not the clocks.

The core/mem freq also arent written to the json file by the gui which im not sure if thats intentional. If you manually edit the json its fine.

@ilya-zlobintsev ilya-zlobintsev added the bug Something isn't working label Aug 12, 2021
@Big-FG
Copy link
Author

Big-FG commented Aug 17, 2021

I was looking at other amdgpu related tools and noticed in amdgpu-clocks there is a section about restarting upon resume after suspend. not sure if this helps

https://github.com/sibradzic/amdgpu-clocks

@Big-FG
Copy link
Author

Big-FG commented Aug 17, 2021

Ill create a service and see if this works for resume on suspend

@Big-FG
Copy link
Author

Big-FG commented Aug 17, 2021

I created a lactd-resume.service and enabled it
this seems to resolve the reapplying on resume from suspend and it also includes hibernate and sleep targets. Needs more testing but it restarts lactd upon resume

[Unit]
Description=AMDGPU Control Daemon Resume
After=hibernate.target
After=hybrid-sleep.target
After=suspend.target
After=suspend-then-hibernate.target

[Service]
ExecStart=/bin/systemctl --no-block restart lactd.service

[Install]
WantedBy=graphical.target
WantedBy=hibernate.target
WantedBy=hybrid-sleep.target
WantedBy=suspend.target
WantedBy=suspend-then-hibernate.target

@ilya-zlobintsev
Copy link
Owner

Hmm, this seems like a bit of a hack to call systemctl restart from another systemd unit, but I'll look into it.

@ilya-zlobintsev
Copy link
Owner

This is now fixed, LACT will reapply all settings on suspend/resume events received from dbus.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants