(SOLVED) Linux Laptop Gets Stuck on Black Screen After Suspending, No Way to Use Unless Restarted With Power Button

Recently bought a new laptop that comes with an AMD Radeon gpu and installed OpenSuse Tumbleweed on it which I had installed on my previous laptop as well but never had issues with suspending and resuming. However, with the new laptop, I am unable to resume after suspending or closing the lid unless I force it to shut down by holding the power button which is a major inconvenience.

I’m also dual booting alongside Windows and have secure boot enabled and have the Linux and Windows partitions encrypted if that’s what’s causing it which I doubt since this is the same setup I had on my old laptop

Any suggestions or advice would be greatly appreciated.

Edit: I was able to figure out that it does not suspend at all when I close the lid or click the suspend button on Gnome. Only found this out because when going through YaST Services Manager and manually starting systemctl suspend, the laptop suspends just fine and wakes back up. So I’m starting to think it’s more of a systemd issue? Any inputs?

Edit: turns out it was an issue with the official opensuse built kernel not sitting well. Downloaded a community version from the opensuse repository and it works fine. Very odd

fhek,

These problems, 9/10 times is solved by using another kernel.

ShaunaTheDead,
@ShaunaTheDead@kbin.social avatar

Are you using the dedicated GPU as your primary GPU or the integrated GPU? I've found using the dGPU as the primary can sometimes lead to suspend/resume issues.

MagneticFusion,

Pretty sure it only has an integrated GPU

Hector,

It is happening to me too on my surface tablet. Do you have TLP installed? Just out of curiosity

MagneticFusion,

Yes I do. This is the same exact setup I had on my previous laptop and the previous one worked fine but this one does not. Would you advise I uninstall TLP?

Hector,

According to this github.com/linux-surface/linux-surface/…/1113 TLP is one of the culprits but I would rather the boot sequence and wake up from suspend process hang than uninstall TLP. Without it, intel boost keeps overheating my tablet and the battery becomes shit.

MagneticFusion,

Just uninstalled it and it did not fix the issue sadly

paradox2011,

I know it’s not super helpful, but I’ll add that this happens to me periodically on my EndeavourOS, Intel based desktop as well. Not even all of the time, just sometimes when it suspends. It seemed to get better when I changed my settings to hybrid sleep, but it just happened again yesterday, so I’m back to square one. Bookmarking to check for possible solutions later.

charliegrahamm,

I have the same problem with shutdown occasionally too, using > sudo shutdown now solves the problem.

paradox2011,

Interesting, I’ll look in to that

olympicyes,

I have this same problem when passing an AMD GPU to a virtual machine on my Linux desktop. It works the first time and then doesn’t initialize the card on reset. What you’re experiencing sounds an awful lot like the AMD Reset Bug. In my case a host machine restart resets the card. I’d suggest checking the bios to see if it’s got some kind of quick restart feature that is intended for Windows. Not being able to close the lid is unacceptable. You should return it if you can or run windows.

GolfNovemberUniform,
@GolfNovemberUniform@lemmy.ml avatar

I have exactly the same issue (though in my case sometimes there are artifacts instead of just a black screen). I would love a solution but I never found one unfortunately

gunpachi,

I have a similar issue but for me the black screen comes at random times when I open, close or move my windows or mouse.

I found a temporary fix for it by checking out the archwiki amdgpu page

But it still occurs , especially when I wake up my computer after suspending it.

TwoBeeSan,

Happens on my manjaro desktop too. Hope you find a solution.

Schorsch,

I had a similar issue on a new out of the box HP Prodesk. Independently of the distro I was running it wouldn’t want to wake up from standby. Turned out to be an (firmware?) issue with the SSD. After replacing it everything worked fine.

souperk,
@souperk@reddthat.com avatar

It’s a wild guess, but try to disable Bluetooth or WiFi before suspending.

It’s doesn’t happen with all hardware, but it is a knowing issue.

Goingdown,

I have seen this on HP laptop with WWAN device installed. Disabled device from Bios and problem went away.

skullgiver, (edited )
@skullgiver@popplesburger.hilciferous.nl avatar

deleted_by_author

    •
    backhdlp,
    @backhdlp@iusearchlinux.fyi avatar

    Can you check dmesg and/or journald? What model Laptop is it?

    MagneticFusion,

    deleted_by_author

    •
    backhdlp,
    @backhdlp@iusearchlinux.fyi avatar

    sudo dmesg | less and something with journalctl (not sure because I don’t use that currently). There should be some other logs you can check in /var/log too, kern.log sounds useful (though that might just come from sysklogd).

    ABeeinSpace,

    journalctl -b -1 should get you logs from the last boot

    MagneticFusion,

    I was able to figure out that it does not suspend at all when I close the lid or click the suspend button on Gnome. Only found this out because when going through YaST Services Manager and manually starting systemctl suspend, the laptop suspends just fine and wakes back up. So I’m starting to think it’s more of a systemd issue? Any inputs?

    CameronDev,

    I have/had a similar issue, but for an old nvidia laptop. What happens if you get it to suspend and resume again? Mine would come back the second time.

    MagneticFusion,

    deleted_by_author

    •
    CameronDev,

    Yeah, but for mine, i could close the lid and it would suspend again, and then i could resume. Pressing the power button briefly also worked.

    KryptonNerd,

    I don’t have any advice, but I just wanted to confirm I have the same issue sometimes with my laptop running fedora.

    souperk,
    @souperk@reddthat.com avatar

    If you use a recent release of Fedora (last 2-3 years). Try disabling WiFi and/or Bluetooth before suspending. There is an issue with some hardware, especially adapters. It doesn’t happen everytime, and it’s hard to accurately reproduce. Also, the symptoms can vary from black screen to sudo being stuck.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • linux@lemmy.ml
  • fightinggames
  • All magazines
    •