On Thu, 18 Jun 1998, Chris Cowdery wrote:

> 
> podulebus0 (root)
> podule2  at podulebus0 : ICS : IDE Interface : IDE Interface
> netslot0 at podulebus0 : I-Cubed : etherlan 600 network slot interface : i-cubed ltd, EtherLan 600 interface (00:c0:32:00:26:d7)
> eh0 at podulebus0 [ netslot 0 ]:1.2.3.4.5. address 00:00:a4:10:32:76 pio mode
>
Okay I guess the new ne0 driver hasn't been pulled into the 1.3.2 release
branch. 
> I did wonder at this point about the interface being identified as eh0 not ne0,
> so I changed the config to use eh0. The boot ran without any errors, and ifconfig -a
> now gives:
> 
> eh0: flags=463<UP,BROADCAST,NOTRAILERS,RUNNING,OACTIVE> mtu 1500
> 	address: 00:00:a4:10:32:76
> 	inet 1.0.0.4 netmask 0xff000000 broadcast 255.255.255.0
> lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 32976
> 	inet 127.0.0.1 netmask 0xff000000 
>
Thats good the driver has recognised and is talking to the card okay.

> However, it still doesn't work!........(in BSD/arm32)
> 
I can only think of two problems. You are using a 10BaseT connection which
ISTR the eh0 driver does do automatic interface selection. To solve this
get one of the NetBSD-current kernels which contain the ne0 based driver.
This does the interface sensing required. If there are no non-UVM current
kernels available drop me a line and I'll build one for you.

The other alternative is that you have not ifconfig'd the interface under
RISCOS before starting BSD. 

If it's neither of these then I have no idea what's going on.

Mike