I upgraded to current last night. Everything went smoothly, I knew that catalyst would have to be re-installed due to an upgrade of mesa. I tried to reinstall but it failed.
"Error:
Kernel includes at /usr/src/linux/include do not match current kernel.
they are versioned as '3.14.5'
instead of '3.10.17'
you might need to adjust your symlinks:
- /usr/include
/usr/src/linux
ERROR: I didn't make module
[error] generate package - error generating package : Slackware/Slackware

Any help is appreciated. I get confused when thinking about symlinks and the syntax involved. Any help is appreciated.

Remove a symlink with:

rm symlink

Create one with:

ln -s /path/to/folder/or/file /path/to/symlink

I'd assume you would have to remove the old ones (3.10.17) and create new ones (3.14.5)

How would I find the symlink?

How would I find where the symlinks are?

Most probably you didn't properly upgrade to -current (and in my opinion you should have better waited to do that to have some more experience with Slackware, but that's another story). My guess is that your kernel-* packages are not are not all at the same version.

To check please provide output of following command:

It's a bad bad advice to do that manually. Instead, the OP should have installed the proper packages. Bear in mind that Slackware is not built as other distributions.

PS aaa_base that provides the symlinks didn't change from -14-1 to -current at time of writing and my first assumption would be that the kernel-source and the running kernel are not at the same version, hence the command I suggested Pinonoir to run.

It makes more sense now, I wasn't really sure of what was happening (hence the "I'd guess")

By any chance when you upgraded the kernel did you manually try to update the kernel-headers as well?

Sorry about the late reply and forgive the formatting, here is the output of ls -1 /var/log/packages/kernel* - /var/log/packages/kernel-firmware-20140506git-noarch-1
/var/log/packages/kernel-generic-3.10.17-x86_64-2
/var/log/packages/kernel-headers-3.14.5-x86-1
/var/log/packages/kernel-huge-3.10.17-x86_64-2
/var/log/packages/kernel-huge-3.14.5-x86_64-1
/var/log/packages/kernel-modules-3.10.17-x86_64-2
/var/log/packages/kernel-modules-3.14.5-x86_64-1
/var/log/packages/kernel-source-3.14.5-noarch-1

So your system is not consistent as you should have all kernel packages with the same version number. You are probably still running the kernel 3.10.17 but as the kernel source package was upgraded to 3.14.5, there is actually a version mismatch, thus the catalyst driver module can't be compiled. The error message is right, but the last part of it mis leaded you as the assumption it states that the symbolic links are bad is wrong.

My guess is that you made a kernel "upgrade" but probably not the right way as you installed the new kernel alongside the old one instead of replacing it. Also, you probably forgot to edit /etc/lilo.conf to replace the older kernel by the new one or you didn't run lilo after installing the new kernel. To make sure please provide also the output of following commands. The option of the "ls" commands is -l or hyphen followed by the letter l, not to confused by the digit 1:In addition it would be interesting to know which exact steps you took to make this kernel upgrade so we can tell you what was wrong in the procedure.

uname -r = 3.10.17
ls -l /usr/src/linux = lrwxrwxrwx 1 root root 12 Jun 11 23:32 /usr/src/linux -> linux-3.14.5/



image = /boot/vmlinuz-generic-3.10.17
initrd = /boot/initrd.gz # add this line so that lilo sees initrd.gz
root = /dev/sda1
label = Slackware
--
image = /boot/vmlinuz
root = /dev/sda1
label = Linux
read-only
--
image = /boot/vmlinuz-huge-3.14.5
root = /dev/sda1
label = New-Kernel
read-only

lrwxrwxrwx 1 root root 19 Jun 11 23:06 /boot/vmlinuz -> vmlinuz-huge-3.14.5-rw-r--r-- 1 root root 3450176 Feb 14 16:40 /boot/vmlinuz-generic-3.10.17
-rw-r--r-- 1 root root 6436992 Feb 14 16:45 /boot/vmlinuz-huge-3.10.17
-rw-r--r-- 1 root root 6685104 May 31 22:50 /boot/vmlinuz-huge-3.14.5

And I do not remember the exact steps I took.

In /etc/lilo.conf the stanzas beginning with
image = /boot/vmlinuz
and
image = /boot/vmlinuz-huge-3.14.5
are redundant as /boot/vmlinuz is a symbolic link to /boot/vmlinuz-huge-3.14.5

Anyhow, run this as root:
"lilo -t -v"
then if all goes well:
"lilo"

Then reboot and choose either Linux or New-Kernel, not Slackware (that is, do not use the old kernel).

Then, you can upgrade catalyst.

I reinstalled the open source ati driver, It works and everything checks out. Also, using the latest firefox. I tried to install catalyst again and received the following from the /usr/share/ati/fglrx-install.log

AMD kernel module generator version 2.1
doing Makefile based build for kernel 2.6.x and higher
rm -rf *.c *.h *.o *.ko *.a .??* *.symvers
make -C /lib/modules/3.14.5/build SUBDIRS=/home/pino/Downloads/fglrx-14.20/fglrx-install.37BFaH/common/lib/modules/fglrx/build_mod/2.6.x modules
make[1]: Entering directory `/usr/src/linux-3.14.5'
CC [M] /home/pino/Downloads/fglrx-14.20/fglrx-install.37BFaH/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.o
/home/pino/Downloads/fglrx-14.20/fglrx-install.37BFaH/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function 'KCL_GetEffectiveUid':
/home/pino/Downloads/fglrx-14.20/fglrx-install.37BFaH/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:1787:5: error: incompatible types when returning type 'kuid_t' but 'KCL_TYPE_Uid' was expected
return current_euid();
^
/home/pino/Downloads/fglrx-14.20/fglrx-install.37BFaH/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:1793:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
make[2]: *** [/home/pino/Downloads/fglrx-14.20/fglrx-install.37BFaH/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.o] Error 1
make[1]: *** [_module_/home/pino/Downloads/fglrx-14.20/fglrx-install.37BFaH/common/lib/modules/fglrx/build_mod/2.6.x] Error 2
make[1]: Leaving directory `/usr/src/linux-3.14.5'
make: *** [kmod_build] Error 2
build failed with return value 2
ERROR: I didn't make module
[Error] Generate Package - error generating package : Slackware/Slackware

Hello,

As stated here, the latest fglrx driver supports kernel up to 3.11 (3.13 for beta). However, you can try to proceed as explained in this article to get latest fglrx to work with kernel 3.14.

--
SeB

I followed the instructions to the letter. Everything checked out. I even ran aticonfig --initial which went well. glxinfo said everything was good and direct rendering was enabled....then I rebooted. I checked glxinfo again and received a seg fault. I'm thinking about just reinstalling and sticking to stable as per the advice I received.