this post was submitted on 16 Jan 2025
40 points (100.0% liked)

Linux

49045 readers
1169 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
40
[SOLVED] Suspend doesn't work on my Fedora Workstation 41 (lemmy.world)
submitted 1 day ago* (last edited 1 day ago) by mypasswordis1234@lemmy.world to c/linux@lemmy.ml
8 comments fedilink hide all child comments
 

SOLVED

Edit: Solved using workaround of creating a systemd service that disables GPP0 wakeup: https://forums.linuxmint.com/viewtopic.php?t=364220&start=20

Hey everyone!

The suspend feature has never worked on my system, so I always turned it off in the settings. But now, with the electricity prices going up in my country (we have the most expensive electricity in Europe, lol), I figured it’s a good time to tackle this.

When the system tries to go into sleep mode, it just wakes up right away, and the monitors don’t show anything (no signal). I’ve got a backlit keyboard and an RGB mouse, but they don’t light up during this, and the caps lock key doesn’t respond when I press it.

I’m on kernel 6.12.7 and I updated the BIOS a few days ago, but the problem is still there.

My hardware:

  • CPU: Ryzen 5 5600
  • MOBO: GIGABYTE B550 GAMING X V2 (rev. 1.3)
  • GPU: RX 6700 XT
  • PSU: SilentiumPC Supremo M2 (600W I guess?)
  • CASE: be quiet! Pure Base DX500

If anyone has any ideas on how to fix this, I would really appreciate your help!

top 8 comments
sorted by: hot top controversial new old
[–] Sustolic@lemmy.world 8 points 1 day ago* (last edited 1 day ago) (1 children)

This is a specific issue with several of the amd 500 series gigabyte motherboards, the only workaround is to disable GPP0 wakeup

You have to disabled it again every reboot so you will have to find a way to disable it automatically on boot

[–] mypasswordis1234@lemmy.world 3 points 1 day ago* (last edited 1 day ago) (1 children)

Thank you very much! It works now!!!!!!!! I used the disable-gpp0-wakeup service workaround from here. Unfortunately, I can't wake my computer with the keyboard or mouse, only with the power button, but I'll figure that out on my own.

Thank you so much for pointing out the issue.

cc: @Nilz@sopuli.xyz

[–] Nilz@sopuli.xyz 1 points 10 hours ago

Thank you!

[–] Nilz@sopuli.xyz 4 points 1 day ago

Just to chime in I'm facing the same issue on Arch with a 5950X and 6900XT on a X570 Aorus Ultra. It has never really worked for me either.

[–] Concave1142@lemmy.world 3 points 1 day ago (1 children)

I had an issue recently where my new PC build would not shut down. It would power itself back on on every shutdown immediately.

Checked the bios and found that I had Wake on PCIe (something like that) enabled. Soon as I disabled it, I was able to shut down my PC.

My assumption is that I was shutting down my PC and my monitor still being on was causing my Asus mobo to see it as a turn on event.

[–] mypasswordis1234@lemmy.world 0 points 1 day ago

All “Wake on” things are disabled in my UEFI settings.

To be sure, I also reset the UEFI to have “clean” settings, but that didn't help, unfortunately.

[–] narc0tic_bird@lemm.ee 1 points 1 day ago (1 children)

Does this happen with the network cable unplugged?

[–] mypasswordis1234@lemmy.world 1 points 1 day ago

Yes. I just checked it, and the same problem is still happening.