dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5318
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Resolution help... again.

Sun Jun 03, 2012 4:38 pm

Actually you captured "edit.dat" so try:
/opt/vc/bin/edidparser edit.dat
Can you attach the edit.dat file to your next message? (click on upload attachment when posting)

TheFreeman04
Posts: 28
Joined: Mon Feb 20, 2012 4:42 pm

Re: Resolution help... again.

Sun Jun 03, 2012 5:43 pm

HDMI:EDID version 1.3, 1 extensions, screen size 88x50 cm
HDMI:EDID features - videodef 0xa0 !standby !suspend active off; colour encoding:RGB444|YCbCr422; sRGB is not default colourspace; preferred format is native; does not support GTF
HDMI:EDID ignored unknown descriptor tag 0x0
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 50-60 Hz, horizontal is 30-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 LONTIUM
HDMI:EDID found preferred CEA detail timing format: 1920x1080p @ 60 Hz (16)
HDMI:EDID established timing I/II bytes are 21 08 00
HDMI:EDID found DMT format: code 4, 640x480p @ 60 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 16, 1024x768p @ 60 Hz in established timing I/II
HDMI:EDID standard timings block x 8: 0x6140 A940 0101 0101 0101 0101 0101 0101
HDMI:EDID found DMT format: code 16, 1024x768p @ 60 Hz (4:3) in standard timing 0
HDMI:EDID found DMT format: code 51, 1600x1200p @ 60 Hz (4:3) in standard timing 1
HDMI:EDID parsing v3 CEA extension 0
HDMI:EDID monitor support - underscan IT formats:yes, 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 format: code 16, 1920x1080p @ 60Hz
HDMI:EDID found CEA format: code 31, 1920x1080p @ 50Hz
HDMI:EDID found CEA format: code 4, 1280x720p @ 60Hz (native)
HDMI:EDID does not understand CEA format code 0
HDMI:EDID does not understand CEA format code 0
HDMI:EDID does not understand CEA format code 0
HDMI:EDID found CEA format: code 2, 720x480p @ 60Hz
HDMI:EDID does not understand CEA format code 0
HDMI:EDID does not understand CEA format code 0
HDMI:EDID does not understand CEA format code 0
HDMI:EDID does not understand CEA format code 0
HDMI:EDID found audio format 2 channels PCM, sample rate: 32|44|48 kHz, sample size: 16|20|24 bits
HDMI:EDID found Video Capability DB length 2
HDMI:EDID video capability: CE:3 IT:3 PT:0 QS:0
HDMI:EDID found HDMI VSDB length 7
HDMI:EDID HDMI VSDB has physical address 2.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 max TMDS clock 225 MHz
HDMI:EDID HDMI VSDB has no latency information
HDMI:EDID adding mandatory support for CEA (1) 640x480p @ 60Hz
HDMI:EDID adding mandatory support for CEA (3) 720x480p @ 60Hz
HDMI:EDID adding mandatory support for CEA (17) 720x576p @ 50Hz
HDMI:EDID adding mandatory support for CEA (18) 720x576p @ 50Hz
HDMI:EDID adding mandatory support for CEA (19) 1280x720p @ 50Hz
HDMI:EDID filtering formats with pixel clock > 162 MHz or h. blanking > 1023
HDMI:EDID filtering out CEA format: 640x480p @ 60 Hz (1) with pixel clock 25 MHz and hfp:16 hs:96 hbp:48
HDMI:EDID filtering out CEA format: 720x480p @ 60 Hz (2) with pixel clock 27 MHz and hfp:16 hs:62 hbp:60
HDMI:EDID filtering out CEA format: 720x480p @ 60 Hz (3) with pixel clock 27 MHz and hfp:16 hs:62 hbp:60
HDMI:EDID filtering out CEA format: 1280x720p @ 60 Hz (4) with pixel clock 74 MHz and hfp:110 hs:40 hbp:220
HDMI:EDID filtering out DMT format: 640x480p @ 60 Hz (4) with pixel clock 25 MHz and hfp:16 hs:96 hbp:48
HDMI:EDID filtering out DMT format: 800x600p @ 60 Hz (9) with pixel clock 40 MHz and hfp:40 hs:128 hbp:88
HDMI:EDID filtering out CEA format: 1920x1080p @ 60 Hz (16) with pixel clock 148 MHz and hfp:88 hs:44 hbp:148
HDMI:EDID filtering out DMT format: 1024x768p @ 60 Hz (16) with pixel clock 65 MHz and hfp:24 hs:136 hbp:160
HDMI:EDID filtering out CEA format: 720x576p @ 50 Hz (17) with pixel clock 27 MHz and hfp:12 hs:64 hbp:68
HDMI:EDID filtering out CEA format: 720x576p @ 50 Hz (18) with pixel clock 27 MHz and hfp:12 hs:64 hbp:68
HDMI:EDID filtering out CEA format: 1280x720p @ 50 Hz (19) with pixel clock 74 MHz and hfp:440 hs:40 hbp:220
HDMI:EDID filtering out CEA format: 1920x1080p @ 50 Hz (31) with pixel clock 148 MHz and hfp:528 hs:44 hbp:148
HDMI:EDID filtering out DMT format: 1600x1200p @ 60 Hz (51) with pixel clock 162 MHz and hfp:64 hs:192 hbp:304
HDMI:EDID preferred mode is updated to CEA (1) 640x480p @ 60 Hz with pixel clock 25200000 Hz
HDMI:EDID has HDMI support and audio support
edid_parser exited with code 0

