I’ve been having issues with my PC not waking from sleep, the fan keeps spinning, but the screen stays black, and it won’t respond. I could just keep it on all the time, but it uses a lot of electricity, so I prefer not to.

So far I’ve tried:

  • Using Wayland / X11
  • Secure boot off/on
  • Installing the latest BIOS update
  • Waking with keyboard presses, mouse movement, power button

Some more information:

  • Sleeps works fine on Windows.
  • I’m using an AMD CPU & GPU
  • I’m using OpenSUSE Tumbleweed, and I’m fully up-to-date (version 20240919).
  • I’m using kernel 6.10.9-1-default (64-bit)
  • I have a swap partition with the same size as my memory
  • narc0tic_bird@lemm.eeEnglish
    31·
    3 months ago

    Had that happen yesterday for the first time with a similar (AMD CPU and GPU) setup.

      • narc0tic_bird@lemm.eeEnglish
        2·
        1 month ago

        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.

        • qaz@lemmy.worldOPEnglish
          1·
          1 month ago

          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.

      • narc0tic_bird@lemm.eeEnglish
        2·
        3 months ago

        Didn’t happen again so far, so I didn’t investigate further. The qcode display on my mainboard displayed an error code I think.

      • narc0tic_bird@lemm.eeEnglish
        2·
        2 months ago

        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.