Guybrush
Posts: 1
Joined: Sun Aug 06, 2017 6:04 am

Re: STICKY: Setting up HDMI output when video output is wrong.

Sun Aug 06, 2017 6:27 am

Hi folks,

I'm new here and I'm having an issue setting up an LCD panel properly.

More specifically, this one:

http://www.ebay.com/itm/9-TFT-LCD-Displ ... 2749.l2649

I'm wondering if anyone here has experience with that specific screen. The driver board is PCB800099-V9. The panel is stamped BCL900-23EM. I cannot find any information or specs on it.

The issue: the panel is supposed to be 1024x600 (and that isn't really 16/9 either), but even after defining a custom setting in config.txt for it, the display is pretty horrid. In a web browser, fonts are pretty bad, fuzzy, pixels running into adjacent ones, irregular spaces...pretty much looking like bad scaling.

After spending a lot of time fiddling with it, it seems that using a resolution of 800x480 fixes the problem mentioned above. It's still not a pretty screen (TN panel, bad colors, bad angles), but the text looks correct, and pixel spacing is regular.

So I'm wondering if this is simply a 800x480 panel, or if my 1024x600 config is wrong (and if the driver board could have anything to do with the issue), because it basically looks like the higher resolution is being scaled down.

Here is the EDID output. It seems to be guessing that the resolution is 800x480. I just don't know how much of this is accurate.

Thanks a bunch for any ideas :)

Code: Select all

HDMI:EDID version 1.3, 1 extensions, screen size 47x26 cm
HDMI:EDID features - videodef 0x81 !standby !suspend active off; colour encoding:RGB444|YCbCr444|YCbCr422; sRGB is default colourspace; preferred format is native; does not support GTF
HDMI:EDID found monitor S/N descriptor tag 0xff
HDMI:EDID found monitor range descriptor tag 0xfd
HDMI:EDID monitor range offsets: V min=0, V max=0, H min=0, H max=0
HDMI:EDID monitor range: vertical is 56-75 Hz, horizontal is 30-83 kHz, max pixel clock is 210 MHz
HDMI:EDID monitor range does not support GTF
HDMI:EDID found monitor name descriptor tag 0xfc
HDMI:EDID monitor name is HDMI
HDMI:EDID failed to find a matching detail format for 800x480p hfp:44 hs:88 hbp:124 vfp:3 vs:6 vbp:46 pixel clock:33 MHz
HDMI:EDID calculated refresh rate is 60 Hz
HDMI:EDID guessing the format to be 800x480p @60 Hz
HDMI:EDID found unknown detail timing format: 800x480p hfp:44 hs:88 hbp:124 vfp:3 vs:6 vbp:46 pixel clock:33 MHz
HDMI:EDID established timing I/II bytes are AF EF 00
HDMI:EDID found DMT format: code 4, 640x480p @ 60 Hz in established timing I/II
HDMI:EDID found DMT format: code 5, 640x480p @ 72 Hz in established timing I/II
HDMI:EDID found DMT format: code 6, 640x480p @ 75 Hz in established timing I/II
HDMI:EDID found DMT format: code 8, 800x600p @ 56 Hz in established timing I/II
HDMI:EDID found DMT format: code 9, 800x600p @ 60 Hz in established timing I/II
HDMI:EDID found DMT format: code 10, 800x600p @ 72 Hz in established timing I/II
HDMI:EDID found DMT format: code 11, 800x600p @ 75 Hz in established timing I/II
HDMI:EDID found DMT format: code 16, 1024x768p @ 60 Hz in established timing I/II
HDMI:EDID found DMT format: code 17, 1024x768p @ 70 Hz in established timing I/II
HDMI:EDID found DMT format: code 18, 1024x768p @ 75 Hz in established timing I/II
HDMI:EDID found DMT format: code 36, 1280x1024p @ 75 Hz in established timing I/II
HDMI:EDID standard timings block x 8: 0x0101 0101 0101 0101 0101 0101 0101 0101 
HDMI:EDID parsing v3 CEA extension 0
HDMI:EDID monitor support - underscan IT formats:no, basic audio:yes, yuv444:yes, yuv422:yes, #native DTD:1
HDMI:EDID found preferred CEA detail timing format: 720x576p @ 50 Hz (17)
HDMI:EDID found CEA detail timing format: 1920x1080i @ 60 Hz (5)
HDMI:EDID found CEA detail timing format: 1920x1080i @ 50 Hz (20)
HDMI:EDID found CEA detail timing format: 1280x720p @ 50 Hz (19)
HDMI:EDID found CEA detail timing format: 1920x1080p @ 50 Hz (31)
HDMI:EDID found CEA format: code 6, 1440x480i @ 60Hz 
HDMI:EDID found CEA format: code 7, 1440x480i @ 60Hz 
HDMI:EDID found CEA format: code 2, 720x480p @ 60Hz 
HDMI:EDID found CEA format: code 3, 720x480p @ 60Hz 
HDMI:EDID found CEA format: code 21, 1440x576i @ 50Hz 
HDMI:EDID found CEA format: code 22, 1440x576i @ 50Hz (native)
HDMI:EDID found CEA format: code 17, 720x576p @ 50Hz 
HDMI:EDID found CEA format: code 18, 720x576p @ 50Hz 
HDMI:EDID found CEA format: code 19, 1280x720p @ 50Hz 
HDMI:EDID found CEA format: code 4, 1280x720p @ 60Hz 
HDMI:EDID found CEA format: code 20, 1920x1080i @ 50Hz 
HDMI:EDID found CEA format: code 5, 1920x1080i @ 60Hz 
HDMI:EDID found CEA format: code 31, 1920x1080p @ 50Hz 
HDMI:EDID found CEA format: code 16, 1920x1080p @ 60Hz (native)
HDMI:EDID found audio format 2 channels PCM, sample rate: 32|44|48 kHz, sample size: 16|20|24 bits
HDMI:EDID found HDMI VSDB length 5
HDMI:EDID HDMI VSDB has physical address 1.0.0.0
HDMI:EDID HDMI VSDB has no extension fields
HDMI:EDID adding mandatory support for CEA (1) 640x480p @ 60Hz
HDMI:EDID filtering formats with pixel clock > 162 MHz or h. blanking > 1023
HDMI:EDID best score mode initialised to CEA (1) 640x480p @ 60 Hz with pixel clock 25 MHz (score 0)
HDMI:EDID best score mode is now CEA (1) 640x480p @ 60 Hz with pixel clock 25 MHz (score 61864)
HDMI:EDID best score mode is now CEA (2) 720x480p @ 60 Hz with pixel clock 27 MHz (score 66472)
HDMI:EDID CEA mode (3) 720x480p @ 60 Hz with pixel clock 27 MHz has a score of 66472
HDMI:EDID best score mode is now CEA (4) 1280x720p @ 60 Hz with pixel clock 74 MHz (score 135592)
HDMI:EDID DMT mode (4) 640x480p @ 60 Hz with pixel clock 25 MHz has a score of 18432
HDMI:EDID best score mode is now CEA (5) 1920x1080i @ 60 Hz with pixel clock 74 MHz (score 4773832)
HDMI:EDID DMT mode (5) 640x480p @ 72 Hz with pixel clock 31 MHz has a score of 22118
HDMI:EDID CEA mode (6) 1440x480i @ 60 Hz with pixel clock 27 MHz has a score of 45736
HDMI:EDID DMT mode (6) 640x480p @ 75 Hz with pixel clock 31 MHz has a score of 23040
HDMI:EDID CEA mode (7) 1440x480i @ 60 Hz with pixel clock 27 MHz has a score of 45736
HDMI:EDID DMT mode (8) 800x600p @ 56 Hz with pixel clock 36 MHz has a score of 26880
HDMI:EDID DMT mode (9) 800x600p @ 60 Hz with pixel clock 40 MHz has a score of 28800
HDMI:EDID DMT mode (10) 800x600p @ 72 Hz with pixel clock 50 MHz has a score of 34560
HDMI:EDID DMT mode (11) 800x600p @ 75 Hz with pixel clock 49 MHz has a score of 36000
HDMI:EDID CEA mode (16) 1920x1080p @ 60 Hz with pixel clock 148 MHz has a score of 398248
HDMI:EDID DMT mode (16) 1024x768p @ 60 Hz with pixel clock 65 MHz has a score of 47185
HDMI:EDID best score mode is now CEA (17) 720x576p @ 50 Hz with pixel clock 27 MHz (score 5087208)
HDMI:EDID DMT mode (17) 1024x768p @ 70 Hz with pixel clock 75 MHz has a score of 55050
HDMI:EDID CEA mode (18) 720x576p @ 50 Hz with pixel clock 27 MHz has a score of 66472
HDMI:EDID DMT mode (18) 1024x768p @ 75 Hz with pixel clock 78 MHz has a score of 58982
HDMI:EDID CEA mode (19) 1280x720p @ 50 Hz with pixel clock 74 MHz has a score of 3617160
HDMI:EDID CEA mode (20) 1920x1080i @ 50 Hz with pixel clock 74 MHz has a score of 4232360
HDMI:EDID CEA mode (21) 1440x576i @ 50 Hz with pixel clock 27 MHz has a score of 45736
HDMI:EDID CEA mode (22) 1440x576i @ 50 Hz with pixel clock 27 MHz has a score of 56104
HDMI:EDID CEA mode (31) 1920x1080p @ 50 Hz with pixel clock 148 MHz has a score of 3232360
HDMI:EDID DMT mode (36) 1280x1024p @ 75 Hz with pixel clock 135 MHz has a score of 98304
HDMI:EDID preferred mode remained as CEA (17) 720x576p @ 50 Hz with pixel clock 27 MHz
HDMI:EDID has HDMI support and audio support
edid_parser exited with code 0


