Kernel panic with new kernel

My Etch server boots fine with the default 2.6.18 kernel. I downloaded the 2.6.25 kernel and did: make all make modules_install make install depmod 2.6.21.3 mkinitrd.yaird -o /boot/initrd.img-2.6.25 2.6.25 Updated grub and rebooted. I'm getting a kernel panic: /usr/lib/yaird/exec/run_init:

Re: Kernel panic with new kernel

Daniel D Jones wrote: My Etch server boots fine with the default 2.6.18 kernel. I downloaded the 2.6.25 kernel and did: make all make modules_install make install depmod 2.6.21.3 mkinitrd.yaird -o /boot/initrd.img-2.6.25 2.6.25 Updated grub and rebooted. I'm getting a kernel panic:

Panic on new kernel

Got a problem with a box, dual PIII/933 2GB RAM, dual 36GB SCSI drives on a MegaRAID controller. The box is running unstable. The original kernel, linux-image-2.6.15-1-486, boots. However, this box is slated to run VMware server. Since Debian is not a supported host OS, there are no pre-compiled

Re: Panic on new kernel

Hello Bradley. So the problem I have is that any more recent stock kernel (I have tried 2.6.16-smp and 2.6.17) panics on boot: Kernel panic: No init found. Try passing init= option to kernel How does the config file of your bootmanager look like? Regards, Mathias signature.asc

Re: Panic on new kernel

Mathias Brodala wrote: Hello Bradley. So the problem I have is that any more recent stock kernel (I have tried 2.6.16-smp and 2.6.17) panics on boot: Kernel panic: No init found. Try passing init= option to kernel How does the config file of your bootmanager look like?

Re: Panic on new kernel

Hello Bradley. Kernel panic: No init found. Try passing init= option to kernel How does the config file of your bootmanager look like? Regards, Mathias Here is menu.lst (sans comments): […] Hm, doesn’t seem wrong to me. Have you tried to add something like „init=/bin/bash“ to