Date: Tue, 30 Nov 1999 06:47:18 +1100 From: Peter Jeremy <jeremyp@gsmx07.alcatel.com.au> To: manning@uclink4.berkeley.edu Cc: alpha@FreeBSD.ORG Subject: Re: UPDATE: boot install disk on multia Message-ID: <99Nov30.064004est.40335@border.alcanet.com.au> In-Reply-To: <384237C8.ECDD6C0D@uclink4.berkeley.edu> References: <199911290803.AAA02716@mass.cdrom.com> <384237C8.ECDD6C0D@uclink4.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1999-Nov-29 19:22:32 +1100, manning@uclink4.berkeley.edu wrote: >And about the network install: i WILL go read the doc's on it, but do you do >it over the serial link? or ethernet? I'm reasonably certain that it's not possible using the serial link: The main serial link is used as the console. According to my reading of the kernel config file, the second link is "reserved for low-level IO" (though I haven't tried using it). It's just painful over Ethernet: The Multia SRM is broken in ways that are incompatible with netboot: The SRM is old enough to require the MAC address hard-coded into netboot (reasonably simple given a binary editor and a 64-bit hex calculator), but does not meet netboot's associated definition of `broken_firmware'. This basically means that you either need a _good_ binary editor (capable of patching constants buried in the code), or you need to re-compile netboot. The 3.2-RELEASE (and earlier) netboots also abuse DHCP (this is fixed back to BOOTP in the later versions). The easiest way is probably to DD the 2.88MB boot image onto a SCSI disk. This can be the same disk you're installing to (though you'll get a warning about partition size mismatches, which can be safely ignored). Peter 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?99Nov30.064004est.40335>