Misirlou
Posts: 7
Joined: Fri Sep 29, 2017 11:54 pm

Re: STICKY: Setting up HDMI output when video output is wrong.

Wed Oct 18, 2017 9:46 am

Edit: I solved the problem below, that a headless Pi with VNC Viewer always has a small default screensize, even if you choose another resolution. I had enabled the experimental graphics driver. Commenting out the following line in /boot/config.txt solved the problem:

Code: Select all

dtoverlay=vc4-kms-v3d
Original post:
~~~~~~~~~

I'm running Jessie headless with VNC Viewer, and have set up the /boot/config.txt file configured with:

Code: Select all

# uncomment if hdmi display is not detected and composite is being output
hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
hdmi_group=2
hdmi_mode=85
This used to work ok, but now I'm stuck with the small default screen. I don't know what changed. It used to work ok. If I try with a fresh copy of Raspian it works, but I'd like not to have to reinstall everything from scratch. Is there something else I can check?

I tried doing it with raspi-config, with the "Raspberry Pi Configuration" menu, and manually editing config.txt (all of which resulted in the same config lines, above). I also tried uncommenting this:

Code: Select all

# uncomment to force a console size. By default it will be display's size minus
# overscan.
framebuffer_width=1280
framebuffer_height=720
But it makes no difference. Any help appreciated!

User avatar
BorbingoBoy
Posts: 13
Joined: Sun Apr 09, 2017 6:24 am
Location: Croatia
Contact: Website

Re: STICKY: Setting up HDMI output when video output is wrong.

Sun Oct 22, 2017 9:57 am

Hello.

I am constantly getting no HDMI output after shutting down my Pi 3 and turning it back on. I had to edit the config.txt many times only to have the HDMI output reset again after I shut the Pi down. Restarting doesn't change this, though.
3.1415926535897932384626433832795028841971693993751058209749445923078164062862089986280348253421170679821480865132823066470938446095505822317253594081284811174502841027019385211055596446229489549303819644288109756659334461284756482337867831652712019091456

User avatar
rpdom
Posts: 12582
Joined: Sun May 06, 2012 5:17 am
Location: Essex, UK

Re: STICKY: Setting up HDMI output when video output is wrong.

Sun Oct 22, 2017 10:23 am

BorbingoBoy wrote:
Sun Oct 22, 2017 9:57 am
Hello.

I am constantly getting no HDMI output after shutting down my Pi 3 and turning it back on. I had to edit the config.txt many times only to have the HDMI output reset again after I shut the Pi down. Restarting doesn't change this, though.
What did you change in config.txt and did the changes "stick" after power off?

