I’m having trouble with the NVIDIA driver again after the last Tubleweed update. The system no longer starts into the graphics mode.
According to my research so far, there are various reasons why the graphics system does not start. Incompatibility of proprietary driver and kernel, X11/Xwayland, BIOS signature etc. How can I at least narrow down the error?
There is a lengthy thread about a similar GPU https://forums.opensuse.org/t/re-install-old-kernel-default/178626
Looks like the G5 470.xx driver has trouble with the latest kernels.
You may completely uninstall the proprietary driver if you can afford running on the nouveau oss driver. Or wait here for a better advice.
Are you sure that this is the problem in my case? How can I distinguish between the various known problems?
How do I start the nouveau driver? I only use the PC for office work and videos, but not for games. Can I try and see if I can get along with the nouveau driver?
That says that no driver is currently engaged (driver:N/A) for whatever reason and that an alternate driver (nouveau) is available, but not loaded since it is blacklisted since the proprietary driver is installed.
I cannot tell for sure why the Nvidia driver is not loaded, but if you need your pc ASAP I think that completely uninstalling Nvidia is a viable solution for office work.
Are there instructions somewhere on how I can switch to the nouveau driver, since it apparently is already installed. That way I could try it out and maybe that would be enough for me. Then I would finally be rid of the everlasting trouble with the proprietary Nvidia driver.
Nouveau is already installed with the kernel, but installing the proprietary driver blacklists it to avoid conflicts. To use nouveau you must uninstall the Nvidia driver using (in reverse) the same method you used for installing it, see SDB:NVIDIA and write back if something is still not clear.
Okay! I uninstalled “nvidia-computeG05 (32 bit)”, “nvidia-glG05 (32 bit)”, “x11-video-nvidiaG05 (32 bit)” and “nvidia-gfxG05-kmp-default” with yast2. After a restart, the start screen was displayed with a higher resolution, but the graphics mode was not started. I ended up back at the console login prompt. But I was able to start X via the command “startplasma-wayland”. So the graphics mode works. Great and thank you so far.
Any last tips on how I can get the system to automatically boot into graphics mode like it did before?
I did so in the mean time. Everthing seemed to run well. System does not start into graphics mode, though. I attach the output from inxi -GSaz one more.
Instead of startplasma-wayland, see what sudo systemctl status xdm reports, then try sudo systemctl restart xdm, and startplasma-wayland only if SDDM didn’t just start. Then when Konsole is running, show us input/output from grep dev/dr /var/log/Xorg.0.lo*. If there is a not found or no output, try sudo journalctl -b | grep -C3 dev/dr.
systemctl restart xdm does nothing. The command simply returns to the prompt. Please find enclosed the output of " systemctl status xdm" and " journalctl -b | grep -C3 dev/dr".
–
● display-manager.service - X Display Manager
Loaded: loaded (/usr/lib/systemd/system/display-manager.service; enabled; preset: enabled)
Active: active (running) since Wed 2024-10-09 18:19:33 CEST; 18min ago
Invocation: 472b0b6672554792a7533fb8ba0c6640
Process: 2125 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=0/SUCCESS)
Main PID: 2161 (sddm)
Tasks: 2 (limit: 18916)
CPU: 51ms
CGroup: /system.slice/display-manager.service
└─2161 /usr/bin/sddm
Oct 09 18:19:33 drei sddm[2161]: Loaded empty theme configuration
Oct 09 18:19:33 drei sddm[2161]: Xauthority path: "/run/sddm/xauth_fnwzDb"
Oct 09 18:19:33 drei sddm[2161]: Using VT 2
Oct 09 18:19:33 drei sddm[2161]: Display server starting...
Oct 09 18:19:33 drei sddm[2161]: Writing cookie to "/run/sddm/xauth_fnwzDb"
Oct 09 18:19:33 drei sddm[2161]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_fnwzDb -noreset -displayfd 16
Oct 09 18:19:33 drei sddm[2161]: Failed to read display number from pipe
Oct 09 18:19:33 drei sddm[2161]: Display server stopping...
Oct 09 18:19:33 drei sddm[2161]: Attempt 1 starting the Display server on vt 2 failed
Oct 09 18:19:33 drei systemd[1]: Started X Display Manager.
–
Oct 09 18:20:56 XXXX systemd[1]: Started Disk Manager.
Oct 09 18:20:56 XXXX udisksd[2497]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Oct 09 18:20:56 XXXX systemd[1]: Starting Daemon for power management...
Oct 09 18:20:56 XXXX kwin_wayland[2465]: kwin_wayland_drm: drmSetClientCap for Atomic Mode Setting failed. Using legacy mode on GPU "/dev/dri/card0"
Oct 09 18:20:56 XXXX systemd[1]: Started Daemon for power management.
Oct 09 18:20:56 XXXX kwin_wayland[2465]: could not create a component for "krunner.desktop"
Oct 09 18:20:56 XXXX baloo_file[2464]: QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.46'
--
Oct 09 18:39:07 XXXX systemd[2298]: Started sandboxed app permission store.
Oct 09 18:39:07 XXXX systemd[2298]: Started flatpak document portal service.
Oct 09 18:39:07 XXXX kwin_wayland[4980]: No backend specified, automatically choosing drm
Oct 09 18:39:07 XXXX kwin_wayland[4980]: kwin_wayland_drm: drmSetClientCap for Atomic Mode Setting failed. Using legacy mode on GPU "/dev/dri/card0"
Oct 09 18:39:07 XXXX kwin_wayland[4980]: could not create a component for "krunner.desktop"
Oct 09 18:39:08 XXXX kcminit_startup[4986]: Initializing "/usr/lib64/qt6/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Oct 09 18:39:08 XXXX kwin_wayland_wrapper[5037]: (WW) Option "-listen" for file descriptors is deprecated
I don’t think they make much of a difference wrt X not starting, but:
uninstall openSUSE-repos-MicroOS-NVIDIA (it is plain wrong, you are not using MicroOS, or are you?)
I would uninstall also libnvidia-egl-wayland1 and nvidia-libXNVCtrl which have no use without the proprietary driver.
I updated to the latest kernel version 6.11.2-3.g92ca8ff-default via yast2. It suggested to install the uninstalled G5 nvidia drivers again. I accepted this proposal. After the update was done, the system not even starts into graphics mode with startplasma-wayland any more. So things are more worse than before
– startplasma-wayland –
kf.dbusaddons: Skipping syncing of environment variable "BASH_FUNC_mc%%" as name contains unsupported characters
Error: could not determine $DISPLAY.
Error: Can not contact kdeinit5!
org.kde.startup: "kdeinit5_shutdown" QList() exited with code 255
startplasma-wayland: Shutting down...
startplasmacompositor: Shutting down...
startplasmacompositor: Done.
Looks to me like nouveau and your 10de:128b GPU should not be issues. My GK208B/GT 720/10de:1288 works just fine, though I use neither SDDM nor Plasma6 nor Wayland:
