Subject: Re: Getting networking working
To: Mike Pumford <mpumford@mpc-data.co.uk>
From: Roger Lynn <roger@compsoc.man.ac.uk>
List: port-arm32
Date: 06/05/1998 00:23:29
> Well it's fairly straightforward. You need to set up a file called
> /etc/ifconfig.eh0 which contains something like the following:
> 
> inet 192.168.1.2
> 
> You should replace 192.168.1.2 with the IP address that you want for the
> machine. It should be noted that this assumes the old EtherH driver. If you
> download one of the newer kernels the EtherH interface name has changed to
> ne0  since it it now supported using the generic NetBSD ne2000 driver. In this
> case you the file you need to create should be called /etc/ifconfig.ne0.
> 
> One other thing to note is that both of the EtherH drivers required that the
> card has been configured for use under RISC OS before they will work
> correctly. As the author of the updated EtherH driver and having found some
> free time again I'm in the process of tracking this down.

I think the basic problem is that we don't appear to have any ethernet
devices in /dev. The installation instructions say that support for all
ethernet cards is compiled in. I tried compiling my own kernel using the
1.3 sources, but got an error in disassem.c, which apparently has been
fixed in 1.3.2. However the supplied 1.3.2 (and 1.3.1) kernel binaries
hang immediately after changing mode after displaying all the coloured
bars. I haven't tried compiling the 1.3.2 sources yet.

The output from ifconf -l gives:

lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 32976
        inet 127.0.0.1 netmask 0xff000000
sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 296
sl1: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 296
ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
ppp1: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
tun0: flags=10<POINTOPOINT> mtu 1500
tun1: flags=10<POINTOPOINT> mtu 1500

none of which look like ethernet interfaces to me. Browsing through /dev
is no more helpful.

Where do I get an ethernet device from? All the advice I have received
so far appears to assume that we have an eh0 or ne0 device.
When booting up the kernel says it is configuring the network interfaces:.
It then says that the network is unreachable.

Does using the port under RISC OS immediately before booting 'BSD imply
that it's probably correctly configured?

On another point, I've had a couple of kernel panics. Other than
rebooting, is there anything else I should do when this occurs? Is
anyone interested in seeing logs or anything? (not that I've kept any
yet.)

Thanks for the help,

Roger