Wayland session dissapeared

After upgrading recently, there was nvidia related updates,kmods and stuff and i believe it overwrited my build..Everything is here..
nvidia-drm.ko loaded
drm.ko loaded
nvidia.ko loaded
nvidia-modeset.ko loaded
hw.nvidiadrm.modeset: 1
seatd_enable: YES

but on sddm i dont see Wayland option to choose from anymore..what went wrong after upgrade? i run some commands to check my setup, and all is there..so now im confused..
 
i had to reinstall: cd /usr/ports/x11/nvidia-kmod
sudo make clean
sudo make reinstall clean

and

cd /usr/ports/graphics/nvidia-drm-612-kmod
sudo make clean
sudo make reinstall clean and that brought back wayland session..because of mismach of nvidia drm kmod, in upgraded version is: nvidia-driver-595.104.02
nvidia-kmod-595.104.02.1501000
but nvidia-drm-612-kmod was-595.99.02.1501000 .. so every time nvidia kmod gets upgraded, this action will be needed? Or i must compare versions and only if versions are matching then do an pkg upgrade?
 
Yeah... Don't mix ports from /usr/ports packages and precompiled packages from PKG install... You can have incompatibility software and I hope it don't occurr in long term your system can be corrupted... From ports it's take more time to have latest versions. But you always can install manually from Nvidia page the binary.
 
It would be nice to know what sddm really executes after choosing Wayland. It should give a hint on CLI output. This is why I don't use display managers and start X.org scripted instead. Not using Wayland but I guess it takes a command to start it.
 
It would be nice to know what sddm really executes after choosing Wayland. It should give a hint on CLI output. This is why I don't use display managers and start X.org scripted instead. Not using Wayland but I guess it takes a command to start it.
When SDDM was not working I used this to start a Plasma Wayland session:
/usr/local/lib/libexec/plasma-dbus-run-session-if-needed /usr/local/bin/ck-launch-session /usr/local/bin/startplasma-wayland
 
Back
Top