Hi @ricardo.gonzalez1, sorry for the late update.
Last week, I tried reinstalling JetPack using a fresh image downloaded through SDK Manager for both versions 5.1.4 and 5.1.3, but neither resolved the issue. Given this, I think we can rule out image corruption as the cause for now.
Regarding your suggestion, xrandr
doesnât show display output when accessed through an SSH session on my Jetson. I confirmed the same behavior on my laptop :
ââ[Jasont@Arch-LP] - [~] - [2025-02-10 04:12:15]
ââ[0] <> xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 340mm x 190mm
1920x1080 60.00*+ 48.00
....
....
*[Irrelevant Output.]*
ââ[Jasont@Arch-LP] - [~] - [2025-02-10 04:12:24]
ââ[0] <> ssh Jasont@localhost
Last login: Mon Feb 10 03:40:52 2025 from ::1
ââ[Jasont@Arch-LP] - [~] - [2025-02-10 04:12:34]
ââ[0] <> xrandr
Can't open display
ââ[Jasont@Arch-LP] - [~] - [2025-02-10 04:12:37]
ââ[1] <> sudo xrandr
Can't open display
ââ[Jasont@Arch-LP] - [~] - [2025-02-10 04:12:41]
ââ[1] <> xrandr --listmonitors
Can't open display
ââ[Jasont@Arch-LP] - [~] - [2025-02-10 04:12:48]
ââ[1] <> sudo xrandr --listmonitors
Can't open display
I tried reinstalling the display driver as you instructed
sudo apt update
sudo apt reinstall nvidia-l4t-x11
and it still doesnât work after restart. I made sure to have HDMI attached to the module FWIW.
Though, thanks to your suggestions, I found a strange behavior that resulted in the module displaying to the screen. Though, it went back to ground zero after restarting the module. Hereâs what i did :
- Plug in HDMI Cable to Jetson and power up. Wait for it to pass the boot screen
- If Jetson is not displaying, plug off HDMI Cable
- Get into ssh session and reboot
- Wait for Jetson to reboot. HDMI cable is still plugged off.
- After finished booting, get on ssh session and reboot again.
- Again, wait for Jetson to reboot. HDMI cable is still plugged off.
- After a few seconds of boot, Plug in HDMI Cable.
- A login screen showed up here. If jetson is still not displaying, redo step 2 to step 7. It should work the second time.
Again, display went back to no signal again after restarting this session. I suspect this might be related to the kernel not loading the display driver correctly at boot, so I attempted to reload the video driver using modprobe
.
In the failed display session, I tried reloading the video driver with modprobe (through ssh) :
jetsonnn@ubuntu:~$ lspci -k
0005:00:00.0 PCI bridge: NVIDIA Corporation Device 1ad0 (rev a1)
Kernel driver in use: pcieport
0005:01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
Subsystem: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
Kernel driver in use: nvme
jetsonnn@ubuntu:~$ sudo modprobe pcieport
[sudo] password for jetsonnn:
modprobe: FATAL: Module pcieport not found in directory /lib/modules/5.10.216-tegra
But it canât find the video driver module.
Extra Informations (Through an active display session) :
jetsonnn@ubuntu: ~ $ xrandr
Screen 0: minimum 8 x 8, current 1366 x 768, maximum 32767 x 32767
HDMI-0 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 520mm x 290mm
1366x768 60.08*+
1920x1080 60.00 59.95 50.00
1360x768 60.02
1280x768 59.87
1280x720 60.00 59.94 50.00
1024x768 60.01
800x600 60.32
720x576 50.00
720x480 59.94
640x480 59.94
DP-0 disconnected (normal left inverted right x axis y axis)
jetsonnn@ubuntu: ~ $ xrandr --listmonitors
Monitors: 1
0: +*HDMI-0 1366/520x768/290+0+0 HDMI-0
jetsonnn@ubuntu: ~ $ sudo lspci -v
[sudo] password for jetsonnn:
0005:00:00.0 PCI bridge: NVIDIA Corporation Device 1ad0 (rev a1) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 26
Bus: primary=00, secondary=01, subordinate=ff, sec-latency=0
I/O behind bridge: [disabled]
Memory behind bridge: 40000000-400fffff [size=1M]
Prefetchable memory behind bridge: [disabled]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [70] Express Root Port (Slot-), MSI 00
Capabilities: [b0] MSI-X: Enable- Count=8 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Secondary PCI Express
Capabilities: [168] Physical Layer 16.0 GT/s <?>
Capabilities: [190] Lane Margining at the Receiver <?>
Capabilities: [1c0] L1 PM Substates
Capabilities: [1d0] Vendor Specific Information: ID=0002 Rev=4 Len=100 <?>
Capabilities: [2d0] Vendor Specific Information: ID=0001 Rev=1 Len=038 <?>
Capabilities: [308] Data Link Feature <?>
Capabilities: [314] Precision Time Measurement
Capabilities: [320] Vendor Specific Information: ID=0004 Rev=1 Len=054 <?>
Kernel driver in use: pcieport
0005:01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 (prog-if 02 [NVM Express])
Subsystem: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
Flags: bus master, fast devsel, latency 0, IRQ 26
Memory at 1f40000000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [b0] MSI-X: Enable+ Count=33 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-00-00-00-00-00-00-00
Capabilities: [158] Power Budgeting <?>
Capabilities: [168] Secondary PCI Express
Capabilities: [188] Latency Tolerance Reporting
Capabilities: [190] L1 PM Substates
Kernel driver in use: nvme
My thoughts on this :
- It seems like the display driver isnât initializing correctly at boot. Is there a way to force the proper driver load sequence?
- Could this be a kernel module issue? Would rebuilding or reloading the relevant modules help?
- I noticed
lspci -k
on display only shows pcieport
module in both session (display and no display). Is this the right video driver module?
[note: no-display session is ssh, display session is the jetson desktop environment terminal]
It might be selfish for me to say this, but I would prefer not do the whole plug on off hdmi cable again just to display the screen, as it clearly shows the problem is still there. T-T
Appreciate it again for your insights, and thanks for the help!