I would appreciate any help on re-establishing the visibility of the login screen … I am really happy with TW kernel 5.15 on my new computer … all the newest Intel hardware works really well … a sound issue I initially had is fully resolved … there is just one minor thing … in booting in the initial login screen (where we choose Wayland etc and enter the password) is blank … so I type the password and keep my fingers crossed … so far all has been good and with relief the desktop opens … however I will be in a real mess if the desktop doesn’t open … I have tried a few things that had no effect (like Yast bootloader refresh) so would appreciate help to re-establish this login screen if possible … many thanks!
Something to try at the black screen, twice in quick succession: Ctrl-Alt-BS
Something else to try: switch to a different display manager:
sudo update-alternatives --config default-displaymanager
Thanks mrmazda … this seems to result in a display manager restart but only returns to the black screen.
Something else to try: switch to a different display manager:
sudo update-alternatives --config default-displaymanager
This has caused me huge issues. Now I can only log in occasionally using a snapshot. First I set the display manager to xdm and then could not get through the black login screen. Changing back to sddm auto had the same result of a black screen that wouldn’t accept my password. Also setting sddm manual had the same result. I’m back to ssdm auto and can only login through snapshots and entering my password into the black screen. Also, formerly when I exited a desktop session I saw the proper login screen, now I only see the black screen when I log out. So I’m in quite a bind now.
I’ve recovered to the point that I can at least log in through the black screen again … not sure what go me back to this point as I reinstalled all sddm, xdm & all kernel.
Video card/driver???
Please post content of /etc/X11/xorg.conf.d/*intel.conf if such exists.
Please post URL resulting from:
sudo cat /var/log/Xorg.0.log | susepaste
Please manage if you can to login to any GUI, then run in an X terminal
sudo inxi -CGay
and post the result. Otherwise do it from a vtty login (e.g. Ctrl-Alt-F3), if Ctrl-Alt-F3 does not also produce a black screen.
Hi gogalthorp … my NVIDIA RTX3070 seems to be operating fine but there could be a vga-type login issue … I tried nomodeset in the login parameters but this didn’t work
No files of that name … there is a 90-nvidia.conf with:
Section "ServerLayout"
Identifier "layout"
Screen "nvidia"
Inactive "intel"
Inactive "modesetting"
EndSection
Section "Screen"
Identifier "intel"
Device "intel"
EndSection
Section "Device"
Identifier "intel"
Driver "intel"
EndSection
Section "Screen"
Identifier "modesetting"
Device "modesetting"
EndSection
Section "Device"
Identifier "modesetting"
Driver "modesetting"
EndSection
Section "Screen"
Identifier "nvidia"
Device "nvidia"
EndSection
Section "Device"
Identifier "nvidia"
Driver "nvidia"
BusID "PCI:1:0:0"
Option "DPI" "96 x 96"
Option "AllowEmptyInitialConfiguration"
Option "AllowExternalGpus"
EndSection
Please post URL resulting from:
sudo cat /var/log/Xorg.0.log | susepaste
sudo cat /var/log/Xorg.0.log | susepaste
Pasted as:
https://susepaste.org/1133747
https://paste.opensuse.org/1133747
Please manage if you can to login to any GUI, then run in an X terminal
sudo inxi -CGayand post the result. Otherwise do it from a vtty login (e.g. Ctrl-Alt-F3), if Ctrl-Alt-F3 does not also produce a black screen.
I’m managing to log in through the black screen to the desktop … this is what I get from a terminal …
stuart@localhost:~> sudo inxi -CGay
**CPU:**
**Info:** 8-Core **model:** 11th Gen Intel Core i7-11800H **socket:** U3E1 **bits:** 64
**type:** MT MCP **arch:** Tiger Lake **family:** 6 **model-id:** 8D (141) **stepping:** 1
**microcode:** 34 **cache:****L2:** 24 MiB
**flags:** avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
**bogomips:** 73728
**Speed:** 796 MHz **min/max:** 800/4600 MHz **base/boost:** 2178/5000 **volts:** 0.7 V
**ext-clock:** 100 MHz **Core speeds (MHz):****1:** 796 **2:** 1032 **3:** 945 **4:** 801 **5:** 789
**6:** 800 **7:** 929 **8:** 801 **9:** 1030 **10:** 1053 **11:** 985 **12:** 845 **13:** 789 **14:** 927
**15:** 801 **16:** 910
**Vulnerabilities:****Type:** itlb_multihit **status:** Not affected
**Type:** l1tf **status:** Not affected
**Type:** mds **status:** Not affected
**Type:** meltdown **status:** Not affected
**Type:** spec_store_bypass
**mitigation:** Speculative Store Bypass disabled via prctl and seccomp
**Type:** spectre_v1
**mitigation:** usercopy/swapgs barriers and __user pointer sanitization
**Type:** spectre_v2 **mitigation:** Enhanced IBRS, IBPB: conditional, RSB filling
**Type:** srbds **status:** Not affected
**Type:** tsx_async_abort **status:** Not affected
**Graphics:**
**Device-1:** Intel TigerLake-H GT1 [UHD Graphics] **vendor:** CLEVO/KAPOK
**driver:** i915 **v:** kernel **bus-ID:** 00:02.0 **chip-ID:** 8086:9a60 **class-ID:** 0300
**Device-2:** NVIDIA GA104M [GeForce RTX 3070 Mobile / Max-Q]
**vendor:** CLEVO/KAPOK **driver:** nvidia **v:** 470.86 **alternate:** nouveau,nvidia_drm
**bus-ID:** 01:00.0 **chip-ID:** 10de:249d **class-ID:** 0300
**Device-3:** Acer BisonCam NB Pro **type:** USB **driver:** uvcvideo **bus-ID:** 3-8:3
**chip-ID:** 5986:9102 **class-ID:** 0e02
**Display:****server:** X.org 1.21.1.1 **compositor:** kwin_x11 **driver:**
**loaded:** modesetting,nvidia **alternate:** intel **tty:** 178x26
**Message:** Advanced graphics data unavailable in console for root.
… appreciate your help mrmazda!
Until seeing your inxi -G, we didn’t know you have an Optimus configuration, which is frequently quite troublesome to get configured satisfactorily. I don’t have that, so don’t recognize everything that shows up in your Xorg.0.log. There could be a clue(s) there, but I don’t recognize any.
Optimus users usually need to use suse-prime. Are you doing that?
Something else to try: rename 90-nvidia.conf to 90-nvidia.con or 90-nvidia.conf.bak so that it does not get used, then restart X.
Another else: try adding i915.modeset=0 to your kernel command line (the linu line in Grub after striking the E key at the Grub menu). If this works you can make it permanent by adding it to /etc/default/grub and running grub2-mkconfig -o /boot/grub2/grub.cfg as root or with sudo or su -.
Hi
Is the system a Laptop or Desktop?
Hi … laptop
Hi
So suse-prime as indicated, there should be no need for any xorg.conf file. Have a read https://en.opensuse.org/SDB:NVIDIA_SUSE_Prime
On a previous laptop using 15.3 I’ve been a regular user of prime-select. However under TW it hasn’t worked … I’ve wondered if this is maybe because I have a AMOLED screen … also bbswitch rpm is installed but as you can see below not recognised in prime-select … and I now see in https://en.opensuse.org/SDB:NVIDIA_SUSE_Prime that prime-select doesn’t work with Wayland (although TW is Plasma-Wayland so i’m not sure about this)
sudo prime-select get-current
No driver configured.
NVIDIA/Intel video card selection for NVIDIA Optimus laptops.
bbswitch module not found. NVIDIA card will not be powered off
Something else to try: rename 90-nvidia.conf to 90-nvidia.con or 90-nvidia.conf.bak so that it does not get used, then restart X.
Another else: try adding i915.modeset=0 to your kernel command line (the linu line in Grub after striking the E key at the Grub menu). If this works you can make it permanent by adding it to /etc/default/grub and running grub2-mkconfig -o /boot/grub2/grub.cfg as root or with sudo or su -.
Thanks … I will try these things now
Thanks Malcolm
No effect using …
i915.modeset=0
Renaming 90-nvidia.conf has some success but also some issues … firstly happy success in that the login screen now appears … albeit in very small font … negative is that the NVIDIA management panel no longer works and there has been window resizing and tiny cursor on the desktop … so I’m not sure which driver is being used … although “prime-select get-current” still says “NVIDIA card will not be powered off” … I wonder if the next NVIDIA rpm update will reestablish 90-nvidia.conf … also I’m now experiencing something like kernel panic which may or not may not be related
Hi
I suspect the nvidia rpm as well as kernel updates. I use the run file here for that very reason, but my nvidia card is a physical one in this desktop and just use offload.
I think you need to look at the steps in the wiki article…
Malcolm … thanks, success with login screen using “prime-select offload” … I reestablished /etc/x11/xorg.conf.d/90-nvidia.conf … then worked through the Wiki steps as you suggested … tried “prime-select offload” … logged out & in … noted Intel now being used
glxinfo | grep 'OpenGL renderer string'
OpenGL renderer string: Mesa Intel(R) UHD Graphics (TGL GT1)
… rebooted and had login screen … noted that prime-select now says driver is offload, however bbswitch is still not found (despite bbswitch-kernel-kmp being installed) and that the NVIDIA card is not powered off (I don’t know if that is important) …
sudo prime-select get-current
Driver configured: offload
bbswitch module not found. NVIDIA card will not be powered off
… I further experimented by using prime-select to switch back to nvidia … logged out and in … checked nvidia was the driver … rebooted and experienced the black login screen again … entered password to run desktop and used prime-select to switch back to offload … again rebooted and login screen was available once more … so it looks like the offload driver is required for now rather than nvidia … until the issue is fixed in either the kernel or nvidia drivers … thanks again for your help Malcolm and mrmazda
Hi
The bbswitch package and kmp are (AFAIK) deprecated and can be removed (I’d lock as well)… as long as you used suse-prime in the past and all was good(?).
Malcolm … removed these bbswitch packages and all ok … I find the offload graphics a bit ugly compared to nvidia … so now we’ve found the fix I’m going to keep using nvidia and hope that an update fixes the black screen issue in the near future