Subject: Re: X and ATI Mobility M3 chipset
From: Dan Amborn (damborn@newsguy.com)
Date: Wed Dec 13 2000 - 04:50:36 GMT+1
On Tue, 12 Dec 2000 22:23:21 -0800, Sam Daniel
<samhdaniel@earthlink.net> wrote:
>I'm trying to set up a Wedge "Starling" 30M, which uses the ATI Mobility
>M3 video chip (identified by Windows as the ATI Rage 128. I believe it
>is the Mobility LF (chipid 0x4c46).
>
>I'm installing SuSE v7.0. I've already downloaded and installed XFree
>4.0.1, which is supposed to support the Mobility LF. However, SAX won't
>run at all, and xconfigurator doesn't have any card options for the Rage
>128 or the Mobility chips.
>
>When I start X, the machine freezes with a gray screen. Sometimes I can
>get out of X with ctrl-alt-backspace, but sometimes I have to power
>down.
>
>Does anyone have a working XF86Config for this chipset, or any sage
>advice on what I'm doing wrong?
>
>Sam
If you want my XF86Config you are welcome to it. I am using Redhat 7.0
and it works out of the box. I made some small tweaks but its pretty
much standard issue. I am running it on a Dell Inspiron 5000e with the
14.1 inch XGA screen.
Here it is.
# File generated by anaconda.
Section "ServerLayout"
Identifier "Anaconda Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
# 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.
RgbPath "/usr/X11R6/lib/X11/rgb"
# 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.
FontPath "/usr/X11R6/lib/X11/fonts/TrueType"
FontPath "unix/:7100"
EndSection
Section "Module"
Load "GLcore"
Load "dbe"
Load "dri"
Load "extmod"
Load "fbdevhw"
Load "pex5"
Load "glx"
Load "pex5"
Load "record"
Load "xie"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
# Option "AutoRepeat" "500 5"
# when using XQUEUE, comment out the above line, and uncomment the
# following line
# Option "Protocol" "Xqueue"
# 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:nocaps"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc101"
Option "XkbLayout" "us"
Option "XkbVariant" ""
Option "XkbOptions" ""
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "PS/2"
Option "Device" "/dev/psaux"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 30-60
VertRefresh 60-90
EndSection
Section "Device"
# no known options
Identifier "ATI Rage 128 Mobility"
Driver "r128"
VendorName "ATI Rage 128 Mobility"
BoardName "ATI Rage 128 Mobility"
#BusID
EndSection
Section "Screen"
Identifier "Screen0"
Device "ATI Rage 128 Mobility"
Monitor "Monitor0"
DefaultDepth 16
Subsection "Display"
Depth 16
Modes "1024x768"
EndSubsection
EndSection
Section "DRI"
EndSection
--Dan Amborn damborn@newsguy.com
Yoda of Borg are we: Futile is resistance. Assimilate you, we will.
This archive was generated by hypermail 2b25 : Sat Dec 16 2000 - 08:44:15 GMT+1