Can't kldload nvidia-drm

[dmitry n medvedev]

"Are there anything in your /usr/local/lib/compat/pkg/?"

Mine is empty.

"Are your users starting Wayland (here, hyprland compositor?) belong to video group?"



"Does /dev/dri/card0 (the number could vary if multiple cards including iGPU are detected, though) and /dev/dri/renderD128, both of which are symlinks to /dev/drm/0 and /dev/drm/128 respectively?"

In my case, no:



What's the solution to this?

as far as I understand, if you do not have /dev/dri/card0 and /dev/dri/renderD128 - this means your nvidia-drm.ko hasn't started. have a look at kldstat | grep nvidia

 

[T-Aoki]

X is working fine for me, ThinkPad P52 with Quadro P1000 (notebook).
Otherwise, I should NOT have submitted my patches to upgrading.

Edit: You'll find a bunch of my name in "Author" field here. This means X works for me.

 

[GlenH]

as far as I understand, if you do not have /dev/dri/card0 and /dev/dri/renderD128 - this means your nvidia-drm.ko hasn't started. have a look at kldstat | grep nvidia

Right, and for some reason this time building graphics/nvidia-drm-kmod didn't move nvidia-drm.ko to /boot/modules/. I rebuilt, and I now have:

% ls -lv /dev/dri/card0
lrwxr-xr-x 1 root wheel 8 Aug 3 22:07 /dev/dri/card0 -> ../drm/0
# ls -lv /dev/dri/renderD128
lrwxr-xr-x 1 root wheel 10 Aug 3 22:07 /dev/dri/renderD128 -> ../drm/128
# ls -lv /dev/drm/0
crw-rw---- 1 root video 0x8d Aug 3 22:07 /dev/drm/0
# ls -l /dev/drm/128
crw-rw---- 1 root video 0x142 Aug 3 22:07 /dev/drm/128

And I'm now back to the identical behavior I had before: plasma6 gives me a black screen, wayfire gives me a grey screen with a cursor but nothing else, and X11 works fine, but when I go back to the console the VGA driver gives me random gibberish and I have to reboot.

 

[T-Aoki]

Right, and for some reason this time building graphics/nvidia-drm-kmod didn't move nvidia-drm.ko to /boot/modules/.

Just a FYI: graphics/nvidia-drm-kmod (graphics/drm-kmod and graphics/nvidia-drm-kmod-devel, too) is the metaport for "first time installation".
Afterwards, what it pulled in (for graphics/nvidia-drm-kmod on 15.3, should be graphics/nvidia-drm-61-kmod, graphics/drm-61-kmod and x11/nvidia-driver) needed to be upgraded/rebuilt. But the metaport itself is not mandatory.

 

[GlenH]

I get exactly one non-expected message from dmesg related to graphics, which I will give here:

freebsd sysctl_add_oid: can't re-use a leaf (hw.dri.debug)!

Other forum threads indicate it's "probably harmless". Just FYI.

 

[T-Aoki]

Trying startplasma-x11 instead of startplasma-wayland would help determining whether the problem is in Wayland or in nvidia driver sets.

But possibly lack of some functionalities on nvidia driver sets (maybe same as PR 286313) could affecting (at least some) Wayland compositors not working, while X works.

 

[GlenH]

Trying startplasma-x11 instead of startplasma-wayland would help determining whether the problem is in Wayland or in nvidia driver sets.

But possibly lack of some functionalities on nvidia driver sets (maybe same as PR 286313) could affecting (at least some) Wayland compositors not working, while X works.

startplasma-x11 works great. I already tried that.