The last couple of weeks my Tumbleweed laptop has had some issues coming out of sleep mode. My typical use is when done with my laptop I just close the lid, come back later (plugged in the whole time). It’s always waken quickly though usually the screen is dim and I have to adjust the brightness (it will show at 100%, but as soon as I go down a little bit it will brighten right back up).
Anyway, I’ve had a couple instances in a row now of putting the computer to sleep and when I come back the screen never comes back. I open the laptop and the screen is just blank. I see it’s still powered on from the lights, but even adjusting the brightness (using the Fn keys) doesn’t work so I’m not sure it’s a brightness issue but something else. I have to hold the power button to force a shutdown then restart and all is well.
Sadly I don’t know best way to troubleshoot this. I did try journalctl -k | lnav to see if there’s any kernel issues but nothing I could decipher. Any help identifying the issue and troubleshooting this would be appreciated.
Laptop is an HP Envy X360 15" - has nVidia MX250 video but only use iGPU most of the time (10th gen i7)
That looks very similar to my thread, describing the exact same problem . . . . So, from your post over there where you said you are using “proprietary” nvidia drivers, one of the problems with that choice is that nvidia doesn’t exactly keep pace with the bleeding edge of TWs technology . . . and that might explain why the machine isn’t reviving from suspend in 6.13???
You can expand the capacity of TW to accept more than one kernel, and then you could try to add the previous kernel back into the mix, and then use grub’s “advanced options” to select the older kernel . . . .
Seems to be hard to get any “bounce” on this issue on the forum these days. It keeps recurring in different iterations, requiring some new insights and new edits to get suspend reviving working again. So far, dropping back in kernel is what gets it done, but I am using “nouveau” drivers . . . .
Same here, Tumbleweed on a Lenovo P51, Nvidia proprietary drivers.
Not a solution, but it works to me to change to another TTY with ctrl-alt-f1 and then return to the X session login screen with ctrl-alt-f2
That is a good tip. Didn’t think of it because the display is black, so why would I try to go to a TTY?? But that f1 to f2 might be something to try, in my Leap install . . . Leap seems to be more messed in my case than the TW, since I can roll back to an earlier kernel in TW, but seems like in Leap the alternate kernels have been distorted???
I didn’t think to try a different TTY either. I’m on KDE btw in case there’s a similarity there because I am not on the nVidia proprietary drivers. I’m on the recently updated version 570.86.16 from the TW repo. I will try the TTY thing next time. I can say when we just went through the plymouth issue’s that was one thing I was able to do to get out of that mess, so I’m going to properly flog myself for my lack of creativity.
I have filed a bug report on my issue awhile back . . . so far not a lot of bounce there, but feel free to add a comment over there, might get something going “upstream”??
So, posting this over here: Alrighty, on the third use of revival from suspend, the display does NOT revive in the newest kernel & packages. Back to square one on it. Now the 5th oldest kernel which was working has been replaced by the newest kernel which appears to be unreliable for the purposes of waking up the display.
And, also, the TTY move didn’t bring the display back from the black. I tested it when the display was working, and voila, it did work. With the display out, no, it did not . . . . : - 0
Mine is intermittent. More often than not it will wake as expected. I’m trying to figure out if there is some behavior I’m doing that prompts this. I can say the last time it happened I did try switching TTY and it did not respond, nor did it respond to CTRL-ALT-DEL, CTRL-ALT-ESC or anything else. Just a blank screen, no cursor or anything. Only a hard reset worked.