From owner-freebsd-alpha Tue Oct 12 10:58:30 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id DEB3914EDF for ; Tue, 12 Oct 1999 10:58:14 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA26642; Tue, 12 Oct 1999 19:42:54 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA55060; Tue, 12 Oct 1999 19:37:00 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199910121737.TAA55060@yedi.iaf.nl> Subject: Re: DEC3000/400 SRM bootp overview In-Reply-To: from Thomas Gellekum at "Oct 12, 1999 8:26:37 am" To: tg@ihf.rwth-aachen.de (Thomas Gellekum) Date: Tue, 12 Oct 1999 19:37:00 +0200 (CEST) Cc: cgd@netbsd.org, freebsd-alpha@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Thomas Gellekum wrote ... > cgd@netbsd.org (Chris G. Demetriou) writes: > > > Wilko Bulte writes: > > > 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. My above observation was not a valid one it seems. At least not universal. The Sandpiper now boots via bootp from the Alpine without problem, apart from the wellknown: Boot device name was: "BOOTP 0 7 0 0 0 2 CORE-IO" Your firmware may be too old to network-boot NetBSD/Alpha, or you might have to hard-code an ethernet address into your network boot block with setnetbootinfo(8). > > the symptom that i noticed when looking into it was that using tcpdump > > to watch the packets that were coming out of the alpha would show > > packets with bad checksums. (I forget whether they were the bootp or > > tftp requests, or whether the bad checksums were the IP or UDP > > checksums... It's been a few years... 8-) > > Same thing here with two 3000/300s. The TFTP packet contains '\0' at > the TOS and the first bytes of the file name fields. The firmware rev > is 6.5. Where can I get older/working versions? I have the f/w images, that is not the problem. How would you get them onto the machine is the question. I mean, the machines support upgrading firmware via bootp. Sort of chicken and egg. MOP netbooting should also work for f/w updates I think. Do you have a host capable of MOP serving maybe? W/ -- | / 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