ATI Radeon Graphics Driver not Working on SuSE i386

Anju · 12-07-2005, 04:30 PM

Okay, I have formated atleast 4 times out of pure frustration and hoping to make a difference installing the new ATI Radeon Drivers. Here is my situation, maybe someone here can help me.

My gaphics card is a Mobility Radeon 9600, I am running SuSE i386 (the 32bit version)

I have followed guides in these links which I found very helpfull, but never quite got there. Along with reading some posts from this forum, which have helped other people but nothing perticular for me yet.
cosmicpothole
suse.de/~sndirsch/ati-installer-HOWTO[/url]
susewiki.org/index.php?title=SUSE_10:_ATI_Driver_Installation[/url]
(don't have the post count to post full url's)

Currently when I input fglrxinfo it shows the Mesa Graphics, and I have yet to get that to change. When I go to the ATI Console that it installs, it will show the specs and then show that it is using OpenGL Mesa. I have intalled Xorg (the latest one, located on the ATI Driver page)

This is how my last installing went. I installed the Xorg file, then backed up a step to install Kernel-source. I continued and installed the ATI Driver (automatic) using there defaults and the visual. That did not work, so I created the rpm package specific for my OS. SUSE100-i386 and tried a install that way. I have done this in init 3 mode and not, if it where to make a difference. I have also made sure AGPGART is loading properly and that is....I have all pre-requisite pacakages installed.

I think I found my problem yet I am not that advanced to know how to tackle it myself. But first things first, here is my xORG file for anyone to view (incase this helps):

Quote:

File: xorg.conf
# File generated by fglrxconfig © ATI Technologies, a substitute for xf86config.

# Note by ATI: the below copyright notice is there for servicing possibly
# pending third party rights on the file format and the instance of this file.
#
# Copyright © 1999 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#

# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **********************************************************************

# **********************************************************************
# DRI Section
# **********************************************************************
Section "dri"
# Access to OpenGL ICD is allowed for all users:
Mode 0666
# Access to OpenGL ICD is restricted to a specific user group:
# Group 100 # users
# Mode 0660
EndSection

# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

Load "dbe" # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection

# This loads the Type1 and FreeType font modules
Load "type1"
Load "freetype"

# This loads the GLX module
Load "glx" # libglx.a
Load "dri" # libdri.a

EndSection

# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.

RgbPath "/usr/X11R6/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#

FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
# FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
# FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
# FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"

# The module search path. The default path is shown here.

# ModulePath "/usr/X11R6/lib/modules"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

# Option "NoTrapSignals"

# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

# Option "DontZap"

# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.

# Option "Dont Zoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

# Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client.

# Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.

# Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

# Option "AllowNonLocalModInDev"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

Identifier "Keyboard1"
Driver "kbd"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

# Option "Protocol" "Xqueue"

Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"

# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"

# These are the default XKB settings for XFree86
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""

# Option "XkbDisable"

Option "XkbRules" "xfree86"
Option "XkbModel" "pc101"
Option "XkbLayout" "us"

EndSection

# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/input/mice"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

# Option "Protocol" "Xqueue"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

# Option "BaudRate" "9600"
# Option "SampleRate" "150"

# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"

# ChordMiddle is an option for some 3-button Logitech mice

# Option "ChordMiddle"

EndSection

# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the XF86Config man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"
Identifier "Monitor0"
# === mode lines based on GTF ===
# VGA @ 100Hz
# Modeline "640x480@100" 43.163 640 680 744 848 480 481 484 509 +hsync +vsync
# SVGA @ 100Hz
# Modeline "800x600@100" 68.179 800 848 936 1072 600 601 604 636 +hsync +vsync
# XVGA @ 100Hz
# Modeline "1024x768@100" 113.309 1024 1096 1208 1392 768 769 772 814 +hsync +vsync
# 1152x864 @ 60Hz
# Modeline "1152x864@60" 81.642 1152 1216 1336 1520 864 865 868 895 +hsync +vsync
# 1152x864 @ 85Hz
# Modeline "1152x864@85" 119.651 1152 1224 1352 1552 864 865 868 907 +hsync +vsync
# 1152x864 @ 100Hz
# Modeline "1152x864@100" 143.472 1152 1232 1360 1568 864 865 868 915 +hsync +vsync
# 1280x960 @ 75Hz
# Modeline "1280x960@75" 129.859 1280 1368 1504 1728 960 961 964 1002 +hsync +vsync
# 1280x960 @ 100Hz
# Modeline "1280x960@100" 178.992 1280 1376 1520 1760 960 961 964 1017 +hsync +vsync
# SXGA @ 100Hz
# Modeline "1280x1024@100" 190.960 1280 1376 1520 1760 1024 1025 1028 1085 +hsync +vsync
# SPEA GDM-1950 (60Hz,64kHz,110MHz,-,-): 1280x1024 @ V-freq: 60.00 Hz, H-freq: 63.73 KHz
# Modeline "GDM-1950" 109.62 1280 1336 1472 1720 1024 1024 1026 1062 -hsync -vsync
# 1600x1000 @ 60Hz
# Modeline "1600x1000" 133.142 1600 1704 1872 2144 1000 1001 1004 1035 +hsync +vsync
# 1600x1000 @ 75Hz
# Modeline "1600x1000" 169.128 1600 1704 1880 2160 1000 1001 1004 1044 +hsync +vsync
# 1600x1000 @ 85Hz
# Modeline "1600x1000" 194.202 1600 1712 1888 2176 1000 1001 1004 1050 +hsync +vsync
# 1600x1000 @ 100Hz
# Modeline "1600x1000" 232.133 1600 1720 1896 2192 1000 1001 1004 1059 +hsync +vsync
# 1600x1024 @ 60Hz
# Modeline "1600x1024" 136.385 1600 1704 1872 2144 1024 1027 1030 1060 +hsync +vsync
# 1600x1024 @ 75Hz
# Modeline "1600x1024" 174.416 1600 1712 1888 2176 1024 1025 1028 1069 +hsync +vsync
# 1600x1024 @ 76Hz
# Modeline "1600x1024" 170.450 1600 1632 1792 2096 1024 1027 1030 1070 +hsync +vsync
# 1600x1024 @ 85Hz
# Modeline "1600x1024" 198.832 1600 1712 1888 2176 1024 1027 1030 1075 +hsync +vsync
# 1920x1080 @ 60Hz
# Modeline "1920x1080" 172.798 1920 2040 2248 2576 1080 1081 1084 1118 -hsync -vsync
# 1920x1080 @ 75Hz
# Modeline "1920x1080" 211.436 1920 2056 2264 2608 1080 1081 1084 1126 +hsync +vsync
# 1920x1200 @ 60Hz
# Modeline "1920x1200" 193.156 1920 2048 2256 2592 1200 1201 1203 1242 +hsync +vsync
# 1920x1200 @ 75Hz
# Modeline "1920x1200" 246.590 1920 2064 2272 2624 1200 1201 1203 1253 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 1400x1050 @ 60Hz M9 Laptop mode
# ModeLine "1400x1050" 122.000 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync
# 1920x2400 @ 25Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@25" 124.620 1920 1928 1980 2048 2400 2401 2403 2434 +hsync +vsync
# 1920x2400 @ 30Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@30" 149.250 1920 1928 1982 2044 2400 2402 2404 2434 +hsync +vsync

EndSection

# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"

# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.

# Chipset "generic"

# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# installed.

# BusID "PCI:0:10:0"

# VideoRam 256

# Clocks 25.2 28.3

EndSection

# === ATI device section ===

