On Tue, 1 Feb 2005 23:56:22 +0100, Jochen Kunz <jkunz@unixag-kl.fh-kl.de> w=
rote:
> On Mon, 31 Jan 2005 22:56:09 -0600
> Keith Bennett <kanezor@gmail.com> wrote:
>=20
> > Here's anothere place where my terminal is rather annoying...
> You should check if you can reconfigure your terminal to an other
> terminal emulation. If this fails you should use a different terminal.
>=20
> > >> NetBSD/prep BOOT, Revision 1.5
> > >> (builds@build, Mon Dec  6 00:12:27 UTC 2004)
> >
> > Boot: Loading in()
> > 3537044+185960=3D0x38d160
> > start=3D0x100000
> >
> > panic: lockmgr: no context
> This is not the patched kernel, this is the original broken kernel. The
> patched kernel will report "build@Zimbo, Mon Jan 24 09:45:11 CET 2005".
> (Actually this is the boot loader, not the kernel.)
>=20
> Most likely you have messed up the boot images or the disk ordering when
> writing the disks. I recommend to remove all but the boot disk if you
> have multiple disks in the target machine.
Aha! Mentioning this reminded me that I had tried installing one of
the old kernels on my second disk, and had set my boot order to
accomodate.

I've fixed this now, and I'm now booting up in the patched kernel.


Thanks, everyone. Aside from the kernel not detecting what its root
device is, are there any other problems I should be aware of regarding
the prep port?

>=20
> Also note that you have to write the generic_com0.fs image to the boot
> disk, not sysinst_com0.fs. The later is for instaling only, the former
> is the GENERIC kernel intended to run the system after instalation.
> --
>=20
> tsch=FC=DF,
>        Jochen
>=20
> Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/
>=20
>