[tulip-bug] I cannot get tulip to load my card up, even though it was compiled fine...

[Donald Becker]

On Sun, 22 Apr 2001, Matt T wrote:

> > > On bootup it gives me the message: initializing interface eth0:
> > > delaying initialization :::failed:::
> >
> > What type of card?
> > What does 'lspci' or /proc/pci report about the chip type?
> > What driver version?
> > What the message when you tried to load the driver?  (Use 'dmesg'.)
> 
> ?It is linksys card ( N100 v 2 I think is some extra info about
> it... )

That's likely a ADMtek Comet card.

> ?are lspci and /proc/pci programs?  I got no output by them... it couldn't
> even find them.  I took a look for /proc/pci and I found it.  There was
> nothing written in them.

lspci is a program.
/proc/pci is a pseudo-file that has no contents until you view it.
Run them as
  /sbin/lspci
  cat /proc/pci

> ?Umm... It is the newest one form scyld.net ( I got it about 3 weeks ago ).
> I don't know the exact numbers...

The exact version number is important.

> ?Well, there wasn't anything in the output of dmesg that had anything to do
> with tulip, eth0, network or anything like that... ( I ran `dmesg | grep
> WORD` where word is the word tulip, eth0, net, pci, and such ).

That means you don't have the tulip module configured.  Even if the
driver doesn't find a card, it still reports the version number.

Donald Becker				becker@scyld.com
Scyld Computing Corporation		http://www.scyld.com
410 Severn Ave. Suite 210		Second Generation Beowulf Clusters
Annapolis MD 21403			410-990-9993