Can't get 1920x1200 with FC5+945G

[metagroboliser]

Folks,

I'm trying to get a new Conroe workstation up using a 945G motherboard and a Dell 2405fpw (1920x1200 LCD) monitor. Unfortunately, I'm at wit's end on how to get the LCD's native 1920x1200 res going with the i810 driver. Here's the rundown of what I've done so far:

1. The FC5 default driver (xorg-x11-drv-i810-1.4.1.3) couldn't do any better than 1280x1024 no matter what I tried. A brief search on google lead to pulling the 1.6 version from the development repo. (this brought along Xorg-1.1.1-47.fc6). I could now do resolutions higher than 1600x1200.

2. Deployed 915resolution-0.5.2 and set up rc.local to substitute 1920x1200, resulting in:

$ sudo /usr/sbin/915resolution -l
Intel 800/900 Series VBIOS Hack : version 0.5.2

Chipset: 945G
BIOS: TYPE 1
Mode Table Offset: $C0000 + $269
Mode Table Entries: 27

Mode 30 : 640x480, 8 bits/pixel
Mode 32 : 800x600, 8 bits/pixel
Mode 34 : 1024x768, 8 bits/pixel
Mode 38 : 1280x1024, 8 bits/pixel
Mode 3a : 1600x1200, 8 bits/pixel
Mode 3c : 1920x1200, 8 bits/pixel
Mode 41 : 640x480, 16 bits/pixel
Mode 43 : 800x600, 16 bits/pixel
Mode 45 : 1024x768, 16 bits/pixel
Mode 49 : 1280x1024, 16 bits/pixel
Mode 4b : 1600x1200, 16 bits/pixel
Mode 4d : 1920x1200, 16 bits/pixel
Mode 50 : 640x480, 32 bits/pixel
Mode 52 : 800x600, 32 bits/pixel
Mode 54 : 1024x768, 32 bits/pixel
Mode 58 : 1280x1024, 32 bits/pixel
Mode 5a : 1600x1200, 32 bits/pixel
Mode 5c : 1920x1200, 32 bits/pixel

Note the successful injection of the 1920x1200 mode.

3. Relevant section of my xorg.conf:

Section "Monitor"

        Identifier   "Monitor0"
        VendorName   "Dell"
        ModelName    "Dell 2405FPW (Analog)"
        DisplaySize  519        324
        HorizSync    30.0 - 81.0
        VertRefresh  56.0 - 76.0
        ModeLine     "1920x1200" 154.0 1920 1968 2000 2080 1200 1203 1209 1235 -hsync +vsync
        Option      "dpms"
        ## modeline explained http://www.tldp.org/HOWTO/XFree86-Video-Timings-HOWTO/synth.ht$        
        ## also see http://gentoo-wiki.com/HOWTO_Widescreen_Resolutions_(WSXGA)
EndSection

Section "Device"
        Identifier  "Videocard0"
        Driver      "i810"
        VendorName  "Intel"
        BoardName   "Intel Corporation 945G Integrated Graphics Controller"
EndSection

Section "Screen"
        Identifier "Screen0"
        Device     "Videocard0"
        Monitor    "Monitor0"
        DefaultDepth     24
        SubSection "Display"
                Viewport   0 0
                Depth     24
                Modes    "1920x1200"
        EndSubSection
EndSection

Note: I created the ModeLine using /var/log/Xorg.0.log, and also double checked other relevant entries against the log.

4. startx -> Xserver starts successfully, but in 1600x1200!

5. Strangely enough, if I perform these steps with 1680x1050 instead of 1920x1200, everything works as expected ... i.e, Gnome boots up nicely in 1680x1050. (Keep in mind that 1680x1050 is another non-standard, widescreen resolution, just like 1920x1200).

So, for some obscure reason, the 915resolution hack, the xorg.conf, the modelines etc seem to be working fine ... except for 1920x1200! I am at a total loss.

Any ideas?

[landoncz]

