Being duped here with a more specific bug, i.e
19.10
optimus hardware
No login to ubuntu session possible with gdm, lightdm is ok
Maybe a few comments.
This bug orig. suggests that one could actually login on optimus hardware with
nvidia-drm.modeset=1 thru gdm. That was once the case, it no
In isolation I don't think it's correct to say that Wayland sessions
have "no external monitors". Wayland sessions do work with external
monitors on the Nvidia driver if you have nvidia-drm.modeset=1. I've
confirmed this on a desktop at least.
It sounds like you're describing some other
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
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
> 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?)
I don't understand the question, sorry. The statement "it won't work" is
wrong. Wayland does work. This bug is about
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,
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.
What we know about this bug is that gdm3, nvidia and modeset=1 is broken
under configurations which are not broken when sddm and lightdm are
used.
we know that gdm3 sessions with external monitors work with root
permissions.
we know that gdm3 compiled with wayland also works (according to the
"gdm3 compile without wayland", I meant
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1716857
Title:
nvidia-drm.modeset=1 results in no monitors detected by Xorg
To manage
Nvidia 430.26 behaves a bit differently. It just fails to start as non-
root and gives reasons:
[ 897.467] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not
permitted)
...
[ 897.470] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please
see the
[ 897.470] (EE)
User generix reports that when gdm3 is compiled without wayland support,
this bug is not seen.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1716857
Title:
nvidia-drm.modeset=1
I posted here:
https://devtalk.nvidia.com/default/topic/1055528/linux/nvidia-driver-in-
modeset-1-requires-root-permissions-daniel-van-vugt-canonical-concludes-
it-is-an-nvidia-bug/?offset=3#5351122
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** No longer affects: gdm3 (Debian)
** Tags added: eoan
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1716857
Title:
nvidia-drm.modeset=1 results in no monitors detected by Xorg
I will post your findings to the nvidia developers forum.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1716857
Title:
nvidia-drm.modeset=1 results in no monitors detected by Xorg
Not yet. I am just untangling more Nvidia bugs today.
Also, I forgot to mention that you CAN run Xorg+Nvidia and see your
monitors as non-root. But only after you have started and stopped Xorg
as root beforehand. Something gets remembered, maybe in $HOME somewhere?
--
You received this bug
Also, it sounds like the root cause here is the same as bug 1769857.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1716857
Title:
nvidia-drm.modeset=1 results in no monitors
Hi Daniel, thanks for not forgetting about this, unlike everyone else :)
Have you communicated this observation to Nvidia at all?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
For a full list of reasons to not use nvidia-drm.modeset=1 right now, please
see:
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=nvidia-drm.modeset
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
18 matches
Mail list logo
