Hello,
I was just working with my Jetson TX2 and suddenly the ubuntu desktop freezed and I am getting a black tty screen,
I tried to follow some possible solutions from the Internet, Including reboot and installing the NVIDIA graphics drivers but it displays,
that package is not available or command not found.
How can i get back to my Ubuntu desktop and is it like the files will be recovered.![]()
https://mail.google.com/mail/u/0?ui=2&ik=4a9b11027e&attid=0.1.1&permmsgid=msg-f:1613844610731001772&th=1665871f794cc7ac&view=fimg&sz=s0-l75-ft&attbid=ANGjdJ-H0bBO-DTqfzzIaUb_ywSxyF-PeteYaDM1kSFzsU8qhP_aleY3EEM81QrUhzkYA7YaqbI21VVnQyJzp3xpuk4p0V44obWJTXKOFR9lXoh_dyMA8a3t2RyMFm0&disp=emb
FYI, regular drivers from the internet will not work with a Jetson. They are for a different architecture, and for PCIe based cards…a TX2 is arm64/aarch64, and the GPU integrated directly into the memory controller.
Have you flashed the Jetson? The initial release they ship with is rather unreliable. Newer releases are far more reliable. If you have not flashed, then this URL is what you would be interested in:
[url]https://developer.nvidia.com/embedded/linux-tegra-r2821[/url]
You can either flash on command line using any host Linux PC (desktop architecture, not another embedded system) and the driver package plus sample rootfs, or else use JetPack. JetPack is a front end to this and does the driver package and sample rootfs download for you, and then a number of steps are done for you. At times it can be more complicated because the host must then be Ubuntu, but it also offers adding optional developer packages to both host and Jetson.
Thank you for the Information, I have thought of doing the same thing, but is there any possibility that the data I have in the NVIDIA can be recovered?
Also the second problem currently I am facing is after downloading and installing JetPack in the Host PC, when I am putting the TX2 in the force recovery mode I am just getting a complete black screen with no further information to proceed for the deployment.
Can you please help me with the same too?
This is what happening
The problem is the system is failing to start the light display manager
Please provide a solution
sudo systemctl enable lightdm.service
this works
sudo systemctl start lightdm.service
Job for lightdm.service failed because the control process exited with error
code. See “systemctl status lightdm.service” and “journalctl -xe” for details.
Lightdm service status
lightdm.service - Light Display Manager
Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; vendor preset: disabled)
Active: inactive (dead) (Result: exit-code) since sam. 2016-04-16 15:36:54 CEST; 12 minutes ago.
Docs: man:lightdm(1)
Process: 2073 ExecStart=/usr/bin/lightdm (code=exited, status=1/FAILURE)
Main PID: 2073 (code=exited, status=1/FAILURE)
There are a lot of reasons why lightdm might not start. One possibility is running out of disk space. Some people fail to change the password before putting it on a publicly accessible network. Regardless of why it failed you can save a copy of the root partition by cloning it. Basically it comes down to this (however, instructions do vary depending upon release…you might want to say what release you are working with if this fails):
- Put the TX2 in recovery mode.
- Attach the micro-B USB cable to the Linux PC host which has the driver package installed (a previous use of JetPack would put this in place, or you can download the version which is the same as the Jetson's current version...see https://devtalk.nvidia.com/default/topic/1000105/jetson-tx2/tx2-cloning/). Verify your host PC can see the Jetson:
lsusb -d 0955:7c18
- Find file "Linux_for_Tegra/flash.sh" from your driver package or a previous use of JetPack.
- From the location of flash.sh be sure you have about 35GB of free space available:
df -H .
- Run the clone procedure with "sudo".
- Under R28.2 it goes something like this:
sudo ./flash.sh -r -k APP -G my_backup.img jetson-tx2 mmcblk0p1
Or with logging:
sudo ./flash.sh -r -k APP -G my_backup.img jetson-tx2 mmcblk0p1 2>&1 | tee clone_log.txt
- Verify you have both a ".img" and ".img.raw" version of this backup file.