First of all, I'd like to express my sincere gratitude for your post on how to correct overscan, for the first time in literally few months since I got my slick little PC, I can sit back and enjoy a real movie played from the htpc, full screen and using the correct resolution! Thank you so much for taking the time to share your knowledge and give back to the community, thank you, thank you, thank you...
I have started in Vista a few months back, had never ending resolution issues with the Intel drivers available back then, and the best I could do is settling for a very odd resolution with everything showing inside a nice black frame on my TV. I obviously grew irritated by this very quickly (not to mention the risks of burn-in on my Plasma TV), add to that various Vista bugs, misbehaviors and sheer Windows annoyances in Media Center, I decided to ditch Windows altogether and jump into a Linux distro with integrated MythTV, I picked MythDora 4.0 which I installed and started working on... The idea for going Linux was that I'd be more likely to find ways to customize resolution, but also to check out what the MythTV hype is all about...
While the graphics are mouth drooling and the overall look and feel was absolutely fantastic, not to mention the kickass functionality & features, I soon hit a brick wall yet again with resolution issues (but of course many others which are typical noob headbanging issues such as LIRC, etc). To start with, my graphic card was not recognized and simply came up as generic which limits what I could do. After spending a LOT of time googling away and chewing on many forums and newsgroups, I figured that to even hope getting somewhere I had to recompile the kernel, recompile X server and only then be able to install and compile the needed Intel 2.2.0 driver which fixes some issues specific to my H/W. Nevertheless, I embarked into this and after hours and hours, days and days of headscratching and battling to set myself free in the Fedora dependency hell
, I had to admit to myself that I have gone to a place which is a out of my league and way beyond my modest and rusty Linux knowledge, though it was both a refreshing and very frustrating experience, I had to... alas... go back to Windows.
My H/W is as follows:
AOpen MiniPC MP965-DR (same as Ryan1!)
Intel T7500 CPU
Graphics GM965 (GMA 3100X)
GMA driver: 184.108.40.2064
My TV is a Pioneer PDP-507XG [www (dot) pioneer (dot) com (dot) sg/storefront/brochure/7GPDP.pdf] The input signals supported through the 2 HDMI ports (3 & 4) which are HDMI 1.1 and HDCP 1.1 compliant are:
50Hz 720p / 1080i / 576p / 576i
60Hz 720p / 1080i / 480p / 480i
The screen resolutions supported are:
1280 x 720
1366 x 768
1920 x 1080
This spits out the following EDID:
0x 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 | 00 FF FF FF FF FF FF 00 41 2F A6 00 01 01 01 01
10 | 00 10 01 03 80 60 36 78 2A D7 B3 AE 51 50 94 23
20 | 0C 4A 47 00 00 00 01 01 01 01 01 01 01 01 01 01
30 | 01 01 01 01 01 01 01 1D 80 D0 72 1C 16 20 10 2C
40 | 25 80 B8 18 32 00 00 9E 01 1D 80 18 71 1C 16 20
50 | 58 2C 25 00 B8 18 32 00 00 9E 00 00 00 FD 00 17
60 | 3D 0F 2E 08 00 0A 20 20 20 20 20 20 00 00 00 FC
70 | 00 50 44 50 2D 78 78 37 47 0A 20 20 20 20 01 08
It is rather unclear from the documentation what the "native reolution" is for this TV, however, basing on its EDID and following the steps detailed in your wiki and DTD Calculator howto, I started off with DTD 01 1D 80 D0 72 1C 16 20 10 2C 25 80 B8 18 32 00 00 9E and end up with a setting (after fine tuning the overscan) of 1824 x 1026 (25Hz).
I just have two questions I hope you can advise on:
1) Based on the EDID above and the datasheet on the URL I provided, what would you say is the native rez I should be shooting for? At the moment, I really have movies playing FULL SCREEN (i.e. no side bars and no top/bottom bars!), which this looks great for HD video playback, it does look a little odd for SD video, not sure what it is (stretching? cropping? dunno...)
2) In your Wiki, you mention the following:"Typically, the DTD is in the first Descriptor Block, but it can be in any of the four. You can tell if the data is a DTD or not because the first two bytes will be nonzero. In some cases, there may be more than one DTD listed because the monitor manufacturer has chosen to provide detailed timings for other modes-- possibly because they have an in-line scaler which works best with specific input timings. Consider all of these for your use, but the most important one for our purposes is the one which matches the native resolution of your display. In most cases (as in the example given), that will be the only one provided. If there are more than one, the best way to decide which to use, if you know what your monitor's native resolution is supposed to be, is to do a brief decode of the DTD parameters"
I'm little confused with this statement: If the EDID contains multiple DTDs, how to find the others? i.e. Ok, I can pick up the first one starting byte 54 and worth 18 bytes, but where are the others?
Many thanks again Archibael for your help.
A final word of kudos for WoOzy and the Clever Tech team for pulling our tormented souls out of trouble, respect!
And BTW, sorry for the long post and thanks for reading this far!