Hello!
I found this site while looking for answers to the problem I just had after compiling my kernel. I'm kind've new to Linux and Slackware but I have a basic understanding of how things work with Linux.

I have an old Compaq Armada 1575DM laptop I installed Slackware 10 on. Slackware works *perfect* on my machine! Install went fine until I recompiled the kernel. Actually the kernel compile process went perfect until I rebooted. Upon rebooting, my laptop now restarts itelf after the BIOS Data Check message.......repeatedly.

So I did a search and came here, read the excellent information available and wrote the steps down to (hopefully) recompile the kernel correctly this time.

Can anyone point out any mistake in this list? I'm trying to do all this from the command line (no X). I would greatly appreciatte any help given. THANKS!!!

Steps to recompile Kernel 2.4.26 in Slackware 10 after a fresh install:

01. Login As root
02. cd /usr/src/linux
03. cp .config ~/
04. rm -rf /lib/modules/2.4.26
05. make mrproper
06. cp ~/.config ./
07. make menuconfig
08. make dep && make clean bzImage modules modules_install
11. cp arch/i386/boot/bzImage /boot/vmlinuz-2.4.26
12. del /boot/vmlinuz
13. ln -s /boot/vmlinuz-2.4.26 /boot/vmlinuz
14. cp System.map /boot/System.map-2.4.26
15. cp .config /boot/config-2.4.26
16. ln -s /boot/System.map-2.4.26 /boot/System.map
17. ln -s /boot/config-2.4.26 /boot/config
18. Edit /etc/lilo.conf
image = /boot/vmlinuz-2.4.26
root = /dev/hda1
label = Slackware-2.4.26
read-only
19. /sbin/lilo
20. Reboot System

I would suggest using the kernel compiling method here , as it does a lot of the file copying work for you and if you edit lilo.conf gives you a backup kernel to boot in the event something goes wrong.

What changes did you make to the kernel configuration when you recompiled?

Thanks for responding! I looked at the article you suggested, I actually looked at it before my first post....I like the method, except for editing the makefile. My line of thought on this is that if I stay away from editing files and try to do as much as possible by typing simple commands, I'll be less likely to screw it up!

I didn't do too many changes to the kernel, mostly just wanted to get rid of Amatuer Radio support - stuff like that - that I'll never use and optimize it for a PII. I left anything I wasn't sure of alone.

So, with a fresh install of slack 10, will the post you linked to absolutely work? I'm going through all this trouble to make a definete list because of the long time it takes to do these things on this machine.....ancient machine.

That's the method I have always used for compiling my kernels and the only time I have had any problems has been when i have selected an incompatible option to be compiled or left out required option (like my filesystem ).
And being able to select the backup working kernel at lilo has meant no hassle in being able to get back in and try again.

The downside of this method is that if the main kernel is non working compiling again will make that main non-working kernel the backup kernel and you would then need to boot the system using a kernel from the CD.

For the first few compiles it can certainly make life a little easier by reducing the amount of hassle to get back into a working system. And if the backup works when the new kernel doesn't then it can at least give you an ide that something is wrong in the compile and you can start narrowing down what options might have caused it.