Did you try switching resolutions with

gnome-display-properties

?

[metagroboliser]

Indeed, I did ... no joy unfortunately. Any other ideas on what might be worth trying? I'm completely stumped by this behaviour!

Has anybody had success with the 945G/1920x1200 yet. If so, what did you do differently?

[metagroboliser]

Did you try switching resolutions with

Sorry, I mis-reported in my last message. When I try:

 gnome-display-properites

... the applet offers me resolutions only up to 1600x1200... 1920x1200 doesn't show up in the drop-down menu.

landoncz, you may be on to something ... what can I do from here? How can I configure gnome to recognise 1920x1200?

muchthanx in advance.

[UPDATE]:

Here is something potentially incriminating from the Xorg log:

(II) I810(0): Printing DDC gathered Modelines:
...
(II) I810(0): Modeline "1920x1200"  154.00  1920 1968 2000 2080  1200 1203 1209 1235 -hsync +vsync
...
(II) I810(0): Not using mode "1920x1200" (no mode of this name)
...
(--) I810(0): Virtual size is 1600x1200 (pitch 2048)
(**) I810(0): *Built-in mode "1600x1200"
(**) I810(0):  Built-in mode "1280x1024"
(**) I810(0):  Built-in mode "1024x768"
(**) I810(0):  Built-in mode "800x600"
...

It looks like the monitor IS reporting 1920x1200, but it isn't being used because the 'Built-in' modes (which I'm guessing are being pulled from the video BIOS) aren't showing a corresponding mode. However, the 915resolution listing (see first post above) clearly shows the 1920x1200 mode as being present in the BIOS.

What could be going on here? Would it be the driver (xorg-x11-drv-i810.1.6.0) or the server (
xorg-x11-server-Xorg.1.1.1-47) that isn't being able to pick up the high resolution mode from the BIOS?

