[Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
Jean-Pierre van Riel
1716857 at bugs.launchpad.net
Sun May 3 13:15:12 UTC 2020
Hi, thanks to everyone, especially Daniel for unpacking this issue.
I have had a very similar issue, where gnome shell fails to run my
external 4K/UHD display at 60HZ and I see the following failure loop
triggered in `journalctl -b -p warning _COMM=gnome-shell`:
May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to blit shared framebuffer: EGL failed to allocate resources for the requested operation.
May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to set CRTC mode 3840x2160: No such file or directory
May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to flip: Device or resource busy
May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to set CRTC mode 3840x2160: No such file or directory
May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to blit shared framebuffer: EGL failed to allocate resources for the requested operation.
May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to set CRTC mode 3840x2160: No such file or directory
May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to blit shared framebuffer: EGL failed to allocate resources for the requested operation.
May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to set CRTC mode 3840x2160: No such file or directory
...
While not sure it's exactly the same, it should still inform the
overall discussion about dealing with GDM3 + Mutter + proprietary Nvidia
drivers modeset problems.
To summarise and share my experience of it on a Lenovo P53 and some
quirks/workarounds:
- `sudo ubuntu-drivers autoinstall` got Nvidia 440.59 drivers installed.
- However, Nvidia modeset was not enabled as yet.
$ sudo cat /sys/module/nvidia_drm/parameters/modeset
N
-
- Using prime-select
- For laptops like mine, seems the external port is connected to the Nvidia GPU.
- Using the proprietary Nvidia drivers seems to then bump into a
** Attachment added: "gnome-shell_journal_warnings_egl_resource_failed.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+attachment/5365716/+files/gnome-shell_journal_warnings_egl_resource_failed.txt
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1716857
Title:
nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external
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
Status in nvidia-graphics-drivers-430 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
Confirmed
Status in systemd 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
More information about the foundations-bugs
mailing list