Date: Mon, 11 Oct 1999 21:13:49 +0200 (CEST) From: Wilko Bulte <wilko@yedi.iaf.nl> To: freebsd-alpha@freebsd.org (FreeBSD-alpha mailing list) Subject: DEC3000/400 SRM bootp overview Message-ID: <199910111913.VAA01776@yedi.iaf.nl>
next in thread | raw e-mail | index | archive | help
See below of the results of my experiments with the various SRM revs
for the DEC3000/400. It seems that 6.0 is the latest one that works
for bootp netbooting. That is, it is the latest rev before 6.9 that I
have in my firmware CD collection.
For all bootp capable SRMs you still need to hack netboot itself because
the system does not return the device it is booting from in the
"boot device name" (should be in the last field, nr 9, whereas these
SRMs only return 8 fields).
I'm now going back to 6.0 and take a close look at netboot.
hope this helps,
Wilko
-------
DEC3000/400 "Sandpiper" SRM version info
========================================
Questions/remarks to wilko@freebsd.org
Mon Oct 11 20:44:08 CEST 1999
How to find out what SRM is currently on the system
---------------------------------------------------
>>> show conf
DEC 3000 - M400
Digital Equipment Corporation
VPP PAL X5.48-82000101/OSF PAL X1.35-82000201 - Built on 20-JUL-1994
12:19:54.68
TCINFO DEVNAM DEVSTAT
------ -------- --------
CPU OK KN15-BA -V5.1-S749-I196-sV1.0-DECchip 21064 P3.0
^--- this is the SRM version
How to get a bootp network boot
-------------------------------
>>> BOOT EZ0
How to down/upgrade the SRM
---------------------------
Insert firmware CD. Read the little booklet (if available)
>>> BOOT DKA400 -FL 0,80
Follow menu. For older CDs you need to tell the bootloader what
file you want when it prompts for it. The filename is something
like [DEC3000]M400_V7_0.EXE VMS-knowledge will help you a bit with
this syntax ;-)
Overview of what SRM revs do with respect to bootp network booting
------------------------------------------------------------------
* 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
* SRM 6.0
- needs hardcoded ethernet address in 'netboot'
- supplies "BOOTP 0 7 0 0 0 2 CORE-IO" as boot device name
* SRM 5.2
- needs hardcoded ethernet address in 'netboot'
- supplies "BOOTP 0 7 0 0 0 2 CORE-IO" as boot device name
* SRM 5.1
- needs hardcoded ethernet address in 'netboot'
- supplies "BOOTP 0 7 0 0 0 2 CORE-IO" as boot device name
* SRM 3.3
- needs hardcoded ethernet address in 'netboot'
- supplies "BOOTP 0 7 0 0 0 2 CORE-IO" as boot device name
* SRM 3.2
- does not do BOOTP correctly, "Host server IP address is 192.168.200.1
AUDIT_BSERVER_FOUND 84 FAIL"
--
| / 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?199910111913.VAA01776>