Software Archive
Read-only legacy content
17061 Discussions

Sony XBR on Intel 82945G custom resolutions

hackiewakie
Beginner
1,715 Views

Arch,
Could you help me translate a few modelines to DTD soI can enter them into my igxp32.inf
I've been pulling my hair out trying to get some custom resolutions to display.
Monitor:Sony KDF-70XBR950 using DVI on a Dell gx620 running xppro w/intergrated intel 82945G graphics.Running Latest Intel drivers 14.29.0.4820 dated april 19th 2007.

I've spend days messing with powerstrip. It just blanks out if I try any custom resolutions.

I know my monitor is capable of displaying 1776x1000 because I had it running using an NVIDIA card. But now I've "upgraded" to a much smaller HTPC and I've had no luck whatsoever with this intel GMA950 default resolutions. The closest i've got to work was 1600x900 but it hasabout 5 inches of underscan and is hard to read.

I would like to try the default sony timings, and perhaps a few custom ones like 1770x1000 or 1776x1000. 1766x 993

Can you translate a few of these for me. Trust me, I've read your tutoral but I must be brain dead when it comes the the hex translation and where to look on the EDID table

Here's my Moninfo..............................................................................

Monitor
Manufacturer description.... SONY TV
Manufacturer................ Sony
----------------------------
Plug and Play ID............ SNY00F8
Serial number............... n/a
EDID data source............ Registry (stored)
----------------------------
Manufacture date............ 2002
EDID revision............... 1.3
Display type and signal..... Digital
Sync input support.......... n/a
Screen size................. n/a
Power management............ n/a

Color characteristics
Display gamma............... 2.20
Red chromaticity............ Rx 0.625 - Ry 0.340
Green chromaticity.......... Gx 0.280 - Gy 0.595
Blue chromaticity........... Bx 0.155 - By 0.070
White point (default)....... Wx 0.283 - Wy 0.298

Timing characteristics
VESA GTF support............ Not supported
Horizontal scan range....... 15-46kHz
Vertical scan range......... 59-61Hz
Video bandwidth............. 80MHz
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.... 720x480 at 60Hz
Modeline................ "720x480" 27.000 720 736 798 858 480 489 495 525 -hsync -vsync

Standard timings supported
640 x 480 at 60Hz - IBM VGA
720 x 480 at 60Hz - Sony
1920 x 540 at 60Hz - Sony
1920 x 1080 at 30Hz - Sony

Raw EDID base
00: 00 FF FF FF FF FF FF 00 4D D9 F8 00 01 01 01 01
10: 00 0C 01 03 80 00 00 78 0A 0D C9 A0 57 47 98 27
20: 12 48 4C 20 00 00 01 01 01 01 01 01 01 01 01 01
30: 01 01 01 01 01 01 01 1D 80 18 71 1C 16 20 58 2C
40: 25 00 00 00 00 00 00 9E 8C 0A D0 8A 20 E0 2D 10
50: 10 3E 96 00 00 00 00 00 00 18 00 00 00 FC 00 53
60: 4F 4E 59 20 54 56 0A 20 20 20 20 20 00 00 00 FD
70: 00 3B 3D 0F 2E 08 00 0A 20 20 20 20 20 20 01 02

Raw EDID extension (reserved)
00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Display adapter
Adapter description......... Intel 82945G Express Chipset Family
Adapter device ID........... 0x27728086
Display settings............ 1600x900, 32bpp

User/computer information
Registered user name........ HTPC
Registered organization..... n/a
Network user name........... Administrator
Network computer name....... HTPC
Windows version ............ Windows XP
Windows build .............. 5.01.2600 Service Pack 2
Installation date .......... 6/29/2007 12:00:00 PM

Here's what viewsonic's softwarecalls up...............................................

