Bug 2270874 - No output on display on Jetson Nano
Summary: No output on display on Jetson Nano
Keywords:
Status: ASSIGNED
Alias: None
Product: Fedora
Classification: Fedora
Component: uboot-tools
Version: 40
Hardware: aarch64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: F40FinalFreezeException, FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2024-03-21 21:50 UTC by Adam Williamson
Modified: 2024-04-09 12:06 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)
journal messages from a minimal boot on the affected system (408.29 KB, text/plain)
2024-03-21 21:50 UTC, Adam Williamson
no flags Details

Description Adam Williamson 2024-03-21 21:50:32 UTC
Created attachment 2022969 [details]
journal messages from a minimal boot on the affected system

I have here a Jetson Nano that's intended for aarch64 validation testing. I have not been able to get it to output anything but the NVIDIA logo via HDMI for years (maybe ever - I don't recall), but I at least have the serial console working well enough to file a useful bug report, I hope.

Currently the board is flashed with the u-boot.bin from https://kojipkgs.fedoraproject.org//packages/uboot-tools/2024.04/0.7.rc4.fc40/noarch/uboot-images-armv8-2024.04-0.7.rc4.fc40.noarch.rpm , using version 32.7.4 of the driver bundle.

Whether I boot a Minimal or Workstation image, I see the NVIDIA logo for a bit during boot, then it goes away, and nothing else is ever shown on the display. The display is a pretty normal monitor, connected by HDMI. It works fine on an x86_64 system.

If I plug in a USB serial cable, attach it to a laptop, and run gtkterm on the laptop, I can see the system boots successfully, and for the Minimal image, I can complete initial-setup on the serial console and then log in.

I'm attaching the journalctl output after doing so, in hopes it provides some clue why I can't see anything on the screen. It would be a bit harder to get logs from the Workstation case, since I don't have a user account I can log into there...

Comment 1 Dennis Gilmore 2024-03-22 14:10:13 UTC
Do you have any bootargs for output. I have the same version u-boot here and while u-boot does not turn on the display so nothing is output on the screen until the linux kernel initialises the display. I get the boot log and a login prompt on the HDMI screen I plug in. It may also be helpful to know what monitor you are using.and if you are using DP or HDMI, I personally have only used HDMI. I have a 7" HDMI screen I use when need be as I have mine mounted in my rack.

Comment 2 Adam Williamson 2024-03-22 15:43:50 UTC
I am not using any custom bootargs, nothing I read indicated that I need any. I'm just following Peter's blog post to flash the device, then write an image to an SD card, plug it into the system, and boot it.

Yeah, I'd heard that uboot doesn't turn on the display so I wouldn't get any boot messages there, but I don't get a login prompt either, on either spin (Minimal or Workstation).

The monitor I'm currently trying to use is an MSI Optix G242P. It's a fairly normal 24" HDMI monitor, nothing exotic. It displays the NVIDIA logo just fine, during very early boot, so the board is clearly capable of outputting to it.

Comment 3 Fedora Blocker Bugs Application 2024-04-03 02:47:49 UTC
Proposed as a Blocker for 40-final by Fedora user pbrobinson using the blocker tracking app because:

 The final complete fix for this that we decided to document and not respin beta for never made it stable due to lack of karma so we need this in GA with zero doubt.

Comment 4 Adam Williamson 2024-04-04 19:30:15 UTC
Peter: oh, so you think the pending update should actually fix video output on the Nano? If so, I can try it here. I guess I need to reflash the uboot image again?

Comment 5 Adam Williamson 2024-04-04 21:42:16 UTC
sadly, still doesn't seem to have fixed that. i reflashed the nano using the uboot image from https://bodhi.fedoraproject.org/updates/FEDORA-2024-1d0b793bc1, then tried booting a current Rawhide workstation raw.xz (so the image would also have the updated bits), written using arm-image-installer from the update, and...still nothing on the HDMI output (except the NVIDIA logo).

Comment 6 Peter Robinson 2024-04-05 03:26:45 UTC
(In reply to Adam Williamson from comment #4)
> Peter: oh, so you think the pending update should actually fix video output
> on the Nano? If so, I can try it here. I guess I need to reflash the uboot
> image again?

No, it won't, hence why it's not linked against the update ;-) I am going to look at it when I'm back in the same location as my nano, it will need some upstream bits.

Comment 7 Adam Williamson 2024-04-05 06:00:55 UTC
ah, I see, the comment was for https://bugzilla.redhat.com/show_bug.cgi?id=2241252 . gotcha. will remove my negative karma.

Comment 8 Adam Williamson 2024-04-05 06:03:03 UTC
I *would* say this would be worth an FE, though, if you happen to find a fix in time, so let's throw it on the list.

Comment 9 Adam Williamson 2024-04-05 19:19:53 UTC
+3 in https://pagure.io/fedora-qa/blocker-review/issue/1555 , marking accepted.

Comment 10 Peter Robinson 2024-04-09 12:06:13 UTC
There's currently no upstream support for display on Tegra210 in U-Boot.


Note You need to log in before you can comment on or make changes to this bug.