No DP output on jetson nano #152
Comments
|
There is this thread from nvidia forums and it seems that it is related to the DP version of the monitor |
|
Hi, thanks for your reply, My monitor (Dell P2419hc) supports DP 1.2.
Now I'm building an image with xrandr to check if with that I can set the
output to DP
El mié, 5 mar 2025 a la(s) 10:18 a.m., Badr ***@***.***)
escribió:
… There is this thread from nvidia forums and it seems that it is related to
the DP version of the monitor
https://forums.developer.nvidia.com/t/displayport-not-working/71989/11
—
Reply to this email directly, view it on GitHub
<#152 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPXOJ3AX3U6P5MKMIIRZOT2S32RDAVCNFSM6AAAAABYMCHGSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBQHEYDMOBUGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: pythops]*pythops* left a comment (pythops/jetson-image#152)
<#152 (comment)>
There is this thread from nvidia forums and it seems that it is related to
the DP version of the monitor
https://forums.developer.nvidia.com/t/displayport-not-working/71989/11
—
Reply to this email directly, view it on GitHub
<#152 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPXOJ3AX3U6P5MKMIIRZOT2S32RDAVCNFSM6AAAAABYMCHGSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBQHEYDMOBUGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I have the same problem on Nano B01. Here is the event log output by the I think the problem may arise here causing the link training to be reset multiple times, since this log appears repeatedly:
Does this mean we need to recompile the device tree? Here is a discussion that seems to be related to this issue： https://forums.developer.nvidia.com/t/display-port/53284/2 https://forums.developer.nvidia.com/t/edp-link-training-fails/110364/16 Hope the information I provided will be helpful. |
|
I just solved this problem, here are the steps for reference. 1. Decompile the device tree file on Jetson Nano:
2. Open the file with a text editor, locate node then save it as a different file name. Here is 3. Confirm the current kernel dtb file name, and backup it On my device, it shows
4. Compile the new dtb file:
5. Replace original dtb file with your new dtb file:
6. reboot |
|
@nenekodev I have a couple of questions for you:
|
@pablitok Yes, it's definitely a little weird... For question 2 first, I just tried using Here's the Notice that it mentioned Btw, I recalled that if you only plug in the DP cable and start it, the device will not display the Nvidia logo on the boot interface, but will directly display the mouse pointer and desktop environment after XWindows starts. So this may mean that the solution is only applicable to XWindows. For question 1, This link gives a reference, pointing out that the default xorg server version in the Ubuntu 22.04 may have ABI incompatibility issues, which will make the XWindow unable to start, so you need to specify the xorg version first and prohibit updating the package: Then install the x-window software and your favorite desktop environment. Here I have installed LXDE in a minimal way, and subsequently modified some of my personal flavor settings. Finally, don't forget to change the default startup to the graphical interface. If you don't mind typing |
|
After some research, I think the problem is probably the lack of nvidia's proprietary DRM driver in the kernel, because the DP output comes from the buffer and drm before the GUI is started. I found that only So I tried to compile a kernel with I will continue to follow up on this issue, but you may try to back up the existing kernel and try the official or third-party compiled version to see if you can get DP to work properly in the console interface. |
|
Hi @nenekodev , yesterday I was looking around to see if I can see something interesting and the only thing I saw is that |
|
@pablitok Maybe you can try the kernel compiled by myself https://github.com/nenekodev/jetson-linux-build/releases/tag/4.9.337-tegra And the image automatically built using GitHub action (note that this image has not yet installed the graphical interface, uses the default kernel, and the device tree has not been modified. After flashing the image, you can follow the steps I provided before to modify the device tree to achieve DP support for the graphical interface) https://drive.google.com/file/d/1c8GcOcI2X_c58oL55cMeN5YdyFZyQ5Mp/view?usp=sharing |
|
Great, after work I'll try both |
|
@nenekodev I'm trying the kernel image. |
|
Your Also, I'm not sure if the hardware carrier you are using is the same as mine (B01, internal model P3449-45-13450-0000-100). I'm trying to compile a kernel with |
|
Hi! last night I tried your image and worked, seems that the DP output only works in X. |
|
The easiest way is to check the interface configuration on the left side of the carrier board. If there are two CSI camera interfaces, it is B01, otherwise it is A02. More detailed instructions here: https://www.arducam.com/nvidia-jetson-nano-b01-update-dual-camera/ Since JetPack 4.4.1, the official system mirrors of the two are common, discussed here: https://forums.developer.nvidia.com/t/do-jetson-nano-b01-and-a02-use-the-same-sd-card-mirror/165278 But I’m not sure whether the system image we built ourselves is also compatible with the differences in details between the two versions of hardware, so I want to ask you to confirm whether the hardware version you are using is the same as mine, which is the later version B01. |
|
I just tried the latest official image jetpack 4.6.1. After flashing it to the SD card, its DP also only works in the graphical interface. Once it switches to the character interface, the screen will go black. Therefore, I suspect that this is caused by nvidia's failure to do a good job of the graphics driver under the character interface. This was later confirmed on the linux kernel website: Note that tegra 210 is the soc of jetson nano. I looked up nvidia's official developer forum and found two posts mentioning this issue. The community administrator replied that https://forums.developer.nvidia.com/t/cant-load-tegra-drm-module-on-custom-build-kernel/73771/2 https://forums.developer.nvidia.com/t/tegra-drm-driver-building/276603/3 which confirmed my guess: for the jetson nano product and the corresponding L4T 32.x version, there is no kernel-level drm driver, but only user-mode driver - so you can use the DP port to output GPU content normally in the Xwindow, but you can only use HDMI output in the character interface. Moreover, because Jetson Nano and JetPack 4.x have been officially listed as obsolete products, they probably don't plan to continue to follow up on this development. Later, I found the kernel compilation document of L4T 35.x on the nvidia official website: This may answer why I failed to compile the kernel with nvidia-drm. Maybe only L4T35.x and above can compile successfully. |
|
Ok, then I'll stop tinkering with that, thanks! |
Hi, I'm trying to use this repo to create a ubuntu version for my jetson nano 4g, the image creates well, I can boot it, but I'm using the jetson with a DP monitor and it's not giving me video signal. If I connect it via hdmi, it works fine.
Connected to DP seems to have signal (when there is no signal the screen monitor shows a text and go to sleep, also I see that the monitor is blank but turned on)
With other image (the official one or this one) Display Port has video signal
The text was updated successfully, but these errors were encountered: