[vortex] 3C905C-TX / 2.0.29

Donald Becker becker@scyld.com
Mon Apr 29 08:55:01 2002


On Sat, 27 Apr 2002 Jan.Ceuleers@alcatel.be wrote:

> Subject: [vortex] 3C905C-TX / 2.0.29
>
> I know, I know: I've got an ancient kernel.

That kernel should work fine.

> Nevertheless, I'm trying to get a second Ethernet card working. The
> first-one is a 3C509B and that's working fine. The second-one is a 3C905C
> and I can't get that to work.

What driver version are you using?
What is the detection message?

> ifconfig yields:
>
> eth1      Link encap:10Mbps Ethernet  HWaddr 00:02:1B:F3:02:13
>           inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
..
>           RX packets:13 errors:0 dropped:0 overruns:0
>           TX packets:17 errors:0 dropped:0 overruns:0

This looks fine.  You are sending and receiving packets with no errors.
Check your routing table.

> This is what's in dmesg:
>
> pci-scan: Handling APM event 11 for driver list vortex...

You are getting a lot of APM_STANDBY_RESUME events.  From your
description I expected a PCI card in a desktop machine, not a laptop
with frequent power management events. This is mostly harmless, but
unexpected.

> eth1: Media selection timer tick happened, Autonegotiate.
> eth1: MII transceiver has status 782d.

Normal

> eth1: interrupt, status e401, latency 4 ticks.
> eth1: In interrupt loop, status e401.
>   In boomerang_rx(), status e001, rx_status 000a.

You received a packet with no error.

> eth1: Queuing Tx packet, index 14.
> eth1: interrupt, status e201, latency 2 ticks.

And transmitted one.

-- 
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