RedHat9 X on ATI-rage-mobility VERY slow to start

RedHat9 X on ATI-rage-mobility VERY slow to start

Post by Rick Stuar » Thu, 24 Apr 2003 07:25:04



I have installed a very generic RedHat9 install on my laptop.  I noticed
that it seems to take a long time for X to start.  The LED's flash 3-4
times with a 1 second delay in between, then I finally see the X-cursor
and then the GDM stuff start to draw.  This laptop has been through
RH6.2,7.3,8.0 without this problem.  I am dual booting with 7.3 and do
not have the problem.

I have NOT tried the XF86Config file from the RH7.3 install.  I am not
on the laptop now, so can not include the XF86Config, but will later in
a followup.

Thanks,

Rick

 
 
 

RedHat9 X on ATI-rage-mobility VERY slow to start

Post by Rick Stuar » Fri, 25 Apr 2003 02:48:59



> I have installed a very generic RedHat9 install on my laptop.  I noticed
> that it seems to take a long time for X to start.  The LED's flash 3-4
> times with a 1 second delay in between, then I finally see the X-cursor
> and then the GDM stuff start to draw.  This laptop has been through
> RH6.2,7.3,8.0 without this problem.  I am dual booting with 7.3 and do
> not have the problem.

> I have NOT tried the XF86Config file from the RH7.3 install.  I am not
> on the laptop now, so can not include the XF86Config, but will later in
> a followup.

> Thanks,

> Rick

As promised, my XF86Config file:

[ XF86Config 3K ]
# 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 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" "PS/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/input/mice"
        Option      "ZAxisMapping" "4 5"
        Option      "Emulate3Buttons" "no"
EndSection

Section "Monitor"
        Identifier   "Monitor0"
        VendorName   "Monitor Vendor"
        ModelName    "cpq1324"
        HorizSync    32.0 - 60.0
        VertRefresh  57.0 - 85.0
        Option      "dpms"
EndSection

Section "Device"
        Identifier  "Videocard0"
        Driver      "ati"
        VendorName  "Videocard vendor"
        BoardName   "ATI Rage Mobility"
EndSection

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

Section "DRI"
        Group        0
        Mode         0666
EndSection

 
 
 

1. XFree86 4.1 + FreeBSD 4.4 + ATI Rage Pro Mobility = Slow Graphics

Hi. Hopefully someone here can answer my question, and I have searched
the 'Net with little result.

Why is X accelerated on Linux, and not FreeBSD for my Mobility
configuration? Is there a difference in the drivers?

Right now the performance is horrible. For example, when I move the
Mozilla window around, it distorts and ghosts very badly. I am using
BlackBox for my WM.

I tried this same X Configuration in the past on Linux, and it was very
fast, even with KDE running.

Thanks,
Eric

2. scanpci utility in /usr/X11R6/bin

3. ATI Rage Mobility w/ External Monitor

4. More then one IP address?

5. ATI Rage Mobility and Red Hat 6.1

6. Broadcasting to 255.255.255.255 on more than on interface

7. ATI Rage Mobility M on a thinkpad 1480

8. L20 DLT robot, command line ?

9. Does XFree86 3.3.6 Support ATI Rage-Mobility Pro ?

10. Sony PCG-F690 (ATI Rage Mobility M1) Problem

11. Xfree86 4.0 and ATI Rage Mobility

12. ATI Rage Mobility M Setup

13. ASUS A7v8X-X, XP2400+, ATI rage mobility, Debian 3.0 problem