Hello,
In my case, appending __GL_SYNC_DISPLAY_DEVICE=DP-0 in the
/etc/environment file (DP-0 is my 144hz monitor - see X Server XVideo
Settings in NVIDIA X Server Settings) seems to works (config: GTX
1070/60 Hz + 144 Hz monitors).
I forced resolution + frequency in NVIDIA X Server Settings for
Additionnal note for the previous comment: it also works when Sync to
VBlank is enabled (tested with glxgears), but causes tearing for the 60
hz monitor.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu
Thanks for pointing that out because I also had
__GL_SYNC_DISPLAY_DEVICE=DP-0 in /etc/environment as completely forgot
to mention that in my previous comment to yours here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphic
I've also run into this issue on Pop!_OS 20.04 LTS; Nvidia driver
450.66; Linux kernel 5.4.0-7642-generic; GeForce GTX 1080 8GB; mutter
3.36.4; GNOME Shell 3.36.4.
I'm running two monitors: NS-PMG278 (144Hz DP connection) + Dell U2719D
(60Hz DP connection), both at 1440x2560.
I'm getting the exac
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 la
OK I have now regression tested on the latest 19.10, with the above
^^software stack. All except incrementing the kernel from 5.8.11 to
5.8.13.
I can now confirm that the old bug has also re-appeared on 19.10 too. So
it is not only exclusive to 20.04.
To myself, I really don know what to try. But
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1430
https://gitlab.gnome.org/GNOME/mutter/-/issues/1430
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/1430
Importance: Unknown
Status: Unknown
** Also affects: mutter (Ubuntu)
Importance:
** Changed in: mutter (Ubuntu)
Status: Opinion => Invalid
--
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
** No longer affects: mutter
--
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
moni
dreamcat4,
Ubuntu 19.10 is not supported. It reached end of life on July 17, 2020.
This is a bug/design feature of Xorg graphics drivers like Nvidia and
AMD's. You can work around it either by explicitly configuring the
driver to sync to the fastest monitor, or by enabling "TearFree" if
available
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1139
https://gitlab.gnome.org/GNOME/mutter/-/issues/1139
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/1139
Importance: Unknown
Status: Unknown
--
You received this bug notification because y
** Changed in: mutter
Status: Unknown => New
--
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
** No longer affects: mutter (Ubuntu)
** Bug watch removed: gitlab.gnome.org/GNOME/mutter/issues #503
https://gitlab.gnome.org/GNOME/mutter/issues/503
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubunt
Hello,
I'm also have this bug.
Ubuntu 20.04.1 LTS
Video card - gtx 1070
I'm install 450.57 nvidia driver, but it doesn't help.
I have two monitors - Dell 60hz and Acer 144hz. If Dell is turn on, Acer
enforce to 60hz.
If you need any additional information, I can add any.
--
You received this
Did you see it work on previous ubuntu version (19.10)? Or is 20.04 the
first version you tested here?
--
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:
Hello, dreamcat4!
20.04 is only version I tested this case
--
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 frame
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" re
I can also confirm that this bug is still present. I'm on Ubuntu 19.04
with the latest drivers & updates installed.
Also, I want to add something here: It's not that it specifically
limits the framerate to 60 Hz. Rather, it limits it to the monitor with
the lowest refresh rate. Try setting one
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
mo
I can confirm this bug too. But additionally I have noticed one more
interesting fact:
It seems that this bug affects only PCs with dedicated GPUs (AMD,
Nvidia). When I connect monitors into motherboard ports this bugs
disappears. In my case via VGA(60Hz) and DVI-D(120Hz), but I believe
that with
well by that logic, then somebody with an amd ryzen APU (such as 3200G
or whichever with the integrated Vega graphics). Would also not be
affected by this bug.
But the other reason would be that intel's linux igp drivers are not
affected. That is a different reason as to whether the gpu is being
r
Good point, then there can be 2 explanations:
1) dedicated vs integrated GPU
2) intel vs amd/nvidia
I will try to get some AMD APU to test it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
https:/
23 matches
Mail list logo