You can do a lot of change on your host… but if you didn’t put the new kernel image into the right location and flash to the board, then your kernel image is always previous one…
New kernel image should be put to Linux_for_Tegra/kernel/Image so that it will be updated.
You can also read the sudo dmesg on your jetson. The kernel build time will tell you if this is the kernel you just built out…
In the following command?
sudo ./apply_binaries.sh
Or do you mean the module installation command?
sudo make ARCH=arm64 modules_install INSTALL_MOD_PATH=/{BSP Directory}/Linux_for_Tegra/rootfs
These two didn’t change the kernel image at all.
Please be sure that you know what are kernel image and what are kernel modules…
There has to be an error somewhere in the actual procedure. Can you provide a full serial console boot log, plus the “/boot/extlinux/extlinux.conf”? This might shed a clue.
Incidentally, it is usually incorrect to use the same “CONFIG_LOCALVERSION” if you are removing or changing an “=y” parameter. Instead of “-tegra” you might consider something like “-ncm_mod”. Then you would install both kernel and new modules. The output of “uname -r” would change to use the extension “-ncm_mod”, and the new module directory would be: /lib/modules/$(uname -r)/kernel
(where you would put all modules from the new build without reusing the “-tegra” modules)