Re: argh...no init found
On Tuesday 27 November 2001 05:58 pm, you stated : > --- John Hiemenz <[EMAIL PROTECTED]> wrote: > > > > Your mount points/names are different between the two boxes? > > (if I'm right, do I get a chocolate bar?) > > Yes, the mount points & names do differ between the two boxes. But i > don't follow on how that would cause the problem. > IF you are right, i'll gladly send you a chocolate bar. > > If root is on different mount point (partition) that would be a problem, yes? ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: SOLVED! Re: argh...no init found
On Tuesday 27 November 2001 06:02 pm, you stated : > Bingo! User error strikes again. Wrong root= for the new kernel. > Thanks. > Hersheys Symphony with almonds ;P ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: argh...no init found
Net Llama wrote: % support. It boots & runs that 2.4.5-xfs kernel perfectly. Its got a RH % OS load with bits & pieces of 6.2 & 7.x on it. % Here's when things get annoying. When I try to boot off of a 2.4.14-xfs % kernel on box #2, it always hangs just after detecting all the drives % (basically where it goes to start mounting stuff) with the error, "no % init found". First I thought that i forgot to include console support % in the kernel, but i didn't. So, i figured, i'll just use the same % .config from box #1, and i should be golden. No dice. The kernel % builds without a hitch, and when i go to boot, i get the same ugly % error. % So, i'm at my whit's end. Anyone have any ideas? Look at the root= line in /etc/lilo.conf. Kurt -- rm -rf /bin/laden ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
SOLVED! Re: argh...no init found
Bingo! User error strikes again. Wrong root= for the new kernel. Thanks. --- Dave Anselmi <[EMAIL PROTECTED]> wrote: > What does your lilo.conf look like on the box that hangs? Sounds like > you > don't have the right root= line. > > Net Llama wrote: > > > I'm incredibly stumped at a weird kernel related issue. I've got > two > > boxes with identical hardware in them (other than the CPU speed, > however > > both are PIII). > > On 1 box, i've successfully built a 2.4.14 kernel with patched xfs > > support. It boots & runs perfectly. FWIW, its got a Caldera OS > load, > > with bits & pieces of 2.4 & 3.1 on it. > > On the 2nd box, i've successfully built a 2.4.5 kernel with patched > xfs > > support. It boots & runs that 2.4.5-xfs kernel perfectly. Its got > a RH > > OS load with bits & pieces of 6.2 & 7.x on it. > > Here's when things get annoying. When I try to boot off of a > 2.4.14-xfs > > kernel on box #2, it always hangs just after detecting all the > drives > > (basically where it goes to start mounting stuff) with the error, > "no > > init found". First I thought that i forgot to include console > support > > in the kernel, but i didn't. So, i figured, i'll just use the same > > .config from box #1, and i should be golden. No dice. The kernel > > builds without a hitch, and when i go to boot, i get the same ugly > > error. > > So, i'm at my whit's end. Anyone have any ideas? = Lonni J. Friedman [EMAIL PROTECTED] Linux Step-by-step help: http://netllama.ipfox.com . __ Do You Yahoo!? Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1 ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: argh...no init found
--- John Hiemenz <[EMAIL PROTECTED]> wrote: > On Tuesday 27 November 2001 04:34 pm, you stated : > > I'm incredibly stumped at a weird kernel related issue. I've got > two > > boxes with identical hardware in them (other than the CPU speed, > however > > both are PIII). > > On 1 box, i've successfully built a 2.4.14 kernel with patched xfs > > support. It boots & runs perfectly. FWIW, its got a Caldera OS > load, > > with bits & pieces of 2.4 & 3.1 on it. > > On the 2nd box, i've successfully built a 2.4.5 kernel with patched > xfs > > support. It boots & runs that 2.4.5-xfs kernel perfectly. Its got > a RH > > OS load with bits & pieces of 6.2 & 7.x on it. > > Here's when things get annoying. When I try to boot off of a > 2.4.14-xfs > > kernel on box #2, it always hangs just after detecting all the > drives > > (basically where it goes to start mounting stuff) with the error, > "no > > init found". First I thought that i forgot to include console > support > > in the kernel, but i didn't. So, i figured, i'll just use the same > > .config from box #1, and i should be golden. No dice. The kernel > > builds without a hitch, and when i go to boot, i get the same ugly > > error. > > So, i'm at my whit's end. Anyone have any ideas? > > > > > > Your mount points/names are different between the two boxes? > (if I'm right, do I get a chocolate bar?) Yes, the mount points & names do differ between the two boxes. But i don't follow on how that would cause the problem. IF you are right, i'll gladly send you a chocolate bar. = Lonni J. Friedman [EMAIL PROTECTED] Linux Step-by-step help: http://netllama.ipfox.com . __ Do You Yahoo!? Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1 ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: argh...no init found
John Hiemenz wrote: > I assume the kernel reads /etc/fstab to (re) mount / and /boot (if there) > after getting initial values from the bootloader and that it isn't hardcoded > into the kernel somewhere. I'm not a kernel wacker, to say the least, just > propounding audibly. No, the kernel only reads what lilo gives it. Telling lilo root= is how the kernel knows what to mount as root (and it only mounts it once - subsequent mounts are done by init). mount is what reads /etc/fstab. Dave ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: argh...no init found
On Tuesday 27 November 2001 04:48 pm, you stated : > > So, i'm at my whit's end. Anyone have any ideas? > > Your mount points/names are different between the two boxes? > (if I'm right, do I get a chocolate bar?) > ___ forget I said anything. I re-read your message a few times, I don't think you said anything about changing lilo or menu.lst, so mount points shouldn't be involved, should they. I assume the kernel reads /etc/fstab to (re) mount / and /boot (if there) after getting initial values from the bootloader and that it isn't hardcoded into the kernel somewhere. I'm not a kernel wacker, to say the least, just propounding audibly. ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: argh...no init found
What does your lilo.conf look like on the box that hangs? Sounds like you don't have the right root= line. Net Llama wrote: > I'm incredibly stumped at a weird kernel related issue. I've got two > boxes with identical hardware in them (other than the CPU speed, however > both are PIII). > On 1 box, i've successfully built a 2.4.14 kernel with patched xfs > support. It boots & runs perfectly. FWIW, its got a Caldera OS load, > with bits & pieces of 2.4 & 3.1 on it. > On the 2nd box, i've successfully built a 2.4.5 kernel with patched xfs > support. It boots & runs that 2.4.5-xfs kernel perfectly. Its got a RH > OS load with bits & pieces of 6.2 & 7.x on it. > Here's when things get annoying. When I try to boot off of a 2.4.14-xfs > kernel on box #2, it always hangs just after detecting all the drives > (basically where it goes to start mounting stuff) with the error, "no > init found". First I thought that i forgot to include console support > in the kernel, but i didn't. So, i figured, i'll just use the same > .config from box #1, and i should be golden. No dice. The kernel > builds without a hitch, and when i go to boot, i get the same ugly > error. > So, i'm at my whit's end. Anyone have any ideas? > > = > > Lonni J. Friedman [EMAIL PROTECTED] > > Linux Step-by-step help: http://netllama.ipfox.com > > . > > __ > Do You Yahoo!? > Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. > http://geocities.yahoo.com/ps/info1 > ___ > Linux-users mailing list > Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: argh...no init found
On Tuesday 27 November 2001 04:34 pm, you stated : > I'm incredibly stumped at a weird kernel related issue. I've got two > boxes with identical hardware in them (other than the CPU speed, however > both are PIII). > On 1 box, i've successfully built a 2.4.14 kernel with patched xfs > support. It boots & runs perfectly. FWIW, its got a Caldera OS load, > with bits & pieces of 2.4 & 3.1 on it. > On the 2nd box, i've successfully built a 2.4.5 kernel with patched xfs > support. It boots & runs that 2.4.5-xfs kernel perfectly. Its got a RH > OS load with bits & pieces of 6.2 & 7.x on it. > Here's when things get annoying. When I try to boot off of a 2.4.14-xfs > kernel on box #2, it always hangs just after detecting all the drives > (basically where it goes to start mounting stuff) with the error, "no > init found". First I thought that i forgot to include console support > in the kernel, but i didn't. So, i figured, i'll just use the same > .config from box #1, and i should be golden. No dice. The kernel > builds without a hitch, and when i go to boot, i get the same ugly > error. > So, i'm at my whit's end. Anyone have any ideas? > > Your mount points/names are different between the two boxes? (if I'm right, do I get a chocolate bar?) ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
