Setting up HDMI output


318 posts   Page 2 of 13   1, 2, 3, 4, 5 ... 13
by deadlyfingers » Tue May 29, 2012 12:06 am
Still can't seem to get HDMI working... I'm get the following results:
[root@alarmpi ~]# LD_LIBRARY_PATH=/opt/vc/lib /opt/vc/bin/tvservice -s
state 0x40001, 720x480 @ 60Hz, interlaced
[root@alarmpi ~]# LD_LIBRARY_PATH=/opt/vc/lib /opt/vc/bin/tvservice -m CEA
Group CEA has 0 modes:
[root@alarmpi ~]# LD_LIBRARY_PATH=/opt/vc/lib /opt/vc/bin/tvservice -m DMT
Group DMT has 0 modes:

I'm running the Arch Linux ARM image.

What should I try next - a different Linux distribution? or is there something I'm missing here?
Posts: 5
Joined: Mon May 28, 2012 8:42 pm
by dukla2000 » Tue May 29, 2012 8:35 am
deadlyfingers wrote:What should I try next - a different Linux distribution? or is there something I'm missing here?
Seems to me your monitor isn't HDMI! Are our you plugged into the monitor and running at 720*480 when you ran those tvservice results? Have you got any hdmi stuff in your config.txt?

Could try
1. Run “tvservice –d <file>” to capture a monitor’s EDID.
2. Pass this file to edidparser. Run “edidparser <file>”.
As per first post and put the results here - I would doubt it is distribution problems (but worth clutching at straws) - more likely a cable/monitor issue.
Posts: 109
Joined: Tue Jan 10, 2012 12:02 am
Location: Reading.UK.EU
by piglet » Tue May 29, 2012 8:46 am
Hi John,

create/edit /boot/config.txt, and add the line:

hdmi_force_hotplug=1

That should force HDMI.
User avatar
Posts: 569
Joined: Sat Aug 27, 2011 1:16 pm
by timboe » Thu May 31, 2012 11:53 pm
Just a quick note, I was having no luck with my DVI-D monitor (HDMI one was fine)

Turned out to be that I was using the same HDMI cable for both, with a HDMI to DVI-D adapter when plugging into the DVI monitor. Could cause the monitor to come out of sleep and search but never got an image.

Buying a £2 HDMI to DVI-D cable off of amazon has sorted me.
Posts: 1
Joined: Sat May 19, 2012 6:50 pm
by dom » Fri Jun 01, 2012 9:06 am
@deadlyfingers
It seems some Arch images incorrectly have a config.txt file that forces a hdmi mode. Please delete that file if it exists (/boot/config.txt).

