[tulip-bug] SMC1255TX/LP Problem - TX errors and Carrier errors X2
Denny Fox
dennyf@mninter.net
Tue Aug 20 17:22:01 2002
Hello,
I am running Debian 2.2 (potato, up to date) with a 2.2.19 locally
compiled kernel. I'm getting errors when using an SMC1255TX/LP nic
card for eth0 in a VIA EPIA Mini-ITX motherboard. I've searched
through the tulip-bug archives for this year and haven't found any
answer.
Two other brand nic cards with Realtek 8139 chips on them work
correctly and report correctly (no errors) in this system.
Here is output from ifconfig for the SMC1255TX/LP...
eth0 Link encap:Ethernet HWaddr 00:04:E2:42:D4:72
inet addr:192.168.20.254 Bcast:192.168.20.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:38 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:51 dropped:0 overruns:0 carrier:102
collisions:0 txqueuelen:100
Interrupt:11 Base address:0x8000
The TX packet count is 0. For each TX packet there is logged a TX
error, and 2 TX carrier errors.
The odd thing is, the card seems to operate at the application level
OK. Pings and other network traffic seem to be going as expected. The
throughput for a 1mbyte file transfer was measured at 679 kB/sec
transmit and 765 kB/sec receive.
The card is connected to a 10BT hub. I do not get any difference in
symptoms whether it is set to auto-negotiate, or fix it to 10BT/Half
DUples with mii-diag.
SMC supplied a patched version of tulip.c:v0.91g 7/16/99 with a
section added for the card:
{ "SMC EZ Card 10/100 (SMC1255TX)",
0x1113, 0x1216, 0xffff, PCI_ADDR0_IO, 256, 32, tulip_probe1 },
I have compiled this both as a module, and directly into the kernel
and get the same results.
I downloaded the latest tulip driver tulip.c:v0.95 6/21/2002 and
compiled it as a module and got the same results. I then added
{ "SMC EZ Card 10/100 (SMC1255TX)", { 0x12161113,
0xffffffff },
TULIP_IOTYPE, TULIP_SIZE1, COMET },
just above
{ "ADMtek AN981 Comet", { 0x09811317, 0xffffffff },
TULIP_IOTYPE, TULIP_SIZE1, COMET },
to see if that would help. The boot process now shows the SMC id, but
the symptom remains the same.
Is this a reporting error, or is there something wrong? It would be
nice if the SMC card reports correctly using ifconfig.
Thanks in advance for any help, other backround information is shown
below...
Denny Fox
-------------
dmesg output
tulip.c:v0.95 6/21/2002 Written by Donald Becker <becker@scyld.com>
http://www.scyld.com/network/tulip.html
eth0: SMC EZ Card 10/100 (SMC1255TX) rev 17 at 0xc3818000,
00:04:E2:42:D4:72, IRQ 11.
eth0: MII transceiver #1 config 0000 status 784d advertising 05e1.
eth0: MII transceiver #2 config 1000 status 7849 advertising 05e1.
eth0: MII transceiver #3 config 1000 status 7849 advertising 05e1.
eth0: MII transceiver #4 config 1000 status 7849 advertising 05e1.
/proc/pci
Bus 0, device 20, function 0:
Ethernet controller: SMC Unknown device (rev 17).
Vendor id=1113. Device id=1216.
Medium devsel. Fast back-to-back capable. IRQ 11. Master
Capable. Latency=32. Min Gnt=255.Max Lat=255.
I/O at 0xec00 [0xec01].
Non-prefetchable 32 bit memory at 0xe4000000 [0xe4000000].
/etc/network/interfaces
iface eth0 inet static
address 192.168.20.254
netmask 255.255.255.0
network 192.168.20.0
broadcast 192.168.20.255
up /usr/local/bin/mii-diag -F 10baseT-HD eth0
mii-diag eth0
Basic registers of MII PHY #1: 0000 784d 001d 2411 05e1 0021 0004
2001.
Basic mode control register 0x0000: Auto-negotiation disabled, with
Speed fixed at 10 mbps, half-duplex.
You have link beat, and everything is working OK.
Your link partner is generating 10baseT link beat (no
autonegotiation).
End of basic transceiver information.
tulip-diag -aem (after ifdown eth0)
tulip-diag.c:v2.13 8/6/2002 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a Accton EN1217/EN2242 (ADMtek Comet) adapter at
0xec00.
Accton EN1217/EN2242 (ADMtek Comet) chip registers at 0xec00:
0x00: fff98000 ffffffff ffffffff 00251810 00251a10 fc06c012 ffb70111
fffe5410
0x40: fffe0000 fff597f8 00000000 fffe0000 00000000 00000200 00000000
00000008
Extended registers:
0x80: 0006c812 03fe5410 a4dc0004 ffffffff 00000100 00251a30 002518f0
ffe0f000
0xa0: 70000000 42e20400 ffff72d4 80000000 00000000 00000000 00000000
00000000
0xc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
0xe0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000
30000027
Comet duplex is reported in the MII status registers.
Transmit stopped, Receive stopped.
The Rx process state is 'Waiting for packets'.
The Tx process state is 'Stopped'.
The transmit unit is set to store-and-forward.
Interrupt sources are pending! CSR5 is fc06c812.
Tx complete indication.
Link passed indication.
Timer expired indication.
Early Rx indication.
Comet MAC address registers 42e20400 ffff72d4
Comet multicast filter 8000000000000000.
EEPROM 64 words, 6 address bits.
Ethernet MAC Station Address 00:04:e2:42:d4:72.
Default connection type 'Autosense'.
PCI IDs Vendor 1113 Device 1216 Subsystem 10b8 1255
PCI min_grant 255 max_latency 255.
CSR18 power-up setting 0xa4dc****.
MII PHY found at address 1, status 0x784d.
MII PHY found at address 2, status 0x784d.
MII PHY found at address 3, status 0x784d.
MII PHY found at address 4, status 0x784d.
MII PHY #1 transceiver registers:
0000 784d 001d 2411 05e1 0021 0004 2001
0000 0000 0000 0000 0000 0000 0000 0000
1001 0000 2033 205f 0000 000f 7490 0000
8111 6946 2c58 1326 8911 0444 0230 0000.
MII PHY #2 transceiver registers:
0000 784d 001d 2411 05e1 0021 0004 2001
0000 0000 0000 0000 0000 0000 0000 0000
1001 0000 0033 205f 0000 000f 7490 0000
8111 6946 2c58 1326 8911 0444 0230 0000.
MII PHY #3 transceiver registers:
0000 784d 001d 2411 05e1 0021 0004 2001
0000 0000 0000 0000 0000 0000 0000 0000
1001 0000 0033 205f 0000 000f 7490 0000
8111 6946 2c58 1326 8911 0444 0230 0000.
MII PHY #4 transceiver registers:
0000 784d 001d 2411 05e1 0021 0004 2001
0000 0000 0000 0000 0000 0000 0000 0000
1001 0000 0033 205f 0000 000f 7490 0000
8111 6946 2c58 1326 8911 0444 0230 0000.
----------
EOF