I'm confused. So I don't do all those different makes like?:
make dep
make clean
make bzImage
make
make install
make modules
make modules_install

"make" now makes the kernel image AND modules.

Although you CAN still do just "make modules"

make dep isn't necessary, it's done by make modules_install now.

"make clean" still does what it always did.

I was trying to go from default slack kernel 2.4.xx to 2.6.1 after fresh install. Weird because I got a 2 errors at the very end that said /boot/vmlinuz.old did not exist. So I rebooted and saw that lilo had not had my new entries in. I then ran lilo to update it and it said my new entry was added. I rebooted and lilo still didn't have my new entry. only my first kernel under it's original name appeared. blah i'm done with messing around with kernels.

I just want to say a big thank you for this guide! I've messed with Slackware for quite some time, but never compiled my own kernel until now. This make it very easy, and now I'm running 2.6.1 without any problems.

Now I'm off to do some tweaking.

vmlinuz is still my old kernel after doing this 3 different times. where is this new kernel being saved to, because /boot/vmlinuz is still my old kernel though a different file size. after loading it still says "Welcome to 2.4.22!" I don't know what I'm doing wrong. I even tried cping /usr/src/linux-2.6.1/arch/i386/boot/bzImage and System.map to /boot. Still says it's 2.4.22 after loading.

Thanx to DaOne (MASTER!!) even I now succesfully recompiled my kernel (2.4.22). However, a simple (?) question remains:

After the first recompile I ended up with my new kernel and the original one (Slack.old). Good!

But when I tried to further tweak the new kernel, the .old one was replaced with the first new one (now called Slack.old) and the second tweaked one. I would have liked to keep the original one (Slack.old) and have the new one to fool around with.

I did not change anything in lilo.conf nor in the Makefile (after the changes made to recompile for the first time). I guess I should have?

Leon.

Lots of compliments to the good-hearted people here at the Slack forum!!!

LJSBrokken...

Yes, this can be a problem if you have to compile several kernels until you get it the way you want/need it to be. What I like to do to get around this is this...

Before I install any newly compiled kernels, I will cp /boot/vmlinuz /boot/vmlinuz.safe
cp /boot/System.map /boot/System.safe

What this does is copies you current working kernel image to .safe so that it will always be there for booting. This is useful if you compile several bad kernels in a row, because vmlinuz.old is removed, and vmlinuz becomes vmlinuz.old, and your newly installed kernel image becomes vmlinuz every time you run make install. Make sense?

Anyway, once you add the .old and .safe entries, you will see the kernel images are added after make install runs /sbin/lilo.

HTH

i have no problems recompiling a kernel, but compiling a new one. su -c "make modules_install" only does something for one second and it spits out something about if System.map.... fi. then if I continue to make install and reboot to new kernel I can't even make out the screen.


if I haven't compiled a kernel on a system before, do I need a System.map or a .config from a previous compile(and not from just a fresh install of slack)?

You added the .old entries in lilo.conf and uncommented line 450 in /usr/src/linux-2.6.1 right?

If you run make mrproper, then cp /boot/config-ide-2.4.22 /usr/src/linux-2.6.1/.config, you will now have a config file to start with. This is the config file for the bare.i kernel from the Slack install CD. You can then do make menuconfig and configure the rest of the options and save the configuration. Then just do...

make
su -c"make modules_install"
make install

See if that works for you.

Me again....

A few days ago I asked here if someone could help me ... but nobody answered.
So I'm asking you again ... How can I install SlackWare on a system with S-ATA HDD ?
I don't have a spare IDE HDD, I can't make the controller emulate an IDE HDD ... But now I have a FDD. ... if this could help. I found on the net a sata.i but is for Silicon controller not for Promise, which I have.

So could you please help me ...\

P.S. If I boot from a FDD or a Boot-CD in DOS I can see one partition on my HDD which is Fat32.

I don't know much about S-ATA...you may get more responses by creating a new thread, and also try posting in the hardware forum. Alot of members frquent hardware and never see what is in the distro specific forums.

correct. first added entry to lilo. changed linux to point to linux-2.6.1. so in /usr/src/linux... then uncommented export install path=/boot line in Makefile, which for 2.6.1 is actually a few more lines down than 450. then ran mrproper. then did menuconfig and saved config as .config, make, su -c "make modules_install" and make install. like i said the command involving make modules_install just spits out 2 lines and then some part of a script involving System.map, hence the fi.

I downloaded the kernel from www.kernel.org and the file is named patch-2.6.1; should I rename it linux-2.6.1?

no, download F(full source). If you just click on 2.6.1 name it will download the patch, not source.