Hello there. Good news for a change:
Re-tested this bug today on latest linux 5.3.1 kernel and nvidia 435.21
binary (closed) drivers. And it seems like there might be some
improvement now.
What I noticed this time:
* Enabled 120hz overclock on my high refresh 120hz monitor, and rebooted this
monitor. It is my primary display.
* Opened nvidia settings ("NVIDIA X Server Settings")
* Set the frame rate of this dispaly in there to 120hz with force full
composition pipeline both on
* Frame rate was initially capped at 60 fps. Which matches the slower 2nd
monitor as before. As shown by the command: 'sudo journalctl -f'
* Then I unplugged my 2nd slower 60hz monitor.
* Frame rate was still capped at 60 fps
* Closed some graphical (probably open GL based) programs: Glxgears, kodi, and
bitwig studio.
* Frame rate was now capped to 71 fps
* Went back to NVIDIA settings GUI
* Navigated to "OpenGL Settings" page
* Un-checked all of the first 4 settings on that page, which were:
[ ] "Sync to VBlank"
[ ] "Allow Flipping"
[ ] "Allow G-SYNC/G-SYNC Compatible"
[ ] "Enable G-SYNC/G-SYNC Compatible Visual Indicator"
* The fps shown in 'sudo journalctl -f' is now going all the way up to
120hz. Whilst running the command 'glxgears' to make a graphical
workload
I then went back and re-enabled all of the options in the OpenGL page,
except for "Allow Flipping", like this:
[x] "Sync to VBlank"
[ ] "Allow Flipping"
[x] "Allow G-SYNC/G-SYNC Compatible"
[x] "Enable G-SYNC/G-SYNC Compatible Visual Indicator"
* The frame rate was still reaching up to 120Hz.
* Then I plugged my 2nd slower 60hz monitor back into the NVIDIA graphics card
* Previously this was the point in the test when the frame rate would
immediately drop back down to only 60 FPS
However this time, it stayed at 120fps. Which is very encouraging and a
positive result from my testing today.
What I am not sure about:
* How easily it is to get the system into this state
* For example whether it can come up like this after a reboot. Or if it
requires a certain ritual / ceremony / fernagaling to get everything to this
point
* How stable this state is, how delicate / easily broken by launching some
specific program(s).
In particular I am thinking about fullscreen games. However my gpu here
(GT 1030) simply isn't powerful enough to do proper testing for more
demanding programs and workloads like that.
Anyhow I think it's a great result from what we can observe so far. Just
wish I had a better graphics card now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
https://bugs.launchpad.net/bugs/1820832
Title:
[xorg] multiple monitors: limits the framerate of faster 120/144hz
monitors to 60hz
Status in nvidia-graphics-drivers-418 package in Ubuntu:
Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
Confirmed
Bug description:
multiple monitors on xorg
=============================
Was recently discussed over on
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892
Another user + myself have the following issue:
The slowest connected display limits the FPS. The test case we used is
over at the top of the other bug report ^^
This we found today happens with either amd vega graphics, or nvidia
pascal graphics, the vendor doesn't seem to matter. We have both seen
the same issue (xorg).
This is on 18.10, and booting into the 'Gnome (xorg)' login option.
With the FPS being logged by journalctl -f. With only single monitor
attached. Then it initially goes as high as the primary monitor can
show. (And glmark2 running in background, to maintain a continued
load). Which is 120fps for my case. Then as soon as secondary monitor
is plugged in, which is a 60hz TV. This is being plugged into the HDMI
port of the same graphics card in real time. Then the FPS logged by
'journalctl -f' drops, and becomes capped to 60hz, in the output being
printed by journalctl -f.
My setup:
kernel 5.0.0-050000-lowlatency #201903032031
NVIDIA Driver for UNIX platforms 415.27 (the closed source one)
ubuntu 18.10
mutter version:
mutter/cosmic-updates,now 3.30.2-1~ubuntu18.10.4 amd64 [installed]
mutter-common/cosmic-updates,cosmic-updates,now 3.30.2-1~ubuntu18.10.4 all
[installed]
To confirm where the '.4' at the very end of the ~ubuntu18.10.4
version number, it seems to be that we have updated now on our client
machines the be most recent bugfix updates, kindly provided by Daniel.
Which closed the other bug
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 being
referred to, as being solved for people's single monitor scenarios.
Thanks again for the other recent bug fixes in this area, it is a nice
progress. Very helpful! We hope you can also look into this latest
problem / issue for the multiple monitor scenario.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1820832/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