TheFreeman04
Posts: 28
Joined: Mon Feb 20, 2012 4:42 pm

Re: Resolution help... again.

Sun Jun 03, 2012 5:44 pm

I couldn't open the file; so i pasted from my raspberry.

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5318
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Resolution help... again.

Sun Jun 03, 2012 6:01 pm

Are you going through a HDMI to VGA adaptor?

TheFreeman04
Posts: 28
Joined: Mon Feb 20, 2012 4:42 pm

Re: Resolution help... again.

Sun Jun 03, 2012 6:25 pm

Yes, Is that by any chance the problem? :|

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5318
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Resolution help... again.

Sun Jun 03, 2012 8:42 pm

Well the EDID is being generated by the adaptor and it looks like garbage - reporting modes your monitor doesn't support and not reporting modes it does support.

Try adding:
hdmi_ignore_edid=0xa5000080

and see if forcing a mode works any better. I'm guessing the adaptor won't support 1280x1024, but on the off chance try:
hdmi_group=2
hdmi_mode=35

But otherwise you'll have to pick something from the parsed EDID list that both adaptor and display support.

TheFreeman04
Posts: 28
Joined: Mon Feb 20, 2012 4:42 pm

Re: Resolution help... again.

Sun Jun 03, 2012 9:28 pm

Gave me an interesting result; monitor shows neither the RPi's image or a "no signal message".
Cheers for the help :D

TheFreeman04
Posts: 28
Joined: Mon Feb 20, 2012 4:42 pm

Re: Resolution help... again.

Sun Jun 03, 2012 9:47 pm

Is there any way to add resolutions to the RPi, maybe adding 1280x800?

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5318
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Resolution help... again.

Sun Jun 03, 2012 9:51 pm

We can drive 1280x800.
http://elinux.org/RPi_config.txt

hdmi_group=2
hdmi_mode=27
hdmi_ignore_edid=0xa5000080

but there's no evidence your adaptor/display combination will support it.

TheFreeman04
Posts: 28
Joined: Mon Feb 20, 2012 4:42 pm

Re: Resolution help... again.

Sun Jun 03, 2012 9:54 pm

Hmmm, again, no image or "no display" message. Guess I'm stuck with 720p :|

dgwsoft
Posts: 3
Joined: Sun Jul 01, 2012 4:47 pm

Similar problem

Sun Jul 01, 2012 5:16 pm

Hello everyone,

I have a similar issue. I went out and bought the cheapest HDMI television I could lay my hands on (ALBA LED 16911DVDP, £69.99 from Argos).

It works pretty much out-of-the box with my RPi, but at its "native" 1920x1080 the text is a bit small and poor quality. I have messed with config.txt to get 1280x720 (according to tvservice -s) which looks about right, but X is actually displaying at 1184x664 (according to Display Settings). I suspect it would look better at a genuine 1280x720 (correct aspect ratio), and would like to figure out how to make it do that.

I have tried most of the things discussed in this thread, including setting the frame buffer size, but this has no effect.

What I think I am missing is an overview of the problem. I am used to working with xorg.config, but RPi (debian build) does not have one and (as others have noted) won't create one with Xorg -configure. Why? Is it worth trying to create one by hand or is there some reason we don't use xorg.config here? Can/should everything be done in /boot/config.txt? Is displaying on an HDMI telly somehow different from using an DVI or VGA computer monitor?

Thanks for any help with this.

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5318
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Similar problem

Sun Jul 01, 2012 5:27 pm

dgwsoft wrote:It works pretty much out-of-the box with my RPi, but at its "native" 1920x1080 the text is a bit small and poor quality. I have messed with config.txt to get 1280x720 (according to tvservice -s) which looks about right, but X is actually displaying at 1184x664 (according to Display Settings). I suspect it would look better at a genuine 1280x720 (correct aspect ratio), and would like to figure out how to make it do that.
disable_overscan=1

