ATI Prop. Drivers - config problem:

Hey all,
First off, I'm a new Arch user, coming off a basic Gentoo install - like the forums here - everyone seems very helpful!
Pleased with how setting up Arch is going - basic desktop install.  I'm having problems though with the ATI drivers.  I'm trying to get the proprietary driverrs working, and having problems running the aticonfig program.  Here's the problem:
[root@myhost X11]# aticonfig --initial --input=/etc/X11/xorg.conf
Uninitialised file found, configuring.
Using /etc/X11/xorg.conf
Saved back-up to /etc/X11/xorg.conf.original-0
*** glibc detected *** aticonfig: munmap_chunk(): invalid pointer: 0xbfe10c25 ***
Then it prints a backtrace and memory map and aborts:
======= Backtrace: =========
/lib/libc.so.6[0xb7d085e6]
aticonfig[0x805c5c7]
aticonfig[0x805c875]
aticonfig[0x8054528]
aticonfig[0x804985e]
aticonfig[0x80496cb]
/lib/libc.so.6(__libc_start_main+0xe0)[0xb7cb8970]
aticonfig[0x8049601]
======= Memory map: ========
08048000-08067000 r-xp 00000000 08:13 111078 /usr/bin/aticonfig
08067000-0806a000 rw-p 0001e000 08:13 111078 /usr/bin/aticonfig
0806a000-0808b000 rw-p 0806a000 00:00 0 [heap]
b7c95000-b7c96000 rw-p b7c95000 00:00 0
b7c96000-b7c98000 r-xp 00000000 08:13 2366 /lib/libdl-2.6.so
b7c98000-b7c9a000 rw-p 00001000 08:13 2366 /lib/libdl-2.6.so
b7c9a000-b7c9e000 r-xp 00000000 08:13 32630 /usr/lib/libXdmcp.so.6.0.0
b7c9e000-b7c9f000 rw-p 00003000 08:13 32630 /usr/lib/libXdmcp.so.6.0.0
b7c9f000-b7ca1000 r-xp 00000000 08:13 32611 /usr/lib/libXau.so.6.0.0
b7ca1000-b7ca2000 rw-p 00001000 08:13 32611 /usr/lib/libXau.so.6.0.0
b7ca2000-b7ca3000 rw-p b7ca2000 00:00 0
b7ca3000-b7dcd000 r-xp 00000000 08:13 2355 /lib/libc-2.6.so
b7dcd000-b7dce000 r--p 0012a000 08:13 2355 /lib/libc-2.6.so
b7dce000-b7dd0000 rw-p 0012b000 08:13 2355 /lib/libc-2.6.so
b7dd0000-b7dd3000 rw-p b7dd0000 00:00 0
b7dd3000-b7df5000 r-xp 00000000 08:13 2344 /lib/libm-2.6.so
b7df5000-b7df7000 rw-p 00021000 08:13 2344 /lib/libm-2.6.so
b7df7000-b7edf000 r-xp 00000000 08:13 32950 /usr/lib/libX11.so.6.2.0
b7edf000-b7ee3000 rw-p 000e7000 08:13 32950 /usr/lib/libX11.so.6.2.0
b7ee3000-b7ef0000 r-xp 00000000 08:13 33724 /usr/lib/libXext.so.6.4.0
b7ef0000-b7ef1000 rw-p 0000c000 08:13 33724 /usr/lib/libXext.so.6.4.0
b7ef1000-b7ef8000 r-xp 00000000 08:13 34374 /usr/lib/libXrender.so.1.3.0
b7ef8000-b7ef9000 rw-p 00006000 08:13 34374 /usr/lib/libXrender.so.1.3.0
b7ef9000-b7efe000 r-xp 00000000 08:13 35188 /usr/lib/libXrandr.so.2.1.0
b7efe000-b7eff000 rw-p 00004000 08:13 35188 /usr/lib/libXrandr.so.2.1.0
b7eff000-b7f00000 rw-p b7eff000 00:00 0
b7f0a000-b7f14000 r-xp 00000000 08:13 8375 /usr/lib/libgcc_s.so.1
b7f14000-b7f15000 rw-p 00009000 08:13 8375 /usr/lib/libgcc_s.so.1
b7f15000-b7f16000 rw-p b7f15000 00:00 0
b7f16000-b7f17000 r-xp b7f16000 00:00 0 [vdso]
b7f17000-b7f31000 r-xp 00000000 08:13 2328 /lib/ld-2.6.so
b7f31000-b7f32000 r--p 00019000 08:13 2328 /lib/ld-2.6.so
b7f32000-b7f33000 rw-p 0001a000 08:13 2328 /lib/ld-2.6.so
bfdfc000-bfe12000 rw-p bfdfc000 00:00 0 [stack]
Aborted
I haven't been able to find much on this invalid pointer problem - any suggestions?  Below is my original xorg.conf:
Regards,
Mike
# 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(5) 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 "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/share/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/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
# FontPath "/usr/share/fonts/TTF"
# FontPath "/usr/share/fonts/Type1"
# FontPath "/usr/lib/X11/fonts/local/"
# FontPath "/usr/lib/X11/fonts/misc/"
# FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/Speedo/"
# FontPath "/usr/lib/X11/fonts/Type1/"
# FontPath "/usr/lib/X11/fonts/TrueType/"
# FontPath "/usr/lib/X11/fonts/freefont/"
# FontPath "/usr/lib/X11/fonts/75dpi/"
# FontPath "/usr/lib/X11/fonts/100dpi/"
# The module search path. The default path is shown here.
# ModulePath "/usr/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 <Ctrl><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 <Ctrl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Ctrl><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" "pc104"
Option "XkbLayout" "us"
EndSection
# Core Pointer's InputDevice section
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto" # Auto detect
Option "Device" "/dev/input/mice"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7. Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.
Option "ZAxisMapping" "4 5 6 7"
# Emulate3Buttons is an option for 2-button 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 - 64.3
# 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 "* Generic VESA compatible"
Driver "vesa"
#VideoRam 131072
# 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 "* Generic VESA compatible"
Monitor "My Monitor"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024" "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

