Linux and Open Source Blog

May 12, 2006

SUSE 10.1: ATI Drivers Installation

Filed under: 1. openSUSE/SUSE, Hardware, HowTos/Tutorials/Tips — E@zyVG @ 3:19 pm

Got my SUSE Linux 10.1 up and runnin and already enjoying, though still got to go through all the customization. I will probably post a review on my experience with SUSE 10.1. But one thing for sure, the ATI drivers gave me a little kick, before I came up with these instructions, that I hope will work on most of the computers. Remember that I was trying to install these drivers as to later be able to install and launch Xgl/Compiz on desktop.

This time I decided to make the howto with more pics, thinking that maybe this way it will be easier for you guys to understand what is going on. At least I tried my best, well nearly. Here we go.

As of writing this I am running SUSE Linux 10.1 (maybe you already forgot), x86_64 platform (AMD64), with my ATI Radeon X800 series PCI-E interface on DFI nForce4 Ultra based motherboard. The latest driver version is 8.24.8

Once again there are prerequisites before you begin installing the drivers. You will need to have the following installed. All these can be found on your SUSE 10.1 CDs or DVD, unless by the time you will be reading this post and already there are online updates available for these packages, via Yast/Apt/Yum repositories. The packages are:

1. kernel-source 2.gcc 3. make

Info for n00b or rather newbies: When you see “~>” bfore command, that means execute it as user, and when you see “#“, you have to be root (by typing “su” and supplying the password when asked). No disrespect … :-]

Once the above mentioned packages are installed, let’s prepare the kernel modules (not necessary, but no harm in doing so). Execute the following commands (as root):

# cd /usr/src/linux

# make mrproper

# make cloneconfig

# make modules_prepare

and one last command to clean the kernel source:

# make clean

Also, if you have tried installing drivers before, let’s remove them properly by executing the command:

# rpm -e $(rpm -qa | grep fglrx)

Now to installing drivers. From the following screenshot you can clearly see that when a fresh copy of SUSE 10.1 is installed, OpenGL rendering is supported by MESA supplied drivers. Basically, when you see MESA - that means the ATI drivers are not up and running. This can be found by running either of the commands: glxinfo or fglrxinfo (as user, not root)


Lets get started the:

1. Download the latest available drivers from ATI Drivers and Software section. Choose your version of drivers: x86 for 32 bit, x86_64 for 64 bit. You need to download “ATI Driver Installer”

2. Once downloaded, copy to a folder that you wont forget. In my case it is /home/me/temp

3. Now we need to leave the cool graphical desktop and switch to console mode by typing (as root):

# init 3

4. Log in as root and switch to folder where you downloaded the file. In my case:

# cd /home/me/temp

5. Now we need to build a package (installer) by typing the following command:

# sh ./ati-driver-installer-8.24.8-x86_64.run –buildpkg SuSE/SUSE101-AMD64

or if you have 32 bit, then

# sh ./ati-driver-installer-8.24.8-x86_64.run –buildpkg SuSE/SUSE101-IA32

6. Now we will need to install the created .rpm file:

# rpm -ihv fglrx64_6_9_0_SUSE101-8.23.7-1.x86_64.rpm

and at the end you should have something similar to the following, without any errors:

7. Edit ld.so.conf (not all people need this, but it helps if certain people encounter problem with /usr/lib/fglrx/lib/libGL.so.1.2 errors). Use your favourite text editor. I am using “vim”.

For newbies with vim -> once in text mode press “i” –> type the lines shown below –> press “ESC” –> press “shift+:” –> type “wq“–> Enter

# vim /etc/ld.so.conf

and add the following (add lib64 part only if you are using x86_64) as first line(s)

/usr/lib64/fglrx/lib

/usr/lib/fglrx/lib

8. Now run the following command. I required it for x86_64 setups, or had probs with running next command on some other computers. 32-bit users can also run it, won’t disturb.

# ldconfig

9. Once above has been completed, execute the following:

# aticonfig –initial –input=/etc/X11/xorg.conf

Your old xorg.conf file get’s backed up to xorg.conf.fglrx-0 (who knows what’s gonna happen. Unfortunately i had to use the backup - it’s good it did create a backup)

10. Now we need to execute one more command:

# sax2 -r -m 0=fglrx

