Did you do the strip work after you build the binary?
$ <tool_chain_path>/aarch64-linux-gnu-strip -–strip-unneeded <path-of-kernel-module.ko>
I think what you need to find out is why sometimes the nvgpu driver is not up. The dmesg does not provide any log of nvgpu. It seems not auto probe at all.
No, I didn’t execute the command.
We would also like to find out why “nvgpu” does not auto-load. Can you give us some advice on how to find out this reason?
Thanks,
BR,
Do you have this file in your filesystem?
/etc/modules-load.d/nv.conf
No, it’s not there:
nvidia@xavier-rt:/var/log$ ls /etc/modules-load.d/
cups-filters.conf modules.conf
nvidia@xavier-rt:/var/log$
Looks like that is the problem. How did you prepare your rootfs here? Are you using the sample rootfs from our website?
Yes, I used the example rootfs package of the official website, and then recompiled the kernel and module, without doing anything special.
How can I solve this problem?
BR,
Try to run apply_binaries.sh in Linux_for_Tegra before your recompiled kernel and module is installed. Check if nv.conf shows up in rootfs.
By the way, I added “/sbin/depmod -a” to the rc.local file, does this affect?
Hi WayneWWW,
Thanks very much for your replay!
I will try and test it ,thank you !
By the way ,“apply_binaries.sh” has been run before, should it be run every time?After each run, the user name must be reset when entering the system.
BR,