User avatar
BorbingoBoy
Posts: 13
Joined: Sun Apr 09, 2017 6:24 am
Location: Croatia
Contact: Website

Re: STICKY: Setting up HDMI output when video output is wrong.

Sun Oct 22, 2017 11:26 am

rpdom wrote:
Sun Oct 22, 2017 10:23 am
BorbingoBoy wrote:
Sun Oct 22, 2017 9:57 am
Hello.

I am constantly getting no HDMI output after shutting down my Pi 3 and turning it back on. I had to edit the config.txt many times only to have the HDMI output reset again after I shut the Pi down. Restarting doesn't change this, though.
What did you change in config.txt and did the changes "stick" after power off?
Sorry, I forgot to mention that I applied the force HDMI hotplug setting, and after that changed the resolution using raspi-config to preferred monitor resolution, because the force hotplug setting changes the resolution to the lowest one. Anyway, if I restart after applying the resolution, everything is okay, but once I shut it down, the force HDMI hotplug setting in config.txt gets commented.
3.1415926535897932384626433832795028841971693993751058209749445923078164062862089986280348253421170679821480865132823066470938446095505822317253594081284811174502841027019385211055596446229489549303819644288109756659334461284756482337867831652712019091456

User avatar
DougieLawson
Posts: 33003
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website

Re: STICKY: Setting up HDMI output when video output is wrong.

Sun Oct 22, 2017 5:55 pm

Are you using NOOBS?

Hold/tap the [SHIFT] key during boot-up. Use the NOBS rescue system config editor to set the parameters you want.
Microprocessor, Raspberry Pi & Arduino Hacker
Mainframe database troubleshooter
MQTT Evangelist
Twitter: @DougieLawson

2012-18: 1B*5, 2B*2, B+, A+, Z, ZW, 3Bs*3, 3B+

Any DMs sent on Twitter will be answered next month.

theatomicsoul
Posts: 4
Joined: Sat Nov 04, 2017 9:15 pm

Re: STICKY: Setting up HDMI output when video output is wrong.

Sat Nov 04, 2017 9:40 pm

The Raspberry Pi3 I just purchased is not properly recognizing the 8.9" screen I got to use with it.

The Pi works fine connected to my PC monitor but is giving an incorrect display / video feed when connected to my smaller (8.9") 2K screen.
When the pi connects to the 8.9" screen it cuts off the left half of the screen (shows black) and shows three vertacle stacked versions of the right half of the screen on that side.
The 8.9" screen works properly when connected to my PC.

What do I need to do to fix it to use the full 2560x1600 display?

Running Raspian with NanoDLP.
https://youtu.be/fLJjvJXFq60

I have this screen:
https://m.aliexpress.com/item/328050026 ... 8c0bCHEJX1

ElizabethMireles
Posts: 1
Joined: Tue Nov 07, 2017 1:16 pm
Contact: Website

Re: STICKY: Setting up HDMI output when video output is wrong.

Tue Nov 07, 2017 1:19 pm

I'm glad to see the post! I find it absolutely helpful, since i has the same problem. Thanks to this thread, I was able to find a proper solution!

PeterCoghlan
Posts: 2
Joined: Fri Dec 08, 2017 5:22 pm

Re: STICKY: Setting up HDMI output when video output is wrong.

Fri Dec 08, 2017 5:56 pm

I believe I have come across the same issue as BorbingoBoy above.

I have a VGA style monitor connected to my Raspberry Pi using a HDMI to VGA converter. With all the cables plugged in and the monitor turned on, when I power up the Pi, it fails to recognise the presence of the monitor and the monitor receives no signal.

If I add hdmi_hotplug=1 to /boot/config.txt, video is sent to the monitor when the Pi is powered up but this is not a satisfactory solution for several reasons. Firstly, doing this means I have to re-edit /boot/config.txt in order to use the RCA video output rather than just unplugging the HDMI cable. Secondly, The monitor ends up in 640x480 mode instead of the 1024x768 that it is capable of. I can add hdmi_group=2 and hmdi_mode=16 to /boot/config.txt but this is also unsatisfactory as I have several other monitors and I would like to be able to connect whichever monitor is convenient without having to edit /boot/config.txt to suit the particular monitor each time. I would therefore like to avoid using hdmi_hotplug=1 at all.

I have tried several other entries in /boot/config.txt such as config_hdmi_boost and hdmi_drive but non resulted in the monitor being activated after powerup of the Pi except for hdmi_hotplug=1

I discovered that if I reboot the Pi from an SSH session without powering it off, in the course of rebooting, the Pi notices the monitor is connected and sends video to it in the correct 1024x768 resolution ie everything appears to work the way it should. It is only when the Pi is started by powering it on that the problem arises.

My suspicion is that my el-cheapo HDMI to VGA converter takes longer to start up from power-on than the Pi does and when the Pi attempts to query the monitor regarding it's resolution etc, the converter is not yet ready to pass on the request and the Pi decides no monitor is present.

Any suggestions on how to check out my theory?

Is there any way to get the Pi to wait longer at boot time before it queries the HDMI monitor port?

Failing other solutions, any recommendations for a HDMI to VGA converter that does not have this issue?

User avatar
FTrevorGowen
Forum Moderator
Forum Moderator
Posts: 4507
Joined: Mon Mar 04, 2013 6:12 pm
Location: Bristol, U.K.
Contact: Website

Re: STICKY: Setting up HDMI output when video output is wrong.

Fri Dec 08, 2017 7:16 pm

PeterCoghlan wrote: ...
My suspicion is that my el-cheapo HDMI to VGA converter takes longer to start up from power-on than the Pi does and when the Pi attempts to query the monitor regarding it's resolution etc, the converter is not yet ready to pass on the request and the Pi decides no monitor is present.
Any suggestions on how to check out my theory?
Is there any way to get the Pi to wait longer at boot time before it queries the HDMI monitor port?
Failing other solutions, any recommendations for a HDMI to VGA converter that does not have this issue?
1) It may not provide the hotplug signal
2) It may not "pass through" some of the display info. (some pass their "name" rather than that of the display)
3) If it's not externally powered, but can be, that may help.
FWIW, these are the ones I've tried:
http://www.cpmspectrepi.uk/raspberry_pi ... erter.html
http://www.cpmspectrepi.uk/raspberry_pi ... rter2.html
http://www.cpmspectrepi.uk/raspberry_pi ... erter.html
http://www.cpmspectrepi.uk/raspberry_pi ... Audio.html
and notes on "Display Optimisation" which may be of interest and show behaviour "2" happening:
http://www.cpmspectrepi.uk/raspberry_pi ... GA_Monitor
Trev.
Still running Raspbian Jessie on some older Pi's (an A, B1, B2, B+, P2B, 3xP0, P0W) but Stretch on my P3B+, P3B, B+, A+ and a B2. See: https://www.cpmspectrepi.uk/raspberry_pi/raspiidx.htm

