1366 x 768 resolution

crazyburns · ‎05-24-2007

I have 3 Windows Vista computers that I am connecting up to Sony Bravia KDL40S2000 LCD tvs using a VGA connection. The computers are Dells with and intel Q965/Q963 Express Chipset. I am trying to run the screens at there default resolution of 1366 x 768, but this is not an option. The only resolution close to this that works is 1280 x 768, however this leaves black bars on each side of the image. I have downloaded the latest driver but this didn't make a difference. I have tried finding a display driver for the monitor (it shows up as generic display) but have been unable to find an available one. I also attempted to use PowerStrip to set a custom resolution, but this did nothing (I've read somewhere that PowerStrip doesn't work with Intel).

I found an article where they discussed editing the [NonEDIDMode_AddSwSettings] in the driver inf file, however I did not understand what all of these diffenet settings mean. Is this the best way to make this work?

Any help would be greatly appreciated.

Aaron_B_Intel · ‎05-24-2007

Found this for your monitor on the MythTV Website:

Sony KDL-40S2000

I am able to get the picture exactly as it is with XP under Ubuntu with these settings.

HorizSync    30-66
VertRefresh  30-61
Modeline "1360x768"   85.500   1360 1432 1544 1792   768 771 777 795

That Modeline translates to DTD:

66,21,50,B0,51,00,1B,30,48,70,36,00,00,00,00,00,00,1C

Unfortunately, the Modeline I found didn't specify sync, so there are three alternates in case that one doesn't work:

66,21,50,B0,51,00,1B,30,48,70,36,00,00,00,00,00,00,1E

66,21,50,B0,51,00,1B,30,48,70,36,00,00,00,00,00,00,1A

66,21,50,B0,51,00,1B,30,48,70,36,00,00,00,00,00,00,18

Download the latest Intel drivers in .ZIP form and extract them to a directory. In that directory or a subdirectory, find (depending on your version)

Vista 32: igdlh.inf

Vista 64: igdlh64.inf

Open it. Search for

HKR,, TotalDTDCount, %REG_DWORD%, 0

Change it to

HKR,, TotalDTDCount, %REG_DWORD%, 4

Underneath that is

HKR,, DTD_1,%REG_BINARY%, 01,1D,80,18,71,1C,16,20,58,2C,1A,00,00,00,00,00,00,86,37,01;1920x1080@60...Interlaced HKR,, DTD_2,%REG_BINARY%, 01,1D,80,D0,72,1C,16,20,10,2C,1A,80,00,00,00,00,00,86,37,01;1920x1080@50...Interlaced HKR,, DTD_3,%REG_BINARY%, 01,1D,00,BC,52,D0,1E,20,B8,28,25,40,00,00,00,00,00,04,37,01;1280x720@50....Non-interlaced HKR,, DTD_4,%REG_BINARY%, 01,1D,00,72,51,D0,1E,20,6E,28,25,00,00,00,00,00,00,06,37,01;1280x720@60....Non-interlaced HKR,, DTD_5,%REG_BINARY%, 00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00 ;Fifth DTD

Change it to

HKR,, DTD_1,%REG_BINARY%, 66,21,50,B0,51,00,1B,30,48,70,36,00,00,00,00,00,00,1C,37,01;1920x1080@60...Interlaced HKR,, DTD_2,%REG_BINARY%, 66,21,50,B0,51,00,1B,30,48,70,36,00,00,00,00,00,00,1E,37,01;1920x1080@50...Interlaced HKR,, DTD_3,%REG_BINARY%, 66,21,50,B0,51,00,1B,30,48,70,36,00,00,00,00,00,00,1A,37,01;1280x720@50....Non-interlaced HKR,, DTD_4,%REG_BINARY%, 66,21,50,B0,51,00,1B,30,48,70,36,00,00,00,00,00,00,18,37,01;1280x720@60....Non-interlaced HKR,, DTD_5,%REG_BINARY%, 00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00 ;Fifth DTD

Save and close the file; run setup.exe in the directory you extracted to. 1360x768 modes should show up.

If that doesn't work, it probably means Dell is explicitly removing those modes in the BIOS. There is another possible workaround in that case, but try the aforementioned first.

crazyburns · ‎05-25-2007

That worked, however the text wasn't as crisp as when the monitor was set in 1280x 768. I ended up leaving the monitor at 1280 x 768 and stretching it using the tv's display settings. The stretch was barely visible.

Thanks for the information. It was very helpful.

Aaron_B_Intel · ‎05-25-2007

Weird that it looked worse at the supposed "native" rez of the monitor, but as long as you're happy...

cdickinson66 · ‎06-13-2007

Hey Archibael I tried this hack to the latest Intel drivers (may-31) for WinXP MCE and it just made my screen not work at all. Reinstalled latest driver from VGA mode to restore.

My problem is this. When I run MonInfo the LCD (Vizio 37") says the max resolution is 1920x540 .... But the tech support guys at Vizio said that the correct resolution is 1366x768 @ 60Hz

Of course neither of these resolutions show up in the Display settins for Intel Graphics.

Not sure who to believe. I am unsure as to what the correct DTD line values are can you help?

Thanks

-Charles

Aaron_B_Intel · ‎06-13-2007

Charles,

What were the MonInfo results, and what DTD did you use?

We can work through this.

cdickinson66 · ‎06-13-2007

I trid the above changes in this thread as but they did not work. Here is my Monitor Info for the Mac Mini running Windows XP MCE , DVI output into HDMI input of Vizio 37" LCD.

Any help would be great!!

-Charles

=====================================================

Monitor
Windows description......... Plug and Play Monitor
Manufacturer description.... VIZIO L37 HD
Manufacturer................ VIZ

Plug and Play ID............ VIZ1300
Serial number............... HLEABAG086975
EDID data source............ I2C bus (real-time)

Manufacture date............ 2006, ISO week 8
EDID revision............... 1.3
Display type and signal..... Digital
Sync input support.......... n/a
Screen size................. 820 x 460 mm (~39")
Power management............ n/a

Color characteristics
Display gamma............... 2.20
Red chromaticity............ Rx 0.640 - Ry 0.330
Green chromaticity.......... Gx 0.290 - Gy 0.600
Blue chromaticity........... Bx 0.150 - By 0.060
White point (default)....... Wx 0.280 - Wy 0.290

Timing characteristics
VESA GTF support............ Not supported
Horizontal scan range....... 31-70kHz
Vertical scan range......... 50-85Hz
Video bandwidth............. 110MHz
Extension blocks............ 1
Timing recommendation #1.... 1920x540 at 60Hz
Modeline................ "1920x540" 74.250 1920 2008 2052 2200 540 542 547 562 +hsync +vsync
Timing recommendation #2.... 1920x1080 at 30Hz
Modeline................ "1920x1080" 74.250 1920 2008 2052 2200 1080 1084 1094 1124 interlace +hsync +vsync
Timing recommendation #3.... 1920x540 at 60Hz
Modeline................ "1920x540" 74.250 1920 2008 2052 2200 540 542 547 562 +hsync +vsync
Timing recommendation #4.... 1920x1080 at 30Hz
Modeline................ "1920x1080" 74.250 1920 2008 2052 2200 1080 1084 1094 1124 interlace +hsync +vsync
Timing recommendation #5.... 640x480 at 60Hz
Modeline................ "640x480" 25.180 640 656 752 800 480 490 492 525 -hsync -vsync
Timing recommendation #6.... 1280x720 at 60Hz
Modeline................ "1280x720" 74.250 1280 1390 1430 1650 720 725 730 750 +hsync +vsync
Timing recommendation #7.... 720x480 at 60Hz
Modeline................ "720x480" 27.000 720 736 798 858 480 489 495 525 -hsync -vsync
Timing recommendation #8.... 720x576 at 50Hz
Modeline................ "720x576" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync

Standard timings supported
640 x 480 at 60Hz - IBM VGA
640 x 480 at 60Hz - VIZ
720 x 480 at 60Hz - VIZ
720 x 576 at 50Hz - VIZ
1280 x 720 at 60Hz - VIZ
1920 x 540 at 60Hz - VIZ
1920 x 1080 at 30Hz - VIZ

Raw EDID base
00: 00 FF FF FF FF FF FF 00 59 3A 00 13 01 01 01 01
10: 08 10 01 03 80 52 2E 78 0A E6 9D A3 54 4A 99 26
20: 0F 47 4A 20 00 00 01 01 01 01 01 01 01 01 01 01
30: 01 01 01 01 01 C1 00 00 00 FD 00 32 55 1F 46 0B
40: 02 00 00 00 00 00 00 00 01 1D 80 18 71 1C 16 20
50: 58 2C 25 00 34 CC 31 00 00 9E 00 00 00 FF 00 48
60: 4C 45 41 42 41 47 30 38 36 39 37 35 00 00 00 FC
70: 00 56 49 5A 49 4F 20 4C 33 37 20 48 44 0A 01 84

Raw EDID extension (CEA-861)
00: 02 03 18 75 45 85 81 84 83 92 23 09 07 03 83 01
10: 00 00 65 03 0C 00 10 00 01 1D 80 18 71 1C 16 20
20: 58 2C 25 00 34 CC 31 00 00 9E D6 09 80 A0 20 E0
30: 2D 10 10 60 A2 00 34 CC 31 00 00 18 01 1D 00 72
40: 51 D0 1E 20 6E 28 55 00 34 CC 31 00 00 1E 8C 0A
50: D0 8A 20 E0 2D 10 10 3E 96 00 34 CC 31 00 00 18
60: 8C 0A D0 90 20 40 31 20 0C 40 55 00 34 CC 31 00
70: 00 18 00 00 00 00 00 00 00 00 00 00 00 00 00 B0

EIA/CEA-861 Information
Revision number............. 3
DTV underscan............... Not supported
Basic audio................. Supported
YCbCr 4:4:4................. Supported
YCbCr 4:2:2................. Supported
Native formats supported.... 5
DTV formats supported....... 5

CE standard timings supported
1920 x 1080i at 59.94/60Hz (16:9) - HDTV (Native)
640 x 480p at 59.94/60Hz (4:3) - Default (Native)
1280 x 720p at 59.94/60Hz (16:9) - HDTV (Native)
720 x 480p at 59.94/60Hz (16:9) - EDTV (Native)
720 x 576p at 50Hz (16:9) - EDTV (Native)

Display adapter
Adapter description......... Mobile Intel 945 Express Chipset Family
Adapter device ID........... 0x27A28086
Display settings............ 1920x1080, 32bpp

User/computer information
Registered user name........ MiniXP
Registered organization..... n/a
Network user name........... charles
Network computer name....... MINIXP-FCA97E9D
Windows version ............ Windows XP
Windows build .............. 5.01.2600 Service Pack 2
Installation date .......... 2/18/2007 12:00:00 PM

Aaron_B_Intel · ‎06-13-2007

Ah, using the HDMI input... it's usually problematic with today's technology to get native rez over HDMI. The dirty little truth of the matter is, the HDMI inputs on most HDTVs (there are a few exceptions) only accept the so-called "CE resolutions" (CE = consumer electronics), aka 1920x1080, 1280x720, 720x480, etc. This is due to a limitation of the HDMI reciever chips the TV manufacturers are buying, and thus regardless of what native rez you have, you will only ever get joy from driving a CE resolution-- even if native rez works just fine over VGA or DVI (different, more flexible circuitry). There are some limitations to Intel's drivers (god knows that's why the whole "Programmable Resolutions..." thread exists in the first place), but in this case Nvidia or ATI drivers are going to give you the same result. In fact, if you hook up using the VGA port, you might get an entirely different EDID result, including 1366x768!

Your best bet is in using the resolutions provided (either 1080i or 720p), with DTDs:

01 1D 80 18 71 1C 16 20 58 2C 25 00 34 CC 31 00 00 9E ; 1080i
01 1D 00 72 51 D0 1E 20 6E 28 55 00 34 CC 31 00 00 1E ; 720p

because that's what the scaling chips in your monitor are built to accept and turn into 1366x768.

It's possible your monitor is the exception, but my research (http://www.avsforum.com/avs-vb/printthread.php?t=607501&page=6&pp=30) implies that your monitor is problematic and may not even have a valid EDID over VGA. I recommend 720p

cdickinson66 · ‎06-13-2007

I am currently using 1920x1080 from the downloaded driver and that does work however is cut off a bit enough that I cannot see the WIndows bar at the bottom of the screen and I lose a bit all the way around.

I tried the Intel 1280x720 but that doesn't work.

Do I need a special DTD for the 720p or a proper fitting 1080i?? I don't understand Should I copy these 2 lines into my INF file and set Number of DTDs to 2?? I'm lost.

Also Am I really getting a better quaility of picture with the HDMI then if I were to just use VGA?

-Charles

cdickinson66 · ‎06-14-2007

Well I decided to hookup with the VGA and See . You were right the proper resolution is detected with the VGA port youcan see from this report from MonitorInfo how it has completely different results:

Monitor
Windows description......... Plug and Play Monitor
Manufacturer description.... VIZIO L37 HD
Manufacturer................ VIZ

Plug and Play ID............ VIZ1300
Serial number............... HLEABAG086975
EDID data source............ I2C bus (real-time)

Manufacture date............ 2006, ISO week 8
EDID revision............... 1.3
Display type and signal..... Analog 0.714,0.286 (1.0V p-p)
Sync input support.......... Separate, Composite, Sync on green
Screen size................. 820 x 460 mm (~39")
Power management............ Standby, Suspend, Active off/sleep

Color characteristics
Display gamma............... 2.20
Red chromaticity............ Rx 0.640 - Ry 0.330
Green chromaticity.......... Gx 0.290 - Gy 0.600
Blue chromaticity........... Bx 0.150 - By 0.060
White point (default)....... Wx 0.280 - Wy 0.290

Timing characteristics
VESA GTF support............ Not supported
Horizontal scan range....... 31-70kHz
Vertical scan range......... 50-85Hz
Video bandwidth............. 110MHz
Extension blocks............ n/a
Timing recommendation #1.... 1366x768 at 60Hz
Modeline................ "1366x768" 85.500 1366 1494 1624 1798 768 770 776 795 +hsync -vsync

Standard timings supported
640 x 480 at 72Hz - VESA
640 x 480 at 75Hz - VESA
800 x 600 at 56Hz - VESA
800 x 600 at 60Hz - VESA
800 x 600 at 72Hz - VESA
800 x 600 at 75Hz - VESA
1024 x 768 at 60Hz - VESA
1024 x 768 at 75Hz - VESA
1366 x 768 at 60Hz - VIZ

Raw EDID base
00: 00 FF FF FF FF FF FF 00 59 3A 00 13 01 01 01 01
10: 08 10 01 03 3F 52 2E 78 EA E6 9D A3 54 4A 99 26
20: 0F 47 4A 0F CA 00 01 01 01 01 01 01 01 01 01 01
30: 01 01 01 01 01 01 00 00 00 FD 00 32 55 1F 46 0B
40: 01 00 BC 90 21 00 00 1A 66 21 56 B0 51 00 1B 30
50: 80 82 26 00 34 CC 31 00 00 1A 00 00 00 FF 00 48
60: 4C 45 41 42 41 47 30 38 36 39 37 35 00 00 00 FC
70: 00 56 49 5A 49 4F 20 4C 33 37 20 48 44 0A 00 BC

Display adapter
Adapter description......... Mobile Intel 945 Express Chipset Family
Adapter device ID........... 0x27A28086
Display settings............ 1366x768, 32bpp

User/computer information
Registered user name........ MiniXP
Registered organization..... n/a
Network user name........... charles
Network computer name....... MINIXP-FCA97E9D
Windows version ............ Windows XP
Windows build .............. 5.01.2600 Service Pack 2
Installation date .......... 2/18/2007 12:00:00 PM

Is there no way to get this on the HDMI por t? And why doesn't 1280x720 work in HDMI ... this monitor is strange. The 1920x1080 works with just a little cropping on the HDMI but on the VGA it crops off almost half the screen in the same setting.

-Charles

Aaron_B_Intel · ‎06-14-2007

I would use the two DTDs I provided (comma delimited, with ,37,01 tagged onto the end) to replace the ones in the .INF file, and yes, you should change the Number of DTDs to as many as you've replaced in the .INF. Basically, follow the directions from Wiki, using the DTDs I just gave you.

HDMI can give you a better picture if your VGA cable is noisy or lossy, which it will be to some (possibly insignificant) extent. HDMI is most useful to merge sound and graphics into one cable and to allow you to display AACS-protected material, but it is not required for anything besides that.

For the overscan you're seeing, I recommend messing with the parameter in the .INF file called something like "HDMI Overscan Percentage". Currently it's set to zero, but you might want to tweak it up and down to see if it helps.

Aaron_B_Intel · ‎06-14-2007

cdickinson66:

Timing recommendation #1.... 1366x768 at 60Hz
Modeline................ "1366x768" 85.500 1366 1494 1624 1798 768 770 776 795 +hsync -vsync

Raw EDID base
00: 00 FF FF FF FF FF FF 00 59 3A 00 13 01 01 01 01
10: 08 10 01 03 3F 52 2E 78 EA E6 9D A3 54 4A 99 26
20: 0F 47 4A 0F CA 00 01 01 01 01 01 01 01 01 01 01
30: 01 01 01 01 01 01 00 00 00 FD 00 32 55 1F 46 0B
40: 01 00 BC 90 21 00 00 1A 66 21 56 B0 51 00 1B 30
50: 80 82 26 00 34 CC 31 00 00 1A 00 00 00 FF 00 48
60: 4C 45 41 42 41 47 30 38 36 39 37 35 00 00 00 FC
70: 00 56 49 5A 49 4F 20 4C 33 37 20 48 44 0A 00 BC

Is there no way to get this on the HDMI port? And why doesn't 1280x720 work in HDMI ... this monitor is strange. The 1920x1080 works with just a little cropping on the HDMI but on the VGA it crops off almost half the screen in the same setting.

-Charles

You could try using the 1366x768 DTD you got from VGA

66 21 56 B0 51 00 1B 3080 82 26 00 34 CC 31 0000 1A

in the .INF file; it may show up then for HDMI, but even if it does there's no guarantee the monitor will accept it.

Like I said, the circuitry is completely different on the VGA inputs than it is on the HDMI, which is why they're behaving differently for you.

cdickinson66 · ‎06-14-2007

I will try all three with the following command added to the INF file

HKR,, TotalDTDCount, %REG_DWORD%, 3

HKR,, DTD_1,%REG_BINARY%,
01,1D,80,18,71,1C,16,20,58,2C,25,00,34,CC,31,00,00,9E,37,01 ; 1080i
HKR,, DTD_2,%REG_BINARY%,
01,1D,00,72,51,D0,1E,20,6E,28,55,00,34,CC,31,00,00,1E,37,01 ; 720p
HKR,, DTD_3,%REG_BINARY%,
66,21,56,B0,51,00,1B,30,80,82,26,00,34,CC,31,00,00,1A,37,01 ; 1366x768 at 60Hz

Does that look right to you?Well No harm in trying it ... I'll let you know. Thanks!

-Charles

Aaron_B_Intel · ‎06-14-2007

Looks right to me. Hope you get some decent results with either HDMI or VGA.

cdickinson66 · ‎06-15-2007

OK I tried the new 3 lines and yes the 1366x768 will now appear in the drop down menu for the Intel Display however is doesn't work. Too funny it looks as f you were correct about the HDMI since when pluggin into the VGA 1366x768 is detected on startup and configured perfectly.

On the HDMI It will do 1920x1080 still but there is cropping all the way around. I didn't see anything on Overscan but there was a variable called HDMIUnderScan so I changed that from 0 to 7.5 just to see what it did. And nothing happened. Weird that the EDID is different for one port to the other. Not sure that the HDMI port really pays attention to the driver... or at least the underscan variable. Does it matter that I am coming out the DVI to HDMI of the screen??

-Charles

Aaron_B_Intel · ‎06-15-2007

If you're coming out the DVI port and using a DVI-to-HDMI cable I'm not sure the AddUnderscanPercentageHDMI will work, since the card thinks you're on DVI. Even if it does work, using a decimal value like 7.5 would be bad since it should be in hexadecimal. It's automatically defaulting to 7.5% underscan with the setting at 0; try tweaking it upward to see if you get results.

Can you run MonInfo when hooked up to HDMI? Even if the underscan percentage variable doesn't work for you, you could create your own timings with PowerStrip or manually (I'd help) which would shrink the number of pixels being sent to something like 1900x1000, thus fitting onscreen better.

cdickinson66 · ‎06-15-2007

Yes the Montior info in HDMI (DVI) is the first one I sent above here, it read the Screen and suggested the 1080i or 720p. Which is what we based the Modlines on I thought. That's why I thought that one of the 3 DTD would work. 2 were based on the MonInfo with HDMI and the 1366x768 was based on the MonInfo with the VGA.

Powerstrip seems to load up showing custom resolutions available now (before the recent update it was greyed out) but It doesn't seem to write to the graphics chip properly just yet.

How would I change my pixel count to fit the screen? Just reduce the number of pixels? Would that really work? ...

-Charles

Aaron_B_Intel · ‎06-15-2007

Yep.

First of all, understand that we would be doing what Powerstrip refers to as a "resolution within a resolution": we'd be sending what the TV thinks is a 1920x1080 picture, but we would only be lighting up some smaller number.

Take the DTD you're working on. The critical numbers are:

01,1D,80,18,71,1C,16,20,58,2C,25,00,34,CC,31,00,00,9E

80, 18, 71 --> 780, 118 in hex = 1920, 280 in decimal. This is the horizontal resolution (number of active pixels) and the blanking interval (rest of the pixels-- black). You want their total to remain the same, so if you drop the number of active pixels from 1920 to 1900, you need to raise the blanking interval from 280 to 300. Convert back to hex:

1900 -> 76C, 300 -> 12C

Put the bytes in the proper order:

6C,2C,71

And you've nowshrunk thehorizontal resolution by 20. It should work similar with the bluevalues in thevertical direction: again, make sureif youlower the active pixelsby one, you need to increase the blanking interval by the same amount. In the above DTD example, if you want to drop the number of vertical lines by 8, you'd subtract

1C - 8 = 14

and add

16 + 8 = 1E

So the vertical numbers would be

14,1E,20

It's possible-- even probable-- that now your image is off-center. At that point, you start messing with the green values, but let's not go there yet.

This would be easier with Powerstrip, but since you can't seem to get it working, try horizontal first, then add vertical in.

cdickinson66 · ‎06-15-2007

Ok I understand now! but the byte order is kinda crazy with the string. One question if this is supposed to be 1920x1080 why does the line read as 1920x540 after translated from Hex?

-Charles

Aaron_B_Intel · ‎06-15-2007

Good question. The resolution, 1080i, is an interlaced one (last byte begins with a "9"), which means that though there are 1080 lines total, only 540 are written in one pass; the next pass writes the other 540 in between ("interlaced with") the last set. Your eyes are slow and therefore don't notice. With a progressive resolution (720p), all 720 lines are written at once, then the next frame of 720 lines is written.

cdickinson66 · ‎06-15-2007

Ahh! of course 540 doubled up to be interlaced. 1080i not p.

Well I did the change and it didn't do anything? Heh? that doesn't make sense.... So it would seem that DTD is not getting read. Is there another declariation of the 1080 setting in the file somewhere I wonder....
Or maybe it ignores this one for some reason... but then when I added a 1366 one it did add that to the menu. So that would indicate I am changing the correct spot right?

weird

-Charles