Time: 22:55:16
Date: Tue Jul 03, 2007
______________________________________________________________________
______________________________________________________________________
VIEWSONIC CORPORATION
EDID Version # 1, Revision # 3
DDCTest For: SNY SONY TV
______________________________________________________________________
______________________________________________________________________
128 BYTES OF EDID CODE:
0 1 2 3 4 5 6 7 8& nbsp; 9
________________________________________
0 | 00 FF FF FF FF FF FF 00 4D D9
10 | F8 00 01 01 01 01 00 0C 01 03
20 | 80 00 00 78 0A 0D C9 A0 57 47
30 | 98 27 12 48 4C 20 00 00 01 01
40 | 01 01 01 01 01 01 01 01 01 01
50 | 01 01 01 01 01 1D 80 18 71 1C
60 | 16 20 58 2C 25 00 00 00 00 00
70 | 00 9E 8C 0A D0 8A 20 E0 2D 10
80 | 10 3E 96 00 00 00 00 00 00 18
90 | 00 00 00 FC 00 53 4F 4E 59 20
100 | 54 56 0A 20 20 20 20 20 00 00
110 | 00 FD 00 3B 3D 0F 2E 08 00 0A
120 | 20 20 20 20 20 20 01 02
______________________________________________________________________
(08-09) ID Manufacturer Name ________________ = SNY
(11-10) Product ID Code _____________________ = 00F8()
(12-15) Last 5 Digits of Serial Number ______ = Not Used
(16) Week of Manufacture _________________ = 00
(17) Year of Manufacture _________________ = 2002
(10-17) Complete Serial Number ______________ = See Descriptor Block
(18) EDID Version Number _________________ = 1
(19) EDID Revision Number ________________ = 3
(20) VIDEO INPUT DEFINITION:
Digital Signal
Non - VESA DFP 1.x Compatible

(21) Maximum Horizontal Image Size ________________ = mm
(22) Maximum Vertical Image Size __________________ = mm
(23) Display Gamma ________________________________ = 2.20
(24) Power Management and Supported Feature(s):
Preferred Timing Mode
Display Type = R/G/B Color
(25-34) CHROMA INFO:
Red X - 0.625 Green X - 0.280 Blue X - 0.155 White X - 0.283
Red Y - 0.340 Green Y - 0.595 Blue Y - 0.070 White Y - 0.298
(35) ESTABLISHED TIMING I:
640 X 480 @ 60Hz (IBM,VGA)
(36) ESTABLISHED TIMING II:
(37) Manufacturer's Reserved Timing:
None Specified
(38-53) Standard Timing Identification:
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
______________________________________________________________________
(54-71) Detailed Timing / Descriptor Block 1:
1920x540 Pixel Clock: 74.25 MHz
______________________________________________________________________
Horizontal Image Size: 0 mm Vertical Image Size: 0 mm
Refreshed Mode: Interlaced Normal Display - No Stereo

Horizontal:
Active Time: 1920 pixels Blanking Time: 280 pixels
Sync Offset: 88 pixels Sync Pulse Width: 44 pixels
Border: 0 pixels Frequency: 33.75 KHz

Vertical:
Active Time: 540 lines Blanking Time: 22 lines
Sync Offset: 2 lines Sync Pulse Width: 5 lines
Border: 0 lines Frequency: 60.05 Hz

Digital Separate, Horizontal Polarity (+) Vertical Polarity (+)


______________________________________________________________________
(72-89) Detailed Timing / Descriptor Block 2:
720x480 Pixel Clock: 27.00 MHz
______________________________________________________________________
Horizontal Image Size: 0 mm Vertical Image Size: 0 mm
Refreshed Mode: Non-Interlaced Normal Display - No Stereo

Horizontal:
Active Time: 720 pixels Blanking Time: 138 pixels
&n bsp; Sync Offset: 16 pixels Sync Pulse Width: 62 pixels
Border: 0 pixels Frequency: 31.47 KHz

Vertical:
Active Time: 480 lines Blanking Time: 45 lines
Sync Offset: 9 lines Sync Pulse Width: 6 lines
Border: 0 lines Frequency: 59.94 Hz

Digital Separate, Horizontal Polarity (-) Vertical Polarity (-)


______________________________________________________________________
(90-107) Detailed Timing / Descriptor Block 3:

Monitor Name:
SONY TV


______________________________________________________________________
(108-125) Detailed Timing / Descriptor Block 4:

Monitor Range Limits:
Min Vertical Freq - 59 Hz
Max Vertical Freq - 61 Hz
Min Horiz. Freq - 15 KHz
Max Horiz. Freq - 46 KHz
Pixel Clock - 80 MHz
Secondary GTF - Not Supported

