Thnx but I've already tried ALL of your suggestions (it's there all written down, isn't it ;) ?, I might have missed something?) ~
My main question still stands unanswered: > Here's my big question: when I boot from a CD Linux-image, does my system still use the init in /dev/hda2/sbin/ ? (I think so since there's no init on the CD) > Why then can my new kernel not use this init but more important: why can't my old kernel too! (the one after first installation residing on my HDD which is now named vmlinuz.old) > to try and make things a little more clear: the kernel boots! Lilo works fine! it is the init part where all activity halts at the point where normally the supplementary hardware (sound, network, mice, special CD-romplayers, etc) would be initialized after which the daemons would be started. At the moment of halt the memory is filled with kernel but not yet with system configuration. ??que?? I'm confused of this. Help! Mythiq. ----- Original Message ----- From: ktb <[EMAIL PROTECTED]> To: <[email protected]> Sent: Monday, June 11, 2001 8:58 AM Subject: Re: weird problem with init after compiling new kernel On Mon, Jun 11, 2001 at 12:45:03AM +0200, Mythiq wrote: > hello everyone, > > I have compiled a new kernel for an 486 which was going to be a filtering firewall. Not for a while I'm afraid, because it won't boot up anymore. (btw: I started with a clean freshly installed system with debian 2.2.18pre21) > Lilo works fine; it boots the kernel; > after the kernel has started booting, there is a step where the ext2 fs root is mounted read-only (as usual); > the next step is my problem: "kernel-panic, no init found. try to pass init= to the kernel." and there it halts. > > No problem I thought, reboot, hold shift at startup and inform lilo to pass init=/sbin/init to the kernel (which is a stupid thing to do since that is the default, this part ought to go by itself!) right: that did'nt work. > > > Here's my big question: when I boot from a CD Linux-image, does my system still use the init in /dev/hda2/sbin/ ? (I think so since there's no init on the CD) > Why then can my new kernel not use this init but more important: why can't my old kernel too! (the one after first installation residing on my HDD which is now named vmlinuz.old) > > Would be nice if anyone can help. baking a kernel on this machine takes about half a day... Did you change your /etc/lilo.conf to reflect the new kernel changes? Did you run /sbin/lilo after installing the new kernel? If not that could be why you can't access your kernels. At the boot prompt try linux init=/bin/sh or linux single That may get you in so you can fix your problem. hth, kent -- From seeing and seeing the seeing has become so exhausted First line of "The Panther" - R. M. Rilke -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
