Black screen white cursor after upgrade, boot on SSD


I have upgraded my Jetson Agx Xavier dev kit, with boot from SSD, from version 35.2.1 to version 35.3, with sudo apt-get dist-upgrade. And now it doesn’t boot, the screen stays black and the cursor blinks, I can access the boot device selector, but once the boot starts, the screen stays black with the white cursor blinking, what can I do?

From what @sudash has told me the update with apt upgrade has been the problem as the boot with SSD is not supported.

You can use the serial console to access the board and share me the dmesg first.

minicom_output.log (57.7 KB)

This is the minicom output from the start of the jetson. I think this is interesting:

[ 7.544317] Freeing unused kernel memory: 3968K
[ 7.544549] Run /init as init process
WARNING: clock_disable: clk_power_ungate on gated domain 27 for gpcclk
[ 7.591142] Root device found: initrd
[ 7.592524] Mount initrd as rootfs and enter recovery mode
Finding OTA work dir on external storage devices
Checking whether device /dev/mmcblk?p1 exist
Looking for OTA work directory on the device(s): /dev/mmcblk0p1
Checking whether device /dev/sd?1 exist
Device /dev/sd?1 does not exist
Checking whether device /dev/nvme?n1p1 exist
Looking for OTA work directory on the device(s): /dev/nvme0n1p1
[ 7.673013] EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
OTA work directory /mnt/ota_work is not found on /dev/nvme0n1p1
Finding OTA work dir on internal storage device
[ 7.727956] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
OTA work directory /mnt/ota_work is not found on /dev/mmcblk0p1
OTA work directory is not found on internal and external storage devices
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
bash-5.0# [ 8.396501] tegra-xusb 3610000.xhci: entering ELPG done
[ 37.974605] vdd-3v3-cvb: disabling
[ 37.974708] vdd-epb-1v0: disabling
[ 37.974798] vdd-sata-1v5: disabling
[ 37.974884] vdd-1v8-slt: disabling
[ 37.974954] vdd-3v3-slt: disabling
[ 37.975027] vdd-fan: disabling
[ 40.192773] random: crng init done

This is not interesting to me. This log is already no need to check.

We have a mechanism called recovery boot. This situation will happen if you fail to boot into kernel in consecutive 3 times.

L4TLauncher: Attempting Recovery Boot
EFI stub: Booting Linux Kernel…
EFI stub: Using DTB from configuration table
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Exiting boot services and installing virtual address map…

Thus, when you showed me a recover boot log, it is already too late. Because recovery boot log does not have anything related to the crash reason.

Also, you can only reflash the board now.

I have flashed via sdk manager my SSD, after flashing, when it reboots and should start the operating system, it started again with ¨L4TLauncher: Attempting Recovery Boot
¨ what can I do?

Please share me the flash log to confirm if you really flash it correctly.

Also, I just want to highlight again. Recovery boot will only happen after 3 times consecutive boot failure.

Thus, you need to immediately check and share the log after flash is done. You cannot just “ok, it is done flashing, I will put it there and come back after an hour to check”. If some error happens in this hour, then your board will be in recovery boot again.

I think it was a punctual error the first time it had not flashed well. I flashed again from the sdkmanager and now the system is ready and everything works normally.

Thank you very much for everything and I’m sorry for not being of more help.

No need to be sorry. Glad it is working now.

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.