Section "Device"
Identifier "ATI Graphics Adapter"
Driver "fglrx"
# ### generic DRI settings ###
# === disable PnP Monitor ===
#Option "NoDDC"
# === disable/enable XAA/DRI ===
Option "no_accel" "no"
Option "no_dri" "no"
# === misc DRI settings ===
Option "mtrr" "off" # disable DRI mtrr mapper, driver has its own code for mtrr
# ### FireGL DDX driver module specific settings ###
# === Screen Management ===
Option "DesktopSetup" "(null)"
Option "ScreenOverlap" "0"
Option "GammaCorrectionI" "0x00000000"
Option "GammaCorrectionII" "0x00000000"
# === OpenGL specific profiles/settings ===
Option "Capabilities" "0x00000000"
Option "CapabilitiesEx" "0x00000000"
# === Video Overlay for the Xv extension ===
Option "VideoOverlay" "on"
# === OpenGL Overlay ===
# Note: When OpenGL Overlay is enabled, Video Overlay
# will be disabled automatically
Option "OpenGLOverlay" "off"
# === Center Mode (Laptops only) ===
Option "CenterMode" "off"
# === Pseudo Color Visuals (8-bit visuals) ===
Option "PseudoColorVisuals" "off"
# === QBS Management ===
Option "Stereo" "off"
Option "StereoSyncEnable" "1"
# === FSAA Management ===
Option "FSAAEnable" "no"
Option "FSAAScale" "1"
Option "FSAADisableGamma" "no"
Option "FSAACustomizeMSPos" "no"
Option "FSAAMSPosX0" "0.000000"
Option "FSAAMSPosY0" "0.000000"
Option "FSAAMSPosX1" "0.000000"
Option "FSAAMSPosY1" "0.000000"
Option "FSAAMSPosX2" "0.000000"
Option "FSAAMSPosY2" "0.000000"
Option "FSAAMSPosX3" "0.000000"
Option "FSAAMSPosY3" "0.000000"
Option "FSAAMSPosX4" "0.000000"
Option "FSAAMSPosY4" "0.000000"
Option "FSAAMSPosX5" "0.000000"
Option "FSAAMSPosY5" "0.000000"
# === Misc Options ===
Option "UseFastTLS" "0"
Option "BlockSignalsOnLock" "on"
Option "UseInternalAGPGART" "yes"
Option "ForceGenericCPU" "no"
BusID "PCI:1:0:0" # vendor=1002, device=4e50
Screen 0
EndSection

# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen0"
Device "ATI Graphics Adapter"
Monitor "Monitor0"
DefaultDepth 24
#Option "backingstore"

Subsection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0 # initial origin if mode is smaller than desktop
# Virtual 1280 1024
EndSubsection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
Identifier "Server Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.

Screen "Screen0"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"

EndSection

Now here is something I tried doing last, I went into init 3 and logged in as root.
I wanted to force my driver package so I input "rpm -Uhv --force fglrx_6_8_0_SUSE-8.19.10-1.i386.rpm" and it reported this error:

Quote:

make: Entering directory /usr/src/linux-2.6.13-15.7-obj/i386/default
make: *** No targets specified and no makefile found. Stop.
make: Leaving directory '/usr/src/linux-2.6.13-15.7-obj/i386/default'

*******************************
Build of kernel module failed!
*******************************

*******************************************************************************
Building/installation of fglrx kernel module failed! Try again by calling "/usr/X11R6/bin/fglrx-kernel-build.sh" manually.
*******************************************************************************

I tried 'calling" the line...and recieve the same error as the one above, and Build of kernel module failed.

I'm sure the answer is there....well not that sure. Yet I am not that experienced to figure it out myself. Please.....5 days of trying to install a driver and still no luck. Thanks alot.

Anju · 12-07-2005, 09:25 PM

I am still lost....could anyone lend a helping hand please...

Anju · 12-08-2005, 09:13 AM

No one can help me?

Cogar · 12-08-2005, 09:21 AM

I do not have an answer (sorry), but let me say that messages with no replies are automatically "bumped." You do not need to bump messages with 0 replies.

Anju · 12-08-2005, 09:39 AM

Well nvm now.....I figured it out myself, thanks for not helping because I feel alot better about myself now.

I was messing with installing some latest updates (yes I updated when I formmated) but there were some other recent updates that I had yet to install. Well I would install that, then some system updates from CD's which would then install the old Kernel again. Thus I installed and uninstalled Kernel after Kernel till I had the latest ones.(was not paying much attention to what it was installing)

