Hi to everyone,

new ATI drivers 8.24.8 have been released 2 days ago, and I downloaded them to try if they work with my Radeon X1900XT. Until now I must use vesa drivers (before I had a Radeon 9500 PRO), as ATI didn't support yet new graphics cards like X1300, X1600, X1800 and X1900 (shocking!).
The question is when I run command startx, the screen become black and my PC is stuck. Even keyboard doesn't work.

This is my xorg.conf (generated by aticonfig):


# File generated by xf86config.
#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#
# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **********************************************************************
# NOTE: This is a NEW IMPROVED version of XF86Config-fbdev that uses the vesa
# driver instead of the fbdev driver. Thanks to Kenneth Fanyo who pointed
# this out to me.
# This XF86Config file is designed for use with the VESA framebuffer.
# This generic interface should work with nearly all video cards
# (although not every card will support every resolution).
# With the new driver, it should no longer be required to have frame buffer
# support in the kernel, or to run it on the console.
#
# Enjoy!
# -- volkerdi@slackware.com
#
# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************
# **********************************************************************
# Server flags section.
# **********************************************************************
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
# Some examples of extended input devices
# 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
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
# **********************************************************************
# 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.
# **********************************************************************
# 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
# 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.
# 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".
Identifier "Simple Layout"
Screen 0 "aticonfig Screen 0" 0 0
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection

Section "Files"

# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#
# ModulePath can be used to set a search path for the X server modules.
# The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/"
EndSection

Section "Module"

# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
# This loads the GLX module
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "type1"
Load "freetype"
#Load "speedo"
Load "glx"
Load "dri"
EndSection

Section "InputDevice"

# 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"
# Set the keyboard auto repeat parameters. Not all platforms implement
# this.
# Option "AutoRepeat" "500 5"
# Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)).
# Option "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# Option "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a European
# keyboard, you will probably want to use one of:
#
# Option "XkbModel" "pc102"
# Option "XkbModel" "pc105"
#
# If you have a Microsoft Natural keyboard, you can use:
#
# Option "XkbModel" "microsoft"
#
# If you have a US "windows" keyboard you will want:
#
# Option "XkbModel" "pc104"
#
# 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 X.Org
#
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
Identifier "Keyboard1"
Driver "kbd"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "it"
EndSection

Section "InputDevice"

# Identifier and driver
# On platforms where PnP mouse detection is supported the following
# protocol setting can be used when using a newer PnP mouse:
# Option "Protocol" "Auto"
# The available mouse protocols types that you can set below are:
# Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2
# Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
# MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
# ThinkingMouse ThinkingMousePS/2 Xqueue
# which is usually a symbolic link to the real device.
# Option "Device" "/dev/mouse"
# Option "Device" "/dev/psaux"
# Option "Device" "/dev/ttyS0"
# Option "Device" "/dev/ttyS1"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/input/mouse0"
# Option "Buttons" "3"
EndSection

Section "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 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.
Identifier "My Monitor"
HorizSync 30.0 - 81.0
VertRefresh 56.0 - 75.0
EndSection

Section "Monitor"
Identifier "aticonfig Monitor 0"
EndSection

Section "Device"

#VideoRam 4096
# Insert Clocks lines here if appropriate
Identifier "VESA Framebuffer"
Driver "vesa"
EndSection

Section "Device"
Identifier "ATI Graphics Adapter 0"
Driver "fglrx"
Option "(null)"
Option "DesktopSetup" "single"
Option "UseInternalAGPGART" "off"
Option "KernelModuleParm" "off"
BusID "PCI:1:0:0"
EndSection

Section "Screen"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.
# DefaultDepth 8
# DefaultDepth 16
# DefaultDepth 32
# "1024x768" is also a conservative usable default resolution. If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)
Identifier "Screen 1"
Device "VESA Framebuffer"
Monitor "My Monitor"
DefaultDepth 24
SubSection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 32
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "Screen"

# Monitor "My Monitor"
Identifier "aticonfig Screen 0"
Device "ATI Graphics Adapter 0"
Monitor "aticonfig Monitor 0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection




Xorg.0.log doesn't have errors, only some warning.
My doubt is that ATI made usual bugged drivers.
I use Slackware 10.2 with kernel 2.6.13.

Thanks in advance.

Scorpion77

Taken from Phoronix.com

For those inquiring about the known issue in the 8.24.8 release with motherboard compatibility issues -- X Server may fail to load when using an ATI Radeon X1x00, 512MB product with certain motherboards. Further details can be found in topic number 737-22056 --
we have some additional information available today. While we are still waiting for replies from ATI's Linux department, an ATI representative has told Phoronix that the compatibility issue plagues 512MB X1000 products using dual PCI Express motherboards. From what we have been told so far, the compatibility problem will not affect single PCI Express x16 slot motherboards. More information to come as it is received. UPDATE: We have been told that the motherboard compatibility issue should be corrected in the next release. If you are personally experiencing this issue, we ask that you submit your system specifications to us using our contact page so the data can be passed onto ATI for further examination.

Thanks a lot!
But I have a ABIT KN8 Ultra motherboard, which is a single slot motherboard. Maybe the chipset (nForce4 Ultra) is incompatible with these drivers. I hope new release can fix this problem.

Scorpion77

I am unable to get my ATi x1900XT to work with Suse 10... I am just gonna have to go buy an Nvidia card i suspect.

The downside is I am a MCSE and am trying to get into Linux, and the driver issues/ hardware problems dont help. I too have a single slot PCIe board (Abit Fatality AN8, also with Nforce4 chipset). Read lots about the install process but always end up with a black white screen... most disheartening.

Removed, sorry, wrong forum.

I have a Sapphire Radeon x1600 Pro 512mb AGP and I've yet to find any distro that works with it. Only Gentoo
PCLinuxoS said its too new for Linux
FRugalware = no answer
Ubuntu = havent tried
Phaeronix = didnt work
Kororaa = havent tried
Kanotix = havent tried
Fedora Core 5 = wrong resolution & installation wont do

Thats all in the list

Be aware that they have a major problem in the latest ATI driver release. It doesn't work with kernels above 2.6.16.x because the no_iommu variable is has been removes from the header files, so atis drivers doesn't even compile.

And there is are lots of other problems. I have battled during the whole afternoon with many different glitches before things started to work out. And my opteron still only has 2D accelaration, only could get direct rendering in the laptop.

Register at ATI and mail them, so they start working. Those lazy bastards. 2.6.16.x kernels have been around for a while now and they didn't bother to read the Changelogs. So now they don't have support for the latest ones.

Thanks Krugger, I think i seen you somewhere in IRC cant remember

Maybe it helps getting the driver running:

I have it running with ati radeon 1800 xl:

I compiled it three times ( don't ask me why by it didn't work from the start ), did an aticonfig and there it is.

I'm using Slackware 10.2 ( actually current ) with xorg 6.9 and default Slackware Kernel 2.6.14. Runs great, though I still have some crashs, but I have those under M$ Windows XP too, so I guess it's an ati bug somewhere.

My hardware is an epox nforce 4 ultra Mainboard with amd64 3200+. So there should be no major incompatibility with nforce4 Boards.

I've tried vesa in Gentoo(Phaeronix) works but wrong resolutions didn't change to comment the modeline though.

I tried running with fglrx jsut didnt work.

Acer AL1916W 19" LCD/Widescreen
1002:71c2 shows up for ATI Technology unknown|

Which is a sapphire radeon x1600 pro 512mb

I am thinking of upgrading to the latest AGP ATI card but not so sure