Trying to run KDE 6 Plasma with Wayland....

Did u resign to help me to find the reason why I can't use nvidia-drm-61.ko ? I don't see any further operation that I can try.
 
Don ZioMario said:
Did u resign to help me to find the reason why I can't use nvidia-drm-61.ko ? I don't see any further operation that I can try.
Click to expand...
I'm not a nvidia insider. What I can look into and try is quite limited, what's actually on my hand. I've already adviced almost everything I can for now.

The remaining thing what I can advice is:
  • If you're trying graphics/nvidia-drm-61-kmod on 14.0 for your VM, resign. It requires codes that are not merged into 14.0-Release-p*. Focus on bare-metal 14.1 or switch to graphics/nvidia-drm-515-kmod for both.
  • You seem to have Turing or newer generation of GPU, as nvidia-smi is trying to load the firmware module nvidia_gsp_tu10x_fw.ko added on 560.28.03 as of your screenshots. But I haven't test it at all, as I don't have GPU supporting GSP firmwares. So possibly there's some problems that I cannot even notice. Trying 555.58.02 or 550.107.02 could help, if the problem is related with GSP firmware. Or try adding nvidia_gsp_tu10x_fw.ko, which nvidia-smi attempts to load, in kld_list variable in /etc/rc.conf[.local].
  • If sticking with 560 series of Beta drivers, newer 560.31.02 is already available. Running fine for me on xorg (not Wayland), Pascal generation of GPU (Quadro P1000 notebook) with disabling iGPU in CPU by UEFI.
These are everything I can advice for now. If I could get some new insights on PR 280772 or somewhere else, or found newer versions of drivers are released, I'll let you know here.
 
it might be worth trying to install KDE using Linux

something like kde neon or kubuntu

KDE neon

KDE neon is the latest and greatest of KDE community software.
neon.kde.org neon.kde.org

that way you could find out if your nvidia card works with kde and wayland on linux
and then the issue is with freebsd and nvidia

it might give you a few clues,
such as the packages installed or what setting are used

that you could try setting on freebsd running kde

not suggesting you use linux permanently
just install it to test hardware compatibility

and if kde and wayland doesnt work on linux then you know its not just a freebsd issue
 
NapoleonWils0n said:
it might be worth trying to install KDE using Linux

something like kde neon or kubuntu

KDE neon

KDE neon is the latest and greatest of KDE community software.
neon.kde.org neon.kde.org

that way you could find out if your nvidia card works with kde and wayland on linux
and then the issue is with freebsd and nvidia

it might give you a few clues,
such as the packages installed or what setting are used

that you could try setting on freebsd running kde

not suggesting you use linux permanently
just install it to test hardware compatibility

and if kde and wayland doesnt work on linux then you know its not just a freebsd issue
Click to expand...

I know for sure that the problem is caused by nvidia and/or some component connected to nvidia,because kde 6 and wayland worked (even if it crashed many times) with the older [Intel] gpu of my secondary pc.
 
I've seen pkg upgrade -n showing Number of packages to be removed.
Sometime it was quite a large number, but currently my installed pkgs are up to date with my current ports tree, so cannot show example.
 
NapoleonWils0n said:
freebsd 14.1 p3 seems to have removed some kde and plasma packages …
Click to expand...

Coincidence.

Noted on Wednesday 14th: "… a few new builders going online this week. …".

Various amd64 packages that were recently unavailable for FreeBSD:13:quarterly are now available. FreeBSD:14:quarterly might be not far behind.
 
Cath O'Deray said:
Coincidence.

Noted on Wednesday 14th: "… a few new builders going online this week. …".

Various amd64 packages that were recently unavailable for FreeBSD:13:quarterly are now available. FreeBSD:14:quarterly might be not far behind.
Click to expand...

but on the FreeBSD 14.1-p3 I use to test KDE 6 + Wayland,I use latest...have those packages been removed even on latest ?
 
arent the packages back in latest as well

i just used poudriere to build linux-widevine-cdm using latest
and ffmpeg and all the packages seem to be in latest
 
