Combining Kernel Modules and Backport Modules

Technical Support
,
1

I find myself at a point now where I have a working Linux distribution for the Apalis TK1, which relies on a number of kernel modules (adv7280, etc) as well as the Wi-Fi modules from a backported package.

When I deploy the kernel modules to my target, I copy across a structure such as the following to the /lib/modules directory:

/lib/modules/3.10.40-g19722d4/build/*
/lib/modules/3.10.40-g19722d4/kernel/*
/lib/modules/3.10.40-g19722d4/source/*
/lib/modules/3.10.40-g19722d4/modules.alias
/lib/modules/3.10.40-g19722d4/modules.alias.bin
/lib/modules/3.10.40-g19722d4/modules.builtin
/lib/modules/3.10.40-g19722d4/modules....

and so on.

Likewise when I come to deploy the backport modules onto my target, I’m also copying a structure similar to the /lib/modules directory:

/lib/modules/3.10.40-g19722d4/updates/*
/lib/modules/3.10.40-g19722d4/modules.alias
/lib/modules/3.10.40-g19722d4/modules.alias.bin
/lib/modules/3.10.40-g19722d4/modules....

and so on.

Given that both installs create these modules.alias, modules.alias.bin, modules... files, as soon as I copy the backports across, this will overwrite the existing files created by the kernel modules copy.

Is there any way of keeping both sets of modules... files so that they do not get overwritten when deployed to the target? Is there any benefit in keeping these files anyway?

Thank you

2

When doing modules_install in kernel and backports with the same modules directory it will generate single set of modules.* files. That way you can deploy entire folder /lib/modules/3.10.40-g19722d4 and not worry about it

3

Hi @dominik.tx, thank you for your answer. I automatically assumed that the files would be overwritten however it does appear that they are appended. Thank you