To upgrade from JetPack 5.0/5.0.1 Developer Preview:
First edit etc/apt/sources.list.d/nvidia-l4t-apt-source.list to first point to 35.1 repo (just change the version to r35.1 in both lines) and then use the following commands, then physcially reboot the system:
The last line is required because in JetPack 5.0.2 release cuda-nvprof-11-4 package was renamed.
Then I executed “reboot” command on the terminal to reboot the device.
However when the device is booting, the display showed the warning below and after only 2 or 3 seconds, the display turned black and the fun stopped although the power button was still on.
The fun started to work after a while but display still doesn’t work.
Jetson UEFI firmware (version r34.1-975eef6 built on 2022-05-16T20:58:45-07:00)
** WARNING: Test Key is used. **
L4T boot options
0: primary kernel
1: Custom Header Config: <HDR40 User Custom [2022-06-24-193156]>
Press 0-1 to boot selection eithin 3.0 seconds.
Press any other key to boot default(Option: 1)
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…
(The last 4 lines appeared in a moment, then the desplay goes black.)
I tried to type any key but it didn’t work.
Could you tell me how to turn it on?
FYI, if you run “dmesg --follow” on the host PC, and then plug in the fully running Jetson (or plug in and then power up), you should see some new log lines associated with the device. This can tell you what device is detected.
that’s booting up process for checking keys, that’s 256-bit key to sign/encrypt UEFI.
if you’ve not assign keys, it’ll use test key and pop-up this warning messages. you may ignore this for your development process.
I’m sorry for sending lack log.
I upload the full log bellow.
I think that it is a full file but because of my poor knowledge, I can’t confirm it by myself.
So, I’m sorry maybe I sended lack log again.
And I tried “sudo apt update” , “sudo apt dist-upgrade” and " sudo apt install --fix-broken -o Dpkg::Options::=“–force-overwrite” "again.
And I found that some error happend on “sudo apt dist-upgrade” and " sudo apt install --fix-broken -o Dpkg::Options::=“–force-overwrite” "
I upload the messages that was shown on host PC through the minicom.