Your comments are correct there is something wrong with the monitor
settings. In this section of your config file
Section "Monitor"
Indentifier "Monitor0"
VendorNmae "Monitor Vendor"
ModelName "Unprobed Monitor"
HorizSync 50.0-61.0
VertRefresh 31.5-31.5
Options "dpms"
EndSection
The HorizSync and VertRefresh rates are swapped over. I don't believe your
monitor has a HORIZONTAL refresh rate of 50 to 61 KHZ and a Vertical Refresh
of 31.5HZ.
That's why you get lots of messages like this
(II) SAVAGE(0): Not using default mode "640 * 350" (hsync out of
range)
and
(II) SAVAGE(0): Not using default mode "800 * 600" (vrefresh out of
range)
The label on the back of your monitor should tell you what the refresh rates
should be.
Secondly I note that your have a Savage chipset.
This may explain why you had the problem where your monitor went blank.
(Your original problem).
Fortunately I've seen this problem my self and the solution is reasonably
easy.
In the following section.
Section "Device"
Identifier "VideoCard0"
Driver "Savage"
VendorNmae "VideoCard vendor"
BoardName "S3 Prosavage KM133"
EndSection
Add the following lines before the EndSection.
Option "UseBIOS" "False"
VideoRAM 8192
The first line stops XFree from attempting to use settings in the Savage
BIOS which has been known to cause problems.
The second line tells the Savage Driver how much of your system RAM is
allocated to your graphics controller. The value should be the same as the
amount of video RAM allocated in your BIOS.
Note that your BIOS will probably allocate the memory in MBytes while the
VideoRAM setting is in Kbytes. So in my example above I have the video ram
in the bios set to 8M therefore my VideoRAM setting in the config file is
8192 (8M x 1024).
Hope this helps.
Kevin
email: [EMAIL PROTECTED]
Tel: +44 (0)118 971 5032
-----Original Message-----
From: John Puri [mailto:[EMAIL PROTECTED]
Sent: 15 January 2005 03:57
To: Benstead, Kevin
Subject: RE: [XFree86] Troubleshoot
Respected
As you requested my /etc/X11/XF86Config
# XFree86 4 configuration created by pyxf86Config
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "DevInputMice" "AlwaysCore"
EndSection
Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "unix/ :7100"
EndSection
Section "Module"
Load "dbe"
Load "extmod"
Load "fbdevhw"
Load "glx"
Load "record"
Load "freetype"
Load "type1"
Load "dri"
EndSection
Section "InputDevice"
Indentifier "Keyboard0"
Driver "keyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/psaux"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection
Section "InputDevice"
# If the normal CorePointer mouse is not a USB mouse then
# this input device can be used in AlwaysCore mode to let you
# also use USB mice at the same time
Identifier "DevInputMice"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/inpu/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection
Section "Monitor"
Indentifier "Monitor0"
VendorNmae "Monitor Vendor"
ModelName "Unprobed Monitor"
HorizSync 50.0-61.0
VertRefresh 31.5-31.5
Options "dpms"
EndSection
Section "Device"
Identifier "VideoCard0"
Driver "Savage"
VendorNmae "VideoCard vendor"
BoardName "S3 Prosavage KM133"
EndSection
Section "Screen"
Identifier "Screen0"
Device "VideoCard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "640 * 480"
EndSubSection
EndSection
Section "DRI"
Group 0
Mode 066
EndSection
/var/log/XFree86.0.log file
After looking the log file I came to guess that my monitor is not been
supported. My
monitor is PROLINK and model no is : PRO 1570/S. When installing this model
number was
unlisted and the system by default took Unprobed Monitor. And also by
default it take
horizsync 50 - 61
vertsync 31.5
How can I know about ranges of monitor? I have written some last message of
the file.
(II) SAVAGE(0): Monitor0: Using hsync range of 50.00 - 61.0 kHz
(II) SAVAGE(0): Monitor0: Using vrefresh value of 31.50 Hz
(II) SAVAGE(0): Clock range: 10.00 to 220.00 MHz
(II) SAVAGE(0): Not using default mode "640 * 350" (hsync out of range)
(II) SAVAGE(0): Not using default mode "320 * 175" (hsync out of range)
(II) SAVAGE(0): Not using default mode "640 * 400" (hsync out of range)
(II) SAVAGE(0): Not using default mode "320 * 200" (hsync out of range)
(II) SAVAGE(0): Not using default mode "720 * 400" (hsync out of range)
(II) SAVAGE(0): Not using default mode "360 * 200" (hsync out of range)
(II) SAVAGE(0): Not using default mode "640 * 480" (hsync out of range)
(II) SAVAGE(0): Not using default mode "320 * 240" (hsync out of range)
which continues go on with differernt resolution size. and also
(II) SAVAGE(0): Not using default mode "800 * 600" (vrefresh out of range)
(II) SAVAGE(0): Not using default mode "400 * 300" (vrefresh out of range)
(II) SAVAGE(0): Not using default mode "640 * 480" (vrefresh out of range)
(WW) SAVAGE(0): Mode pool is empty
(EE) SAVAGE(0): No valid modes found
(II) Unload Module: "Savage"
(II) Unload Module: "abe"
(II) Unloading /usr/X11R6/lib/modules/libabe.a
(II) Unload Module: "int10"
(II) Unloading /usr/X11R6/lib/modules/linux/libint10.a
(II) Unload Module: "vgahw"
(II) Unloading /usr/X11R6/lib/modules/libvgahw.a
(EE) Screen(s) found, but non have a usable configuration
Fatal server error
no screen found
If I change monitor what do I have to configure? While running Windows
Bootdisk Linux will be lost, to recover it what do I have to do? I have disk
partation as below :
/ (2761mb)
/home (500mb)
swap (188mb)
/tmp (100mb). Is this partation all right?
Hope to have a favourable reply.
Thanking sincerely
Yahoo! Messenger - Communicate instantly..."Ping" your friends today!
Download Messenger Now
_______________________________________________
XFree86 mailing list
XFree86@XFree86.Org
http://XFree86.Org/mailman/listinfo/xfree86
