Adaptive Sync causes screen signal loss after power cycling the monitor

Graphics / Linux Linux
1

-Software-
Distros tested: Ubuntu 19.04 (fresh install), Kubuntu 18.04
Tested driver versions: 430.40, 418.56

-Hardware-
Monitor: Alienware AW2518HF (non validated).
GPU: GTX 1070ti

-Steps to reproduce-

  • Login to desktop and make sure Adaptive Sync is working.
  • Turn off you monitor (don't turn off your machine).
  • Wait a few seconds and turn you monitor back on again.
  • Start a fullscreen application/game with Adaptive Sync active.
  • Observe the screen going blank and losing signal (like if nothing was attached to it).
  • Close the fullscreen application (blindly) with Alt+F4 or use a virtual terminal and kill it from there.
  • Observe the screen magically come back to life.

    • If you launch a fullscreen game with Adaptive Sync disabled, the screen keeps working normally.

    This bug persists until you change metamodes with nvidia-settings (you can change to another resolution/refresh rate and then switch it back for the bug to go away) or logout from your X session and log back in again.

    Launching the Unigine Heaven benchmark via terminal when triggering this bug shows this (repeated ad infinitum):

    GLFrameBuffer::enable(): unsupported
OpenGL error: invalid framebuffer operation

    I don’t have another FreeSync monitor to test this with so I can’t write out the possibility that this might be related to this specific hardware only… Nvidia’s Adaptive Sync support on this one seems quite buggy to say the least…
    nvidia-bug-report.log.gz (1.18 MB)

    1 Like
    2

    I have the exact same issue on Pop!_OS 20.04 and the 455.23 driver. I am using an ASUS VG27AQ G-SYNC COMPATIBLE monitor. As soon as my screen goes blank after locking the screen, G-Sync is broken and I have to log out and log back in to make it work again.

    3

    Actually, since I upgraded to 440.82+ a while ago, I can’t reproduce this problem anymore. If you don’t have a 3080 or 3090, try to downgrade to a stable driver release just to see if it’s a regression in the new beta drivers that you’re using right now or not.

    Also isn’t your monitor the one that can use backlight strobing and adaptive sync at the same time? Assuming that’s the right monitor, try to disable what ASUS calls “ELMB” sync in your monitor’s hud just to see if it changes anything. I’m not really sure how (or why) that could help but, at the very least, that’s another thing you can try…

    4

    I think Pop!_OS has slightly modified repositories for the NVIDIA drivers compared to Ubuntu, so I am not able to downgrade to 440 (I tried, and it just installs 455 anyways) unless there is a way to force it.
    Also, I have been having this issue for a while, even on 440 drivers.

    You are correct in the fact that my monitor has ELMB Sync, but I normally have it disabled and the issue still persists.

    @green_squid, what card, kernel, driver, and distro are you currently using? I am using the 5.4 kernel, I don’t know if upgrading to a newer one would help.

    5

    Never used Pop!_OS myself but on Ubuntu you can just purge the latest 455 beta and install the nvidia-driver-450 metapackage from a terminal.

    GPU: GTX 1070ti
    Kernel 5.8.13-xanmod1 (5.4 still works fine though)
    Drivers: 450.66 (from the ppa)
    Distro: Kubuntu 20.04

    6

    So I managed to force the 450.51 driver using the Ubuntu PPA. The issue still persists, although I noticed that it sometimes has a different behavior:
    After I turn the monitor off and on again, if I launch Overwatch, the screen loses display signal. On the other hand, if I launch Osu! Lazer, which runs at a much higher framerate, I get crazy flashing on the display. I can sort of make out what’s on the display but it is completely unplayable. It might have something to do with the framerate?