Actually, maybe those other DMs don't run as root. My memory is failing.
So again maybe we do want a similar workaround in gdm3. But that doesn't
seem to be the root cause of the bug.
** Changed in: gdm3 (Ubuntu)
Status: Invalid => Opinion
** No longer affects: mutter (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu.
https://bugs.launchpad.net/bugs/1716857
Title:
nvidia-drm.modeset=1 results in no monitors detected by Xorg
Status in gdm3 package in Ubuntu:
Opinion
Status in nvidia-graphics-drivers-375 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
Confirmed
Bug description:
Context:
17.10 development packages, nvidia binary driver 375, modeset=1 for the
nvidia driver.
ubuntu desktop (gnome shell), fresh install
ThinkPad W520 in Nvidia Optimus bios mode.
Nvidia profile.
Result:
no external monitors are detected.
xrandr does not even list them as disconnected (normally it would list five
external disconnected monitors)
lsmod
shows that nvidia driver is loaded
and the modesetting is working at some level because there is no tearing on
the laptop panel
Note: modeset=1 is the only way to get flicker-free graphics on the laptop
panel. modeset=1 is not the default setting but it is highly desirable.
It works if lightdm is used which is why I have reported this against gdm3
My sessions in this configuration have mostly crashed after a few minutes
with a gdm3 fail whale message in syslog but nothing else looks interesting.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
