Is your /usr/src 100% in sync with installed/running kernel, means, are your running (when you're attempting to load nvidia-drm.ko) kernel and modules installed in /boot/modules built using your current (you used to build graphics/nvidia-drm-61-kmod) /usr/src?
Can't load i915kms: unsupported file type
Hello, I've recently re-installed FreeBSD on my ThinkPad T14 and suddenly X11 stopped working. I've installed the graphics/drm-kmod package and enabled the i915kms module but when the kernel tries to load the module it says link_elf_obj: symbol ppsratecheck undefined linker_load_file...forums.freebsd.org
Basically, 26.6. Updating FreeBSD from Source.
make delete-old-libs until you're sure it's safe (nothing is linked with to-be-deleted old libraries). make installworld and BEFORE shutdown -r now in Chapter 26.6.5. dmesg | grep -A 7 BOOT git reflog show on /usr/src. It would show you in which commit hash your /usr/src is.Nice! the issue has a bigger audience than the thread suggests.
#!/bin/sh
export QT_DEBUG_PLUGINS=1
export QT_LOGGING_RULES="*.debug=true"
export XDG_SESSION_TYPE="wayland"
export QT_QPA_PLATFORMTHEME=qt6ct
export QT_QPA_PLATFORM=wayland
export QT_WAYLAND_SHELL_INTEGRATION="xdg-shell"
exec ck-launch-session dbus-launch --exit-with-session startplasma-waylandqt.core.plugin.factoryloader: looking at "/usr/local/lib/qt6/plugins/wayland-shell-integration/libqt-shell.so"
qt.core.plugin.loader: Found metadata in lib /usr/local/lib/qt6/plugins/wayland-shell-integration/libqt-shell.so, metadata=
{
"IID": "org.qt-project.Qt.WaylandClient.QWaylandShellIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"qt-shell"
]
},
"archlevel": 1,
"className": "QWaylandQtShellIntegrationPlugin",
"debug": false,
"version": 395008
}
qt.core.plugin.factoryloader: Got keys from plugin meta data QList("qt-shell")
qt.core.plugin.factoryloader: checking directory path "/usr/local/bin/wayland-shell-integration" ...
qt.core.library: "/usr/local/lib/qt6/plugins/wayland-shell-integration/libxdg-shell.so" loaded library
qt.qpa.wayland: Loading shell integration failed.
qt.qpa.wayland: Attempted to load the following shells QList("xdg-shell")
qt.core.library: "/usr/local/lib/qt6/plugins/wayland-shell-integration/libxdg-shell.so" loaded library
qt.qpa.wayland: Loading shell integration failed.
qt.qpa.wayland: Attempted to load the following shells QList("xdg-shell")
org.kde.startup: "kdeinit5_shutdown" QList() exited with code 255
startplasma-wayland: Shutting down...
startplasmacompositor: Shutting down...
startplasmacompositor: Done.
qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
% uname -KU
1500023 1500023
% make
===> src (all)
===> src/nvidia (all)
machine -> /usr/src/sys/amd64/include
x86 -> /usr/src/sys/x86/include
i386 -> /usr/src/sys/i386/include
awk -f /usr/src/sys/tools/makeobjops.awk /usr/src/sys/dev/acpica/acpi_if.m -h
awk -f /usr/src/sys/tools/makeobjops.awk /usr/src/sys/kern/bus_if.m -h
awk -f /usr/src/sys/tools/makeobjops.awk /usr/src/sys/kern/device_if.m -h
:> opt_acpi.h
awk -f /usr/src/sys/tools/makeobjops.awk /usr/src/sys/dev/pci/pci_if.m -h
awk -f /usr/src/sys/tools/vnode_if.awk /usr/src/sys/kern/vnode_if.src -p
awk -f /usr/src/sys/tools/vnode_if.awk /usr/src/sys/kern/vnode_if.src -q
awk -f /usr/src/sys/tools/vnode_if.awk /usr/src/sys/kern/vnode_if.src -h
touch opt_global.h
/usr/local/bin/ccache cc -O2 -pipe -O3 -pipe -march=native -mtune=native -DNV_VERSION_STRING=\"560.28.03\" -D__KERNEL__ -DNVRM -Wno-unused-function -Wuninitialized -O2 -fno-strict-aliasing -ffreestanding -mno-red-zone -mcmodel=kernel -UDEBUG -U_DEBUG -DNDEBUG -DNV_SPECTRE_V2=1 -DNV_KERNEL_INTERFACE_LAYER -Werror=undef -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I../common/inc -include /tmp/NVIDIA-FreeBSD-x86_64-560.28.03/src/nvidia/opt_global.h -I. -I/usr/src/sys -I/usr/src/sys/contrib/ck/include -fno-common -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -fdebug-prefix-map=./machine=/usr/src/sys/amd64/include -fdebug-prefix-map=./x86=/usr/src/sys/x86/include -fdebug-prefix-map=./i386=/usr/src/sys/i386/include -MD -MF.depend.nvidia_acpi.o -MTnvidia_acpi.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector -Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wcast-qual -Wundef -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas -Wswitch -Wno-error=tautological-compare -Wno-error=empty-body -Wno-error=parentheses-equality -Wno-error=unused-function -Wno-error=pointer-sign -Wno-error=shift-negative-value -Wno-address-of-packed-member -Wno-format-zero-length -mno-aes -mno-avx -std=gnu99 -c nvidia_acpi.c -o nvidia_acpi.o
In file included from nvidia_acpi.c:13:
./nv-freebsd.h:17:2: error: This driver does not support FreeBSD-CURRENT!
17 | #error This driver does not support FreeBSD-CURRENT!
| ^
1 error generated.
*** Error code 1
Stop.
make[2]: stopped making "all" in /tmp/NVIDIA-FreeBSD-x86_64-560.28.03/src/nvidia
*** Error code 1
Stop.
make[1]: stopped making "all" in /tmp/NVIDIA-FreeBSD-x86_64-560.28.03/src
*** Error code 1
Stop.
make: stopped making "all" in /tmp/NVIDIA-FreeBSD-x86_64-560.28.03
%Hm, I've not yet tried 560 series of drivers on main (aka 15-Curret) yet, but running on stable/14. But ustream driver package states that they support only stable and releng branches and usually has code to reject main.
According your photo, both the branch (releng/14.1) and commit hash (first 12 digits are dcdea9e8623e) matches. Looks OK, unless no local modifications are done in /usr/src after the kernel was built.
Although I've been unable to take time to give a shot on main (15-Current) yet, my assumption is that it would work as usual when built via x11/nvidia-driver, overriding driver version.
It does not matter. Just an example of builders.
dbus-run-session startplasma-waylanddbus-launch --exit-with-session dwldbus-launch --exit-with-session startplasma-wayland/var/run/xdg/username
github.com
errors
1 - unable to auto launch dbus daemon without a $DISPLAY for X11
looks like dbus is trying to use $DISPLAY which isnt set because you are trying to launch Wayland
$DISPLAY is only for X11, so you shouldnt get that error using Wayland
i would imagine thats related to how you are starting dbus
and environmental variables not being set for wayland
Code:dbus-run-session startplasma-wayland
instead of using
Code:dbus-launch --exit-with-session dwl
which is what i have used to start every wayland compisor i have tried dwl, wayfire, labwc and hikari
Code:dbus-launch --exit-with-session startplasma-wayland
you are still setting the XDG_RUNTIME_DIR set to the old location of /var/run/user/1001
dont set the XDG_RUNTIME_DIR in your startup script
as i said Freebsd 14.2 creates the XDG_RUNTIME_DIR and exports the variable
Code:/var/run/xdg/username
you should use the new location for XDG_RUNTIME_DIR
otherwise if you use the old location you have to manually create the directory and set the permissions ( which a lot of people forget )
2 - pipewire
dont try starting pipewire before you get kde working
you can always look at that after you get the desktop working
3 - wireplumber not found
dont try starting wireplumber until you get kde working
wireplumber is used to replace pulseaudio with pipewire
you also have to copy config files into place to use wireplumber
my notes on setting up wireplumber on ubuntu
cerberus/pipewire/pipewire-install.org at master · NapoleonWils0n/cerberus
cerberus code library. Contribute to NapoleonWils0n/cerberus development by creating an account on GitHub.
4 - xdg-desktop-portal-kde: not found
you shouldnt need to start the xdg-desktop-portal-kde
the desktop should handle that
I don't have exactly the same environment as you on hand. And I've already seen your wrongly edited/patched Makefile etc. several times. So cannot be sure your (at least) ports tree is in the correct state.
# NVIDIA Distversion
#
# This will be included from x11/nvidia-driver and the nvidia-drm port
NVIDIA_DISTVERSION = 560.28.03