|
Smacking in the head part MUST work for everyone! :D
|
Quote:
|
Ermmm i dunno too be honest all i know is in one of the readmes it tells you how. I suggest running the .run in Konsole though.
|
Quote:
|
Yes I saw it. RPM package of X.org ;)
|
Quote:
|
Quote:
"Direct rendering - no" and glxgears are verrrrry slooooow |
Are you using suse 9.3?
I can try to help, but I'm pretty new to Linux. I'm amazed I even got MINE working. Did you update the linux kernel? Did you uninstall EVERYTHING related to fglrx? Especially the km_fglrx packages? And then make sure they don't get installed again? Did you install the'fglrx_6_8_0-8.16.20-1.i386.rpm' with yast? Did you then open a console where you saved 'ati-driver-installer-8.16.20-i386.run', set file permissions and then run it from within the console? Did you go into your usr/X11R6/bin and run fglrxconfig? And then reboot? (You probably don't have to reboot, just restart x, but I rebooted to be safe cause i'm a noob) |
Quote:
The only reason you would run the installer and do an RPM is if you choose to build the distribution specific RPM with the installer. Note: Creating a distirbution specific RPM is the recommended method because it put all files, particularly documentation (which can be distro specific), in the correct folders. You can also run fglrxconfig without going into /usr/X11R6/bin. As an alternative to fglrxconfig you can do the following (Also the more correct way to do it in SuSE): Code:
su |
Oh... ok! I guess I was just following instructions from earlier in the post (which worked for me, BTW):
Quote:
...except for whatever reason, the installer never actually seemed to INSTALL drivers. This was MY experience: I ran the installer, and after installing by the generic install method ran fglrxconfig, rebooted and still had no 3D. That's when I did a search in yast for ati drivers (fglrx) and i realized, for whatever reason, there were no actual drivers installed. So that's when I installed the rpm i downloaded from ati and restarted, and everything worked. Wish I would have known there was a better way to do it. |
My latest experience, which dates from yesterday, is also that the .run file does not install the drivers correctly.
For SuSE 10.1, the steps I've followed are: 1) Download the latest drivers from ATI. 2) From a console window, change to runmode 3 : init 3 3) Uninstall everything ATI-related from the system : rpm -qa |grep fglr | xargs rpm -e 4) Execute the .run file with the --buildpkg option: ./ati-driver-installer-8.18.6-XXX.run --buildpkg PKG Replace XXX by the architecture of your system (i386 for 32 bits or x86_64 for 64-bit PCs). Also replace PKG by the distro you are currently using (if you execute the .run with the --get-supported option you will see a list of supported distros). For example, since I'm running SuSE 10 in an Athlon64, I've used: ./ati-driver-installer-8.18.6-x86_64.run --buildpkg SuSE/SUSE100-AMD64 5) Install the package, using: rpm -Uhv PKG where PKG is the rpm file that you've just created (ls *.rpm will show you the list of rpms) 6) Configure: fglrxconfig Use the default options, except for mouse,kbd and language. 7) If using SuSE, you'll find a file called README.SuSE in /usr/share/doc/packages/fglrx/ Run the sax command as described in the file. It should look something like this: sax2 -r -m 0=fglrx -b /usr/.... (the path continues, but I can't remember it) 8) Reboot 9) fglrxinfo should tell you that your using the ATI card for 3D acceleration (instead of the Mesa drivers). If it doesn't work, go back to step 6 and try using the external AGPGART driver (it is one of the last options proposed by fglrxconfig). Note: I've read that some sites (even SuSE) recommend to patch the fglrx sources for x86_64 systems using a .diff file. Since the last release of the ATI drivers, this is no longer necessary (the sources already take into account the fact that some headers are in other directories). I hope that this helps someone! |
| All times are GMT -5. The time now is 09:06 AM. |