Yes, sorry. I am trying to track hundreds of bugs in my head and I don't
always remember (or reread) the context of each one every day.
I have now modified the task list for this bug so it tracks both Nvidia
and AMD drivers.
** No longer affects: mutter
** Also affects: xserver-xorg-video-amdgpu (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- [nvidia] [xorg] multiple monitors: limits the framerate of faster 120/144hz
monitors to 60hz
+ [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors
to 60hz
--
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 mutter package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-418 package in Ubuntu:
Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
New
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/mutter/+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
