You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a Dell D6000 docking station connected to my Lenovo Legion 5 Pro laptop. Everything works (keyboard & mouse through usb, ethernet), but my monitors do not display anything on Wayland. Connecting the cable turns on the monitor but then it goes to standby because it gets 'No signal'.
On X11, everything works fine. On Windows too.
dmesg logs when reconnecting an HDMI 1920x1080@60 monitor to my dock on Wayland, with evdi verbose logging (level 6) (disconnecting, waiting a couple seconds, then reconnecting again): evdi-wayland.log. Reconnection happens between the empty lines I added.
dmesg logs when reconnecting (same thing as above) on X11: evdi-xorg.log. I left some newlines on lines 63-67 to show where I reconnected.
Xrandr output on Xorg, with the monitor connected (DVI-I-1-1): xrandr-xorg.log.
I compared the logs and noticed that on Wayland, after the Edid property is set, it immediately logs evdi_user_framebuffer_destroy, evdi_painter_close, and evdi_driver_close. These logs don't occur on X when connecting the monitor.
On Wayland, the monitor (Acer, id=3, my second monitor is connected directly to my laptop and works fine) is connected properly, shows the correct size, resolution, name, etc:
But the monitor doesn't get a signal.
I also notice that when I use the nouveau drivers instead of the proprietary Nvidia drivers, the monitor does get a signal, but only shows the cursor, the background is black and I can't move windows to the monitor. Either way, using nouveau isn't an option, as I'm planning to use this dock on Hyprland, and play games: both of which aren't great with nouveau. But this info might be useful to determine the cause.
Let me know if you need any other logs.
The text was updated successfully, but these errors were encountered:
Seems it happens due to the combination Nvidia + Wayland: I see the same behaviour on KDE + Wayland and on Hyprland when using Nvidia, but when running them on my AMD Integrated GPU it works fine. My other laptop with Intel integrated GPU also works fine.
Is this the right place to report this? Or should I report it to the nvidia forums?
6.8.0-40-generic
7.7+23ubuntu3
, core:21.1.12-1ubuntu1
libwayland-server0:amd64 1.22.0-2.1build1
gnome 46.0
nvidia-550
(proprietary)I have a Dell D6000 docking station connected to my Lenovo Legion 5 Pro laptop. Everything works (keyboard & mouse through usb, ethernet), but my monitors do not display anything on Wayland. Connecting the cable turns on the monitor but then it goes to standby because it gets 'No signal'.
On X11, everything works fine. On Windows too.
dmesg
logs when reconnecting an HDMI 1920x1080@60 monitor to my dock on Wayland, with evdi verbose logging (level 6) (disconnecting, waiting a couple seconds, then reconnecting again): evdi-wayland.log. Reconnection happens between the empty lines I added.dmesg
logs when reconnecting (same thing as above) on X11: evdi-xorg.log. I left some newlines on lines 63-67 to show where I reconnected.Xrandr output on Xorg, with the monitor connected (DVI-I-1-1): xrandr-xorg.log.
I compared the logs and noticed that on Wayland, after the Edid property is set, it immediately logs
evdi_user_framebuffer_destroy
,evdi_painter_close
, andevdi_driver_close
. These logs don't occur on X when connecting the monitor.On Wayland, the monitor (Acer, id=3, my second monitor is connected directly to my laptop and works fine) is connected properly, shows the correct size, resolution, name, etc:
But the monitor doesn't get a signal.
I also notice that when I use the nouveau drivers instead of the proprietary Nvidia drivers, the monitor does get a signal, but only shows the cursor, the background is black and I can't move windows to the monitor. Either way, using nouveau isn't an option, as I'm planning to use this dock on Hyprland, and play games: both of which aren't great with nouveau. But this info might be useful to determine the cause.
Let me know if you need any other logs.
The text was updated successfully, but these errors were encountered: