I guess that's what you need:
00:0e.0 Ethernet controller: Bridgecom, Inc: Unknown device 0985 (rev 11)
        Subsystem: Bridgecom, Inc: Unknown device 0574

It's a Linksys EtherFast 10/100 LAN card (supposedly to have been "tested
with Linux")... and worked with the tulip driver not the old_tulip.
Thanks a lot.
Regards, 
Marcio

> Marcio Cordero <[EMAIL PROTECTED]> writes:
> 
> > Thanks for the advice Pixel.
> > I tried it with the newest network.img. But now, I get the message: no
> net
> > device found when trying to use my (DEC21xxx compatible) ethernet card.
> On the
> > terminal I get
> > ...have to insmod tulip
> > needs tulip
> > init_module:tulip:Device or resource busy
> > failed
> > warning, insmod failed (tulip(null))... even after chosig tulip by hand.
> 
> Some problems with tulip cards were fixed only in kernel-2.2.18.
> 
> Currently we use kernel-2.2.17 to boot the installer, are you sure that
> your network card should be supported?
> 
> Have you tried with options at insmod time?
> 
> Message "device or resource busy" seems to indicate that the kernel can't
> find your card, though.
> 
> 
> If the network.img worked for you only last week (with kernel-2.4 for
> installer) then that's probably the problem.
> 
> 
> > Maybe it's out of topic but I had the same problem while installing
> LM7.2:
> > during installation it wouldn't find the card, after the first login and
> using
> > Draknet, it found the net device (Linksys Etherfast10/100). Still, I had
> to
> > alias eth0 tulip and depmod -a/modprobe eth0 to get it to work.
> Essentially I
> > had to do all by hand except the dhcp thing. The last network.img I had
> used
> > (from 2001/01/16) found the card after I chose tulip.o from the
> selection
> > and I was happy to see the problem fixed. In the newest network.img
> however,
> > the problem "resurrected". Any clues?
> 
> Yep, probably kernel-2.4 found it and current 2.2 did not. Please wait for
> kernel-2.4 in installer and all should be smooth (one more week? some more
> days?).
> 
> In the meantime, in order for us to detect it automatically, can you tell
> me the PCI entry of your network card? It's the second value in the
> relevant line of your /proc/bus/pci/devices ; you may find which relevant
> line by printing "lspci -vv", the order of the devices is the same.
> 
> 
> 
> -- 
> Guillaume Cottenceau - http://us.mandrakesoft.com/~gc/
> 

-- 
Sent through GMX FreeMail - http://www.gmx.net

Reply via email to