Missing kernel modules on snapshots

LuKePicci

Hi, is it expected to have missing kernel modules in /boot/kernel on latest 2.7.0 snapshots?

In particular, I'm missing tpm.ko which was there on 2.6.0. Have they moved into a separate package?

Thanks

jimp

tpm.ko is there:

: ls -l /boot/kernel/tpm.ko
-r-xr-xr-x  1 root  wheel  60776 Mar  1 01:54 /boot/kernel/tpm.ko

: pkg which /boot/kernel/tpm.ko
/boot/kernel/tpm.ko was installed by package pfSense-kernel-pfSense-2.7.0.a.20230301.0600

LuKePicci

@jimp then there must be something wrong with the 20230308 snapshot

Will try 20230301, thanks

LuKePicci

Update

20230309 has same issue of 20230308, modules are missing (not just tpm.ko)
20230301 and 20230302 didn't boot for other OT reasons (stuck at configuring firewall).

Will go back in time until I find one which includes modues and boots fine.

jimp

It did change somewhere between the 1st and 8th builds. I started a Redmine issue here:

https://redmine.pfsense.org/issues/14086

There are quite a few missing, it went from >800 modules to ~80.

Dobby_

@lukepicci said in Missing kernel modules on snapshots:

Update

20230309 has same issue of 20230308, modules are missing (not just tpm.ko)

20230301 and 20230302 didn't boot for other OT reasons (stuck at configuring firewall).

Will go back in time until I find one which includes modues and boots fine.

Update, on 2023-05-17 (both 23.05RC and 2.7 Devel)

pfSense 23.05 RC (latest)

[23.05-RC][root@xx xx xx]/root: ls -l /boot/kernel/*.ko | wc -l
     822

pfSense 2.7 Devel (zfs) x86_64 (latest)

[2.7.0-DEVELOPMENT][root@xx xx xx]/root: ls -l /boot/kernel/*.ko | wc -l                                                                          
      73

jimp

We are working on getting back to a state where we only include the modules necessary to function, rather than carrying them all (and the extra disk space they consume).

If you can identify the specific modules you need that were not present in the other images, then we can look into whether or not it's feasible to include them in builds. It may depend on what they are / what their dependencies are.

LuKePicci

For our needs we need the tpm.ko module in order to get device attestation in Azure IoT Hub. We have a tested and working solution already on 2.6.0.

It would be fine to have such modules on packages instead of being included into the main build.

I would heavily discourage to drop all modules from production builds without having packages for them available.