Orin NX 16gb r36.3 problem with assign static MAC address on usb ethernet (lan7850)

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
,
1

Hello nvidia support team,
I use Orin NX with Jetson Linux R36.3 and also custom carrier board with two ethernet interfaces:
eth0 pcie
eth1 usb (lan7850 chip)

I have problem with usb eth1. After each power up cycle the system assign random MAC address for eth1.

In try to fix it I modified lan78xx driver to use only constant MAC 86:a3:7f:97:15:c8
Now after each boot up I check lan7850 register values and I see it use value 86:a3:7f:97:15:c8
But despite this the system still use random MAC at each power up.

If I reload lan7850 driver:
sudo rmmod lan78xx
sudo insmod lan78xx

the system getting correct mac address value 86:a3:7f:97:15:c8 for eth1

Do you have any ideas how to fix problem with random mac at power up?

nvuser@localhost:~$ ifconfig

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::cf7d:aae6:7cf0:b01b  prefixlen 64  scopeid 0x20<link>
        ether 92:4e:21:a8:97:8a  txqueuelen 1000  (Ethernet)
        RX packets 4  bytes 240 (240.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 23  bytes 3826 (3.8 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

nvuser@localhost:~$ sudo rmmod lan78xx
nvuser@localhost:~$ sudo insmod lan78xx.ko
nvuser@localhost:~$ ifconfig

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.137.3  netmask 255.255.255.0  broadcast 192.168.137.255
        inet6 fe80::41bd:44b6:2e3c:17b7  prefixlen 64  scopeid 0x20<link>
        ether 86:a3:7f:97:15:c8  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 20  bytes 2488 (2.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
3

This is not NV support scope. This is vendor driver behavior. Checking the dmesg might help clarify that.

4

Seeing this , it looks like.the ethernet driver is not getting loaded properly on boot up and you need to manually load the driver with insmod.

Put these insmod command inside some initial boot.up script like rc. local inside /etc folder and reboot the check.
It should work most probably…

6

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.