|
Bugzilla – Full Text Bug Listing |
| Summary: | [Wayland] Internal display (eDP) stopped working, only external (HDMI) works | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Tobias Burnus <burnus> |
| Component: | X11 3rd Party Driver | Assignee: | Stefan Dirsch <sndirsch> |
| Status: | RESOLVED FIXED | QA Contact: | Stefan Dirsch <sndirsch> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | CC: | burnus |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
"wayland-info" output
'glxinfo -B' / 'lsmod | grep nvidia' | + after 'prime-select nvidia': glxinfo -B [X11] xrandr -q – after 'prime-select nvidia', finding both monitors (eDP+ external) [Wayland] Screen cast via mobile phone |
||
|
Description
Tobias Burnus
2024-06-26 10:24:25 UTC
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). Also provide the output of lsmod | grep nvidia 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. Created attachment 875709 [details] '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?). 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). (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 (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. Created attachment 875712 [details] [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 :-) (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. Created attachment 875715 [details] [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'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 ... (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.) 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]. (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? > 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.
Ok. Thanks! |