Hello,

On an old box running Slackware 10.2, with the default 2.4 kernel, I have to recompile the kernel in order to get a printer working.
I've tried it once (with the latest 2.4 kernel) and it wasn't exactly a success...
Question: Is it safe to just grab the latest 2.6 (SMP) kernel and follow Alien Bob's guide (with that guide I've always succeeded, but that was on SW 12 machines)?

The instructions from Alien bob look pretty standard to me and should work. Just make sure you select the modules you need and compile the filesystem support into the kernel, not as a module. I've done kernel compiles on Slack 10 and up and it always worked for me.

Thanks for the reply!
I'll go for it then (yes, I did know to compile filesystem support in, thanks anyway).

I think you have to do some additional stuff to get a 'properly' running system when upgrading from the 2.4 to the 2.6 kernel. The 2.6 kernel uses sysfs, which isn't supported by the 2.4 kernel. There may be some funky iptables/netfilter stuff as well. There may be additional changes, but I'm not positive. It would be best to wait for someone who knows what they're doing...

So I experienced...
The kernel(s) booted alright, but X just wouldn't start (not in 2.6*, nor in 2.4*).
Got loads of errors and trying to fix it only made it worse.

Installing 10.2 again with the default kernel.
Gonna try it again with a new compile later, this time with a 2.4* kernel.

Is the Alien Bob's guide OK for that too?

X not starting is probably just a module issue. You need the correct module for your video card in order for X to work. What kind of video card do you have.

I've installed 10.1 with the default 2.4 kernel and compiled 2.6 with no issues other than video. Downloaded the correct kernel module for my card and installed it and it works. No issues.

Indeed X complained about not finding the modules (yes I did make modules install, sure of that), so I symlinked /lib/modules/2.4.31 to /lib/modules/2.6.24.
But that didn't solve anything.

Apart from that (the card is an on board chip: Intel 82815, which uses the i810 module. Which couldn't be loaded (dunno why)...

Anyways, I reinstalled SW 10.2 now and want to compile a new 2.4 kernel (all because of the HP Deskjet 720 that I cannot get to work ).

The rule is: "make modules_install", not "make modules install".

gnashley is right. But if you are going for a 2.4 Kernel just follow the same instructions.

Who is the biggest fool of them all?
I AM!

It was late and I was tired, so it could very well be possible that I missed the _ ...
It sure would explain a lot.

What I don't understand is: when booting the 2.4 kernel, I got the same error. How is that possible, because the 2.4 modules were installed?

Try using the original config file for the Slackware standard 'bare.i' kernel and just add whatever options you need.
You can find the config file in the same place as the kernels, for example:
ftp://ftp.slackware.at/slackware-10..../bare.i/config

After unpacking the fresh kernel sources, just copy that config file into the toplevel of the sources and change the name to '.config'. Then run 'make oldconfig' and just click ENTER each time it asks you about new options. Then when it finishes you can run 'make menuconfig' and change anything you need to. If you've been running the standard kernel you shouldn't need to change anything unless it has to do with your printer someway.
Then run 'make bzImage && make modules && make install_modules. Be sure to manually install the new kernel and re-run lilo.

Kernel 2.6.24.3 is up and running and so is X.
Thank you for the help.

Still, out of curiosity: why didn't X start with the 2.4 kernel, while those modules were installed?