The above error, combined with this, indicates a bad starting configuration, and perhaps an incorrect install:
This reinforces the probability that configuration or install was not valid:
Below is a long URL with extended information on configuration and install:
https://forums.developer.nvidia.com/t/problem-smb-jetson-nano/193640/11
In that URL it does offer a “recipe” for native compile, but this would also apply to cross-compile if arguments and environment setup for cross-compile is merged in.
Some tips about cross-compile versus native compile:
- Cross-compile uses the “
ARCH=arm64”, but never use this for native build. - If you need to know about “
uname -r”, then always use the one from the Jetson, not the host PC. - The “
CROSS_COMPILE” environment variable is only used for cross-compile…don’t use this in native build, but do add this to each build line for cross-compile. - If you use the “
/boot/config.gz”, then this is the one from the Jetson. - In both cases it is a very common mistake to fail to correctly set the “
CONFIG_LOCALVERSION” to “-tegra”. This will lead to 100% failure of modules in most cases.
Note that if you just added a module (the “.ko” file), then I would not expect all of the other modules to fail. It is possible that if you added a module which was missing its own chain of dependencies, then this would occur, but I see this, which indicates “wxo.ko” was never added (and thus could not trigger a chain of dependencies):
Look carefully at that URL for how to configure prior to starting the build. Something in the configuration was incomplete before you started the build.
Here is a URL with further explaination related to build and install of kernels:
https://forums.developer.nvidia.com/t/jetson-nano-board-setup/163668/6