We have encountered the follwoing issue:
We start with a completely new Jetson Orin Nano Devkit, with an nvme drive, flashed with the Nvidia SDKmanager with JetPack 6.1, and then boot it:
First we see the bootloader screen with the nvidia logo
Then the extlinux sequence with the terminal output of the linux startup
Lastly we land at the login screen
In order to change the logo, we followed the instructions here (Build with docker · NVIDIA/edk2-nvidia Wiki · GitHub ), and are using revision r36.4.0-updates
.
We can successfully build the new uefi_jetson_RELEASE.bin, and copy it over to the according location in the nvidia dir before flashing the QSPI only:
sudo ./flash.sh --no-systemimg -c bootloader/generic/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit-nvme internal
If we now boot the device, we see the following:
First the bootloader screen with our custom logo
Then the videofeed disconnects, i.e. the monitor says no input
The videofeed reconnects and we see the login screen
The time at step 2 is about the same, and the config in /boot/extlinux/extlinux.conf did not change, and was never modified:
TIMEOUT 30
DEFAULT primary
MENU TITLE L4T boot options
LABEL primary
MENU LABEL primary kernel
LINUX /boot/Image
INITRD /boot/initrd
APPEND ${cbootargs} root=PARTUUID=... rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 nospectre_bhb video=efifb:off console=tty0 nv-auto-config
Is there a configuration we missed to not loose the videofeed?
Thank you and have a nice day!
Just to clarify if this is related to the logo file itself or something else.
If you change the logo back to default file, would you see the desktop GUI comes back?
Please share the /var/log/Xorg.0.log by using serial console log.
https://www.jetsonhacks.com/2019/04/19/jetson-nano-serial-console/
I would be surprised if this is related in any way to the logo, should have clarified that ^^ we also tried to just compile it with the default logo and observed the same behavior (it was on rev r36.4.0
, not r36.4.0-updates
).
Assuming desktop GUI refers to ubuntu, we have no issues with that, the loginscreen appears always, its only the tty output / screen connectivity during the linux boot that is different.
will share asap
Maybe you should take a video for your issue.
I just went back to read your description and It looks like the issue you are reporting here is a very short period during boot got disappeared. But not monitor went off forever. Is that correct?
Thx to @bobekjan for solving the issue:
opened 06:52AM - 02 Dec 24 UTC
closed 05:42AM - 04 Dec 24 UTC
Dear edk2-nvidia team
First off, thx for the great package!
We have encountere… d the follwoing issue:
We start with a completely new Jetson Orin Nano Devkit, with an nvme drive, flashed with the Nvidia SDKmanager with JetPack 6.1, and then boot it:
1) First we see the bootloader screen with the nvidia logo
2) Then the extlinux sequence with the terminal output of the linux startup
3) Lastly we land at the login screen
In order to change the logo, we followed the instructions here (https://github.com/NVIDIA/edk2-nvidia/wiki/Build-with-docker), and are using revision `r36.4.0-updates`.
We can successfully build the new uefi_jetson_RELEASE.bin, and copy it over to the according location in the nvidia dir before flashing the QSPI only:
`sudo ./flash.sh --no-systemimg -c bootloader/generic/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit-nvme internal`
If we now boot the device, we see the following:
1) First the bootloader screen with our custom logo
2) Then the videofeed disconnects, i.e. the monitor says no input
3) The videofeed reconnects and we see the login screen
The time at step 2 is about the same, and the config in /boot/extlinux/extlinux.conf did not change, and was never modified:
```
TIMEOUT 30
DEFAULT primary
MENU TITLE L4T boot options
LABEL primary
MENU LABEL primary kernel
LINUX /boot/Image
INITRD /boot/initrd
APPEND ${cbootargs} root=PARTUUID=... rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 nospectre_bhb video=efifb:off console=tty0 nv-auto-config
```
Is there a configuration we missed to not loose the videofeed?
Thank you and have a nice day!
TL;DR: SOC handoff was set to never, and should be set to auto.
1 Like
yes, I only “loose” the screen for 10-15 seconds, during the linux kernel boot sequence (because SOC Handoff was set to Never). Its a little surprising that this is the default to me but there probably is good reason for it.
1 Like
system
Closed
January 1, 2025, 12:49am
11
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.