Also updating firmware could help (with Hexxeh's tool).
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 4042
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge
by Peter Ryan » Fri Jun 01, 2012 10:16 pm
Hi all!

I have a Samsung SyncMaster 2032MW TV/Monitor[1]. It's a 20" screen with a 1680x1050 native resolution and I'm connected using HDMI.

For some reason, the Pi only seems to want to output 1920x1080. If I try to set a mode, the monitor won't show anything. If I try and force it using "hdmi_ignore_edid=0xa5000080" then the monitor just says "Mode not supported".

Here's my tvservice / edid parsings:
Code: Select all
$ ./tvservice -m CEA
Group CEA has 11 modes:
           mode 1: 640x480 @ 60Hz, progressive
           mode 2: 720x480 @ 60Hz, progressive
           mode 3: 720x480 @ 60Hz, progressive
           mode 4: 1280x720 @ 60Hz, progressive
  (native) mode 5: 1920x1080 @ 60Hz, interlaced
           mode 16: 1920x1080 @ 60Hz, progressive
           mode 17: 720x576 @ 50Hz, progressive
           mode 18: 720x576 @ 50Hz, progressive
           mode 19: 1280x720 @ 50Hz, progressive
           mode 20: 1920x1080 @ 50Hz, interlaced
           mode 31: 1920x1080 @ 50Hz, progressive
$ ./tvservice -m DMT
Group DMT has 1 modes:
           mode 4: 640x480 @ 60Hz, progressive
$ ./edidparser /tmp/edidit.txt
Parsing /tmp/edidit.txt...
HDMI:EDID version 1.3, 1 extensions, screen size 16x9 cm
HDMI:EDID features - videodef 0x80 !standby !suspend !active off; colour encoding:RGB444|YCbCr422; sRGB is not default colourspace; preferred format is native; does not support GTF
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 49-61 Hz, horizontal is 27-68 kHz, max pixel clock is 150 MHz
HDMI:EDID monitor range does not support GTF
HDMI:EDID found monitor name descriptor tag 0xfc
HDMI:EDID monitor name is SAMSUNG
HDMI:EDID found preferred CEA detail timing format: 1920x1080i @ 60 Hz (5)
HDMI:EDID found CEA detail timing format: 1280x720p @ 60 Hz (4)
HDMI:EDID established timing I/II bytes are 20 00 00
HDMI:EDID found DMT format: code 4, 640x480p @ 60 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 CEA detail timing format: 720x480p @ 60 Hz (2)
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: 720x576p @ 50 Hz (17)
HDMI:EDID found CEA detail timing format: 1920x1080p @ 60 Hz (16)
HDMI:EDID found CEA format: code 5, 1920x1080i @ 60Hz (native)
HDMI:EDID found CEA format: code 4, 1280x720p @ 60Hz
HDMI:EDID found CEA format: code 3, 720x480p @ 60Hz
HDMI:EDID found CEA format: code 20, 1920x1080i @ 50Hz
HDMI:EDID found CEA format: code 19, 1280x720p @ 50Hz
HDMI:EDID found CEA format: code 18, 720x576p @ 50Hz
HDMI:EDID found CEA format: code 16, 1920x1080p @ 60Hz
HDMI:EDID found CEA format: code 31, 1920x1080p @ 50Hz
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 6
HDMI:EDID HDMI VSDB has physical address 1.0.0.0
HDMI:EDID HDMI VSDB supports AI:yes, dual link DVI:no
HDMI:EDID HDMI VSDB deep colour support - 48-bit:no 36-bit:no 30-bit:no DC_yuv444:no
HDMI:EDID HDMI VSDB has no latency information
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 is now CEA (2) 720x480p @ 60 Hz with pixel clock 27 MHz (score 4141472)
HDMI:EDID CEA mode (3) 720x480p @ 60 Hz with pixel clock 27 MHz has a score of 141472
HDMI:EDID best score mode is now CEA (4) 1280x720p @ 60 Hz with pixel clock 74 MHz (score 4710592)
HDMI:EDID best score mode is now CEA (5) 1920x1080i @ 60 Hz with pixel clock 74 MHz (score 5473248)
HDMI:EDID CEA mode (16) 1920x1080p @ 60 Hz with pixel clock 148 MHz has a score of 2348832
HDMI:EDID CEA mode (17) 720x576p @ 50 Hz with pixel clock 27 MHz has a score of 2641472
HDMI:EDID CEA mode (18) 720x576p @ 50 Hz with pixel clock 27 MHz has a score of 141472
HDMI:EDID CEA mode (19) 1280x720p @ 50 Hz with pixel clock 74 MHz has a score of 3192160
HDMI:EDID CEA mode (20) 1920x1080i @ 50 Hz with pixel clock 74 MHz has a score of 3807360
HDMI:EDID CEA mode (31) 1920x1080p @ 50 Hz with pixel clock 148 MHz has a score of 307360
HDMI:EDID preferred mode remained as CEA (5) 1920x1080i @ 60 Hz with pixel clock 74 MHz
HDMI:EDID has HDMI support and audio support
edid_parser exited with code 0


I'm going to hazard a wild stab in the dark and guess the problem is 'cos the screen itself doesn't mention 1680x1050 at all! Amiright?!

Any help appreciated!

Peter.

[1] Full monitor specs here: http://www.samsung.com/levant/consumer/ ... 0PMASF/XSG
Posts: 10
Joined: Sat Mar 03, 2012 12:44 am
by dom » Fri Jun 01, 2012 10:45 pm
Well, your monitor doesn't report that it supports 1680x1050 in the EDID.
It also reports that 1920x1080i is it's native resolution (usually meant to mean matches the number of pixels) and is its preferred resolution.
So we choose to output 1920x1080i. There's no evidence that we should do anything else.

If I were to try to force the monitor, I'd go for:
hdmi_group=2
hdmi_mode=57
hdmi_ignore_edid=0xa5000080

But if the monitor doesn't like that then you are out of luck I'm afraid. (*)

(*) We are considering allowing completely arbitrary settings of clocks, widths, heights, blanking periods to be specified somehow for completely non-standard monitors, but no promises, and probably not for some time. And no guarantees that you would be able to find the setttings that your monitor wants.
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 4042
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge
by Peter Ryan » Fri Jun 01, 2012 11:28 pm
Thanks for the reply dom!

I tried your settings but the screen just says "Mode not supported", so I guess I'm out of luck. :(

It is usable though, and I'll l'm SSHing in for a lot of things... so not the end of the world. Not sure if this is a common issue with Samsung screens though; I had a problem a year or so ago trying to connect a PC running Ubuntu up to a Samsung P2270HD (native 1920x1080) and couldn't get that to play nicely either - I ended up connecting via DVI as HDMI just wouldn't get the correct resolution.
Posts: 10
Joined: Sat Mar 03, 2012 12:44 am
by joecon » Sat Jun 02, 2012 3:32 am
I got 1080p 60Hz running using this config.txt file:

hdmi_force_hotplug=1
hdmi_drive=1
hdmi_mode=16
disable_overscan=1

Any confusion about what each line does just check the first couple posts.
Hope this helps!
Posts: 1
Joined: Sat Jun 02, 2012 3:14 am
by lanlafi » Sat Jun 02, 2012 2:29 pm
I have a Samsung 2243SW monitor (22", 16:9, 1920x1080). I connected it with HDMI-DVI cable. The Pi booted up, the picture was small, resolution on the monitor 1600x1200, the Pi framebuffer was a bit smaller, some very odd numbers.

I quickly runned tvservice and saw that the monitor was missing the 1920x1080 60Hz definition in it's EDID. I could "force it" to 1680x1050 with config.txt, which was in the EDID. II've tried to force it to 1920x1080, but no picture then.

Last night, after some googling we managed to read and edit the EDID information of the monitor, added the missing definition, and wrote it back to the monitor (using a PC).

Since then, the Pi boots straight into the proper 1920x1080 res with only disable overscan in the config.txt.

The tools used for EDID: tvservice on the Pi to read and dump EDID. Hexdump on the Pi to convert to Hexadecimal text, Phoenix EDID Editor on the PC to add the missing mode, ddcw.exe on the PC to write it back into the monitor.

But this is only recommended for pros, as it can make the monitor unusable.
Posts: 16
Joined: Sat Jun 02, 2012 9:15 am
by dom » Sat Jun 02, 2012 2:42 pm
Latest start.elf from github has a secret option:
hdmi_edid_file=1
Enable that and put a file "edid.dat" on the boot partition and it will use the edid.dat file rather than reading from the display.
I don't recommend using this, but if you're going to be programming your monitor's edid, then at least test that the file you are programming helps!
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 4042
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge
by lanlafi » Sat Jun 02, 2012 3:36 pm
That is a good option.

Is this newest loader/firmware the one which displays a colorful screen just before linux starts to boot? Was it released 1-2 days ago?

I've had one issue with it using pisces raspbian. I was set up to 1680x1050 in config.txt, and it booted fine, but every couple of sec the screen went black for a second, then came back to normal. If I removed the hdmi* options from config.txt, I got normal working screen without blanking. Since the EDID update of the monitor, I have no problems with the screen at all. And Debian with the older firmware also worked fine with 1680x1050 in config.txt
Posts: 16
Joined: Sat Jun 02, 2012 9:15 am
by dom » Sat Jun 02, 2012 3:45 pm
lanlafi wrote:Is this newest loader/firmware the one which displays a colorful screen just before linux starts to boot? Was it released 1-2 days ago?

Yes. Although there was more that one update with the coloured square so I would like to know if updating again affects the problem you saw.
lanlafi wrote:I've had one issue with it using pisces raspbian. I was set up to 1680x1050 in config.txt, and it booted fine, but every couple of sec the screen went black for a second, then came back to normal. If I removed the hdmi* options from config.txt, I got normal working screen without blanking. Since the EDID update of the monitor, I have no problems with the screen at all. And Debian with the older firmware also worked fine with 1680x1050 in config.txt


Can you be clearer? Exactly what goes settings in the config.txt are needed for blanking to occur (minimal list).
Are you setting the same mode as is automatically detected with no config.txt?
Does "config_hdmi_boost=4" have any effect on the blanking?
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 4042
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge
by lanlafi » Sat Jun 02, 2012 4:22 pm
Testing it right now with the following confg.txt (same as when the problem occured):

hdmi_drive=1
hdmi_group=2
hdmi_mode=0x3a
disable_overscan=1

uptime is now 13 minutes, running pisces, X, Midori, scrolling in webpages, and only 2 blanking occured. So I cannot reproduce it the same way any more.
Posts: 16
Joined: Sat Jun 02, 2012 9:15 am
by dom » Sat Jun 02, 2012 4:42 pm
Can you try adding config_hmdi_boost=4 and see if blanking goes away?
Can you try hdmi_mode=0x39 rather than 0x3a?
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 4042
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge
by latro666 » Thu Jun 07, 2012 8:25 pm
Ok so got the Pi today and have put it into 32" HDMI tv and it says the native resolution is 1280x720 using /tvservice -m CEA

My PC running Windows 7 connects to the same TV over DVI to its VGA port and runs 1360x768, a mode not supported from the above (assume this is a DVI/HDMI thing).

Problem is the pi looks on this TV (i'v tried several modes in the config) like complete toilet compared the DVI mode running windows. Its not a windows has aero thing, the text simply looks blurry/stretched.

Kinda baffles me a tiny bit about the testing of the concept that pluging-and-playing so to speak can result in a very poor screen, ok for us who can work out how to adjust it but kids programming? we'll have a nation of blind computer scientists :D.

I tried to do a print screen, after using scrot to take the picture i tried to use the pi to send the pic via gmail and when that failed, photobucket, appears its incapable of running these websites :(. You wont be able to do much programming on this if you cant view modern websites...

sorry turned into a rant, bit disappointed is all, think web browsing might of been a better thing to get right than playing HD videos...

any ideas on the HDMI thing, might try it with an old monitor.
Posts: 9
Joined: Thu Jun 07, 2012 7:45 pm
by dom » Thu Jun 07, 2012 11:10 pm
Well 1360x768 is a DMT mode, so "tvservice -m DMT" would be more useful.
Try:
hdmi_group=2
hdmi_mode=39

(see http://elinux.org/RPi_config.txt for more info).

If there is still a problem, capture your edid (tvservice -d edid.dat) and post it here.
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 4042
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge
by latro666 » Fri Jun 08, 2012 8:11 am
Thanks for the reply, yea, did a bit of research after posting. It appears to be more of a general issue of outputting any PC desktop over HDMI, something to do with pixel ratios etc...

The -DMT showed like one res and it was very low. 1360x768 is perfect but ofc you can only get this via the TV's VGA in.

I actually tried that exact config as a punt, it just didnt load anything onscreen. Assume this is because that mode isn't HDMI.

So begs the question is there anyway to sort this, pretty annoying really, never had much luck with HDMI.
Posts: 9
Joined: Thu Jun 07, 2012 7:45 pm
by dom » Fri Jun 08, 2012 8:52 am
The EDID can be different per port (eg HDMI/DVI). Connecting Pi through DVI port with HDMI to DVI adaptor would probably give the resolution you want.

First try:
hdmi_group=2
hdmi_mode=39
hdmi_ignore_edid=0xa5000080
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 4042
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge
by latro666 » Fri Jun 08, 2012 7:08 pm
Sadly did not work
Posts: 9
Joined: Thu Jun 07, 2012 7:45 pm
by freakiwombatman » Fri Jun 08, 2012 8:23 pm
bredman wrote:As I said earlier, I was unhappy that this post was not suitable for Absolute Beginners.

Rather than just complain, I got off my ass to improve it. I have rewritten the wiki page http://elinux.org/RPi_config.txt to be more suitable for beginners. It now includes instructions on how to edit the config.txt file and has a more logical presentation of the parameters and their values.

Does anybody know what the terms "2x", "4x" and "H" represent?

Feedback is welcome if somebody thinks it could be improved more.


thanks so much for this made my life soooo much easier as a newbie
Posts: 7
Joined: Tue Jun 05, 2012 8:12 pm
by listerdude » Sun Jun 10, 2012 7:44 am
Nice Wiki page but I'm still a little confused as a noob. I noticed your example file right at the start and you have a line that says hdmi_mode=0x10 but I can't see any modes that have a 0x10 in the list further down. Where is does that mode come from? in fact I've seen people posting other modes that start 0x but cant understand why you need the 0x.
Posts: 2
Joined: Sun Jun 10, 2012 7:17 am
by dom » Sun Jun 10, 2012 10:18 am
0x10 is a hexadecimal number (base 16) commonly used by programmers. It is exactly the same as 16. I've changed the wiki to use the decimal version.
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 4042
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge
by davaka » Sun Jun 10, 2012 1:14 pm
Perhaps I am looking at it wrong but the /boot folder is empty on my SD card.

Is there a step by step tutorial available for setting the hdmi resolution?
I cannot find where to change these settings.

Thanks!
I am still learning. be patient
Posts: 7
Joined: Wed Jun 06, 2012 7:33 pm
Location: Netherlands
by dom » Sun Jun 10, 2012 1:22 pm
Where are you looking from?
From Pi, it looks like /boot
From windows it will just be root of sdcard (e.g. E:\)
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 4042
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge