Re: 2.2.0 no-go (2.2.0-final was ok). (more)

Romano Giannetti (romano@dea.icai.upco.es)
Tue, 26 Jan 1999 17:17:34 +0100

On Tue, Jan 26, 1999 at 04:49:02PM +0100, Romano Giannetti wrote:
> This is something that *really* puzzles me. With the same exact system,
> config, etc, 2.2.0-final work beautifully and 2.2.0 refuse to boot: the
> screen is filled by endless, rapidly scrolling messages that (seems to
> me) tell that some fork failed trying to exec modprobe.
> I have kmod built in, and in 2.2.0-final it works perfectly.
> One hour looking at patch-2.2.0-final.gz and no idea.
> Can anyone help here? TIA,
> Romano
>

Another data point: if I remove kmod, I have ...init not found, please
use init= option. Tried single, init=/bin/bash, no-go. It seems like it
is mounting the wrong root partition (but I cannot say). My
/etc/lilo.conf doesn't have typo :) and for safe22pre (that's
2.2.0-final) it worked:

boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=200
image=/boot/bzImage
label=linux22
root=/dev/hda5
read-only
vga=771
append="hdc=noautotune"
image=/boot/vmlinuz-2.0.36-0.7
label=linux20
root=/dev/hda5
read-only
other=/dev/hda1
label=win
table=/dev/hda
image=/boot/bzImage.save
label=safe22pre
root=/dev/hda5
read-only
vga=771

-- 
Romano Giannetti, Professor  -  Univ. Pontificia Comillas (Madrid, Spain)
Electronic Engineer - phone +34 915 422 800 ext 2410  fax +34 915 596 569


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/