(126) (01) Extension EDID Block(s)
(127) CheckSum OK

Thanks

-Hakie

0 Kudos
14 Replies
Aaron_B_Intel
Employee
1,715 Views

Hakie,

I love the ViewSonic EDID tool; it's how I originally puzzled out how to modify DTDs.

01 1D 80 18 71 1C 16 20 58 2C25 00 00 00 00 00 00 9E

1080i is the only useful one listed, although you can go with 540p instead.

PowerStrip doesn't play well with Intel on the interlaced resolutions, but you might still be able to get it to do what you want. Try this:

I would assume that the Intel graphics driver allows 1080i to be selected. Choose that, then start PowerStrip. In PowerStrip, choose Display Profiles, Configure, Advanced Timing Options. In the lower right hand corner, there's a triangle-and-ruler icon for Design A Resolution Within A Resolution. Stretch it to fit your display to eliminate the overscan, then click OK. Click the "Copy to Clipboard" icon, and paste the results here. You should get a Modeline with a resolution within 1080i, and I can help you convert it to something the Intel drivers will enjoy.

0 Kudos
hackiewakie
Beginner
1,715 Views

Archi,

When I use powerstip and adjust the up/down buttons or "center" buttons in "advanced timings", my monitor blanks out, and looses sync.

(However I have not triedperformingthese adjustmentswhen my default resolution was set to 1080i) I will try this tonight. I will also look for the triangle and ruler you're refering to, (I don't remember seeing that)

Do you want me to enter this data into my igxp.inf file prior to the experimet with powerstrip? "01 1D 80 18 71 1C 16 20 58 2C25 00 00 00 00 00 00 9E"

What about this idea.....Since I alreadyown an "old" PC that drivesthe sonymonitor perfectly at 1776x1000, is there any datawe can extractthat will help us generate a DTD for the intel graphics?

Also I've been reading...Some people have had luck with the following settings. Does this help us shead light? Can we convert their infoto DTD and experiment?

Copy/paste from other forum.....

snip

"These are the timings I have got to work on my 60XBR:"

{Note: mine's a 70xbr, But what's 10 inches among friends....)

PowerStrip timing parameters:
1280x720p=1280,72,40,256,720,18,5,30,74160,7
1280x768p=1280,80,136,240,768,1,2,6,79740,7
1304x734p=1304,64,40,240,734,11,5,23,74160,7
1320x734p=1320,64,136,200,734,1,3,22,79081,7
1336x734p=1336,64,144,200,734,1,3,23,79753,7
1344x734p=1344,56,128,192,734,1,3,22,79081,7
1376x744p=1376,176,24,168,744,0,1,18,79760,5

more copy/paste from another post

Snip

1766x993 works. I have a Media PC with NVIDIA 6800GT, and a Sony KDF-70XBR950. Out of the box, this setup works great with the Sony. It "recognizes" the Sony. The NVIDIA interface of the monitor setup corrects for overscan automatically, and allows you to choose a 480p, 720p, or 1080i resolution for your HDTV monitor over DVI.

For example, I choose 1080i with overscan correction. Then a resolution appeared in the monitor control panel for 1766 by 993 (very odd, but that's what the NVIDIA card must have "known" to choose). Bingo. Perfect picture, perfect size.

Anyway, I have not had to waste one second with Powerstrip. For most applications I am liking the 720p resolution, text is a little brighter. I can gaurantee I do not have 1:1 pixel mapping, which I thought I "must" have; the picture looks too darn good for me to care.
Snip

That's pretty much what happened to me, the NVIDIA worked great out of the box.

More.....

Snip

http://www.avsforum.com/avs-vb/showthread.php?threadid=206854

Here is the snip of the resolution:
--------------------------------------------------------------------
PowerStrip timing parameters:
1776x1000i HDTV adapter=1776,136,48,240,1000,42,5,78,74250,280

Generic timing details for 1776x1000:
HFP=136 HSW=48 HBP=240 kHz=34 VFP=42 VSW=5 VBP=78 Hz=30
interlace +hsync +vsync

Snip

0 Kudos
Aaron_B_Intel
Employee
1,715 Views

Yeah, I had the same result with "center" and the up/down left/right stuff on PowerStrip, but the triangle/ruler worked great (I still have the 1000x420 pixel resolution on my home PC from my experiments :) ).

