no init found when installing 2.4.27
I'm having trouble when I upgrade to kernel 2.4.27.. I dont understand why, but I keep getting the error -
"Warning: unable to open an initial console. Kernel panic: No init found. Try passing init= option to kernel" I've read previous posts about this problem and have google'd it but anything suggested doesn't seem to fix it for me. I installed Debian using the cd ISO's with the bf24 boot image(i've tried 2.2 boot and it does the same thing), so it currently has 2.4.18. I got the NIC working and downloaded the source for 2.4.27, and when compiling the kernel everything goes smoothly, I make my lilo image, reboot, and when I choose the new "Linux" option, it attempts to boot the new kernel and it gets this message. It does the same with the 2.6 series kernel. I've compiled kernel's on debian quite a few times in the past and have never run into this problem, its only on this specific machine. I can load the original kernel(2.4.18) just fine. I've tried using init=/bin/sh, init=/sbin/init at the boot prompt and I still get the same message. It's strange how I can boot 2.4.18 just fine but when trying other kernel's that I've compiled it wont work.. Maybe I'm missing something in the compile but I've never had this problem before. I'll give some hardware info about the machine: Pentium 4 3.0ghz ATI Radeon 9700PRO 1 GB ram 200GB HDD Any other info anyone needs please just ask for it, and I appreciate any feedback. Thanks. |
report this poswhy compile from s kernel already exists...
apt-get install kernel-image-2.4.27.xxx.deb |
Quote:
|
Maybe a stupid question, but the bf2.4 kernel does not use an initrd image, while non bf kernels usually do.
Are you sure that your kernel does not expect an intrd image? If it does expect an initrd image, turn it off by building the kernel without the --initrd option. If you re-use the old config file, that is without initrd, be sure to use the 2.4.18-bf2.4 config file, which has IDE support compiled in: CONFIG_IDEDISK_MULTI_MODE=y If you use initrd, be sure that it is mentioned in your lilo.conf initrd=/initrd.img #make sure this is the correct file! Also, I have experienced problems that the cramfs format for initrd was not supported. A precompiled kernel using initrd worked fine, a self-built did not! jlinkels |
All times are GMT -5. The time now is 07:36 AM. |