PeterCoghlan
Posts: 2
Joined: Fri Dec 08, 2017 5:22 pm

Re: STICKY: Setting up HDMI output when video output is wrong.

Fri Dec 08, 2017 10:21 pm

Many thanks for the pointers.

My monitor is a Fujitsu Siemens SENICVIEW A15-1

tvservice -n reports device_name=FUS-A15-1

tvservice -d followed by edidparser reports HDMI:EDID monitor name is A15-1

These both clearly relate to the monitor rather than the HDMI to VGA converter and gives me no clue as to the identity of the converter I am using. The only thing written on my converter is "VICTSING". It looks rather like the PSG90916 unit in one of the links except that mine is black and has no micro USB or sound ports and not being externally powered, I cannot try powering it before I power up the Pi.

I think it does pass the hotplug signal though because the monitor is successfully detected without my having specified hdmi_hotplug=1 when I reboot the Pi without powering it off. Also, I can disconnect the VGA cable from the monitor and plug in into a different monitor and tvservice -n and tvservice -d then report the name of the new monitor.

As an aside, I also notice that the Pi / converter combination sends enough power down the VGA cable to the monitor to enable the EDID to work even if the power cable to the monitor is disconnected.

woaklb
Posts: 1
Joined: Mon Dec 25, 2017 6:16 pm

Help! Setting up HDMI output when video output is wrong.

Mon Dec 25, 2017 6:29 pm

I also have had video output issues and my efforts to solve the problem have made things worse! Initial problem was a flickering screen. I had bought an HDMI adapter so I could use an old VGA monitor. On seeing the flickering black screen I checked out the forums that suggested changing the settings in the config.txt file. Once booted up I found the line command and I upped the HDMI boost function to 8 as suggested with no effect then read 8 was too high so I tried an alternative approach changing the hdmi_group = 1 and the hdmi_mode = 41. This resulted in the monitor displaying 'out of range' and I have now have no access to the OS. I have tried to access the SD card on my PC and edit the config file back to the original settings but with no success.

Can any kind soul help?

waterc88
Posts: 2
Joined: Fri Feb 02, 2018 2:18 am

HELP HDMI BLINK ONLY

Fri Feb 02, 2018 2:45 am

I make mini laptop project with RPI 3
I already make everything batt...3d printed body... keyboard
and when i plug the hdmi lcd module.. it just blank...and the backlight is ke blink, on and off (it only happen when i plug my rpi 3 )
the lcd module its ok ...i try to plug my laptop ..its fine
the RPI 3 is ok too..i plug to my pc monitor...the hdmi output its fine

FIY:
RPI 3 with RASPBIAN STRETCH (not noob)
lCD module LS059T1SX01
https://www.aliexpress.com/item/5-9-108 ... 46407.html

what have i try and nothing change (config.txt) :
hdmi_mode
hdmi_driver
hdmi_boost
hdmi_hotplug
hdmi_safe

