There is nothing in logs that would tell anything about the problem. To me this looks like something maybe in gnome-shell or mutter “disturbs” the Nvidia driver g-sync feature and “takes over” refresh of the screen. So toggling screen refresh rate somehow resets the issue. Then when starting the game it is like the driver “takes over” and G-sync then drives the refresh rate up to 100 Hz and keeps it on. Another way without rebooting is to change Resolution in Nvidia-settings from Auto to 3440x1440 and then set resfresh rate to 60 Hz (sometimes toggling a couple of times between 60 and 100 Hz is necessary). Now to get it to work again in the game, you can reboot the PC, or simply turn off g-sync in Nvidia settings. To get it to stop losing signal you must quit the game or alt-tab to desktop. But when I pause the game and let the Gnome screensaver lock the screen, then unlocks screen and continue gaming, the monitor starts to turning the input off and on every few seconds (like it has lost the signal). On-screen indicators show FLIP - VSYNC ON and G-SYNC. The game plays with G-sync and refresh rate looks variable (everything plays smooth and nice). I use displayport cable directly connected to the screen.Īfter starting the PC and immediately starting a game with G-sync on (and with “Allow G-SYNC on monitor not validated etc.”), everything works fine. This is an ultra-wide (21:9) 34" 100 Hz screen with freesync support. The issue has existed in several past versions of the linux driver (as long as I’ve had this monitor). I’m using Fedora/Gnome and Nvidia linux driver 430.34 (GTX 1070 card). I wonder if this is a known issue and if someone has any idea in which component the issue is.
0 Comments
Leave a Reply. |