Re: [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
just one last thing, possibly you are not aware that 19.04 Ubuntu wayland sessions have exactly the same problem: no external monitors. While this bug refers to Xorg, the problem is not limited to Xorg. At least on my Optimus laptop. And when I use its multiplexor to go into pure Nvidia mode, no monitors work, not even the laptop panel. On Fri, 21 Jun 2019 at 12:50, Daniel van Vugt wrote: > 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 subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1716857 > > Title: > nvidia-drm.modeset=1 results in no monitors detected by Xorg > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions > -- Tim Richardson -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
I think his point was to isolate the problem as being gdm3's wayland code. If you need modeset=1 for wayland, then why is there any effort to support nvidia and wayland under gnome, since it won't work (or are only optimus systems affected by this?) my point was that you marked this as invalid, but the only way to avoid this bug is to avoid using gdm3. You don't have to change anything else. So it looks like a gdm3 bug. On Fri, 21 Jun 2019 at 11:50, Daniel van Vugt wrote: > Compiling gdm3 without wayland isn't a fix. It's a workaround, and kind > of pointless. It's pointless because the most common reason for using > nvidia-drm.modeset=1 is to get Wayland support. I know there are other > reasons for wanting nvidia-drm.modeset=1 such as avoiding tearing in > PRIME setups. But mostly if people use modeset=1 it is to get Wayland > support. > > If we can't get a fix from Nvidia then some kind of workaround that runs > Xorg as root (like comment #26) is probably the next best option. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1716857 > > Title: > nvidia-drm.modeset=1 results in no monitors detected by Xorg > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions > -- Tim Richardson -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
