*BSD News Article 66668


Return to BSD News archive

Newsgroups: comp.unix.bsd.bsdi.misc
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!qns3.qns.com!imci4!newsfeed.internetmci.com!howland.reston.ans.net!EU.net!sun4nl!geertj
From: geertj@solair1.inter.NL.net (Geert Jan de Groot)
Subject: Re: BSDI can't recognize NE2000 Ethernet card
Message-ID: <Dq8Ky0.2Io@solair1.inter.NL.net>
Organization: NLnet
X-Newsreader: NN version 6.5.0 #2 (NOV)
References: <Pine.SOL.3.91.960418174556.15974B-100000@alcor.usc.edu>
Date: Sun, 21 Apr 1996 23:51:35 GMT
Lines: 43

Wee-San Lee <wlee@alcor.usc.edu> writes:

>On Fri, 19 Apr 1996, Geert Jan de Groot wrote:
>	Well, my problem was that when I boot from BSDI installation 
>disk, my REAL NE2000 Ethernet card can't be recognized.  Instead, pe0 and 
>xir0 are shown on screen.  I was told by techical support that the port #
>of NE2000 has to be set to 0x320 but I found no switch or jumper on the 
>card.  I even rebuilt the kernel and turned off pe0 and xir0.  I ended 
>up having nothing.

If your card does not have jumpers, then it is not an NE2000; it may
be an NE2000 clone however, but it is *not* the 'real thing'
In that case, the card should have come with a floppy to set the
port number and such. If the floppy is missing, complain to your 
ethernet card vendor.

If you happen to know to what address your NE2000 clone was set, you
may try to get it to work by tapping spacebar during the 'boot:'
countdown, entering -dev ne0 port=0x<portnumber>, and entering return twice.
If this works, add this line to /etc/default.boot.
Oh, and you should still complain to your ethernet card vendor
because your card was shipped incomplete.

pe0 and xir0 are completely irrelevant to your problem. These are 
'printerport ethernet-adapters', and they always probe if your machine
has a printer port (the actual test if the card is there is donw when
you try to ifconfig the interface).

>	I was trying to 'mknod' a ne device by myself and consulted the 
>major and minor number of ne device from technical support.  However, I 
>was told that it doesn't work out.  Maybe one of you could give me the 
>numbers so that I could have a try, at least!

Wrong again. An ethernet device does *not* have a device node, so
this will never work this way.

I suggest that you get in touch with more experienced UNIX system 
administrators at your university. Having local help will probably
be much more efficient and make chances much higher that you'll
get this to work.

Geert Jan