Re: unexpected problem from the kmod repo

On Wed, 12 Nov 2025 21:09:50 +0000
void <[email protected]> wrote:

> On Wed, Nov 12, 2025 at 03:28:28PM +0200, Andriy Gapon wrote:
> >
> >I am using nvidia packages as an example, because I personally have 
> >been affected, but the problem can be more general.
> >
> >Splitting nvidia-driver into the kernel and userland pieces was the 
> >right thing from the perspective that the kernel driver is obvious 
> >coupled with kernel version.
> >
> >But it seems that nvidia userland and kernel module are also coupled 
> >with each other.

Correct.
Just like the version of x11/inux-nvidia-libs* (if installed) must be
in sync with x11/nvidia-driver*.


> >Main package repo-s and kmod repo-s are updated at independent cadences.
> >Also, there can be build failures that can introduce further 
> >unpredictability into package update cycles.
> >So, it can happen and has happened recently that nvidia packages got 
> >updated in one place but remained at an older version in the other.

Hope this is an extraordinary situation in preparation of new
*.0-Release. I'm not using official pkg repos, but IIRC, nvidia
driver things on main repo are usually built quickly after commits.


> Yikes! :(
> 
> I don't use repos/pkgs, and build everything from source.
> Although everything in a port gets built into a pkg before it
> installs.
> 
> On a desktop, the x11/nvidia-driver-470 port gets rebuilt and 
> reinstalled every time the kernel gets rebuilt and reinstalled.
> It does this because of a PORTS_MODULES+= line
> in /etc/src.conf containing x11/nvidia-driver-470
> 
> Will this still take care of everything required or is 
> "userland" something else, does it need to build something else
> in addition to make sure userland and the kmod don't go out of sync
> like you describe?

Not sure it works or not (I'm not using PORTS_MODULES), but possibly
abusing PORTS_MODULES for x11/nvidia-driver* help, if related codes
does NOT checking if the specified ports are actually kmod ones or not.

> -- 


-- 
Tomoaki AOKI    <[email protected]>