Prime Synchronization not enabled after enabling closed NVidia driver

Bug #1673194 reported by bryceadamprescott on 2017-03-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers (Ubuntu)

Bug Description

This affects all versions and derivatives of Ubuntu on any Optimus laptop running Xorg (to the best of my knowledge). Mir and Wayland don't work with closed drivers to any testable extent so it is unknown how this affects those graphical servers.

After enabling restricted/closed NVidia driver on an Optimus laptop (Intel and NVidia chips), there are terrible screen tearing issues because Prime Synchronization is not being used. An easy way to test is to enable the restricted/closed NVidia driver on an Optimus laptop and view this YouTube video in full screen: screen tearing test:

Prime Synchronization has been possible since NVidia 370.23 ( It, unfortunately, requires some manual setup. Since Ubuntu is famous for its automagic, and the restricted/closed driver tool does automation anyways, it would be nice for this to be enabled/setup automatically when a user enables the NVidia driver. The consequences of not doing this are horrendous because it makes Ubuntu (and Linux in general) look bad visually when compared to Windows.

I have been able to get Prime Synchronization setup and working using drivers downloaded from and manually changing xorg.conf and Grub. I haven't been able to get this working on Ubuntu (not sure why) but I can get it working on Fedora (blasphemy!).

I've attached some files for research purposes. I'll try making a legit patch if I have time and can figure it out.

You'll notice nvidia-drm.modeset=1 added on the command line Linux line

description: updated
description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers