Hi Everybody, i have made a tutorial for a 13.37 Kernel Upgrade at http://2012revolution.us/doku.php?id=start , let me know what you think!!! i can help and add to the tutorial along the way, and dont be afraid to comment to the wiki! Thanks!
-Phillip

Hi. Well done for making an effort. A couple of observations:

I'm not sure that who the target audience in terms of skill level, but if this is aimed at beginners they should be advised to verify the kernel tar ball before compiling. On overview of the stages at the beginning would also be good, as would some references and more detailed explanation of what each stage is for.

The lack of initrd implies that you are building from the huge config. You might want to address this in the guide, as it is arguably better to build from a generic config.

It's your computer so you can build the kernel where you like, but I'm wondering why you don't use /usr/src as that's where the kernel sources are by default.

Thanks for your input kristizz!

Nice work.
As kristizz said why not compile in /usr/src ?
However:
This will not copy to /boot
You should use
Then lilo.conf will be correct
BTW, nvidia will not compile on kernel 3.3.0

You do know everybody can edit your page, right?

Kind regards

You do not need to be root to compile a kernel.

I repeat: You do not need to be root to compile a kernel.

I do not understand why people believe this.

Please, please, please read Linux Kernel in a Nutshell. It was written by Greg Kroah-Hartman who is a kernel maintainer.

Is it just me, or the link doesn't work?
EDIT: Sorry, it's working now.

all very good feedback and very valid, but with that said, thanks for the laying the foundation of a user guide for upgrades, it will only get better now that you have laid the foundation


Rasta420

Root makes life easier.

wget "http://www.kernel.org/pub/linux/kernel/v3.0/testing/linux-3.3-rc6.tar.bz2" -O - | tar vxj ; cd linux*;cp /boot/config*huge ./.config;make&&make modules&&make install&&make modules_install;reboot

one line to rule them all

While it is true that root is not required to build the kernel and the official README says
I still side with salemboot: it is kind of easier. It also seems to be the Slackware way, judging by slackbuilds.

I have to point out, though, that skipping make oldconfig may cause you to have a bad time. In one instance I forgot to do it and still was able to boot a misconfigured kernel. Super-glitchy graphics gave away my mistake, so I fixed it, but who knows what else was broken?

Also, in my latest attempt to bring custom kernels to multiple desktops and laptops, I wrote a kernel slackbuild script. It is an amalgamation of the official Slackware scripts for kernel, modules, and firmware. You still have to configure the kernel (which is by far the hardest part), but then you can follow my very easy README and make a package which can be used to upgrade kernel/modules/firmware in one fell swoop, as simply as
You also benefit from being able to uninstall your custom kernels cleanly and quickly. One major caveat is my refusal to deal with initrd: since I am already making my own kernel, I can easily throw in whatever it needs to boot (in my case, just ext4).

qweasd, looks like you're doing something very similar to me. I also have a combined kernel+modules SlackBuild script I use. I still use a separate package for firmware though. (currently the one from current)

I thought about adding a "mkinitrd' to the doinst.sh, but at the moment I still do that bit and lilo manually.

elvis, thanks for the link...just finished reading it, good info in there and was nice to hear from an official kernel developer to build in a user created directory and not in /usr/src like everyone says

Rasta420

repo,

do you know if the nvidia driver compiles on 3.2.9 kernel?

my laptop is ATI graphics and so far the 3.2.9 kernel is good to go but desktop is nvidia gts 250 and havent updated the kernel there yet

Rasta420

Good Work!

I am a newbie at Linux and am about to tackle Slackware with all new hardware and had wondered how to perform brain surgery if necessary.

I also like all of the comments! I get to learn several things at once.

T L
On the Wet Coast
Light rain and 48 F

Starting with 144, udev looks in /lib/firmware/$(uname -r) and then /lib/firmware. So there is a very clean way to install the correct firmware without colliding with the Slackware package.

1 members found this post helpful.

I know it compiles on 3.2.7.
For the 3.3.0 kernel,
I found this on the net
Then rerun the nvidia installer.
Works on my system with kernel 3.3.0.
Seems to me it should work on 3.2.9 also.

Kind regards