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: No such file or directory Attempted to kill init From what I can find, this is usually related to moving partitions around or otherwise confusing the system as to where the root system is located. I haven't changed anything as to partition layout. The system boots fine with the old kernel. The grub entries are identical except for the number associated with the kernel. The root (hd0,1) and the root argument applied to the kernel are both the same and are correct. Any hints or suggestions as to where to go from here appreciated. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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: /usr/lib/yaird/exec/run_init: No such file or directory Attempted to kill init From what I can find, this is usually related to moving partitions around or otherwise confusing the system as to where the root system is located. I haven't changed anything as to partition layout. The system boots fine with the old kernel. The grub entries are identical except for the number associated with the kernel. The root (hd0,1) and the root argument applied to the kernel are both the same and are correct. Any hints or suggestions as to where to go from here appreciated. Daniel, Try the debian way, it is way easy. apt-get install kernel-package do all the normal untaring and such. cd into the kernel dir: cp /boot/someimage.config ./.config make menuconfig/gconfig/oldconfig make-kpkg clean make-kpkg --initrd --revision=1.something (letters will keep dpkg from replacing with an upgrade) kernel_image module_image (---I use this one to get nvidia w/custom kernel see debian nvidia wiki) when you are done you have a linux-image-somestring.deb and any modules you made.deb one dir up. dpkg -i string.deb dpkg -i modulename.deb you are now done, further, you package system can now track your kernel, remove it, replace it, what ever. Grub is updated. see /usr/share/doc/kernel-package/README.gz for step by step (all though I just gave it to you, there are other options) The .deb can be transported to a like machine if desired or simple admired. I only had to make module_image for nvidia use on a custom kernel. Presumably, if you needed to make a module work with a running kernel, you would know it. In short, Daniel, I have no idea why you can't bood, but following these steps should fix the problem. HTH. -- Damon L. Chesser [EMAIL PROTECTED] http://www.linkedin.com/in/dchesser -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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 modules for the kernel. The installed kernel was built with gcc-4.0.3, but the installed gcc is 4.1.5, which means the module will not load. 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 I have generally rolled my own kernels in the past, what is the proper way of getting a stock kernel installed? (I have cramfsprogs and yaird installed) --b -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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 Description: OpenPGP digital signature
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? Regards, Mathias Here is menu.lst (sans comments): default 0 timeout 5 color cyan/blue white/blue title Debian GNU/Linux, kernel 2.6.16-2-686-smp root(hd0,0) kernel /boot/vmlinuz-2.6.16-2-686-smp root=/dev/sda1 ro initrd /boot/initrd.img-2.6.16-2-686-smp savedefault title Debian GNU/Linux, kernel 2.6.16-2-686-smp (recovery mode) root(hd0,0) kernel /boot/vmlinuz-2.6.16-2-686-smp root=/dev/sda1 ro single initrd /boot/initrd.img-2.6.16-2-686-smp savedefault title Debian GNU/Linux, kernel 2.6.15-1-486 root(hd0,0) kernel /boot/vmlinuz-2.6.15-1-486 root=/dev/sda1 ro initrd /boot/initrd.img-2.6.15-1-486 savedefault title Debian GNU/Linux, kernel 2.6.15-1-486 (recovery mode) root(hd0,0) kernel /boot/vmlinuz-2.6.15-1-486 root=/dev/sda1 ro single initrd /boot/initrd.img-2.6.15-1-486 savedefault -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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 one of the kernels and booting it thereafter? Regards, Mathias signature.asc Description: OpenPGP digital signature
