Kernel Panic...I did something wrong, but I do not know what

[debian111]

I compiled kernel 2.6.15 last weekend and some problems occurred during my work
Distribution is Debian Sarge

in /lib modules is as follows


tdebian:/lib/modules/2.6.15-new# ls -l
total 992
lrwxrwxrwx 1 root root 36 2006-02-05 09:52 build -> /usr/local/src/kernel/linux-2.6.15.1
drwxr-xr-x 10 root root 4096 2006-02-05 09:53 kernel
-rw-r--r-- 1 root root 195650 2006-02-05 09:53 modules.alias
-rw-r--r-- 1 root root 69 2006-02-05 09:53 modules.ccwmap
-rw-r--r-- 1 root root 220991 2006-02-05 09:53 modules.dep
-rw-r--r-- 1 root root 813 2006-02-05 09:53 modules.ieee1394map
-rw-r--r-- 1 root root 394 2006-02-05 09:53 modules.inputmap
-rw-r--r-- 1 root root 21025 2006-02-05 09:53 modules.isapnpmap
-rw-r--r-- 1 root root 175911 2006-02-05 09:53 modules.pcimap
-rw-r--r-- 1 root root 96337 2006-02-05 09:53 modules.symbols
-rw-r--r-- 1 root root 259743 2006-02-05 09:53 modules.usbmap
lrwxrwxrwx 1 root root 36 2006-02-05 09:52 source -> /usr/local/src/kernel/linux-2.6.15.1


when I start new kernel chosing it in grub, after 5 sec I got output like bellow

modprobe: FATAL: Could not load /lib/modules/2.6.16-new/modules/dep
No such file or directory
umount: defs: not mounted
pivot-root: No such file or directory
/sbin/init: 432: cannot open dev/console : No such file
Kernel Panic – not syncing: Attemped to kill init

.....I cannot understand what I did wrong

in /boot directory are following folders
tdebian:/boot# ls -l
total 12916
-rw-r--r-- 1 root root 512 2006-01-27 23:02 boot.0200
-rw-r--r-- 1 root root 308326 2006-01-27 22:29 coffee.bmp
-rwxr--r-- 1 root root 55809 2005-05-19 10:38 config-2.6.8-2-386
lrwxrwxrwx 1 root root 15 2006-01-27 22:29 debian.bmp -> /boot/sarge.bmp
-rw-r--r-- 1 root root 153720 2006-01-27 22:29 debianlilo.bmp
drwxr-xr-x 2 root root 4096 2006-02-05 10:02 grub
-rw-r--r-- 1 root root 4317184 2006-02-05 09:58 initrd-2.6.15.1-new
-rw-r--r-- 1 root root 4317184 2006-01-12 20:52 initrd.img-2.6.8-2-386
-rw-r--r-- 1 root root 23662 2006-01-27 22:29 sarge.bmp
-rw-r--r-- 1 root root 24116 2006-01-27 22:29 sid.bmp
-rw-r--r-- 1 root root 698046 2006-02-05 09:57 System.map-2.6.15.1-new
-rw-r--r-- 1 root root 865733 2005-05-19 11:26 System.map-2.6.8-2-386
-rw-r--r-- 1 root root 1157420 2006-02-05 09:56 vmlinuz-2.6.15.1-new
-rw-r--r-- 1 root root 1097419 2005-05-19 11:25 vmlinuz-2.6.8-2-386

for my old kernel (still working ) /lib/modules is as follows
tdebian:/lib/modules/2.6.8-2-386# ls -l
total 828
drwxr-xr-x 2 root root 4096 2006-01-12 20:52 boot
drwxr-xr-x 2 root root 4096 2006-01-12 20:52 initrd
drwxr-xr-x 10 root root 4096 2006-01-12 20:52 kernel
-rw-r--r-- 1 root root 138720 2006-01-12 20:35 modules.alias
-rw-r--r-- 1 root root 69 2006-01-12 20:35 modules.ccwmap
-rw-r--r-- 1 root root 235506 2006-01-12 20:35 modules.dep
-rw-r--r-- 1 root root 517 2006-01-12 20:35 modules.ieee1394map
-rw-r--r-- 1 root root 1061 2006-01-12 20:35 modules.inputmap
-rw-r--r-- 1 root root 16427 2006-01-12 20:35 modules.isapnpmap
-rw-r--r-- 1 root root 131958 2006-01-12 20:35 modules.pcimap
-rw-r--r-- 1 root root 104676 2006-01-12 20:35 modules.symbols
-rw-r--r-- 1 root root 157116 2006-01-12 20:35 modules.usbmap
lrwxrwxrwx 1 root root 100 2006-01-12 20:52 source -> /home/horms/tmp/debian-kernel-test/kernel-image-2.6.8-i386/kernel-image-2.6.8-i386-2.6.8/install-386

