Focal PRIME Synchronization still not working (450.x)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nvidia-graphics-drivers-390 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
nvidia-graphics-drivers-435 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
nvidia-graphics-drivers-440 (Ubuntu) |
Confirmed
|
High
|
Unassigned | ||
nvidia-graphics-drivers-450 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Ubuntu 19.04 (Disco)
Linux 5.4.6-050406-
linux-firmware-
mutter-
nvidia-driver-440:
Installed: 440.44-0ubuntu1
Candidate: 440.44-0ubuntu1
Version table:
*** 440.44-0ubuntu1 500
500 http://
100 /var/lib/
I've noticed screen tearing with the nvidia 440 driver on 5.4.x kernels. Typically, this is resolved by setting the xrandr option 'PRIME Synchronization' to '1', however, doing so with the above combination results in never being enabled.
$ xrandr --output eDP-1-1 --set 'PRIME Synchronization' '1'
$ xrandr --verbose | grep PRIME
PRIME Synchronization: 0
PRIME Synchronization: 1
PRIME Synchronization: 1
PRIME Synchronization: 1
Reverting to Linux 5.0.0-37-generic resolve the issue, so I figured I'd raise it here first, however, it seems like a potential kernel regression issue if the only thing I'm changing is indeed the kernel version. Your input would be appreciated. I tried to figure out how to post a bug on the PPA, however, it seems bug creation is disabled on that PPA, so I ended up here.
I've been testing newer kernel versions to get fixes for other problems with my hardware. Due to another package dependency, I'm stuck on disco for some pulseaudio bluetooth codec support, so I've been pushing forward the kernel, firmware and nvidia driver versions to get the other driver fixes. I realise this is not ideal.
Changed in nvidia-graphics-drivers-440 (Ubuntu): | |
status: | Triaged → Fix Released |
Changed in nvidia-graphics-drivers-435 (Ubuntu): | |
status: | New → Confirmed |
Changed in nvidia-graphics-drivers-440 (Ubuntu): | |
status: | Fix Released → Confirmed |
Status changed to 'Confirmed' because the bug affects multiple users.