I don't know the exact fix for your issue but I did have that happen before. I had GSconnect extension installed in GNOME DE and kde connect on phone. From the phone I sent the Wayland screen on busctl command and it wakes up the monitor.
I had exactly the same problem on kernel 6.11+. To confirm, try downgrading the kernel to 6.10.x.
My issue was with modern sleep, and it's persistent on all distros with 6.10+.
IIRC what I ended up doing was disabling modern sleep in the bios.
Looks like I'm running kernal 6.17x so I'll look into downgrading via the bios.
What happens when you turn off the PC, unplug (or flip the power supply switch), press power, then replug or flip back on the psu switch and start the PC? Does net and gpu return?
Exactly same behavior.
Okay, rules out hardware then. Hmmm...
What kernel and Nvidia driver versions are you on?
Also, just download any Live USB and see if you get the same suspend issues to test it out. Dmesg output would also be useful right after the problem happens.
Kernal 16.17x. I forget what driver is on there now, but it's around 580x.
I did a clean install early on after updating to the Nvidia drivers killed my Linux install the first time. I was fine for about a week and then things crashed again.
For some reason, I can't get dmesg to do anything. I did run journalctrl -b -p err and I got a few error messages. see below.
These look like they occurred during boot. I ran these through AI and it responded that Most likely causes:
GNOME/GDM packages are broken or partially installed Your user runtime/session is failing Bad permissions in your home folder Display driver issue causing GNOME session startup failure Leftover damage from previous repair/driver changes
Jul 07 13:58:14 host gdm3[3615]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISP> Jul 07 13:58:42 host gdm-password] [4192]: gkr-pam: unable to locate daemon control fi> Jul 07 13:58:42 host qdm3[3615]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISP> Jul 07 13:58:43 host systemd[4203]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkc> Jul 07 13:58:43 host systemd[4203]: Failed to start app-gnome-gnome\x2dkeyring\x2dsec> Jul 07 13:58:43 host systemd[4203]: Failed to start app-gnome-gnome\x2dkeyring\x2dssh> Jul 07 13:58:43 Jul 07 13:58:43 host systemd[4203]: Failed to start app-gnome-user\x2ddirs\x2dupdate> Jul 07 13:59:14 host qdm3[3615]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DI>
Jul 07 13:57:52 host thermald[1110]: Thermal DTS or hwmon: No Zones present Need to c>
host systemd[4203]: Failed to start app-gnome-im\x2dlaunch-4737.scope>
Let me make sure you performed the Nvidia driver install in this order:
nvidia-smi to ensure everything loaded correctlyAll of that sound about right?
I can't recall but I may have followed a similar process before, but I'll go through that once again.
Ask Claude Opus. Follow its suggestions. You'll probably find a fix.
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
Be respectful: Treat fellow community members with respect and courtesy.
Quality over quantity: Share informative and thought-provoking content.
No spam or self-promotion: Avoid excessive self-promotion or spamming.
No NSFW adult content
Follow general lemmy guidelines.