dukla2000
Posts: 190
Joined: Tue Jan 10, 2012 12:02 am
Location: Reading.UK.EU

Re: Similar problem

Sun Jul 01, 2012 6:34 pm

dgwsoft wrote:... I went out and bought the cheapest HDMI television I could lay my hands on
Hey - I think a couple of us cheapskates are competing for this award - mine is Technika from Tesco! One downside, certainly I am sure my Technika doesn't know its EDID from its elbow.
dgwsoft wrote:... but at its "native" 1920x1080 the text is a bit small and poor quality.
Yup, ditto, but after extensive playing what I found is my Technika gives a much better image using the 50Hz options rather than 60Hz - for a long time was using hdmi_mode=16 (1080p @ 60Hz) and saving for an opticians bill, since swapping to hdmi_mode=31 ([email protected]) am much happier.
dgwsoft wrote:I am used to working with xorg.config, but RPi (debian build) does not have one and (as others have noted) won't create one with Xorg -configure. Why?
It was deprecated several X revs ago.

So my 6p - try hdmi_mode19 (if you want to stick to 720p). If you really want to force your X window size add framebuffer_width and framebuffer_height lines to your config.txt

In the hope that dom passes by again I have included my parsed EDID data below - I figure it starts off wrong with a size of 70*39cm (actually measures around 20*11.25" =approx 50.8*28.6cm). Question, is there anything else to try get a clean image on this monitor?
Config.txt is

Code: Select all

hdmi_force_hotplug=1
hdmi_mode=31
# 
overscan_top=-22
overscan_bottom=-22
Parsed EDID is

Code: Select all

Parsing edid.dat...
HDMI:EDID version 1.3, 1 extensions, screen size 70x39 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 name descriptor tag 0xfc
HDMI:EDID monitor name is LCDTV___
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 22-80 Hz, horizontal is 14-91 kHz, max pixel clock is 160 MHz
HDMI:EDID monitor range does not support GTF
HDMI:EDID found preferred CEA detail timing format: 1280x720p @ 60 Hz (4)
HDMI:EDID found CEA detail timing format: 1920x1080i @ 60 Hz (5)
HDMI:EDID established timing I/II bytes are 21 08 00
HDMI:EDID found DMT format: code 4, 640x480p @ 60 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 16, 1024x768p @ 60 Hz in established timing I/II
HDMI:EDID standard timings block x 8: 0x8BC0 8140 81C0 6140 0101 0101 0101 0101 
HDMI:EDID unknown standard timing 1360x765 @ 60 Hz aspect ratio (16:9)
HDMI:EDID found DMT format: code 32, 1280x960p @ 60 Hz (4:3) in standard timing 1
HDMI:EDID found DMT format: code 85, 1280x720p @ 60 Hz (16:9) in standard timing 2
HDMI:EDID found DMT format: code 16, 1024x768p @ 60 Hz (4:3) in standard timing 3
HDMI:EDID parsing v3 CEA extension 0
HDMI:EDID monitor support - underscan IT formats:yes, basic audio:yes, yuv444:yes, yuv422:yes, #native DTD:2
HDMI:EDID found CEA detail timing format: 720x480p @ 60 Hz (2)
HDMI:EDID found CEA detail timing format: 1280x720p @ 50 Hz (19)
HDMI:EDID found CEA detail timing format: 1920x1080i @ 50 Hz (20)
HDMI:EDID found CEA detail timing format: 720x480p @ 60 Hz (2)
HDMI:EDID found CEA detail timing format: 720x576p @ 50 Hz (17)
HDMI:EDID found CEA format: code 1, 640x480p @ 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 4, 1280x720p @ 60Hz (native)
HDMI:EDID found CEA format: code 5, 1920x1080i @ 60Hz 
HDMI:EDID found CEA format: code 16, 1920x1080p @ 60Hz 
HDMI:EDID found CEA format: code 18, 720x576p @ 50Hz 
HDMI:EDID found CEA format: code 19, 1280x720p @ 50Hz (native)
HDMI:EDID found CEA format: code 20, 1920x1080i @ 50Hz 
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 5
HDMI:EDID HDMI VSDB has physical address 1.0.0.0
HDMI:EDID HDMI VSDB has no extension fields
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 5265888)
HDMI:EDID CEA mode (5) 1920x1080i @ 60 Hz with pixel clock 74 MHz has a score of 4848832
HDMI:EDID DMT mode (9) 800x600p @ 60 Hz with pixel clock 40 MHz has a score of 28800
HDMI:EDID CEA mode (16) 1920x1080p @ 60 Hz with pixel clock 148 MHz has a score of 348832
HDMI:EDID DMT mode (16) 1024x768p @ 60 Hz with pixel clock 65 MHz has a score of 147185
HDMI:EDID CEA mode (17) 720x576p @ 50 Hz with pixel clock 27 MHz has a score of 2141472
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 3738240
HDMI:EDID CEA mode (20) 1920x1080i @ 50 Hz with pixel clock 74 MHz has a score of 3307360
HDMI:EDID CEA mode (31) 1920x1080p @ 50 Hz with pixel clock 148 MHz has a score of 307360
HDMI:EDID DMT mode (32) 1280x960p @ 60 Hz with pixel clock 108 MHz has a score of 173728
HDMI:EDID DMT mode (85) 1280x720p @ 60 Hz with pixel clock 74 MHz has a score of 155296
HDMI:EDID preferred mode remained as CEA (4) 1280x720p @ 60 Hz with pixel clock 74 MHz
HDMI:EDID has HDMI support and audio support
edid_parser exited with code 0
ps - should add that with nothing in config.txt get borders at top/bottom of screen, not left/right. Adding disable_overscan=1 causes image to exceed screen in all dimensions needing large overscan_top/bottom/left/right settings to get things back and visible.

