SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Ok, just checking to see if anyone (who uses SuSE) has had any luck getting ATI's latest video driver to work? I've got an ATI All-In-Wonder 9700 Pro video card and SuSE 9.2 Pro installed. I downloaded the ATI driver a few day's ago and tried to install it with YAST. The installation went great.... no hiccups or burps. I ran Sax2 and picked 24 bit color and 1280 x 1024 screen resolution and tried to enable 3-D acceleration... of course, it would not let me enable 3-D acceleration. So, I ran fglrxinfo and the out put comes back that the Mesa driver is installed. Don't get me wrong... the graphics are great... far better than what they look like when I boot up into Windows XP Pro... But, when I try to run a 3-D game ( like tux racer ) the graphics look great but the program is super slow and the movements are jerky. Anyway, my question is this.... Is there a full-proof way of installing the ATI video driver to make it work properly in SuSE 9.2 Pro? I see lots of articles and replies in various linux forums... but its hard to tell which fix is correct... ie... I don't want to try something and create an X-Server nightmare. My computer has an Intel Motherboard and 3.06 GHz processor with hyperthreading and 1.5 Gig ram and 200 Gig hardrive... Soundblaster Audigy Platinum soundcard and All-In-Wonder 9700 Pro video card.
I also have a an AIW 9700 Pro & am running SUSE 9.2. I'm trying to find a way to get 3D Acceleration to work as well.
From what i've been able to dig up, you have to build and install the ATI kernel module to enable 3D Acceleration. There are instructions on ATI's website, but I'm not sure how accurate they are...
I'll be trying it out this weekend, but if anyone experienced in this sort of thing could help out it'd be much appreciated (especially because I'm such a newbie ).
I built & installed the kernel module; installed the fglrx rpm, & ran fglrgconfig and everything appeared to be fine. Then I tried to restart X windows and it crashes. X won't even load. I was going to cut & paste the error messages, but without X this is a little difficult. When I have more time I'll see if the errors ended up in a log file somewhere. At the moment I have no idea what the exact problem is; I hope to play with it more this weekend. If anyone else has any more information on known issues with Suse 9.2 & the ATI drivers, please let me know. I'm running Suse 9.2 on an Asus A7N8X-X mb with an Athalon XP processor, ATI Radeon 9600XT graphics card, and a Hitachi SuperScan Elite 751 moniter.
Its ALIVE. I appear to have working ATI drivers on a Suse 9.2 box. While searching for information on the Suse forums, I found a link to the repackaged Suse drivers: ftp://ftp.suse.com/pub/suse/i386/sup...6/fglrx/8.8.25
I downloaded the files and followed the instructions in the readme. A couple of things to note:
In step 3, when I ran the command rcxdm stop, my machine froze. I rebooted, logged in as root (as opposed to just using a root terminal window), and this time when I ran the command it simply kicked me out of Gnome and left me at a command prompt. I'm guessing this is what should normally happen. The next command would not run because it said the machine was in the wrong run level. However, it told me to "init 3", which I did and then everything appeared to be fine. Moral of the story, I'd issue all of the commands from a command prompt as root without X running at all. I'm not sure how to tell for certain if X is using the hardware 3D acceleration as opposed to software; but the "tearing" of models in my 3-D CAD software is gone. I can spin an assembly model consisting of a couple hundred parts as fast as I can move the mouse, so I suspect that the hardware accel is working. The only problem I've experienced so far is that the thumb buttons on my logitech mouse quit working. I know there are ways to fix this, but before they worked by default. Anyway, I'll post more details if I run into any problems; but for the moment I'm claiming success.
lo ppl, i've read all your posts very carefully, downloaded all requested files in order to do that, but unfortunatelly i wasn't so lucky to make the 3D accelleration to work
i forgot to mention that my installation is on a FUJITSU SIEMENS LAptop. Amilo M 1420 with a resolution of 1280 x 800 and a ATI Radeon 9600 Graphics Card with 128 MB of RAM. hope that helps .
i will post below my settings
1. the Ati Control Panel in X Server (KDE Enviroment)
# **********************************************************************
# 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.
# 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).
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"
# 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" ""
everything seems to be fine, but when i try to run e.g. the game CHROMIUM the 3D acceleration is disabled and the screen of the game runs lets say at -1 fps in other words there is no 3D acceleration at all.
any suggestions and any help would be appreciated, i tried the mandrake 10 distro and there the 3D acceleration worked fine, but for many reasons i dont want to get back to mandrake since my Wireless card and other hardware doesnt work at all.
Actually, I figured out what the problem was for me. I thought I was running XFree86 instead of X.Org, & the kernel module is intended for XFree86 users.
I downloaded the X.Org ATI driver from their website & installed it according to their directions (rpm -Uvh 'filename'.rpm). Then I entered a console as root & ran fglrxconfig (backup your existing xorg.conf file!). Followed the steps & everything works fine. You might have to restart your xserver before the changes take place. A handy command I learned: go to another console window, login as root & type: /etc/init.d/xdm restart
Ran glxgears afterward & now get around 4000 fps . For some reason it picks up my card as a 9500 Pro, but I guess thats because the architecture is the same.
Last edited by Mr_Failure; 03-23-2005 at 02:14 PM.
I went to the ATI web site and I didn't find any guide to installing the drivers, can you tell me were they are or give me some more accurate hints on how you did it?
thanks
I installed the X.Org 6.8 drivers using text mode only and the instructions in the previous threads, and fglrxconfig after that. It was a lot of guessing, but I even managed to set my monitor horizontal rates correctly without checking the manual (ie. because I don't have it).
Some programs fail to detect the drivers, though. 3Ddiag didn't detect anything, neither did SuperTux. Damn, that's been my fave Linux game this far.
Here's exactly what I did to get the driver working:
Download the latest ATI X.Org 6.8 Driver (current: fglrx_6_8_0-8.10.19-1.i386.rpm)
Open a console and type:
Code:
cd (Directory you downloaded the rpm to)
su
rpm -Uvh fglrx*.rpm
cp /etc/xorg.conf ~/xorg.conf.bakup (Not necessary, but just in case)
fglrxconfig
If you can, find out what the exact horizontal & vertical refresh rates for your monitor are. Use those instead of the defaults. For everything else, the defaults should be okay (whatever is in the []). Now either restart the x server (see my previous post) or restart your computer. Then to see if everything's working OK, enter a console and type:
Code:
fglrxinfo
glxgears
fglrxinfo should list the 3D renderer as whatever ATI card you have. Anything over 1000 fps (more or less) with glxgears & you should be good to go.
You won't be able to use SaX2 to configure 3D settings after setting up the ATI driver, but I haven't needed to use it.
Last edited by Mr_Failure; 03-24-2005 at 09:02 AM.
I did exactly what you said and now I can't get a GUI. It's only text mode. When I run "fglrxinfo" it says
"Error: unable to open display :0"
and glxgears says
"Error: couldn't open display '(null)'"
I'm somewhat new to linux and I'm not sure how to get things back. Also my xorg.conf links to XF86Config and it won't let my cp my backup into the etc/X11 directory. I tried starting KDE and I get multiple errors mostly saying
"xset: unable to open display "" "
...
"ksplash: cannot connect to X server"
"kdeinit: Aborting. $Display not set."
...
I think this might be an easy fix but I'm not sure how to do it.
Go to the ATI website and download the ATI Driver Installer Pakcage. It is a .run file, so make it executable and run it. When it comes up choose the generic option in stead of distro specific. Then just follow the prompts. I'm pretty sure afterwards you have to run fglrxconfig, but can't remember for sure. Reboot or restart X and you should be good to go.
I too want to install the latest ATI drivers. I have never been through this before, and I must say it is disheartening to read all of the problems people have. Can I ask a few, very basic questions?
1) When I tried to down load the ATI installer package, I did not get a straightforward download. Instead, the program text appeared in my browser, after a significant wait. I then saved the page as a file with the right name. Surely this was not what was supposed to happen?
2) What is the best way to run without X? The only way I know is to boot into safe mode. So far, I haven't successfully run even check.sh.
3) Is the best way to run the ATI Installer from a command line boot? (I assume that is what init 3 is.) Or are you supposed to run from a command prompt with the default boot (I.e., all the normal GUI stuff is there)?
1) That's an issue with how your browser is registered to handle the filetype.
2) Best way is to set your system to boot with init 3 instead of init 5. Alternatively you can su and then run init 3 to close out of X.
3) I ran the installer just fine from a standard boot including gui and everything. In order to run the file you can use whatever desktop you have and right click a the file and change properties so it is executable, then just click the file to run it. You can also run it from a commandline by typing 'sh ati.installer.name.run'
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Latest ATI Video Drivers
).
in other words there is no 3D acceleration at all.
