Hello everyone, my LS055R1SX04 display refuses to work with my jetson nano. I have read and even created posts about this before but they all end in failure, so I decided to take a break. After a few more rabbitholes, I am again stuck and am resorting to the forum. If anyone could help that would be greatly appreciated.
My display is going through a driver board called the VS-CXMIPI-V1. At one point I considered reprogramming the driver board because I thought potentially the driver board was broken, since Xorg.0.log tells me that whenever the display is hooked up no EDID is detected. However, the display and driver board works perfectly on Raspberry Pi without any set up, so the driver board must be fine.
Also, other posts say that I have to recompile kernel to allow for such a resolution (which I don’t know how to do), but even then, shouldn’t the nano be getting an EDID? If the solution is to reprogram the driver board, I might need to be pointed in the right direction because according to ChatGPT’s advice, my driver board has no EEPROM and is not reprogrammable (but that’s AI’s opinion).
Lastly, it is important to know that I am not working with the official nvidia carrier board - I am working with Yahbooms 16gb emmc carrier board, since it has two CSI cameras.
If anyone can help me that would be greatly appreciated! This is the only consistent problem holding back my project; as it turns out, programming machine learning object detection is easier than getting a screen to light up.
Hi,
I think something need to be clarified first.
What is that monitor interface in use here? I am not quite sure what does that mean display is “LS055R1SX04” and driver board called the VS-CXMIPI-V1.
So is it a DP monitor to Jetson or a HDMI interface?
1440x2560 is indeed a rare resolution one for Jetson nano which I also don’t think it would support either. But just check why EDID is not there first.
Sorry, I just gave the name of the display and driver board. The whole interface is plugged into HDMI and xrandr recognizes it as HDMI-0.
I just checked the driver code. We don’t support a mode with y resolution over 2160 on Jetson Nano.
So this mode is not supported.
I’m just wondering, you have advised people before with the same display just to recompile the kernel and get rid of that restriction. Why does that not apply here?
Hi,
Those things are just experiment. The driver puts some limitation there has its reason.
You could still try to modify driver code there but I don’t guarantee those things should be in use for production.
You could start from learning how to build Linux driver code first if you don’t know how to do it.
You could dump the kernel log by dmesg command first so that we can check why there is no EDID as I suggested previously.
kernel.log (56.6 KB)
Here is my kernel log from reboot. The SDA USB device is just because I am keeping my filesystem on a USB stick with an SD card in it, because the on board storage is too small.
There is no error related to missing EDID from your dmesg.
I don’t know how did you come out that conclusion.
Yes, but my Xorg.0.log says that no edid is detected and is set to nvidia-autoselect modes. How come there is disparity between my Xorg log and dmesg log, and which one is right. Also, if my edid really isn’t broken, how do I proceed from here?
You could share out your xorg log and xrandr result too.
It does not matter what you saw on you side. It is about sharing out so that others could help you check.