I confirm this issue on Ubuntu 20.04 LTS; Nvidia driver 440.100; Linux kernel 
5.4.0-42-lowlatency; GeForce 1060 6GB
Two monitors: LG 27GL850 (144Hz DP connection) and Asus VG248 (60 Hz 
single-link DVI connection, despite display could more)
If the second (slow) display is connected "effective" refresh rate on first 
(fast) display is limited to 60 Hz. I mean effective, despite xrandr shows 140, 
actual window moving traces, effects in 3D games are similar to 60 Hz, and 
testufo.com also shows 60Hz. If I disable slow display in nvidia-settings, 
effective refresh rate (window moving, games) are smooth as supposed to be, and 
ufotest shows 144 Hz and smooth ufo moving. 
I remember that there were no such issues with some previous version of nvidia 
driver (3xx)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-amdgpu 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/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to