i fell so stupid to go all the way without try to connect the rpi and lcd :(
any suggestion??

Bill378
Posts: 1
Joined: Tue Mar 06, 2018 2:02 pm

Re: STICKY: Setting up HDMI output when video output is wrong.

Tue Mar 06, 2018 2:12 pm

Hello,

New to this site and I'm hoping someone can help me. My setup is as follows, I'm using a Micro SD card and an Ext Hard Drive. The SD card only has a copy of the Boot info and the Ext Hard Drive has the Image. When I boot up the card I'm getting 640/480 and I want to get 1080p. So do I change the (see below) in the config.txt file in both places to get 1080p?

# uncomment to force a specific HDMI mode (this will force VGA)
hdmi_group=1
hdmi_mode=16

Thanks in advance,
Bill

User avatar
saper_2
Posts: 232
Joined: Sun Aug 03, 2014 10:08 am
Location: PL

Re: STICKY: Setting up HDMI output when video output is wrong.

Wed Mar 07, 2018 11:43 pm

Hi,

I have (and not only me :D) a mini hdmi display (kedei 3,5" hdmi - check my review for more info :D).
I got inspired by another owner ot this display - he want to get native resolution with openGL driver enabled - this seems a bit interesting so I started to look around how to get this little fella work at 480x320 with GL driver - the driver pick the highest available resolution that is offered by scaler chip on display board but the displayed image is a bad joke.
I managed to get 720x480 and the image is not so bad BUT I am a real stubborn entity :D

1. Get some data on working display
First I run the display without GL enabled, just with hdmi_cvt option that make display to work in native resolution.
/boot/config.txt:

Code: Select all

hdmi_force_hotplug=1
hdmi_group=2
hdmi_mode=87
hdmi_drive=2
hdmi_cvt 480 320 60 6 0 0 0
And here is my results:

Code: Select all

[email protected]:~ $ tvservice -s
state 0x12000a [HDMI DMT (87) RGB full 15:9 x4], 480x320 @ 59.00Hz, progressive
[email protected]:~ $ tvservice -m DMT
Group DMT has 15 modes:
           mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive
           mode 5: 640x480 @ 72Hz 4:3, clock:31MHz progressive
           mode 6: 640x480 @ 75Hz 4:3, clock:31MHz progressive
           mode 8: 800x600 @ 56Hz 4:3, clock:36MHz progressive
           mode 9: 800x600 @ 60Hz 4:3, clock:40MHz progressive
           mode 10: 800x600 @ 72Hz 4:3, clock:50MHz progressive
           mode 11: 800x600 @ 75Hz 4:3, clock:49MHz progressive
           mode 16: 1024x768 @ 60Hz 4:3, clock:65MHz progressive
           mode 17: 1024x768 @ 70Hz 4:3, clock:75MHz progressive
           mode 18: 1024x768 @ 75Hz 4:3, clock:78MHz progressive
           mode 36: 1280x1024 @ 75Hz 5:4, clock:135MHz progressive
           mode 47: 1440x900 @ 60Hz 16:10, clock:106MHz progressive
           mode 48: 1440x900 @ 75Hz 16:10, clock:136MHz progressive
           mode 49: 1440x900 @ 85Hz 16:10, clock:157MHz progressive
  (prefer) mode 87: 480x320 @ 59Hz 15:9, clock:47MHz x4 progressive
[email protected]:~ $ DISPLAY=:0 xrandr -q
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 480 x 320, current 480 x 320, maximum 480 x 320
default connected 480x320+0+0 0mm x 0mm
   480x320        0.00*
[email protected]:~ $  vcgencmd hdmi_timings
hdmi_timings=1920 0 64 160 224 320 1 3 7 6 0 0 4 59 0 47000004 6
[email protected]:~ $ cvt 480 320 59
# 480x320 57.81 Hz (CVT) hsync: 19.43 kHz; pclk: 11.50 MHz
Modeline "480x320_59.00"   11.50  480 496 536 592  320 323 333 336 -hsync +vsync
[email protected]:~ $ cvt 480 320 59.8
# 480x320 59.07 Hz (CVT) hsync: 19.85 kHz; pclk: 11.75 MHz
Modeline "480x320_59.80"   11.75  480 496 536 592  320 323 333 336 -hsync +vsync
[email protected]:~ $ uname -a
Linux raspberrypi 4.9.59-v7+ #1047 SMP Sun Oct 29 12:19:23 GMT 2017 armv7l GNU/Linux
So I got 47MHz pixel clock :?: and multipler "x4" :? :? :? If I use a refresh 59.8Hz and multiple pixel clock by 4 - from 2nd result from cvt command then I get 47MHz ..... hmmmmmm..... - just thinking...

So let me analyze, the "vcgencmd hdmi_timings" command with options from xrandr

Code: Select all

hdmi_timings=1920 0 64 160 224 320 1 3 7 6 0 0 4 59 0 47000004 6 :
	<h_active_pixels>=1920 (?? - 480*4=1920 - because "x4" multipler?)
	<h_sync_polarity>=0 (-hsync)
	<h_front_porch>=64
	<h_sync_pulse>=160
	<h_back_porch>=224
	<v_active_lines>=320 (320px height - 320 lines)
	<v_sync_polarity>=1 (+vsync)
	<v_front_porch>=3
	<v_sync_pulse>=7
	<v_back_porch>=6
	<v_sync_offset_a>=0
	<v_sync_offset_b>=0 
	<pixel_rep>=4
	<frame_rate>=59 (Refresh 59Hz)
	<interlaced>=0 (non-interlaced)
	<pixel_freq>=47000004 (47MHz)
	<aspect_ratio>=6 (15:9)
I'm not sure what to do with back/front _porch, sync_pulse and pixel_rep...

Enable GL driver and let Pi reboot
So now I have:

Code: Select all

[email protected]:~ $ DISPLAY=:0 xrandr
Screen 0: minimum 320 x 200, current 1280 x 720, maximum 2048 x 2048
HDMI-1 connected primary 1280x720+0+0 (normal left inverted right x axis y axis) 697mm x 392mm
   1280x720      60.00*+  50.00    59.94
   1920x1080     60.00    50.00    59.94
   1920x1080i    60.00    50.00    59.94
   1280x1024     75.02
   1440x900      74.98    59.90
   1024x768      75.03    70.07    60.00
   800x600       72.19    75.00    60.32    56.25
   720x576       50.00
   720x576i      50.00
   720x480       60.00    59.94
   720x480i      60.00    59.94
   640x480       75.00    72.81    60.00    59.94
   720x400       70.08
Composite-1 unknown connection (normal left inverted right x axis y axis)
   720x480       62.69
DSI-1 disconnected (normal left inverted right x axis y axis)
[email protected]:~ $ DISPLAY=:0 xrandr --verbose
Screen 0: minimum 320 x 200, current 1280 x 720, maximum 2048 x 2048
HDMI-1 connected primary 1280x720+0+0 (0x46) normal (normal left inverted right x axis y axis) 697mm x 392mm
        Identifier: 0x42
        Timestamp:  6944
        Subpixel:   unknown
        Gamma:      1.0:1.0:1.0
        Brightness: 1.0
        Clones:
        CRTC:       0
        CRTCs:      0
        Transform:  1.000000 0.000000 0.000000
                    0.000000 1.000000 0.000000
                    0.000000 0.000000 1.000000
                   filter:
        EDID:
                00ffffffffffff004a8b544c01000000
                0c110103814627788aa58ea6544a9c26
                124546afcf009500950f951901010101
                010101010101011d007251d01e206e28
                5500b9882100001e8c0ad08a20e02d10
                103e9600b98821000018000000fd0032
                4b183c0b000a202020202020000000fc
                0033325633482d4836410a2020200129
                020321714e0607020315961112130414
                051f90230907078301000065030c0010
                008c0ad090204031200c405500b98821
                000018011d8018711c1620582c2500b9
                882100009e011d80d0721c1620102c25
                80b9882100009e011d00bc52d01e20b8
                285540b9882100001e023a80d072382d
                40102c4580b9882100001e00000000d0
  1280x720 (0x46) 74.250MHz +HSync +VSync *current +preferred
        h: width  1280 start 1390 end 1430 total 1650 skew    0 clock  45.00KHz
        v: height  720 start  725 end  730 total  750           clock  60.00Hz
  1920x1080 (0x47) 148.500MHz +HSync +VSync
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  67.50KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  60.00Hz
  1920x1080 (0x48) 148.500MHz +HSync +VSync
        h: width  1920 start 2448 end 2492 total 2640 skew    0 clock  56.25KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  50.00Hz
  1920x1080 (0x49) 148.352MHz +HSync +VSync
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  67.43KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  59.94Hz
  1920x1080i (0x4a) 74.250MHz +HSync +VSync Interlace
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  33.75KHz
        v: height 1080 start 1084 end 1094 total 1125           clock  60.00Hz
  1920x1080i (0x4b) 74.250MHz +HSync +VSync Interlace
        h: width  1920 start 2448 end 2492 total 2640 skew    0 clock  28.12KHz
        v: height 1080 start 1084 end 1094 total 1125           clock  50.00Hz
  1920x1080i (0x4c) 74.176MHz +HSync +VSync Interlace
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  33.72KHz
        v: height 1080 start 1084 end 1094 total 1125           clock  59.94Hz
  1280x1024 (0x4d) 135.000MHz +HSync +VSync
        h: width  1280 start 1296 end 1440 total 1688 skew    0 clock  79.98KHz
        v: height 1024 start 1025 end 1028 total 1066           clock  75.02Hz
  1440x900 (0x4e) 136.750MHz -HSync +VSync
        h: width  1440 start 1536 end 1688 total 1936 skew    0 clock  70.64KHz
        v: height  900 start  903 end  909 total  942           clock  74.98Hz
  1440x900 (0x4f) 88.750MHz +HSync -VSync
        h: width  1440 start 1488 end 1520 total 1600 skew    0 clock  55.47KHz
        v: height  900 start  903 end  909 total  926           clock  59.90Hz
  1280x720 (0x50) 74.250MHz +HSync +VSync
        h: width  1280 start 1720 end 1760 total 1980 skew    0 clock  37.50KHz
        v: height  720 start  725 end  730 total  750           clock  50.00Hz
  1280x720 (0x51) 74.176MHz +HSync +VSync
        h: width  1280 start 1390 end 1430 total 1650 skew    0 clock  44.96KHz
        v: height  720 start  725 end  730 total  750           clock  59.94Hz
  1024x768 (0x52) 78.750MHz +HSync +VSync
        h: width  1024 start 1040 end 1136 total 1312 skew    0 clock  60.02KHz
        v: height  768 start  769 end  772 total  800           clock  75.03Hz
  1024x768 (0x53) 75.000MHz -HSync -VSync
        h: width  1024 start 1048 end 1184 total 1328 skew    0 clock  56.48KHz
        v: height  768 start  771 end  777 total  806           clock  70.07Hz
  1024x768 (0x54) 65.000MHz -HSync -VSync
        h: width  1024 start 1048 end 1184 total 1344 skew    0 clock  48.36KHz
        v: height  768 start  771 end  777 total  806           clock  60.00Hz
  800x600 (0x55) 50.000MHz +HSync +VSync
        h: width   800 start  856 end  976 total 1040 skew    0 clock  48.08KHz
        v: height  600 start  637 end  643 total  666           clock  72.19Hz
  800x600 (0x56) 49.500MHz +HSync +VSync
        h: width   800 start  816 end  896 total 1056 skew    0 clock  46.88KHz
        v: height  600 start  601 end  604 total  625           clock  75.00Hz
  800x600 (0x57) 40.000MHz +HSync +VSync
        h: width   800 start  840 end  968 total 1056 skew    0 clock  37.88KHz
        v: height  600 start  601 end  605 total  628           clock  60.32Hz
  800x600 (0x58) 36.000MHz +HSync +VSync
        h: width   800 start  824 end  896 total 1024 skew    0 clock  35.16KHz
        v: height  600 start  601 end  603 total  625           clock  56.25Hz
  720x576 (0x59) 27.000MHz -HSync -VSync
        h: width   720 start  732 end  796 total  864 skew    0 clock  31.25KHz
        v: height  576 start  581 end  586 total  625           clock  50.00Hz
  720x576i (0x5a) 13.500MHz -HSync -VSync Interlace
        h: width   720 start  732 end  795 total  864 skew    0 clock  15.62KHz
        v: height  576 start  580 end  586 total  625           clock  50.00Hz
  720x480 (0x5b) 27.027MHz -HSync -VSync
        h: width   720 start  736 end  798 total  858 skew    0 clock  31.50KHz
        v: height  480 start  489 end  495 total  525           clock  60.00Hz
  720x480 (0x5c) 27.000MHz -HSync -VSync
        h: width   720 start  736 end  798 total  858 skew    0 clock  31.47KHz
        v: height  480 start  489 end  495 total  525           clock  59.94Hz
  720x480i (0x5d) 13.514MHz -HSync -VSync Interlace
        h: width   720 start  739 end  801 total  858 skew    0 clock  15.75KHz
        v: height  480 start  488 end  494 total  525           clock  60.00Hz
  720x480i (0x5e) 13.500MHz -HSync -VSync Interlace
        h: width   720 start  739 end  801 total  858 skew    0 clock  15.73KHz
        v: height  480 start  488 end  494 total  525           clock  59.94Hz
  640x480 (0x5f) 31.500MHz -HSync -VSync
        h: width   640 start  656 end  720 total  840 skew    0 clock  37.50KHz
        v: height  480 start  481 end  484 total  500           clock  75.00Hz
  640x480 (0x60) 31.500MHz -HSync -VSync
        h: width   640 start  664 end  704 total  832 skew    0 clock  37.86KHz
        v: height  480 start  489 end  492 total  520           clock  72.81Hz
  640x480 (0x61) 25.200MHz -HSync -VSync
        h: width   640 start  656 end  752 total  800 skew    0 clock  31.50KHz
        v: height  480 start  490 end  492 total  525           clock  60.00Hz
  640x480 (0x62) 25.175MHz -HSync -VSync
        h: width   640 start  656 end  752 total  800 skew    0 clock  31.47KHz
        v: height  480 start  490 end  492 total  525           clock  59.94Hz
  720x400 (0x63) 28.320MHz -HSync +VSync
        h: width   720 start  738 end  846 total  900 skew    0 clock  31.47KHz
        v: height  400 start  412 end  414 total  449           clock  70.08Hz
Composite-1 unknown connection (normal left inverted right x axis y axis)
        Identifier: 0x43
        Timestamp:  6944
        Subpixel:   unknown
        Clones:
        CRTCs:      0
        Transform:  1.000000 0.000000 0.000000
                    0.000000 1.000000 0.000000
                    0.000000 0.000000 1.000000
                   filter:
        mode: NTSC
                supported: NTSC, NTSC-J, PAL, PAL-M
  720x480 (0x64) 13.500MHz Interlace
        h: width   720 start  734 end  798 total  858 skew    0 clock  15.73KHz
        v: height  480 start  483 end  486 total  502           clock  62.69Hz
DSI-1 disconnected (normal left inverted right x axis y axis)
        Identifier: 0x44
        Timestamp:  6944
        Subpixel:   unknown
        Clones:
        CRTCs:      2
        Transform:  1.000000 0.000000 0.000000
                    0.000000 1.000000 0.000000
                    0.000000 0.000000 1.000000
                   filter:
So now I run "1280x720 (0x46) 74.250MHz +HSync +VSync" but this is unreadable :sad:

Test1
Here is my attempt to translate the vcgencmd hdmi_timings to xrandr arguments:

Code: Select all

[email protected]:~ $ DISPLAY=:0 xrandr --newmode test1 47 1920 1984 2144 2368 320 323 326 336 -hsync +vsync
[email protected]:~ $ DISPLAY=:0 xrandr --addmode HDMI-1 test1
[email protected]:~ $ DISPLAY=:0 xrandr --output HDMI-1 --modetest1
How I got those values - this IS VERY LIKELY WRONG!:

Code: Select all

1984=1920+h_front_porch(64)
2144=1920+h_back_porch(224)
2368=1920+h_front_porch+h_back_porch+h_sync_pulse
323=320+v_front_porch(3)
326=320+v_back_porch(6)
336=320+v_front_porch+v_back_porch+v_sync_pulse
'-hsync'=h_sync_polarity(0)
'+vsync'=v_sync_polarity(1)
It actually work :mrgreen: and the "height" seems fine but width is crazy :lol: (about 4x of screen so the image is shrank in x axis - this look like squeezed box at post office :lol: ) - I know the problem is the "x4" multiplier but I don't know how to apply it in xrandr :/

Anyone know hot to handle the "pixel multipler" in xrandr ?

Ps. the DISPLAY=:0 tell xrandr to access a xorg display not the one on SSH session that I run those command from...

-- EDIT 2018-03-08 00:45+1: forgot to check & fix typos ---

User avatar
saper_2
Posts: 232
Joined: Sun Aug 03, 2014 10:08 am
Location: PL

Re: STICKY: Setting up HDMI output when video output is wrong.

Sun Mar 18, 2018 8:56 pm

Hi,

So no one had any idea... I figured it out...
The dirty way solution
The display have 480x320 px, when I have it in 1920x320 the image is "stretched" but the pixel clock have ~47MHz this is allowed value by the scaler chip on display board. So I used a "scale" option from xrandr.
Here is the simple bash script that "reconfigure the display":

Code: Select all

[email protected]:~ $ cat gldrvtest
#!/bin/bash
DISPLAY=:0 xrandr --newmode test1 47 1920 1984 2144 2368 320 323 326 336 -hsync +vsync
DISPLAY=:0 xrandr --addmode HDMI-1 test1
DISPLAY=:0 xrandr --output HDMI-1 --mode test1
DISPLAY=:0 xrandr --output HDMI-1 --scale 0.25x1

[email protected]:~ $ ./gldrvtest
Attachments
xrandr_resize_scale_test1.jpg
xrandr_resize_scale_test1.jpg (62.58 KiB) Viewed 1988 times

elpa02
Posts: 3
Joined: Thu Mar 22, 2018 9:00 pm

Re: STICKY: Setting up HDMI output when video output is wrong.

Fri Mar 23, 2018 1:40 pm

Dear all,

I face a similar problem with my raspberry pi 3 model b and i hope to your experience. To be more specific :
I set up kodi over xbian on a Samsung 50UE6500 and everything worked fine (hdmi, cec) etc.
Then i connected raspberry to a LG LE5500 but even if the hdmi input seems to be activated (from the TV menu) there is no video at all.
I tried all of the LG's 4 hdmi inputs with 2 different cables which cables are working on a PC monitor (LG also).
After i tried many hacks i found in different forums like hdmi_hotplug, mode, safe, drive etc with no luck.
LG's CEC aka simplink seems to recognize that something is conected on the TV cause among "TV" there is another option activated -"HDD player"- in the same way the hdmi input is activated.

Since the raspberry is not faulty what else i could do to overcome this situation?
Is Xbian a good choice or there are better alternatives to set up kodi?

Any help is appreciated.

trustytrev
Posts: 2
Joined: Thu Mar 29, 2018 10:54 pm

Re: STICKY: Setting up HDMI output when video output is wrong.

Thu Mar 29, 2018 11:59 pm

Hello,
This is my first post here so I hope I am in the right place. I have a Pi Zero W and it boots up OK and HDMI output works.
I have used an sd card with the latest version of Rasabian and it works OK. I have used an sd card with NOOBS and that works OK.
However when I try the same setup using a RASPBERRY Pi 3 Model B with the same sd card setup cables/connections and TV I get no video output.
I assume from this the PI 3 is faulty. Does the scenario I have described make my conclusion very likely or have I maybe overlooked something.
I did try making changes in the config.txt file using the information in the Video/Display section. The only time I got a display with the Pi 3 was when I un-commented
# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

That was no good though because the image was blurred and unreadable.
I would just like a second opinion before I return the Pi 3 to the seller.
Thank you.

User avatar
FTrevorGowen
Forum Moderator
Forum Moderator
Posts: 4507
Joined: Mon Mar 04, 2013 6:12 pm
Location: Bristol, U.K.
Contact: Website

Re: STICKY: Setting up HDMI output when video output is wrong.

Fri Mar 30, 2018 5:34 pm

trustytrev wrote:
Thu Mar 29, 2018 11:59 pm
Hello,
This is my first post here so I hope I am in the right place. I have a Pi Zero W and it boots up OK and HDMI output works.
I have used an sd card with the latest version of Rasabian and it works OK. I have used an sd card with NOOBS and that works OK.
However when I try the same setup using a RASPBERRY Pi 3 Model B with the same sd card setup cables/connections and TV I get no video output.
I assume from this the PI 3 is faulty. Does the scenario I have described make my conclusion very likely or have I maybe overlooked something.
I did try making changes in the config.txt file using the information in the Video/Display section. The only time I got a display with the Pi 3 was when I un-commented

Code: Select all

# uncomment if you get no picture on HDMI for a default "safe" mode
That was no good though because the image was blurred and unreadable.
I would just like a second opinion before I return the Pi 3 to the seller.
Thank you.
Two things to try first:
1) Instead of using the card from the Pi0W try a different card with a Raspbian imaged via Etcher** rather than a NOOBS install.
2) Since your Pi0W works with your display (what is it?) and use the tvservice command on that to found out what HDMI settings are "preferred" or "native" modes**** and use that info. to modify the HDMI settings in the P3B's config.txt
Trev.
** https://www.raspberrypi.org/documentati ... /README.md
**** More info./examples here: http://www.cpmspectrepi.uk/raspberry_pi ... tings.html
Still running Raspbian Jessie on some older Pi's (an A, B1, B2, B+, P2B, 3xP0, P0W) but Stretch on my P3B+, P3B, B+, A+ and a B2. See: https://www.cpmspectrepi.uk/raspberry_pi/raspiidx.htm

