• SupportSolved
  • Screen stay black when the computer comes back from sleep state/standby mode

penny-farthing Do I understand that the problems I encountered could be caused by those observed on kernel 6.10 and on NVIDIA graphics cards?

Possibly. I've seen another person mention that their boot process got stuck at the manufacturer's logo; though I'm unsure whether that's connected to the kernel 6.10 + Nvidia combination or not.

penny-farthing I tried again and it worked the same way

By that you mean it got stuck again?

    Staudey By that you mean it got stuck again?

    When I returned to a normal situation, I tried to hibernate my computer again and I found the same anomalies as before, during my first attempt (no shutdown of the PC, but a restart, then a freeze on the Gigabyte logo; forced to turn off, then turn on my machine again: long time before being able to open my admin session and to see that the hibernation process had not worked).

    Going trough nvidia forums, this one looks most relevant (bug acknowledged by nvidia).

    link

    a month later
    • After last update:
      • budgie 10.9.2
      • Solus 4.6 Convergence
      • Linux 6.11.5-307.current

    graphic card GTX1070

    • After boot, first try to come out of standby, got the following screen:

    • Then some reboots. Second try to come out from standby: I obtained a black screen with a blinking white cursor.

    I have the same configuration as @touzain , and following the last major Solus update, I tested the Hibernate (Mettre en veille) and Suspend (Suspendre) functions of the User Indicator applet again and here are the results.

    Hibernate:
    I left the Firefox window open on a Solus forum post (post #25 of 75), then I selected Hibernate: I got a black screen, the computer remaining on indefinitely; so I turned off my computer, then I turned it back on after 2 minutes -> the Gigabyte test pattern appeared, then the boot started and after 56 seconds, after logging in, the screen opened a new session.
    If I remember correctly what @WetGeek said on a previous post, in principle, we should get the display of the window of the application we were on before hibernating, and this, in the same place of its consultation.
    NB. Firefox allows you to recover the page you were on before hibernating.

    Suspend:
    I left the LibreOffice application open on a .odt document, then I selected Suspend: my computer turned off immediately; I turned it back on after 2 minutes -> there, no Gigabyte test pattern, a screen remaining black indefinitely; so I turned off my computer, then I turned it back on after 2 minutes -> the Gigabyte test pattern was displayed, then the boot started and after 53 seconds, after logging in, the screen opened a new session.
    NB. LibreOffice, when opening, asks us if I want to recover the document consulted before suspending the session.

    So that's all, if this can help to see more clearly and remaining at your disposal,
    Best regards.

    Anyone who is affected by these issues, please look through our issue list. If you don't see an issue that matches yours, please file a new one. That's the only way we will be able to investigate and fix these. Thanks.

      zero-vector You could try the nvidia-beta-driver packages to test this particular change (if you're comfortably with running a beta release of a GPU driver)

        Staudey Thanks, I reverted to lts kernel and 470 Nvidia drivers for now.
        I will probably stay at this setup for some time, until I regain the willpower to tinker with new versions again.

        penny-farthing
        Thanks for opening the issue.

        There is a thread on the NVIDIA forums for feedback on the 560 driver for those interested.

        a month later

        Seems to be solved since last update, for me at less. Waking up is working, quite slow but working. Good job, thank you.

        • Solus 4.6 Convergence
        • Budgie 10.9.2
        • kernel Linux 6.11.10-310.current
        • Nvidia Driver Version: 565.77

        For me, the issue can be closed. Is it ok for other users with equivalent problem?

        7 days later

        I have also noticed that the issue has been resolved as of the latest updates.

        kernel: 6.12.5-311.current
        nvidia driver: nvidia-glx-driver-current, version: 565.77, release: 554

        If anyone still has an issue with this, please open an issue on our tracker so we can investigate.