Call For Testing: nvidia-drm kernel module

grahamperrin said:
T-Aoki (if you're not already aware of the port): graphics/nvidia-drm-kmod … and amongst reports,

273699 – graphics/nvidia-drm-510-kmod, graphics/nvidia-drm-515-kmod: package messages about loading the kernel module

bugs.freebsd.org bugs.freebsd.org
Click to expand...
Unfortunately, it's not relevant here. nvidia-drm.ko itself is not built yet.
My assumption reading Release Highlights of 550.40.07 is that it builds nvidia-drm.ko by itself, by default to be available. But it turned out that it's not currently true at least building via x11/nvidia-driver port.

Possibly overlooked, but as I couldn't find any prerequisites or special method to build nvidia-drm.ko, I thought nvidia added all actually required codes in driver package, regardless incorporating codes by 3rd parties (licensed) or developed by themselves, and it is built without additional external dependencies as-is.
 
Ah, sorry, I overlooked the beta context despite your mention:

T-Aoki said:
… 550.40.07 … BETA …
Click to expand...

(/boot/modules/nvidia-drm.ko is listed at <https://www.freshports.org/graphics/nvidia-drm-510-kmod/#pkg-plist> and <https://www.freshports.org/graphics/nvidia-drm-515-kmod/#pkg-plist>.)


T-Aoki said:
… x11/linux-nvidia-libs …
Click to expand...

NVIDIA graphics libraries and programs (Linux version)

Not documented:

Code: 
% rg linux-nvidia-libs /usr/doc/documentation/content/en
%

What is the purpose of this port? I have one of its slaves installed, but I don't know why, I probably took a lucky dip approach in relation to some bugs.

<https://www.freshports.org/x11/linux-nvidia-libs#requiredby> it's not required by any other port. Is it recommended, or required, for things that use the Linuxulator?
 
grahamperrin said:
(/boot/modules/nvidia-drm.ko is listed at <https://www.freshports.org/graphics/nvidia-drm-510-kmod/#pkg-plist> and <https://www.freshports.org/graphics/nvidia-drm-515-kmod/#pkg-plist>.)
Click to expand...
Yes, I know. What I wondered is that it is now incorporated into official (beta) driver package or not. I'm puzzled with this.
Currently, ashafer is creating his upstream distfile and update the port when x11/nvidia-driver and x11/linux-nvidia-libs are updated.
Anyway, even if it becomes buildable, it's on maintainers (danfe@, x11@ and ashafer) how these should be handled. I'd be able to help, but have no authority for it.

grahamperrin said:
What is the purpose of this port? I have one of its slaves installed, but I don't know why, I probably took a lucky dip approach in relation to some bugs.
Click to expand...
It's for Linux apps working on top of linuxulator.
Even if nothing in ports tree needs it, anyone manually installing Linux apps (without using ports) needs nvidia proprietary libraries provided by this port should need it.
And as its contents comes from nvidia driver package for Linux and should better in sync with driver for FreeBSD (a bunch of libraries provided are unavailable for FreeBSD native ones, especially CUDA-related ones).
 
Yes the nvidia-drm patches are now incorporated into the official driver. No they are not built by default, you'll have to cd into src/nvidia-drm and make + make install there. It's not built by default because it requires having a copy of drm-kmod to reference during the build, and this way we don't have to suddenly update every testing system to be set up for DRM usage/builds and break existing flows.

For the average user this won't matter as I'll update the nvidia-drm-*-kmod ports to build nvidia-drm from the release tarball and get rid of my github patch distribution thing (finally!). Nobody should really be building the driver outside of ports anyway. I've been waiting for the 550 driver to get picked up by the nvidia-driver port, I see you created bug 277028 so I guess I should go ahead and start doing this.
 
ashafer said:
Yes the nvidia-drm patches are now incorporated into the official driver. No they are not built by default, you'll have to cd into src/nvidia-drm and make + make install there. It's not built by default because it requires having a copy of drm-kmod to reference during the build, and this way we don't have to suddenly update every testing system to be set up for DRM usage/builds and break existing flows.

For the average user this won't matter as I'll update the nvidia-drm-*-kmod ports to build nvidia-drm from the release tarball and get rid of my github patch distribution thing (finally!). Nobody should really be building the driver outside of ports anyway. I've been waiting for the 550 driver to get picked up by the nvidia-driver port, I see you created bug 277028 so I guess I should go ahead and start doing this.
Click to expand...
Thanks for the clarification! So same distfile is used for both x11/nvidia-driver and graphics/nvidia-drm-*-kmod once 550 or later becomes production, but kept separately not to confuse existing users who don't need drm features.

Yes, I've filed PR 277028 basically for allowing x11/linux-nvidia-libs to be built overriding DISTVERSION to 550.40.07.
For not to be rejected, updates for latest production branch driver is incorporated (usually, patches only for beta and/or new feature branch is not accepted).
 
Will this patch make it into packages? At present, with nvidia-drm-515-kmod-535.146.02 (from packages) I am unable to get Wayland working on my machine with an NVidia card.
Even though for me, Wayland is more a curiosity than anything else, thank all of you for your work on this.
 
scottro said:
Will this patch make it into packages? At present, with nvidia-drm-515-kmod-535.146.02 (from packages) I am unable to get Wayland working on my machine with an NVidia card.
Even though for me, Wayland is more a curiosity than anything else, thank all of you for your work on this.
Click to expand...
Maybe unlikely.
Almost just after I posted my previous comment, nvidia released driver 550.54.14 as production Latest Production Branch Version.
I'll update again (dropping nvidia-drm-*-kmod part) with subject line after some casual testing, if no new fatal-to-me breakage is found.

For graphics/nvidia-drm-*-kmod, ashafer would be investigating how to implemet for this new framework from 550.* now as he posted at #55 here.
There seems to be no plan to migrate graphics/nvidia-drm-*-kmod ports into x11/nvidia-driver port, not to bother who don't need drm support.
 
Uploaded patch to updating to new production branch driver 550.54.14 at PR 277028. Edited its Summary: field to reflect the switch of production branch.
Note that patches for graphics/nvidia-drm-*-kmod are not included for now, as it requires ashafer's work to finish.
For this reason, previous patch for 535.154.05 #2 is kept. Please be patient until ashafer's work is to be finished.
 
You must log in or register to reply here.
Back
Top