Then I removed the current graphics card driver from the system, using the system update. Also removed the one before that, so when I booted up I had no graphical. I installed the computer specific driver through commands (simple) and configured it as well....through commands. I went to enter init 5, yet that did not work. So I ran init 3 again and then init 5 and it worked. I restarted computer and it is now showing the ATI Radeon drivers and giving out a frame rate of 4-5K FPS. Hope this helps anyone who had a problem similar to me.

Quote:

Originally Posted by Cogar

I do not have an answer (sorry), but let me say that messages with no replies are automatically "bumped." You do not need to bump messages with 0 replies.

Alright, thanks for the tip. I would not know that, but as you typed that I was typing how I solved it. Hopefully I don't have to come here with problems in the near future. Thanks for atleast replying.

beeblequix · 12-08-2005, 09:54 AM

http://www.linuxquestions.org/questi...&highlight=ati
http://www.linuxquestions.org/questi...&highlight=ati
http://www.linuxquestions.org/questi...=radeon+ati+3d

This one has a bunch of extra stuff but when I wrote it I hoped the ATI install stuff would be useful, and in your case it really may be the best fit:
http://www.linuxquestions.org/questi...=radeon+ati+3d

See if my experience helps at all. IMHO it sounds like you just (hehe.."just"=complicated for n00bs) need to use modprobe to load the correct opengl driver to get rid of MESA.

ß

Anju · 12-08-2005, 01:43 PM

I don't know what happened but....

I was trying to install Cedega and it told me the Mesa Drivers.....altho fglrx clearly states Radeon. I went into the modprobe and made sure graphical was running....loaded VIA again to make sure... (for my computer)

Then I did a fglrxinfo and it shows Mesa once again...... *tear*

So I decide to roll back my computer from a backup I made....except it tells me the .tar file is corrupted. *sigh*

I restart the computer and......this is my error.

INIT: cannot execute "/etc/init.d/boot
INIT: Entering runlevel :5
INIT: cannot execute "/etc/init.d/rc"

I am then stuck in Runlevel 3 and the prompt shows "(none) Login: _)
No login works and I believe somehow I screwed up the boot loader? Atleast something on the lines...I doubt this can be fixed short from a Format.

beeblequix · 12-08-2005, 01:56 PM

Format.

One thing I dislike about SuSe is the need to use 'init'. Debian defaults to the right one anyway (I think init 5).

When you go thru this process again would you mind documenting how you're setting up your ATI card? I'd like to see it before I install the latest Suse DVD eval.

ß

Anju · 12-08-2005, 02:07 PM

sure...I'll format in a couple hours and document any changes I make. My friend runs SuSE and he stands by it, I have only played with it (basics) dual booting from my desktop. So this was my "big jump" for my laptop....anyways I will update soon enough. Although I was going to try using the repair ability from the CD's first...to see if that fixes anything.

Anju · 12-08-2005, 04:46 PM

