Do you have a swap partition? If not try disabling hibernation.
this post was submitted on 21 Sep 2024
25 points (90.3% liked)
Linux
8106 readers
104 users here now
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.
founded 1 year ago
MODERATORS
Yes, I do have a swap partition with the same size as my RAM
did you try switching to text mode tty console using Ctrl-Alt-F3 or -F4 or -F1 or so? if that works, maybe switching back helps. if switching back doesn't help, you can at least investigate the logs/journals with text mode.
Yeah, I'd certainly try to see if it's a graphical issue or actually locking up.
You can also try toggling num/caps/scroll lock to see if the keyboard LEDs respond. That's a core kernel function, so if even that isn't working, it's really locked up. (Or just really slow to respond.)
It didn't respond to that anymore after entering sleep mode
I see. You could try and enable Magic SysRq, but honestly I don't see how that would lead to a permanent fix.
Thanks for the suggestion, I hadn't heard of it yet and it seems very useful. However, I might as well just shut it down completely in this scenario if I have to reboot anyway.
I've been having similar issues for a while on OpenSUSE.
I noticed that if I press the power button it works, but if I try the keyboard, the issue happens
I can't wake it with the power button either. Do you mean that it freezes after using the keyboard?
Yes, that's what I meant.
Sorry I can't help you more
Had that happen yesterday for the first time with a similar (AMD CPU and GPU) setup.
Have you been able to find a fix?
Didn't happen again so far, so I didn't investigate further. The qcode display on my mainboard displayed an error code I think.
Okay, it now seems to happen more frequently.
Man, I had so many issues related to standby and VRR seemingly caused by the amdgpu driver most of the time that I'll definitely reevaluate whether an AMD GPU is the correct choice for Linux in the future.
Not sure if you still encounter the issue, but I finally did some trial and error.
It doesn't seem to be related to the AMD GPU, as I briefly swapped it out for an Intel Arc A750 and had the same issue. I then went ahead and tried disabling most onboard devices of my mainboard (ASUS ROG Strix B650E-E) and sure enough: that fixed it. I then re-enabled them one by one, trying waking the PC from sleep each time and narrowed it down to the on-board Bluetooth.
Do you happen to have a mainboard that has the "MediaTek MT7922A" (or AMD rebranded variant "AMD RZ616") Wi-Fi/Bluetooth card? If so, try disabling the Bluetooth portion of it in the BIOS.
My motherboard (AMD B550) doesn't seem to have built in Wi-Fi/Bluetooth. It has a Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac PCIe Wireless Network Adapter.
No, it's has a Realtek PCIe card, but thanks anyway.