Slackware 12.1 and ATI Drivers

itz2000 · 05-09-2008, 12:13 PM

Today I've installed Slackware 12.1 instead of 12.0 which I had

But I've got a problem with the ati drivers, downloaded from :
http://ati.amd.com/support/drivers/l...ux-radeon.html

Code:

root@Zukmeister:/home/zuki/Desktop# ./ati-driver-installer-8-4-x86.x86_64.run --buildpkg Slackware/All
Created directory fglrx-install.m9cKah
Verifying archive integrity... All good.
Uncompressing ATI Proprietary Linux Driver-8.476.....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
==================================================
 ATI Technologies Linux Driver Installer/Packager
==================================================
Generating package: Slackware/All

ATI SlackBuild Ver. 1.2.0
--------------------------------------------
by: Emanuele Tomasi <tomasiATcli.di.unipi.it>
    Ezio Ghibaudo<ekxiusATgmail.com>
    Federico Rota<federico.rota01ATgmail.com>

ATI module generator V 2.0
==========================
initializing...
Error:
kernel includes at /lib/modules/2.6.24.5/build/include do not match current kernel.
they are versioned as ""
instead of "2.6.24.5".
you might need to adjust your symlinks:
- /usr/include
- /usr/src/linux
Error -> I don't have make module
Removing temporary directory: fglrx-install.m9cKah

/usr/src/linux points to /usr/src/linux-2.6.24.5

I've Googled it and found out that it happened to other people as-well but havn't seen a working solution.

Thanks for your help!

symatic · 05-09-2008, 01:54 PM

what kernel are you running? It is using the none smp "/lib/modules". I'm gonna assume you are using the non-smp? I built it using the generic-smp kernel and it works without any problems. If you are using the non-smp you will have to /extra on the dvd/cd and install/patch the kernel source. I don't imagine you are using that kernel on purpose, but that is what I am assuming.

T3slider · 05-09-2008, 05:07 PM

Quote:

Originally Posted by CHANGES_AND_HINTS.TXT

As stated earlier, it is recommended that you use one of the generic kernels
rather than the huge kernels; the huge kernels are primarily intended as
"installer" and "emergency" kernels in case you forget to make an initrd.
For most systems, you should use the generic SMP kernel if it will run,
even if your system is not SMP-capable. Some newer hardware needs the
local APIC enabled in the SMP kernel, and theoretically there should not be
a performance penalty with using the SMP-capable kernel on a uniprocessor
machine, as the SMP kernel tests for this and makes necessary adjustments.
Furthermore, the kernel sources shipped with Slackware are configured for
SMP usage, so you won't have to modify those to build external modules
(such as NVidia or ATI proprietary drivers) if you use the SMP kernel.

If you decide to use one of the non-SMP kernels, you will need to follow the
instructions in /extra/linux-2.6.24.5-nosmp-sdk/README.TXT to modify your
kernel sources for non-SMP usage. Note that this only applies if you are
using the Slackware-provided non-SMP kernel - if you build a custom kernel,
the symlinks at /lib/modules/$(uname -r)/{build,source} will point to the
correct kernel source so long as you don't (re)move it.

Follow symatic's advice (or switch to the generic-smp kernel)

itz2000 · 05-09-2008, 08:20 PM

I did in-fact installed the huge.s kernel.

Is there a nice way to use the other kernels with the pkgtool, I wouldn't have asked it unless

Code:

root@Zukmeister:/mnt/dvd# for i in $(find /mnt/dvd/ -iname *.tgz -print | grep -i kernel | grep -i smp); do upgradepkg --dry-run $i; done
kernel-headers-2.6.24.5-x86-2 would upgrade: kernel-headers-2.6.24.5_smp-x86-2
kernel-modules-smp-2.6.24.5_smp-i686-2 would be skipped (already installed).
kernel-huge-smp-2.6.24.5_smp-i686-2 would be skipped (already installed).
kernel-generic-smp-2.6.24.5_smp-i686-2 would be skipped (already installed).
kernel-headers-2.6.24.5_smp-x86-2 would be skipped (already installed).
kernel-source-2.6.24.5_smp-noarch-2 would be skipped (already installed).
root@Zukmeister:/mnt/dvd# uname -a
Linux Zukmeister 2.6.24.5 #2 Wed Apr 30 14:13:52 CDT 2008 i686 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux

T3slider · 05-09-2008, 09:09 PM

It looks like the generic-smp kernel is already installed. Check /boot to see if there exists vmlinuz-generic-smp-2.6.24.5-smp and System.map-generic-smp-2.6.24.5-smp. If they do exist, add a stanza in /etc/lilo.conf such as the following (change /dev/sda1 to point to your Slackware root partition):

Code:

image = /boot/vmlinuz-generic-smp-2.6.24.5-smp
  initrd = /boot/initrd.gz
  root = /dev/sda1
  label = Generic
  read-only

Then make an initrd (read /boot/README.initrd for help on that) and run `lilo` as root. That should get you booted into the generic-smp kernel if it exists on your machine.

subgenius · 05-09-2008, 11:13 PM

T3slider had it exactly right. Once I switched to the smp kernel, the driver installed
with no problems. If you read the referenced file
(/extra/linux-2.6.24.5-nosmp-sdk/README.TXT) you will see that the smp kernels are
recommended.

And if you want to stay with your non-smp kernel there is a script to run (patch-to-non-smp.sh) in /extra to convert your kernel sources.

shadowsnipes · 05-14-2008, 11:05 PM

Btw, there are ATI slackBuilds out now at slackBuilds.org.

Alstare · 05-15-2008, 02:38 AM

kudos on the Slackbuild ATI Packages!

I will have to give them a shot on the next box I setup.

Bruce Hill · 05-15-2008, 02:54 AM

You also seem to be installing a 64-bit driver on a 32-bit OS:

Code:

ati-driver-installer-8-4-x86.x86_64.run

Maybe I'm wrong, but if not, will it work?

disturbed1 · 05-15-2008, 03:30 AM

Quote:

Originally Posted by Bruce Hill

You also seem to be installing a 64-bit driver on a 32-bit OS:

Code:

ati-driver-installer-8-4-x86.x86_64.run

Maybe I'm wrong, but if not, will it work?

That's just ATI's naming

. I actually (re) downloaded the package 3 times because it had x86_64 in the name.

Shame my x1600 is still only on par with an nVidia fx5500, but that's another story

.