I installed jetpack 5.1.x using sd card. Installation was successful but after boot there is no eth0 device inside /dev and not able to configure ip.
Ethernet devices don’t show up in “/dev” (although CANbus can, this is different). These occur with “/sys” exports for most cases.
Depending on software release one of these sets of commands will be of interest to you (I am excluding Wi-Fi commands in the first part of the list):
# older and my favorite:
ifconfig
route
# newer:
ip -s addr
ip route
I’m not really a Wi-Fi person, but the above will show some Wi-Fi devices (if active). Some other commands related to Wi-Fi:
rfkill
rfkill list
Someone else would have to help with wireless, but one of the things that confuses a lot of people is that Wi-Fi usually runs only from a GUI login, and is then owned by that user until they log out. Not being in the GUI, or having some detail about your login account not behave as expected, could lead to Wi-Fi also failing. You would have to provide more details about what you are doing and connecting for someone to help (and if it is Wi-Fi I can’t help).
Hi,
Thanks for the response. Please see the output of commands:
ifconfig ( If you see below output there is no eth0)
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:d7:4e:e9:dd txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 390 bytes 33317 (33.3 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 390 bytes 33317 (33.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
rndis0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 52:74:18:7a:31:51 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
usb0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 52:74:18:7a:31:53 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.219 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 2600:1700:453:10:e36e:ee85:f118:46b7 prefixlen 64 scopeid 0x0
inet6 fe80::a3cb:dd8d:acff:5f09 prefixlen 64 scopeid 0x20
inet6 2600:1700:453:10::1b prefixlen 128 scopeid 0x0
inet6 2600:1700:453:10:1e37:c3ef:6494:9d9f prefixlen 64 scopeid 0x0
ether b4:8c:9d:1c:56:15 txqueuelen 1000 (Ethernet)
RX packets 130469 bytes 105943555 (105.9 MB)
RX errors 0 dropped 16010 overruns 0 frame 0
TX packets 26937 bytes 7066353 (7.0 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default dsldevice.attlo 0.0.0.0 UG 600 0 0 wlan0
link-local 0.0.0.0 255.255.0.0 U 1000 0 0 wlan0
172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0
192.168.1.0 0.0.0.0 255.255.255.0 U 600 0 0 wlan0
also find lspci command output which does not show “ethernet controller”
0001:00:00.0 PCI bridge: NVIDIA Corporation Device 229e (rev a1)
0001:01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac PCIe Wireless Network Adapter
lab1@orin01:~/Downloads/etn$ cat /etc/nv_tegra_release
R35 (release), REVISION: 4.1, GCID: 33958178, BOARD: t186ref, EABI: aarch64, DATE: Tue Aug 1 19:57:35 UTC 2023
Wifi is working fine, problem is with wired connection, no IP system is able to take static or dynamic.
Regards,
Prashant
Please issue an ifconfig -a
ifconfig without -a only shows the interfaces currenty in use.
Please find the output of ifconfig -a:
ab1@orin01:/lib/modules/5.10.120-tegra/kernel/drivers/net/ethernet/intel$ ifconfig -a
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:b8:8b:ec:f2 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
dummy0: flags=130<BROADCAST,NOARP> mtu 1500
ether 12:fc:01:bc:8b:7a txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
l4tbr0: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 52:74:18:7a:31:51 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 996 bytes 84914 (84.9 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 996 bytes 84914 (84.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
rndis0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 52:74:18:7a:31:51 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
usb0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 52:74:18:7a:31:53 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.219 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 2600:1700:453:10::1b prefixlen 128 scopeid 0x0
inet6 fe80::a3cb:dd8d:acff:5f09 prefixlen 64 scopeid 0x20
inet6 2600:1700:453:10:f4c0:a655:4602:4dff prefixlen 64 scopeid 0x0
inet6 2600:1700:453:10:1e37:c3ef:6494:9d9f prefixlen 64 scopeid 0x0
ether b4:8c:9d:1c:56:15 txqueuelen 1000 (Ethernet)
RX packets 493046 bytes 765597650 (765.5 MB)
RX errors 0 dropped 61776 overruns 0 frame 0
TX packets 123122 bytes 13172963 (13.1 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Also attached dmesg log
dmesg.log (90.3 KB)
Is this an NVIDIA developer’s kit AGX Orin? Or does it use a third party carrier board?
It is NVIDIA developer’s ket AGX Orin.
I am not quite sure what you are saying.
The device tree name said you posted a log for Orin Nano …
I made some changes after that when I rebooted the machine, I could see eth0 interface but there is a difference in the lshw output. Attached, why do we have a difference after reboot?
The product in the lshw changed to “Jetson AGX Orin” from “NVIDIA Orin Nano Developer Kit”.
AfterChangesAndReboot.txt (10.6 KB)
BeforeChanges.txt (9.7 KB)
I can’t answer, but quite often the AGX version is created first, and any of the small form factor Nanos only come out later. The flash itself is capable of making some changes to make the AGX appear as a Nano for people who are getting ready to port software to Nano prior to it actually being available. Perhaps your system was originally flashed with a setting to make it look like an Orin Nano. Maybe.
How can I know the exact Linux kernel version used in Jetson Linux with different versions like r35.2, r35.3 and r35.4.
The document only says 5.10 but I need 5.10.120, so which version should I use?
I feel you didn’t notice that you already shared a log which includes the kernel version…
Dmesg will tell the kernel version…
BTW, if eth0 is working now, please file a new topic for your new question. We don’t really want you to use one topic to ask 100 different questions…
You can go here to find specific L4T releases, including links to documentation for that particular release:
https://developer.nvidia.com/embedded/jetson-linux-archive
Other than what that documentation has, I’m not sure what more specific information you might find. You could always download the driver package, unpack that as a regular user (which creates “Linux_for_Tegra/” and an empty “Linux_for_Tegra/rootfs/” subdirectory), then unpack the “sample root filesystem” with sudo in “rootfs/”, followed by running (from Linux_for_Tegra/) “sudo ./apply_binaries.sh”. This puts the basic L4T system in “rootfs/”. Actual flash will copy some content into “rootfs/boot/” prior to flash, but I think the kernel version of “rootfs/boot/Image” would be the same regardless of boot configuration. Other than that I do not know how to tell without actually having the Jetson flashed with that release.
uname -r will tell you the running kernel’s version. You might want to specify why you need this exact release of kernel.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.