Hi, I've compiled my own 2.4.26 kernel and added it to lilo. At boot it get the errormassage:

No Setup Signature found...

Luckily i've kept the old kernel in there, too and it boots correctly.
I am new to slackware, so pleaze be understanding... Whats wrong? Who can help?! Th4Nx a lot in advance!

I have seen this message before
Did you compile devfs support and did you say "mount at boot"?

What about initrd and so

how did you create the kernel

did you copy the bzImage to /boot/vmlinuz-2.4.26 or somesuch?

--Shade

Tanks a lot for your fast replies! I did:
make xconfig, make dep, make clean, make zImage, make modules, make install with a lilo.conf, that is edited correctly, i think (copied, pasted and .old added to old kernel) Have no devfs selected, cause not needed i think.

ok, i got it! i've just copied the wrong image, as you supposed, shade. I've copied zImage instead of bzImage. thx btw!

Hi,

I've now compiled the 2.6.7 Kernel but i doens't work as it should. :-/ The system freezes after following lines while booting:

...
NTFS-fs warning (device hda8): ntfs_fill_super(): Atime updates are not implemented yet. Disabling them.
UDF-fs: No partition found (1)
Kernel panic: VFS: Unable to mount root fs on hda8
_


hda8 is my root partition with ReiserFS. I've unchecked UDF-FS support, but don't understand why the NTFS-fs warning points to hda8. My hda1 is NTFS. Please help!

When I am in trouble compiling a kernel I copy .config to a save place

cp .config ../myconfig

and than I make mrproper that cleans up everything

after that I copy cp ../myconfig .config

and make xconfig (it's also linking asm with the machine type asembler headers and stuff)

than make dep && make bzImage && make modules

than make install && make modules install

copying just bzImage is not always enough - if you want to have your headers in place I noticed.

I hope it helps

I had one more thing in mind ....

what kernel are you using while compiling and did this kernel has devfs enabled or initrd

Post up your fstab.

I think linux thinks your root partition is ntfs. linux can't write to ntfs reliably yet, there's one problem.
If your / is reiserfs, make darn certain that you compiled reiserfs file support into the kernel, it cannot be a module without using an initrd. I much prefer to go without an initrd and simply compile everything I need to boot in. The less important things I load as modules.

--Shade

thanks again for your replies!

while compiling my new 2.6.7 kernel i was running 2.4.26. of course my old kernel is booting properly. i have no ramdisk installed.

my fstab seems to be ok, beacuse it is accepted by the 2.4.26 kernel and i think both kernels share the same fstab.

hda1 /mnt/MTFS-C : NTFS
hda5 /mnt/FAT32 : FAT32
hda6 /boot : ext2
hda7 : swap
hda8 / : reiserfs
hda9 /usr : reiserfs
hda10 /home : reiserfs

i have no idea, cause everything seems well configured, and i have support for reiserfs checked. what about this UDF-fs ?! Maybe some more ideas?! I would be very grateful if someone could help!

Hi again,

I've reinstalled my system, but now with the ext2 fs. After compiling my 2.6.7 kernel it booted correctly! no errors, like before while i had reiserfs, what i really do not understand... I've recognized, that i can only build the kernel once. If i compile a new kernel after another there are no changes made. Why not?! i've done make mrproper, but should i do make clean, too?!

I'm just getting used to slackware, so I'm sorry for my "stupid" comments. I think i have learnd a lot till now and gonna ask some more. hope you'll help!

best regards!

When you compile a kernel there are a few steps you have to take...

1. in /usr/src/linux-2.6.x edit the Makefile (look for a line that says export=install path /boot --or something like this-- and remove the # in front of it)---> this makes sure that make install installs your kernel to /boot.
2. cd to /boot and make sure that your current running kernel has a seperate vmlinuz, System.map, and config ---> I usually
cp vmlinuz vmlinuz-2.6.7-mm4
cp System.map System.map-2.6.7-mm4
cp config config-2.6.7-mm4

3. Edit /etc/lilo.conf and make an entry to boot your vmlinuz-2.6.7-mm4 (just copy the current entry and change the label and point the image to your vmlinuz (image = /boot/vmlinuz-2.6.7-mm4).
4. run lilo

For configuring your kernel it's good to get an understanding of what type of support you need to compile in dmesg can give you some pointers.

kernel commands

make menuconfig (select what you need ---> make sure alsa is compiled as modules, and the type of filesystem your using is compiled into the kernel or you'll get a kernel panic as you did before)
make
make modules_install
make install

That's it... you're next boot will boot Linux entry in lilo to your new kernel... and you'll have you're working kernel in case something went wrong...

Each kernel compile after this will overwrite vmlinuz, System.map, config in boot and make install will update lilo so you'll just need to reboot...

*Edit* Note: above the 2.6.7-mm4 should be replaced by whatever kernel version your building (just in case it wasn't obvious )

Thanks a lot for these tips. i'll do it this way next. one question: does "make" do the same like "make all" ?!

make for 2.6 combines make, make modules, and make bzImage

lupin_the_3rd you are right.
The first thing after I do make xconfig is to check .config and Makefile

In .config I put my own subversion

and in Makefile I remove the # before export=install so the install process knows where to find vmlinuz

didn't think that fckalya does not know this

fckalya you've got to the kernel docs - it's odd but I think it's the proper way

regards