If somebody know what I did wrong acording to my outputs above, please write it down, I would pritiete that.


Thank you

[Steven E. Protter]

Shalom,

You may have done nothing wrong.

This panic may be caused by hardware support not being in the new kernel. If you need to put that support in, you need to see that the drivers installed in the old kernel are installe din the new ones.

SEP

[debian111]

???
but my new kernel does not work, and I wish I can make it work because it is very important for me it works.
I mada my own .config file and I included all neccessary modules ( or not ?) and i am wondering what is problem.

Thank you for help

[Sergejs Svitnevs]

You are trying to install kernel 2.6.15 but got output "modprobe: FATAL: Could not load /lib/modules/2.6.16-new/modules/dep".
How is this possible? What does "2.6.16" mean?

I propose to recompile kernel according to Debian instructions:
http://www.debian.org/releases/stable/i386/ch08s05.html.en

Regards,
Sergejs

[debian111]

2.6.16 is just mistyping....there shoul be 2.6.15....it is set correct in /grub/menu.lst

here it is just mistyping...

Thank you

[Ivan Ferreira]

You may try starting with a working kernel configuration, for example, do could do make oldconfig, and then, add or remove the kernel modules. Better yet if you have the .config file of your working kernel, use that as baseline.

[Sergejs Svitnevs]

But what about "modules/dep"?
Is it also a TYPE error and we should read "modules.dep"?

[debian111]

I know what you suggest me, but look at error I got, it is confusing, I think.

I tried to use old kernel configuration as my starting position, and I did not get a correct output.
Kernel says that it cannot find file
/lib/modules/2.6.15---kernel version/modules.dep but file modules.dep is there as you can see.

Anyway thank you for your suggestions and help,

regards
debian111

[debian111]

modules.dep.....
Was not able to copy/paste error I got....

modules/dep should be modules.dep...sorry people I am very tired, this problems about kernel, some other problems exshausted me.

Thank you

[Ivan Ferreira]

Sometimes, when I recompile the kernel, I have problems with LABEL= in grub.conf. Try changing the root device in grub.conf to the specific device, if it's using labels.

[Procnus]

I haven't rebuilt my kernel for awhile, but my thoughts on are:

The key might lie with the line "umount: devfs: not mounted" (I've added the v which seemed to be missing) Your devfs does not appear to be mounting. I'm guessing devfs is your problem as the FATAL came from modprobe and /dev/console could not be found.

Cheers
Steven

[Stuart Browne]

Related tot hat last post, are you sure you included the filesystem componants in the kernel?

Did you build it modular, if so did you re-build the initrd with the filesystem modules in it?

[debian111]

I have no so much experinece, could you plese be more precise, I mean can you explain it in more details, I read many HOWTOs and I got the output I posted before , so now I am in stuck, I tried the same process last night and I got the same output
when I enter in shell

dpkg -l|grep udev, I got that I am using some 0.5? I do not exacly which version, but I read somewhere that I must install udev 0.72 or later for kernel 2.6.12 or later compilation.

Shoul I install udev before kernel compiation or after kernel compilation?

Anyway I pritiete very much your help, and thank you for that.

Regards
Debian111

[Bill Thorsteinson]

2.6 deprecated DEVFS. Make sure you have
the appropriate stuff in /dev and remove
devfs from the boot functionality.

Replacement devfs funtionality is in udev.

[genti_1]

I have the same problem. I uninstalled devfs and installed udev.
kernel 2.6.15.1 boots fine but the 2.6.16.1 doesn't. Probably because it is custom build.

does the drive address change from 2.6.15 to 2.6.16? mine right now is /dev/sda but i have also some usb card adapter that takes 4 devs (sdb-sde) and whenever I ugrade a kernel or do something to the boot it replaces the sda with sde.

[genti_1]

I think i narrowed down to initrd. I used the old initrd from the previous kernel to see what happened and from there it says that /sda was not found but i can get to a prompt.

to make a initrd i used
# minitrd -o /boot/initrd.img-2.6.16-amd64-k8

any thoughts?