I have flashed the board and install Ubuntu using Nvidea SDK Manager with
DeepStram Version: 5.1
Jetpack Version: 4.5.1
and create the image and install in another TX2 but not able to detect the eth0 port in TX2
aiu@aiu-desktop:~$ ifconfig
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:a9:7d:81:2e 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
l4tbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.55.1 netmask 255.255.255.0 broadcast 192.168.55.255
inet6 fe80::c077:bff:feb5:d51 prefixlen 64 scopeid 0x20
inet6 fe80::1 prefixlen 128 scopeid 0x20
ether c2:77:0b:b5:0d:51 txqueuelen 1000 (Ethernet)
RX packets 5210 bytes 856838 (856.8 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2599 bytes 450886 (450.8 KB)
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 1 (Local Loopback)
RX packets 15009 bytes 852134 (852.1 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 15009 bytes 852134 (852.1 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
rndis0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::c077:bff:feb5:d51 prefixlen 64 scopeid 0x20
ether c2:77:0b:b5:0d:51 txqueuelen 1000 (Ethernet)
RX packets 3740 bytes 526339 (526.3 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 915 bytes 146568 (146.5 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::c077:bff:feb5:d53 prefixlen 64 scopeid 0x20
ether c2:77:0b:b5:0d:53 txqueuelen 1000 (Ethernet)
RX packets 1569 bytes 353430 (353.4 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3748 bytes 826504 (826.5 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.116 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::d8ca:7554:86f1:2419 prefixlen 64 scopeid 0x20
ether 48:b0:2d:0f:5e:3f txqueuelen 1000 (Ethernet)
RX packets 13282 bytes 7836640 (7.8 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 11047 bytes 1887131 (1.8 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
For this i am using Tegra186_Linux_R32.4.4_aarch64
Image Creation Steps:
sudo ./flash.sh -r -k APP -G system.img jetson-tx2 mmcblk0p1
Image Installation Steps:
sudo ./flash.sh -r -k APP jetson-tx2 mmcblk0p1
While using this version its working success
DeepStram Version: 5.0
Jetpack Version: 4.5
I have Tested in 4 TX2 Systems but In 2 TX2 it’s working properly and In 2 TX2 it’s not working properly.
What is the exactly software version you are using? Why do you use a 32.4.4 version on jp4.5.1 and jp4.5?
32.4.4 is for jetpack4.4.1.
I am using the 32.5.1 version and face this Issue
For this i am using Tegra186_Linux_R32.4.4_aarch64
Image Creation Steps:
sudo ./flash.sh -r -k APP -G system.img jetson-tx2 mmcblk0p1
Image Installation Steps:
sudo ./flash.sh -r -k APP jetson-tx2 mmcblk0p1
Then could you explain what is above comment talking about? This is from your comment.
Steps1: I am Download this file and unzip it on the host machine. https://developer.nvidia.com/embedded/L4T/r32_Release_v4.4/r32_Release_v4.4-GMC3/T186/Tegra186_Linux_R32.4.4_aarch64.tbz2
Step2: Go to the Linux_for_Tegra folder and run this sudo ./flash.sh -r -k APP -G system.img jetson-tx2 mmcblk0p1 command for create the image
Step3: move the system.img file in the Linux_for_Tegra/ bootloader folder
Step4: connect another TX2 using the USB and run this sudo ./flash.sh -r -k APP jetson-tx2 mmcblk0p1 command to install the system image file in another tx2
For all the steps I am using tx2 in recovery mode
Looks like you don’t understand that I want you to check your step one.
You are using jetpack4.5.1, good. But then you download a zip file with r32.4.4… Please align the version first.
previously I am using 32.4.4 and all are working fine.
but after upgrading the 32.5.1 when I install the image file in another TX2 and after successfully installation ethernet cable is not detected.
when I am checking using ifconfig I am not getting any eth0.
Hi,
Then could you describe your steps again how do you reproduce this error on your jetpack4.5.1 ?
I just want to clarify this: Do you use Tegra186_Linux_R32.4.4_aarch64.tbz2 in this issue or not?
No, there is no issue Tegra186_Linux_R32.4.4_aarch64.tbz2 in this.
Ok, so make a summary,
r32.4.4 → eth0 working fine.
r32.5 → eth0 working fine.
r32.5.1 → eth0 NG.
Is this correct?
Could you share the dmesg for your r32.5.1?
And could you correct your previous comment to the right package?
If below steps cannot reproduce issue, then it is not helpful here. Please correct it.
Steps1: I am Download this file and unzip it on the host machine. https://developer.nvidia.com/embedded/L4T/r32_Release_v4.4/r32_Release_v4.4-GMC3/T186/Tegra186_Linux_R32.4.4_aarch64.tbz2
Step2: Go to the Linux_for_Tegra folder and run this sudo ./flash.sh -r -k APP -G system.img jetson-tx2 mmcblk0p1 command for create the image
Step3: move the system.img file in the Linux_for_Tegra/ bootloader folder
Step4: connect another TX2 using the USB and run this sudo ./flash.sh -r -k APP jetson-tx2 mmcblk0p1 command to install the system image file in another tx2
For all the steps I am using tx2 in recovery mode
dmesg.log (179.1 KB)
r32.4.4 → eth0 working fine.
r32.5 → eth0 working fine.
r32.5.1 → eth0 NG.
It’s correct.
Please also reply my last comment. I really want to clarify what are the steps to reproduce issue.
Yes, steps are correct but its come frequently in some TX2 its working and some not
for this i am connecting TX2 using the USB to connect with host machine.
In host machine i am using Ubuntu 18.04.5 LTS in virtual-machine.
Hi,
Then what you are doing is wrong… We are in a loop now.
You should not use Tegra186_Linux_R32.4.4_aarch64.tbz2 to do the clone work for 32.5.1. You should use the driver package from 32.5.1. but not 32.4.4…
If you still cannot understand what I am talking about, please tell.
Also, we don’t support VM, please find a native host to prevent unnecessary bug.
I am not able to understand what you are talking about.
Please tell me what is this file doing in your step.
I am using this file for creating and installing system.img file in TX2
Yes, but this package, as its name, is for r32.4.4 which is jetpack4.4.1. You should not use this package to creating and install system.img for rel-32.5.1 which is jetpack4.5.1.