pps - something else weird about my Technika is with the HDMI cable connected to Pi and no other power connected to Pi, Pi' red power LED glows dimly and I have about 2.9V across TP1/2. Hasn't caused me any grief but slightly concerning.
Daily driver: Pi3B, 64GB Samsung Evo+ @100MHz, DVB-T, onboard WiFi for internet, BT/USB dongle for KB/mouse, 250GB HDD via USB for media, Raspbian Jessie Lite with Openbox desktop.
Museum: Pi B

dgwsoft
Posts: 3
Joined: Sun Jul 01, 2012 4:47 pm

Re: Resolution help... again.

Sun Jul 01, 2012 7:05 pm

Thanks for the response, dom, but that does not seem to be the problem.

I had tried that before, when when I just tried it again, it resulted in no display at all on boot. After fixing that (SD card in the PC) my /boot/config.txt is:

Code: Select all

# Set stdv mode to PAL (as used in Europe)
sdtv_mode=2

# Force the monitor to HDMI mode so that sound will be sent over HDMI cable
hdmi_drive=2

# Set monitor mode to DMT
# Set monitor resolution to 1024x768 XGA 60Hz (HDMI_DMT_XGA_60)
#hdmi_group=2
#hdmi_mode=16

# Set monitor mode to CEA
# Set monitor resolution to 1280x720 XGA 60Hz
hdmi_group=1
hdmi_mode=4
framebuffer_width=1280
framebuffer_height=720

# disable overscan
disable_overscan=0  # 1 results in no display

# Make display smaller to stop text spilling off the screen
overscan_left=0
overscan_right=0
overscan_top=-20
overscan_bottom=-20
As I said this displays OK but the X server is actually giving 1184x664.

I would be interested to know if it is a good idea to create an xorg.conf file or if not, why not.

Thanks again.

dgwsoft
Posts: 3
Joined: Sun Jul 01, 2012 4:47 pm

Aha!

Mon Jul 02, 2012 9:51 am

OK, what seems to be happening is that overscan mode reduces the number of pixels available for X. Setting the framebuffer size can't override that.

So dom is right, if you want the full number of pixels given in the display mode you must have disable_overscan=1. (But some modes on my TV don't work at all, which is a different issue)

I managed to get the display to fit on the screen, at either 1920x1080 or 1280x720 by using the TV remote control to set the screen mode to FULL. You can verify the actual number of pixels used by X with:

xdpyinfo | grep dimensions

and compare this with the tv display mode

/opt/vc/bin/tvservice -s

Moral: if the display does not fit on the screen play with the remote control before you play with overscan! (Maybe that's obvious but I missed it).

I have experimented with interlaced/progressive and 60Hz/50Hz but can't see any difference. The native 1920x1080 is still a bit small but 1280x720 works quite nicely.

As an aside, I have read the rationale for not supporting VGA, but that does seem to conflict with the idea that people can run an RPI using old bits of hardware they have lying around. I have half a dozen monitors around the house but they are all VGA. If I had a HDMI or DVI monitor I would be using it with my main desktop machine. The only HDMI devices in my house are the TV in the living room and another in my son's bedroom, neither of which I really take into the office to use for RPI hacking. Hence the need to go out and buy a new TV.

Summary: The ALBA 16911DVDP works well with:

hdmi_group=1
hdmi_mode=19
disable_overscan=1

Return to “Troubleshooting”