-
Hi. I found out that the kernel modules installed in my image are much larger than NV stock ones. NV L4T kernel modules only take up ~88MB space, while mine take up ~2.0GB. Is there any config affecting this? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
I hadn't noticed this before, but the problem is that starting with JetPack 5, NVIDIA changed the default kernel config to set There are a couple of ways this can be fixed. I'm leaning towards disabling |
Beta Was this translation helpful? Give feedback.
I hadn't noticed this before, but the problem is that starting with JetPack 5, NVIDIA changed the default kernel config to set
CONFIG_MODULE_SIG
andCONFIG_MODULE_SIG_ALL
. The latter is causing kernel modules to get signed as part of the build process (specifically, during thedo_install
task), and so the normal debug info stripping that would happen during packaging gets skipped (because that would invalidate the signature).There are a couple of ways this can be fixed. I'm leaning towards disabling
CONFIG_MODULE_SIG_ALL
in our builds by default. In the meantime, you could do this yourself via a bbappend by adding a config fragment to the SRC_URI that says# CONFIG_MODULE_SIG_ALL is not set