one other question (hopefully!)

the card is detected fine now (after booting with GENERIC), however, my 
network provider only offers dhcp connections. I have edited rc.conf and 
added:

dhclient=YES
dhclient_flags="xi0" 

i have also created a dhclient.conf file that looks something like this:

timeout 60;
retry 60;
reboot 10;
select-timeout 5;
initial-interval 2;
interface "xi0" 

the problem is that on boot, the card is detected, it shows the ethernet 
address, dhcp starts but goes to fallback (which I have not set since I 
have to use dhcp) and then it attempts about 6 times to make dhcp contact 
before giving up and continuing with the boot. Before using dhclient, I 
tried to specify a static connection, but got an xi0 timeout straight away. 
After looking through the archives I tried to set the media as was 
suggested a while back but setting it to 100baseTX just killed the card, 
setting it to 10baseT brings it back again but it still timesout.

if anyone can help I will be MOST grateful - please bear in mind that I am 
a unix newbie and am googling my way through this so its quite possible 
that I may have missed something obvious!

thanks
steve

On Aug 5 2004, Miles Nordin wrote:

> >>>>> "sd" == S Dobson <sd20@york.ac.uk> writes:
> 
>     sd> in the /dev directory there are no network devices
> 
> There shouldn't be, but you should see the interface listed in
> 'ifconfig -a'.  If you don't, the card's driver isn't working right.
> This could be because the card isn't supported, because there's a bug
> in the driver, or because the driver isn't compiled into your kernel.
> 
> Often the GENERIC config files for non-i386 are out-of-sync
> accidentally or on purpose, and they don't include all the drivers, so
> if your card indeed doesn't show up in 'ifconfig -a' you should cross
> your fingers and hope that's the case.  Then post your boot output and
> tell us what kernel you're using.
> 
>     sd> Netbsd detects it but doesn't give it a device name (such as
>     sd> xi0 or eth0).
> 
> you should post the boot messages.  you can get them back with
> something like
> 
> $ dmesg | less
> 
> To get them into an email, maybe you can copy them onto a CF disk and
> then stick the disk into another laptop with network?
> 
>