Boot Screen (press Esc) no longer visible due to modeline change after SDK Manager flash

Autonomous Machines Jetson & Embedded Systems Jetson Orin Nano
1

I have my Orin Nano Developer Kit attached to a Wacom Cintiq Pro 24" monitor. The module was purchased about 6-8 months ago.

The first time I used the device, I flashed a 64GB SD card using the “JP512-orin-nano-sd-card-image.zip” on the page JetPack SDK | NVIDIA Developer → JETSON XAVIER NX DEVELOPER KIT & ORIN NANO DEVELOPER KIT.

With the SD card, the Nano would display the BOOT message with “Press ESCAPE for boot options”, etc., when powered on and then proceed to the OS.

The SD card died, so I installed an NVMe and flashed the board with JetPack 5.1.2 and all optional SDKs and tools using SDK Manager 2.0.0.11402 x86_64 and Ubuntu 20.04.

After the flash, the board boots and run fine, but at the Boot Screen (press Esc) stage, my monitor now displays the message, “Invalid frequency,” because the modeline used to display the boot menu has changed.

Is there a way I can change the modeline for the boot back to what it was so I can see the boot screen again and set my default boot device to the NVMe? Was this change intentional, unintentional, or a result of something I did?

Thanks.

PS – While getting the link to the SD card image for this post I noticed that the Jetson Nano Developer Kit SD Card Image pointed to by the Get Started With Jetson Nano Developer Kit | NVIDIA Developer page still links to the jetson-nano-jp461-sd-card-image.zip version of the SD card image.

3

Hi,

I’m not sure what exactly you are talking about.

What do you mean with this?
So are you able to boot from the NVMe drive or not?

4

I can boot from the NVMe, yes, but during the boot I cannot see the “press ESC” message to get into the boot menu and change the default boot device because the format of the image being sent to the monitor is not compatible with the monitor anymore. If I press ESC anyway, I just see a “Invalid frequency” (my monitor telling me the output of the HDMI is incompatible.)

As soon as the boot completes, it switches to the correct mode and I can see the screen again, but by this time I am looking at Ubuntu, not at the boot menu.

Before using the SDK manager to reflash the board, I was able to see the boot menu.

5

Then you may connect the device to a host PC, and UEFI will be accessible via serial console.

6

Do it like this:

Use the keyboard of your host PC for entering UEFI menu.

8

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