I can work with what you've provided. Lots of options here, but I'll choose the final one at 1776x1000i(would love to see a Modeline for the 1766x933, that seems pretty interesting).

01 1D F0A8 61 F43E 10 88 30 A5 08 00 00 00 00 00 9E

Try that one and let me know how it works out.

0 Kudos
hackiewakie
Beginner
1,715 Views

Arch, your great!

01 1D F0A8 61 F43E 10 88 30 A5 08 00 00 00 00 00 9E

This is so close, itsrunning at 1776x1000i

The width is perfect but the screen is shifted up a whole inch and a half (on a 70 inch screen)

In other words theres black under the task bar.

I could fit one and a half task bars in the black area under the task bar. (best guess 32 pixels in height)

The top of the screen goes past the viewable area. in otherwords you cannot see the "file, edit, view" pull downs.

the aspect looks perfect.... we just need to shift the image down.

any ideas?

thanks so much

-Hackie

0 Kudos
Aaron_B_Intel
Employee
1,715 Views

Great news, Hackie. The up/down is controlled by the red values:

01 1D F0A8 61 F43E 10 88 30 A5 08 00 00 00 00 00 9E

in inverse byte order. We actually only use the top two bits of the "8" ( 8 = 1000b), so the number is actually 10b = 2, and thus the value is 2Ah, or 42. This is the number of pixels between the last line on the screen and the sync pulse (basically, the electrical signal that tells the pixels to start again at the top.

Keep in mind that since this is interlaced, the 42 is actually doubled to 84 (if you do the math, you'll see that this is actually 1776x500, and the 9E at the end tells the driver to double the 500 and interlace). Anyway, what that means is if you want the screen to shiftdownward, you need to decrease the distance between the last line and the sync pulse, i.e. make the 42 smaller. If you think it's 32 pixels,drop the 42 by 16 (doubled is 32), getting 26 =1A. The A is unchanged, but the 1 becomes the top two bits of the second digit of byte 12, so 0100b = 4.

I know for those who are unaccustomed to working with binary and hex that was probably mumbo jumbo. Basically, try:

01 1D F0A8 61 F43E 10 88 30 A5 04 00 00 00 00 00 9E

For every increment ofthe red digityou go up, theimage will shift up two (interlaced) pixels, and if A goes down the image will shift down. Think of the blue digit as the "carry" value: if you go up past "F" on the red digit, you start over at "0" and change the carry digit to 8. If you go below "0" in the down direction, the carry bit at blue becomes "0". Make sense? (Barely does, to me)

0 Kudos
hackiewakie
Beginner
1,715 Views

Arch,

Hey, this worked.. we moved the image down.., this is fun...

We are still 10 pixelstoo high, and since we're aming for perfection we're 4 pixels too far right.

So..... We need to move the image down 10 morepixels and left 4 pixels

So i understand this: for every decrement of the A value we move the image down 2 pixels

so right now its 26 =(1A)

take 10 pixels divide by 2 = 5 pixels

decrease the 26 by 5 =21

21 converted to hex is 15h

I tried modifing the values muself and lost sync and had to go safe mode to recover. obviously did something wrong.

help...

0 Kudos
Aaron_B_Intel
Employee
1,715 Views

01 1D F0A8 61 F43E 10 88 30 55 04 00 00 00 00 00 9E

should have worked. It's possible there's an issue with odd numbers there (trying 4 and 6 might improve matters), but that doesn't really make sense to me. Vertical sync is a tricky one because it drives refresh rate and monitors can be very picky about sync and offsets to sync.

To get the 4 pixels left, switch the following value

01 1D F0A8 61 F43E 10 8C 30 55 04 00 00 00 00 00 9E

Similar to what we've been doing to vertical, this increases the distance from the end of the line to the horizontal sync pulse, which effectively shifts the image left.

0 Kudos
hackiewakie
Beginner
1,715 Views

Arch01,1D,F0,A8,61,F4,3E,10,8C,30,25,04,00,00,00,00,00,9E,37,01

I moved it down more...

This is the best so far, perfect on the vertical.

But I don't think the image shifted to the left at all are we going in the correct direction?

Half of the scroll bar is cut off.

I have to move themouse off the screen to scroll up or down....

.....should we try another 4 pixels?

Is this correct?

01,1D,F0,A8,61,F4,3E,10,84,30,25,04,00,00,00,00,00,9E,37,01

thanks

Hakie

0 Kudos
Aaron_B_Intel
Employee
1,715 Views

Glad the vertical worked.

Shifting left should definitely be accomplished by increasing the offset value, so if 8C isn't enough, try incrementing further. Fortunately, there's no weird 2x needs horizontally, and no weird carry bit we need to use, so it should be 1:1: if you want8 more pixels,add 8 to the 8C value in hexadecimal and it should move.

0 Kudos
hackiewakie
Beginner
1,715 Views

Arch,

I was experimenting last night and was decrementing the 8C value...

I took it as low as: 01,1D,F0,A8,61,F4,3E,10,80,30,25,04,00,00,00,00,00,9E,37,01

and didn't really notice much change...wonder why it wasn't shifting the wrong way...

8C in hex = 140 in decimal(add 8 to140 =148)

94 in hex =148

01,1D,F0,A8,61,F4,3E,10,94,30,25,04,00,00,00,00,00,9E,37,01

Shall I try that instead?

By the way It looks sooooo awesome. I downloaded one of thosewindowsHD videos andit's crystal clear... It givesdish network @1080i a run for it's money...

Web surfingyou need 20-20 vision because the detail is so fine it's hard to read the small text.... My set is capable of 1080i but not 1080p i wonder if that's the reason...

I kicked up the DPI from 96 to 120... not sure how this helped...It didn't look all that different.. any suggestions on how to make it more readable for web usage...

I have a 8 megapixel camera and the photos are amazing at 70 inches.....

-hackie..

0 Kudos
Aaron_B_Intel
Employee
1,715 Views

Yes, I'd increment to 94. Think of it this way: the value we're adjusting is the horizontal sync offset. It's the distance from the last horizontal pixel and (this is an oversimplification:) the right edge of the screen. If you reduce it, the last horizontal pixel gets closer to the right edge of the screen, and therefore the image is shifting right. If you increase it, the last horizontal pixel gets farther from the right edge of the screen, and therefore the image is shifting left.

Some monitors have "auto image adjust" features, and that might be why you're seeing little to no shift when you decrement-- it's deciding the image is already too far right and it adjusts its own signal to match what it thinks is best for you. But you should be able to shift left to some extent before that kicks in on that side.

0 Kudos
hackiewakie
Beginner
1,715 Views

Arch,

Thank you again for all your help you're providing to all us newbee's. I'm sure many of us would have just given up and settled with black bars, and over-scan if it wasn't for you.

You've certainly taught me a thing or two about editing.inf files and how monitors work.

Companies like Intel, Microsoft, ATI etc, need more people like you!

Thanks again from all of us!

-Hackie

0 Kudos
hackiewakie
Beginner
1,715 Views

Arch,

Getting back to shifting the image to the left.... (so that the start button is closer to the bottom left edge....

I've been playing around with the 94

I've incremented this number a lot and the screen does not shift to the left at all.

Actually it does not shift at all, no matter if i increment or decrement...

Could it be another value that' casuingthe 94 to beoverwritten or ignored?

01,1D,F0,A8,61,F4,3E,10,94,30,25,04,00,00,00,00,00,9E,37,01

Thanks

-hackie

0 Kudos
Aaron_B_Intel
Employee
1,715 Views

Shouldn't be, Hackie. Only thing I can think of is image processing happening internal to the TV itself. Especially if it's doing deinterlacing, it could be processing the incoming signal and adjusting it to the right.

01,1D,F0,A8,61,F4,3E,10,94,30,25,04,00,00,00,00,00,9E,37,01

You could add a much larger number and see what happens (try C4 or even F4), but you're doing everything right. At some point it's your TV. You could add more active pixels to make sure the space gets filled to the left, or perhaps your TV is trying to "center" the image, so fewer pixels would be warranted. Difficult to predict. Would love to hear what results you see, though.

0 Kudos
Reply