[This is based on what I eventually noticed in the material
of my reply to a different message on freebsd-current .]

Modern https://cgit.freebsd.org/src/blame/sys/sys/param.h has:

#define __FreeBSD_version 1500048

as of https://cgit.freebsd.org/src/commit/sys/sys/param.h?id=e3a4b989d7f7

which was from:

committer Olivier Certner <o...@freebsd.org> 2025-06-18 02:09:29 +0000

Yet today when I do commands like (aarch64 example here aarch64):
(Note: amd64 also observed.)

# pkg search -rFreeBSD-kmods -g '*'
acpi_call-1.0.1.1500043_2 Kernel module for calling ACPI methods from userspace
devctl-jail-kmod-g20190521.1500043 Module to expose jail lifecycle events
intel-ixv-kmod-1.5.34.1500043_2 10G FreeBSD Base Driver Virtual Function for 
Intel(R) NIC
linux_dvbwrapper-kmod-1.0.1500043_2 Linux compatibility layer - DVB ioctl 
handler
mac_nonet-kmod-g20150821.1500043 MAC policy to disable access to networking for 
certain group
mac_rtprio-kmod-g20170417.1500043 MAC policy to manage access for setting 
realtime priorities by GID
mbgtools-f.1.0.0.1500043_1 Drivers and tools for Meinberg PTP/GPS cards
ng_mikrotik_eoip-1.0.1500043 Netgraph node for Mikrotik EoIP tunneling
open-vm-kmod-12.5.0.1500043,2 Open VMware kernel modules for FreeBSD VMware 
guests
openzfs-kmod-2.3.2.1500043,1 OpenZFS kernel module for FreeBSD
. . .

So: 1500043 based, not 1500048 based.

For reference:
150043 started: committer Lexi Winter <i...@freebsd.org> 2025-05-15 00:02:52 
+0000
150044 started: committer Konstantin Belousov <k...@freebsd.org> 2025-05-28 
11:11:23 +0000

So: over 3 weeks ago. (The detailed timing depends on that pkg 2.1+
is still in use in the ampere* based ports-package builds for the
aarch64 context. They will eventually get to pkg 2.2+ .)

That means it looks like the PkgBase builds for main are not
building a FreeBSD-kmods that is a match to any of the kernel
from main's PkgBase build. Instead, it looks to be providing
whatever the ports-package builders have built. For main, that
will frequently not match any of the PkgBase kernels built.

SIDE QUESTION: main has multiple kernels available but only one
FreeBSD-kmods (instead of one per kernel). Which kernel is
FreeBSD-kmods supposed to match? What happens if/when a
different one of those kernels is used instead?

As near as I can tell, unless the kmods are built to match the
intended PkgBase kernel, FreeBSD-kmods would best be avoided
(disabled) for main and handled separately.


NOTE: I've not checked any context but main. But it may well
be that 14.3-STABLE's PkgBase has some similar issues to what
main has.

===
Mark Millard
marklmi at yahoo.com


Reply via email to