Salix Forums

Hello, I'm researching how to upgrade the kernel in Salix (for wireless support) and was wondering: can I use the kernel files from the Slackware -current ftp? Which files should I pull from the /source folder to use in Salix?
ftp://slackware.mirrors.tds.net/pub/sla ... /source/k/

I'm reading AlienBOB's kernel building wiki entry , but only about 60% makes sense to me right now. I'd be skipping a step or two in the "Downloading and configuring" section if I did this, right? Or is it not recommended I use this method?
http://alien.slackbook.org/dokuwiki/dok ... elbuilding

Hello,

If you want to upgrade the kernel, you can download de kernel-source package from slackware current with the good config file (config-generic or config-huge) and compile it.
If you want to use the built kernel from current, you have to upgrade all the building chain (glibc, kernel-header, gcc, coreutils…), I think compile the kernel yourself is easier.

Okay, thanks. I'll give that a try right now.

Edit: How do I add the -current repository? I'm coming from the Fedora/*buntu land of GUIs.

I did this recently the other way (downloading from a Slackware mirror) and it was quite straightforward. However I didn't upgrade the "building chain" and would be interested to know what comes in the list after those dots! Actually I think I did upgrade glibc when I had trouble compiling something, and that was apparently enough to fix it. Presumably I can expect similar problems in the future

I was tempted to wait until Slackware 1.4 came out, since currently both of my laptops have unsupported hardware, but I figured I'd just jump in and just do a kernel upgrade. The learning curve is pretty steep. Kind of like running into a wall!

mimosa wrote:However I didn't upgrade the "building chain" and would be interested to know what comes in the list after those dots!

I don't know exactly because I never do that. Maybe I forgot binutils and util-linux.

thom1 wrote:If you want to use the built kernel from current, you have to upgrade all the building chain (glibc, kernel-header, gcc, coreutils…)

You don't have to upgrade your toolchain.
Just list the kernel packages, that are currently installed on your 13.37 system: ls -l /var/log/packages/kernel-*
Get those packages from current and upgrade.

thenktor wrote:

thom1 wrote:If you want to use the built kernel from current, you have to upgrade all the building chain (glibc, kernel-header, gcc, coreutils…)

You don't have to upgrade your toolchain.
Just list the kernel packages, that are currently installed on your 13.37 system: ls -l /var/log/packages/kernel-*
Get those packages from current and upgrade.

The problem are third-party kernel modules. Upgrading just the kernel is enough, but as the gcc version changed with current, you won't anymore be able to build third-party modules for the kernel from current, as the kernel was built with 4.6. But your gcc is 4.5.

It's probably easier to build the current kernel yourself with gcc 4.5, i.e. a stock 13.37 toolchain. Unless you don't need 3rd-party modules. This is because upgrading a toolchain can have quite a huge impact compared to a kernel change.

I just ran ls -l /var/log/packages/kernel-* and got a pretty short list.

-rw-r--r-- 1 root root 6134 Mar 27 01:50 /var/log/packages/kernel-firmware-2.6.37.6-noarch-2
-rw-r--r-- 1 root root 21052 Mar 27 01:50 /var/log/packages/kernel-headers-2.6.37.6_smp-x86-2
-rw-r--r-- 1 root root 952 Mar 27 01:52 /var/log/packages/kernel-huge-2.6.37.6-i486-2
-rw-r--r-- 1 root root 187363 Mar 27 01:52 /var/log/packages/kernel-modules-2.6.37.6-i486-2
-rw-r--r-- 1 root root 2310368 Mar 29 16:55 /var/log/packages/kernel-source-2.6.37.6_smp-noarch-2

So this is all I need to upgrade (changing the kernel number?)?

This is a fresh install, so I don't think I'm using any third-party modules.

Also, does this correctly point to the Slackware -current repository: "http://slackware-current.net/index.php/"?

Shador wrote:The problem are third-party kernel modules. Upgrading just the kernel is enough, but as the gcc version changed with current, you won't anymore be able to build third-party modules for the kernel from current, as the kernel was built with 4.6. But your gcc is 4.5.

That's right, but everyone knows: third party modules are evil (I'm using them, too )

Shador wrote:It's probably easier to build the current kernel yourself with gcc 4.5, i.e. a stock 13.37 toolchain. Unless you don't need 3rd-party modules. This is because upgrading a toolchain can have quite a huge impact compared to a kernel change.

A toolchain only upgrade is insane, better upgrade everything to current then... and lose a lot of Salix packages that might not work in current.