Don ZioMario said:
I use latest...have those packages been removed even on latest ?
Click to expand...

1723992682801.pngkde6-devel is present, as are various Wayland-related packages.
 
astyle said in a profile post comment:

… x11/plasma-wayland-protocols has absolutely nothing that actually depends specifically on QT5 or QT6, …
Click to expand...

From a run of poudriere:

Code: 
[00:00:08] x11/plasma-wayland-protocols depends on devel/ccache
[00:00:08] x11/plasma-wayland-protocols depends on devel/cmake-core
[00:00:08] x11/plasma-wayland-protocols depends on devel/kf6-extra-cmake-modules
[00:00:08] x11/plasma-wayland-protocols depends on devel/ninja
[00:00:08] x11/plasma-wayland-protocols depends on devel/qt5-buildtools
[00:00:08] x11/plasma-wayland-protocols depends on devel/qt5-core
[00:00:08] x11/plasma-wayland-protocols depends on devel/qt5-qmake
[00:00:08] x11/plasma-wayland-protocols depends on ports-mgmt/pkg


1724723901121.pngPeople, please avoid profile posts for technical discussion. It's often unsuitable.

Cath O'Deray said:
… the annoyingly tight character limit (like, it's last century) …
Click to expand...

… and so on. Thanks.
 
Cath O'Deray said:
Code: 
[00:00:08] x11/plasma-wayland-protocols depends on devel/qt5-buildtools
[00:00:08] x11/plasma-wayland-protocols depends on devel/qt5-core
[00:00:08] x11/plasma-wayland-protocols depends on devel/qt5-qmake
Click to expand...
This is the stuff that needs to be accounted for when writing the Makefile, apparently. Thanks for the correction!
 
Well, I tried to follow this thread, do the env exports as suggested by NapoleonWils0n, install seatd and qt6ct, and ended up with this:
Code: 
org.kde.startup: not a reply org.freedesktop.locale1 QDBusMessage(type=Error, service
="", error name="org.freedesktop.DBus.Error.ServiceUnknown", error message="The name
org.freedesktop.locale1 was not provided by any .service files", signature="s", conte
nts=("The name org.freedesktop.locale1 was not provided by any .service files") )
Initializing  "/usr/local/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_mouse.so"
kcm_mouse: Not able to select appropriate backend.
Initializing  "/usr/local/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
kf.kirigami.platform: Failed to find a Kirigami platform plugin for style ""
No backend specified, automatically choosing drm
QKqueueFileSystemWatcherEngine::addPaths: open: No such file or directory
kwin_core: Could not determine the active graphical session
kwin_wayland_drm: failed to open drm device at "/dev/dri/card0"
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
kwin_core: Could not determine the active graphical session
kwin_wayland_drm: failed to open drm device at "/dev/dri/card0"
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
kwin_core: Could not determine the active graphical session
kwin_wayland_drm: failed to open drm device at "/dev/dri/card0"
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
kwin_core: Could not determine the active graphical session
kwin_wayland_drm: failed to open drm device at "/dev/dri/card0"
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
kwin_core: Could not determine the active graphical session
kwin_wayland_drm: failed to open drm device at "/dev/dri/card0"
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
kwin_core: Could not determine the active graphical session
kwin_wayland_drm: failed to open drm device at "/dev/dri/card0"
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
kwin_core: Could not determine the active graphical session
kwin_wayland_drm: failed to open drm device at "/dev/dri/card0"
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
kwin_core: Could not determine the active graphical session
kwin_wayland_drm: failed to open drm device at "/dev/dri/card0"
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
kwin_core: Could not determine the active graphical session
kwin_wayland_drm: failed to open drm device at "/dev/dri/card0"
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
kwin_core: Could not determine the active graphical session
kwin_wayland_drm: failed to open drm device at "/dev/dri/card0"
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
kwin_core: Could not determine the active graphical session
kwin_wayland_drm: failed to open drm device at "/dev/dri/card0"
kwin_wayland_drm: No suitable DRM devices have been found
org.kde.startup: "kdeinit5_shutdown" QList() exited with code 255
Initializing  "/usr/local/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_style.so"
startplasma-wayland: Shutting down...
startplasmacompositor: Shutting down...
startplasmacompositor: Done.
/usr/local/bin/xrdb: Connection refused
/usr/local/bin/xrdb: Can't open display ':0'
/usr/local/bin/xsetroot:  unable to open display ':0'
That's my entire output from command dbus-launch --exit-with-session startplasma-wayland 2> startplasma.log

(Hardware description coming in a separate post)
 
there was an update for wayland last night
dont know if that helps

from the log file it looks like its trying its trying to open an X display
not sure if thats because its trying to start an X session

or if its related to XWayland

Code: 
/usr/local/bin/xrdb: Can't open display ':0'

wayland use a WAYLAND_DISPLAY variable with a value of wayland-0

Code: 
WAYLAND_DISPLAY=wayland-0

whereas X11 uses a DISPLAY variable with a value of :0

Code: 
DISPLAY=:0

thats why i mentioned the error
because it say cant open display :0

which you wouldnt get with wayland because there is no :0 like there is on X
 
I start the Xorg session with XINITRC=/usr/local/bin/startplasma-x11. Then within Xorg, I start the Plasma Wayland session using same command (run within the Xorg session in Konsole) as my previous post. That command's only output was (uint32 1,) , and a successful launch of a KDE Wayland session in its own window.
 

Attachments

  • original_Xorg_session.png
    original_Xorg_session.png
    118.8 KB · Views: 31
  • Wayland_session.png
    Wayland_session.png
    146.2 KB · Views: 27
i came across this on the arch wiki

KDE - ArchWiki

wiki.archlinux.org wiki.archlinux.org

Code: 
/usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland

obviously you would need to change this path because thats on linux

does this command work on freebsd

Code: 
plasma-dbus-run-session-if-needed startplasma-wayland
 
astyle said:
so you're saying that WAYLAND_DISPLAY needs to be exported by hand, too?
Click to expand...
hi mate, you shouldnt need to
normally the compositor or desktop will set it

i have run wayfire, labwc, hikari, river and dwl
and didnt set it for any of them

i dont export it in my ~/.zshenv
i only export the XDG directories

Code: 
# ~/.zshenv

# Path
typeset -U PATH path
path=("$HOME/bin" "/usr/local/bin" "$path[@]")
export PATH

# xdg directories
export XDG_CONFIG_HOME="$HOME/.config"
export XDG_CACHE_HOME="$HOME/.cache"
export XDG_DATA_HOME="$HOME/.local/share"
# XDG_RUNTIME_DIR automatically set to /var/run/xdg/djwilcox

if you want to export the wayland settings in your shell config
it would look like this

Code: 
# wayland
export WAYLAND_DISPLAY=wayland-0
# qt
export QT_QPA_PLATFORM=wayland
# gtk
export GDK_BACKEND=wayland
 
NapoleonWils0n said:
does this command work on freebsd

Code: 
plasma-dbus-run-session-if-needed startplasma-wayland
Click to expand...
Nope, I get same results as earlier, even after adjusting for running on FreeBSD.

I did have success with running Wayfire as a pure Wayland thing. That has me thinking that it's probably a compositor issue - Wayfire is a relatively simple compositor, so it has relatively simple interaction with Wayland underneath it. kwin6, OTOH, is pretty complex, so its interaction with Wayland underneath is a non-trivial matter.

Just keeping track of ENV variables, commands, errors, and results - one needs to have a spreadsheet to keep track of combinations, what worked, what didn't, and notes on why. Would be nice if I had the time and patience to do that myself... Otherwise, this is just a crapshoot by rank-and-file users like me.
 
I did have success with running Wayfire as a pure Wayland thing. That has me thinking that it's probably a compositor issue
Click to expand...
i think your right mate

Wayfire and other window manager dont have that many dependencies

Whereas KDE and Kwin have dependencies that have more dependencies
and if one of the many packages doesnt work then the desktop doesnt work either

Thats why a lot of Linux distros dont ship KDE as the default desktop
 
You must log in or register to reply here.
Back
Top