Hi !

> Does error=60 mean that it got no response from the bootparam server?

Yes ! (don't know exactly, but this is the problem in your case.)

> When I run rpc.bootparamd -d, I see no debug output.
> 
> curiously tho, doing a tcpdump shows this:
> 
> 21:57:08.485148 vax.1023 > 10.255.255.255.sunrpc: udp 96
> 
> it looks like the kernel has got the wrong bcast address.
> (The LAN here is a 10.0.0.0/24 network.  The VAX is 10.0.0.4 and the alpha
> which which is the boot server is 10.0.0.3)

Something 'bout netmasks:

The kernel must figure out the netmask when doing bootparams, because
this protocol doesn't transmits it. And the kernel does right, i looked
insiside (something with bootparams.c or so). The specs of netmasks for
private networks are:

10.x.x.x and 127.x.x.x -> Class-A network, Netmask 255.0.0.0
172.16.x.x - 172.31.x.x -> Class-B network, Netmask 255.255.0.0
192.168.0.x - 192.168.255.x -> Class-C network, Netmask 255.255.255.0

So the kernel figures out the right netmask, as the internet gurus say.
I have a 192.168-network running here, everything works. You have two
possibilities to make it right:
1) Change to a 192.168 network
2) Patch the kernel, that it does bootp when mounting the root fs (maybe
i try it somewhen, because my whole network works with bootp here,
including linux and windoze boxes).

cu.. Michael