Tried hwd -xa, here's the xorg.conf it generated.  Didn't work - went to black, blank screen when it went to KDM at startup.  Thoughts?  Did I do something wrong changing the driver?  I modprobe'd fglrx, I get no output - normal?
Section "ServerLayout"
Identifier "Xorg Configured"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "PS/2 Mouse" "CorePointer"
# Serial Mouse not detected
# USB Mouse not detected
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail" "true"
EndSection
Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc:unscaled"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/PEX"
# Additional fonts: Locale, Gimp, TTF...
FontPath "/usr/share/fonts/cyrillic"
# FontPath "/usr/share/lib/X11/fonts/latin2/75dpi"
# FontPath "/usr/share/lib/X11/fonts/latin2/100dpi"
# True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/ttf/western"
FontPath "/usr/share/fonts/ttf/decoratives"
FontPath "/usr/share/fonts/truetype"
FontPath "/usr/share/fonts/truetype/openoffice"
FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
FontPath "/usr/share/fonts/latex-ttf-fonts"
FontPath "/usr/share/fonts/defoma/CID"
FontPath "/usr/share/fonts/defoma/TrueType"
EndSection
Section "Module"
Load "ddc" # ddc probing of monitor
Load "dbe"
Load "dri"
Load "extmod"
Load "glx"
Load "bitmap" # bitmap-fonts
Load "type1"
Load "freetype"
Load "record"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" ""
Option "XkbVariant" ""
EndSection
Section "InputDevice"
Identifier "Serial Mouse"
Driver "mouse"
Option "Protocol" "Microsoft"
Option "Device" "/dev/ttyS0"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "PS/2 Mouse"
Driver "mouse"
Option "Protocol" "auto"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "USB Mouse"
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "SendCoreEvents" "true"
Option "Protocol" "IMPS/2"
Option "ZAxisMapping" "4 5"
Option "Buttons" "5"
EndSection
# Auto-generated by Archie mkxcfg
Section "Monitor"
Identifier "Monitor0"
Option "DPMS" "true"
# HorizSync 28.0 - 78.0 # Warning: This may fry very old Monitors
HorizSync 28.0 - 96.0 # Warning: This may fry old Monitors
VertRefresh 50.0 - 75.0 # Very conservative. May flicker.
# VertRefresh 50.0 - 62.0 # Extreme conservative. Will flicker. TFT default.
# Default modes distilled from
# "VESA and Industry Standards and Guide for Computer Display Monitor
# Timing", version 1.0, revision 0.8, adopted September 17, 1998.
# $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
# 640x350 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "640x350" 31.5 640 672 736 832 350 382 385 445 +hsync -vsync
# 640x400 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "640x400" 31.5 640 672 736 832 400 401 404 445 -hsync +vsync
# 720x400 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "720x400" 35.5 720 756 828 936 400 401 404 446 -hsync +vsync
# 640x480 @ 60Hz (Industry standard) hsync: 31.5kHz
ModeLine "640x480" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
# 640x480 @ 72Hz (VESA) hsync: 37.9kHz
ModeLine "640x480" 31.5 640 664 704 832 480 489 491 520 -hsync -vsync
# 640x480 @ 75Hz (VESA) hsync: 37.5kHz
ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -hsync -vsync
# 640x480 @ 85Hz (VESA) hsync: 43.3kHz
ModeLine "640x480" 36.0 640 696 752 832 480 481 484 509 -hsync -vsync
# 800x600 @ 56Hz (VESA) hsync: 35.2kHz
ModeLine "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
# 800x600 @ 60Hz (VESA) hsync: 37.9kHz
ModeLine "800x600" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
# 800x600 @ 72Hz (VESA) hsync: 48.1kHz
ModeLine "800x600" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
# 800x600 @ 75Hz (VESA) hsync: 46.9kHz
ModeLine "800x600" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
# 800x600 @ 85Hz (VESA) hsync: 53.7kHz
ModeLine "800x600" 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync
# 1024x768i @ 43Hz (industry standard) hsync: 35.5kHz
ModeLine "1024x768" 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync Interlace
# 1024x768 @ 60Hz (VESA) hsync: 48.4kHz
ModeLine "1024x768" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
# 1024x768 @ 70Hz (VESA) hsync: 56.5kHz
ModeLine "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
# 1024x768 @ 75Hz (VESA) hsync: 60.0kHz
ModeLine "1024x768" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
# 1024x768 @ 85Hz (VESA) hsync: 68.7kHz
ModeLine "1024x768" 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
# 1152x864 @ 75Hz (VESA) hsync: 67.5kHz
ModeLine "1152x864" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
# 1280x960 @ 60Hz (VESA) hsync: 60.0kHz
ModeLine "1280x960" 108.0 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync
# 1280x960 @ 85Hz (VESA) hsync: 85.9kHz
ModeLine "1280x960" 148.5 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync
# 1280x1024 @ 60Hz (VESA) hsync: 64.0kHz
ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
# 1280x1024 @ 75Hz (VESA) hsync: 80.0kHz
ModeLine "1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
# 1280x1024 @ 85Hz (VESA) hsync: 91.1kHz
ModeLine "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
# 1600x1200 @ 60Hz (VESA) hsync: 75.0kHz
ModeLine "1600x1200" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 65Hz (VESA) hsync: 81.3kHz
ModeLine "1600x1200" 175.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 70Hz (VESA) hsync: 87.5kHz
ModeLine "1600x1200" 189.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 75Hz (VESA) hsync: 93.8kHz
ModeLine "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 85Hz (VESA) hsync: 106.3kHz
ModeLine "1600x1200" 229.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1792x1344 @ 60Hz (VESA) hsync: 83.6kHz
ModeLine "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
# 1792x1344 @ 75Hz (VESA) hsync: 106.3kHz
ModeLine "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
# 1856x1392 @ 60Hz (VESA) hsync: 86.3kHz
ModeLine "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
# 1856x1392 @ 75Hz (VESA) hsync: 112.5kHz
ModeLine "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
# 1920x1440 @ 60Hz (VESA) hsync: 90.0kHz
ModeLine "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
# 1920x1440 @ 75Hz (VESA) hsync: 112.5kHz
ModeLine "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
# Additional modelines
ModeLine "1800x1440" 230 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
ModeLine "1800x1440" 250 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
# Extended modelines with GTF timings
# 640x480 @ 100.00 Hz (GTF) hsync: 50.90 kHz; pclk: 43.16 MHz
ModeLine "640x480" 43.16 640 680 744 848 480 481 484 509 -HSync +Vsync
# 768x576 @ 60.00 Hz (GTF) hsync: 35.82 kHz; pclk: 34.96 MHz
ModeLine "768x576" 34.96 768 792 872 976 576 577 580 597 -HSync +Vsync
# 768x576 @ 72.00 Hz (GTF) hsync: 43.27 kHz; pclk: 42.93 MHz
ModeLine "768x576" 42.93 768 800 880 992 576 577 580 601 -HSync +Vsync
# 768x576 @ 75.00 Hz (GTF) hsync: 45.15 kHz; pclk: 45.51 MHz
ModeLine "768x576" 45.51 768 808 888 1008 576 577 580 602 -HSync +Vsync
# 768x576 @ 85.00 Hz (GTF) hsync: 51.42 kHz; pclk: 51.84 MHz
ModeLine "768x576" 51.84 768 808 888 1008 576 577 580 605 -HSync +Vsync
# 768x576 @ 100.00 Hz (GTF) hsync: 61.10 kHz; pclk: 62.57 MHz
ModeLine "768x576" 62.57 768 816 896 1024 576 577 580 611 -HSync +Vsync
# 800x600 @ 100.00 Hz (GTF) hsync: 63.60 kHz; pclk: 68.18 MHz
ModeLine "800x600" 68.18 800 848 936 1072 600 601 604 636 -HSync +Vsync
# 1024x768 @ 100.00 Hz (GTF) hsync: 81.40 kHz; pclk: 113.31 MHz
ModeLine "1024x768" 113.31 1024 1096 1208 1392 768 769 772 814 -HSync +Vsync
# 1152x864 @ 60.00 Hz (GTF) hsync: 53.70 kHz; pclk: 81.62 MHz
ModeLine "1152x864" 81.62 1152 1216 1336 1520 864 865 868 895 -HSync +Vsync
# 1152x864 @ 85.00 Hz (GTF) hsync: 77.10 kHz; pclk: 119.65 MHz
ModeLine "1152x864" 119.65 1152 1224 1352 1552 864 865 868 907 -HSync +Vsync
# 1152x864 @ 100.00 Hz (GTF) hsync: 91.50 kHz; pclk: 143.47 MHz
ModeLine "1152x864" 143.47 1152 1232 1360 1568 864 865 868 915 -HSync +Vsync
# 1280x960 @ 72.00 Hz (GTF) hsync: 72.07 kHz; pclk: 124.54 MHz
ModeLine "1280x960" 124.54 1280 1368 1504 1728 960 961 964 1001 -HSync +Vsync
# 1280x960 @ 75.00 Hz (GTF) hsync: 75.15 kHz; pclk: 129.86 MHz
ModeLine "1280x960" 129.86 1280 1368 1504 1728 960 961 964 1002 -HSync +Vsync
# 1280x960 @ 100.00 Hz (GTF) hsync: 101.70 kHz; pclk: 178.99 MHz
ModeLine "1280x960" 178.99 1280 1376 1520 1760 960 961 964 1017 -HSync +Vsync
# 1280x1024 @ 100.00 Hz (GTF) hsync: 108.50 kHz; pclk: 190.96 MHz
ModeLine "1280x1024" 190.96 1280 1376 1520 1760 1024 1025 1028 1085 -HSync +Vsync
# 1400x1050 @ 60.00 Hz (GTF) hsync: 65.22 kHz; pclk: 122.61 MHz
ModeLine "1400x1050" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -HSync +Vsync
# 1400x1050 @ 72.00 Hz (GTF) hsync: 78.77 kHz; pclk: 149.34 MHz
ModeLine "1400x1050" 149.34 1400 1496 1648 1896 1050 1051 1054 1094 -HSync +Vsync
# 1400x1050 @ 75.00 Hz (GTF) hsync: 82.20 kHz; pclk: 155.85 MHz
ModeLine "1400x1050" 155.85 1400 1496 1648 1896 1050 1051 1054 1096 -HSync +Vsync
# 1400x1050 @ 85.00 Hz (GTF) hsync: 93.76 kHz; pclk: 179.26 MHz
ModeLine "1400x1050" 179.26 1400 1504 1656 1912 1050 1051 1054 1103 -HSync +Vsync
# 1400x1050 @ 100.00 Hz (GTF) hsync: 111.20 kHz; pclk: 214.39 MHz
ModeLine "1400x1050" 214.39 1400 1512 1664 1928 1050 1051 1054 1112 -HSync +Vsync
# 1600x1200 @ 100.00 Hz (GTF) hsync: 127.10 kHz; pclk: 280.64 MHz
ModeLine "1600x1200" 280.64 1600 1728 1904 2208 1200 1201 1204 1271 -HSync +Vsync
EndSection
# Auto-generated by Archie mkxcfg
Section "Device"
Identifier "Card0"
Driver "fglrx"
VendorName "All"
BoardName "All"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultColorDepth 16
SubSection "Display"
Depth 1
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "DRI"
Mode 0666
EndSection

