https://bugs.kde.org/show_bug.cgi?id=478616
--- Comment #6 from Stefan Hoffmeister <stefan.hoffmeis...@econos.de> ---
It appears as if - somehow - this is indeed related to the NVIDIA driver "being
around".
With all prior changes reverted and only the following changes on place, I now
again get reliable boots into a KDE Plasma graphical user interface:
* blacklist modules nvidia, nvidia-drm, nvidia-modeset, nvidia-uvm
("/etc/modprobe.d/nvidia-blacklist.conf")
* dracut blacklist the above modules
("/lib/dracut/dracut.conf.d/99-nvidia-dracut.conf")
* set module parameter "options nvidia_drm fbdev=0"
("/etc/modprobe.d/nvidia_drm.conf") - this is somewhat pointless given that the
module is blacklisted, but on my system I will never need an NVIDIA framebuffer
* mask falling back to the nouveau driver ("systemctl mask
nvidia-fallback.service")
The net effect of this is that "lsmod | grep -E '^(nvidia|nouveau)'" will
return only
```
nvidia_uvm 3522560 0
nvidia 62394368 9 nvidia_uvm
```
which _disables_ the complete graphics stack (including NVIDIA Prime with
OpenGL / Vulkan), but which _retains_ the ability run NVIDIA CUDA processing
loads (I cannot explain at this time where nvidia_uvm actually gets loaded).
There also seems to have been some kind of interaction with multiple screens
attached (all of them attached to the Intel GPU, though!) - booting with a
single screen seems to have always worked.
FWIW, I do not have a GNOME installation on this box, so I am unable to tell
whether this would be affected as well; by the look-and-feel of everything, I
would suspect that GNOME would suffer from exactly the same problems.
--
You are receiving this mail because:
You are watching all bug changes.
