| View previous topic :: View next topic |
| Author |
Message |
crimsonphire
n00b
Joined: 25 Mar 2004
Posts: 59
Location: U.S.A.
|
 Posted: Thu Jan 20, 2005 5:14 am Post subject: Using new ati-drivers, and getting very bad performance... |
 |
|
I emerged the latest ati-drivers.
I tried using the ati config but when I moved it and put in xorg.conf it just froze my system, so I used a xorgconfig version using radeon as my driver.
My card is an ati mobile 9000 64mb... This should be pretty good graphics wise, but I am not seeing the gamming performance I am used to...
Even x and movies seem slugish.
Here is my xorg.conf ...
| Code: |
# File generated by xorgconfig.
#
# Copyright 2004 The X.Org Foundation
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
#
# **********************************************************************
# Refer to the xorg.conf(5x) man page for details about the format of
# this file.
# **********************************************************************
# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
# This loads the font modules
Load "type1"
# Load "speedo"
Load "freetype"
# Load "xtt"
# This loads the GLX module
Load "glx"
# This loads the DRI module
Load "dri"
EndSection
# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************
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 (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
#
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/Type1/"
# FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/local/"
# FontPath "/usr/share/fonts/Speedo/"
# FontPath "/usr/share/fonts/TrueType/"
# FontPath "/usr/share/fonts/freefont/"
# The module search path. The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
EndSection
# **********************************************************************
# Server flags section.
# **********************************************************************
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
# Option "NoTrapSignals"
# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# Option "Dont Zoom"
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
# Option "DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# Option "DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
# Option "AllowNonLocalModInDev"
EndSection
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# 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" "pc105"
# 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"
# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xorg"
Option "XkbModel" "pc101"
Option "XkbLayout" "us"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
EndSection
# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the xorg.conf man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "My Monitor"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
HorizSync 31.5
# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
VertRefresh 50-70
EndSection
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
# Standard VGA Device:
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# Device configured by xorgconfig:
Section "Device"
Identifier "** ATI Radeon (generic) [radeon]"
Driver "radeon"
#VideoRam 65536
# Insert Clocks lines here if appropriate
EndSection
# **********************************************************************
# Screen sections
# **********************************************************************
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "** ATI Radeon (generic) [radeon]"
Monitor "My Monitor"
DefaultDepth 24
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
# **********************************************************************
# ServerLayout sections.
# **********************************************************************
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
Section "ServerLayout"
# The Identifier line must be present
Identifier "Simple Layout"
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
Screen "Screen 1"
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
Section "DRI"
Mode 0666
EndSection
|
_________________
"The heart of Gentoo is that concern for others, and the joy we had helping others."
-Daniel Robbins |
|
| Back to top |
|
 |
desertstalker
Apprentice
Joined: 18 Sep 2004
Posts: 209
|
| Posted: Thu Jan 20, 2005 6:23 am Post subject: |
|
|
"radeon" is the xorg implementation of the ati driver not the driver from ATI itself. That is called fglrx.
I recently ran the fglrxconfig and the only problem i ran into was having to rename the "Keyboard" driver to kbd.
I suggest that you use fglrxconfig than copy the device section into the onld config, replactin the ones already there. |
|
| Back to top |
|
|
total_planlos
n00b
Joined: 02 Jan 2005
Posts: 71
Location: Austria/Klagenfurt
|
| Posted: Thu Jan 20, 2005 7:48 am Post subject: |
|
|
I have an ATI MOBIL 9200 and use fglrx and dri is enabled! you could try my xorg.conf if you want:
| Code: |
# File: XF86Config-4
# File generated by fglrxconfig (C) ATI Research, a substitute for xf86config.
# Note by ATI: the below copyright notice is there for servicing possibly
# pending third party rights on the file format and the instance of this file.
#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#
# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **********************************************************************
# **********************************************************************
# DRI Section
# **********************************************************************
Section "dri"
# Access to OpenGL ICD is allowed for all users:
Mode 0666
# Access to OpenGL ICD is restricted to a specific user group:
# Group 100 # users
# Mode 0660
EndSection
# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
# This loads the Type1 and FreeType font modules
Load "type1"
Load "freetype"
# This loads the GLX module
Load "glx" # libglx.a
Load "dri" # libdri.a
EndSection
# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************
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 (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#
FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
FontPath "/usr/share/fonts/ttf-bitstream-vera/"
FontPath "/usr/share/fonts/freefont/"
FontPath "/usr/share/fonts/corefonts/"
# The module search path. The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
EndSection
# **********************************************************************
# Server flags section.
# **********************************************************************
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
# Option "NoTrapSignals"
# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# Option "Dont Zoom"
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
# Option "DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# Option "DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
# Option "AllowNonLocalModInDev"
EndSection
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# 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"
# These are the default XKB settings for XFree86
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "de"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/input/mice"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
EndSection
# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the XF86Config man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "Monitor0"
HorizSync 31.5 - 60.0
VertRefresh 50 - 70
Option "DPMS"
# === mode lines based on GTF ===
# VGA @ 100Hz
# Modeline "640x480@100" 43.163 640 680 744 848 480 481 484 509 +hsync +vsync
# SVGA @ 100Hz
# Modeline "800x600@100" 68.179 800 848 936 1072 600 601 604 636 +hsync +vsync
# XVGA @ 100Hz
# Modeline "1024x768@100" 113.309 1024 1096 1208 1392 768 769 772 814 +hsync +vsync
# 1152x864 @ 60Hz
# Modeline "1152x864@60" 81.642 1152 1216 1336 1520 864 865 868 895 +hsync +vsync
# 1152x864 @ 85Hz
# Modeline "1152x864@85" 119.651 1152 1224 1352 1552 864 865 868 907 +hsync +vsync
# 1152x864 @ 100Hz
# Modeline "1152x864@100" 143.472 1152 1232 1360 1568 864 865 868 915 +hsync +vsync
# 1280x960 @ 75Hz
# Modeline "1280x960@75" 129.859 1280 1368 1504 1728 960 961 964 1002 +hsync +vsync
# 1280x960 @ 100Hz
# Modeline "1280x960@100" 178.992 1280 1376 1520 1760 960 961 964 1017 +hsync +vsync
# SXGA @ 100Hz
# Modeline "1280x1024@100" 190.960 1280 1376 1520 1760 1024 1025 1028 1085 +hsync +vsync
# SPEA GDM-1950 (60Hz,64kHz,110MHz,-,-): 1280x1024 @ V-freq: 60.00 Hz, H-freq: 63.73 KHz
# Modeline "GDM-1950" 109.62 1280 1336 1472 1720 1024 1024 1026 1062 -hsync -vsync
# 1600x1000 @ 60Hz
# Modeline "1600x1000" 133.142 1600 1704 1872 2144 1000 1001 1004 1035 +hsync +vsync
# 1600x1000 @ 75Hz
# Modeline "1600x1000" 169.128 1600 1704 1880 2160 1000 1001 1004 1044 +hsync +vsync
# 1600x1000 @ 85Hz
# Modeline "1600x1000" 194.202 1600 1712 1888 2176 1000 1001 1004 1050 +hsync +vsync
# 1600x1000 @ 100Hz
# Modeline "1600x1000" 232.133 1600 1720 1896 2192 1000 1001 1004 1059 +hsync +vsync
# 1600x1024 @ 60Hz
# Modeline "1600x1024" 136.385 1600 1704 1872 2144 1024 1027 1030 1060 +hsync +vsync
# 1600x1024 @ 75Hz
# Modeline "1600x1024" 174.416 1600 1712 1888 2176 1024 1025 1028 1069 +hsync +vsync
# 1600x1024 @ 76Hz
# Modeline "1600x1024" 170.450 1600 1632 1792 2096 1024 1027 1030 1070 +hsync +vsync
# 1600x1024 @ 85Hz
# Modeline "1600x1024" 198.832 1600 1712 1888 2176 1024 1027 1030 1075 +hsync +vsync
# 1920x1080 @ 60Hz
# Modeline "1920x1080" 172.798 1920 2040 2248 2576 1080 1081 1084 1118 -hsync -vsync
# 1920x1080 @ 75Hz
# Modeline "1920x1080" 211.436 1920 2056 2264 2608 1080 1081 1084 1126 +hsync +vsync
# 1920x1200 @ 60Hz
# Modeline "1920x1200" 193.156 1920 2048 2256 2592 1200 1201 1203 1242 +hsync +vsync
# 1920x1200 @ 75Hz
# Modeline "1920x1200" 246.590 1920 2064 2272 2624 1200 1201 1203 1253 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 1400x1050 @ 60Hz M9 Laptop mode
# ModeLine "1400x1050" 122.000 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync
# 1920x2400 @ 25Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@25" 124.620 1920 1928 1980 2048 2400 2401 2403 2434 +hsync +vsync
# 1920x2400 @ 30Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@30" 149.250 1920 1928 1982 2044 2400 2402 2404 2434 +hsync +vsync
EndSection
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
# Standard VGA Device:
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# installed.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# === ATI device section ===
Section "Device"
Identifier "ATI Graphics Adapter"
Driver "fglrx"
# ### generic DRI settings ###
# === disable PnP Monitor ===
#Option "NoDDC"
# === disable/enable XAA/DRI ===
Option "no_accel" "no"
Option "no_dri" "no"
# === misc DRI settings ===
Option "mtrr" "off" # disable DRI mtrr mapper, driver has its own code for mtrr
# ### FireGL DDX driver module specific settings ###
# === Screen Management ===
Option "DesktopSetup" "0x00000100"
Option "MonitorLayout" "AUTO, NONE"
Option "IgnoreEDID" "off"
Option "HSync2" "unspecified"
Option "VRefresh2" "unspecified"
Option "ScreenOverlap" "0"
# === TV-out Management ===
Option "NoTV" "no"
Option "TVStandard" "PAL-B"
Option "TVHSizeAdj" "0"
Option "TVVSizeAdj" "0"
Option "TVHPosAdj" "0"
Option "TVVPosAdj" "0"
Option "TVHStartAdj" "0"
Option "TVColorAdj" "0"
Option "GammaCorrectionI" "0x00000000"
Option "GammaCorrectionII" "0x00000000"
# === OpenGL specific profiles/settings ===
Option "Capabilities" "0x00008000"
# === Video Overlay for the Xv extension ===
Option "VideoOverlay" "on"
# === OpenGL Overlay ===
# Note: When OpenGL Overlay is enabled, Video Overlay
# will be disabled automatically
Option "OpenGLOverlay" "off"
# === Center Mode (Laptops only) ===
Option "CenterMode" "off"
# === Pseudo Color Visuals (8-bit visuals) ===
Option "PseudoColorVisuals" "off"
# === QBS Management ===
Option "Stereo" "off"
Option "StereoSyncEnable" "1"
# === FSAA Management ===
Option "FSAAEnable" "no"
Option "FSAAScale" "1"
Option "FSAADisableGamma" "no"
Option "FSAACustomizeMSPos" "no"
Option "FSAAMSPosX0" "0.000000"
Option "FSAAMSPosY0" "0.000000"
Option "FSAAMSPosX1" "0.000000"
Option "FSAAMSPosY1" "0.000000"
Option "FSAAMSPosX2" "0.000000"
Option "FSAAMSPosY2" "0.000000"
Option "FSAAMSPosX3" "0.000000"
Option "FSAAMSPosY3" "0.000000"
Option "FSAAMSPosX4" "0.000000"
Option "FSAAMSPosY4" "0.000000"
Option "FSAAMSPosX5" "0.000000"
Option "FSAAMSPosY5" "0.000000"
# === Misc Options ===
Option "UseFastTLS" "0"
Option "BlockSignalsOnLock" "on"
Option "UseInternalAGPGART" "yes"
Option "ForceGenericCPU" "no"
BusID "PCI:1:0:0" # vendor=1002, device=4c66
Screen 0
EndSection
# **********************************************************************
# Screen sections
# **********************************************************************
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen0"
Device "ATI Graphics Adapter"
Monitor "Monitor0"
DefaultDepth 24
Option "backingstore"
Subsection "Display"
Depth 24
Modes "1280x800"
ViewPort 0 0 # initial origin if mode is smaller than desktop
Virtual 1024 768
EndSubsection
EndSection
# **********************************************************************
# ServerLayout sections.
# **********************************************************************
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
Section "ServerLayout"
# The Identifier line must be present
Identifier "Server Layout"
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.
Screen "Screen0"
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
#Section "Extensions"
# Option "Composite" "Enable"
# Option "RENDER" "Enable"
#EndSection
### EOF ###
|
|
|
| Back to top |
|
|
RealNitro
Tux's lil' helper
Joined: 01 Jul 2004
Posts: 98
|
| Posted: Thu Jan 20, 2005 9:27 pm Post subject: |
|
|
I'm having the same problems with my system:
(- Intel P4 3.0Ghz, 1.5gigs of RAM)
- ATI Radeon 9800
- xorg-x11-6.8.0-r3
- ati-drivers-8.8.25
Today, I updated my system from xog 6.7 to 6.8 (6.8 was masked because the ati-drivers did not support it). I had a little problem with the Keyboard->kbd thing, but I can boot now. The only problem is that from the moment the X server starts, everything becomes sloooow (as in 7 seconds to start gnome-terminal). e.g. when I start gedit, the CPU use goes to 100% for 6 seconds, and then gedit appears.
One thing that might solve this:
| Code: | dell root # opengl-update ati
* Switching to ati OpenGL interface...
ln: creating symbolic link `/usr/lib/modules/extensions/libglx.a' to `/usr/lib/opengl/ati/extensions/libglx.a': No such file or directory [ ok ] |
It seems there is something wrong there, but I don't know what... Maybe I should try using fglrxconfig, but I don't want to 'rebuild' my xorg.conf again (fonts and mouse stuff).
This is the part of my xorg.conf file that has to do with libglx.a:
| Code: | # **********************************************************************
# DRI Section
# **********************************************************************
Section "dri"
# Access to OpenGL ICD is allowed for all users:
Mode 0666
# Access to OpenGL ICD is restricted to a specific user group:
# Group 100 # users
# Mode 0660
EndSection
# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" ###
EndSubSection
# This loads the Type1 and FreeType font modules
Load "type1"
Load "freetype"
# This loads the GLX module
Load "glx" # libglx.a
Load "dri" # libdri.a
EndSection
|
Any help is appreciated.
EDIT: I made a new XF86Config-4 file with fglrxconfig, and did | Code: | | diff xorg.conf XF86Config-4 |
the result (with some sections removed):
| Code: | 26c63
< Option "omit xfree86-dga" ###
---
> Option "omit xfree86-dga" # don't initialise the DGA extension
139c168
< Driver "kbd"
---
> Driver "Keyboard"
186a216
>
197,201c227,228
< Option "Protocol" "ExplorerPS/2"
< Option "Buttons" "7"
< Option "ZAxisMapping" "6 7"
< Option "SendCoreEvents" "true"
< Option "Resolution" "1200"
---
> Option "Protocol" "ImPS/2"
> Option "ZAxisMapping" "4 5"
212,213c239,240
< Option "BaudRate" "19200" #"9600"
< Option "SampleRate" "300" # "150"
---
> # Option "BaudRate" "9600"
> # Option "SampleRate" "150"
235,256c317,376
<
< Identifier "Dell-monitor"
<
< # HorizSync is in kHz unless units are specified.
< # HorizSync may be a comma separated list of discrete values, or a
< # comma separated list of ranges of values.
< # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
< # USER MANUAL FOR THE CORRECT NUMBERS.
<
< HorizSync 31.5 - 57.0
<
< # HorizSync 30-64 # multisync
< # HorizSync 31.5, 35.2 # multiple fixed sync frequencies
< # HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
<
< # VertRefresh is in Hz unless units are specified.
< # VertRefresh may be a comma separated list of discrete values, or a
< # comma separated list of ranges of values.
< # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
< # USER MANUAL FOR THE CORRECT NUMBERS.
<
< VertRefresh 60-75
---
> Identifier "Monitor0"
> HorizSync 31.5 - 48.4
> VertRefresh 60 - 85
> Option "DPMS"
259a380
>
347,348c468,469
< Option "FSAAEnable" "yes"
< Option "FSAAScale" "4"
---
> Option "FSAAEnable" "no"
> Option "FSAAScale" "1"
366c487
< Option "UseInternalAGPGART" "no"
---
> Option "UseInternalAGPGART" "yes"
370,371d490
< # added for screenshot prob
< Option "KernelModuleParm" "agplock=0"
385c504
< Monitor "Dell-monitor"
---
> Monitor "Monitor0"
430,434c549
< #TRANSPARANT
< #Section "Extensions"
< # Option "Composite" "Enable"
< # Option "RENDER" "Enable"
< #EndSection
---
> ### EOF ###
|
|
|
| Back to top |
|
|
Wedge_
Advocate
Joined: 08 Aug 2002
Posts: 3614
Location: Scotland
|
| Posted: Thu Jan 20, 2005 9:48 pm Post subject: |
|
|
| RealNitro wrote: | One thing that might solve this:
| Code: | dell root # opengl-update ati
* Switching to ati OpenGL interface...
ln: creating symbolic link `/usr/lib/modules/extensions/libglx.a' to `/usr/lib/opengl/ati/extensions/libglx.a': No such file or directory [ ok ] |
It seems there is something wrong there, but I don't know what... |
Do you have a /usr/lib/modules/extensions directory? If not, create it using "mkdir -p /usr/lib/modules/extensions" and try running opengl-update again. It sounds like you don't have 3D acceleration enabled - try running "glxinfo | grep direct".
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ |
|
| Back to top |
|
|
RealNitro
Tux's lil' helper
Joined: 01 Jul 2004
Posts: 98
|
| Posted: Fri Jan 21, 2005 7:40 am Post subject: |
|
|
| Wedge_ wrote: | | RealNitro wrote: | One thing that might solve this:
| Code: | dell root # opengl-update ati
* Switching to ati OpenGL interface...
ln: creating symbolic link `/usr/lib/modules/extensions/libglx.a' to `/usr/lib/opengl/ati/extensions/libglx.a': No such file or directory [ ok ] |
It seems there is something wrong there, but I don't know what... |
Do you have a /usr/lib/modules/extensions directory? If not, create it using "mkdir -p /usr/lib/modules/extensions" and try running opengl-update again. It sounds like you don't have 3D acceleration enabled - try running "glxinfo | grep direct". |
I created the directory, and opengl-update worked: | Code: | dell root # opengl-update ati
* Switching to ati OpenGL interface... [ ok ]
dell root # glxinfo | grep direct
direct rendering: Yes |
so direct rendering works (I can play 3d games too). But my system is still to slow (no improvement). I'll do a reboot, and if things speed up after that, I'll post it here. If I don't, the problem is still there. |
|
| Back to top |
|
|
Wedge_
Advocate
Joined: 08 Aug 2002
Posts: 3614
Location: Scotland
|
| Posted: Fri Jan 21, 2005 8:49 am Post subject: |
|
|
If things are still slow, post your log.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ |
|
| Back to top |
|
|
RealNitro
Tux's lil' helper
Joined: 01 Jul 2004
Posts: 98
|
| Posted: Fri Jan 21, 2005 10:18 am Post subject: |
|
|
| Wedge_ wrote: | | If things are still slow, post your log. |
I did an emerge sync this morning, and upgraded to version ati-drivers-8.8.25-r1. Still no use though. I uploaded my log here. One thing I must say: it's a loooong time ago since I did an etc-update. Maybe that's where the problem is? Problem is that I'm studying for my exams atm. Next one is tuesday. I'm planning to do a complete etc-update after the exam.
Erm, I'v checked out the log and: | Code: | drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card12
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed |
seems suspicious. Two things: the ati-drivers ebuild seems to patch the kernel somehow? But doesn't it patch the 2.6.10, and not the 2.6.8? (I recompiled the gentoo-dev-sources-2.6.8_r3 yesterday), second: this topic says there is something wrong with my kernel. How come? I'm using the same options as with the previous ati-drivers. |
|
| Back to top |
|
|
Wedge_
Advocate
Joined: 08 Aug 2002
Posts: 3614
Location: Scotland
|
| Posted: Fri Jan 21, 2005 10:27 am Post subject: |
|
|
| RealNitro wrote: | | One thing I must say: it's a loooong time ago since I did an etc-update. Maybe that's where the problem is? Problem is that I'm studying for my exams atm. Next one is tuesday. I'm planning to do a complete etc-update after the exam. |
I don't know for sure, it would depend on what needs updated, but I don't think it's very likely. Worth checking though.
The long string of drmOpenDevice and drmOpenByBusid actually appear to be "normal" with the new drivers. They didn't appear before but I also have them in my logs now. The only thing that indicates a problem is that the first two calls don't succeed: | Code: | (II) Loading extension ATIFGLRXDRI
(II) fglrx(0): doing DRIScreenInit
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: Open failed
drmOpenByBusid: Searching for BusID PCI:1:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 4, (OK)
drmOpenByBusid: drmOpenMinor returns 4 |
It should look something like this: | Code: | (II) Loading extension ATIFGLRXDRI
(II) fglrx(0): doing DRIScreenInit
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 5, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 5, (OK)
drmOpenByBusid: Searching for BusID PCI:3:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 5, (OK)
drmOpenByBusid: drmOpenMinor returns 5 |
| RealNitro wrote: | | Two things: the ati-drivers ebuild seems to patch the kernel somehow? But doesn't it patch the 2.6.10, and not the 2.6.8? (I recompiled the gentoo-dev-sources-2.6.8_r3 yesterday) |
The driver ebuild should never be attempting to patch the kernel. What you'll be seeing is a patch being applied to the driver itself to take into account changes in the kernel. The patch should work with older kernels even though it has 2.6.10 in the filename.
| RealNitro wrote: | | second: this topic says there is something wrong with my kernel. How come? I'm using the same options as with the previous ati-drivers. |
What do you mean? Do you have the kernel DRM enabled?
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ |
|
| Back to top |
|
|
RealNitro
Tux's lil' helper
Joined: 01 Jul 2004
Posts: 98
|
| Posted: Fri Jan 21, 2005 12:09 pm Post subject: |
|
|
| Wedge_ wrote: | | RealNitro wrote: | | second: this topic says there is something wrong with my kernel. How come? I'm using the same options as with the previous ati-drivers. |
What do you mean? Do you have the kernel DRM enabled? |
Thx for putting your time in this.
No drm enabled in the kernel (not even a module). I just can't figure out what's wrong. Desktop apps (gnome, gdm) are sloooow, but I can play Doom3 better with these new drivers. Maybe it's a gnome-only thing?
[...]
Just started kile, same slowdown. 
lsmod gives:
| Code: | dell linux # lsmod
Module Size Used by
fglrx 238560 7
tun 6656 1
l2cap 22784 2
ohci_hcd 32516 0
tuner 18960 0
tda9887 11524 0
msp3400 22292 0
bttv 147532 0
video_buf 18180 1 bttv
i2c_algo_bit 9224 1 bttv
v4l2_common 5248 1 bttv
btcx_risc 4232 1 bttv
i2c_core 19712 5 tuner,tda9887,msp3400,bttv,i2c_algo_bit
videodev 7936 1 bttv
snd_emu10k1 93832 3
snd_rawmidi 21156 1 snd_emu10k1
snd_ac97_codec 65924 1 snd_emu10k1
snd_util_mem 3712 1 snd_emu10k1
snd_hwdep 7684 1 snd_emu10k1
intel_mch_agp 8208 1
agpgart 28204 2 intel_mch_agp
snd_seq_oss 33024 0
snd_seq_midi_event 6656 1 snd_seq_oss
snd_seq 52752 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 7048 4 snd_emu10k1,snd_rawmidi,snd_seq_oss,snd_seq
snd_pcm_oss 49320 0
snd_pcm 87556 2 snd_emu10k1,snd_pcm_oss
snd_page_alloc 9352 2 snd_emu10k1,snd_pcm
snd_timer 22916 2 snd_seq,snd_pcm
snd_mixer_oss 17920 3 snd_pcm_oss
snd 49892 15 snd_emu10k1,snd_rawmidi,snd_ac97_codec,snd_util_mem,snd_hwdep,
snd_seq_oss,snd_seq_midi_event,snd_seq,snd_seq_device,snd_pcm_oss,
snd_pcm,snd_timer,snd_mixer_oss
hci_usb 10368 2
bluetooth 43396 6 l2cap,hci_usb
8250 20192 2
serial_core 21120 1 8250
uhci_hcd 30476 0
eepro100 27276 0
|
Last edited by RealNitro on Fri Jan 21, 2005 1:29 pm; edited 1 time in total |
|
| Back to top |
|
|
Wedge_
Advocate
Joined: 08 Aug 2002
Posts: 3614
Location: Scotland
|
| Posted: Fri Jan 21, 2005 12:43 pm Post subject: |
|
|
Can you check that you don't get the same slowdown using the radeon driver? Just change the driver name in your xorg.conf from "fglrx" to "radeon" and restart X. You won't have 3D accel of course, but you can try to start some applications and see how fast that goes. Another thing to try is run "top" in a console while you're starting apps, and look for the process consuming all the CPU time. If it's a driver problem it'll almost certainly be the X process.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ |
|
| Back to top |
|
|
RealNitro
Tux's lil' helper
Joined: 01 Jul 2004
Posts: 98
|
| Posted: Fri Jan 21, 2005 12:59 pm Post subject: |
|
|
| Wedge_ wrote: | | Can you check that you don't get the same slowdown using the radeon driver? Just change the driver name in your xorg.conf from "fglrx" to "radeon" and restart X. You won't have 3D accel of course, but you can try to start some applications and see how fast that goes. Another thing to try is run "top" in a console while you're starting apps, and look for the process consuming all the CPU time. If it's a driver problem it'll almost certainly be the X process. |
Just did what you asked:
-> Using top, I noticed that the X CPU usage did never go above 5.3%, over 90% was used by the app (gedit).
-> When I changed the driver to radeon, and killed X, my screen went black (and stayed that way). I rebooted, but the slowdown is still there. Not an ATI issue apparently. (starting Cube only gave me a completely black screen though, dunno if that's normal with the radeon driver) |
|
| Back to top |
|
|
Wedge_
Advocate
Joined: 08 Aug 2002
Posts: 3614
Location: Scotland
|
| Posted: Fri Jan 21, 2005 1:09 pm Post subject: |
|
|
If it's not the ATI driver, check that DMA is still enabled on your hard drives (run "hdparm /dev/hda" etc and look for the "using_dma" line). If it's not enabled, you can turn it on with "hdparm -d1 /dev/hda".
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ |
|
| Back to top |
|
|
RealNitro
Tux's lil' helper
Joined: 01 Jul 2004
Posts: 98
|
| Posted: Fri Jan 21, 2005 1:28 pm Post subject: |
|
|
| Wedge_ wrote: | | If it's not the ATI driver, check that DMA is still enabled on your hard drives (run "hdparm /dev/hda" etc and look for the "using_dma" line). If it's not enabled, you can turn it on with "hdparm -d1 /dev/hda". |
If my hd would have become slow, I would never be able to play/load Doom3 the way I can now. And I can't use hdparm, my hd is a SATA disk. |
|
| Back to top |
|
|
Wedge_
Advocate
Joined: 08 Aug 2002
Posts: 3614
Location: Scotland
|
| Posted: Fri Jan 21, 2005 2:06 pm Post subject: |
|
|
| RealNitro wrote: | | Wedge_ wrote: | | If it's not the ATI driver, check that DMA is still enabled on your hard drives (run "hdparm /dev/hda" etc and look for the "using_dma" line). If it's not enabled, you can turn it on with "hdparm -d1 /dev/hda". |
If my hd would have become slow, I would never be able to play/load Doom3 the way I can now. And I can't use hdparm, my hd is a SATA disk. |
Whoops, should have realised that would affect games as well, sorry. When you have time, I'd suggest upgrading to a 2.6.10 kernel and/or trying a more recent version of Xorg. You might be better off starting a separate thread about this if it doesn't appear to be a driver problem.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ |
|
| Back to top |
|
|
RealNitro
Tux's lil' helper
Joined: 01 Jul 2004
Posts: 98
|
| Posted: Fri Jan 21, 2005 2:38 pm Post subject: |
|
|
| Wedge_ wrote: | | RealNitro wrote: | | Wedge_ wrote: | | If it's not the ATI driver, check that DMA is still enabled on your hard drives (run "hdparm /dev/hda" etc and look for the "using_dma" line). If it's not enabled, you can turn it on with "hdparm -d1 /dev/hda". |
If my hd would have become slow, I would never be able to play/load Doom3 the way I can now. And I can't use hdparm, my hd is a SATA disk. |
Whoops, should have realised that would affect games as well, sorry. When you have time, I'd suggest upgrading to a 2.6.10 kernel and/or trying a more recent version of Xorg. You might be better off starting a separate thread about this if it doesn't appear to be a driver problem. |
k, thx for the help, anyway  |
|
| Back to top |
|
|
RealNitro
Tux's lil' helper
Joined: 01 Jul 2004
Posts: 98
|
| Posted: Sun Jan 23, 2005 7:33 pm Post subject: |
|
|
My pc just finished emerging xorg-x11-6.8.0-r4, and the problem is gone.
Yay!  |
|
| Back to top |
|
|
Wedge_
Advocate
Joined: 08 Aug 2002
Posts: 3614
Location: Scotland
|
| Posted: Sun Jan 23, 2005 8:21 pm Post subject: |
|
|
That's a little weird, but good to hear it 
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
