Eth1 is not showing up

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
1

I have an Jetson AGX Orin 32GB H01 Kit, i can see my eth0 but not the eth1.

I bought one last year and I can see both eth0 and eth1 just fine.

The differences is maybe that the older Jetson have JetPack build 5.10.120-tegra and the new one have JetPack build 5.10.216-tegra.

Thanks !

2

*** Please note that this reply is generated by LLM automatically ***

Based on the provided context, it appears that you are experiencing an issue with the Jetson AGX Orin 32GB H01 Kit, where you can only see the eth0 interface but not the eth1 interface. You have also mentioned that you have an older Jetson AGX Orin kit from last year, which has both eth0 and eth1 interfaces visible.

To troubleshoot this issue, let’s first understand the differences between the two kits. The older kit has a 510120tegra version, while the new kit has a 510216tegra version. This suggests that there might be some changes in the hardware or software configuration between the two versions.

However, based on the provided context, there is no specific information about the differences between the two versions. Therefore, we can only make some general suggestions to troubleshoot the issue.

  1. Check the hardware configuration: Ensure that the Ethernet ports are properly connected and configured on the new kit. Verify that the Ethernet cables are securely plugged in and that the ports are enabled in the BIOS settings (if applicable).
  2. Check the software configuration: Verify that the network interfaces are properly configured in the operating system. Check the network settings and ensure that the eth1 interface is enabled and configured correctly.
  3. Check the kernel version: Ensure that the kernel version on the new kit is compatible with the Ethernet interfaces. You can check the kernel version by running the uname -r command.
  4. Check the device tree: The device tree might have changed between the two versions, which could affect the visibility of the eth1 interface. You can check the device tree by running the dtc -I fs /sys/firmware/devicetree command.

To further troubleshoot the issue, you can try the following:

  1. Check the system logs: Check the system logs for any error messages related to the eth1 interface. You can use the dmesg command to view the system logs.
  2. Run a network diagnostic tool: Run a network diagnostic tool, such as ethtool or mii-tool, to check the status of the eth1 interface.
  3. Try a different Ethernet port: Try using a different Ethernet port on the new kit to see if the issue is specific to one port.

If none of these suggestions help, you may want to consider contacting NVIDIA support for further assistance, as the issue might be specific to the new kit or the 510216tegra version.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

3

Thank you for your reply.

I have already checked all the points you mentioned. Here is what I found:

Hardware: Both Jetsons are identical — Jetson AGX Orin Developer Kit (p3737-0000+p3701-0004)

Key finding: The difference is in the DTB files between the two kernel versions:

  • Old Jetson (5.10.120-tegra): DTB contains ethernet@2310000 with status = "okay" → creates eth0 (1Gbps) and eth1 (100Mbps)

  • New Jetson (5.10.216-tegra): DTB is completely missing ethernet@2310000 → only eth0 (5Gbps) exists

The ethernet@2310000 controller is entirely absent from the new kernel’s DTB, which is why eth1 never appears.

My question: Is it safe to copy the old Jetson’s DTB file (kernel_tegra234-p3701-0004-p3737-0000.dtb) to the new Jetson and boot with it to restore eth1? Or is there a proper device tree overlay method that works with the Jetson bootloader (extlinux) to add ethernet@2310000 back?

Thank you!

5

Hi,

I feel that you ask this question in a wrong place.

I have an Jetson AGX Orin 32GB H01 Kit,

This carrier board is not a NV devkit but a custom carrier board. NV devkit does not have 2 ethernet ports enabled by default but only the MGBE one. The RGMII interface is not present on the NV devkit hardware at all.

Your carrier board could not be flashed with any software (Jetpack) that NV provided by default because of above reasons. We actually didn’t enable RGMII in any of our Orin AGX devkit software. If you flash the board with pure Jetpack software, then it will of course not enable the interfaces on your custom board.

Key finding: The difference is in the DTB files between the two kernel versions:

  • Old Jetson (5.10.120-tegra): DTB contains ethernet@2310000 with status = "okay" → creates eth0 (1Gbps) and eth1 (100Mbps)
  • New Jetson (5.10.216-tegra): DTB is completely missing ethernet@2310000 → only eth0 (5Gbps) exists

Above finding only indicates that your software 5.10.120 was a custom software from a vendor and you probably flashed your board again with our default software. This makes RGMII interface disabled which is totally expected.

The correct way here is contact the board vendor and get their customized BSP to flash your board. But not totally relying on NV Jetpack.

If you don’t understand anything points above, please tell instead of doing something without full understanding.