problem compiling kernel 2.6.7
 

I'm trying to compile kernel 2.6.7 in slackware 10 using DaOne's guide everything seems ok but when i reset the system, it boot's with the old kernel, i've gone through the guide step by step several times and the result is still the same, can anybody tell me what may be happening or what i can do about it, I'm new to Linux an may be missing something obvious:cry:

did you run lilo? post up your lilo.conf file if you have run lilo already

It may be a wrong config at lilo, or maybe you're using the symlink and forgot to update it. As trey85 said, try to post your lilo.conf or if you have doubts about the symlink do: ls -l /boot/vmlinuz

Edit: The symlink is optional so if you haven't done it, don't worry :)

not 100% sure exactly what i'm looking for here, i've tried removeing .old still boots to 2.4:scratch:
windows isn't installed.
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771

# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Windows bootable partition config begins
other = /dev/hda1
label = Windows
table = /dev/hda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz.old
root = /dev/hde1
label = linux.old
read-only
# Linux bootable partition config ends

Well you didn't add an entry for the new kernel there...
Add something like:
And run: lilo

Edit: change /boot/vmlinuz to suit your system.

I don't know this guide - but these are the steps:

configure the kernel source (make menuconfig - for instance)

make

make modules

make modules_install

cp ./System.map /boot/System.map --> copy the new System.map...

cp ./arch/i386/boot/bzImage /boot/bzImage (or to whatever name you would like to give your kernel)

add the new kernel to your boot-loaders configuration-file (/etc/lilo.conf or /etc/grub.conf)

update your boot loader - by running: lilo -v or grub-install /dev/hd?

depmod -a --> to update the dependencies of the new kernel-modules

reboot

still not working i've tried the suggestions but it still boots to the old version:scratch: :confused: :cry: , anymore help i will be thankfull, i'll try again tommorrow

Simple solution. Build Kernel incrementally
 

I have seen people have this problem before and get frustrated with kernel compiles. In almost all cases it comes down to a mis configuration in make menuconfig. What I do is start with a very _SIMPLE_ kernel with the fewest amount of features I can get away with. Then I build another kernel with more features and test it. I can always revert back to the first kernel built and rebuild again. This method has always worked for me especially when I am working on a new machine. Good luck and don't ever give up!

tjb do: ls -l /boot
and paste it here, and also paste the new lilo.conf

...this guide you where mentioning - it is - as far as I have found it using google - just a thread on this forum. And: it does miss out or is unclear on some steps that may be necessary...

You should have used a HOWTO - that is what they are for: step by step explaining how and why.
A collection of probably all of them is here as well as much more:
http://www.tuxfinder.com/

Did you use the most obvious source of information: read the Readme file included with the Kernel-source - it explains, how it is to be done, in great detail...

What I wrote was basically a summary of that Readme (and of what I always do, when I compile a new kernel)

The important thing is: you have to add you new kernel to the /etc/lilo.conf as gbonvehi was saying and then run "lilo" to write the new information to disk.

The lilo.conf you posted, shows that your boot-menu gives you two choices:

first entry is Windows - on /dev/hda1
second entry is linux.old - on /dev/hde1

so everything is all right with lilo here - is does just what you told it to do - boot the old kernel!

You will want to change it to include an entry for your new kernel as gbonvehi said...

Sorry for this stupid question. (and also seems offtopic)
What is the purpose of system.map?
Is the above step necessary? (It overwrites the old System.map!)
Coz I faced the kernel panic on mounting fs, but I compile all the fs module needed)

Thanks.

good question! I do not really know - I suppose it describes the kernel-code and what capabilities are built in ...but: I don't know! You will have to google..

Still it is needed and that's why I always copied it too.

Actually - I do NOT copy it over the old one - I use a link to point to it.
This way I really have everything needed to go back to my old kernel or to another one...
I just change the link to point to the correct System-map.

this is what it looks like currently:

ls -al ./System.map
lrwxr-xr-x 1 root root 22 2004-06-19 10:05 ./System.map -> /boot/System.map-2.6.7

...the link "System-map" points to the correct file "System-map-2.6.7"

this will help out greatly.... when copying the bzImage and System.map file.. I generally add -2.x.x to the end of each.. to depict the kernel version.

you can then add a second entry to lilo.... i.e.

image = /boot/bzImage-2.x.x
root = /dev/hda6 #this varies on your partition setup.
label = Linux-2.6.7
read-only

good luck.

just got back from work i haven't tried anything else yet, i've had a look at the site recommnded jomen can't see any howtos on compileing kernels?, i'll have another look around
total 9465
lrwxrwxrwx 1 root root 37 2004-08-06 23:26 README.initrd -> /usr/doc/mkini trd-1.0.1/README.initrd
-rw-r--r-- 1 root root 998534 2004-08-08 23:21 System.map
-rw-r--r-- 1 root root 620999 2004-06-15 03:29 System.map-ide-2.4.26
-rw-r--r-- 1 root root 762268 2004-08-08 18:13 System.old
-rw-r--r-- 1 root root 512 2004-08-06 23:38 boot.0300
-rw-r--r-- 1 root root 209 2004-08-06 23:38 boot_message.txt
-rw-r--r-- 1 root root 2226132 2004-08-08 23:22 bzImage
lrwxrwxrwx 1 root root 17 2004-08-06 23:26 config -> config-ide-2.4.26
-rw-r--r-- 1 root root 41017 2004-06-15 03:29 config-ide-2.4.26
-rw-r--r-- 1 root root 5032 2004-05-21 08:19 diag1.img
-rw------- 1 root root 40448 2004-08-08 23:33 map
-rw-r--r-- 1 root root 2226133 2004-08-08 22:54 vmlinuz
-rw-r--r-- 1 root root 1248111 2004-06-15 03:29 vmlinuz-ide-2.4.26
-rw-r--r-- 1 root root 1494200 2004-08-08 18:13 vmlinuz.old

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Windows bootable partition config begins
other = /dev/hda1
label = Windows
table = /dev/hda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/bzImage
root = /dev/hde1
label = linux-2.6.7
read-only
# Linux bootable partition config ends

This looks right, make sure you run lilo as root... what happens now when you boot into linux-2.6.7