Problem compiling kernel module for newer BalenaOS

krix · March 28, 2024, 7:23am

I have for a while been compiling a kernel module for my BalenaOS devices.
I download kernel headers from the Balena s3 bucket.

It compiles for all BalenaOS v2.x.x, but breaks for v3.x.x and onwards.
I notice this line in the change log: “use kernel-devsrc to provide kernel headers”

github.com

balena-os/meta-balena/blob/master/CHANGELOG.md#v300

Change log
-----------

# v5.2.3
## (2024-03-22)

* mv docs/{,uefi-}secure-boot.md [Joseph Kogut]
* docs: secure-boot: update for PCR7 sealing [Joseph Kogut]
* os-helpers: compute_pcr7: merge event log digests [Joseph Kogut]
* Update policy's PCR7 value in hostapp-update hook [Joseph Kogut]
* os-helpers-tpm2: compute_pcr7: allow overriding efivars [Joseph Kogut]
* Move policy update to HUP commit hook [Joseph Kogut]
* rollback-health: move apply-dbx to HUP commit hook [Joseph Kogut]
* hostapp-hooks: include 0-signed-update only for efi [Joseph Kogut]
* secure boot: seal luks passphrase w/ PCR7 [Joseph Kogut]
* os-helpers-tpm2: separate authentication from crypto [Joseph Kogut]
* tcgtool: new recipe [Joseph Kogut]
* recipes-bsp: add recipe for GRUB 2.12 [Joseph Kogut]
* tests: skip bootloader config integrity check [Joseph Kogut]
* secureboot: enroll kernel hash in db for EFISTUB [Joseph Kogut]

This file has been truncated. show original

I suspect this means I need to compile in a different way, but I have not been able to find out what the change is and/or what to do about it.

The exact error message I get with the newer kernel headers is this (though that might not tell you much):
make[4]: *** No rule to make target ‘/usr/src/app/peak-linux-driver-8.15.2/driver/src/pcan_main.o’, needed by ‘/usr/src/app/peak-linux-driver-8.15.2/driver/pcan.o’.

klutchell · April 3, 2024, 1:01pm

Hey @krix , welcome back to the forums!

I think this blog post should answer all of your questions, and specifically mentions what changes are needed for v3.x:

Let us know if you are still having trouble after following the advice in the blog!

krix · April 3, 2024, 7:31pm

Thank you. The trick was the need for make modules_prepare.