You are not logged in.
Hi
I am unable to start an Wayland session in KDE. After I login I get a black screen with a cursor. I am using an Nvidia 4070, and I have read the Nvidia wiki page, installed the correct driver, and also set all of the options below.
In my grub config I have updated it as below to include nvidia_drm.modeset=1 nvidia-drm.fbdev=1 as below
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet nvidia_drm.modeset=1 nvidia-drm.fbdev=1"I then updated grub using
grub-mkconfig -o /boot/grub/grub.cfgI have created a file at /etc/modprobe.d/nvidia.conf with the line
options nvidia_drm modeset=1In /etc/mkinitcpio.conf I have set the modules and hooks as below
MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)
HOOKS=(base udev autodetect microcode modconf keyboard keymap consolefont block filesystems fsck)When I run `sudo cat /sys/module/nvidia_drm/parameters/modeset1 it outputs Y
However after rebooting whenever I try and login to a Wayland session, after entering my password I just get a black screen with the cursor. I can login to an X11 sesion ok.
My logs are below. I did notice a few repeating lines such as below
Jul 04 17:09:09 Arc kwin_wayland_wrapper[1169]: src/nv_gbm.c:123: GBM-DRV error (nv_gbm_bo_create): DRM_IOCTL_NVIDIA_GEM_ALLOC_NVKMS_MEMORY failed (ret=-1)
Jul 04 17:09:09 Arc kernel: [drm:nv_drm_gem_alloc_nvkms_memory_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000500] Failed to allocate NVKMS memory for GEM objectLogs: https://paste.mozilla.org/4CkETYy9
Thank you for any help
Last edited by Jstriker (2024-07-04 16:49:53)
Offline
Have you already seen / tried this post[?
Offline
I did just try this now, but when I set auto login for Wayland it just logged into a black screen with a cursor again, and I had to edit my sddm config file to disable auto login and after rebooting I got the normal login page again, and I could login into an X11 session.
Offline
These error messages mean your GPU is crashing, the most harmless variation of this is it's simply not seated correctly, could also be a driver bug, which connector are you using? I'd also suggest you test dropping the fbdev parameter, it's still experimental but not required for a proper GUI session anyway.
Also your snippet/paste is unreachable, please repost it.
Last edited by V1del (2024-07-04 18:42:17)
Offline