Hello!

I aquired one of those Digital Multias machine that recently have been sold by
CPU Micromart and am now trying to run it as a diskless station using NetBSD
1.3.2, but am stuck at the point where the "netbsd" file (the kernel) should be
transferred. The Multia just does not seem to try to NFS mount the proper
directory. Here is the exact description of the problem:

As server, i intend to use a machine running FreeBSD 2.2.8 (i386). The server
is 192.168.1.2, the diskless client should be 192.168.1.5. My bootptab on
FreeBSD looks as follows:

vulcan.bland.fido.de.master:\
        :ip=3D192.168.1.1:\
        :td=3D/tftpboot:hd=3D/tftpboot:bf=3Dboot.netbsd.alpha:\
        :rp=3D/usr/clients/alpha/netbsd:\
        :ht=3Dethernet:ha=3D08002be436a9:\
        :sm=3D255.255.255.0:sa=3D192.168.1.2:
vulcan.bland.fido.de:ha=3D08002be436a9:tc=3Dvulcan.bland.fido.de.master:
vulcan.bland.fido.de:ha=3D08002be4e052:tc=3Dvulcan.bland.fido.de.master:

Where the first mac address is the one that the srm console shows, and the
second is the one that was printed on the box in which I received the machine.

Unter /tftpboot, I have placed boot.netbsd.alpha. Because my SRM console seems
to be too old, I had to compile setnetbootinfo for FreeBSD and patch the file
with the MAC address (I tried both ...). Later, assuming my hack for
setnetbootinfo might be faulty, I also tried the netboot images that are
generated at http://www.imrryr.org/NetBSD/alpha/netboot/ (again both MAC
addresses), but the problem remaind the same.

Now to the boot process: I boot the machine using

  Multia SRM Console  BL3 X3.5-72, built on Nov 30 1994 at 18:22:35
  >>> boot -prot bootp ewa0.

The first bootp connect succeeds, FreeBSD bootpd prints:

  bootpd: info(6):   bootptab mtime: Wed Feb 17 19:54:44 1999
  bootpd: info(6):   reading "/etc/bootptab"
  bootpd: info(6):   read 3 entries (3 hosts) from "/etc/bootptab"
  bootpd: info(6):   recvd pkt from IP addr 0.0.0.0
  bootpd: info(6):   bootptab mtime: Wed Feb 17 19:54:44 1999
  bootpd: info(6):   request from Ethernet address 08:00:2B:E4:36:A9
  bootpd: info(6):   found 192.168.1.5 (vulcan.bland.fido.de)
  bootpd: info(6):   bootfile=3D"/tftpboot/boot.netbsd.alpha"
  bootpd: info(6):   vendor magic field is 0.0.0.0
  bootpd: info(6):   sending reply (with no options)
  bootpd: info(6):   setarp 192.168.1.5 - 08:00:2B:E4:36:A9

and the Multia correctly displays all information:

  Trying BOOTP boot.

  Broadcasting BOOTP Request...
  Received BOOTP Packet File Name: /tftpboot/boot.netbsd.alpha
  Bflags are 2
  Server name: romulus.bland.fido.de
  Boot filename is /tftpboot/boot.netbsd.alpha
  TFTP server name is romulus.bland.fido.de
  TFTP server ip address is 192.168.1.2
  TFTP server hw address is 00-00-b4-82-6c-6b
  TFTP local ip address is 192.168.1.5
  TFTP local hw address is 08-00-2b-e4-36-a9
  local inet address: 192.168.1.5
  remote inet address: 192.168.1.2
  TFTP Read File Name: /tftpboot/boot.netbsd.alpha
  ..
  bootstrap code read in
  base =3D 154000, image_start =3D 0, image_bytes =3D 16e08
  initializing HWRPB at 2000
  initializing page table at 146000
  initializing machine state
  setting affinity to the primary CPU
  jumping to bootstrap code

  NetBSD/Alpha Network Root, Revision 1.6
  (root@mabelode.imrryr.org, Tue NOV 17 01:29:08 PST 1998)

  VMS PAL rev: 0x1000000010530
  OSF PAL rev: 0x1000000020123
  Switch to OSF PAL code succeeded.

  Boot flags: 0

  Loading netbsd...
  boot: boot device name does not contain ethernet address.
  boot: using hard-coded ethernet address.
  boot: ethernet address: 08:00:2b:e4:36:a9
  bootp: no reply
  net_open: BOOTP failed
  open netbsd: Input/output error

Do you have any hints on what is going wrong here? The second bootp attemt
never seems to reach my bootpd at all!?

Viele Gr=FC=DFe,
Tobias