It would be nice to understand what is going on here. Currently on 19.10 and have not upgraded to 20.04 yet... because of this very same bug! It took so long to get rid of the last time around. Many months.
Should also do a regression test here back on 19.10 too? It seems I can install both the latest kernel v5.8.11 and the nvidia drivers are currently at 450.57 (on this system). Looking to re-test here soon... also need to remember / check my version of gnome shell (xorg). It seems to be this one? gnome-shell/eoan-updates,now 3.34.3-1ubuntu1~19.10.1 amd64 [installed] According to my machine those are all now fully up to date, for what is currently available on the ubuntu 19.10 release. All these above as of today ^^. With 0 pending updates. Oh wait... mutter version? libmutter-2-0/now 3.28.3-2~ubuntu18.04.2 amd64 [installed,local] window manager library from the Mutter window manager libmutter-5-0/eoan-updates,now 3.34.3-1ubuntu1~19.10.1 amd64 [installed,automatic] window manager library from the Mutter window manager mutter/eoan-updates,now 3.34.3-1ubuntu1~19.10.1 amd64 [installed] Example window manager using GNOME's window manager library Will come back with the testing results in my next comment. After a clean boot into gnome shell etc. -- 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
