Re: For main [so: 15] FreeBSD:15:/base_latest/ and FreeBSD:15:/kmods_latest/ do not track [14.3-STABLE's FreeBSD:14:* too]

In reply to: Mark Millard : "For main [so: 15] FreeBSD:15:*/base_latest/ and FreeBSD:15:*/kmods_latest/ do not track"
Go to: [ bottom of page ] [ top of archives ] [ this month ]
From: Mark Millard <marklmi_at_yahoo.com>
Date: Wed, 25 Jun 2025 19:29:58 UTC
On Jun 24, 2025, at 20:08, Mark Millard <marklmi@yahoo.com> wrote:

> [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 <olce@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 <ivy@FreeBSD.org> 2025-05-15 00:02:52 +0000
> 150044 started: committer Konstantin Belousov <kib@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.


I got an aarch64 booted with a 14.3-STABLE PkgBase
installation (somewhat older, but after 14.3-STABLE).

# uname -apKU
FreeBSD official-PkgBase 14.3-STABLE FreeBSD 14.3-STABLE stable/14-n271679-d752f91d7f0a GENERIC arm64 aarch64 1403502 1403502

So: 1403502 has been in place for some time.

# pkg repositories
FreeBSD: { 
    url             : "http://pkg.FreeBSD.org/FreeBSD:14:aarch64/latest",
    enabled         : yes,
    priority        : 0,
    mirror_type     : "SRV",
    signature_type  : "FINGERPRINTS",
    fingerprints    : "/usr/share/keys/pkg"
  }
FreeBSD-kmods: { 
    url             : "http://pkg.FreeBSD.org/FreeBSD:14:aarch64/kmods_latest",
    enabled         : yes,
    priority        : 0,
    mirror_type     : "SRV",
    signature_type  : "FINGERPRINTS",
    fingerprints    : "/usr/share/keys/pkg"
  }
FreeBSD-base: { 
    url             : "pkg+https://pkg.FreeBSD.org/FreeBSD:14:aarch64/base_latest",
    enabled         : yes,
    priority        : 0,
    mirror_type     : "SRV",
    signature_type  : "FINGERPRINTS",
    fingerprints    : "/usr/share/keys/pkg"
  }

# pkg search -rFreeBSD-kmods -g '*'
acpi_call-1.0.1.1403501_2      Kernel module for calling ACPI methods from userspace
devctl-jail-kmod-g20190521.1403501 Module to expose jail lifecycle events
hammer2-1.2.9.1403501          HAMMER2 file system for FreeBSD (experimental write support)
intel-em-kmod-7.7.8.1403501    Gigabit FreeBSD Base Drivers for Intel(R) Ethernet
intel-ice-kmod-1.38.16.1403501_2 Intel® Network Adapter Driver for E810 Series Devices
intel-igb-kmod-2.5.28.1403501  NIC Driver for Intel(R) 82575/6 and 82580-Based cards
intel-ix-kmod-3.3.35.1403501_2 10 gigabit FreeBSD Base Driver for Intel(R) Network Connections
intel-ixl-kmod-1.13.4.1403501_2 40 gigabit FreeBSD Base Driver for Intel(R) Network Connections
intel-ixv-kmod-1.5.34.1403501_2 10G FreeBSD Base Driver Virtual Function for Intel(R) NIC
linux_dvbwrapper-kmod-1.0.1403501_2 Linux compatibility layer - DVB ioctl handler
mac_nonet-kmod-g20150821.1403501 MAC policy to disable access to networking for certain group
mac_rtprio-kmod-g20170417.1403501 MAC policy to manage access for setting realtime priorities by GID
mbgtools-f.1.0.0.1403501_1     Drivers and tools for Meinberg PTP/GPS cards
ndproxy-3.2.1403501_1          Implementation of IPv6 Neighbor Discovery proxy
ng_mikrotik_eoip-1.0.1403501   Netgraph node for Mikrotik EoIP tunneling
open-vm-kmod-12.5.0.1403501,2  Open VMware kernel modules for FreeBSD VMware guests
openzfs-kmod-2.3.2.1403501,1   OpenZFS kernel module for FreeBSD
parallels-tools-0.1.2.1403501_1 Parallels Desktop Tools for FreeBSD
plasma-kmod-0.1.1403501_4      Plasma-effect screensaver kernel module
pwcbsd-1.4.1.1403501_15        The Linux pwc webcam driver ported to FreeBSD
quantis-kmod-v18.03.08.1403501 Kernel driver for Quantis PCI/PCIe random number generator
realtek-re-kmod-1100.00.1403501_1 Kernel driver for Realtek PCIe Ethernet Controllers
realtek-re-kmod198-198.00.1403501 Kernel driver for Realtek PCIe Ethernet Controllers
sysctlbyname-improved-kmod-20221211.1403501 Internal sysctl object to implement an improved sysctlbyname(3)
sysctlinfo-kmod-20221211.1403501_1 Kernel sysctl MIB-Tree interface
uarduno-1.02.1403501_1         FreeBSD Kernel Driver for the Arduino Uno USB interface
utouch-kmod-0.0.5.1403501      Kernel driver for absolute USB HID mice
vether-kmod-g20211214.1403501_1 Virtual Ethernet Interface
wifi-firmware-ath10k-kmod-20240513.1403501_2 Firmware modules for the ath10k (ath10k) WiFi NIC driver
wifi-firmware-ath11k-kmod-20240513.1403501_2 Firmware modules for the ath11k (ath11k) WiFi NIC driver
wifi-firmware-ath12k-kmod-20240513.1403501_2 Firmware modules for the ath12k (ath12k) WiFi NIC driver
wifi-firmware-iwlwifi-kmod-20241017.1403501_2 Firmware modules for the iwlwifi (iwlwifi) WiFi NIC driver
wifi-firmware-mt76-kmod-20240513.1403501_2 Firmware modules for the mt76 (mt76) WiFi NIC driver
wifi-firmware-mt7601u-kmod-20241017.1403501_2 Firmware modules for the mt7601u (mt7601u) WiFi NIC driver
wifi-firmware-rtw88-kmod-20241017.1403501_2 Firmware modules for the rtw88 (rtw88) WiFi NIC driver
wifi-firmware-rtw89-kmod-20241017.1403501_2 Firmware modules for the rtw89 (rtw89) WiFi NIC driver

So: 1403501 based kmods, not 1403502 based.

Again not matching any kernel's built by
PkgBase for the installation/update
that would be done now (for 14.3-STABLE
this time).

It would seem that when FreeBSD-kmods does
not match the intended kernel, it should be
avoided/disabled, much like for main.

(At least for the likes of 14.3-STABLE, it
likely updates less often than main and a
smaller fraction might be breaking changes.
So an asctually-valid combination would
likely be possible for a higher fraction of
the overall time.)

Which kernel should it track? There is more
than one kernel to pick from for 14.3-STABLE:

# pkg search -rFreeBSD-base -g '*kernel*' | grep -v '\-dbg-'
FreeBSD-kernel-generic-14.snap20250625092520 FreeBSD GENERIC kernel 
FreeBSD-kernel-generic-mmccam-14.snap20250625092520 FreeBSD GENERIC-MMCCAM kernel 

(The names do not identify the 1403502 status,
which is unfortunate for the purpose here.)

The 2 kernels conflict on dtb files and so
cannot both be installed. But amd64 might
allow both to be installed, there being no
*.dtb files involved.

What should happen when the other kernel is
picked?

I'll note that 14.3-RELEASE patching may be
unlikely to have such issues and certainly
happens less often overall.

But, for 14.3-RELEASE, there still is the:

FreeBSD-kernel-generic-14.3.pkg
vs.
FreeBSD-kernel-generic-mmccam-14.3.pkg

issue vs. what ends up available from:

https://pkg.freebsd.org/FreeBSD:14:aarch64/kmods_latest_3/

and which kernel it supports.


===
Mark Millard
marklmi at yahoo.com