[Maybe some of you will ask why samething twice - I don't know, but this worked for me the best - believe me. I tried other 2-3 ways or so and was ending up with no go or with strange xorg.file !!!]

11. Reboot(!) before you enter your DE (Destop Environenment). I know this is not Windows - again, this worked for me and really hope that will be true with you.

Once rebooted and back to your KDE/Gnome and logged in as user, launch few more commands to verify that all went good and OpenGL is working now at it’s max:

~> fglrxinfo

~> glxinfo

If it states ATI Technologies Inc and the make of your card - excellent. Everything is setup correctly and working flawlessly. Time to relax and have a cup of coffee.

One more thing - just verify the following in your /etc/X11/xorg.conf file. Also make sure that under ” Modules” section there is -> Load “dri

IMPORTANT: You need to recompile and install the fglrx kernel module after each kernel update.

With my current setup I am getting the following result:

Hope this HowTo will be of help.

Enjoy

Update (20th April 2007): openSUSE 10.2: AMD/ATI Drivers Installation

 

298 Comments »

  1. Neatly Explained Tutorial. Wish would work everywhere. RPM method didn’t work for me on Suse 10. Had to use ATI Installer. Got it right, but FPS 1200 only. Didn’t know to use sax2 after aticonfig. Hope will improve FPS

    Comment by NarahariBabu — May 12, 2006 @ 4:41 pm

  2. heh, thanks for providing the 10.1 version of your tutorial so soon.. will certainly come in handy next week ;)

    I wondered how you took the screenshots when you were in single user mode? (init 3)

    also, I noticed that it seems that the default font config does not do the kerneling very well :S see for example the “home” word in the screenshot

    Comment by mattie — May 12, 2006 @ 6:29 pm

  3. It’s atrange, but no matter which method I try, which enables the drivers ok, there is this problem: if i try to switch to another screen (tty) {Ctrl+Alt+F1/F2/F3…F8} the screen goes black. Same thing happens if i want to launch another instance of X for another user.

    Anyone knows what’s wrong. The Xorg file is same as above.

    Comment by john2k — May 12, 2006 @ 10:07 pm

  4. Guys, since I wrote this HowTo so early, I really hope that I haven't done any mistakes … as I myself need to test it out for some days to come. Plus once I receive my box version I will be reinstallingand hope to see newer drivers available from ATI. If there will be some modifications to be made, I will do so by updating the current post.

    For the mean time if you have suggestions or remarks - do let me know.

    Comment by E@zyVG — May 12, 2006 @ 10:08 pm

  5. This did the trick.

    Was having trouble getting the ATI driver going with an X600 on 10.1

    At least 10.1 will load the graphical without ATI drivers. 10.0 would use out of range values with an X600.

    Comment by kiryuu — May 12, 2006 @ 11:33 pm

  6. mattie>> I wondered how you took the screenshots when you were in single user mode? (init 3)

    I did it the hard way - so that you guys can see the process. The hard way means I launched these commands in init 5 (you shouldn't do it) to take snapshots. Then I switched to init 3, reverssed everything (cleaned) and did all again.

    Comment by E@zyVG — May 13, 2006 @ 12:46 am

  7. I have been trying to get my 3D work for some programs, I first tried in Ubuntu, then on SUSE 10.0 now on 10.1 but or some reason all didnt work, i got blank screen the every time I restarted my computer :( and could not do anything, reversed everything back to Vesa using the failsafe boot.

    Amd64 3800 + Dual Processor
    ATI X800 GTO Fireblade Edition video card, please help

    Comment by Lava — May 13, 2006 @ 1:29 am

  8. John2K>>> I also encountered the same problem and still don't know how I resolved it. Maybe someone later in comments will explain this phenomena.

    Lava>>> I can suggest you to check your manual for the monitor and manually enter the horizontal and vertical sync (Hz) once you launch sax2 command.

    It can be that the resolution and frequency are not being setup correctly.

    Comment by E@zyVG — May 13, 2006 @ 3:11 am

  9. BTW, as Moosy mentioned, the same instructions can be applied to SLED10, as they are based on same code.

    Check out his blog for Xgl setup, as I will be following his instructions  first - kinda scared though that something might go wrong.

    If all goes OK I will try to write another small HowTo with the help of information based on his blog.

    Comment by E@zyVG — May 13, 2006 @ 3:13 am

  10. Great walkthrough. Worked like a charm.

    Seems like you have a lot of people visiting your post, but not much comments.
    I have reommended few of my friends to your post as they also have ati cards.

    Thank you.

    Comment by agusto — May 13, 2006 @ 7:38 pm

  11. First, Great tutorial and thank you for posting it so soon. I too used the 10.0 version to much aid. I am having a problem with my card and would like to run it by you.

    System:
    AOpen AK77-600Max
    AMD AthlonXP 3200
    1.5GB Ram
    ATI Radeon 9600XT (Sapphire)

    The driver installs ok per your tutorial above. The only difference I noticed was there were a few refereneces to an invalid pointer during the rpm package install.

    I am able to test with glxgears and returns decents scores on the FPS, but should I try to run any OPENGL application (Screen Saver) the screen freezes and I am forced to hard restart.

    The system seems to be working behind the freeze as indidcated by hard drive acticity during a download.

    Any thoughts or a helpful link for support would be great. I delt with this in version 10.0 but would like to know if the problem is somewhere on my end.

    Thanks,

    Matthew

    Comment by Matthew — May 13, 2006 @ 10:07 pm

  12. How were you able to resolve it on 10.0. Try using the same method - though i think you already did that. Let me know how you were able to resolve it. Also, if you try to switch screens (ctrl+alt+f1/f2 … f7) are you getting a black screen, or eveything is ok with that? BTW, send me a copy of your xorg.file.

    Comment by E@zyVG — May 13, 2006 @ 11:57 pm

  13. Well done!

    Recommend you add at the beginning: backup /etc/X11/xorg.conf — just copy it to somewhere in /home/yourname. That way they can always get back to the beginning start point by copying it back & overwriting the file if ever needed. An easy 1st step.

    jim

    Comment by Snakedriver — May 14, 2006 @ 12:48 am

  14. Snakedriver>>

    As you can see from step 7, the file get’s backed up prior to modifications.

    Comment by E@zyVG — May 14, 2006 @ 1:55 am

  15. Suggestion that I had to do on my laptop -

    Run ldconfig after the rpm install but before step 7 otherwise aticonfig might complain about not finding one of the fglrx libraries. Didn’t happen to me on the other 2 systems I installed to so not sure what happened on this one.

    Comment by kiryuu — May 14, 2006 @ 3:31 am

  16. [...] http://jarpack.net/ati-driver-how-to http://moosy.blogspot.com/2006/04/sled10-and-ati.html http://linux.wordpress.com/2006/05/12/suse-101-ati-drivers-installation/ [...]

    Pingback by Funraill Foundation'blog | Standards libres - Php, Javascript, Xul, Ajax, C, C++, OpenGL... — May 14, 2006 @ 3:03 pm

  17. Thanks for the directions!
    You’re using HTML entity #8211 (en-dash) instead of double dashes on some of the switches (like “–buildpkg”), which will be confusing for new folks.

    I had to make a couple small changes for it to work for me:

    Using sh to run the installer didn’t work. Instead, I made it runnable:
    chmod +x ati-driver-installer-8.24.8-x86_64.run
    and ran it directly:
    ./ati-driver-installer-8.24.8-x86_64.run –buildpkg SuSE/SUSE101-AMD64

    The first time I ran aticonfig, it couldn’t find its libraries. I had to add their directory to the path:
    export PATH=$PATH:/usr/X11R6/lib64

    The screen came up the wrong size, but ran I Sax2 again once I was in KDE. That fixed it.

    (Using a Radeon X550, Athlon 64, and a fresh OpenSuSE 10.1 install.)

    Comment by Dan Gerhards — May 14, 2006 @ 8:40 pm

  18. wow it working
    Thanx

    Comment by k0da — May 14, 2006 @ 9:36 pm

  19. “KernelModuleParm” “agplock=0″ has a red arrow next to it, but why? The driver seems to be installed and working for me (~6500 fps in glxgears w/ a Radeon9800Pro) without the agplock bit.

    Comment by IMAPIRATE! — May 15, 2006 @ 1:40 am

  20. Re posts 13 & 14: Sorry I didn’t zero in on step 7. That too is well done! Do you have a command to replace the backup, or, just copy & paste?

    Comment by Snakedriver — May 15, 2006 @ 4:12 am

  21. thanx for the tips guys, will try it tomorrow once i get to my linux machine :)

    Never even thought about the monitor frequencies, hehehe, i know that monitor is an antique oldie!

    Bye

    Comment by Lava — May 15, 2006 @ 11:08 am

  22. John2K>>

    I think under Section "Screen" if you have several resolutions listed in "Modes", remove all but the first one, i.e the one which is maximum resolutions, and save the file. BTW, don't forget to backup the original xorg.conf - just in case.

    Hope this resolves the issue.

    P.S>> Guys, if my guide is of some help, please leave your tnx comments and also let me know how is Xgl functioning on your 10.1 (state KDE/Gnome). Tnx

    IMAPIRATE>> 

    If your drivers are working fine without it then it Ok. Just make sure that Xgl will work, as I think this can be required for it, though I might be wrong. Good to see your card is working. 

    Comment by E@zyVG — May 15, 2006 @ 12:52 pm

  23. I have some problems with this. Basically I followed all steps (3 times just to be on the save side) and it still does not work. When I type fglrxinfo (9) i get “unable to open display :0″ and when I restart X and try it again it shows me the Mesa stuff:

    display: :0.0 screen: 0
    OpenGL vendor string: Mesa project: http://www.mesa3d.org
    OpenGL renderer string: Mesa GLX Indirect
    OpenGL version string: 1.2 (1.5 Mesa 6.4.1)

    Besides, all my Monitor settings are lost (resultution etc). I am running a IBM Z60m notebook with ATI X600 (1680×1050).

    Any ideas?

    Comment by max — May 15, 2006 @ 3:56 pm

  24. Thanks to the opensuse XGL troubleshooting page (http://en.opensuse.org/Xgl_Troubleshooting) and the NVidia XGL wlkthrough (http://www.novell.com/coolsolutions/feature/17174.html), I’ve got XGL up and running on both Gnome and KDE.

    My somewhat old video card can apparently do XGL without the agplock; however, the XGL troubleshooting page on opensuse suggests it for newer cards (x300+). Your mileage may vary. I did use Option “no_dri” “no”. Some people suggest using Option “VideoOverlay” “on”, but I’ve not tried it yet.

    After some poking around in the KDM setup files without much luck, I bit the bullet, changed my login display manager to GDM, and made the “0=support” to “1=support” change recommended on Troubleshooting. If anyone gets KDM launching correctly, please post. I’d like to switch back :-)

    Once the ATI drivers were installed, I mostly followed the instructions from Scott Morris’s XGL on NVidia walkthrough. The “config” portion of his walktrhough is a bit outmoded, as 10.1Final includes a set of command line scripts to toggle XGL on and off (gconf-xgl-*) and a GUI in the desktop controls. If you use the GUI or script to turn XGL on, you can use the gconf-xgl-switch to turn it off at the command line if things don’t work, which will probably be easier for most folks than making backups of xorg.config, sysconfig, etc. and restroing them by hand.

    The Gnome and KDE setup portions of the Nvidia walkthrough work equally well for ATI cards. Using Scott’s instructions, it’s possible to tweak the plugin settings in Gnome, but in KDE changing the plugin settings in gcong only changes SOME behaviour (ex: drop shadows). I’ve not been able to make some changes I want (ex: “insied” view of the cube, mouse flipping of cube sides) in KDE, yet. If anyone is able to get KDE fully configured, please post a followup.

    Comment by IMAPIRATE! — May 15, 2006 @ 4:11 pm

  25. Hello E@zyVG
    First I want to thank you soo much for helping.
    I still get the blank screen after all the steps :(
    I even checked refresh rate and the refresh rate for the screen was within the monitor’s range (Monitor == Sony FD400 (FD Triniton) and is autodetectable by SUSE). May be I will try removing all the other screens like you suggested John 2K. Hopefully that will work out.
    Again I want to thank you very much for this guide.
    Lava

    Comment by Lava — May 15, 2006 @ 8:13 pm

  26. well, removing the screen things didnt work either :. Let me go through all the things I did in your process,
    All the above process went fine till step 7
    On Step 8 when I do Sax2 that is when I get blank screen and I still get blank screen when I restart.
    If my system profile helps, it is
    Biostar nForce Ultra A9 - motherboard
    AMD64 Manchester 3800 Dual Processor
    PCI ATI X800 GTO FireBlade
    Sony FD Triniton (FD400)
    WD 80 Gig HD
    WD 250 Gig SATA drive
    1.5 Gig of PC3200 RAM
    Setup :
    Windows XP on the WD 250 gig
    SUSE 10.1 on the WD 80 gig

    May be I am doing something wrong somewhere, :(
    Any help is much appreciated :),
    Thank you
    Lava

    Comment by Lava — May 15, 2006 @ 11:37 pm

  27. It’s a great Guide! but not work for me! :-(
    MB: MSI RD480 Neo2 (rs480 ship Xpress200)
    VGA: ATi X1600pro
    I install the last driver on Suse 10.1.
    The result is a corrupt colors! and can’t enter in terminal mode(ctrl+alt+F1).
    I try Suse rpm, ati automatic.. etc.. and the result is the same ! :-( Where is the problem shipset or atiX1600pro?? please Help!

    Comment by Mario Morais — May 16, 2006 @ 12:01 am

  28. Lava>>
    I see you got new specs computer. Try updating the BIOS for motherboard.
    Next, open xorg.file and check the frequencies (vert. and horizontal) once again, and compare them to what is stated in your monitors manual.
    I am not sure, but try google and do search on smp-kernel and ati drivers, since you have dual-core cpu … i have no experience with that as of yet. That’s all I can think of right now.

    Mario>>
    E-mail me your copy of xorg.conf file once you have done everything that is in tutorial. I hope you are not getting any error or warning messages when compiling driviers or installing them.

    Comment by E@zyVG — May 16, 2006 @ 12:31 am

  29. Excellent Instructions. Although I didn’t follow them exactly (I followed more of what ATI’s website suggested) your page gave me the confidence that this was something that could be done in ~1/2 hour.

    Low and behold.. All worked out great. Thanks!

    Comment by Richard Galka — May 16, 2006 @ 7:29 am

  30. Thanks for excellent instructions.

    Now I am working on setting up the cool Xgl on my desktop.

    Comment by Lewis — May 16, 2006 @ 1:00 pm

  31. I’ve tried several different methods to install this and still having no luck. I managed to get the drivers working on suse 10.0 no probs but my x850xt died 3 days later :(. Currently using a x1800xt. The problem i’m having is that after the drivers are installed i boot up and my display is corrupted and multi-coloured. The only method i can’t use is the actual ati installer because my vesa framebuffer rez is permanently set to 1024×768 I can’t click on the ok button to proceed with the installation :/ as its some where off the desktop. I’m currently at work but if someone could help me later on when I have access to my pc with the xorg.conf and xorg logs I will be gratefull.

    Comment by Steve — May 16, 2006 @ 5:34 pm

  32. I just tried the above method as well with no success :( Here are my specs

    AMD Athlon X2 4200+
    ATI Radeon x1900 xtx
    2 Gig Ram

    I have the same results as Mario, where the colors are all messed up and I can’t even go back into the console mode. Only way was to putty into my system and revert back to the original xorg.conf, then reboot. I am trying to do this with Suse 10.0 x86_64. Could it be because of the newer video card and SuSE using the smp kernel?

    Comment by Thom — May 16, 2006 @ 8:15 pm

  33. As I have mentioned above, the reason can lie with the smp-kernel that dual-core owners are using. Not having one at the moment, I am unable to resolve this issue. Maybe googling around will give you guys some tips and once you know what extra steps are required, you can then base your installation with above howto.

    Also check ATI website - maybe they have some info on multi-core processors and ATI cards in combo.

    Comment by E@zyVG — May 16, 2006 @ 8:58 pm

  34. Well I did some searching and there have been problems with some ati cards X1xxx with 512mb having problems with these drivers and therefore they won’t work in linux. There is supposed to be the 8.25 series coming with the new catalyst drivers soon that is supposed to fix the problem.

    Comment by Steve — May 17, 2006 @ 5:02 am

  35. Ah forgot to add the link it apparently only happens with certain x1xxx 512 cards and mobo combinations http://www.driverheaven.net/printthread.php?t=103796 (post right at the bottom)

    Comment by Steve — May 17, 2006 @ 5:13 am

  36. I can’t get it to work!!!!! ThinkPad T42P. Sax2 fails even though I see the same script when I rpm the package. Looks like the drivers are not installing even though it says it does. This sucks!!!!!

    Comment by Ted — May 17, 2006 @ 8:22 am

  37. The ldconfig just prior to step 7 sorted everything out for my install on an Acer Aspire 1500 series Amd 64 bit laptop. Excellent work.

    Comment by Jock Stewart — May 18, 2006 @ 1:42 pm

  38. ************************************************
    Small UPDATE - Step 7 (Xtra Step Added)
    ************************************************

    Maybe this will resolve some issues!!!

    Comment by E@zyVG — May 18, 2006 @ 1:42 pm

  39. Hey. This is a great tutorial, however, I have some problems. I ran ldconfig before aticonfig and everything seemed to install fine. Then, I tried the sax command and when X11 started, I got color problems metioned earlier. I tried rebooting and when I try to log into GNOME and I still get the color problems. I can only now boot into XEN with no 3D Acceleration.

    My system:
    AMD Athlon X2 4400+ Processor
    MSI RD280 Neo2 Mobo
    ATI Radeon X1800 All-in-Wonder Graphics Card

    Before I installed SuSE 10.1, I used Fedora Core 4 and the drivers installed without a hitch and 3D Acceleration worked great. Odd.

    Comment by Sean — May 18, 2006 @ 5:30 pm

  40. Anyone found a solution to the “black screen / Freeze” when switching TTY with Ctrl-alt- F1 F2 … ?? Everything else works, except for this problem. I edited my xorg.conf to keep only the first (highest) resolution without success.

    Comment by Xtrem — May 18, 2006 @ 9:08 pm

  41. Unfortunately no. Removing those lines doesn’t help as it seems. The problem lies somewhere else. Still trying to figure out.

    Comment by E@zyVG — May 18, 2006 @ 9:18 pm

  42. Hi, I have gone through all the steps many times. However, the end result is that the opengl version is still Mesa. I’m sure it is something stupid that I am missing. Can someone please give me their input. I am using a Centrino with a Mobile Radeon 9600 (obviously IA32). Thanks, Chris.

    Comment by Chris — May 19, 2006 @ 6:22 am

  43. lol yea…something stupid indeed…i didn’t configure/have the kernel source. Thank you very much for a great tutorial.

    Comment by Chris — May 19, 2006 @ 7:03 am

  44. Hi. thanks.
    Finally 3d is working in my laptop compaq xpress 200m.
    bye and thanks again

    Comment by Juan — May 19, 2006 @ 8:27 am

  45. Great work!
    HP nc6000 laptop
    ATI Mobility Radeon 9600
    OpenGL and indirect glx working!

    Comment by Phoenix49 — May 19, 2006 @ 7:32 pm

  46. [...] Ένα σχετικό άρθρο. [...]

    Pingback by qablunaaq’s corner » Blog Archive » ATI driver — May 19, 2006 @ 11:47 pm

  47. About the “black screen / Freeze” when switching from XGL to console :
    It look like an ATI BUG (a known issue according to release note) :
    “Toggling between console mode and X Server graphical mode may result in a system hang. Further details can be found in topic number 737-22058″

    Any idea? The issue number doesn’t provide any article.

    Comment by Xtrem — May 20, 2006 @ 3:37 am

  48. I have x800gto card and Its doesn’t work for me :( After doing all steps I have blank screen, no matter run sax2 or not(step9). I’ve check my xorg.conf file and find that all the frequency ranges correct. Just wondering what else I can do to make it works…

    Comment by Ulver — May 20, 2006 @ 4:34 am

  49. The blank screen seems to be driver problem. Let’s hopr that next drivers will resolve this issue.

    Comment by E@zyVG — May 20, 2006 @ 11:35 am

  50. Nice entry - works great on my hp Compaq nc8000 with ATI Mobility Radeon 9600.

    I can’t think why ATI are incapable of producing such quality how-to’s for Linux support… actually I’d rather they spend the time bringing their drivers up-to-date! ;)

    Comment by lamaslany — May 21, 2006 @ 4:33 pm

  51. Excuse my n00biness, but I dont have 64bit, I have an AMD Athlon XP 2400 with a “SAPPHIRE RADEON 9600 ATLANTIS 256MB DDR AGP 4X/8X Video Card”

    Do I still download the 64bit version ATI Installer and just do that 32bit step “-buildpkg SuSE/SUSE101-IA32″

    and complete the rest? or Do I have to do something else?

    just wanting to make sure before I accidentally blow up my computer or something ;]

    thanks

    Comment by King of all N00bs — May 21, 2006 @ 6:52 pm

  52. King>> IA32, i.e. 32-bit is for you. so download 32-bit drivers and complete the rest as it's same.

    Comment by E@zyVG — May 21, 2006 @ 6:59 pm

  53. >>Xtrem I looked up the same issue too, but there is no article regarding that issue number or a bunch of issue numbers on that page.

    Any one know the release date of next ATI drivers for linux?

    Comment by Lava — May 21, 2006 @ 7:33 pm

  54. The drivers are coming out tomorrow, not for sure, but 99% possible, because there are the catalyst 6.5 (windows final version, not betas)) drivers leaked already out there.

    So i hope they release them tomorrow because i have the same problem (colourful and weird desktop) using my 1800XT 512mb..

    Comment by HitMaker — May 21, 2006 @ 7:53 pm

  55. Thanks E@zyVG

    I now have the 3d support and it regonizes my RADEON 9600 woo hoo!

    only problem is, i totally messed up my display and when I go into YaST to scoot the screen over it wont let me =(

    I’m just going to reinstall and try again, now that I got this under me

    Once again, thanks!

    Comment by King of all N00bs — May 21, 2006 @ 11:47 pm

  56. Thanks! This is the first time (after trying Fedora and Ubuntu) that I got the ATI drivers to work on my AMD64 + X850XT. And I now have 3D in Linux!

    Comment by Jeff — May 22, 2006 @ 10:17 am

  57. Thank you very much! This worked for me with a few exceptions:

    -indeed in step 5 “–buildpkg” needs to be “-–buildpkg” (two dashes)

    - Step 8 did not work because I had no xorg.conf file to begin with. I just let sax2 make it. Should I re-run the aticonfig command?

    -Once the system (10.1 w/ KDE) was up and running, I tried to run “ATI Control” and I get an error “Command firegtlcontrol not found”. Anyone know why?

    Comment by chad — May 22, 2006 @ 1:20 pm

  58. Thanks. Everytıng works fine on MSI m635 laptop.(turion 64,X700). Except the screen resolutin. It has a 15.4 LCD. But i cant set it beyond 800-600. When i set the resolution to 1280-800 i get a black screen.

    Comment by ssaylanc — May 22, 2006 @ 6:09 pm

  59. in step 6 picture 2. that error about not finding .libfglrx_ip.a.GCC4.cmd is holding me up, how did you get that error and get past it? you say similiar as the picture but no error’s so how did you solve that error?

    Comment by josh — May 23, 2006 @ 9:01 am

  60. It don’t work, It can’t create the rpm file and i don’ know why!!!??
    But thank you for your work

    Comment by RôM1 — May 24, 2006 @ 2:05 am

  61. Ok, new drivers came out, have you tried them (people with X1X00 512GRAM), did it work now? i hope it did….

    Comment by HitMaker — May 25, 2006 @ 12:28 am

  62. [...] I will update the Howto once I get back home and install the new verion. [...]

    Pingback by Linux and Open Source Blog » New ATI Display Drivers 8.25.18 - “LifeSaver” — May 25, 2006 @ 2:48 am

  63. ************************************************************************************
    New ATI Display Drivers 8.25.18 - “LifeSaver”
    ************************************************************************************

    I will UPDATE the HowTo soon, if required.

    ************************************************************************************

    Comment by E@zyVG — May 25, 2006 @ 2:51 am

  64. Well these did nothing for me, I installed them but now when trying to startx it just dies saying “No matching Device Section for instance BusID (PCI:3:0:1) found.

    So then I went ahead and just did sax2, and found out that the system thinks my card is a “VESA FrameBuffer Graphics”

    wtf, I have a 512MB ATI X1900 xtx and the dame thing doesn’t work. Way to go ATI!!

    Sorry for the rant but this is just so aggitating

    ps. Is there any way to force these drivers?

    Comment by Thom — May 25, 2006 @ 3:41 am

  65. Ok, so this is what I think is happenning;

    3:0:1 is actually the second Digital-Out in case I have 2 monitors. Problem is I don’t have 2 monitors, so I don’t care about 3:0:1 right? That’s just a guess, but at this point I’m pretty fed up with this. How freaking hard can it be to make these work, I mean c’mon ATI, you make millions…jeeez

    I even tried the –dual-monitor switch with aticonfig and that didn’t do jack, it didn’t even create a correct xorg.conf, it still made to screen devices with both being 3:0:1, pretty pathetic.

    If anyone got this to work on a high end card, PLEASE let me know! I find it hard to believe that I’m the only linux user with a card like this, then again with the support ATI gives us, you never know…

    Comment by Thom — May 25, 2006 @ 4:49 am

  66. forcing the dual monitor with aticonfig create two devices with 3:0:0, not 3:0:1, my apologies

    Comment by Thom — May 25, 2006 @ 4:51 am

  67. Can’t get it work… I have Opteron 165 and Radeon 9200, installed 32bit version of Suse 10.1. Do I need to go with 64bit?

    Can’t install rpm. “error: Failed dependencies:
    libexpat.so.0 is needed by fglrx_6_9_0_SUSE101-8.25.18-1.i386″

    Ran ATI install, it failed to run post-kernel script. I continued anyway, driver has changed, but it hang the system after any action (like press a button, move a window), forget about 3D…

    Reerted back to saved xorg.conf…

    Comment by alex — May 25, 2006 @ 6:06 am

  68. The new drivers fixed the problem it seems so, even though I could not enable 3d using the install instruction provided on the website of ATI, now when i do fglrxinfo i get the exact screen on STEP 10 above with ATI instead of MESA. + glxinfo gives me about 7272 fps (i dont know what fps should i be getting).

    Thanx EAZYVG :)

    Comment by Lava K.C. — May 25, 2006 @ 12:05 pm

  69. It still doesn’t work for me, not even with the new driver. I followed the instructions, resolved the failed dependencies error (@alex: install compat-expat1), but after I run the sax2 command a color-corrupted screen appears. Just like with the previous driver. It seems that my HP Compaq nx7000 won’t be having ATI drivers under SuSE ;_;

    Comment by Preditcon — May 25, 2006 @ 6:32 pm

  70. I cannot say what’s wrong with the color curruption, but when I updated the drivers on my friends computer this same issue arrised, even though it was working fine before.

    I am trying to figure out, so give me few days. Hopefully I’ll have the answer. And if so, I will make a post. Maybe it’s still the bug in drivers.

    Comment by E@zyVG — May 25, 2006 @ 7:15 pm

  71. I tried this with the 8.25.18 driver and kept getting the “libexpat.so.0 is needed by fglrx” error, but haven’t had any luck finding compat-expat1.
    So I tried with 8.24.8 and I’ve followed the guide step-by-step with no errors what-so-ever, but fglrxinfo still says I’m using Mesa.
    I’m running a Pentium 4 with Radeon Mobility 9000.

    Comment by Samutz — May 25, 2006 @ 9:08 pm

  72. “compat-expat1″ rpm can be found here (if someone is looking for one):
    http://download.opensuse.org/distribution/SL-10.1/inst-source/suse/i586/compat-expat1-1.95.8-6.i586.rpm

    Comment by E@zyVG — May 25, 2006 @ 9:58 pm

  73. hahaha, lol, i thought everything was working and had not tried ctrl+alt+F1 to F6. Those screen are messed up and if i try going to those screen, i get a scrambled picture screen and the system reboots :(. Then I thought running sax2 would fix the problem, but if i use sax2 and save anything, everything gets messed up :( the next time X windows starts up. This is real sad, next time I buy a video card, I will see if that v.c is properly supported in linux or not and then buy it. May be I should give up on installing drivers on this dual core machine and buy a new casing and put together my old machine :).. If anyone know how to fix that problem, pls let me know

    Bye

    Comment by Lava KC — May 25, 2006 @ 11:53 pm

  74. Hi all,
    First off, thanks alot for the tutorial, very informative. However, even after following the tutorial numerous times, including a fresh install, I am unable to activate OpenGL or, it would appear, install the drivers at all. Everything installs fine, no errors or strange behaviour, but i still get MESA as my opengl driver when i do a fglrxinfo, and of course gears is pathetically slow.

    I think i may have a problem with unsupported hardware. I am running a Compaq R3000 laptop with ATI Mobility 9100 IGP, RS300 chipset. From reading docs and googling, i think the drivers do not support DRI with this chipset. I seem to have a smoother running 2D environment, but really want the 3D working.

    ATI Control panel works and shows everything as being fine, even recognising my GFX card as an ATI chipset. But still no 3D.

    Does anyone know of a way to Force the drivers to load DRI? I am willing to at least try this even if it causes the system to be unstable, either way i would know. Or does anyone know of a workaround for this problem?

    Much Appreciated.

    Comment by Unstable — May 26, 2006 @ 1:36 am

  75. Ok, so I’m using the new 8.25.18 drivers and I can’t get 3D acceleration to work.

    I can build the SUSE 10.1 package without a hitch, install it, configure xorg.conf with SAX, load the kernel module and start X.

    However when I issue the command fglrxinfo (or glxinfo/glxgears) all I get is:

    [fglrx] API ERROR: could not register entrypoint for SelectTextureSGIS
    [fglrx] API ERROR: could not register entrypoint for SelectTextureTransformSGIS
    [fglrx] API ERROR: could not register entrypoint for ClientActiveVertexStreamATI
    [fglrx] API ERROR: could not register entrypoint for VertexBlendEnviATI
    [fglrx] API ERROR: could not register entrypoint for VertexBlendEnvfATI
    [fglrx] API ERROR: could not register entrypoint for VertexStream2sATI
    [fglrx] API ERROR: could not register entrypoint for VertexStream2svATI
    [fglrx] API ERROR: could not register entrypoint for VertexStream2iATI
    [fglrx] API ERROR: could not register entrypoint for VertexStream2ivATI
    [fglrx] API ERROR: could not register entrypoint for VertexStream2fATI
    [fglrx] API ERROR: could not register entrypoint for VertexStream2fvATI
    [fglrx] API ERROR: could not register entrypoint for VertexStream2dATI
    [fglrx] API ERROR: could not register entrypoint for VertexStream2dvATI
    [fglrx] API ERROR: could not register entrypoint for VertexStream3sATI
    [fglrx] API ERROR: could not register entrypoint for VertexStream3svATI
    [fglrx] API ERROR: could not register entrypoint for VertexStream3iATI
    [fglrx] API ERROR: could not register entrypoint for VertexStream3ivATI
    [fglrx] API ERROR: could not register entrypoint for VertexStream3fATI
    [fglrx] API ERROR: could not register entrypoint for VertexStream3fvATI
    [fglrx] API ERROR: could not register entrypoint for VertexStream3dATI
    .
    .
    .

    Anyone with the same problem or any idea what’s going on?

    Comment by Jad K — May 26, 2006 @ 2:04 pm

  76. I have the same problem of Jad.
    I have installed the driver on SUSE 10.0 with a radeon 8500.
    Sorry for my poor english. ;-)

    GT

    Comment by GT — May 26, 2006 @ 8:05 pm

  77. hmm…i think that the problem is this lib: “/usr/lib/fglrx/lib/libGL.so.1.2″

    I have two version installed:
    1) /usr/lib/fglrx/lib/libGL.so.1.2 (from ati drivers installation)
    2) /usr/lib/libGL.so.1.2 (mesa project i suppose)

    Executing as root:

    #fglrxinfo

    I get this output:
    ——–
    display: :0.0 screen: 0
    OpenGL vendor string: Mesa project: http://www.mesa3d.org
    OpenGL renderer string: Mesa GLX Indirect
    OpenGL version string: 1.2 (1.5 Mesa 6.2.1)
    ——–

    Executing as normal user:

    ~>fglrxinfo

    I get a long list of: “[fglrx] API ERROR: could not register entrypoint”

    I think that from root shell “fglrxinfo” command use /usr/lib/libGL.so.1.2 (mesa project)
    instead of /usr/lib/fglrx/lib/libGL.so.1.2 .
    From normal shell viceversa.

    Again…sorry for my poor english ;-)

    GT

    Comment by GT — May 26, 2006 @ 9:02 pm

  78. Hi E@zyVG, and all!

    Thanky you bery much for yor great howto. Pls allow me to update a little bit with experience I have been gathering for days. (and gray hair, too). I’m in a rush, but I felt I must share infos with you.

    The newest driver is 8.25! What you should know:
    -when you want to install the generated rpm, it will require the libexpat.so.0 during the install. Altough expat is in the fresh install, that does not matter. Because: it IS NOT in the SuSE 10.1 release!!! You must dl from http://download.opensuse.org/distribution/SL-10.1/inst-source/suse/i586/compat-expat1-1.95.8-6.i586.rpm and install it BEFORE the fglrx..rpm

    -I could install Xgl simply with Xgl and compiz packs with Yast.
    BUT

    DO NOT believe the wiki on opensuse: I use Gnome, and if you follow the Troubleshooting guide for gnome, the Xgl won’t work.

    Please confirm me that my method works for you, guys.
    (Suse 10.1, ATI 9550, 32bit, Xgl)

    Have a nice weekend! :)

    Lityi

    Comment by Lityi — May 26, 2006 @ 9:12 pm

  79. **************************************************************************************

    UPDATE: Extra Step added from 7
    **************************************************************************************

    Let me know if this resolves certain issues.

    GT >>> This might help u.

    Comment by E@zyVG — May 26, 2006 @ 11:52 pm

  80. Absolutely the same problem as described above in Comment by Lava KC — May 25, 2006 @ 11:53 pm.

    Comment by Ulver — May 27, 2006 @ 12:27 am

  81. The extra step does not resolve the problem with libGL :-(

    Thanks anyway ;-)

    GT

    Comment by GT — May 27, 2006 @ 12:41 am

  82. I think ATI should visit this post to see all the bugs, as I am quite sure that these are bugs.

    Comment by E@zyVG — May 27, 2006 @ 2:16 am

  83. hello all
    i got the same fuc..’ problems encountered by GT.
    I have a radeon mobility 9000 card.

    Comment by marty — May 27, 2006 @ 2:27 am

  84. Thanks for expat1 tip, Preditcon! I installed SuSE amd64, installed ATI driver via rpm. No errors. But “Desktop Effect Settings” dialog says 3D Acceleration is disabled, 3D Desktop is disabled also, obviously. I remember I saw 3D accel enabled when I attempted to install ATI driver on 32 bit SuSE… How do I enable it? glxgears gives me 3300fps…

    Comment by Alex — May 27, 2006 @ 4:23 am

  85. I forced 3D acceleration recognition (hold shift and double click on “disabled”), enabled 3D desktop, restarted xwin - and it works!!! Wow! BUT now 3d games look funny or crash. They work again if I disable 3d desktop… Is it possible to have both?

    Comment by Alex — May 27, 2006 @ 6:20 am

  86. I have also the problem with the radeon mobility 9000 like GT. Has anybody a solution for it?

    thanks.

    Comment by Jimmy — May 27, 2006 @ 6:56 pm

  87. During my last debug session i have forced fglrxinfo/glxinfo/glxgears to use libGL.so.1.2 by ATI . The probably conflict is between fglrx (the module i suppose) and libGL.so.1.2 by ATI. If i force glx* to use libGL.so.1.2 by mesa everything is ok but is very SLOW (obviously).
    Another interesting thing is the output of:

    “~> export LIBGL_DEBUG=verbose”
    “~> glxinfo”

    ————————-
    name of display: :0.0
    libGL: XF86DRIGetClientDriverName: 8.25.18 atiogl_a (screen 0)
    libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/atiogl_a_dri.so
    fglrx: libGL version does not match - OpenGL module is using glapi fallback
    …..
    (lot of API ERROR)
    …..
    ————————-
    I have searched on google about the last line but i haven’t found any solutions.

    GT

    Comment by GT — May 27, 2006 @ 9:32 pm

  88. It still works (minus games), what a surprise! ;-) My next card will be from linux-friendly manufacturer, that’s for sure.

    Comment by Alex — May 27, 2006 @ 9:57 pm

  89. GT, I think I found a solution.
    I downloaded an old driver:
    (8.14.13:https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.14.13.run)
    extract it : sh ati-driver-installer-8.14.13.run –extract /home/~/extract
    and copy the old libGL.so.1.2 to /usr/lib/fglrx/lib
    cp /home/~/extract/x680/usr/X11R6/lib/libGL.so.1.2 /usr/lib/fglrx/lib
    keep setting from step 7 of this Tuto.
    reboot
    It works for me.I have 2000.000fps with glxgears and fgl_glxgears works fine.
    now i can use perfectly opengl screensavers with my radeon mobility 9000.
    glxinfo and fglrxinfo works too:

    display: :0.0 screen: 0
    OpenGL vendor string: ATI Technologies Inc.
    OpenGL renderer string: MOBILITY/RADEON 9000 DDR Generic
    OpenGL version string: 1.3.1072 (X4.3.0-8.25.1 8)

    let me know if it’s ok for you, GT & Jimmy
    See ya

    Comment by marty — May 28, 2006 @ 5:53 am

  90. I run ati-driver-installer in a Terminal and let him build the Package for SuSE 10.1. There after rpm -Uhv fglrx_6_9_0_SUSE101-8.25.18-1.i386.rpm and then /usr/X11R6/bin/aticonfig –initial. After Systemreboot fglrxinfo:
    display: :0.0 screen: 0
    OpenGL vendor string: ATI Technologies Inc.
    OpenGL renderer string: RADEON X800 PRO Generic
    OpenGL version string: 2.0.5814 (8.25.1 8)

    and with glxgears i get 7537.735 fps.

    System:
    Intel P4 HT
    ATI Radeon x800 Pro.

    The only is, when i reboot or shutdown System there are only colored Stripes on Screen.

    Comment by Andreas — May 28, 2006 @ 2:20 pm

  91. [...] Added: Check also my HowTo on installing ATI drivers on SUSE 10.1 [...]

    Pingback by Linux and Open Source Blog » Hacking SUSE Linux 10.1 — May 28, 2006 @ 2:53 pm

  92. Hi marty - you are the best - your solution works for me also great.

    Thanks a lot - Jimmy

    Comment by Jimmy — May 28, 2006 @ 4:21 pm

  93. Ok, now work perfectly!!

    Thanks a lot marty ;-)

    GT

    Comment by GT — May 28, 2006 @ 11:15 pm

  94. I’m glad for you.but i got something weird.with windowmaker, glxgears gives 2000.000 fps and i can see cube with fgl_glxgears.But with kde glxgears gives 200.000 fps and i can’t see anymore cube with fgl_glxgears (20.000 fps).Is It the same things for you ?

    Comment by marty — May 29, 2006 @ 4:45 am

  95. No..
    …with kde 3.5.2 i get 2500.000 fps with glxgears.

    Have you try with gnome or other window-manager ?

    GT

    Comment by GT — May 29, 2006 @ 11:39 am

  96. Yes, I had.It happen only with KDE

    Comment by marty — May 30, 2006 @ 4:50 am

  97. i have a litle problem! when i run the command ./ati….run ./ati-driver-installer-8.25.18-x86_64.run –buildpkg SuSE/SUSE101-AMD64
    Creating directory fglrx-install
    Verifying archive integrity… All good.
    Uncompressing ATI Proprietary Linux Driver-8.25.18…………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………….
    ==================================================
    ATI Technologies Linux Driver Installer/Packager
    ==================================================
    Generating package: SuSE/SUSE101-AMD64
    Requested package is not supported.
    Removing temporary directory: fglrx-install

    and…
    ./ati-driver-installer-8.25.18-x86_64.run –listpkg
    Creating directory fglrx-install
    Verifying archive integrity… All good.
    Uncompressing ATI Proprietary Linux Driver-8.25.18…………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………….
    ==================================================
    ATI Technologies Linux Driver Installer/Packager
    ==================================================
    List of generatable packages:

    Package Maintainer(s): Aric Cyr
    Status: Verified
    Debian Packages:
    Debian/woody
    Debian/oldstable
    Debian/sarge
    Debian/stable
    Debian/sid
    Debian/unstable
    Debian/etch
    Debian/testing

    Package Maintainer(s): Arnaud Patard
    Status: Verified
    Mandriva Packages:
    Mandriva/2006

    Package Maintainer(s): Aric Cyr
    Status: Verified
    Ubuntu Packages:
    Ubuntu/warty
    Ubuntu/4.10
    Ubuntu/hoary
    Ubuntu/5.04
    Ubuntu/breezy
    Ubuntu/5.10
    Ubuntu/dapper
    Ubuntu/6.06

    For example, to build a Debian Etch package, run the following:
    % ./ati-driver-installer–.run –buildpkg Debian/etch

    Removing temporary directory: fglrx-install
    please tell me what to do…

    Comment by mike — May 30, 2006 @ 10:02 pm

  98. I gotta say that I’m disappointed with ATI. I would really like to believe that it’s my lack of knowledge but 2 weeks now I’ve read many Kbytes of text made many clean installs trying different variations of the ati driver.
    I have Suse 10.1 x86_64 AMD64 with ati x1600 512mb pci(the board is asus but the chipset is ati)

    When I try to run the xserver with sax2 -r -m 0=fglrx it always fails to load and at /var/log/SaX.log it tells me
    (II) fglrx(0): Display1: No EDID information from DDC.
    (WW) fglrx(0): Specified desktop setup not supported: 8

    At first I thought it was a compile problem with the rpm but for Module.symvers error missing, I googled it and found a workaround but still nothing. I’ve read at the ATI site that you have to compile as module the AGP and not load it into the kernel. Done that ..nothing

    Also I’ve noticed that at step 6 (rpm install) I don’t get messages for modules like agpgart, agp3 and so on. I only get this:

    LD /usr/src/kernel-modules/fglrx/built-in.o
    CC [M] /usr/src/kernel-modules/fglrx/firegl_public.o
    LD [M] /usr/src/kernel-modules/fglrx/fglrx.o
    Building modules, stage 2.
    MODPOST
    CC /usr/src/kernel-modules/fglrx/fglrx.mod.o
    LD [M] /usr/src/kernel-modules/fglrx/fglrx.ko
    make: Leaving directory `/usr/src/linux-2.6.16.13-4′
    make: Entering directory `/usr/src/linux-2.6.16.13-4′
    INSTALL /usr/src/kernel-modules/fglrx/fglrx.ko
    DEPMOD 2.6.16.13-4-default
    make: Leaving directory `/usr/src/linux-2.6.16.13-4′

    any suggestions are really welcome

    Comment by vangelis — May 30, 2006 @ 11:15 pm

  99. hi again! I was in a hurry last day and I didn’t have the time to ask if the driver dosen’t have SuSE package support where can i get the version that E@zyVG used… because i’ve downloaded the exact version and it says the same… only debian, mandriva and ubuntu package support.

    Comment by Mike — May 31, 2006 @ 10:50 am

  100. hey easy, i gave up installing ati drivers in my amd 64 x 2 machine. I brought a new case and put my old computer together and now I installed the ATI drivers for 32 bit. My system is
    AMD Barton 2600
    Saphire ATI Radeon 9600 Pro.
    80 Gb HD
    512 MB PC 2700 Ram
    NForce2 Chipset Motherboard

    My question is how do I get Xgl compiz working on that machine ?. The gnome 3d desktop for compiz -xgl says my card is not in the database. If you know, it will be of great help.. Thanx a lot :)
    In the mean time, I will look it up in the compiz forums too :)

    Bye
    Lava

    Comment by Lava — May 31, 2006 @ 12:17 pm

  101. I tried Xgl , but switched back, as I want it to become more usable on KDE, especially to see Compiz Control Panel for KDE being developed. On Gnome it’s great. If you wanna try it out, check this comprehensive guide with links to more info:

    http://en.opensuse.org/Using_Xgl_on_SUSE_Linux#Enabling_3D_Acceleration_with_ATI_or_NVIDIA_cards

    Comment by E@zyVG — May 31, 2006 @ 1:03 pm

  102. :)) hi again! I don’t know, but by some mracle I managed to get my ati driver working, horray! after 5 days of pain…:)) 10x for the tutorial verry helpful! bye

    Comment by mike — May 31, 2006 @ 3:23 pm

  103. Im having the same problem as above
    amd 1800
    ati radeon 9600 SE
    suse 10.1
    glxinfo | grep direct direct rendering: yes
    glxgears look good but when i start a 3d game the screen freezes hard restart
    is needed.

    Comment by John — May 31, 2006 @ 5:01 pm

  104. when I have seen to run the screensaver in gl they are put to me to cry , they were years that I tried of having the 3d in linux
    i will remember of you in my memories

    Comment by carmen — May 31, 2006 @ 5:49 pm

  105. Well still can’t get it to work with my x1800xt so i sold the card on ebay and got a 7900GT and guess what it works, its amazing what a company can accomplish provided it puts in the resources into driver development for Linux. Don’t think i will be buying ATI again and i’ve been with them for 6 years.

    Comment by Steve — June 1, 2006 @ 6:18 am

  106. http://www.ground-impact.com/libGL.so.1.2

    Right click it and save target as and save it to /usr/lib/fglrx/lib

    Comment by E@zyVG — June 1, 2006 @ 12:06 pm

  107. has any one got this working with a X1800xt 512mb ram in a system with a dual core AMD processor?

    Comment by john — June 1, 2006 @ 3:16 pm

  108. ATTN: SuSU 10.1 | Xgl | ATI Cards | KDE

    I’ve been working at this for a while, hard editing everywhere throughout the system trying go get Xgl to run. I always ran into the error where starting x would result in the .X0-lock error. I tried everything from runnin init 3 to totally shut down x then bringin back up level 5 and then deleting the .X0-lock file from the /tmp directory… all it gave me was a very broken GUI; tearing like crazy.

    I’ve found two good ways around this ( I prefer the later [#2])

    #1)

    [ Credit goes to Chromakode at http://tectonic.co.za/view.php?id=916 ]
    *note that he edits the ~/.Xsession file but SuSE doesn’t look there, it looks at ~/.xinitrc

    Check out that site for the gist, but here is what I did:

    I edited xorg.conf like so:

    Option “NoFlip” “True”
    Option “UseInternalAGPGART” “no”
    Option “KernelModuleParm” “agplock=0″

    Then I pasted this code into ~/.xinitrc with a little chmod +x ~/.xinitrc action

    #!/bin/sh
    # Start up Xgl, compiz, and KDE
    # Run Xgl server on :1, on top of normal X
    Xgl :1 -fullscreen -ac -accel xv -accel glx:pbuffer &
    # Tell subsequent X programs to access the Xgl server at :1
    DISPLAY=:1
    # Start Compiz window manager
    kde-window-decorator &
    compiz gconf decoration wobbly fade minimize cube rotate zoom scale move resize place menu switcher &
    # Start GNOME
    exec kde-session

    It works! Boots up great in KDE. Rendering is definitely slower; hopefully that will be resolved soon. If anyone has any tips on speeding up the acceleration, share it please!

    /#1

    #2)Credit goes to noiesmo over at the compiz.net forums:

    create a file called /usr/local/bin/compiz.sh

    #!/bin/sh
    # Start up Xgl, compiz
    # Run Xgl server on :1, on top of normal X
    /usr/bin/Xgl :1 -fullscreen -ac -accel glx:pbuffer -accel xv:pbuffer &
    # Tell subsequent X programs to access the Xgl server at :1
    DISPLAY=:1
    # Start Compiz window manager
    sleep 5
    gnome-window-decorator &
    compiz –replace gconf &
    # Start KDE
    exec startkde

    also create a file called /usr/share/xsessions/compiz.desktop

    [Desktop Entry]
    Encoding=UTF-8
    Name=Compiz
    Comment=Candy store
    Exec=/usr/local/bin/compiz.sh
    Icon=
    Type=Application

    The compiz.desktop file will add an entry to the GDM Sessions where you can select compiz.

    [Desktop Entry]
    Encoding=UTF-8
    Name=Compiz
    Comment=Candy store
    Exec=/usr/local/bin/compiz.sh
    Icon=
    Type=Application
    This will add an entry to the GDM Sessions where you can select Compiz or whatever you name it. I really like this one because I can select regular KDE or KDE with Xgl from login.

    /#2

    Comment by Erik Fritsch — June 1, 2006 @ 6:43 pm

  109. What ‘flag’ do I use on the ‘buildpkg’ for Intel 64 bit processor (Pendium D)? I see notes in here for AMD (-AMD64) and for Intel 32 bit (-IA32), but nothing for Intel 64 bit. Is it -IA64 or something else?

    Comment by John — June 1, 2006 @ 10:05 pm

  110. Intels 64 bit is AMD64 licensed, hence if you want to compile 64bit version of drivers then use AMD64.

    Comment by E@zyVG — June 1, 2006 @ 10:57 pm

  111. I get this Warning and my install doesn’t seem to work (using RPM) after adding libexpat for 10.1:
    WARNING: could not find /usr/src/kernel-modules/fglrx/.libfglrx_ip.a.GCC4.cmd fo r /usr/src/kernel-modules/fglrx/libfglrx_ip.a.GCC4

    Would this cause a problem?

    Comment by Kurt Peters — June 2, 2006 @ 6:00 am

  112. I just uninstalled and reinstalled ATI driver without touching anything else. (I completed all the steps above once). And it now works completely normal, 3D is recognized and enabled, xgl works, 3d games start in a window or complain but do not crash. Oh, boy…

    But is it normal for Radeon 200 (something like R200QL) to give 2500 fps in glxgears? Do I need a new card to get 6000 fps? ;-)

    Comment by Alex — June 2, 2006 @ 4:59 pm

  113. It is ATI’s shame I have been trying to install this card for at least 6 hours and still nothing it is goin to be my 3 reinstall. I DO hope they reading this posts and fix this!
    My config:
    ATI RADEON X 1600 PRO
    ASUS motherboard
    AMD 3200+ 64

    When I start sax2 it just drop me back to the command line. I’m VERY disappointed with this! Under windows the installation took about 5 mins. WHY????

    Comment by Boni — June 3, 2006 @ 1:35 am

  114. Thank you for this howto. It works fine on my computer:
    SUSE 10.1
    AMD +3000
    radeon x300
    nForce4

    Comment by Karlos — June 3, 2006 @ 2:55 pm

  115. Fucking great! This ruined my Ati card totally. It got toasted…

    Nice

    Comment by Mahr — June 4, 2006 @ 8:09 pm

  116. Drivers cannot toast your video card, so please be carefull with your words, or else seek help somewhere else … hope you got my point. Next time your comments will be deleted.

    Comment by E@zyVG — June 5, 2006 @ 1:07 am

  117. I’m having the same problem as Mike back in comment #97, but I don’t see a response to that problem (since it appears he got around it somehow). I try building the package in Step 5 of the instructions, but then get…

    Generating package: SuSE/SUSE101-AMD64
    Requested package is not supported.

    Why is the package not supported? What do I do to get around the problem?

    I’m running:
    * Intel Pentium D 930 (3.0 GHz, Dual Core)
    * ASUS motherboard with Intel 975x chipset (latest Intel chipset)
    * ATI X1900GT graphics card
    * SUSE 10.1

    Sorry to sound so lost, but I am. If I were having a Windows problem, I could troubleshoot with the best of them, but this is my first adventure into the world of Linux and I’m feeling extremely helpless. :-)

    Thanks — John

    Comment by John — June 5, 2006 @ 4:18 pm

  118. btw - my ATI card is PCI-E (not AGP), if that makes a difference in any way

    Comment by John — June 5, 2006 @ 4:20 pm

  119. I get this Warning and my install doesn’t seem to work (using RPM) after adding libexpat for 10.1:
    WARNING: could not find /usr/src/kernel-modules/fglrx/.libfglrx_ip.a.GCC4.cmd for /usr/src/kernel-modules/fglrx/libfglrx_ip.a.GCC4
    What Would this cause a problem?
    Comment by Kurt Peters — June 2, 2006 @ 6:00 am

    i gets this same problem too.
    does anyone know how to fix this?? i have an ati x1600 pro 512mb agp video card.
    i really need this fixed. i’m new to linux. only been using it for about 1 week and this is really making me mad. i wanted something better than windows. and i don’t want to have to buy a newer Nvidia. i’ve got a Nvidia FX 5200. but thats old and i want to use my ati x1600. please… don’t make me quit and go back to MICROSOFT WINDOWS!!!

    Comment by phinux — June 6, 2006 @ 8:39 am

  120. Update from my comments/questions yesterday… I figured out why the package wouldn’t make. I had placed the downloaded ATI .run file in a folder named “Temp (for install)”. I’m not sure if it was the spaces of the parenthesis, but the folder name was the problem. Once I moved it to a directory called simply “Temp” it made the package fine.

    [Side note: The odd thing is that when I did a --listpkg on it, several of the package options would enumerate fine even with the first folder name, but the SUSE packages, and a few others, would not. Interesting.]

    So now even though I got the package made, I still can’t get the drivers installed and working correctly. Arrrggghhh! I was doing it last night and can’t recall now exactly what the error was, bu tI can’t get the sax2 config step to work right. It tries to do something, then aborts and after doing that, doing a kde or startx both end in an abort failure. If I run sax2 again and set it back to the MESA drivers everything starts again.

    I’ve tried the uninstall step, then the reinstall and still get the same thing. I think I probably screwed things up with all my various failed attempts, so tonight I will delete everthing, do a fresh SUSE install, and start from scratch again. Wish me luck!

    Comment by John — June 6, 2006 @ 6:03 pm

  121. Regarding the color corrupted screen thing mentioned in some of the above posts (including my own). I’ve read somewhere that the drivers fail to properly detect modelines that are compatible with some LCD screens. You can correct that by adding appropriate “Modeline” lines into your “Monitor” section of the xorg.conf file (different monitors have different modelines). I did that and most of the corruption went away (there still is some, but that’s probably because I used wrong modeline parameters). You can find modeline generators by googling. But. Even if this is the solution for this problem it doesn’t solve much… When I try to use glxgears or glxinfo I get the API ERROR (which is also mentioned above).
    I hope someone finds this useful. And if anyone tries this modeline thing, do be careful. Wrong settings can damage your screen.
    I think I’ll give up on this for now. ATI and Linux just don’t get along. ;_;

    Comment by Preditcon — June 6, 2006 @ 9:14 pm

  122. Vichtar, thank you very much for your instructions. Unfortunately they don’t work for me. The last step (10) sax stops and gives the following text at the end of sax.log:

    (WW) fglrx(0): Specified desktop setup not supported: 8

    *** If unresolved symbols were reported above, they might not
    *** be the reason for the server aborting.

    Backtrace:
    0: /usr/sbin/xw(xf86SigHandler+0×7e) [0x44866e]
    1: /lib64/libc.so.6 [0x2ab2f325db20]
    2: /lib64/libc.so.6(memset+0×82) [0x2ab2f32a1b72]
    3: /usr/X11R6/lib64/modules/libvbe.so(VBEGetModeInfo+0×19) [0x2ab2f56f8ee9]
    4: /usr/X11R6/lib64/modules/drivers/fglrx_drv.so [0x2ab2f468ca9c]
    5: /usr/X11R6/lib64/modules/drivers/fglrx_drv.so(SetAdapterMapping+0×101) [0x2ab2f468a771]
    6: /usr/X11R6/lib64/modules/drivers/fglrx_drv.so(R200PreInitDAL+0×2a2) [0x2ab2f468c2b2]
    7: /usr/X11R6/lib64/modules/drivers/fglrx_drv.so(R200PreInit+0×616) [0x2ab2f4663cd6]
    8: /usr/sbin/xw(InitOutput+0×9ec) [0x43251c]
    9: /usr/sbin/xw(main+0×21a) [0x49512a]
    10: /lib64/libc.so.6(__libc_start_main+0xf4) [0x2ab2f324b154]
    11: /usr/sbin/xw [0x430cc9]

    Fatal server error:
    Caught signal 11. Server aborting

    I’m about to give up and return the card (X1600 Pro Asus version), swapping it for a better supported one :-(

    Comment by Sebastià — June 7, 2006 @ 2:50 am

  123. I got the exact same error funny thing is these drivers seem to work fine with the x800 series cards from what i have tested but as soon as you hit the x1000 models SOME of them are causing problems; or should I say these drivers are causing problems working with those cards. In the mean time i’m in GREEN pastures until ATI sort their act out and start putting more effort and testing into these drivers they aren’t release worthy. My advice is leave it for now or try another distro of linux and see if you have any luck such as Fedora or Unbuntu or Debian.

    Comment by Steve — June 7, 2006 @ 5:14 pm

  124. Ok! I called ATI tech support where I spoke with a tech support representative. He explained me that they offically do NOT support linux. The driver works on an “as is” base.
    Now I’m totally disappointed… I bought radeon x1600 pro
    pci express trying to install it under suse 10.1 on AMD64.
    Any idea?

    Comment by Boni — June 7, 2006 @ 9:05 pm

  125. They have one more day tomorrow i bring it back to the shop where i bought it :)

    Comment by Boni — June 7, 2006 @ 9:08 pm

  126. I have tried several instructions and reinstallations to get my Asus EAX1600XT to work but with Suse 10.1 but so far unsuccesfull. Your instruction differs a little with the “just in case” instructions so I’m going for it again tonight.

    Thnx.

    Comment by avdh — June 8, 2006 @ 2:47 pm

  127. hope you had some luck but in the mean time i think from this response:

    Ok! I called ATI tech support where I spoke with a tech support representative. He explained me that they offically do NOT support linux. The driver works on an “as is” base.
    Now I’m totally disappointed… I bought radeon x1600 pro
    pci express trying to install it under suse 10.1 on AMD64.
    Any idea?

    Its not worth buying ATI if you use linux regardless if ATi are better then Nvidia or Visa Versa. Truth is ATi has poor linux support Nvidia has “better” linux support. Since i’m not bothered about Windows its pointless trying to spend hours getting a card which isn’t supported on your OS to work with it hence its time to consider another GFX card company.

    Comment by Steve — June 8, 2006 @ 4:56 pm

  128. [...] [Update] From the comments at http://linux.wordpress.com/2006/05/12/suse-101-ati-drivers-installation I could gather that I am not the only one facing the “switching-to-text-console-problem”. It looks like an ATI BUG (a known issue according to release note) : “Toggling between console mode and X Server graphical mode may result in a system hang. Further details can be found in topic number 737-22058″ [...]

    Pingback by Tomorrow’s Classroom @ the Eichendorff Highschool » Quoth the raven, “never more!” — June 9, 2006 @ 12:32 am

  129. It looks like 8.25.18 version does nothing to solve the blank screen/freeze problem with a RADEON XPRESS 200 G. All the graphics xgl features work perfectly, I just love the desktop cube and semi-transparent windows. But any command that switches from the X display freezes the computer with a blank screen. I can not even do a clean reboot. Disabling the 3D features does not help. It looks like I will have to install an older driver, until ATI gets their act together and write something that works, or open sources a driver so we can fix it ourselves.

    Comment by Bill — June 9, 2006 @ 5:21 am

  130. nope. no go. din work for Radeon X700.

    Comment by Mr.Bear — June 9, 2006 @ 4:54 pm

  131. do not work for Radeon X 1600 pro.
    other hardware spec same

    Comment by g4g33 — June 10, 2006 @ 9:36 am

  132. This was my first and last ati card, I’ll never use it again.
    its in an hp nx6125

    Rather buy nvidia
    I get an spectacular 5 fps in 1024×768 ut2k4 with the hardware drivers.
    I’m sure that my fx5200 will give better performance.

    Comment by Leon Lessing — June 12, 2006 @ 1:47 am

  133. This howto has worked for me, I have an ATI Radeon 9600 Pro and my kernel is 2.6.16.13-4-bigsmp .
    The only thing that did not happen in the same way that this howto says is that in my /etc/X11/xorg.conf file, I don’t have that line you marked: Option “KernelModuleParm” “agplock=0″ . Everything seems to work, so it doesn’t matter.

    Thank you E@zyVG (I also could get my wireless Ralink RT2500 wifi card with your howto: “SUSE 10.1 and RT2500 Wi-Fi”). Thank you, thank you, thank you :)

    Wanchu

    Comment by Wanchu — June 12, 2006 @ 12:38 pm

  134. For me also driver 8.25.18 does not work on suse 10.1+dual core centrino+radeon x1400.
    After running sax 2 or rebooting without sax2 i get a blank screen.
    I tried driver 8.24.x and this one works but just on external monitor on 60Hz but lcd display of notebook is weird up as thom says in 32.
    At the moment i use Suse 10.0 whwere everything works fine with actual driver.

    regards

    Comment by Erwin — June 12, 2006 @ 6:48 pm

  135. beautiful online information center. greatest work… thanks

    Comment by bert — June 14, 2006 @ 3:56 am

  136. It’s doesn’t work on ati X1600Pro
    on AMD64 + DFI lanparty :(
    So, we have to wait to the next release of the driver

    Comment by Marco — June 14, 2006 @ 12:05 pm

  137. After following these instructions I, like some other users, am getting a load of API ERRORs when I do fglxinfo or try to run glxgears. However, if I log in as su it will run, and it shows that it’s suing the mesa drivers. When not logged in as su, it seems to try to use the ATI drivers I installed, but something clearly isn’t right. Can anybody help?

    Comment by Ian — June 14, 2006 @ 9:02 pm

  138. Hello!

    Here is the problem I experience: every time I execute “sax2 -r -m 0=flgrx” in “init 3″ mode, I just got a black screen and that’s it! I have to hard reboot the computer by pressing the power button :( After building the rpm, the installation of the driver went as follow:

    > less /usr/share/fglrx/fglrx-install.log

    /tmp/fglrx
    Package fglrx64_6_9_0_SUSE101-8.25.18-1.x86_64.rpm has been successfully generated

    > rpm -ivh fglrx64_6_9_0_SUSE101-8.25.18-1.x86_64.rpm

    Preparing… ########################################### [100%]
    1:fglrx64_6_9_0_SUSE101 ########################################### [100%]
    /usr/src/kernel-modules/fglrx /
    make: Entering directory `/usr/src/linux-2.6.16.13-4-obj/x86_64/default’
    make -C ../../../linux-2.6.16.13-4 O=../linux-2.6.16.13-4-obj/x86_64/default
    LD /usr/src/kernel-modules/fglrx/built-in.o
    CC [M] /usr/src/kernel-modules/fglrx/firegl_public.o
    /usr/src/kernel-modules/fglrx/firegl_public.c: In function ‘firegl_put_user_ptr’:
    /usr/src/kernel-modules/fglrx/firegl_public.c:1246: warning: cast from pointer to integer of different size
    /usr/src/kernel-modules/fglrx/firegl_public.c:1246: warning: cast from pointer to integer of different size
    /usr/src/kernel-modules/fglrx/firegl_public.c:1246: warning: cast from pointer to integer of different size
    /usr/src/kernel-modules/fglrx/firegl_public.c:1246: warning: cast from pointer to integer of different size
    /usr/src/kernel-modules/fglrx/firegl_public.c: In function ‘__ke_unregister_ioctl32_conversion’:
    /usr/src/kernel-modules/fglrx/firegl_public.c:2406: warning: ‘return’ with a value, in function returning void
    LD [M] /usr/src/kernel-modules/fglrx/fglrx.o
    Building modules, stage 2.
    MODPOST
    WARNING: could not find /usr/src/kernel-modules/fglrx/.libfglrx_ip.a.GCC4.cmd for /usr/src/kernel-modules/fglrx/libfglrx_ip.a.GCC4
    CC /usr/src/kernel-modules/fglrx/fglrx.mod.o
    LD [M] /usr/src/kernel-modules/fglrx/fglrx.ko
    make: Leaving directory `/usr/src/linux-2.6.16.13-4-obj/x86_64/default’
    make: Entering directory `/usr/src/linux-2.6.16.13-4-obj/x86_64/default’
    make -C ../../../linux-2.6.16.13-4 O=../linux-2.6.16.13-4-obj/x86_64/default modules_install
    INSTALL /usr/src/kernel-modules/fglrx/fglrx.ko
    DEPMOD 2.6.16.13-4-default
    make: Leaving directory `/usr/src/linux-2.6.16.13-4-obj/x86_64/default’
    /

    *************************************************************
    Please read “/usr/share/doc/packages/fglrx/README.SuSE” for
    configuration details when using SaX2.
    *************************************************************

    Now checking the /usr/share/doc/packages/fglrx/ for sax2-profile, I find nothing. Then executing fglrx-kernel-build.sh doesn’t show the “/usr/src/kernel-modules/fglrx/firegl_public.c: …” warnings anymore and I have already the sax2-profile file generated. So I proceed with:

    > sax2 -r -m 0=fglrx -b /usr/share/doc/packages/fglrx/sax2-profile

    SaX: initializing please wait…
    SaX: your current configuration will not be read in

    SaX: no X-Server is running
    SaX: will start own server if needed
    SPP: prepare device [0] profile: FireGL
    SPP: prepare device [1] profile: synaptics
    SPP: calling device [1] profile script: synaptics
    SPP: including prepared profile(s)…
    SPP: prepare device [0] profile: sax2-profile
    SPP: profile will add new section(s) -> moving: 1
    SPP: including prepared profile(s)…

    SaX: startup

    ServerLayout -> all -> Screen -> 0 -> top =
    ^ line : syntax error: invalid KEY in LValue specification or invalid assigment: expected LValue=RValue with LValue=KEY sequence and RValue=STRING
    ServerLayout -> all -> Screen -> 0 -> bottom =
    ^ line : syntax error: invalid KEY in LValue specification or invalid assigment: expected LValue=RValue with LValue=KEY sequence and RValue=STRING
    ServerLayout -> all -> Screen -> 0 -> left =
    ^ line : syntax error: invalid KEY in LValue specification or invalid assigment: expected LValue=RValue with LValue=KEY sequence and RValue=STRING
    ServerLayout -> all -> Screen -> 0 -> right =
    ^ line : syntax error: invalid KEY in LValue specification or invalid assigment: expected LValue=RValue with LValue=KEY sequence and RValue=STRING

    The result is that no sax2 configuration window opens, and this far I could get. I started init 5 because I couldn’t run fglrxinfo or glxinfo (can’t open display) in init 3 mode and here is the output:

    > fglxinfo

    Xlib: extension “XFree86-DRI” missing on display “:0.0″.
    display: :0.0 screen: 0
    OpenGL vendor string: Mesa project: http://www.mesa3d.org
    OpenGL renderer string: Mesa GLX Indirect
    OpenGL version string: 1.2 (1.5 Mesa 6.4.1)

    Now I tried to execute the sax2 command with -b /usr/share/doc/packages/fglrx/sax2-profile and got the same meassage as above without seening the sax2 window. However, executing only “sax2 -r -m 0=fglrx” poped up the sax2 window without any complains. So now I saved the new xorg.xonf. After OK, if I hit the button Test the screen turn into black screen and again nothing, I have to hard reboot and replace the xorg.conf file with the original one. I really don’t know what more to do!

    Here are the specifications of my laptop:
    HP dv5000, AMD Turion 64 ML, ATI Radeon Xpress 200m, SUSE 10.1 (64)

    I would really like to run the Xgl on it.

    Any help is highly appreciated!
    iso

    Comment by iso — June 15, 2006 @ 3:59 am

  139. Well I’ve basically given up on this and have come to the conclusion that the driver’s will not work on a Dual Core CPU running a NEW Ati Card (Mine’s a x1900 xtx) on Suse x64. I’m done with linux until Suse 10.2, what a shame since I’ve been using linux since 9.1… All my games run great on windows…bleh…

    Comment by Thom — June 15, 2006 @ 8:31 pm

  140. I ended up going back to SuSE 10.0 and installed the ATI drivers. Everything is working now.
    It works better overall anyway. 10.1 had problems with my network and 10.0 doesn’t.
    Either SuSE 10.1 has some serious bugs or ATI needs to update to use the new kernel.

    Comment by swag — June 17, 2006 @ 6:53 pm

  141. I got a Suse 10.1 smp x64 on x2 4400 1024DDR600 with x1900xt 512GDDR, my card is detected to have only 256M GDDR and like many of you i got something like
    Backtrace:
    0: /usr/sbin/xw(xf86SigHandler+0×7e) [0×44866e]
    1: /lib64/libc.so.6 [0×2ab2f325db20]
    2: /lib64/libc.so.6(memset+0×82) [0×2ab2f32a1b72]
    3: /usr/X11R6/lib64/modules/libvbe.so(VBEGetModeInfo+0×19) [0×2ab2f56f8ee9]
    4: /usr/X11R6/lib64/modules/drivers/fglrx_drv.so [0×2ab2f468ca9c]
    5: /usr/X11R6/lib64/modules/drivers/fglrx_drv.so(SetAdapterMapping+0×101) [0×2ab2f468a771]
    6: /usr/X11R6/lib64/modules/drivers/fglrx_drv.so(R200PreInitDAL+0×2a2) [0×2ab2f468c2b2]
    7: /usr/X11R6/lib64/modules/drivers/fglrx_drv.so(R200PreInit+0×616) [0×2ab2f4663cd6]
    8: /usr/sbin/xw(InitOutput+0×9ec) [0×43251c]
    9: /usr/sbin/xw(main+0×21a) [0×49512a]
    10: /lib64/libc.so.6(__libc_start_main+0xf4) [0×2ab2f324b154]
    11: /usr/sbin/xw [0×430cc9]

    Fatal server error:
    Caught signal 11. Server aborting

    i tought it didn’t like to have a dual screen with res (1600×1200 on 2080ux+ and 1680×1050 on wgx²)
    but after a clean install with only the wgx², exactly same error: install without a bug but error on Sax -r -m 0=fglrx

    would you have some ideas?

    Xag

    Comment by xagire — June 17, 2006 @ 7:44 pm

  142. with a8n32-sli as motherboard seems to be part of the problem

    Comment by xagire — June 17, 2006 @