> I have made the relevant changes that you outlined below.
> After making these changes, I noticed that the dmesg file does
> configure the device but the mac address is not resolved.

Well, apparently the driver thinks the ethernet address is the
ethernet broadcast address.  Not Good.

> I can ping x.x.x.1 or x.x.x.255 or the IP address of the unit
> but I can not ping any of the other units on the network or the
> gateway.  I presume that this is because of the unit not having
> a unique IP address.

Er, I think you meant to say "because the the machine thinks that
it's MAC address is the ethernet broadcast address".

> I have included the dmesg file from the unit.

Uh, not a complete one; the start isn't included.  Any chance you
could increase MSGBUFSIZE (see options(4)) to e.g. 16K and
re-send the result?

I see another nit-picky thing which probably isn't going to cure
this problem, which is that you have "ukphy1 at fxp0", while
according to the files in -current's sys/dev/mii/, you should
have "inphy at fxp0".  (However, 1.6.1 would behave the way your
dmesg shows.)

Which version of NetBSD is it you're trying to make go, again,
BTW?  If it's a variant of 1.6.1, it might be worth retrying with
a -current kernel.  If that fails, I suspect someone with better
documentation and more insight into the fxp driver than I have
will need to take a closer look at this.

Regards,

- H=E5vard