[Bug 1227068] New: [Wayland] Internal display (eDP) stopped working, only external (HDMI) works
https://bugzilla.suse.com/show_bug.cgi?id=1227068 Bug ID: 1227068 Summary: [Wayland] Internal display (eDP) stopped working, only external (HDMI) works Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs@suse.de Reporter: burnus@gmx.de QA Contact: sndirsch@suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 875706 --> https://bugzilla.suse.com/attachment.cgi?id=875706&action=edit "wayland-info" output This is on a Lenovo ThinkPad P1 Gen6 with an Intel i7-13800H (→ "i915"/"xe" GPU driver) + Nvidia RTX A1000 6GB Laptop with nvidia-open-driver-G06 ... 550.90.07. After today's update: under Wayland, the internal laptop monitor (eDP) stopped working. Tried with "Plasma (Wayland)" and "GNOME (Wayland)". Under X11, only the internal monitor is visible. I don't know whether that's a regression or was the case before. (I had issues with the proprietary Nvidia driver in the past in this regard: it either only supported the internal one or either the internal or the external; fixed by using the open-kernels driver; cf. bug #1226116). To be precise: Last reboot was June 20 , last kdm re-login last Monday (after first Plasma 6.1 install). Today, Qt 6.7.1, some KDE and a few others (Mesa/Vulcan packages) were installed and the system rebooted. * * * As the issue shows up with KDE and GNOME under Wayland, it seems to be unrelated to the Qt and KDE/Plasma updates. Some of today's RPMs (rpm -qa --last), I hope I haven't missed some crucial package but due to Qt6.7.1 and KDE Framework/Plasma update, the list is rather long - and Qt and KDE have Wayland components. kwayland6-6.1.0-1.2.x86_64 Wed Jun 26 10:56:45 2024 xwaylandvideobridge-0.4.0+git12-3.5.x86_64 Wed Jun 26 10:54:26 2024 libOSMesa8-32bit-24.1.2-382.1.x86_64 Wed Jun 26 10:56:47 2024 libOSMesa8-24.1.2-382.1.x86_64 Wed Jun 26 10:56:47 2024 libQt6WaylandEglCompositorHwIntegration6-6.7.2-1.1.x86_64 Wed Jun 26 10:54:12 2024 Mesa-libva-24.1.2-382.1.x86_64 Wed Jun 26 10:50:33 2024 libvulkan_intel-24.1.2-382.1.x86_64 Wed Jun 26 10:50:31 2024 libvdpau_nouveau-24.1.2-382.1.x86_64 Wed Jun 26 10:50:31 2024 Mesa-vulkan-device-select-24.1.2-382.1.x86_64 Wed Jun 26 10:50:21 2024 Mesa-libglapi0-32bit-24.1.2-382.1.x86_64 Wed Jun 26 10:50:21 2024 Mesa-libglapi0-24.1.2-382.1.x86_64 Wed Jun 26 10:50:20 2024 * * * * Looks fine initially (kdm) but after login (KDE with Wayland), the internal laptop screen is black, but an external screen (HDMI) works - using ALT-CTRL-F... it is possible to change to the terminal or (F2) the used KDM login screen - all of those are shown on the the internal laptop monitor, only. $ kscreen-doctor -o Output: 1 HDMI-A-1 enabled connected priority 1 HDMI Modes: 0:1920x1080@60*! [...] i.e. the internal screen is not seen. * When choosing Plasma X11 instead of Wayland, only the internal monitor works, the external one does not even show up i.e.: $ xrandr Screen 0: minimum 320 x 200, current 2560 x 1600, maximum 16384 x 16384 eDP-1 connected primary 2560x1600+0+0 (normal left inverted right x axis y axis) 344mm x 215mm ... $ kscreen-doctor -o Output: 66 eDP-1 enabled connected priority 1 Panel Modes: 68:2560x1600@165*! [...] While HWINFO sees both: # hwinfo --monitor 31: None 00.0: 10002 LCD Monitor Model: "22FHD_LCD_TV" Vendor: VES Device: eisa 0x3700 "22FHD_LCD_TV" ... Resolution: 1920x1080@60Hz ... Detailed Timings #0: Resolution: 1920x1080 Horizontal: 1920 2448 2492 2640 (+528 +572 +720) +hsync Vertical: 1080 1084 1089 1125 (+4 +9 +45) +vsync Frequencies: 148.50 MHz, 56.25 kHz, 50.00 Hz ... Detailed Timings #1: Resolution: 1920x1080 Horizontal: 1920 2008 2052 2200 (+88 +132 +280) +hsync Vertical: 1080 1084 1089 1125 (+4 +9 +45) +vsync Frequencies: 148.50 MHz, 67.50 kHz, 60.00 Hz Driver Info #0: Max. Resolution: 1920x1080 Vert. Sync Range: 48-62 Hz Hor. Sync Range: 15-70 kHz Bandwidth: 148 MHz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #11 (VGA compatible controller) 32: None 00.0: 10002 LCD Monitor ... Model: "BOE CQ LCD Monitor" Vendor: BOE "BOE CQ" Device: eisa 0x0ae0 Serial ID: "0" Resolution: 2560x1600@60Hz Size: 344x215 mm ... Detailed Timings #0: Resolution: 2560x1600 Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync Vertical: 1600 1603 1609 1732 (+3 +9 +132) +vsync Frequencies: 282.67 MHz, 103.92 kHz, 60.00 Hz Driver Info #0: Max. Resolution: 2560x1600 Vert. Sync Range: 60-165 Hz Hor. Sync Range: 31-31 kHz Bandwidth: 282 MHz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #25 (VGA compatible controller) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1227068 https://bugzilla.suse.com/show_bug.cgi?id=1227068#c1 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(burnus@gmx.de) CC| |burnus@gmx.de Priority|P5 - None |P3 - Medium Assignee|gfx-bugs@suse.de |sndirsch@suse.com Status|NEW |IN_PROGRESS --- Comment #1 from Stefan Dirsch <sndirsch@suse.com> --- Let's begin with X11. Please provide the output of glxinfo -B Also attach ~/.local/share/xorg/Xorg.0.log (if the time stamp is related to the current Xsession start). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1227068 https://bugzilla.suse.com/show_bug.cgi?id=1227068#c2 --- Comment #2 from Stefan Dirsch <sndirsch@suse.com> --- Also provide the output of lsmod | grep nvidia -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1227068 https://bugzilla.suse.com/show_bug.cgi?id=1227068#c3 --- Comment #3 from Stefan Dirsch <sndirsch@suse.com> --- I believe for X11 external output you need suse-prime on your laptop. So check that. prime-select get-current If it isn't configured any longer - for whatever reasons - you need to run (again).. prime-select nvidia and then restart your Xsession. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1227068 https://bugzilla.suse.com/show_bug.cgi?id=1227068#c4 Tobias Burnus <burnus@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(burnus@gmx.de) | --- Comment #4 from Tobias Burnus <burnus@gmx.de> --- Created attachment 875709 --> https://bugzilla.suse.com/attachment.cgi?id=875709&action=edit 'glxinfo -B' / 'lsmod | grep nvidia' | + after 'prime-select nvidia': glxinfo -B
Let's begin with X11.
For which I have less data as I used Wayland lately - and usually without any external screen.
prime-select get-current
# /usr/sbin/prime-select get-current No driver configured. # prime-select nvidia nvidia catched Preparing first configuration NVIDIA modules are loaded Logout to switch graphics → And, indeed, after the login, switching between the external display and the internal one works (again? now?). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1227068 https://bugzilla.suse.com/show_bug.cgi?id=1227068#c5 Tobias Burnus <burnus@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #5 from Tobias Burnus <burnus@gmx.de> --- Trying with *Wayland* after that change: When kdm has been started without the external screen, i.e. it is only displayed on the laptop, it is as above: Wayland only has the external screen. When kdm has been started with both screens available, i.e. showing the enter-password login on both screens, it shows the startup wheel on the external screen and then everything gets black and an oversized mouse pointer is visible that can be moved between external and internal screen; it looks okay in terms of right/left; at least on the higher-res laptop screen, the stops half way to the top and it looks as if one can move is far below the visible screen to the bottom, but I might have missed to spot tip of the mouse pointer at the bottom of the screen. – As the keyboard didn't seem to work, I had I rebooted with SysRq + s(ync),u(nmount),b(oot). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1227068 https://bugzilla.suse.com/show_bug.cgi?id=1227068#c6 --- Comment #6 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Tobias Burnus from comment #4)
Created attachment 875709 [details] 'glxinfo -B' / 'lsmod | grep nvidia' | + after 'prime-select nvidia': glxinfo -B
Looks good. OpenGL renderer string: NVIDIA RTX A1000 6GB Laptop GPU/PCIe/SSE2
→ And, indeed, after the login, switching between the external display and the internal one works (again? now?).
See above. So both monitors are working now? Check with xrandr -q -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1227068 https://bugzilla.suse.com/show_bug.cgi?id=1227068#c7 --- Comment #7 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Tobias Burnus from comment #5)
Trying with *Wayland* after that change:
When kdm has been started without the external screen, i.e. it is only displayed on the laptop, it is as above: Wayland only has the external screen.
When kdm has been started with both screens available, i.e. showing the enter-password login on both screens, it shows the startup wheel on the external screen and then everything gets black and an oversized mouse pointer is visible that can be moved between external and internal screen; it looks okay in terms of right/left; at least on the higher-res laptop screen, the stops half way to the top and it looks as if one can move is far below the visible screen to the bottom, but I might have missed to spot tip of the mouse pointer at the bottom of the screen. – As the keyboard didn't seem to work, I had I rebooted with SysRq + s(ync),u(nmount),b(oot).
Ok. Not sure if I understand this all correctly. Maybe you can make a video with your smartphone - if available - to demonstrate it. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1227068 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(burnus@gmx.de) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1227068 https://bugzilla.suse.com/show_bug.cgi?id=1227068#c8 --- Comment #8 from Tobias Burnus <burnus@gmx.de> --- Created attachment 875712 --> https://bugzilla.suse.com/attachment.cgi?id=875712&action=edit [X11] xrandr -q – after 'prime-select nvidia', finding both monitors (eDP+ external) (In reply to Stefan Dirsch from comment #6)
So both monitors are working now? Check with xrandr -q
With X11 – yes :-) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1227068 https://bugzilla.suse.com/show_bug.cgi?id=1227068#c9 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #9 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Tobias Burnus from comment #8)
Created attachment 875712 [details] [X11] xrandr -q – after 'prime-select nvidia', finding both monitors (eDP+ external)
Looks good.
(In reply to Stefan Dirsch from comment #6)
So both monitors are working now? Check with xrandr -q
With X11 – yes :-)
Ok. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1227068 https://bugzilla.suse.com/show_bug.cgi?id=1227068#c10 Tobias Burnus <burnus@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(burnus@gmx.de) | --- Comment #10 from Tobias Burnus <burnus@gmx.de> --- Created attachment 875715 --> https://bugzilla.suse.com/attachment.cgi?id=875715&action=edit [Wayland] Screen cast via mobile phone [Wayland]
Ok. Not sure if I understand this all correctly. Maybe you can make a video with your smartphone - if available - to demonstrate it.
(a) [0:00] login screen only on the laptop, HDMI connected external screen. Login with Wayland – shows up on the external screen, local screen: nothing happens (X11 based login screen still shown at [Alt][Ctrl][F2]; usually the Wayland screen shows up at [F3]) (b) [0:42] Without external display – nothing happens after the login. [1:10] Trying to move the mouse or switch to the console ([Alt][Ctrl][F1]) has no effect. [1:22] Plugging-in now the monitor shows that wayland was started - and shows up there; now also using the mouse and keyboard works like it should, again. (c) [1:43] When external display is available when KDM is restarted - the login screen shows up on both screens. [2:28] When logging-in, it shows up as with (a). [2:48] Now switching to a console [Alt][Ctrl][F1] and back to [F3]: The mouse pointer now shows up on both monitors – but with black background and no key press work. The mouse pointer is also oversized. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1227068 https://bugzilla.suse.com/show_bug.cgi?id=1227068#c11 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(burnus@gmx.de) --- Comment #11 from Stefan Dirsch <sndirsch@suse.com> --- You're not really using X11 and Wayland at the same time, do you? I wouldn't know how to configure this - let a lone support it ... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1227068 https://bugzilla.suse.com/show_bug.cgi?id=1227068#c12 Tobias Burnus <burnus@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(burnus@gmx.de) | --- Comment #12 from Tobias Burnus <burnus@gmx.de> --- (In reply to Stefan Dirsch from comment #11)
You're not really using X11 and Wayland at the same time, do you? I wouldn't know how to configure this - let a lone support it ...
Well, in terms of user handling – I choose either '<Plasma|GNOME> (Wayland)' or '<Plasma|GNOME> (X11)', i.e. in that sense I only use one at a time. I was using "Plasma (Wayland)" before – and that stopped working → reason for opening this bug report. However, after it failed (eDP screen dark), I started playing around with "(X11)" instead of "(Wayland)" on the login screen and with "GNOME (Wayland)" to see whether it was a KDE/Qt library problem or a more generic one. * * * However: My impression is that the KDM uses X11 – when choosing X11, that virtual screen is also used for that purpose (virtual terminal/screen 2, i.e. what you reach via [Alt][Ctrl][F2]). Whereas when choosing Wayland, the KDM remains waiting on screen 2 state and Wayland is spawn on screen 3 ([Alt][Ctrl][F3]). But I have no idea of the inner workings of KDM/GDM/XDM nor of the current setup. * * * I wrote the following morning but it didn't came through as we had a comment-adding clash and I didn't see it as I moved to a different tab after hitting "Save Changes":
After applying today's updates to MESA (24.1.2-382; Linux kernel 6.9.6, systemd, …):
Wayland now works again. :-)
(plasmashell crashes (+ restarts) when plugging the HDMI cable, segfaulting in some libQt6Wayland*.so file but that's unrelated and doesn't block working.) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1227068 https://bugzilla.suse.com/show_bug.cgi?id=1227068#c13 --- Comment #13 from Stefan Dirsch <sndirsch@suse.com> --- Ah. Ok. So sddm runs on an Xserver before starting a Wayland session. So you can switch between Wayland session and sddm login screen with [Ctrl][Alt][Fx] and [Fy]. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1227068 https://bugzilla.suse.com/show_bug.cgi?id=1227068#c14 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(burnus@gmx.de) --- Comment #14 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Tobias Burnus from comment #12)
I wrote the following morning but it didn't came through as we had a comment-adding clash and I didn't see it as I moved to a different tab after hitting "Save Changes":
After applying today's updates to MESA (24.1.2-382; Linux kernel 6.9.6, systemd, …):
Wayland now works again. :-)
(plasmashell crashes (+ restarts) when plugging the HDMI cable, segfaulting in some libQt6Wayland*.so file but that's unrelated and doesn't block working.)
So thinks are working now and we can close this ticket. Or do I misunderstand that? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1227068 https://bugzilla.suse.com/show_bug.cgi?id=1227068#c15 Tobias Burnus <burnus@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #15 from Tobias Burnus <burnus@gmx.de> ---
So thinks are working now and we can close this ticket. Or do I misunderstand that?
Yes. Seemingly one of the last changes (MESA?) caused the regression and a follow-up change (in that package or another one) fixed it. -> CLOSE as FIXED. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1227068 Tobias Burnus <burnus@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(burnus@gmx.de) | -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1227068 https://bugzilla.suse.com/show_bug.cgi?id=1227068#c16 --- Comment #16 from Stefan Dirsch <sndirsch@suse.com> --- Ok. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com