One more thing: to get it to work without a monitor connected I added Option "AllowEmptyInitialConfiguration" "true" to the Device section.
On Saturday, August 29, 2020 at 2:24:47 PM UTC-4 Eric Frey wrote: > I was having the same issue with version 450.66 on a CentOS 7 system. > Commenting out Option "DPMS" in the monitor section and adding Option > "hardpms" "false" as suggested by Patrik Pira fixed the problem. Many > thanks for the posts. > > On Monday, February 3, 2020 at 4:16:43 PM UTC-5 Patrik Pira wrote: > >> Looks like the Nvidia driver version 440.59 might be fixed now. I have >> not tried it though. >> >> From the releasenotes: >> - Disabled frame rate limiting for configurations without active displays >> when HardDPMS is enabled. >> >> Den fre 6 dec. 2019 15:22Patrik Pira <[email protected]> skrev: >> >>> From the changelog for 440.26: >>> >>> - Enabled HardDPMS by default. See the README entry on the X configuration >>> option "HardDPMS" for more information. >>> >>> >>> Try, >>> >>> Option "HardDPMS" "false" >>> >>> >>> Den lördag 19 oktober 2019 kl. 10:47:32 UTC+2 skrev ziegler: >>>> >>>> I have set up VirtualGL to run OpenGL applications on an Nvidia card >>>> through TurboVNC. >>>> >>>> I run lightdm display manager, and a mate-session. >>>> >>>> Based on what glxinfo tells me, the setup seems to be working: >>>> >>>> "OpenGL vendor string: NVIDIA Corporation >>>> OpenGL renderer string: GeForce GTX 1650/PCIe/SSE2 >>>> OpenGL core profile version string: 4.6.0 NVIDIA 440.26" >>>> >>>> I now have the strange effect that basically any application (I have >>>> tried glxgears, glxspheres and my own custom code) that I run through >>>> vglrun runs with exactly 1.00 FPS (check the screenshot below). >>>> >>>> The CPU usage while running is negligible, so I assume that there is >>>> some artificial throttling happening, like some bogus VSYNC. >>>> >>>> One thing special maybe about my setup is that this is a rack mount >>>> server, which, appart from the discrete Nvidia card, also has an onboard >>>> VGA which runs GL via mesa, so this is a dual head setup. >>>> >>>> I separately tried >>>> >>>> VGL_SPOILLAST=0 >>>> VLS_SYNC=1 >>>> >>>> With no noticeable effect. >>>> >>>> Has anybody experienced this strange effect? Any ideas on how to solve >>>> it? >>>> >>>> Any hint is appreciated, Thanks! >>>> >>>> Julius >>>> >>>> [image: Annotation 2019-10-19 104529.png] >>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "VirtualGL User Discussion/Support" group. >>> >> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/virtualgl-users/08d89bf7-e24a-4969-9f51-53f8150d0e65%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/virtualgl-users/08d89bf7-e24a-4969-9f51-53f8150d0e65%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- You received this message because you are subscribed to the Google Groups "VirtualGL User Discussion/Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/b68c8c3d-c151-4c75-b956-d2722194cb22n%40googlegroups.com.
