[Desktop-packages] [Bug 1673194] [NEW] Prime Synchronization not enabled after enabling closed NVidia driver
Public bug reported: 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: https://www.youtube.com/watch?v=5xkNy9gfKOg. Prime Synchronization has been possible since NVidia 370.23 (https://devtalk.nvidia.com/default/topic/957814/linux/prime-and-prime- synchronization/). 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 www.nvidia.com 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. ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: nvidia ** Attachment added: "Manual Xorg setup" https://bugs.launchpad.net/bugs/1673194/+attachment/4838383/+files/xorg.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1673194 Title: Prime Synchronization not enabled after enabling closed NVidia driver Status in nvidia-graphics-drivers package in Ubuntu: New 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: https://www.youtube.com/watch?v=5xkNy9gfKOg. Prime Synchronization has been possible since NVidia 370.23 (https://devtalk.nvidia.com/default/topic/957814/linux/prime-and- prime-synchronization/). 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 www.nvidia.com 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1673194/+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
[Desktop-packages] [Bug 1673194] Re: Prime Synchronization not enabled after enabling closed NVidia driver
You'll notice nvidia-drm.modeset=1 added on the command line Linux line ** Attachment added: "Altered grub" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1673194/+attachment/4838384/+files/grub ** Description changed: This affects all versions and derivatives of Ubuntu on any Optimus - laptop (to the best of my knowledge). + 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: https://www.youtube.com/watch?v=5xkNy9gfKOg. Prime Synchronization has been since NVidia 370.23 (https://devtalk.nvidia.com/default/topic/957814/linux/prime-and-prime- synchronization/). 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 www.nvidia.com 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. ** Description changed: 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: https://www.youtube.com/watch?v=5xkNy9gfKOg. - Prime Synchronization has been since NVidia 370.23 + Prime Synchronization has been possible since NVidia 370.23 (https://devtalk.nvidia.com/default/topic/957814/linux/prime-and-prime- synchronization/). 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 www.nvidia.com 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 received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1673194 Title: Prime Synchronization not enabled after enabling closed NVidia driver Status in nvidia-graphics-drivers package in Ubuntu: New 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: https://www.youtube.com/watch?v=5xkNy9gfKOg. Prime Synchronization has been possible since NVidia 370.23 (https://devtalk.nvidia.com/default/topic/957814/linux/prime-and- prime-synchronization/). 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
[Desktop-packages] [Bug 1671799] Re: FFe: xserver 1.19.x
Tested on Lenovo Yoga 20FY that has an Optimus setup (Intel HD 520 and Nvidia 540M Card). Used Ubuntu 17.04 daily and added PPA: https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging. Test 1 - No restricted/closed drivers Upgrade worked with no packages broken, etc.. Unfortunately, Ubuntu will not boot after doing this and just hangs forever. Test 2 - Enable restricted/closed NVidia driver (and Intel microcode if it matters) BEFORE PPA Upgrade worked with no packages broken, etc.. Ubuntu was able to boot and I was able to login. There didn't seem to be any obvious problems with the graphics stack at this point. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1671799 Title: FFe: xserver 1.19.x Status in xorg-server package in Ubuntu: Confirmed Bug description: xserver 1.19 has been out for quite some time now, and xmir has been recently ported to it so we can push 1.19 to zesty now. It's currently being staged on a ppa: https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging This bugreport is for testing feedback. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799/+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