elpa02
Posts: 3
Joined: Thu Mar 22, 2018 9:00 pm

Re: STICKY: Setting up HDMI output when video output is wrong.

Tue Apr 03, 2018 6:17 am

Following my previous message here is what i've tried since then with no success meant i still get a "no signal"
I have made a fresh installation of 17.3 Kodi over latest LibreELEC on Raspberry Pi 3, which is connected to a LG 42LE5500.
I have tried only all 4 LG's HDMI connections and i ve tried to power on rasp pi3 before LG is on, after, on standby etc.

Since LibreELEC's default config file the whole set up didnt play i've tried many hacks combinations found in different forums with no success like:
hdmi_ignore_cec_init=1
hdmi_force_hotplug=1
hdmi_boost=4,5,6,7 till 9
hdmi_safe=1 (alone)

Then i made a SSH connection and run tvservice for both DMT and CEA modes and i was returned that the LG plays both. CEAs are many more with native mode 4 and prefered one mode 16. After that i add some lines in config
config_hdmi_boost=7
hdmi_group=1
hdmi_mode=4 (and hdmi_mode=16)
but still no signal.

In every attempt LG recognises the hdmi where Rasp is connected to and in the case that LG was in standby mode it switches on automatically to the correct hdmi input showing the simplink logo but stiil no signal.
Any help is appreciated

