Hi,

Is it wise to upgrade the Slackware 14.0 kernel from 3.2.29 to the most latest and stable release, 3.6.8?

Hi, Welcome to LQ.

I guess it depends on how comfortable you are with the kernel build process and resolving any issues an update may introduce.
Following the 3.2.x branch might be safer which is what I'm doing. Currently on 3.2.34.

1 members found this post helpful.

A kernel upgrade is not likely to cause any problems. Slackware uses vanilla kernels without any patches.

I'm currently running 3.6.7 with no issues.

1 members found this post helpful.

@Ser Olmy,
Did you use the 'huge' or 'generic' config as template?
I have tried 3.6.8 with the huge config and trying to go easy on myself ...
I found that DLM gave me errors (CONFIG_GFS2_FS_LOCKING_DLM=y) so had to change it to 'n'.
It then compiled with no (serious) errors, but I can't run it - alas - the infamous "failed to mount filesystem on ..."

I tried a good oldfashioned 'make oldconfig' but was asked wayyy too many questions for my simple mind.

If your config-3.6.7 is 32-bits, would you mind terribly posting it somewhere?
Thanks in advance.

I'm afraid I'm running x86_64.

I used the "huge" kernel as a template (downloaded the new kernel, zcat'ed /proc/config.gz to .config, ran make oldconfig and then make menuconfig to change the setting for all non-critical drivers to be compiled as modules).

I've thought about creating a poll about the habits of most slackers.. Do people sit on the stock kernel released with Slack? Or is it a good idea to update the kernel in the same branch (3.2.29 -> 3.2.34)? Jump to the latest release (3.6.8)?

I am using 3.6.7, I was getting some battery drain on my Thinkpad T520 with the stock.

so usually upgrading the kernel is a good idea on most linux distros?

i am following this guide: http://alien.slackbook.org/dokuwiki/...rnelbuilding&s[]=kernel&s[]=compile

hopefully all goes well

Depends on your distro. In Slackware it is much easier and straightforward. Other distro have the kernels so heavily patched it's like playing Twister with a greased pig.

http://docs.slackware.com/howtos:sla...kernelbuilding

Using the above link, I can build a new kernel in 15 - 20 minutes.

@derfzz
I wouldn't think so. On Slackware it should be ok because of lack of patches.
If you look at eg. Redhat - they have 1000+ patches to their kernel - I wouldn't change that for love nor money! (which I guess is the whole purpose of having an 'enterprise' distro ...)

Beaten to it by SqdnGun ...

Playing around with the kernel is so easy in Slackware, it's addictive.

Wasn't Pat going to go with the 3.4 kernel for Slackware 14 but reverted back to 3.2 because something wasn't working right?

Correct.

Same here. The newer kernels are a bit easier on the old battery.

If you don't use Bluetooth then disable it, that is a huge drain. I am also running thinkfan as well and have really improved battery life.