Path: ...!Xl.tags.giganews.com!local-1.nntp.ord.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Sat, 19 Oct 2024 20:55:43 +0000
Subject: Re: Fixed the suspend issue...
From: mummycullen@gmail-dot-com.no-spam.invalid (MummyChunk)
Newsgroups: comp.os.linux.advocacy
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit
User-Agent: newsSync 676492850
References: <AhbQO.87662$afc4.6755@fx42.iad>
Message-ID: <7d2dnYKf7bJSgYn6nZ2dnZfqnPudnZ2d@giganews.com>
Date: Sat, 19 Oct 2024 20:55:43 +0000
Lines: 49
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-UpdoePepu62Sx6ANJ0R8P5kRe5Qg8pPupdj7DCbTwEcDXyydN2vHToxB/i5xO9YlMCWcYKrtsv2yzuk!D2bOcikicjSuTdJZV6jVSg0AG5yDe+t5yjVeClsoNIzuifX/7V2ottSlwOV5Tiu/5oQq3PBNYC09!Pw==
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
Bytes: 2777
X-Original-Lines: 1


 > CrudeSausage wrote:
 > .... it turns out that using the NVIDIA services is indeed the
wrong 
 > thing to do. Stopping/disabling the three NVIDIA services and
removing 
 > /lib/systemd/system-sleep/nvidia did the trick.
 > 
 > I'm crossing fingers that it continues to work in the long run.
 > 
 > -- 
 > CrudeSausage
 > Paleoconservative, Catholic, Christ is king.

Disabling the
NVIDIA services and removing the /lib/systemd/system-sleep/nvidia file
is a solid fix for the suspend issue. However, for those who might not
be familiar, the problem often arises due to conflicts between the
NVIDIA driver and the system’s power management. These services
sometimes prevent the system from entering or waking up from suspend
mode properly.

A couple of additional points to consider:

Check Logs: Always a good idea to check the system logs (journalctl
-xe or /var/log/syslog) for any additional clues or errors related to
power management or GPU drivers.

Kernel Parameters: Some users might need to adjust kernel parameters.
Adding nvidia-drm.modeset=1 to the GRUB configuration can help in
certain cases.

Driver Versions: Ensure that your NVIDIA driver is up-to-date.
Sometimes, these issues are resolved in newer driver releases.

Hybrid Graphics: For laptops with hybrid graphics (NVIDIA + Intel),
additional configurations might be needed. Tools like prime-select or
nvidia-prime can help manage which GPU is in use.

Testing Configurations: Before making permanent changes, test
different configurations. Use a live boot environment if needed to
avoid locking yourself out.

Thanks for sharing your solution
 

This is a response to the post seen at:
http://www.jlaforums.com/viewtopic.php?p=676344779#676344779