From owner-freebsd-alpha Wed Oct 27 17:44:13 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 80AE514C3D for ; Wed, 27 Oct 1999 17:43:50 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40325>; Thu, 28 Oct 1999 10:38:44 +1000 Content-return: prohibited Date: Thu, 28 Oct 1999 10:43:40 +1000 From: Peter Jeremy Subject: Re: Netbooting a Multia with FreeBSD In-reply-to: <19991019085210.A86077@gsmx07.alcatel.com.au> To: freebsd-alpha@freebsd.org, multia-users@explode.unsw.edu.au Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct28.103844est.40325@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <19991019085210.A86077@gsmx07.alcatel.com.au> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 1999-Oct-19 08:52:10 +1000, I wrote: >My problem is that netboot seems unable to accept the DHCP or RARP >responses returned to its requests. It just cycles between DHCP >and RARP requests until it times out. After some experimenting, it appears that making broken_firmware a boolean in /usr/src/sys/boot/alpha/libalpha/srmnet.c does not cover the Multia (at least with SRM 3.8.3). This SRM is broken enough to need the MAC address explicitly included in netbbinfo, but call to prom_read() in prom_get() _does_ need to specify the receiving structure size (ie the broken_firmware test is not needed). Without background on what other varieties of brokenness DEC implemented in various SRMs, I can't offer a sensible patch. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message