[UPDATE #2]

Ok, the findings above are now confirmed:

$ xrandr -q
 SZ:    Pixels          Physical       Refresh
*0   1600 x 1200   ( 521mm x 331mm )  *60
 1   1280 x 1024   ( 521mm x 331mm )   75
 2   1024 x 768    ( 521mm x 331mm )   75
 3    800 x 600    ( 521mm x 331mm )   75
Current rotation - normal
Current reflection - none
Rotations possible - normal left inverted right
Reflections possible - none

So here's our problem statement then: for i810/Xorg 7.1, 915resolution and xrandr do not agree on video BIOS modes.

[update #3]
One additional piece to the puzzle: the i810 module generates a couple of V_BIOS checksum warnings in the Xorg log.

...
(II) I810(0): initializing int10
(WW) I810(0): Bad V_BIOS checksum
(II) I810(0): Primary V_BIOS segment is: 0xc000
...
(II) I810(0): Will attempt to tell the BIOS that there is 12288 kB VideoRAM
(II) I810(0): initializing int10
(WW) I810(0): Bad V_BIOS checksum
(II) I810(0): Primary V_BIOS segment is: 0xc000
(II) I810(0): VESA BIOS detected
(II) I810(0): VESA VBE Version 3.0
(II) I810(0): VESA VBE Total Mem: 12288 kB
(II) I810(0): VESA VBE OEM: Intel(r)Lakeport-G Graphics Chip Accelerated V
...

Could it be that the v1.6 i810 driver is trying to be smart and discarding some modes being reported from the V_BIOS because of a bad checsum (caused presumably by 915resolution)?

Where to go from here?

[landoncz]

Yeah, I mentioned the gnome thing because one time I had my resolution tool and xorg correct, but the option I wanted was only available there. I don't know how to change the options available there...

Looking over your xorg, one thing I did notice, even though you have a modeline, you may want to change the default depth in the screen section to match a depth that 955 is putting in your bios, i.e. 32, 16, or 8, but not 24 because 24 is not in your BIOS. Your depth in this section probably needs to use the depth you entered when creating the modeline but I am not sure. I know you've got the modeline in there, so that may not matter, but other than that I am out of ideas...

[mwette]

Here is the list of supported modes from the i810 driver source (kernel 2.6.18).

        /* 640x480 @ 60Hz */
        /* 640x480 @ 70Hz */
        /* 640x480 @ 72Hz */
        /* 640x480 @ 75Hz */
        /* 640x480 @ 85Hz */
        /* 800x600 @ 56Hz */
        /* 800x600 @ 60Hz */
        /* 800x600 @ 70Hz */
        /* 800x600 @ 72Hz */
        /* 800x600 @ 75Hz */
        /* 800x600 @ 85Hz */
        /* 1024x768 @ 60Hz */
        /* 1024x768 @ 70Hz */
        /* 1024x768 @ 75Hz */          
        /* 1024x768 @ 85Hz */
        /* 1152x864 @ 60Hz */ 
        /* 1152x864 @ 70Hz */
        /* 1152x864 @ 72Hz */
        /* 1152x864 @ 75Hz */
        /* 1152x864 @ 85Hz */
        /* 1280x960 @ 60Hz */
        /* 1280x960 @ 75Hz */
        /* 1280x960 @ 85Hz */
        /* 1600x1200 @ 60Hz */
        /* 1600x1200 @ 65 Hz */
        /* 1600x1200 @ 70 Hz */
        /* 1600x1200 @ 72 Hz */
        /* 1600x1200 @ 75 Hz */
        /* 1600x1200 @ 85 Hz */

I think you should read the xorg.conf man page (regarding ModeLine) to come
up with a mode line and then you can tune it with "xvidtune". Good luck. I've done
this before (years ago). It's not easy but it does work. Here are some old notes
for computing the numbers. Maybe others with more recent experience can
chime in.

Name    dot     hor     sys     sye     hore    vert    sys     sye     verte
----    ---     ---     ---     ---     ----    ----    ---     ---     -----

1: set up the following
        name:   use name, like "1000x800"
        dot:    put monitor video bandwidth
        hor:    horizontal res (e.g., 1000)
        vert:   vertical res (e.g., 800)

2: compute hore = hor/0.8, rounded down to number divisible by 8

3: compute verte = vert*1.05, rounded down to number divisible by 8

4: for sys,sye between hor,hore:
        sys=hor+32
        sye=hore-32

5: for sys,sye between vert,verte:
        sys=vert+3
        sye=sys+3

Here are info messages that I found lurking in my /var/log/Xorg.0.log file. I have the Dell 2407 LCD display.

(II) fglrx(0): Supported additional Video Mode:
(II) fglrx(0): clock: 154.0 MHz   Image Size:  519 x 324 mm
(II) fglrx(0): h_active: 1920  h_sync: 1968  h_sync_end 2000 h_blank_end 2080 h_border: 0
(II) fglrx(0): v_active: 1200  v_sync: 1203  v_sync_end 1209 v_blanking: 1235 v_border: 0
(II) fglrx(0): Serial No: CC3026A32RMS
(II) fglrx(0): Monitor name: DELL 2407WFP
(II) fglrx(0): Ranges: V min: 56  V max: 76 Hz, H min: 30  H max: 83 kHz, PixClock max 170MHz

[metagroboliser]

Thanx for the info ... yes, I did pick up the ModeLine from the Xorg log as you've indicated (read up the on the instructions at the Xorg site) ... the problem appears to be elsewhere.

The i810 driver source listing you've provided is a cause for concern though ... I hope the modes listed there do not represent the absolute set of modes the driver can display, regardless of what the video BIOS reports the chipset being capable of ... if that is indeed the case, my symptoms would be fully explained; however, it would indicate an artificial (and unecessary) limitation in the Xrog driver ... with crtical consequences for anyone running high resolution monitors! (keep in mind, the video BIOS natively reports capability of up to 1920x1440 32bit).

I do hope it isn't so.

[Xavior]

I have a Dell 2407WFP as well and can't get the right ratio, in order for images to not look streched,
the ratio must be around 1600x900 or 1.6-1.7
all I get in the gui's are ratios of 1024x768 or 1.3

any ideas? I installed fglrx but still can't seem to get the right ratios,

thanks,
Xav

[schotty]

Yeah, I mentioned the gnome thing because one time I had my resolution tool and xorg correct, but the option I wanted was only available there. I don't know how to change the options available there...

Looking over your xorg, one thing I did notice, even though you have a modeline, you may want to change the default depth in the screen section to match a depth that 955 is putting in your bios, i.e. 32, 16, or 8, but not 24 because 24 is not in your BIOS. Your depth in this section probably needs to use the depth you entered when creating the modeline but I am not sure. I know you've got the modeline in there, so that may not matter, but other than that I am out of ideas...

24 is what he wants. Linux 24-bit is what windows 32-bit is. Why, I forget. If I dig it up Ill add it somewhere in the forums or my website.

[schotty]

The i810 driver source listing you've provided is a cause for concern though ... I hope the modes listed there do not represent the absolute set of modes the driver can display, regardless of what the video BIOS reports the chipset being capable of ... if that is indeed the case, my symptoms would be fully explained; however, it would indicate an artificial (and unecessary) limitation in the Xrog driver ... with crtical consequences for anyone running high resolution monitors! (keep in mind, the video BIOS natively reports capability of up to 1920x1440 32bit).

I do hope it isn't so.

For now I would say so. The driver may not be stable at higher rez's, thus the artificial lock. It appears that Intel is in the works of completely opensourcing their drivers, this one included:
http://www.intellinuxgraphics.org/documentation.html

So what can you do? Wait it out. At least Intel is openning up all their stuff.

[mwette]

more modes are provided in /usr/share/xorg/extramodes.
There is a 1920x1200 @ 60Hz mode there. You can start with
that and use xvidtune.

Here is what is showing up in Xorg.0.log for my XTI1300 running a Dell 24" wide:
Modeline "1920x1200" 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +vsync


Put the ModeLine line in the Monitor Sectino of /etc/X11/xorg.conf.

[ezioostorero]

Hi all,

I'm installing FC6, AKA "2.6.18-1.2798.fc6xen #1 SMP " on an HP nw8440 laptop.

The video card is an "ATI MOBILITY FireGL V5200" and screen resolution is 1680x1050; i.e a geometrical ratio of 16/10.

I snippet of Xorg.0.log that shows 1680x1050 is supported(?):

(II) VESA(0): VESA VBE OEM Product Rev: 01.00
(**) VESA(0): Depth 24, (--) framebuffer bpp 32
(==) VESA(0): RGB weight 888
(==) VESA(0): Default visual is TrueColor
(==) VESA(0): Using gamma correction (1.0, 1.0, 1.0)
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Loading /usr/lib/xorg/modules/libddc.so
(II) Module ddc: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.0
(II) VESA(0): VESA VBE DDC supported
(II) VESA(0): VESA VBE DDC Level 2
(II) VESA(0): VESA VBE DDC transfer in appr. 1 sec.
(II) VESA(0): VESA VBE DDC read successfully
(II) VESA(0): Manufacturer: LPL Model: 1279 Serial#: 0
(II) VESA(0): Year: 2005 Week: 0
(II) VESA(0): EDID Version: 1.2
(II) VESA(0): Digital Display Input
(II) VESA(0): Max H-Image Size [cm]: horiz.: 33 vert.: 21
(II) VESA(0): Gamma: 2.20
(II) VESA(0): No DPMS capabilities specified; RGB/Color Display
(II) VESA(0): First detailed timing is preferred mode
(II) VESA(0): redX: 0.584 redY: 0.331 greenX: 0.323 greenY: 0.547
(II) VESA(0): blueX: 0.154 blueY: 0.139 whiteX: 0.313 whiteY: 0.329
(II) VESA(0): Manufacturer's mask: 0
(II) VESA(0): Supported additional Video Mode:
(II) VESA(0): clock: 122.0 MHz Image Size: 331 x 207 mm
(II) VESA(0): h_active: 1680 h_sync: 1712 h_sync_end 1776 h_blank_end 1904
h_border: 0
(II) VESA(0): v_active: 1050 v_sync: 1051 v_sync_end 1054 v_blanking: 1066
v_border: 0
(II) VESA(0): LGPhilipsLCD
(II) VESA(0): LP154W02-B1K5
(II) VESA(0): EDID (in hex):
(II) VESA(0): 00ffffffffffff00320c791200000000
(II) VESA(0): 000f0102802115780abca59554528c27
(II) VESA(0): 23505400000001010101010101010101
(II) VESA(0): 010101010101a82f90e0601a10402040
(II) VESA(0): 13004bcf100000190000000000000000
(II) VESA(0): 00000000000000000000000000fe004c
(II) VESA(0): 475068696c6970734c43440a000000fe
(II) VESA(0): 004c503135345730322d42314b3500b2
(II) VESA(0): Printing DDC gathered Modelines:
(II) VESA(0): Modeline "1680x1050" 122.00 1680 1712 1776 1904 1050 1051 1054 1066 -hsync -vsync

On the other hand, 1680x1050 does not show up in the Built-in modes list:

(II) VESA(0): Monitor0: Using hsync range of 31.50-90.00 kHz
(II) VESA(0): Monitor0: Using vrefresh range of 59.90-60.10 Hz
(WW) VESA(0): Unable to estimate virtual size
(--) VESA(0): Virtual size is 1400x1050 (pitch 1400)
(**) VESA(0): *Built-in mode "1400x1050"
(**) VESA(0): *Built-in mode "1280x1024"
(**) VESA(0): *Built-in mode "1280x1024"
(**) VESA(0): *Built-in mode "1280x1024"
(**) VESA(0): *Built-in mode "1152x864"
(**) VESA(0): *Built-in mode "1024x768"
(**) VESA(0): *Built-in mode "1024x768"
(**) VESA(0): *Built-in mode "800x600"
(**) VESA(0): *Built-in mode "800x600"
(**) VESA(0): *Built-in mode "640x480"
(**) VESA(0): *Built-in mode "640x480"
(**) VESA(0): *Built-in mode "720x400"
(**) VESA(0): *Built-in mode "640x400"
(**) VESA(0): *Built-in mode "640x400"
(**) VESA(0): *Built-in mode "640x350"
(**) VESA(0): *Built-in mode "512x384"
(**) VESA(0): *Built-in mode "320x240"
(**) VESA(0): *Built-in mode "320x200"
(**) VESA(0): *Built-in mode "320x200"
(**) VESA(0): Display dimensions: (330, 210) mm
(**) VESA(0): DPI set to (107, 126)
(II) VESA(0): Attempting to use 60Hz refresh for mode "1400x1050" (146)
(II) VESA(0): Attempting to use 60Hz refresh for mode "1280x1024" (11b)
(II) VESA(0): Attempting to use 60Hz refresh for mode "1280x1024" (166)

What does this mean? Is that the list of the BIOS-supported modes?
Can't be, Windows recognized the resolution and geometry at once when installed and booted on the very same box :-(

If I select System->Preferences->Screen Resolution ( i.e. gnome-display-properties)

I get the following possible resolutions:

1400x1050
1280x1024
1152x864
1024x768
800x600
And so on, all with a 4/3 geometry; can't find any 16/10 ratio at all.

If, on the other hand, if I run System->Administration->Display (i.e./usr/bin/system-config-display)

I get a richer choice of of resolution and ratios, such as:

1680x1050 This is the one I want
1600x1200
1600x1024
1440x900
1400x1050
.... and so on

If I select the first one (1680x1050) I get a nice warning saying that I should restart X server and that my /etc/X11/xorg.conf has been changed.

So far so good, that's what I like.

BUT ... if I restart X nothing happens, the selected 1680x1050 resolution is replaced by the darn 1400x1050 in the system-config-display screen and everything on my screen is funnyly stretched-wide as before.

And, BTW, there is no hint of 1680x1050 in my new xorg.conf.

Even if I manually add

Modes "1680x1050" "1280x800"

in my "Subsection Display", nothing happens, it's actually erased by system-config-display the next time I run it.

Looks like gnome-display-properties and system-config-display do not share the same config and gnome-display-properties is having the upper hand. Is there a way to have them in agreement?

I know by reading this and other forums that this is quite a known problem, but finding a solution is really not straightforward ... as this very long post implies.


Follows my current xorg.conf

Section "Monitor"

### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
Identifier "Monitor0"
ModelName "LCD Panel 1680x1050"
### Comment all HorizSync and VertSync values to use DDC:
HorizSync 31.5 - 90.0
VertRefresh 59.9 - 60.1
Option "dpms"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "vesa"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

What's wrong with 1680x1050? I managed to run it on FC5 by installing the
ATI drivers (which, as a side effect prevented system-config-display to run at
all), so I wish to avoid this solution, if possible.

Ciao,

Ezio

[mwette]

The problem is that you are using the "vesa" driver. This is for generic VGA compatible
monitors. If you want high resolutions, I think you may need to use a better driver. What
does your /var/log/Xorg.0.log file report as the board chipset? If it is an older chipset then
the packaged "radeon" driver should work. If it's a newer board (w/ 5XX chipset) then you
may want to install the ATI drivers, in which case you should go to the HOWTO section and
look for the thread "Getting ATI ..."

[ezioostorero]

A few Xorg entries related to chipset:

(--) PCI:*(1:0:0) ATI Technologies Inc unknown chipset (0x71c5) rev 0, Mem @ 0xe0000000/28, 0xf4600000/16, I/O @ 0x4000/8

......
(II) VESA: driver for VESA chipsets: vesa
(II) Primary Device is: PCI 01:00:0
(--) Assigning device section with no busID to primary device
(--) Chipset vesa found

Then ... it goes against my religion, but this is how MS-Windows sees the device:

• Card: ATI MOBILITY FireGL V5200
• Chiptype: ATI display adapter (0x71C5)

From these information, I'm assuming (from a Google search) that the chipset is ATI M56.

So, it looks like not being a supported chipset and I'll have to go for the ATI driver (as I did for FC5).... but in this case I'll run into a known bug of system-config-display not working any more. (see http://www.fedoraforum.org/forum/arc.../t-142640.html)

I'll try and let you know.

Thanks,

Ezio

[ezioostorero]

been there, done that :-|

Installed ATI drivers and got the correct resolution... at a price (as expected):

1) /usr/bin/system-config-display does not work any more

[ezio@cevrin ~]# /usr/bin/system-config-display
Traceback (most recent call last):
File "/usr/share/system-config-display/xconf.py", line 377, in ?
dialog = xConfigDialog.XConfigDialog(hardware_state, xconfig,
rhpxl.videocard.VideoCardInfo())
File "/usr/share/system-config-display/xConfigDialog.py", line 572, in
__init__
self.xml.get_widget("secondMonitorLabel").set_text (monitor_list[1].modelname)
TypeError: GtkLabel.set_text() argument 1 must be string, not None

2) Other applications, such as VMWare refuse to set their resolution to the screen one:

Unable to query the valid mode lines from your X server; will not try to
change host resolution when entering fullscreen mode.

Unable to find an appropriate host video mode.
Adding the guest mode to the 'display' subsection of the 'screen' section of
your /etc/X11/XF86Config or /etc/X11/xorg.conf and restarting X is likely to
help.

Failed to switch to full screen SVGA mode.

So, excuse me for the trivial question: what's wrong with the SVGA-ATI-1680x1050 mix?

Cheers,

Ezio