Problem in Resolution (GUI)
 

hi folks...

i m using RH 9 and facing hell lots of problems regarding GUI... At first during installation i was unable to install in GUI mode... The screen turned blank... Then i used the following command...

boot: linux lowres

it worked out fine, but after completing the installation, i was unable to start X server again... Then i opened the file /etc/X11/XF86config and kept the resolution as 640 * 480... The GUI came back but at very poor resolution....

And ultimately my problem is that if i increase it from 640 * 480, and run startx, the same problem arises again, ie the screen turns blank and a message "Sync. Out of Range" flashes on the screen... Even i tried to change the horrizontal and veritical sync on XF86config, but still i got same bitter taste...

My monitor is SAMTRON from Samsung... And my video card is S3 ProSavage KM 133...

Following are the copy of my XF86config file for additional information:-

--------------------------------------------------------------------------

# XFree86 4 configuration created by redhat-config-xfree86

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "DevInputMice" "AlwaysCore"
EndSection

Section "Files"

# RgbPath is the location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.
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"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# Option "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# Or if you just want both to be control, use:
# Option "XkbOptions" "ctrl:nocaps"
#
Identifier "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" "yes"
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/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "SyncMaster"
DisplaySize 280 210
HorizSync 30.0 - 55.0
VertRefresh 50.0 - 120.0
Option "dpms"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "savage"
VendorName "Videocard vendor"
BoardName "S3 ProSavage KM133"
VideoRam 16384
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "640x480"
EndSubSection
EndSection

Section "DRI"
Group 0
Mode 0666
EndSection

-------------------------------------------------------------------------

So my questions are:-

1. What might be the problem?

2. If the problem is regarding monitor frequency, then why it didnt workout after changing the horrizontal or vertical sync on XF86config?

3. Earlier i used RH 8 with same configuration and everything worked fine, so whats wrong with RH 9?

4. Does my video card is unsupported by this version? If yes, then is there any driver available anywhere for S3 Pro savage KM 133?


That was my problem, and i m seeking for help right now...

Waiting for response and thanks in advance....

Sayantan

India...

try to re-probe your xserver using:
# XFree86 -configure

and then, use the new configuration file.


good luck!

Sorry to say... But it didnt work out...

However i found an alternative solution for that so wanted to share with you all... Just few simple steps.... In the following section...


Section "Device"
Identifier "Videocard0"
Driver "savage"
VendorName "Videocard vendor"
BoardName "S3 ProSavage KM133"
VideoRam 16384
EndSection



Just change the word "savage" with "vesa".....

Chill out.... Prob is solved.....

Congratulations!!

Can you please tell me why did not you change it to something else but to vesa?? me to have a similar problem.

In my case it is i810. I m mandrake 10 user.

It was really a big and 1.5yr old problem for me... I tried to find out many solutions for that, but unfortunately, nothing worked for me... I changed it to "vesa", coz i got this instruction on search result... Hope it may work for u if ur video card is S3ProSavageKM133...


However i didnt try with something other than vesa... I dont want bitter taste again... Now i m enjoying the sweetness... Hope u can enjoy the same....

This is what the manual has to say about vesa :
Type man vesa in a terminal to view the entire manual. Vesa is a generic Video driver that works with most vesa compatible video cards. Sometimes it may just be able to run your videocard. To get improved/better/max performance it's advisable to use a driver provided by the vendor of the particular videocard. I guess you have a machine with an Intel Onboard Video Device (I guess you have an Intel 845/865/........ motherboard) The driver for all these motherboards is now supported by Intel and is known as the i810 driver. That's why you have i810 there.

Post what exact problem you are facing.
Hope this helps!

Hey!
I asked just as to be knowledgible in order to face future problems.yes i have Intel D865GBF moterboard.
I am sorry if it made you pay more attention and pain than required.
My problem is resolved now.

Thanks!

No harm done :)
It is a pleasure to help or provide any information that might be helpful.
Also it's good to hear that your problem is resolved now :D

Thanks again!

So nice of you!!