Similar Messages

  • [SOLVED]Problem installing ATI catalyst drivers

    Hello arch users, ive been having trouble when installing the ati proprietary drivers through pacman. I followed the wiki and added the catalyst repo into my pacman.conf file. however when i type in sudo pacman -Syu i get this:
    :: Synchronizing package databases...
    error: failed retrieving file 'catalyst.db' from catalyst.apocalypsus.net : The requested URL returned error: 404
    error: failed to update catalyst (download library error)
    core is up to date
    extra is up to date
    community is up to date
    multilib is up to date
    :: Starting full system upgrade...
    there is nothing to do
    and when i try to install catalyst and catalyst-utils i get this as an output:
    resolving dependencies...
    looking for inter-conflicts...
    :: catalyst-utils and libgl are in conflict. Remove libgl? [y/N] y
    :: catalyst and ati-dri are in conflict. Remove ati-dri? [y/N] y
    Targets (6): ati-dri-8.0.4-1 [removal] libgl-8.0.4-1 [removal]
    netkit-bsd-finger-0.17-7 xinetd-2.3.15-2 catalyst-12.6-3
    catalyst-utils-12.6-1
    Total Installed Size: 121.91 MiB
    Net Upgrade Size: 74.13 MiB
    Proceed with installation? [Y/n] y
    (4/4) checking package integrity [######################] 100%
    error: catalyst-utils: signature from "Vi0L0 <[email protected]>" is unknown trust
    error: catalyst: signature from "Vi0L0 <[email protected]>" is unknown trust
    error: failed to commit transaction (invalid or corrupted package (PGP signature))
    Errors occurred, no packages were upgraded.
    any idea on what to do?
    i want to use the proprietary over the open source because it gives me less problems when using 3d rendering.
    or are there any other ways of installing these packages other than pacman?
    Last edited by CokaBear (2012-07-19 19:45:35)

    You could add 'SigLevel = Never' under the catalyst repo in pacman.conf, so that it doesn't check for package integrity.
    And about the 404, maybe your 'Server' is incorrect. I use 'Server = http://catalyst.apocalypsus.net/repo/catalyst/$arch'

  • Can't Install ATI Video Drivers on Bootcamp with Windows 7 64-bit

    I've just installed Windows 7 64-bit under Bootcamp but can't seem to get any ATI Graphics drivers to install. I ran into the common blank-screen problem during installation and temporarily solved that by deleting atikmdag.sys from within Lion. At the moment W7 runs with 640x800 resolution (pretty chunky on a 27" screen!). The ATI Catalyst software just doesn't run at all (i.e click on it and nothing happens). I've used DriverSweeper to force remove all drivers and start again but every time I reboot, Windows automatically reinstalls the default driver that seems to be causing the problem in the first place!
    For reference, here are iMac specs:
    iMac 27" w/ OS X Lion 10.7.2
    2.8Ghz Intel Core i7
    4GB 1067Mhz DDR3 RAM
    ATI Radeon HD 4850 512MB GDDR3
    Any ideas?
    Thanks

    gets asked 100s of times, daily too. check my profile bookmarks for "AMD" thread(s).

  • ATI Radeon X1600 GPU problem

    I purchased a MacBook Pro with an ATI Radeon X1600 GPU in 2006. Several weeks ago the GPU failed and I was advised that a replacement logic board was needed and this would cost upwards of £500 by various Apple authorised repair centres that I contacted.
    The system is not worth £500 in working condition.
    It appears that I am not the only one that has found this issue, long after the warranty on the system had expired. In addition a number of people have began on online petition to raise awareness of the situation.
    Several months ago a more recent MacBook Pro (circa 2008) with an NVIDIA GPU failed and I was able to have the logic board replaced for free as this was a known fault, even though my system was out of warranty.
    I was very annoyed to find that the hardware defect in ATI GPU's has not resulted in the same replacement program. I therefore had to pay an engineer to attempt to fix the system through a component level repair, which failed. My 4 year old system that cost me a lot of money is now dead.
    I expected a lot more longevity from this system, and I am sorely disappointed. I am feeling a little ripped off.
    I am the current of owner of a iPhone 4 (2010), MacBook Pro 13" (2010), iMac (2010), iPhone 3G (2008), MacBook Pro 15" (2008) and one dead MacBook Pro 15" (2006).
    As you can see I have spent a lot of money on Apple products and accessories, My very first purchase has now died due to ATI GPU failure and I have already replaced a logic board on a 2008 system due to an NVIDIA GPU failure.
    I have never hesitated to recommend Apple products before, until now!
    I'd like Apple to acknowledge this issue and offer customers with the faulty hardware replacement logic boards, I'd expect Apple to recover this cost from ATI who manufactured the faulty hardware.
    I hope that this post serves to raise awareness of the issue and prompts an appropriate response.
    Thanks for reading.
    Dave.

    Your instructions basically work because you're deleting the ATI display drivers, so OS X defaults to no hardware acceleration. In the very long "display anomalies" thread to which you linked, this seems to be related as a pretty common solution.
    This is not a solution IMO. It's basically telling your computer not to use the built-in video card for much more than a frame buffer. Why is this a bad thing? Well, while it eliminates the anomalies and inevitable freezing, it also makes your computer unusable for anything requiring hardware acceleration (which is a lot of things these days, including 3d games and HD video playback, though the latter can still work albeit more slowly).
    You claim that the problem is due to bugs in the ATI driver, but there are two issues with that theory: 1. the problem also happens under Windows via Boot Camp, using several different versions of ATI's Catalyst drivers that support the R500 family (which the X1600 is a member of); and 2. these sorts of anomalies tend to be usually indicative of hardware failure. For example, the nvidia 8800 series famously had similar issues (more and more graphical anomalies followed by eventual lock-ups), which were ultimately caused by hardware failure relating from many heat cycles.
    In this case, the thing that seems closest to the truth to me came in a forum post over at the WoW forums (see the last post, by member "Flloyd"):
    Flloyd's post
    (Linking to the Google cache because the original seems to have been deleted.)
    Quoting the relevant part here:
    "There has been a lot of discussion an Apple forums and other forums about these issues with the Core Duo (not Core 2 Duo) version 1.1 MBPs with the x1600 GPU. The general consensus is that it is definitely a hardware problem and someone mentioned that Apple knows internally that it is an issue with the solder connection between BGA packages and the main board. These machines came out right around when manufacturers were just starting to become ROHS compliant, (the standard that forbids the use of solder containing lead in electronics,) and so it is not surprising to me, (having dealt with some similar issues from the point of view of the manufacturer at work,) that these problems are happening. The lead-free solder is much more brittle than the old kind and solder joints that crack after many thermal cycles are a common problem that everyone trying to use the lead-free solder has had to confront. That being said, Apple still needs to fix this, because anyone who bought one of these would have had no expectation of this kind of failure and many would have bought something else if they knew this was a possibility."
    Thus, the little BGA solder balls become worse over time, and when heated enough (i.e. when the GPU load becomes great enough for long enough, which is when people usually report the problems to occur at first), may start to get a bad connection to the logic board, as a result of thermal expansion or lower conductivity or a combination of things.
    Now, I'm not 100% sure that this is the answer, but it seems most plausible to me. The other common explanation for this is that the thermal paste is applied unevenly on the GPU, or that the thermal paste gets old. However, while people report getting fewer anomalies after re-applying thermal paste, the problems usually stick around and once again start to get worse over time. My theory here is that while re-applying thermal paste helps with lowering GPU temps and lowering the frequency of the symptoms, it doesn't solve the underlying issue. You can get the same effect (lower GPU temps) by downloading and using the Fan Control preference pane or downloading and using the smcFanControl application to increase fan speed. Like re-applying thermal paste, this would decrease GPU temps (and thus incidence of graphical anomalies and eventual lock-ups), but not eliminate the problem.
    It's sad that Apple doesn't (and likely won't) acknowledge this problem as a hardware defect. As far as I know, the issue manifests itself only after several years of use, which is when warranty (even AppleCare) has run out. Those who are lucky enough to have had the Macbook under warranty when symptoms first appeared just had their logic boards replaced for free, and later reported the same problems appearing after a few years with the new logic boards (which predictably contained the same hardware flaw). As I've said before, I'm not 100% confident in this particular explanation, but I am 100% confident that it's a hardware issue.
    So nowadays, people generally have the choice of either buying a new laptop or forking over $300-600 for a new or used logic board to extend the life of the Macbook for a few more years, which would inevitably fail again. There is hope though: the aforementioned nvidia cards (the GeForce 8800 series) with the hardware flaw were eventually recalled and replaced for free, but a lot of people have reported resurrecting their dead cards using this unorthodox method:
    http://hardforum.com/showthread.php?t=1421792
    http://hardforum.com/showthread.php?t=1553073
    http://hardforum.com/showthread.php?t=1470144
    The same method also worked for people with different failing cards (even built-in laptop GPUs, such as we are talking about here), and not just the GeForce 8800 series. I might try this out in a week or so and see if it works for me and report back. I just don't know if it's worth it -- this is my primary work laptop and I can't afford to have to mess around with getting a new one in the middle of the school year if it dies in the process. Not to mention the fact that while the problem certainly is annoying, since I have to save my work every few minutes in anticipation of the computer locking up, it's certainly not critical.
    <URL Embedded by Host>

  • Probs with ATI Catalysts Drivers

    I’m currently using ATI Catalyst Drivers 6.14.10.6404 (3.9) for my ATI Radeon 9600xt.
    If I upgrade to the latest ATI or Omega Drivers (4.7 I think), my card crashes and is very unstable.
    my current graphics settings are:
    enabled VPU recover
    fast write is on
    AGPx8
    Why does 3.9 work and 4.7 not work, I have only had this problem since changing to this board.
    Any help appreciated.

    Well I hope it works for you engrrowl!  I was installing a slipstreamed version of XP with SP2.  But that sure didn't help me.  I would randomly have my screen corrupt with my 9700.  And that stupid card has given me headaches since I got an LCD.  So driver incompatibility used to make my screen go black all the time.  It would then revert to normal (maybe!).  But there were many times I had to shutdown by the keyboard and disconnect the DVI cable to get it to work again.  And the LCD is a Samsung so it's not cheap.
    I broke down the other night and when I had to reinstall WinXP from scratch I reverted to an older GF4.  This morning I ordered a Geforce 6800, and it will "upgrade" fine.  But if I tried to go from an ATI to an Nvidia I would have had to reload my OS again.    So it worked out for me.
    But it's strange that switching video cards solved all my "issues".  That and the fact that I've never really like ATI's drivers means I will never get another of their cards.  

  • Bootcamp 3.2 on my iMac 27", OSX 10.6 machine - but my ATI Graphic Drivers installation is failing.

    I'm setting Bootcamp 3.2 on my iMac 27", OSX 10.6 machine - but my ATI Graphic Drivers installation is failing.
    i get the message: "setup did not find a driver compatible with your current hardware or operating system., Setup will now exit."
    i think it's having problems "Extracting setup.exe" - i get the message "Cannot create setup.exe" and "Cannot create data1.cab"
    help!

    You're welcome.
    Thanks for the points.
    10 points for your solution!

  • IMac Intel Core Duo and ATI Video Drivers

    I was wondering if the latest ATI Catalyst drivers are compatible with the X1600 that comes in the Intel Core DUO iMacs. I wasn't sure if the driver needed to come from apple or not

    Nope. The latest Catalyst drivers 6.X are not compatible with the iMac vid card. You need the driver on the disc that Bootcamp install creates. It's a ver 8.x driver made especially for our Radeon Mobility x1600's.

  • Audio Config" problem after upgrading to 7.6

    I have only had my ipod one week. It is working beautifully. My problem is that I can no longer charge it or add songs to it because I can not open itunes. The previous version worked beautifully on my computer. After I upgraded to 7.6, it stopped working and I get an Audio Config. problem everytime I try to open it. I have tried uninstalling and reinstalling the program but it does not help. What do I need to do to fix this problem?

    I have had my ipod a few weeks - but have nothing but problems letting itunes run the syncing, sometime it works and sometimes it does not. I had to reset my ipod 2 times already just to keep song on here, should have gone with Zune or Sonys (what my wife has) they are not having a single issue...
    I would like to add my voice to his - I upgraded to 7.6, it stopped working and I get an Audio Config. problem everytime I try to open it. I have tried uninstalling and reinstalling the program but it does not help. What do I need to do to fix this problem ! ! ! ! ?

  • 27in iMac (late 2009) ATI 4850 drivers problem in Windows 7

    This iMac is less than a month old. Windows 7 was working fine until a couple of days ago. While at the Windows 7 desktop the screen pixlated and froze. A tip bubble appeared in the notification bar that said the ATI driver quit but was recovered. The screen went black then restored itself. A moment later the whole thing occurred again. Is this a known issue? Is there a fix? Thanks for any help.

    BANDING AND DRIVER CRASHING SOLVED:
    I bought the following iMac on April 18, 2010 to run Windows 7 and Autodesk REVIT 2011.
    27" iMac (Late 2009)
    Intel Core i7, quad-core, 2.8GHz
    8GB (4x2GB) memory
    1TB Hard Drive
    ATI Radeon HD 4850 512MB Display Adapter
    Apple Magic Mouse
    Apple Wireless Keyboard
    Apple BootCamp with Windows 7 Ultimate
    Installed OSX, downloaded and installed all updates.
    Installed BootCamp 3.1
    Installed Windows 7 Ultimate 64bit and had the problem of the black screen during install. This was solved with the fix from apple support (copy latest drivers to a flash drive and continue to install windows). This resulted in apple windows driver 8.681.0.0 and the 16 bit color with banding. Rolled back the driver to 8.661.0.0. The banding issue was solved, but then had intermittent crashing (reset of the driver) in Chrome and REVIT 2011. This driver caused yellow "dots", then lockup and generally would reset. Very disruptive to REVIT.
    SOLUTION:
    Went to ATI website and downloaded Catalyst 10.4, then manually installed ATI Mobility Radeon HD 4850 display driver version 8.723.0.0. This display driver has 32 bit color, does NOT exhibit the color banding and has not had screen flicker, driver resets, or crashing in any programs run so far. I use this computer only for Autodesk REVIT 2011. The ATI HD 4850 is not officially supported by Autodesk, but I am able to run REVIT 2011 with hardware acceleration and anti-aliasing with no problems. So far that has been only for one day, but was not able to go more than a few minutes with the previous drivers.
    I have not run any speed benchmarks yet, but compared to my Windows 32 bit XP machine, the performance is much improved.

  • ATI Radeon drivers problems (both open-source and proprietary)

    Hi 2 All!!
    I have a problem with my ATI Radeon 9000-series. The open source drivers (xf86-video-ati) don't work very good for me, my monitor's fresh rate isn't "at-top" and the monitor projection is slightly translated to the right (say 8-12 pixels). So I've tried to build the official drivers with ABS, all is gone successfully, except for some worrying warnings, but I thought that it's normal. I have a customized kernel, build through ABS... So, when I've tried to load the fglrx module it says:
    # modprobe fglrx
    FATAL: Error inserting fglrx (/lib/modules/2.6.27-ARCH/video/fglrx.ko): Cannot allocate memory
    Please, help me! My machine is slow, I can't run any OpenGL-accelerated application, even Quake III!!! If you can suggest me how to improve the performance and how to resolve problems with open-source drivers, it also would be very good... Thank you and sorry for my poor English please.

    I had some problems with installing ATI drivers recently (could not build fglrx module, not even manually, I had to change some installation script), but with latest driver version (8.11 I think) from ati.amd.com was everything fine (I have Radeon 9600 Pro)
    Try to do this (and write here the output)
    glxinfo | grep vendor
    fglrxinfo
    In both cases, it should write something like OpenGL...: ATI... if there will be MESA or DRI, that means that you don't have loaded your fglrx module.
    If fglrxinfo output will be something like: no permission for...(should be first or second line of the output), then write this somewhere in your xorg.conf:
       Section "DRI"
           Mode 0666
       EndSection
    run:
    modprobe -a fglrx - and give here the output. If there will be none, run:
    lsmod | grep fglrx - to see wheter fglrx module is really loaded in kernel
    if you will have no module, you can install one, type:
    cd /lib/modules/fglrx/build_mod
    sh make.sh
    cd ../
    sh make_install.sh (as root)
    and post any warning or error here at forum, drivers (but not fglrx module) are installed at /usr/share/ati
    After installing drivers, you also need to configure your system (notice your system that it's there), commands:
    aticonfig --initial (for editing your xorg.conf)
    aticonfig --overlay-type=Xv (acceleration support in xorg.conf)
    Showing your xorg.conf file here is also good idea, here is mine (sections Device and Screen):
    Section "Device"
        #VideoRam    262144
        # Insert Clocks lines here if appropriate
        Identifier  "** ATI Radeon (generic)               [radeon]"
        Driver      "radeon"
    EndSection
    Section "Device"
        Identifier  "aticonfig-Device[0]-0"
        Driver      "fglrx"
        Option        "VideoOverlay" "on"
        Option        "OpenGLOverlay" "off"
        BusID       "PCI:1:0:0"
    EndSection
    Section "Screen"
        Identifier "Screen 1"
        Device     "** ATI Radeon (generic)               [radeon]"
        Monitor    "My Monitor"
        DefaultDepth     24
        SubSection "Display"
            Viewport   0 0
            Depth     8
            Modes    "1280x1024" "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
            Viewport   0 0
            Depth     16
            Modes    "1280x1024" "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
            Viewport   0 0
            Depth     24
            Modes    "1280x1024" "1024x768" "800x600" "640x480"
        EndSubSection
    EndSection
    Section "Screen"
        Identifier "aticonfig-Screen[0]-0"
        Device     "aticonfig-Device[0]-0"
        Monitor    "aticonfig-Monitor[0]-0"
        DefaultDepth     24
        SubSection "Display"
            Viewport   0 0
            Depth     24
        EndSubSection
    EndSection

  • ATI drivers config - help

    Hi!
    I am Arch user still and I please for one ''fish'' more.
    Today I reinstall ARCH (testing repo is now commented). I want to install ATI drivers. I know that they have aticonfig now. I did on Xorg 7.0 but I had a problem with fglrx - didn't work.
    My card is Radeon 9000 (r250). For Xorg 6.8 and Mesa drivers works fine.
    Could someone who has the same card help me, please with his/her xorg.conf.
    Thanks in advance,
    Mitja

    I Installed Xorg 7.0 (works) and I installed ATI drivers and doesn't work.
    In xorg.conf I have :
    Section "Module"
    Load "ddc"
    Load "GLcore"
    Load "dbe"
    Load "dri"
    Load "extmod"
    Load "glx"
    Load "bitmap" # bitmap-fonts
    Load "type1"
    Load "freetype"
    Load "record"
    EndSection
    Section "Device"
    Identifier "Card0"
    Driver "fglrx"
    #Option "NoDDC"
    Option "no_accel" "no"
    Option "no_dri" "no"
    Option "mtrr" "off" # disable DRI mtrr mapper, driver has its own code for mtrr
    Option "DesktopSetup" "(null)"
    Option "ScreenOverlap" "0"
    Option "TVFormat" "NTSC-M"
    Option "TVStandard" "VIDEO"
    Option "TVHSizeAdj" "0"
    Option "TVVSizeAdj" "0"
    Option "TVHPosAdj" "0"
    Option "TVVPosAdj" "0"
    Option "TVHStartAdj" "0"
    Option "TVColorAdj" "0"
    Option "GammaCorrectionI" "0x00000000"
    Option "GammaCorrectionII" "0x00000000"
    Option "Capabilities" "0x00000000"
    Option "CapabilitiesEx" "0x00000000"
    Option "VideoOverlay" "on"
    Option "OpenGLOverlay" "off"
    Option "CenterMode" "off"
    Option "PseudoColorVisuals" "off"
    Option "Stereo" "off"
    Option "StereoSyncEnable" "1"
    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"
    Option "UseFastTLS" "0"
    Option "BlockSignalsOnLock" "on"
    Option "UseInternalAGPGART" "no"
    Option "ForceGenericCPU" "no"
    BusID "PCI:1:0:0" # vendor=1002, device=4152
    Screen 0
    EndSection
    In the Xorg.log I have also:
    (II) fglrx(0): Kernel Module Version Information:
    (II) fglrx(0): Name: radeon
    (II) fglrx(0): Version: 1.19.0
    (II) fglrx(0): Date: 20050911
    (II) fglrx(0): Desc: ATI Radeon
    (WW) fglrx(0): Kernel Module version does *not* match driver.
    (EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work
    (II) fglrx(0): [drm] removed 1 reserved context for kernel
    (II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0xe0f5d000 at 0xb7666000
    (WW) fglrx(0): ***********************************************
    (WW) fglrx(0): * DRI initialization failed! *
    (WW) fglrx(0): * (maybe driver kernel module missing or bad) *
    (WW) fglrx(0): * 2D acceleraton available (MMIO) *
    (WW) fglrx(0): * no 3D acceleration available *
    ...and fglrx info show:
    glrxinfo
    display: :0.0 screen: 0
    OpenGL vendor string: Mesa project: www.mesa3d.org
    OpenGL renderer string: Mesa GLX Indirect
    OpenGL version string: 1.2 (1.5 Mesa 6.4.1
    I don't know what I am doing wrong...
    Mitja

  • Problems with Ati Propietary drivers, Yaourt

    Im an ubuntu refugee and a nub-zilla i will try to include as much information as possible and hope fuly get some help. Thanks in advance!
    Arch x86_64
    I am attempting to install the propietary ati drivers using yaourt from aur
    I have base and base-devel installed (notsure if that matters)
    to find it i issed th command: yaourt catalyst-utils
    the first option is the one i attempt to install
    yaourt -S /aur/catalyst-utils 9.8-1
    everything goes smoothly until the very end
    "Finished making: catalyst 9.8-1 x86_64"
    "Continue installing catalyst utils? [Y/n]
    y
    Password
    "loading package data..."
    "checking dependencies..."
    "error: replacing packages with -U is not supported yet"
    "error: you can replace packages manually using -Rd and -U"
    "error: failed to prepare transaction (conflicting dependencies)"
    ": : catalyst-utils: conflicts with libgl"
    ==>WARNING: You package is saved in blah blah blah
    any suggestions as to how to get this working would be amazingly helpful, im such a nub that im not sure which part of all of this information is useful
    anyway thanks again!

    I have another problem. I install everything properly, reboot my system and dmesg shows fglrx has loaded fine (added it to rc.conf). But when I startx my monitor is left black and my system unresponsive. Cannot get a log for this attempt of x session (not even with startx > xlog). And following the wiki does not solve my problem (it says to delete /etc/ati/amdpcsdb.
    Kernel: 2.6.30-ARCH x86_64
    X: xorg-server 1.6.3.901-1
    Last edited by ldvx (2009-09-12 03:06:08)

  • [SOLVED]Xorg.conf, mouse config problem

    The Rapoo M765 mouse can not work properly under normal mouse configuration.
    The mouse goes beyond controll when config as below:
    hacksign@XSign [14:13:13] : ~
    >> cat /etc/X11/xorg.conf.d/50-mouse-acceleration.conf
    #Section "InputClass"
    # Identifier "Mouse2"
    # MatchProduct "RAPOO RAPOO 2.4G Remote Mouse"
    # MatchIsPointer "yes"
    # MatchDevicePath "/dev/input/event*"
    # Driver "mouse"
    # Option "Protocol" "auto"
    # Option "Emulate3Buttons" "no"
    # Option "Buttons" "7"
    # Option "ButtonMapping" "1 2 3 6 7"
    #EndSection
    When there is no any configuration, the mouse can work abnormally. Movement and right/left click work fine, but I can not use scroll wheel,and the "go forward"&"go backward" mouse key can not work too.
    (I know Option "ZAxisMapping" "4 5" is the configuration of scroll wheel emulation.)
    The real problem is 'mouse beyond controll',the cursor goes crazyly on screen ....
    I guess it is something wrong of ButtonMapping option. But when I tried to get button number from command xev,when scroll wheel scrolles, I get something below(the scroll wheel movement is identified as a key event~):
    //left click
    ButtonPress event, serial 34, synthetic NO, window 0x4a00001,
    root 0x264, subw 0x0, time 3766452, (135,143), root:(2287,595),
    state 0x0, button 1, same_screen YES
    ButtonRelease event, serial 34, synthetic NO, window 0x4a00001,
    root 0x264, subw 0x0, time 3766588, (135,143), root:(2287,595),
    state 0x100, button 1, same_screen YES
    //right click
    ButtonPress event, serial 34, synthetic NO, window 0x4a00001,
    root 0x264, subw 0x0, time 3767716, (135,143), root:(2287,595),
    state 0x0, button 3, same_screen YES
    ButtonRelease event, serial 34, synthetic NO, window 0x4a00001,
    root 0x264, subw 0x0, time 3767852, (135,143), root:(2287,595),
    state 0x400, button 3, same_screen YES
    //mouse scroll, identified as keyboard event(?)
    KeyRelease event, serial 34, synthetic NO, window 0x4a00001,
    root 0x264, subw 0x0, time 3769332, (135,143), root:(2287,595),
    state 0x0, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False
    KeyPress event, serial 34, synthetic NO, window 0x4a00001,
    root 0x264, subw 0x0, time 3769332, (135,143), root:(2287,595),
    state 0x0, keycode 122 (keysym 0x1008ff11, XF86AudioLowerVolume), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False
    here is some Information(I dont know why the mouse is identified as 'type:KEYBOARD'):
    hacksign@XSign [14:55:03] : ~
    >> xinput
    ⎡ Virtual core pointer id=2 [master pointer (3)]
    ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
    ⎜ ↳ RAPOO RAPOO 2.4G Remote Mouse id=13 [slave pointer (2)]
    ⎜ ↳ SynPS/2 Synaptics TouchPad id=15 [slave pointer (2)]
    ⎜ ↳ TPPS/2 IBM TrackPoint id=16 [slave pointer (2)]
    ⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Sleep Button id=8 [slave keyboard (3)]
    ↳ Heng Yu Technology Poker Pro S id=9 [slave keyboard (3)]
    ↳ Heng Yu Technology Poker Pro S id=10 [slave keyboard (3)]
    ↳ Integrated Camera id=11 [slave keyboard (3)]
    ↳ RAPOO RAPOO 2.4G Remote Mouse id=12 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)]
    ↳ ThinkPad Extra Buttons id=17 [slave keyboard (3)]
    hacksign@XSign [14:55:06] : ~
    >> xinput list-props 13
    Device 'RAPOO RAPOO 2.4G Remote Mouse':
    Device Enabled (142): 1
    Coordinate Transformation Matrix (144): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
    Device Accel Profile (270): 0
    Device Accel Constant Deceleration (271): 1.000000
    Device Accel Adaptive Deceleration (272): 1.000000
    Device Accel Velocity Scaling (273): 10.000000
    Device Product ID (260): 9390, 8192
    Device Node (261): "/dev/input/event8"
    Evdev Axis Inversion (274): 0, 0
    Evdev Axes Swap (276): 0
    Axis Labels (277): "Rel X" (152), "Rel Y" (153), "Rel Horiz Wheel" (267), "Rel Dial" (268), "Rel Vert Wheel" (269)
    Button Labels (278): "Button Left" (145), "Button Middle" (146), "Button Right" (147), "Button Wheel Up" (148), "Button Wheel Down" (149), "Button Horiz Wheel Left" (150), "Button Horiz Wheel Right" (151), "Button Side" (265), "Button Extra" (266), "Button Unknown" (263), "Button Unknown" (263), "Button Unknown" (263), "Button Unknown" (263)
    Evdev Scrolling Distance (279): 1, 1, 1
    Evdev Middle Button Emulation (280): 0
    Evdev Middle Button Timeout (281): 50
    Evdev Third Button Emulation (282): 0
    Evdev Third Button Emulation Timeout (283): 1000
    Evdev Third Button Emulation Button (284): 3
    Evdev Third Button Emulation Threshold (285): 20
    Evdev Wheel Emulation (286): 0
    Evdev Wheel Emulation Axes (287): 0, 0, 4, 5
    Evdev Wheel Emulation Inertia (288): 10
    Evdev Wheel Emulation Timeout (289): 200
    Evdev Wheel Emulation Button (290): 4
    Evdev Drag Lock Buttons (291): 0
    hacksign@XSign [14:55:14] : ~
    >> grep -i rapoo /var/log/Xorg.0.log
    [ 29.102] (II) config/udev: Adding input device RAPOO RAPOO 2.4G Remote Mouse (/dev/input/event7)
    [ 29.102] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev keyboard catchall"
    [ 29.102] (II) Using input driver 'evdev' for 'RAPOO RAPOO 2.4G Remote Mouse'
    [ 29.102] (**) RAPOO RAPOO 2.4G Remote Mouse: always reports core events
    [ 29.102] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: Device: "/dev/input/event7"
    [ 29.102] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Vendor 0x24ae Product 0x2000
    [ 29.102] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found keys
    [ 29.102] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as keyboard
    [ 29.102] (II) XINPUT: Adding extended input device "RAPOO RAPOO 2.4G Remote Mouse" (type: KEYBOARD, id 12)
    [ 29.103] (II) config/udev: Adding input device RAPOO RAPOO 2.4G Remote Mouse (/dev/input/event8)
    [ 29.103] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev pointer catchall"
    [ 29.103] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev keyboard catchall"
    [ 29.103] (II) Using input driver 'evdev' for 'RAPOO RAPOO 2.4G Remote Mouse'
    [ 29.103] (**) RAPOO RAPOO 2.4G Remote Mouse: always reports core events
    [ 29.103] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: Device: "/dev/input/event8"
    [ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Vendor 0x24ae Product 0x2000
    [ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found 9 mouse buttons
    [ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found scroll wheel(s)
    [ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found relative axes
    [ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found x and y relative axes
    [ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found absolute axes
    [ 29.103] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Forcing absolute x/y axes to exist.
    [ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found keys
    [ 29.103] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as mouse
    [ 29.103] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as keyboard
    [ 29.103] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Adding scrollwheel support
    [ 29.103] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: YAxisMapping: buttons 4 and 5
    [ 29.103] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 29.103] (II) XINPUT: Adding extended input device "RAPOO RAPOO 2.4G Remote Mouse" (type: KEYBOARD, id 13)
    [ 29.104] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: initialized for relative axes.
    [ 29.104] (WW) evdev: RAPOO RAPOO 2.4G Remote Mouse: ignoring absolute axes.
    [ 29.104] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) keeping acceleration scheme 1
    [ 29.104] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration profile 0
    [ 29.104] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration factor: 2.000
    [ 29.104] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration threshold: 4
    [ 29.104] (II) config/udev: Adding input device RAPOO RAPOO 2.4G Remote Mouse (/dev/input/mouse0)
    hacksign@XSign [14:59:47] : ~
    >> yaourt -Q|grep -i 'input-'
    local/xf86-input-evdev-trackpoint 2.9.1-1
    extra/xf86-input-keyboard 1.8.0-3 (xorg-drivers xorg)
    extra/xf86-input-mouse 1.9.1-1 (xorg-drivers xorg)
    extra/xf86-input-synaptics 1.8.1-1 (xorg-drivers xorg)
    Last edited by Hacksign (2015-01-14 02:22:51)

    Thanks for reply !
    change Driver 'mouse' to Driver 'evdev',solved cursor goes beyond controll problem.
    but I still can not use scroll button and 'go forward'&'go backward' button.
    (BTW:evdev_drv.so is from local/xf86-input-evdev-trackpoint, and local/xf86-input-evdev-trackpoint package is from AUR)
    I think, maybe something wrong with my button number mapping, but I still can not get scroll button number with 'xev' command....
    below is my configuration:
    hacksign@XSign [17:15:19] : /var/log
    >> cat /etc/X11/xorg.conf.d/50-mouse-acceleration.conf
    Section "InputClass"
    Identifier "Mouse2"
    MatchProduct "RAPOO RAPOO 2.4G Remote Mouse"
    MatchIsPointer "yes"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
    Option "Protocol" "auto"
    Option "Emulate3Buttons" "no"
    Option "ZAxisMapping" "4 5"
    Option "Buttons" "9"
    Option "ButtonMapping" "1 2 3 6 7 8 9 4 5"
    EndSection
    and here is Xorg.0.log
    [ 11357.287] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev keyboard catchall"
    [ 11357.287] (II) Using input driver 'evdev' for 'RAPOO RAPOO 2.4G Remote Mouse'
    [ 11357.287] (**) RAPOO RAPOO 2.4G Remote Mouse: always reports core events
    [ 11357.287] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: Device: "/dev/input/event7"
    [ 11357.287] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Vendor 0x24ae Product 0x2000
    [ 11357.287] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found keys
    [ 11357.287] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as keyboard
    [ 11357.287] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/0003:24AE:2000.0003/input/input8/event7"
    [ 11357.288] (II) XINPUT: Adding extended input device "RAPOO RAPOO 2.4G Remote Mouse" (type: KEYBOARD, id 12)
    [ 11357.288] (**) Option "xkb_rules" "evdev"
    [ 11357.288] (**) Option "xkb_model" "pc104"
    [ 11357.288] (**) Option "xkb_layout" "us"
    [ 11357.288] (II) config/udev: Adding input device RAPOO RAPOO 2.4G Remote Mouse (/dev/input/event8)
    [ 11357.288] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev pointer catchall"
    [ 11357.288] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev keyboard catchall"
    [ 11357.288] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "Mouse2"
    [ 11357.288] (II) Using input driver 'evdev' for 'RAPOO RAPOO 2.4G Remote Mouse'
    [ 11357.288] (**) RAPOO RAPOO 2.4G Remote Mouse: always reports core events
    [ 11357.288] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: Device: "/dev/input/event8"
    [ 11357.288] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: ButtonMapping '1 2 3 6 7 8 9 4 5'
    [ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Vendor 0x24ae Product 0x2000
    [ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found 9 mouse buttons
    [ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found scroll wheel(s)
    [ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found relative axes
    [ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found x and y relative axes
    [ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found absolute axes
    [ 11357.288] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Forcing absolute x/y axes to exist.
    [ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found keys
    [ 11357.288] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as mouse
    [ 11357.288] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as keyboard
    [ 11357.288] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Adding scrollwheel support
    [ 11357.288] (**) Option "Emulate3Buttons" "no"
    [ 11357.288] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: YAxisMapping: buttons 4 and 5
    [ 11357.288] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 11357.288] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.1/0003:24AE:2000.0004/input/input9/event8"
    [ 11357.288] (II) XINPUT: Adding extended input device "RAPOO RAPOO 2.4G Remote Mouse" (type: KEYBOARD, id 13)
    [ 11357.288] (**) Option "xkb_rules" "evdev"
    [ 11357.288] (**) Option "xkb_model" "pc104"
    [ 11357.288] (**) Option "xkb_layout" "us"
    [ 11357.288] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: initialized for relative axes.
    [ 11357.288] (WW) evdev: RAPOO RAPOO 2.4G Remote Mouse: ignoring absolute axes.
    [ 11357.289] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) keeping acceleration scheme 1
    [ 11357.289] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration profile 0
    [ 11357.289] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration factor: 2.000
    [ 11357.289] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration threshold: 4
    [ 11357.289] (II) config/udev: Adding input device RAPOO RAPOO 2.4G Remote Mouse (/dev/input/mouse0)
    [ 11357.289] (II) No input driver specified, ignoring this device.
    [ 11357.289] (II) This device may have been added with another device file.
    olive wrote:In the config file you mentioned, all is commented; do you mean that you have problems when you have uncommented it? You should not use the mouse driver (old deprecated driver) but evdev. Try to remove xf86-input-mouse and xf86-input-keyboard (same as before, this is deprecated and handled by evdev) and remove also a "joystick" driver if you have it (I have had problem with it conflicting with the evdev driver).
    Last edited by Hacksign (2015-01-13 09:27:06)

  • HOW TO: Install LATEST ATI CATALYST drivers

    So ATI/AMD doesn't consistently update the "BootCamp" drivers and as a gamer I want utmost performance out of what I have (of course without OCing). Therefore, I went searching for a solution and found it and I will explain it here, step by step. Forgive me if this has already been posted. Note that I did this in XP and NOT Vista.
    1. Download the latest CATALYST drivers from here:
    http://game.amd.com/us-en/drivers_catalyst.aspx?p=xp/radeonx-xp
    2. Open the driver software as if you were going to install it and let it extract to its default directory. Take note of what that directory is as you will need to know that file path for later. Once it extracts it will move on to an installation. Stop/cancel the installation the first chance you get.
    3. REMOVE your currently installed ATI drivers. There are two ways to do this:
    -1. If you downloaded the actually CATALYST Software Suite, there will be a program in the folder to where it extracted called "AtiCimUn" that will remove your drivers.
    -2. Google "remove ATI drivers" and I think it's the first link that tells you a detailed step by step method of removing the drivers.
    4. Restart after successfully removing the drivers.
    5. Download MobilityModder here: http://www.driverheaven.net/modtool.php
    -If you scroll closer to the bottom of that page, there will be a download link AND instructions for the PROPER method of installing MobilityModder.
    6. Run MobilityModder
    7. Browse to the directory where the drivers are installed.
    8. Click "Modify"
    9. When the modification is complete, close MobilityModder and Right Click on "My Computer" then click on Properties
    10. Click the "Hardware" tab
    11. Click on Device Manager
    12. At least one device should have a yellow circle with a black question mark in it. For me, Windows saw it as a "VGA Controller". Right click it and click "Update Drivers"
    13. It will ask you some stuff about if you want Windows Update to look for drivers, say "No not this time" and click next
    14. Select "Install from a list or specific location{Advanced) and click next
    15. Select "Don't search, I will choose the driver to install"
    16. Click on the "Have Disk" button
    17. Browse to the folder where the ATI drivers were extracted to (MobilityModder will have rewritten the modified files to the same location)
    18. The specific file you are looking for is a Configuration file whose icon looks like a white notepad with a yellowish cog that has some metal rod going through it. Click on it and click "open"
    19. At this point Windows should recognize which card you have specifically, if not, it will have the entire list of cards that driver can update. If you run into that, just find it in the list.
    20. Let windows copy the files, if it tells you that the drivers are not digitally signed, say "continue anyway". It's just an effect of the MobilityModder modifying the files and since it doesn't have a certificate, it's not considered signed.
    21. When it's done click finish.
    22. Restart
    23. Happy new drivers
    I'm thinking you might be able to skip the MobilityModder part and just skip straight to directing Windows right to where the drivers are instead of having to mod the files. I'm not sure if it works because I haven't done it but you're welcome to try. If it doesn't work it just means you have to use MobilityModder.
    I hope this helps.

    Update: After using the method described above the drivers did install successfully however, when I loaded some games I noticed that they did not take up the whole screen. No amount of changing the resolution solved the problem.
    So I completely removed the drivers and loaded unmodified drivers. I had to find my x1600 from the list and there were actually two but I just took the first one. I let Windows copy the files after warning that it can't confirm they were for my hardware. After a restart I tried my games again and they were taking up the whole screen as they did when I had BootCamps outdated drivers.
    So I can say that you CAN skip steps 5-9 (the steps for the mobility modding). You'll just have to find your drivers and some of them do show up multiple times. I'm probably going to try the other x1600 listing just to see what happens. I'm not sure if there's a difference between the same listings (mine was Radeon x1600 followed by another Radeon x1600) but I'm assuming there is or else ATI would put so many >.<

  • StartX Failing With ATI Proprietary Drivers

    I have installed the catalyst legacy drivers, but cannot figure out why they are not working.
    My log from xorg:
    [ 2142.903]
    X.Org X Server 1.12.4
    Release Date: 2012-08-27
    [ 2142.903] X Protocol Version 11, Revision 0
    [ 2142.903] Build Operating System: Linux 3.4.8-1-ARCH x86_64
    [ 2142.903] Current Operating System: Linux arch 3.7.10-1-ARCH #1 SMP PREEMPT Thu Feb 28 09:50:17 CET 2013 x86_64
    [ 2142.903] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=82506866-1d99-427a-abf7-4cfa641b7c26 ro quiet nomodeset
    [ 2142.903] Build Date: 27 August 2012 08:04:39AM
    [ 2142.903]
    [ 2142.903] Current version of pixman: 0.28.2
    [ 2142.903] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 2142.903] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 2142.903] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Mar 8 10:50:35 2013
    [ 2142.903] (==) Using config file: "/etc/X11/xorg.conf"
    [ 2142.903] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 2142.903] (==) ServerLayout "aticonfig Layout"
    [ 2142.903] (**) |-->Screen "aticonfig-Screen[0]-0" (0)
    [ 2142.903] (**) | |-->Monitor "aticonfig-Monitor[0]-0"
    [ 2142.903] (**) | |-->Device "aticonfig-Device[0]-0"
    [ 2142.903] (==) Automatically adding devices
    [ 2142.903] (==) Automatically enabling devices
    [ 2142.903] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 2142.903] Entry deleted from font path.
    [ 2142.903] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 2142.903] Entry deleted from font path.
    [ 2142.903] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/100dpi/,
    /usr/share/fonts/75dpi/
    [ 2142.903] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 2142.903] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 2142.903] (II) Loader magic: 0x7c8b00
    [ 2142.903] (II) Module ABI versions:
    [ 2142.903] X.Org ANSI C Emulation: 0.4
    [ 2142.903] X.Org Video Driver: 12.1
    [ 2142.903] X.Org XInput driver : 16.0
    [ 2142.903] X.Org Server Extension : 6.0
    [ 2142.904] (--) PCI:*(0:2:0:0) 1002:9488:106b:00b6 rev 0, Mem @ 0xc0000000/268435456, 0xd0220000/65536, I/O @ 0x00001000/256, BIOS @ 0x????????/131072
    [ 2142.904] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 2142.904] (II) "extmod" will be loaded by default.
    [ 2142.904] (II) "dbe" will be loaded by default.
    [ 2142.904] (II) "glx" will be loaded by default.
    [ 2142.904] (II) "record" will be loaded by default.
    [ 2142.904] (II) "dri" will be loaded by default.
    [ 2142.904] (II) "dri2" will be loaded by default.
    [ 2142.904] (II) LoadModule: "extmod"
    [ 2142.905] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
    [ 2142.905] (II) Module extmod: vendor="X.Org Foundation"
    [ 2142.905] compiled for 1.12.4, module version = 1.0.0
    [ 2142.905] Module class: X.Org Server Extension
    [ 2142.905] ABI class: X.Org Server Extension, version 6.0
    [ 2142.905] (II) Loading extension MIT-SCREEN-SAVER
    [ 2142.905] (II) Loading extension XFree86-VidModeExtension
    [ 2142.905] (II) Loading extension XFree86-DGA
    [ 2142.905] (II) Loading extension DPMS
    [ 2142.905] (II) Loading extension XVideo
    [ 2142.905] (II) Loading extension XVideo-MotionCompensation
    [ 2142.905] (II) Loading extension X-Resource
    [ 2142.905] (II) LoadModule: "dbe"
    [ 2142.905] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
    [ 2142.905] (II) Module dbe: vendor="X.Org Foundation"
    [ 2142.905] compiled for 1.12.4, module version = 1.0.0
    [ 2142.905] Module class: X.Org Server Extension
    [ 2142.905] ABI class: X.Org Server Extension, version 6.0
    [ 2142.905] (II) Loading extension DOUBLE-BUFFER
    [ 2142.905] (II) LoadModule: "glx"
    [ 2142.905] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 2142.905] (II) Module glx: vendor="Advanced Micro Devices, Inc."
    [ 2142.905] compiled for 6.9.0, module version = 1.0.0
    [ 2142.905] (II) Loading extension GLX
    [ 2142.905] (II) LoadModule: "record"
    [ 2142.906] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
    [ 2142.906] (II) Module record: vendor="X.Org Foundation"
    [ 2142.906] compiled for 1.12.4, module version = 1.13.0
    [ 2142.906] Module class: X.Org Server Extension
    [ 2142.906] ABI class: X.Org Server Extension, version 6.0
    [ 2142.906] (II) Loading extension RECORD
    [ 2142.906] (II) LoadModule: "dri"
    [ 2142.906] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 2142.906] (II) Module dri: vendor="X.Org Foundation"
    [ 2142.906] compiled for 1.12.4, module version = 1.0.0
    [ 2142.906] ABI class: X.Org Server Extension, version 6.0
    [ 2142.906] (II) Loading extension XFree86-DRI
    [ 2142.906] (II) LoadModule: "dri2"
    [ 2142.906] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 2142.906] (II) Module dri2: vendor="X.Org Foundation"
    [ 2142.906] compiled for 1.12.4, module version = 1.2.0
    [ 2142.906] ABI class: X.Org Server Extension, version 6.0
    [ 2142.906] (II) Loading extension DRI2
    [ 2142.906] (II) LoadModule: "fglrx"
    [ 2142.906] (II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so
    [ 2142.920] (II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
    [ 2142.920] compiled for 1.4.99.906, module version = 8.97.2
    [ 2142.920] Module class: X.Org Video Driver
    [ 2142.921] (II) Loading sub module "fglrxdrm"
    [ 2142.921] (II) LoadModule: "fglrxdrm"
    [ 2142.921] (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so
    [ 2142.921] (II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."
    [ 2142.921] compiled for 1.4.99.906, module version = 8.97.2
    [ 2142.921] (II) ATI Proprietary Linux Driver Version Identifier:8.97.2
    [ 2142.921] (II) ATI Proprietary Linux Driver Release Identifier: 8.97.100.7
    [ 2142.921] (II) ATI Proprietary Linux Driver Build Date: Nov 16 2012 14:45:00
    [ 2142.921] (--) using VT number 2
    [ 2142.925] (WW) Falling back to old probe method for fglrx
    [ 2142.928] (II) Loading PCS database from /etc/ati/amdpcsdb
    [ 2142.929] (--) Chipset Supported AMD Graphics Processor (0x9488) found
    [ 2142.929] (WW) fglrx: No matching Device section for instance (BusID PCI:0@2:0:1) found
    [ 2142.930] (II) AMD Video driver is running on a device belonging to a group targeted for this release
    [ 2142.930] (II) AMD Video driver is signed
    [ 2142.930] (II) fglrx(0): pEnt->device->identifier=0x93e4a0
    [ 2142.930] (II) fglrx(0): === [xdl_xs112_atiddxPreInit] === begin
    [ 2142.930] (II) Loading sub module "vgahw"
    [ 2142.930] (II) LoadModule: "vgahw"
    [ 2142.931] (II) Loading /usr/lib/xorg/modules/libvgahw.so
    [ 2142.931] (II) Module vgahw: vendor="X.Org Foundation"
    [ 2142.931] compiled for 1.12.4, module version = 0.1.0
    [ 2142.931] ABI class: X.Org Video Driver, version 12.1
    [ 2142.931] (**) fglrx(0): Depth 24, (--) framebuffer bpp 32
    [ 2142.931] (II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
    [ 2142.931] (==) fglrx(0): Default visual is TrueColor
    [ 2142.931] (**) fglrx(0): Option "DPMS" "true"
    [ 2142.931] (==) fglrx(0): RGB weight 888
    [ 2142.931] (II) fglrx(0): Using 8 bits per RGB
    [ 2142.931] (==) fglrx(0): Buffer Tiling is ON
    [ 2142.931] (II) Loading sub module "fglrxdrm"
    [ 2142.931] (II) LoadModule: "fglrxdrm"
    [ 2142.931] (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so
    [ 2142.931] (II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."
    [ 2142.931] compiled for 1.4.99.906, module version = 8.97.2
    [ 2142.932] ukiDynamicMajor: found major device number 250
    [ 2142.932] ukiDynamicMajor: found major device number 250
    [ 2142.932] ukiOpenByBusid: Searching for BusID PCI:2:0:0
    [ 2142.932] ukiOpenDevice: node name is /dev/ati/card0
    [ 2142.932] ukiOpenDevice: open result is 11, (OK)
    [ 2142.932] ukiOpenByBusid: ukiOpenMinor returns 11
    [ 2142.932] ukiOpenByBusid: ukiGetBusid reports PCI:2:0:0
    [ 2142.933] (**) fglrx(0): NoAccel = NO
    [ 2142.933] (**) fglrx(0): ATI 2D Acceleration Architecture enabled
    [ 2142.933] (--) fglrx(0): Chipset: "ATI Mobility Radeon HD 4670" (Chipset = 0x9488)
    [ 2142.933] (--) fglrx(0): (PciSubVendor = 0x106b, PciSubDevice = 0x00b6)
    [ 2142.933] (==) fglrx(0): board vendor info: third party graphics adapter - NOT original ATI
    [ 2142.933] (--) fglrx(0): Linear framebuffer (phys) at 0xc0000000
    [ 2142.933] (--) fglrx(0): MMIO registers at 0xd0220000
    [ 2142.933] (--) fglrx(0): I/O port at 0x00001000
    [ 2142.933] (==) fglrx(0): ROM-BIOS at 0x000c0000
    [ 2142.933] (II) fglrx(0): AC Adapter is used
    [ 2142.940] (EE) fglrx(0): V_BIOS address 0xd00 out of range
    [ 2142.940] (II) fglrx(0): Invalid ATI BIOS from int10, the adapter is not VGA-enabled
    [ 2143.157] (II) fglrx(0): ATI Video BIOS revision 9 or later detected
    [ 2143.157] (--) fglrx(0): Video RAM: 262144 kByte, Type: GDDR3
    [ 2143.157] (II) fglrx(0): PCIE card detected
    [ 2143.157] (--) fglrx(0): Using per-process page tables (PPPT) as GART.
    [ 2143.157] (WW) fglrx(0): board is an unknown third party board, chipset is supported
    [ 2143.158] (II) fglrx(0): Using adapter: 2:0.0.
    [ 2143.257] (II) fglrx(0): [FB] MC range(MCFBBase = 0xf00000000, MCFBSize = 0x10000000)
    [ 2143.271] (II) fglrx(0): Interrupt handler installed at IRQ 46.
    [ 2143.271] (II) fglrx(0): RandR 1.2 support is enabled!
    [ 2143.271] (II) fglrx(0): RandR 1.2 rotation support is enabled!
    [ 2143.271] (==) fglrx(0): Center Mode is disabled
    [ 2143.271] (II) Loading sub module "fb"
    [ 2143.271] (II) LoadModule: "fb"
    [ 2143.271] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 2143.272] (II) Module fb: vendor="X.Org Foundation"
    [ 2143.272] compiled for 1.12.4, module version = 1.0.0
    [ 2143.272] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 2143.272] (II) Loading sub module "ddc"
    [ 2143.272] (II) LoadModule: "ddc"
    [ 2143.272] (II) Module "ddc" already built-in
    [ 2143.423] (II) fglrx(0): Finished Initialize PPLIB!
    [ 2143.428] (II) fglrx(0): Output LVDS using monitor section aticonfig-Monitor[0]-0
    [ 2143.428] (II) fglrx(0): Output DFP1 has no monitor section
    [ 2143.428] (II) fglrx(0): Output DFP2 has no monitor section
    [ 2143.428] (II) fglrx(0): Output CRT2 has no monitor section
    [ 2143.428] (II) Loading sub module "ddc"
    [ 2143.428] (II) LoadModule: "ddc"
    [ 2143.428] (II) Module "ddc" already built-in
    [ 2143.428] (II) fglrx(0): Connected Display0: LVDS
    [ 2143.428] (II) fglrx(0): Display0 EDID data ---------------------------
    [ 2143.428] (II) fglrx(0): Manufacturer: APP Model: 9cbc Serial#: 16843009
    [ 2143.428] (II) fglrx(0): Year: 2009 Week: 26
    [ 2143.428] (II) fglrx(0): EDID Version: 1.4
    [ 2143.428] (II) fglrx(0): Digital Display Input
    [ 2143.428] (II) fglrx(0): 8 bits per channel
    [ 2143.428] (II) fglrx(0): Digital interface is undefined
    [ 2143.428] (II) fglrx(0): Max Image Size [cm]: horiz.: 48 vert.: 27
    [ 2143.428] (II) fglrx(0): Gamma: 2.20
    [ 2143.428] (II) fglrx(0): DPMS capabilities: Off
    [ 2143.428] (II) fglrx(0): Supported color encodings: RGB 4:4:4
    [ 2143.428] (II) fglrx(0): Default color space is primary color space
    [ 2143.428] (II) fglrx(0): First detailed timing is preferred mode
    [ 2143.428] (II) fglrx(0): Preferred mode is native pixel format and refresh rate
    [ 2143.428] (II) fglrx(0): redX: 0.653 redY: 0.334 greenX: 0.300 greenY: 0.620
    [ 2143.428] (II) fglrx(0): blueX: 0.146 blueY: 0.050 whiteX: 0.312 whiteY: 0.329
    [ 2143.428] (II) fglrx(0): Supported established timings:
    [ 2143.428] (II) fglrx(0): Manufacturer's mask: 10
    [ 2143.428] (II) fglrx(0): Supported detailed timing:
    [ 2143.428] (II) fglrx(0): clock: 138.5 MHz Image Size: 475 x 267 mm
    [ 2143.428] (II) fglrx(0): h_active: 1920 h_sync: 1968 h_sync_end 2000 h_blank_end 2080 h_border: 0
    [ 2143.428] (II) fglrx(0): v_active: 1080 v_sync: 1083 v_sync_end 1088 v_blanking: 1111 v_border: 0
    [ 2143.428] (II) fglrx(0): Unknown vendor-specific block 1
    [ 2143.428] (II) fglrx(0): LM215WF3-SLA1
    [ 2143.428] (II) fglrx(0): Monitor name: Color LCD
    [ 2143.428] (II) fglrx(0): EDID (in hex):
    [ 2143.428] (II) fglrx(0): 00ffffffffffff000610bc9c01010101
    [ 2143.428] (II) fglrx(0): 1a130104a0301b78266fb1a7554c9e25
    [ 2143.428] (II) fglrx(0): 0c505400001001010101010101010101
    [ 2143.428] (II) fglrx(0): 0101010101011a3680a070381f403020
    [ 2143.428] (II) fglrx(0): 3500db0b1100001a0000000100061030
    [ 2143.428] (II) fglrx(0): 11000000000000000a20000000fe004c
    [ 2143.428] (II) fglrx(0): 4d3231355746332d534c4131000000fc
    [ 2143.428] (II) fglrx(0): 00436f6c6f72204c43440a20202000ba
    [ 2143.428] (II) fglrx(0): End of Display0 EDID data --------------------
    [ 2143.455] (II) fglrx(0): EDID for output LVDS
    [ 2143.455] (II) fglrx(0): Manufacturer: APP Model: 9cbc Serial#: 16843009
    [ 2143.455] (II) fglrx(0): Year: 2009 Week: 26
    [ 2143.455] (II) fglrx(0): EDID Version: 1.4
    [ 2143.455] (II) fglrx(0): Digital Display Input
    [ 2143.455] (II) fglrx(0): 8 bits per channel
    [ 2143.455] (II) fglrx(0): Digital interface is undefined
    [ 2143.455] (II) fglrx(0): Max Image Size [cm]: horiz.: 48 vert.: 27
    [ 2143.455] (II) fglrx(0): Gamma: 2.20
    [ 2143.455] (II) fglrx(0): DPMS capabilities: Off
    [ 2143.455] (II) fglrx(0): Supported color encodings: RGB 4:4:4
    [ 2143.455] (II) fglrx(0): Default color space is primary color space
    [ 2143.455] (II) fglrx(0): First detailed timing is preferred mode
    [ 2143.455] (II) fglrx(0): Preferred mode is native pixel format and refresh rate
    [ 2143.455] (II) fglrx(0): redX: 0.653 redY: 0.334 greenX: 0.300 greenY: 0.620
    [ 2143.455] (II) fglrx(0): blueX: 0.146 blueY: 0.050 whiteX: 0.312 whiteY: 0.329
    [ 2143.455] (II) fglrx(0): Supported established timings:
    [ 2143.455] (II) fglrx(0): Manufacturer's mask: 10
    [ 2143.455] (II) fglrx(0): Supported detailed timing:
    [ 2143.455] (II) fglrx(0): clock: 138.5 MHz Image Size: 475 x 267 mm
    [ 2143.455] (II) fglrx(0): h_active: 1920 h_sync: 1968 h_sync_end 2000 h_blank_end 2080 h_border: 0
    [ 2143.455] (II) fglrx(0): v_active: 1080 v_sync: 1083 v_sync_end 1088 v_blanking: 1111 v_border: 0
    [ 2143.455] (II) fglrx(0): Unknown vendor-specific block 1
    [ 2143.455] (II) fglrx(0): LM215WF3-SLA1
    [ 2143.455] (II) fglrx(0): Monitor name: Color LCD
    [ 2143.455] (II) fglrx(0): EDID (in hex):
    [ 2143.455] (II) fglrx(0): 00ffffffffffff000610bc9c01010101
    [ 2143.455] (II) fglrx(0): 1a130104a0301b78266fb1a7554c9e25
    [ 2143.455] (II) fglrx(0): 0c505400001001010101010101010101
    [ 2143.455] (II) fglrx(0): 0101010101011a3680a070381f403020
    [ 2143.455] (II) fglrx(0): 3500db0b1100001a0000000100061030
    [ 2143.455] (II) fglrx(0): 11000000000000000a20000000fe004c
    [ 2143.455] (II) fglrx(0): 4d3231355746332d534c4131000000fc
    [ 2143.455] (II) fglrx(0): 00436f6c6f72204c43440a20202000ba
    [ 2143.455] (II) fglrx(0): EDID vendor "APP", prod id 40124
    [ 2143.455] (II) fglrx(0): Printing DDC gathered Modelines:
    [ 2143.455] (II) fglrx(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
    [ 2143.455] (II) fglrx(0): Printing probed modes for output LVDS
    [ 2143.455] (II) fglrx(0): Modeline "1400x1050"x60.0 108.00 1400 1444 1556 1684 1050 1051 1054 1066 +hsync +vsync (64.1 kHz)
    [ 2143.455] (II) fglrx(0): Modeline "1280x1024"x60.0 108.00 1280 1444 1556 1684 1024 1051 1054 1066 +hsync +vsync (64.1 kHz)
    [ 2143.455] (II) fglrx(0): Modeline "1280x960"x60.0 108.00 1280 1444 1556 1684 960 1051 1054 1066 +hsync +vsync (64.1 kHz)
    [ 2143.455] (II) fglrx(0): Modeline "1280x800"x60.0 108.00 1280 1444 1556 1684 800 1051 1054 1066 +hsync +vsync (64.1 kHz)
    [ 2143.455] (II) fglrx(0): Modeline "1152x864"x60.0 108.00 1152 1444 1556 1684 864 1051 1054 1066 +hsync +vsync (64.1 kHz)
    [ 2143.455] (II) fglrx(0): Modeline "1280x768"x60.0 108.00 1280 1444 1556 1684 768 1051 1054 1066 +hsync +vsync (64.1 kHz)
    [ 2143.455] (II) fglrx(0): Modeline "1280x720"x60.0 108.00 1280 1444 1556 1684 720 1051 1054 1066 +hsync +vsync (64.1 kHz)
    [ 2143.455] (II) fglrx(0): Modeline "1024x768"x60.0 108.00 1024 1444 1556 1684 768 1051 1054 1066 +hsync +vsync (64.1 kHz)
    [ 2143.455] (II) fglrx(0): Modeline "1024x600"x60.0 108.00 1024 1444 1556 1684 600 1051 1054 1066 +hsync +vsync (64.1 kHz)
    [ 2143.455] (II) fglrx(0): Modeline "800x600"x60.0 108.00 800 1444 1556 1684 600 1051 1054 1066 +hsync +vsync (64.1 kHz)
    [ 2143.455] (II) fglrx(0): Modeline "800x480"x60.0 108.00 800 1444 1556 1684 480 1051 1054 1066 +hsync +vsync (64.1 kHz)
    [ 2143.455] (II) fglrx(0): Modeline "720x480"x60.0 108.00 720 1444 1556 1684 480 1051 1054 1066 +hsync +vsync (64.1 kHz)
    [ 2143.455] (II) fglrx(0): Modeline "640x480"x60.0 108.00 640 1444 1556 1684 480 1051 1054 1066 +hsync +vsync (64.1 kHz)
    [ 2143.455] (II) fglrx(0): EDID for output DFP1
    [ 2143.455] (II) fglrx(0): EDID for output DFP2
    [ 2143.455] (II) fglrx(0): EDID for output CRT2
    [ 2143.455] (II) fglrx(0): Output LVDS connected
    [ 2143.455] (II) fglrx(0): Output DFP1 disconnected
    [ 2143.455] (II) fglrx(0): Output DFP2 disconnected
    [ 2143.455] (II) fglrx(0): Output CRT2 disconnected
    [ 2143.455] (II) fglrx(0): Using exact sizes for initial modes
    [ 2143.455] (II) fglrx(0): Output LVDS using initial mode 1400x1050
    [ 2143.455] (II) fglrx(0): Display dimensions: (480, 270) mm
    [ 2143.455] (II) fglrx(0): DPI set to (74, 98)
    [ 2143.455] (II) fglrx(0): Adapter ATI Mobility Radeon HD 4670 has 2 configurable heads and 1 displays connected.
    [ 2143.455] (==) fglrx(0): PseudoColor visuals disabled
    [ 2143.455] (II) Loading sub module "ramdac"
    [ 2143.455] (II) LoadModule: "ramdac"
    [ 2143.455] (II) Module "ramdac" already built-in
    [ 2143.455] (==) fglrx(0): NoDRI = NO
    [ 2143.455] (==) fglrx(0): Capabilities: 0x00000000
    [ 2143.455] (==) fglrx(0): CapabilitiesEx: 0x00000000
    [ 2143.455] (==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
    [ 2143.455] (==) fglrx(0): UseFastTLS=0
    [ 2143.455] (==) fglrx(0): BlockSignalsOnLock=1
    [ 2143.455] (--) Depth 24 pixmap format is 32 bpp
    [ 2143.456] (II) Loading extension ATIFGLRXDRI
    [ 2143.456] (II) fglrx(0): doing swlDriScreenInit
    [ 2143.456] (II) fglrx(0): swlDriScreenInit for fglrx driver
    [ 2143.456] ukiDynamicMajor: found major device number 250
    [ 2143.456] ukiDynamicMajor: found major device number 250
    [ 2143.456] ukiDynamicMajor: found major device number 250
    [ 2143.456] ukiOpenByBusid: Searching for BusID PCI:2:0:0
    [ 2143.456] ukiOpenDevice: node name is /dev/ati/card0
    [ 2143.456] ukiOpenDevice: open result is 12, (OK)
    [ 2143.456] ukiOpenByBusid: ukiOpenMinor returns 12
    [ 2143.456] ukiOpenByBusid: ukiGetBusid reports PCI:2:0:0
    [ 2143.456] (II) fglrx(0): [uki] DRM interface version 1.0
    [ 2143.456] (II) fglrx(0): [uki] created "fglrx" driver at busid "PCI:2:0:0"
    [ 2143.456] (II) fglrx(0): [uki] added 8192 byte SAREA at 0x26000
    [ 2143.456] (II) fglrx(0): [uki] mapped SAREA 0x26000 to 0x7f222ea1b000
    [ 2143.456] (II) fglrx(0): [uki] framebuffer handle = 0x27000
    [ 2143.456] (II) fglrx(0): [uki] added 1 reserved context for kernel
    [ 2143.456] (II) fglrx(0): swlDriScreenInit done
    [ 2143.456] (II) fglrx(0): Kernel Module Version Information:
    [ 2143.456] (II) fglrx(0): Name: fglrx
    [ 2143.456] (II) fglrx(0): Version: 8.97.2
    [ 2143.456] (II) fglrx(0): Date: Nov 16 2012
    [ 2143.456] (II) fglrx(0): Desc: ATI FireGL DRM kernel module
    [ 2143.456] (II) fglrx(0): Kernel Module version matches driver.
    [ 2143.456] (II) fglrx(0): Kernel Module Build Time Information:
    [ 2143.456] (II) fglrx(0): Build-Kernel UTS_RELEASE: 3.7.10-1-ARCH
    [ 2143.456] (II) fglrx(0): Build-Kernel MODVERSIONS: no
    [ 2143.456] (II) fglrx(0): Build-Kernel __SMP__: no
    [ 2143.456] (II) fglrx(0): Build-Kernel PAGE_SIZE: 0x1000
    [ 2143.456] (II) fglrx(0): [uki] register handle = 0x00028000
    [ 2143.475] (EE) fglrx(0): Not enough video memory to allocate primary surface (frame buffer).
    [ 2143.475] (II) fglrx(0): Shutdown CMMQS
    [ 2143.475] (II) fglrx(0): [uki] removed 1 reserved context for kernel
    [ 2143.475] (II) fglrx(0): [uki] unmapping 8192 bytes of SAREA 0x26000 at 0x7f222ea1b000
    [ 2143.475] (WW) fglrx(0): ***********************************************************
    [ 2143.475] (WW) fglrx(0): * DRI initialization failed *
    [ 2143.475] (WW) fglrx(0): * kernel module (fglrx.ko) may be missing or incompatible *
    [ 2143.475] (WW) fglrx(0): * 2D and 3D acceleration disabled *
    [ 2143.475] (WW) fglrx(0): ***********************************************************
    [ 2143.475]
    Fatal server error:
    [ 2143.475] AddScreen/ScreenInit failed for driver 0
    [ 2143.475]
    [ 2143.475]
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    [ 2143.475] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    [ 2143.475]
    [ 2143.498] Server terminated with error (1). Closing log file.

    [  2143.475] (WW) fglrx(0): ***********************************************************
    [  2143.475] (WW) fglrx(0): * DRI initialization failed                               *
    [  2143.475] (WW) fglrx(0): * kernel module (fglrx.ko) may be missing or incompatible *
    [  2143.475] (WW) fglrx(0): * 2D and 3D acceleration disabled                         *
    [  2143.475] (WW) fglrx(0): ***********************************************************
    Have you gone over this section of the wiki and made sure everything is done? Are you using the legacy driver? If so how did you install it, and from where?
    Last edited by Kilz (2013-03-09 13:01:00)

Maybe you are looking for