I formated and right after the format, because I have internet, I updated my system before leaving the format window. Completed all the basic questions after the update completed and computer restart, then it restarted again into my fresh system. First thing I did was check that POSIX Shared memory was working and AGPGART was on, also checking that I had glibc installed. (prequisites from http://www.cosmicpothole.com/Linux/ati.php) I went out and downloaded the Xorg file from the radeon website and the ATI Driver, after downloading those two...because I will be using Wine I downloaded it as well. The regular file and the delevel Wine file, latest ones releast today, I believe (9.3). Then I went to Linux Gamers and looked up the requirements for Cedega and Wine and installed all of them from CDs. EXCEPT for the Mesa related ones......

I got my graphics card specific driver out of the ATI installer and left the rpm inside my home folder. Then I restarted the laptop for good measures.

After restart I opened home folder and accessed the console. I went to install the Xorg rpm I had downloaded from ATI earlier. Yet I had not installed the GCC packet, so that did not work. Took a step back, and installed that with the Compiler just for kicks. Went back into console and forced the installation of the Xorg file because it told me it had already been installed.

Went into INIT 3 and went to install the graphics card now. I forced it, but I could not remember what I was forgetting earlier....I needed Kernel-Source...and as I was doing this remember that somewhere I had downloaded for a reason "python-gtk" so I went ahead and installed both of them. It told me there was a Dependecy error between the package I tried to install and the default one....so I deleted the one I tried to because it had basically failed. I am now going back to try installing it again. Yet again I have a different error so I plan to take off the other driver completely through Yast, System Update...it will give me the dependicy error again. I go and delete both of the display drivers. (p.s. don't update because those updates from your CD's will only kick back your kernel version.) It then tells me to reboot...even tho I did not install the older Kernel, but I reboot anyways. Boots into graphical.....and both, default ATI driver and the one I installed are gone. I am going to install now my specific driver that I had recieved earlier.

Then bam...lol, I get the same error I had recieved above. I thought I had it this time...let me mess some more. I will update what I have done in the meantime, read this for now.

Anju · 12-08-2005, 09:53 PM

Alright...some people might laugh at me for this choice but meh. I am going to take a break from SuSE and try my hand at Gentoo AMD 64. I figure since I have the guide open on one computer and doing it on another....I can get through the setup. Plus once it is setup I understand that it is very good, perhaps I will have better luck with the ATI Drivers. As well I will learn more. I will revisite this post later tho.

nlaw · 03-03-2006, 04:17 AM

For what it's worth, I spent 10 hrs tring to install the ATI drivers as downloaded from the ATI website. This was on a SUSE 9.3 with a ATI 9550 grahpics card. I still haven't managed to do it, and had decided it would be better off buying an nvidia card.

It seems you can do it but the ATI installation process really needs to be much less complicated. Currently I'm stuck just trying to load the kernel sources. I've chosen the correct kernel-source RPM but using YAST it doesn't actually extract the sources and put them in the correct place, I'm guessing you have to do some command line stuff here rather than use YAST.

nlaw · 03-03-2006, 04:29 AM

I just found a URL posted by REDSHIRT cosmicpothole.com/Linux/ati.php , looks like this should do the trick.

Cheers
Nick

Anju · 03-03-2006, 11:18 PM

Old post...look at date my friend. I have gotten it to work in the past on two different systems. It is a pain in the rear end. Not only to boot the quality of the drivers are not even par to the regular drivers and you loose ALOT of quality. Like 100-200fps with the ATI Linux drivers. It was just not worth it and I ended up giving up on ATI with Linux. Altho after this post above I did succesfully install and have a working Gentoo machine (from scratch, no pre-built kernel) as well as running Ubuntu and SuSE all with working ATI graphics. I just installed Kubuntu on my home machine to try it out because I prefer KDE to Gnome and that is why I was turned off from ubuntu.(also to see any improvements in the ATI drivers, and I can tell you this now....they still suck) Right now I recommend Linux to all people who have Nvidia, to all my friends with ATI cards I sadly have to not recommend it. (I wish ATI would open source their Linux drivers so people could create better ones)

nlaw · 03-06-2006, 05:41 AM

Thanks for getting back to me. When you are getting desperate you stop looking at the dates as any snippet of information could be useful.

Well finally I got the ATI drivers to work. But, did I struggle. To recap, this is SUSE 9.3 with a ATI 9550 card, and importantly (as you will see later a LCD monitor) after having figured out how to install the kernel-sources (I was using the wrong rpm, (the suffix on the end should have been "kernel-source...i586.rpm" and not "kernel-source...src.rpm". doh!. I ATI install went ahead smoothly, the 3D works, even though in yast/sax2 it says its not enabled. Also in sax2 it says I have a 9700 as well as the fglrx driver if I remove the 9700 driver nothing works.

Also the characters looked really blurry and not well defined and sharp. I knew the answer to that problem already as I had experienced the same thing on a Sun Solaris system.

Initially the system defaulted to a monitor resolution of 1280x1024x85, if you have an LCD monitor it works differently to a CRT, an LCD should be set to 60hz max. With LCD a frequency of 60hz produces an image of the same quality of a CRT running at 85Hz.

So, Every thing is working, except xine but that may be for other reasons, and the quality seems as good as any other card I've seen. However having said that, the amount of time it took just isn't worth it, when I need to put together another system it will have an NVIDIA card in it.

Just one other question, how did you determine your frame rate, I used GL-117 game in KDE that said my fps was 151. I don't know if that's good or bad ?

Regards
Nick