[Newbie]How can I overide the detection of monitor in XF4.2?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,
I've been quite frustrated for a whole week. I'm using
Xfree86 4.2 with Slackware 8.0 on my IBM Thinkpad a20p
with 1400x1050 LCD panel and Rage Mobility M-3. The
detection of the screen is quite ok, I even do not
need to add modeline for 1400x1050 that it works
automatically.
But the problem is, I cannot get any resolution below
1024x768, which I think is quite important for running
SDL applications.
An interesting thing is that, the xfree86 version in
Mandrake 8.1 can detects 640x480 up to 1400x1050, but
either slackware's or xfree86's original binary can
not. I've tried copy Modelines using xvidtune from
mandrake to slackware, but it does not help. Also not
helping is copy XFree86Config-4 from mandrake to
slackware.
Anyone can help me?

Forgive my poor english, it's not my native language.

PS: Lines i think may help in XFree86.0.log
(II) R128(0): VESA BIOS detected
(II) R128(0): VESA VBE Version 2.0
(II) R128(0): VESA VBE Total Mem: 16384 kB
(II) R128(0): VESA VBE OEM: ATI MOBILE M3
(II) R128(0): VESA VBE OEM Software Rev: 1.0
(II) R128(0): VESA VBE OEM Vendor: ATI Technologies
Inc.
(II) R128(0): VESA VBE OEM Product: M3  
(II) R128(0): VESA VBE OEM Product Rev: 01.00
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Reloading /usr/X11R6/lib/modules/libddc.a
(II) R128(0): VESA VBE DDC supported
(II) R128(0): VESA VBE DDC Level none
(II) R128(0): VESA VBE DDC transfer in appr. 2 sec.
(II) R128(0): VESA VBE DDC read failed
(**) R128(0): Using gamma correction (1.0, 1.0, 1.0)
(II) R128(0): My Monitor: Using hsync range of
30.00-100.00 kHz
(II) R128(0): My Monitor: Using vrefresh range of
50.00-100.00 Hz
(II) R128(0): Clock range:  12.50 to 250.00 MHz
(II) R128(0): Not using default mode "640x350" (hsync
out of range)
(II) R128(0): Not using default mode "320x175" (bad
mode clock/interlace/doublescan)
(II) R128(0): Not using default mode "640x400" (hsync
out of range)
(II) R128(0): Not using default mode "320x200" (bad
mode clock/interlace/doubles
can)
(II) R128(0): Not using default mode "720x400" (no
mode of this name)
(II) R128(0): Not using default mode "360x200" (bad
mode clock/interlace/doubles
can)
(II) R128(0): Not using default mode "640x480" (hsync
out of range)
(II) R128(0): Not using default mode "320x240" (bad
mode clock/interlace/doubles
can)
(II) R128(0): Not using default mode "640x480" (hsync
out of range)
(II) R128(0): Not using default mode "320x240" (bad
mode clock/interlace/doubles
can)
(II) R128(0): Not using default mode "640x480" (hsync
out of range)
(II) R128(0): Not using default mode "320x240" (bad
mode clock/interlace/doubles
can)
(II) R128(0): Not using default mode "640x480" (hsync
out of range)
(II) R128(0): Not using default mode "320x240" (bad
mode clock/interlace/doubles
can)(II) R128(0): Not using default mode "800x600"
(vrefresh out of range)
(II) R128(0): Not using default mode "400x300" (bad
mode clock/interlace/doubles
can)
(II) R128(0): Not using default mode "800x600"
(vrefresh out of range)
(II) R128(0): Not using default mode "400x300" (bad
mode clock/interlace/doubles
can)
(II) R128(0): Not using default mode "800x600"
(vrefresh out of range)
(II) R128(0): Not using default mode "400x300" (bad
mode clock/interlace/doubles
can)
(II) R128(0): Not using default mode "800x600"
(vrefresh out of range)
(II) R128(0): Not using default mode "400x300" (bad
mode clock/interlace/doubles
can)
(II) R128(0): Not using default mode "800x600"
(vrefresh out of range)
(II) R128(0): Not using default mode "400x300" (bad
mode clock/interlace/doubles
can)
(II) R128(0): Not using default mode "1024x768" (bad
mode clock/interlace/double
scan)
(II) R128(0): Not using default mode "512x384" (bad
mode clock/interlace/doubles
can)
(II) R128(0): Not using default mode "640x512" (bad
mode clock/interlace/doubles
can)
...
(II) R128(0): Not using mode "640x480" (no mode of
this name)
(II) R128(0): Not using mode "800x600" (no mode of
this name)
(II) R128(0): Not using mode "1024x768" (no mode of
this name)
(**) R128(0): Virtual size is 1400x1050 (pitch 1408)
(**) R128(0): Default mode "1280x1024": 108.0 MHz,
100.4 kHz, 96.6 Hz
(II) R128(0): Modeline "1280x1024"  108.00  1280 1328
1342 1568  1024 1025 1028 
1040 +hsync +vsync
(**) R128(0): Default mode "1400x1050": 108.0 MHz,
92.3 kHz, 86.6 Hz
(II) R128(0): Modeline "1400x1050"  108.00  1400 1448
1462 1688  1050 1050 1053 
1066 +hsync +vsync
(==) R128(0): DPI set to (75, 75)

While the correct modeline from mandrake:
"640x480"     108.00    640  688  702  928    480  480
 483  496 -hsync -vsync
"800x600"     108.00    800  848  862 1088    600  600
 603  616 +hsync +vsync
"1024x768"    108.00   1024 1072 1086 1312    768  769
 772  784 -hsync -vsync


__________________________________________________
Do You Yahoo!?
Yahoo! Games - play chess, backgammon, pool and more
http://games.yahoo.com/


[Index of Archives]     [XFree86]     [Xfree86 Xpert]     [X.org]     [IETF Annouce]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Picture Sharing]     [Linux Security]     [Linux RAID]

  Powered by Linux