I’m experiencing issues when trying to reinstall JetPack on my NVIDIA Thor.
Initially, I performed a successful installation, but now I want to reinstall JetPack from scratch. However, when attempting to do so, I encounter a problem where the screen gets stuck displaying the following message:
EFI stub: Booting linux kernel…
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Measured initrd data into PCR 9
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services…
The system freezes on the last line and does not proceed further.
To debug further, please record the serial console log:
We also recommend installing SDK Manager to perform a full device flash using native Ubuntu 22.04 later. Please refer to the following SDK Manager | NVIDIA Developer.
Thank you very much for your response. When accessing the console log via the serial connection, I see the following errors at the end:
Start: subiquity/Meta/status_GET:
An error occurred. Press enter to start a shell.
Additionally, I have tried booting from the SDK, but it never detects the NVIDIA Thor, even though I remain connected through the USB port used to get the console logs.
Before attempting the SDK set-up, I follow this procedure:
Power off the Thor
Turn it back on and immediately press the recovery button (the middle one)
While holding the recovery button, press the “restart” button (the one opposite the power button)
There’s your sdkmanager problem. The top/highest usbc slot is only for debug/logs.
For flashing, usbc cable must be in the usbc slot next to the power usbc cable. Then restart while briefly holding middle button. If lsusb still doesn’t add nvidia usb listing, then swap the two usbc cables to the opposite slots.
Hello, I have followed all the steps, but I’m still unable to get the host to detect the NVIDIA Thor. I’m attaching some images to show that I’ve tested both USB ports, as well as the output of lsusb on the host machine (both cases generate the same result). Additionally, I’ve included the steps I followed to enter recovery mode. I’ve noticed that when performing this procedure, there isn’t output visible via DisplayPort.