Messages in this thread | | | From | "Stephane GARIN" <> | Subject | RE: 2.2.19pre - Kernel Panic: no init found | Date | Tue, 6 Mar 2001 17:51:23 +0100 |
| |
I checked this but there is no error in my lilo configuration file. root value is the same for my images /boot/vmlinuz-2.2.18 (label=linux) and /boot/vmlinuz-2.2.19pre (label=linuxpre).
All it's ok if I boot on "linux" but I have this Kernel panic if I boot on "linuxpre". I used the same .config file (of 2.2.18 kernel) to make my new 2.2.19pre16 kernel.
I have lot of partitions (8). The order is :
/dev/hda1 (mounted on /boot) /dev/hda2 (extended) /dev/hda5 (mounted on /usr) /dev/hda6 (mounted on /home) /dev/hda7 (swap) /dev/hda8 (mounted on /) /dev/hda9 (mounted on /tmp) /dev/hda10 (mounted on /var)
-----Original Message----- From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of Jeremy Jackson Sent: Tuesday, March 06, 2001 5:18 PM To: Stephane GARIN Cc: linux-kernel@vger.kernel.org Subject: Re: 2.2.19pre - Kernel Panic: no init found
Stephane GARIN wrote:
> Hi, > > I tried with init=/bin/sh but no success. I download a 2.2.18 Kernel and I > use patch 2.2.19pre16 but no success too... I don't know why there is this > error with this 2.2.19 kernel but not with my 2.2.18 kernel. I'm ready to > send all technical information about my computer (PIII 650 with 256Mb and a > ABIT BX133-RAID mothercard).
looks like you have a lot of partitions. maybe the kernel isn't using the right one for root filesystem? if using LILO to boot, make sure root= line for your new kernel is the same as old one. if using redhat on a large disk, it will set up
the first partition as /boot filesystem, so kernel will mount it ok, but won't find any programs like init or sh on it.
Let me know how this works out.
> > > With Regards, > Stephane Garin > > -----Message d'origine----- > De : James Stevenson > Envoyé : samedi 3 mars 2001 18:58 > À : sgarin@sgarin.com > Objet : Re: 2.2.19pre - Kernel Panic: no init found > > Hi > > it would mean pass something like > init=/bin/sh > not the runlevel you want > > In local.linux-kernel-list, you wrote: > >Hi, > > > >I have a kernel panic with the patch 2.2.19pre16 that I test. I use a > 2.2.18 > >Kernel very well. I used the last patch on this kernel and make my kernel > >with sames parameters without error message. At the boot, I can see this : > > > >.. > >eth0: RealTek RTL8139 Fast Ethernet at 0xa800, IRQ 10, 00:50:fc:0b:60:70 > >eth1: RealTek RTL8139 Fast Ethernet at 0xac00, IRQ 11, 00:50:fc:1f:c1:98 > >Partition check: > > hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 hda10 > > >Trying to vfree() noexistent vm area (c00f0000) > >VFS: Mounted root (ext2 filesystem) readonly. > >Freeing unused kernel memory: 68k freed > >Kernel panic: No init found. Try passing init= option to kernel. > > > > > > > >I tried to start with init=3 but no change. I send this information on this > >mailing list because I think that could be a bug. Sorry if it is a wrong > >action of me... > >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |