Hi,
kernel modules in .ko files format that are provided with the file system and are not reloaded during kernel compilation, such as the .ko files for display modules. In the rt-Linux version, these files may have different symbols due to the lack of compilation, which can cause them to fail to load,how to handle this situation?
You need to install not only kernel image but also kernel modules.
https://docs.nvidia.com/jetson/archives/r35.4.1/DeveloperGuide/text/SD/Kernel/KernelCustomization.html#to-build-the-real-time-kernel
I want to add that every module should be compiled against the same kernel source code and when that source code is configured the same for both Image and module build. In part this implies you should be using a consistent “CONFIG_LOCALVERSION” string. The source code release version, in combination with the CONFIG_LOCALVERSION, determines the output of the command “uname -r”, and modules which are compatible with that kernel Image are expected to be in a subdirectory of:
/lib/modules/$(uname -r)/kernel
This means you cannot reuse the old original modules because (A) the source code changed, (B) the configuration changed, and (C) the CONFIG_LOCALVERSION changed. If any one of those changed you’d want to rebuild everything, and in this case, all of them have changed.
Reusing any of the original “/lib/modules/$(uname -r)/kernel” directory would be incorrect for this case.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.