Everything go smoothly from downloading files to building process. To the state of rebooting the jetson, After the NVIDIA splash screen, it shows nothing.
I tried to reboot jetson. It then boot up to ubuntu desktop, and setup. But the log is really strange. After some loading, it show the blank desktop.
Ok I check the router, it is a home network so I pretty sure that it not blocking anything. I connect jetson to router using ethernet cable, and the USB-C serial port to host machine. All connect to the same router, same network.
Then I run the ssh root@fc00:1:1:0::2 command and it’s timed out. So I check the network address of the jetson devkit
Yes, I checked and use the right port - the one next to 40-pin header before plug into the jetson. I also have a SSD drive attached to jetson. Booting from eMMC or external SSD drive not working right now.
For more detail, here the current behavior of the jetson. I power it on → booting (either from eMMC or external SSD), when it show the ubuntu’s desktop screen it will enter the oem config. After the step of entering username and password, it runs some setup and the setup window is gone. Leave it the blank screen. At that time, I can start a terminal session as root, user I just entered is not created (as you can see like the image I sent above). I have tried to start the ssh service, it start successfully but my machine cannot connect to it using ssh (with the address obtained from the command show in the image above). It kind of struggling in some state that I don’t know.
I tried to flash several times with both eMMC and SSD, but the same result happened. Each time it takes couple hours so it really time cosuming.
I haven’t with flashing using command line, may be I will try that. But I have a small question: How does the flashing script get this address - fc00:1:1:0::2?
This time, after using command line on host machine (command sudo ./flash.sh jetson-agx-orin-devkit internal) to flash again. I look at the boot, It go from 36.2 to 36.3. So the kernel is updated. OK!
In step install SDK component, it cannot connect to jetson via ssh.
I have unplugged the ethernet cable, leaving only the USB-c serial port. And for sure on my host machine, I turn off wifi and ethernet as well, leaving the serial port as the only connection. I checked the proxy and make sure to disable the proxy as well.
I try enter both my created user and root user but no luck.
This is just a simple trick to isolate some factors to make sure when I debug, it is not the cause. I can connect to network when needed, not a big deal. The concern is jetson cannot install sdk component. As you can see in the image, the internet connection and physical wiring is NOT a problem.
The message shows that the the apt repository. What could be the cause and how can we fix it? Do you have any suggestion?
You will see in the image, the sdk manager stated clearly that the internet connection is ok. I personally ssh to jetson and check, both local network (via USB-C) and internet (ethernet port) is ok. The jetson module can ping to some hosts like google, nvidia,…
Again if you look in the image at the bottom, you will see the message sudo: /etc/sudo.conf is world writable sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
This propably the cause. Because I cannot execute command with sudo. In ssh command line, the response show exactly this. Just to be clear, the network is not being blocked by proxy or anything else.
I cannot execute the command sudo apt-get update or any command require sudo.
So you are saying that you flash your device with our default BSP, and you cannot use anything require sudo on the device?
I still have no idea what you are doing now. That should not be the case.
I use a different host machine (ubuntu 20.04) to rollback to jetpack 5.1.3 and it works seamleassly. When first boot, it will disables core 8 to 12. I solve this using command provided by WayneWWW’s answer in this post.
May be I will stick to this version and focus on application development.
Meanwhile, I will keep searching around and deal with this problem when I have more free time.
