Ethernet interface not showing up

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
1

Hi,

I am using the official agx orin devkit and I am using the stock dtb from 35.6.2. Secure boot is enabled. With this setup, I get the following errors:

dmesg | grep -i nvethernet
[ 9.858409] nvethernet 6810000.ethernet: Adding to iommu group 51
[ 9.864965] nvethernet 6810000.ethernet: failed to read skip mac reset flag, default 0
[ 9.873114] nvethernet 6810000.ethernet: failed to read MDIO address
[ 9.879664] nvethernet 6810000.ethernet: setting to default DMA bit mask
[ 9.886574] nvethernet 6810000.ethernet: failed to read UPHY GBE mode- default to 10G
[ 10.287806] nvethernet 6810000.ethernet: No MAC address in local DT!
[ 10.294341] nvethernet 6810000.ethernet: failed to get MAC address
[ 10.302661] nvethernet: probe of 6810000.ethernet failed with error -22

In particular it fails to read the MDIO address and there is No Mac address in local DT. Can you confirm that EEPROM should appears on bus 7?

sudo i2cdetect -y -r 7
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – – – – – – – – – – – – –
10: – – – – – – – – – – – – – – – –
20: – – – – – – – – – – – – – – – –
30: – – – – – – – – – – – – – – – –
40: – – – – – – – – – – – – – – – –
50: – – – – – – – – – – – – – – – –
60: – – – – – – – – – – – – – – – –

It is empty, which look strange.

Could it be an hardware fault? I have seen similar references where NVIDIA’s own diagnosis of a failed PHY/EEPROM subsystem requiring board replacement.

Please advice

Thanks

3

Has this system received a fresh Jetpack and Linux installation via SDKManager? Has there anything been altered?

4

No, deployment was made using flashing scripts not using the SDK.

5

The original, unmodified NVidia scripts from the L4T folder?

So a standard unmodified Jetpack/L4T installation?

6

Yes, standard stuff

7

This looks more like a problem from the EERPOM as MAC address should be present by the UEFI during boot (reading from CVM EEPROM).

[ 10.287806] nvethernet 6810000.ethernet: No MAC address in local DT!
[ 10.294341] nvethernet 6810000.ethernet: failed to get MAC address
[ 10.302661] nvethernet: probe of 6810000.ethernet failed with error -22

Please share me the full boot up log from UART.

9

Please find full logs in attachment.

Thanks

putty-may4.log (125.7 KB)

10

Are you sure you didn’t disable something in your setting? It looks like UEFI and kernel are self-built.

DTB build time is also not the default setting with rel-35.6.2 which was released in May, 2025.

11

Yes, we rebuilt them!

12

Hi,

What do you have in your /proc/device-tree/chosen/ directory?

13

board-has-eeprom linux,initrd-end linux,uefi-mmap-start

bootargs linux,initrd-start linux,uefi-system-table

framebuffer linux,uefi-mmap-desc-size name

ids linux,uefi-mmap-desc-ver nvidia,sku

kaslr-seed linux,uefi-mmap-size

14

Hi,

Are you sure your UEFI and UEFI dtb has MGBE node enabled?

From your UEFI log, it looks like not present. If UEFI driver for EQOS is not present, the MAC addr would be missing and then kernel side is not able to proceed.

15

Hi Wayne,

I saw that you asked another developer to dump some values ( Unable to bring up ethernet service and fail to flash on Jetson AGX Orin - #15 by WayneWWW ) then ask for RMA process. Can you check my values to see if I am in the same situation?

Thanks

root@erxbot-uuu-u:/home/nvidia# i2cdump -f -y 0 0x560

No size specified (using byte-data access)

0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef

00: 02 00 fe 00 00 00 00 00 00 00 00 00 00 00 00 00 ?.?..

10: 00 00 00 0a 36 39 39 2d 31 33 37 30 31 2d 30 30 …?699-13701-00

20: 30 30 2d 35 30 30 20 4a 2e 30 00 00 00 00 00 00 00-500 J.0…

30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …

40: 00 00 00 00 c2 fc 83 2d b0 48 31 34 32 32 31 32 …???-?H142212

50: 32 31 30 31 35 32 31 00 00 00 00 00 00 00 00 00 2101521…

60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …

70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …

80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …

90: 00 00 00 00 00 00 4e 56 43 42 00 00 4d 31 00 00 …NVCB..M1..

a0: 00 00 00 00 00 00 00 00 00 00 00 00 c2 fc 83 2d …???-

b0: b0 48 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 ?H?..

c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …

d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …

e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …

f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 be …?

root@erxbot-uuu-u:/home/nvidia# i2cdump -f -y 0 0x506

No size specified (using byte-data access)

0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef

00: 02 00 fe 00 00 00 00 00 00 00 00 00 00 00 00 00 ?.?..

10: 00 00 00 0a 36 39 39 2d 31 33 37 33 37 2d 30 30 …?699-13737-00

20: 30 30 2d 34 30 30 20 48 2e 30 00 00 00 00 00 00 00-400 H.0…

30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …

40: 00 00 00 00 00 00 00 00 00 00 31 34 32 32 31 32 …142212

50: 32 30 37 37 32 31 30 00 00 00 00 00 00 00 00 00 2077210…

60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …

70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …

80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …

90: 00 00 00 00 00 00 4e 56 43 42 00 00 4d 31 00 00 …NVCB..M1..

a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …

b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …

c0: 00 00 00 00 00 00 00 00 36 37 35 2d 31 33 37 33 …675-1373

d0: 30 2d 30 30 30 30 2d 30 30 30 00 00 00 31 34 32 0-0000-000…142

e0: 32 32 32 32 30 38 32 37 30 30 00 00 00 00 00 00 2222082700…

f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d5 …?

16

No, the error here is totally different. Your error does not have anything to do with RMA…

You need to answer my previous question. That is the only problem I saw for your case.

The only issue I saw from your side now is your MAC address is gone.

17

Here is the UART log using the provided uefi binary from Nvidia: Jetson UEFI firmware (version 6.2-40633251 built on 2025-05-16T01:35:20+00:00)

putty-6may.log (94.1 KB)

18

Indeed with this one I do get ethernet. Thanks I need to dig in to see what could cause this problem with our custom build.

Thanks