Hello, could anyone give me a little advice or hint on how to proceed further ?

I have a LCD display salvaged from a broken laptop (CLAA102NA0ACW) and have got a VGA LVDS controller (R.RM3251 for CLAA102NA0ACW). I'm trying to use the PiView to connect the VGA controller to the Pi and have been having little success.

The only way I get an image is when I use "hdmi_safe=1" with the following settings

CVT modes are not compulsory - my guess is your monitor doesn't support CVT timing.
You can explicitly set all the timing parameters (with hdmi_timings), but you will need a datasheet for the LCD to determine what the timings are it requires.

Mortar Art wrote:
from the sounds of it, you're the person to ask about my issue. I've been trying to connect my Rift DK2 to the Pi B+ for a few days now, and have tried almost every possible combination in config.txt.

The DK2 is 1080x1920. It's not a rotated 1080p display. It's natively in portrait. Is there any way to get a 9x16 aspect ratio thrown in to the mix for the sake of people trying to use Oculus devices?

Are you saying you can get an image (e.g. using CVT settings)? If so what problem are you seeing?
I assume the pixels are square?

Hi Dom. I'm not getting an image. The Rift seems to have 3 status indicators on it's LED:

Orange; standby
Orange/blue; Incorrect mode
Blue; on

On is accompanied by the screen being active.

If I leave the Pi's settings alone, and either hotplug or boot with the Rift plugged in, I get Orange/Blue. If I set all manner of settings in config.txt and again via tvservice, I get Orange, if the settings are close to the Rift's needs.

Does the Pi support native portrait, or only rotated aspect ratios? Your earlier posts here seem to indicate that it supports 16:9, but not 9:16.

I was trying to use hdmi_timings do run an DVI-2-LVDS-Converter. Unfortunately I did not work as aspected...

So if got some questions:
- Does hdmi_timings meet the CVT-Standard from VESA? Particulary the Sync-Polarity? If I got right from the VESA standard the sync polarity for normal CRT are HSync - Negative and VSync - Positive. Is this the same for hdmi_timings?

The "standard" sync polarities can differ from mode to mode, you have to look at the relevant standard VESA timing sheet. Not entirely clear from the post, but I'm guessing "0" is negative, 1 for "positive." As for pixel_rep: In effect, I think this is telling the display controller whether each pixel needs to be sent twice. The reason for this is that audio in HDMI is sent in-between frames of video and how much audio can be squeezed in is dependent on the pixel clock. As there are some lower resolution modes in HDMI (e.g. 640x480 interlaced like old SDTV), there wouldn't be enough available bandwidth to fit some of the higher-bandwidth compressed audio modes into the stream (e.g. AC3, DTS), so the HDMI spec defines some modes where the pixel clock runs twice as fast, but where each pixel is sent twice, resulting in the same effective video resolution but then the clock runs fast enough to jam the audio in there.

and it will probably show up, but I suspect that it is way too high to be usable.
1920x1200@60 is the most we officially support.

will try this when back from work. In the ends more about the aspect ratio 21:9 as 16:9 movies look pretty distorted.
If I can't get it working, I will probably look for a resolution close to 1080p but closer to 21:9.

If tried the 3440x1440 with the higher hdmi_pixel_freq_limit as well as hvs_priority set to 0x32ff -> without success.
tvservice -m DMT and tvservice -s are displaying the mode as expected but the kodi screen stays black without reporting any errors in the logs.

Anyhow, if read from my displays edid data that there it also supports 2560x1080, which is also 21:9 (very close to). That one works out of the box and I don't see any performance issues...

Thomason wrote:
Anyhow, if read from my displays edid data that there it also supports 2560x1080, which is also 21:9 (very close to). That one works out of the box and I don't see any performance issues...

Good to hear. Are you using this resolution with OpenELEC without issues?

Thomason wrote:
Anyhow, if read from my displays edid data that there it also supports 2560x1080, which is also 21:9 (very close to). That one works out of the box and I don't see any performance issues...

Good to hear. Are you using this resolution with OpenELEC without issues?

Seems so, tvservice reports the correct resolution and KODI offers that resolution in the video settings.
If quickly tested some 1080p videos and didn't see any tethering or frame drops.
Youtube with 720p is running for over an hour now.

Thomason wrote:
...
Anyhow, if read from my displays edid data that there it also supports 2560x1080, which is also 21:9 (very close to). That one works out of the box and I don't see any performance issues...

I have also a LG Electronics 29UM65-W, 29"
i was able to get a 2560x1080 resolution but i have huge black bars left and rigth and the screen is not centered.
I am able to move the mouse "behind" the right black bar.

with overscan settings i was only able move the picture to the left or rigth.
but if i use a negative value for overscan_left the screen stays black but tells me its getting a signal.
#overscan_left=-50
#overscan_right=-50