I think we are at 2024On the handbook the instructions are dated 2021...we are on 2025.
Indeed, as I wrote it is a core i5 machine. integrated GPU. And it's OS version is 14.1I'm using one nvidia GPU. I've installed nvidia-drm-kmod. I suppose that you don't have one nvidia GPU,for this reason you have installed drm-61-kmod. I don't have it inside the ports or the packages. I have only drm-510-kmod ; drm-515-kmod ; drm-kmod ; nvidia-drm-510-kmod ; nvidia-drm-515-kmod ; nvidia-drm-kmod. Which version of FreeBSD are you running ? Which GPU do u have ?
You use this command, startplasma-wayland, to start Wayland? Have you tried the wayfire way?
and how close are you?I'm getting close to make it work...
yes I obviously removed the kde6 packagesI'm not able to install kde5 + wayland. kde5 packages conflict with kd6 packages.
Nope, it's not. You're running Wayfire, on bare metal, and calling up KDE 6 components. You can call up same KDE components if you were running the GNOME desktop.As the OP, I'm not sure what you mean
This is not KDE6 on Wayland? Or and if not, what is the KDE on Wayland people are after?
/usr/local/bin/startplasma-wayland
still fails, you end up starting Wayfire first to help things along. The goal of "KDE on Wayland" is to make sure that startplasma-wayland
actually works with no external help.kwin6 on bare metal
How about the very idea of having to do a "somewhat workable kludge that only works if you know what you're doing and are willing to spend the time" ? if kwin6 is not able to reliably and demonstrably start with Wayland like it does with Xorg, I see that as a downside.What are the downsides of KWin not on bare metal with Wayland?
"Not on bare metal" means virtualizing, and that eats up extra resources on the bare metal. You can also launch a KDE Wayland session from within a KDE Xorg session. That is good for playing, and 'proof-of-concept', but is just awkward to use as a daily driver.What are the downsides of KWin not on bare metal with Wayland?
… Without kwin6, …
… not kwin …