PS. I've tried different cables and monitors. On a LG pc monitor W2361V and on a Samsung 50UE6500 everything works fine with the same cables , CEC functions etc.

User avatar
FTrevorGowen
Forum Moderator
Forum Moderator
Posts: 4507
Joined: Mon Mar 04, 2013 6:12 pm
Location: Bristol, U.K.
Contact: Website

Re: STICKY: Setting up HDMI output when video output is wrong.

Tue Apr 03, 2018 3:38 pm

elpa02 wrote:
Tue Apr 03, 2018 6:17 am
Following my previous message here is what i've tried since then with no success meant i still get a "no signal"
I have made a fresh installation of 17.3 Kodi over latest LibreELEC on Raspberry Pi 3, which is connected to a LG 42LE5500.
I have tried only all 4 LG's HDMI connections and i ve tried to power on rasp pi3 before LG is on, after, on standby etc.
...
To rule out a possible specific "Kodi/LibreELEC only" issue, can you try using the most recent version of Raspbian Stretch (I don't use Kodi/LibreELEC so cannot comment on whether there are any subtle differences in the display auto-setup or config.txt mechanisms.)
Trev.
Still running Raspbian Jessie on some older Pi's (an A, B1, B2, B+, P2B, 3xP0, P0W) but Stretch on my P3B+, P3B, B+, A+ and a B2. See: https://www.cpmspectrepi.uk/raspberry_pi/raspiidx.htm

trustytrev
Posts: 2
Joined: Thu Mar 29, 2018 10:54 pm

Re: STICKY: Setting up HDMI output when video output is wrong.

Sat Apr 07, 2018 4:21 pm

Hello,
I tried another Pi3 and it worked fine so it looks like I had a faulty one.
Thank you.
trustytrev. :)

