i get the following output…
info: Preparing to unpack …/nvidia-l4t-core_36.4.0-20240912 │
│ ││212859_arm64.deb … │
│ ││info: Pre-installing… skip compatibility checking. │
│ ││info: Unpacking nvidia-l4t-core (36.4.0-20240912212859) … │
│ ││info: Setting up nvidia-l4t-core (36.4.0-20240912212859) … │
│ ││info: Processing triggers for libc-bin (2.35-0ubuntu3.8) … │
│ ││error: qemu: uncaught target signal 11 (Segmentation fault) │
│ ││- core dumped │
│ ││error: Segmentation fault (core dumped) │
│ ││error: qemu: uncaught target signal 11 (Segmentation fault) │
│ ││- core dumped │
│ ││error: Segmentation fault (core dumped) │
│ ││error: dpkg: error processing package libc-bin (–install): │
│ ││error: installed libc-bin package post-installation script │
│ ││subprocess returned error exit status 139 │
│ ││error: Errors were encountered while processing: │
│ ││error: libc-bin │
│ ││error: [exec_command]: /bin/bash -c /home/nvidia/.nvsdkm/repl │
│ ││ays/scripts/JetPack_6.1_Linux/NV_L4T_FILE_SYSTEM_AND_OS_COMP. │
│ ││sh; [error]: libc-bin │
│ ││info: [ Package Install Finished with Error ]
my lsusb output
Hi,
If the device cannot be flashed/booted, please refer to the page to get uart log from the device:
Jetson/General debug - eLinux.org
And get logs of host PC and Jetson device for reference. If you are using custom board, you can compare uart log of developer kit and custom board to get more information.
Also please check FAQs:
Jetson AGX Orin FAQ
If possible, we would suggest follow quick start in developer guide to re-flash the system:
Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation
And see if the issue still persists on a clean-flashed system.
Thanks!
i gave a shot to the Ubuntu 20.04 SDK docker image and failed with the same error, I’m going to install Ubuntu 22.04 on the host and try again.
Hi,
Do you have Ubuntu 20.04 physical machine to install sdk manger?
Thanks
I’m working on having one.
i clean installed ubuntu 20.04 and ran the sdk manager, i got stuck at the device not detected although the device does show with lsusb command. not sure what to do, i think i will use it as it is for now.
Hi,
What is your flashing cable?
Is it a USB-C to AGX Orin, USB-B to host?
Make sure your cable supports data transfer.
Also try other cable to cross check whether issue exist.
Thanks
when using the cable that comes with the kit i get nothing with lsusb, when i use an old usb b cable i found i get Bus 005 Device 006: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
does that mean is data transfer supported? i’m working on getting another cable.
Hi,
Yes.
Please try to put your device in recovery mode.
Also refer to this doc to check whether the device is in recovery mode.
Thanks
finally got it working,i had to connect both usb c and tybe b cables and after that the device got detected, also i had to move the type c power close to the large 40 pin port, i was able to flash and got a completed message from the app but now i’m getting a black screen. adding the flashing log. i went for the nvme option since i had a samsung 980 pro 2tb nvme.
sdkm-2025-01-13-21-12-26.log (996.0 KB)
Hi,
You can use minicom to access device from host to check whether device flash successfully.
When you hotplug your flashing cable, you might find some ttyACM* info show in sudo dmesg.
For example, if you find ttyACM0 in dmesg.
You could try below commands to access it.
sudo minicom -D /dev/ttyACM0 -8 -b 115200
Thanks
my dmesg output
dmesg.log (163.8 KB)
Hi,
The below command might help you access
sudo minicom -D /dev/ttyACM0 -8 -b 115200
Also if you dont install minicom before please install first
Thanks
i was able to select the nvme drive for boot on a menu now running some jobs ( i had to connect a keyboard to hit f11 while looking at the minicom output on the host to access the boot options)
i figured out all my issues, i had to turn off my dell monitor and the agx device manually and start the device, then i had to select the device to boot, doing f11 then select the nvme drive to boot and then i got the ubuntu configuration screen.