-
Notifications
You must be signed in to change notification settings - Fork 74
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
Suspend broken on Gazelle 16 because of Nvidia GPU #358
Comments
Here are the relevant errors (oryx6 on my side):
|
There is also a related known issue on the Nvidia side: https://download.nvidia.com/XFree86/Linux-x86_64/470.86/README/powermanagement.html#KnownIssuesAndWf438e |
Just want to say I have the same issue, I think quite a few people do, thanks for the workaround its not perfect but laptop is no longer frozen on resume |
Okay, here's the actual correct fix. Keep the gpu memory (
Instead, enable these NVIDIA services which are disabled by default. I rebooted and it's finally working as expected with no side effects.
As noted in the Arch wiki and NVIDIA's documentation, this saves gpu memory to a
If someone can turn this into a pull request, go ahead. Maybe the |
Distribution (run
cat /etc/os-release
): Arch Linux (5.19.4 / Nvidia driver 515.65.01)Related Application and/or Package Version (run
apt policy $PACKAGE NAME
): Related to usingxfce4-session-logout --suspend
with the Whisker Menu.Issue/Bug Description: The system wakes up immediately after suspending.
journalctl -p 3 -b
reported logs that looked like these.Steps to reproduce (if you know): You should able to run the command above to trigger it.
Expected behavior: The machine doesn't immediately wake up after screen tears.
Other Notes: I ended up finding my fix here.
Known workaround:
I went into
/etc/modprobe.d/system76-power.conf
and modified this setting to be off instead of on.Proposed fix:
I think something in
src/graphics.rs
needs to be updated, possibly the S3 exception where this setting is being applied. That's the extent of the debugging I'm ready to put into this though, I hope it helps someone else.The text was updated successfully, but these errors were encountered: