Date: Mon, 11 Oct 1999 23:18:17 +0200 (CEST) From: Wilko Bulte <wilko@yedi.iaf.nl> To: cgd@netbsd.org (Chris G. Demetriou) Cc: freebsd-alpha@freebsd.org Subject: Re: DEC3000/400 SRM bootp overview Message-ID: <199910112118.XAA43196@yedi.iaf.nl> In-Reply-To: <87ln9966a8.fsf@redmail.netbsd.org> from "Chris G. Demetriou" at "Oct 11, 1999 12:34: 7 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
As Chris G. Demetriou wrote ... > Wilko Bulte <wilko@yedi.iaf.nl> writes: > > * SRM 7.0 (latest available revision) > > - does not do BOOTP correctly, "? T_ERR_NI - RECEIVE_TIMEOUT" > > - this rev is useless for bootp network boot > > > > * SRM 6.9 > > - does not do BOOTP correctly, "? T_ERR_NI - RECEIVE_TIMEOUT" > > - this rev is useless for bootp network boot > > There are similar issues with some versions of the firmware for > 3000/300 models, too. > > I ran into them when I was developing the NetBSD/alpha code at CMU. > I/we pushed on it a bit with various contacts that we had at DEC, and > it came back that apparently the SRM folks said that it was due to a > "hardware problem"... never mind that previous revisions of the > firmware worked fine. I just noticed that SRM 6.0 had a timeout problem when booting from my Aspen Alpine (EB64+) whereas the same SRM 6.0 worked OK booting from my K6-2 box. This leads me to the suspicion that there is something *very* timing critical (or something close to that) on the later SRM revs. Chris, as I understand it you had NetBSD booting using bootp from SRM. Or did you use MOP maybe? IIRC NetBSD can do MOP boot serving. > "stupid, stupid, stupid." Eh, yeah. -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199910112118.XAA43196>