[SOLVED] ati driver 32-bit compatibility for Slackware 64-bit multilib?
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I just verified that for slackware64-current (and so at this time it would be applicable to slackware64-13.0) the ati installer for fglrx (catalyst) works without changing kernel or adding any 32 bit anything.
Both methods worked. Those being:
1) simply running sh ati*run (9.9 for me) or
2) running sh ati*run --buildpkg Slackware/All and then installing packages.
Keep in mind you should rmmod radeon and drm and then modprobe fglrx. If intending to continue running fglrx you should rename /lib/modules/... radeon.ko and drm.ko so they do not load on reboots.
If you go with option 1 above, the auto installer seems to create the necessary altered /etc/X11/xorg.conf. If you run option 2 you need to install/move/create this yourself.
This is for an r600 (hd3200). I realize some support dropped for earlier cards at 9.3 and above instructions do not apply.
9.3 is the last version for non HD?xxx cards (for the 9550 through the x1900, roughly). If you are using one of those GPUs you should be using the open source driver. If you are using an HD2xxx or higher, you can use 10.1 from the AMD website.
Well I can assure you that catalyst 9.3 will not work on Slackware 13.0, 32-bit or 64-bit. Again, if your card is supported by the fglrx driver (and you haven't actually told us what card you are using), you should download the correct version from the AMD website. 10.1 is the only one to support kernel 2.6.32.* so far, from what I have read.
Right, that's a non-HD card and, therefore, the last catalyst version to work on that GPU is 9.3. Which will not work with Slackware 13.0. If you absolutely must use catalyst, you will need to stick with an older distribution. The open source drivers, however, support both 2D and 3D acceleration on that GPU (I would recommend radeon instead of radeonhd).
Yep. DRI/3D should work out-of-the-box in Slackware 13.0, in fact. There was a bug in Mesa last summer that impacted 3D performance on Express GPUs that might be present in the Mesa version in 13.0, but I'm not 100% sure of that.