Next-in-Thread Next Message

Angry Intel EtherExpress PRO/100 Mobile, model MBLA3200 

Forum: PCMCIA Network Adapter Issues
Date: 2000, Apr 09
From: Jim Perry aziwoqpd

Heya... I was trying to get Linux installed on my laptop
today, and I couldn't get the bloody PCMCIA ethernet driver
to work.  I tried shoving it onto different IRQs and different
ports, but I kept getting the same error.  Anyway, I'm using Linux-2.2.13, the latest pcmcia (pcmcia-cs-3.1.13 i think?).
Here's the logs:

Apr  9 15:57:35 slackware kernel: Linux PCMCIA Card Services 3.1.13 
Apr  9 15:57:35 slackware kernel:   kernel build: 2.2.13 #1 SMP Sun Apr 9 14:10:46 PDT 2000 
Apr  9 15:57:35 slackware kernel:   options:  [pci] [cardbus] [pnp] 
Apr  9 15:57:35 slackware kernel: PCI routing table version 1.0 at 0xf6980 
Apr  9 15:57:35 slackware kernel: PnP: PNP BIOS installation structure at 0xc00fdab0 
Apr  9 15:57:35 slackware kernel: PnP: PNP BIOS version 1.0, entry at f0000:4b88, dseg at f0000 
Apr  9 15:57:46 slackware kernel: Intel PCIC probe:  
Apr  9 15:57:46 slackware kernel:   Ricoh RL5C465 PCI-to-CardBus at slot 00:13, mem 0xfedff000 
Apr  9 15:57:46 slackware kernel:     host opts [0]: [io 4/6/2] [mem 4/6/2] [pci irq 9] [lat 64/176] [bus 1/1] 
Apr  9 15:57:46 slackware kernel:     PCI irq 9 test failed 
Apr  9 15:57:46 slackware kernel:     ISA irqs (default) = 10,11,15 polling interval = 1000 ms 
Apr  9 15:57:56 slackware cardmgr[255]: starting, version is 3.1.13
Apr  9 15:57:56 slackware kernel: cs: IO port probe 0x1000-0x17ff: clean. 
Apr  9 15:57:56 slackware cardmgr[255]: watching 1 sockets
Apr  9 15:58:05 slackware kernel: cs: cb_alloc(bus 1): vendor 0x1011, device 0x0019 
Apr  9 15:58:05 slackware kernel: ROM image dump: 
Apr  9 15:58:05 slackware kernel:   image 0: 0x000000-0x0001ff, signature PCIR 
Apr  9 15:58:05 slackware kernel: cs: cb_config(bus 1) 
Apr  9 15:58:05 slackware kernel:   fn 0 bar 1: io 0x1000-0x107f 
Apr  9 15:58:05 slackware kernel:   fn 0 bar 2: mem 0x600c0000-0x600c007f 
Apr  9 15:58:05 slackware kernel:   fn 0 rom: mem 0x60080000-0x600bffff 
Apr  9 15:58:05 slackware kernel: cs: cb_enable(bus 1) 
Apr  9 15:58:05 slackware kernel:   bridge io map 0 (flags 0x21): 0x1000-0x107f 
Apr  9 15:58:05 slackware kernel:   bridge mem map 0 (flags 0x1): 0x60080000-0x600c0fff 
Apr  9 15:58:05 slackware kernel: tulip_reap() 
Apr  9 15:58:05 slackware kernel: tulip_attach(bus 1, function 0) 
Apr  9 15:58:05 slackware kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford) 
Apr  9 15:58:05 slackware kernel: eth0: Digital DS21143 Tulip rev 48 at 0x1000, EEPROM not present, 00:4C:69:6E:75:79, IRQ 11. 
Apr  9 15:58:05 slackware cardmgr[255]: initializing socket 0
Apr  9 15:58:05 slackware cardmgr[255]: socket 0: Intel EtherExpress PRO/100 CardBus Mobile Adapter32
Apr  9 15:58:05 slackware cardmgr[255]: executing: 'insmod /lib/modules/2.2.13/pcmcia/cb_enabler.o'
Apr  9 15:58:05 slackware cardmgr[255]: executing: 'insmod /lib/modules/2.2.13/pcmcia/tulip_cb.o'
Apr  9 15:58:05 slackware cardmgr[255]: executing: './network start eth0'
Apr  9 15:58:50 slackware kernel: eth0: Tx hung, 9 vs. 0. 
Apr  9 15:58:50 slackware kernel: eth0: 21140 transmit timed out, status f0678006, SIA 000000c6 ffff0001 fffbff7f 8ff04008, resetting... 
Apr  9 15:58:56 slackware kernel: eth0: Tx hung, 9 vs. 0. 
Apr  9 15:58:56 slackware kernel: eth0: 21140 transmit timed out, status f0678106, SIA 000000c6 ffff0000 fffbff7f 8ff04008, resetting... 
Apr  9 15:59:02 slackware kernel: eth0: Tx hung, 9 vs. 0. 
Apr  9 15:59:02 slackware kernel: eth0: 21140 transmit timed out, status f0678106, SIA 000000c6 ffff0000 fffbff7f 8ff04008, resetting... 
Apr  9 15:59:08 slackware kernel: eth0: Tx hung, 9 vs. 0. 
Apr  9 15:59:08 slackware kernel: eth0: 21140 transmit timed out, status f0678106, SIA 000000c6 ffff0000 fffbff7f 8ff04008, resetting... 
Apr  9 15:59:14 slackware kernel: eth0: Tx hung, 9 vs. 0. 
Apr  9 15:59:14 slackware kernel: eth0: 21140 transmit timed out, status f0678106, SIA 000000c6 ffff0000 fffbff7f 8ff04008, resetting... 
(i get mad and take the card out)
Apr  9 15:59:15 slackware kernel: tulip_detach(eth0) 
Apr  9 15:59:15 slackware kernel: cs: cb_disable(bus 1) 
Apr  9 15:59:15 slackware kernel: cs: cb_release(bus 1) 
Apr  9 15:59:15 slackware kernel: cs: cb_free(bus 1) 
Apr  9 15:59:15 slackware kernel: tulip_reap() 
Apr  9 15:59:15 slackware cardmgr[255]: shutting down socket 0

