Hello,

I have been attempting to netboot a multia from a PC164 and am bumping into
a problem which has been reported before.  I've read the HOWTO's and FAQ's
and think I have everything set up properly... correct me if I'm wrong. :-)

BTW, I've netbooted Linux on this client before, using the same server
(running NetBSD).

Here is what I'm getting on the client (serial console):

CPU 0 booting

(boot ewa0.0.0.8.0 -flags a)

Trying BOOTP boot.

Broadcasting BOOTP Request...
Received BOOTP Packet File Name: boot.netbsd.alpha
Bflags are 2
Server name:
Boot filename is boot.netbsd.alpha
TFTP server name is
TFTP server ip address is 192.168.216.5
TFTP server hw address is 00-00-f8-08-e6-74
TFTP local ip address is 192.168.216.9
TFTP local hw address is 08-00-2b-e4-db-6c
local inet address: 192.168.216.9
remote inet address: 192.168.216.5
TFTP Read File Name: boot.netbsd.alpha
.
bootstrap code read in
base = 154000, image_start = 0, image_bytes = fa30
initializing HWRPB at 2000
initializing page table at 146000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
waiting for pka0.7.0.6.0 to change mode to 2...
waiting for pka0.7.0.6.0 to change mode to 2...
waiting for pka0.7.0.6.0 to change mode to 2...
waiting for pka0.7.0.6.0 to change mode to 2...
waiting for pka0.7.0.6.0 to change mode to 2...

NetBSD/alpha 1.6_STABLE Network Bootstrap, Revision 1.9
(bryan@jupiter, Tue Nov 19 16:37:06 PST 2002)

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

Boot flags: a
boot: boot device name does not contain ethernet address.
boot: using hard-coded ethernet address.
boot: ethernet address: 08:00:2b:e4:db:6c
bootp: no reply
net_open: BOOTP failed
open netbsd: Input/output error
boot: boot device name does not contain ethernet address.
boot: using hard-coded ethernet address.
boot: ethernet address: 08:00:2b:e4:db:6c
bootp: no reply
net_open: BOOTP failed
open netbsd.gz: Input/output error

...

The last failure sequence repeats until the netboot aborts.  On the server
(NetBSD-1.6), I see the following log entries:

Jan 18 16:01:16 jupiter dhcpd: BOOTREQUEST from 08:00:2b:e4:db:6c via tlp0
Jan 18 16:01:16 jupiter dhcpd: BOOTREPLY for 192.168.216.9 to pluto (08:00:2b:e4:db:6c) via tlp0
Jan 19 00:01:16 jupiter tftpd[3614]: pluto.terran: read request for boot.netbsd.alpha: success
Jan 18 16:01:46 jupiter dhcpd: DHCPDISCOVER from 08:00:2b:e4:db:6c via tlp0
Jan 18 16:01:46 jupiter dhcpd: DHCPOFFER on 192.168.216.9 to 08:00:2b:e4:db:6c via tlp0
Jan 18 16:01:48 jupiter dhcpd: DHCPDISCOVER from 08:00:2b:e4:db:6c via tlp0
Jan 18 16:01:48 jupiter dhcpd: DHCPOFFER on 192.168.216.9 to 08:00:2b:e4:db:6c via tlp0

...

The last entries (DISCOVER/OFFER instead of REQUEST/REPLY) repeat with each
failed client boot attempt.  BTW, why would the first request be "BOOT..."
and the subsequent ones "DHCP..." ?

Here is the dhcpd.conf configuration (excerpt) I am using on the server:

host pluto {
        hardware ethernet 08:00:2b:e4:db:6c;
        fixed-address 192.168.216.9;
        always-reply-rfc1048 on;
        use-host-decl-names on;
        option host-name "pluto";
        option root-path "/usr/local/net/pluto";
        next-server jupiter;
        filename "boot.netbsd.alpha";
}

And on the server, the NFS setup yields:

% showmount -e
Exports list on localhost:
/usr/local/net/pluto/usr           pluto.terran
/usr/local/net/pluto/swap          pluto.terran
/usr/local/net/pluto/root          pluto.terran
/usr/local/net                     192.168.216.0
%

with "netbsd" in /usr/local/net/pluto/root

Any ideas about what to do next?

thanks,
-bp
--
# Software Engineer