Ethernet port (eth0) not working after Jetpack 4.6.3 update

[cesar7gouveia7]

System Information

Device: Developer Kit Jetson TX2
JetPack previous version: 4.2.2 (rev. 1)
JetPack version that I want to update: 4.6.3

Detailed description

Hey guys,

I was trying to update my Developer Kit Jetson TX2 from JetPack 4.2.2 (rev.1) to 4.6.3, for that I used the NVIDIA SDK Manager, and choosed Manual Install:

Flash goes smothly and after that, TX2 gets rebooted automatically and this screen appears:

Waited for like forever and this screen does not go away and installation does not start. So I just rebooted TX2 again manually (by taking the power off) and after that the ubuntu installation starts. Normal ubuntu installation and after a final reboot, the system initiates normally, however I see that I have no eth0 device connected by using “nmcli d”. Moreover, the physical ethernet port appears to not be working (no orange and green lights blink at the physical port). Has someone experienced this issue after updating the JetPack image?

This is the output of “nmcli d” after the update:

Things I have tried already:

• Tested with other Jetpack 4.6.* versions and the same issue occurs;
• Tried to flash a second time and the same issue occurs.

Thanks for your help,
César.

[KevinFFF]

Hi cesar,

Do you have ethernet cable connected?

Could you help to provide the result of ifocnfig -a on your devkit?

Please also provide the dmesg for further check.

[cesar7gouveia7]

Hey Kevin, thanks for your response.

Do you have ethernet cable connected?
Yes

Please also provide the dmesg for further check.

You can see by the image that there is a failed to load after recognizing the network driver.

[WayneWWW]

Try to provide full log as text file. Such screenshot really not helps…

[cesar7gouveia7]

In a few minutes I’ll give you the full logs, this was just to speed up the process and show you the problem since I don’t have acess to network in the board.

[cesar7gouveia7]

Logs for dmesg, ifconfig and lsmod:

OneDrive_1_14-02-2023.zip (92.7 KB)

[WayneWWW]

Hi,

Your kernel dtb does not match the version of kernel image.

[ 0.161552] DTS File Name: /home/simon/R32.2.1/kernel/kernel-4.9/arch/arm64/boot/dts/…/…/…/…/…/…/hardware/nvidia/platform/t18x/quill/kernel-dts/tegra186-quill-p3310-1000-c03-00-base.dts

If you don’t know the reason, then I can share out some possible reasons to you. But all of them depend on yourself to check.

[cesar7gouveia7]

I have no ideia why this is happening, I’m installing and flashing the system through the sdk manager, so all these details should be transparent to the user I would say.

Off course, please share the possible reasons, I want to have them all checked. Thanks for your attention. I’m looking forward to your reply.

[WayneWWW]

Most likely case: sdkmanager may install the BSP to somewhere else, but where the dtb got loaded is not same as where sdkm installed.

Please check if you have any external device there that may have some old BSP inside of it.
Also, dump the serial console log. The bootloader log would tell us why a R32.2.1 dtb got loaded.

[linuxdev]

I’ll also suggest, in addition to serial console boot log, posting the content of “/boot/extlinux/extlinux.conf”, and stating where it is from (e.g., eMMC or external device or SD card, so on).

[cesar7gouveia7]

Well, I just managed to fix the issue by reinstalling the sdk on a new ubuntu machine, and just installed a single version of jetpack in that sdk manager. The SDK manager supports multiple installed versions right? Altought I managed to fix my issue, I want to have my sdk manager with the possibility of having multiple versions of jetpack, so that I can install different versions for different devices, so I will send you throughout the week the logs you asked.

Thanks.

[linuxdev]

Yes, SDKM supports multiple releases. You would start it like this to see older releases:
sdkmanager --archivedversions
(but the 5.x JetPack won’t support anything older than Xavier, so mostly you are going to install the newest of the 4.x JetPack releases, and then start with --archivedversions)