view the rest of the comments
Linux
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.
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.
Yeah, the modern sleep thing is tricky. Apparently especially on laptops but also on some desktops the manufacturers don't implement all the sleep modes correctly, so depending on the device, some of the sleep modes work and some don't. So you have to try out what works, and you have to always update your linux kernel config to use the correct sleep mode that you set in the bios.
Kernel 6.11 changed something about how sleep works in the kernel, don't know what exactly, but there was a major rework.
The information is pretty spotty to find on google, with a lot of variation between the hardware and quite a overlapping issues.
This is one of the cases where ChatGPT was actually more helpful than google.