Problem with VESA and 1680x1050
jw
jwdevel at gmail.com
Mon Jul 13 01:19:12 UTC 2009
I have a new box with an onboard GeForce 8200, which is not supported
by the 'nv' driver yet.
Therefore I'm trying to get X working with VESA.
It works up to 1280x1024, but the (LCD) screen's native res. is
1680x1050, and displays other resolutions fairly blurry.
I followed instructions in the handbook
(http://www.freebsd.org/doc/en/books/handbook/x-config.html) but it
did not help.
Some details below, if anyone has any insights...
I attached my log, but I think the relevant sections are:
First VESA detects the mode (looks good to me)
<snip>
(II) VESA(0): Manufacturer's mask: 0
(II) VESA(0): Supported Future Video Modes:
(II) VESA(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) VESA(0): #1: hsize: 1280 vsize 960 refresh: 60 vid: 16513
(II) VESA(0): #2: hsize: 1152 vsize 864 refresh: 75 vid: 20337
(II) VESA(0): #3: hsize: 1440 vsize 900 refresh: 60 vid: 149
(II) VESA(0): #4: hsize: 1440 vsize 900 refresh: 75 vid: 3989
(II) VESA(0): #5: hsize: 1680 vsize 1050 refresh: 60 vid: 179
(II) VESA(0): #6: hsize: 1280 vsize 720 refresh: 60 vid: 49281
(II) VESA(0): #7: hsize: 1600 vsize 1200 refresh: 60 vid: 16553
(II) VESA(0): Supported additional Video Mode:
(II) VESA(0): clock: 146.2 MHz Image Size: 408 x 255 mm
(II) VESA(0): h_active: 1680 h_sync: 1784 h_sync_end 1960
h_blank_end 2240 h_border: 0
(II) VESA(0): v_active: 1050 v_sync: 1053 v_sync_end 1059
v_blanking: 1089 v_border: 0
(II) VESA(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 82 kHz,
PixClock max 160 MHz
(II) VESA(0): Monitor name: Acer X193W+
(II) VESA(0): Serial No: LBE090266310
(II) VESA(0): EDID (in hex):
(II) VESA(0): 00ffffffffffff00047214005b017074
(II) VESA(0): 2f11010368291a782ec585a459499a24
(II) VESA(0): 125054bfef0081808140714f9500950f
(II) VESA(0): b30081c0a94021399030621a274068b0
(II) VESA(0): 360098ff1000001c000000fd00384c1e
(II) VESA(0): 5210000a202020202020000000fc0041
(II) VESA(0): 6365722058313933572b0a20000000ff
(II) VESA(0): 004c42453039303236363331300a00a5
(II) VESA(0): EDID vendor "ACR", prod id 20
(II) VESA(0): Using EDID range info for horizontal sync
(II) VESA(0): Using EDID range info for vertical refresh
(II) VESA(0): Printing DDC gathered Modelines:
(II) VESA(0): Modeline "1680x1050"x0.0 146.25 1680 1784 1960 2240
1050 1053 1059 1089 -hsync +vsync (65.3 kHz)
</snip>
But then later on says it can't find the mode:
<snip>
(II) VESA(0): Total Memory: 224 64KB banks (14336kB)
(II) VESA(0): Monitor0: Using hsync range of 30.00-82.00 kHz
(II) VESA(0): Monitor0: Using vrefresh range of 56.00-76.00 Hz
(II) VESA(0): Monitor0: Using maximum pixel clock of 160.00 MHz
(II) VESA(0): Not using mode "1680x1050" (no mode of this name)
(II) VESA(0): Not using built-in mode "1600x1200" (no mode of this name)
(==) VESA(0): Write-combining range (0x0,0x1000) was already clear
(==) VESA(0): Write-combining range (0x0,0x1000) was already clear
(==) VESA(0): Write-combining range (0x0,0x1000) was already clear
(==) VESA(0): Write-combining range (0x0,0x1000) was already clear
(==) VESA(0): Write-combining range (0x0,0x1000) was already clear
(==) VESA(0): Write-combining range (0x0,0x1000) was already clear
(==) VESA(0): Write-combining range (0x0,0x1000) was already clear
(==) VESA(0): Write-combining range (0x0,0x1000) was already clear
(II) VESA(0): Not using built-in mode "640x400" (no mode of this name)
(II) VESA(0): Not using built-in mode "320x400" (no mode of this name)
(II) VESA(0): Not using built-in mode "320x240" (no mode of this name)
(II) VESA(0): Not using built-in mode "320x200" (no mode of this name)
(--) VESA(0): Virtual size is 1280x1024 (pitch 1280)
(**) VESA(0): Built-in mode "1280x1024"
(**) VESA(0): Built-in mode "1024x768"
(**) VESA(0): Built-in mode "800x600"
(**) VESA(0): Built-in mode "640x480"
(**) VESA(0): Display dimensions: (410, 260) mm
(**) VESA(0): DPI set to (79, 100)
</snip>
In particular the line:
(II) VESA(0): Not using mode "1680x1050" (no mode of this name)
So what gives? It seems like VESA is aware that the mode is supported,
yet it drops it later on anyway.
I do note that the Virtual size is shown as 1280x1024.
However, I tried manually adding the line:
Virtual 1680 1050
to my xorg.config. But it still gives the "Not using mode..." message,
and the display is all screwy (wrong pitch for data being sent to the
monitor, so everything is interleaved, i think).
Also, I have read that a mode will be dropped if there is not enough
memory to support it - but I have 14336kB - should be more than
enough, afaik. (1680 x 1050 x 4 =~ 6891kB).
Any other reason it would inexplicably drop the mode?
As the handbook suggested, I tried adding:
Modeline "1680x1050" 146.25 1680 1784 1960 2240 1050 1053 1059
1089 -hsync +vsync
to my "Monitor" section, but that doesn't change anything.
Any ideas?
-John
-------------- next part --------------
A non-text attachment was scrubbed...
Name: xorg.conf
Type: application/octet-stream
Size: 3295 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20090713/a8acb50e/xorg.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Xorg.0.log
Type: application/octet-stream
Size: 56281 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20090713/a8acb50e/Xorg.0.obj
More information about the freebsd-x11
mailing list