compiling kernel, kernel panic, OH NO !!

[mike webb]

did the make bzImage.
renamed it vmlinuz and moved it to the proper place.
then rebooted.

everything seemed to be fine untill the following lines appeared.
uncompressing linux .. ok, booting the kernel
kernel panic - not syncing: VFS: unable to mount root fs on unknow-block (1,0)

anyone know what i need to do ??
if anyone needs detailed discription of how i compiled the kernel let me know and i will provide it.

only thing i really changed was that i added smp ability to the kernel. (via menuconfig)

[John Doe]

uncompressing linux .. ok, booting the kernel
kernel panic - not syncing: VFS: unable to mount root fs on unknow-block (1,0)

I think you copied the wrong file. btw, you don't need the bzImage part anymore. And check out gconfig it's a lot nicer on the eyes than menuconfig.

This works for me:

Code: Select all

#!/bin/sh
cd /usr/src
wget http://www.puppyos.net/test/linux-2.6.18.1-source-patched_sfs_log_via.tar.bz2
rename linux-2.6.18.1 linux-2.6.18.1.old
tar -jxf linux-2.6.18.1-source-patched_sfs_log_via.tar.bz2
cd linux-2.6.18.1
make clean
make mrproper
rm -f .config
cp DOTconfig-K2.6.18.1-19OCT06 .config
#now is a good time for additional patches
make gconfig #Make config changes here
make
make modules
make modules_install

Make sure you get the correct kernel image. You can check the file image type by viewing properties in rox. Just make sure it looks the same as the one on the CD. (bootable...etc..) Sorry I can't remember it's exact path off the top of my head, it's arch/build/boot or something like that.

[mike webb]

think i copy the correct file into the proper place.
after make i had a file in usr/src/linux called bzImage.
i renamed it vmlinuz.
then i went to /initd/mnt/dev_save and renamed vmlinuz to old-vmlinuz.
then i went back to usr/scr/linux and copied vmlinuz from usr/src/linux to /initd/mnt/dev_save.
then reboot, and i got the kernal panic.

makes no difference to me though, you have given me precise instructions on how to build the kernel. i will try that first and see what happens with my new,new kernel. kinda want to try gconfig anyhow.

[mike webb]

okay, recompiled again and still got the same error message. noticed something though.
using rox and asking for the propertys of both kernel files.
the new vmlinuz says:
contents indicate...
linux kernel x86 boot executable RO_rootFS,
root_dev 0xD,swap_dev 0x1,normal VGA

the old vmlinuz said:
contents indicate...
linux kernel x86 boot executable RO_rootFS,
root_dev 0x341,swap_dev 0x1,normal VGA

why would root_dev be in one place in one kernel and in another place with a different kernel. ????

also, suddenly ppp doesn't work, seems ppp.o no longer exists in the filesystem, i got a baaad feeling.

[Ted Dog]

You need to update initrd.gz to match, It is easier to do a full harddrive install, then compile kernel, full install does not use initrd so one less hoop to jump. If you are going to redo. make sure that to make a boot folder for it to install into, that way the system.map and kernel do not have to be found deep inside source/compiled directories

[mike webb]

You need to update initrd.gz to match
hmm, well i have no idea how to do that.
downloading puppy unleased going try by building a "stock" distro.
if that works then i will try building another distro but with smp in the kernel.

i really like puppy, but i got to say this is really getting to be diffcult, if i can't get smp to work thats a show stopper for me. right now puppy blows the doors off my fedora system and thats with just one cpu running, fedora uses both cpu's.

going give this one last try.