Dear Nvidia Team
We are currently upgrading all our platforms to Jetpack 7.2 (migrating from Jetpack 6 / Jetpack 7.1 across Orin Nano, NX, AGX, and AGX Thor).
Our workflow involves modifying the defconfig file located under the following directory and then building the image according to this procedure: Linux_for_Tegra/source/kernel/kernel-noble/arch/arm64/configs/
I am currently working with Jetpack 7.2 and encountered an issue after modifying the kernel configuration.
-
Behavior A (Normal): If I rebuild Jetpack 7.2 using the stock without any modifications, the system boots normally on the platform.
-
Behavior B (Abnormal): However, if I make any changes to the defconfig and recompile, the system fails to boot properly or encounters issues.
The exact same build steps were followed in both scenarios. Could you please clarify if the default defconfig provided in Jetpack 7.2 is the correct one corresponding to this platform?
Please refer to the attached image for the specific error symptoms:
— 🤖 This is an automated AI response. I’m here to help, but please verify important details! —
Based on the provided context, I found a relevant solution in the Community Solutions section.
The issue you’re experiencing, where modifying the defconfig file causes boot failure on Orin/Thor (Kernel-Noble), is likely due to the changes made to the kernel configuration.
According to the Community Solution from Topic #289181, when you modify the kernel configuration, you need to make sure that the CONFIG_LOCALVERSION is set up correctly for the situation. Additionally, you should create a copy of the /proc/config.gz file, which is an exact copy of the configuration of the running kernel, and use it as the configuration after editing CONFIG_LOCALVERSION.
Here’s a step-by-step solution:
- Create a copy of the
/proc/config.gz file: gunzip /proc/config.gz
- Rename the copied file to
.config: mv config .config
- Edit the
.config file to set up CONFIG_LOCALVERSION correctly: make menuconfig
- Save the changes and exit the menuconfig editor.
- Rebuild the kernel using the modified
.config file: make -j8 Image
Please note that you should be careful when modifying the kernel configuration, as it can affect the system’s stability and performance.
If you’re still experiencing issues, please provide more details about the error symptoms you’re encountering, and I’ll do my best to assist you further.
— We support team will also look into your issue to have further suggestions soon. please stay tuned. —
Dear carolyuu,
Sorry for the confusion, but my inquiry is specifically focused on developing from the source code.
I understand that /proc/config.gz is used to retrieve the kernel configuration from a running system. However, because I have several custom drivers that need to be ported, validating the source-based build workflow is critical for us.
This exact process worked perfectly fine in Jetpack 6.x and Jetpack 7.1. Has there been a change in the methodology or best practices for the current version (Jetpack 7.2)?
One way I’ve been using is on Orin or Thor run
zcat /proc/config.gz >defconfig
So I get everything in running kernel.
Then cp or scp/rsync to host if using host.
Then cp -p defconfig arch/arm64/configs/defconfig
Then if you are using
make ARCH=arm64 menuconfig to introduce your driver modifications?
You could run
make ARCH=arm64 olddefconfig
make ARCH=arm64 savedefconfig
cp -p defconfig arch/arm64/configs/defconfig
Here’s two files I modified that basically run the nvbuild.sh scripts to compile kernel, modules, dtbs.
jetpack72-download-extract.sh download every thing once into the directory from where it is run. It runs well on Thor. I’ve run it once on x86_64/amd64 host but did not test the modules.
When run on Thor it downloads and extracts gcc-13.2.0 binaries to use same compile binaries as Nvidia.
nvbuild-kernel-dtb-and-Modules.sh.txt (3.5 KB)
jetpack-download-extract.sh.txt (4.4 KB)
nvbuild-kernel-dtb-and-Modules.sh
Offers to just make modules or kernel, modules, dtbs.
And offers to run make menuconfig.
Then builds the chosen target.