Also, I tried running tulip-diag while it was sitting there 
printing out those "hung" statements.  This is what I got:
tulip-diag.c:v1.19 10/2/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a Digital DS21143 Tulip adapter at 0x1000.
 Port selection is 10mpbs-serial, full-duplex.
 Transmit stopped, Receive stopped, full-duplex.
  The Rx process state is 'Stopped'.
  The Tx process state is 'Stopped'.
  The transmit threshold is 72.
 Interrupt sources are pending!  CSR5 is f0018106.
   Tx complete indication.
   Tx out of buffers indication.
   Receiver stopped indication.
  The NWay status register is 000000c6.
EEPROM size is 6.
 A simplifed EEPROM data table was found.
 The EEPROM does not contain transceiver control information.
EEPROM contents:
  8086 0001 0087 0000 0000 0000 0000 0000
  00c4 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 4448
 ID block CRC 0xc4 (vs. 0xc4).
  Full contents CRC 0x4448 (read as 0x4448).
You have an Intel CardBus card with an incomplete EEPROM.
The station address is 00:a0:c9:7a:d8:a5
New EEPROM contents would be:
  8086 0001 0087 0000 0000 0000 0000 0000
  00c4 0103 a000 7ac9 a5d8 1e00 0000 0800
  8604 0002 08af 00a5 0286 af04 a508 8800
  0304 08af 00a5 8061 0488 af05 a508 6100
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 4448
 ID CRC 0xc4 (vs. 0xc4), complete CRC 4448.
  Internal autonegotiation state is 'Autonegotiation disabled'.

Any ideas?  I heard something about reflashing the EEPROM,
but I didn't do that for two reasons.. Mainly, it sounds
dangerous, and the more important, I don't know how.
Oh, and incidentially, I'm on a 100baseT network, not a
10baseT network.  Tried doing an "ifport eth0 100baseT", but
I just got an ioctl not allowed error.  "ifport eth0" by itself claims
that the adapter is on "auto" mode.

Thanks,
-jim

Next-in-Thread Next Message

Select this message: Intel EtherExpress PRO/100 Mobile, model MBLA3200

Messages Inline: 1 All Outline: 1 2 All

1. Ok EtherExpress fixed! by Jim Perry, 2000, Apr 15
(_ Agree That fixes my card too. But the EEPROM rewrite seems essential. by Kurt Atkinson, 2000, May 24

Message Administration

This form allows you to delete, move, or copy one or more messages. You can move messages by copying and deleting the original. The action will be applied to the messages you select above and all replies to those selected messages.


If you want to copy or move messages, specify the HyperNews path of a destination forum or message that all messages will be copied or moved to. The destination must already exist, so maybe create it first.

Path of Destination (a Forum or Message): (e.g. "test")

Notify Subscribers at destination
NO


If you want to delete messages (the default), specify that here. If you want to move messages, you need to delete the original messages; placeholders will be left pointing to where they were moved.

Delete Messages
NO


Caution: After deleteing messages (the default), if you have not copied them (i.e. no destination above), then the selected messages are not be recoverable.

Members Subscribe No Admin Mode Show Frames Help for HyperNews at pcmcia-cs.sourceforge.net 1.10
[ Edit This Forum ]