elpa02
Posts: 3
Joined: Thu Mar 22, 2018 9:00 pm

Re: STICKY: Setting up HDMI output when video output is wrong.

Sat Apr 07, 2018 6:02 pm

[/quote]
To rule out a possible specific "Kodi/LibreELEC only" issue, can you try using the most recent version of Raspbian Stretch (I don't use Kodi/LibreELEC so cannot comment on whether there are any subtle differences in the display auto-setup or config.txt mechanisms.)
Trev.
[/quote]

Instead of what you proposed I tried first a fresh kodi installation over OSMC still "no signal". So up until now Xbian, LibreELEC and OSMC didn't help. It seems that is an incompatibility between Raspberry Pi3 and LG 42LE5500 that I haven't figured out yet and I assume that has nothing to do with the kodi or the OS itself.
My last hope is Raspbian. Can you help me on how to install kodi over Raspbian?

amigamax
Posts: 2
Joined: Sat Jul 25, 2015 5:04 am

Re: STICKY: Setting up HDMI output when video output is wrong.

Fri Jun 08, 2018 10:29 pm

I am having a problem (I suspect) that the pi boots up and gets no response from the TV (It was not initially powered on on a particular boot - old 720P TV using HDMI and sets the default video mode to something the TV can not sync to. Would it not be a good idea to embed something into the OS where one could temporarily (45 sec etc) set the mode to 1024x768 @ 60 hz or 1280 x 720 @ 60 hz to allow for resetting with raspi-config? thoughts?? CTRL-ALT-7 720p CTRL-ALT-V VGA [email protected] etc??? i can't edit the file because i can't see the screen. i think i have SSH off... thoughts anyone?? I have a HDMI to VGA adapter i normally use to force it to work when the sync is out of range or offset in HDMI mode but all i get is a flashing cursor.

[email protected]

Return to “Troubleshooting”

Who is online

Users browsing this forum: Baidu [Spider] and 49 guests