Date: Fri, 15 May 1998 16:26:38 -0600 (MDT) From: "Justin T. Gibbs" <gibbs@narnia.plutotech.com> To: Werner Griessl <werner@btp1da.phy.uni-bayreuth.de> Cc: stable@FreeBSD.ORG Subject: Re: broken remote boot Message-ID: <199805152226.QAA24093@narnia.plutotech.com> In-Reply-To: <199805151243.OAA16044@btp1da.phy.uni-bayreuth.de>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <199805151243.OAA16044@btp1da.phy.uni-bayreuth.de> you wrote: > I have a problem with diskless remote boot. > I verified, that the changes preventing remote boot > comes between May 6 and May 7 into the stable sources. > With a client kernel from May 6 remote boot is ok, > with a kernel from May 7 the boot fails with: > > "panic: cannot mount root" > > The kernel loads vio bootp, checks the devices up to > "npx0: INT 16 interface", then comes the panic. > normally followes the lines: > NFS SWAP: ... > NFS ROOT: ... > > Here are all files which change between May 6 and 7 : It was probably the changes I made to autoconf.c, but as I don't perform any diskless booting it will be difficult for me to determine what exactly is causing the problem. Can you instrument i386/i386/autoconf.c and determin why it fails to consider an NFS root? > Werner -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805152226.QAA24093>