[ Next-in-Thread ]  [ Next Message ] 

Question: Intel EtherExpress PRO/100 Cardbus 32 

Forum: PCMCIA Network Adapter Issues
Date: 1999, Nov 17
From: Mike Rudgyard MikeR 

Hi,

I am trying to get the above card working on my Dell Latitude machine with the latest tulip driver and pcmcia-cs-3.1.4.

According to the supported cards, this should work. Indeed the
network comes up, and the light on the card comes on:

Nov 17 14:28:51 rock kernel: cs: cb_alloc(bus 35): vendor 0x1011, device 0x0019
Nov 17 14:28:51 rock cardmgr[360]: initializing socket 1
Nov 17 14:28:51 rock cardmgr[360]: socket 1: Intel EtherExpress PRO/100 CardBus Mobile Adapter32
Nov 17 14:28:51 rock cardmgr[360]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/cb_enabler.o'
Nov 17 14:28:51 rock cardmgr[360]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/tulip_cb.o'
Nov 17 14:28:51 rock kernel: cs: cb_config(bus 35)
Nov 17 14:28:51 rock kernel:   fn 0 bar 1: io 0x100-0x17f
Nov 17 14:28:51 rock kernel:   fn 0 bar 2: mem 0x60081000-0x6008107f
Nov 17 14:28:51 rock kernel:   fn 0 rom: mem 0x60041000-0x60080fff
Nov 17 14:28:51 rock kernel: tulip_attach(bus 35, function 0)
Nov 17 14:28:51 rock kernel: tulip.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
Nov 17 14:28:51 rock kernel: eth0: Digital DS21143 Tulip rev 48 at 0x100, EEPROM not present, 00:4C:69:6E:75:79, IRQ 3.
Nov 17 14:28:51 rock cardmgr[360]: executing: './network start eth0'
Nov 17 14:28:52 rock modprobe: can't locate module block-major-22




As it points out, there is no EEPROM present in the card, which I presume is why I can't actually send or receive any
packets. If I use the tulip-diag tool, doing tulip-diag -ee
then I get:

ulip-diag.c:v1.19 10/2/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a Digital DS21143 Tulip adapter at 0x60081000.
 Port selection is 100mbps-SYM/PCS 100baseTx scrambler, full-duplex.
 Transmit started, Receive started, full-duplex.
  The Rx process state is 'Transferring Rx frame into memory'.
  The Tx process state is 'Closing Tx descriptor'.
  PCI bus error!: Unknown 7.
  The transmit unit is set to store-and-forward.
 Interrupt sources are pending!  CSR5 is ffffffff.
   Tx done indication.
   Tx complete indication.
   Tx out of buffers indication.
   Transmit Jabber indication.
   Link passed indication.
   Tx FIFO Underflow indication.
   Rx Done indication.
   Receiver out of buffers indication.
   Receiver stopped indication.
   Receiver jabber indication.
   Link changed indication.
   Timer expired indication.
   Link failed indication.
   PCI bus error indication.
   Early Rx indication.
  The NWay status register is ffffffff.
EEPROM size is 8.
WARNING: The EEPROM is missing or erased!
 This interface is missing the EEPROM.
  This is likely the non-primary interface on a multiport board.
EEPROM contents:
  ffff ffff ffff ffff ffff ffff ffff ffff
  ffff ffff ffff ffff ffff ffff ffff ffff
  ffff ffff ffff ffff ffff ffff ffff ffff
  ffff ffff ffff ffff ffff ffff ffff ffff
  ffff ffff ffff ffff ffff ffff ffff ffff
  ffff ffff ffff ffff ffff ffff ffff ffff
  ffff ffff ffff ffff ffff ffff ffff ffff
  ffff ffff ffff ffff ffff ffff ffff ffff
 ID block CRC 0xfa (vs. 0xff).
  Full contents CRC 0x6a15 (read as 0xffff).
  Internal autonegotiation state is 'Invalid state'.


Unfortunately, I can't find any details of how to program the 
EEPROM (although I can see that the above program can be used to do this...).

Has anyone any ideas ??

Thanks,

Mike

[ Next-in-Thread ]  [ Next Message ] 

Messages Inline: [ 0 ]  [ 1 ] 

The EEPROM isn't the problem

Re: Question: Intel EtherExpress PRO/100 Cardbus 32 (Mike Rudgyard)
Date: 1999, Nov 17
From: David Hinds <dhinds@pcmcia.sourceforge.org> 

The EEPROM is not the problem: the driver isn't talking to the card at
all.  Everything is reading back as ff's.  The EEPROM message is just
one of several complaints.

I think I'd first want to see the PCMCIA messages preceeding this
(they say what kind of CardBus bridge this is, what kernel version and
PCMCIA driver version you're using, etc).

-- Dave

Question: More info...

Re: Question: Intel EtherExpress PRO/100 Cardbus 32 (Mike Rudgyard)
Date: 1999, Nov 18
From: Mike Rudgyard MikeR

Red Hat 6.1 Kernel 2.2.12 tulip.c:v0.91g 7/16/99 pcmcia-cs-3.1.4

Here's what I get in /var/log/messages again: 

Nov 18 10:52:43 rock last message repeated 19 times
Nov 18 10:52:44 rock cardmgr[360]: initializing socket 1
Nov 18 10:52:44 rock cardmgr[360]: socket 1: Intel EtherExpress PRO/100 CardBus Mobile Adapter32
Nov 18 10:52:44 rock kernel: cs: cb_alloc(bus 35): vendor 0x1011, device 0x0019
Nov 18 10:52:44 rock cardmgr[360]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/cb_enabler.o'
Nov 18 10:52:44 rock cardmgr[360]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/tulip_cb.o'
Nov 18 10:52:44 rock kernel: cs: cb_config(bus 35)
Nov 18 10:52:44 rock kernel:   fn 0 bar 1: io 0x100-0x17f
Nov 18 10:52:44 rock kernel:   fn 0 bar 2: mem 0x60081000-0x6008107f
Nov 18 10:52:44 rock kernel:   fn 0 rom: mem 0x60041000-0x60080fff
Nov 18 10:52:44 rock kernel: tulip_attach(bus 35, function 0)
Nov 18 10:52:44 rock kernel: tulip.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
Nov 18 10:52:44 rock kernel: eth0: Digital DS21143 Tulip rev 48 at 0x100, EEPROM not present, 00:4C:69:6E:75:79, IRQ 3.
Nov 18 10:52:44 rock cardmgr[360]: executing: './network start eth0'
Nov 18 10:52:45 rock modprobe: can't locate module block-major-22

Here's what I get with another 3COM card (that works fine...): 

Nov 18 10:52:17 rock last message repeated 53 times
Nov 18 10:52:18 rock cardmgr[360]: initializing socket 1
Nov 18 10:52:18 rock cardmgr[360]: socket 1: 3Com 3CCFE575B/3CXFE575B Fast EtherLink XL
Nov 18 10:52:18 rock kernel: cs: cb_alloc(bus 35): vendor 0x10b7, device 0x5157
Nov 18 10:52:18 rock cardmgr[360]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/cb_enabler.o'
Nov 18 10:52:18 rock cardmgr[360]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/3c575_cb.o'
Nov 18 10:52:18 rock kernel: 3c59x.c:v0.99L 5/28/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
Nov 18 10:52:18 rock kernel: cs: cb_config(bus 35)
Nov 18 10:52:18 rock kernel:   fn 0 bar 1: io 0x100-0x17f
Nov 18 10:52:18 rock kernel:   fn 0 bar 2: mem 0x60021000-0x6002107f
Nov 18 10:52:18 rock kernel:   fn 0 bar 3: mem 0x60020000-0x6002007f
Nov 18 10:52:18 rock kernel:   fn 0 rom: mem 0x60000000-0x6001ffff
Nov 18 10:52:18 rock kernel: vortex_attach(bus 35, function 0, device 5157)
Nov 18 10:52:18 rock kernel: eth0: 3Com 3CCFE575 Cyclone CardBus at 0x100,  00:50:04:5b:b0:b9, IRQ 3
Nov 18 10:52:18 rock kernel: eth0: CardBus functions mapped 60020000->c8073000
Nov 18 10:52:18 rock kernel:   8K byte-wide RAM 5:3 Rx:Tx split, MII interface.
Nov 18 10:52:18 rock kernel:   MII transceiver found at address 0, status 7809.
Nov 18 10:52:18 rock kernel:   Enabling bus-master transmits and whole-frame receives.
Nov 18 10:52:18 rock cardmgr[360]: executing: './network start eth0'
Nov 18 10:52:18 rock modprobe: can't locate module block-major-22
Nov 18 10:52:21 rock last message repeated 5 times
Nov 18 10:52:21 rock kernel: eth0: Setting full-duplex based on MII #0 link partner capability of 41e1.
Nov 18 10:52:22 rock modprobe: can't locate module block-major-22

Here's what tulip-diag gives: 

[root@rock incoming]# tulip-diag
tulip-diag.c:v1.19 10/2/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a Digital DS21143 Tulip adapter at 0x60081000.
 Port selection is 100mbps-SYM/PCS 100baseTx scrambler, full-duplex.
 Transmit started, Receive started, full-duplex.
  The Rx process state is 'Transferring Rx frame into memory'.
  The Tx process state is 'Closing Tx descriptor'.
  PCI bus error!: Unknown 7.
  The transmit unit is set to store-and-forward.
 Interrupt sources are pending!  CSR5 is ffffffff.
   Tx done indication.
   Tx complete indication.
   Tx out of buffers indication.
   Transmit Jabber indication.
   Link passed indication.
   Tx FIFO Underflow indication.
   Rx Done indication.
   Receiver out of buffers indication.
   Receiver stopped indication.
   Receiver jabber indication.
   Link changed indication.
   Timer expired indication.
   Link failed indication.
   PCI bus error indication.
   Early Rx indication.
  The NWay status register is ffffffff.
WARNING: The EEPROM is missing or erased!
  Internal autonegotiation state is 'Invalid state'.
 Use '-a' or '-aa' to show device registers,
     '-e' to show EEPROM contents, -ee for parsed contents,
  or '-m' or '-mm' to show MII management registers.

Since it tells me there is a PCI bus error, here's some info on the PCI devices on Dell Latitude CPi (with the EtherExpress card in....) 

PCI devices found:
  Bus 35, device   0, function  0:
    Ethernet controller: DEC DC21142 (rev 48).
      Medium devsel.  Fast back-to-back capable.  IRQ 3.
      Non-prefetchable 32 bit memory at 0x100 [0x100].
      Non-prefetchable 32 bit memory at 0x60081000 [0x60081000].
  Bus  0, device   0, function  0:
    Host bridge: Intel 440BX - 82443BX Host (no AGP) (rev 2).
      Medium devsel.  Master Capable.  Latency=32.
      Prefetchable 32 bit memory at 0xd0000000 [0xd0000008].
  Bus  0, device   2, function  0:
    VGA compatible controller: Neomagic MagicGraph NM2160 (rev 1).
      Medium devsel.  Fast back-to-back capable.  IRQ 11.  Master Capable.  Latency=32.  Min Gnt=16.Max Lat=255.
      Prefetchable 32 bit memory at 0xe1000000 [0xe1000008].
      Non-prefetchable 32 bit memory at 0xfde00000 [0xfde00000].
      Non-prefetchable 32 bit memory at 0xfdd00000 [0xfdd00000].
  Bus  0, device   3, function  0:
    CardBus bridge: Texas Instruments PCI1131 (rev 1).
      Medium devsel.  IRQ 11.  Master Capable.  Latency=32.  Min Gnt=192.Max Lat=7.
  Bus  0, device   3, function  1:
    CardBus bridge: Texas Instruments PCI1131 (rev 1).
      Medium devsel.  IRQ 11.  Master Capable.  Latency=32.  Min Gnt=128.Max Lat=7.
  Bus  0, device   7, function  0:
    Bridge: Intel 82371AB PIIX4 ISA (rev 1).
      Medium devsel.  Fast back-to-back capable.  Master Capable.  No bursts.
  Bus  0, device   7, function  1:
    IDE interface: Intel 82371AB PIIX4 IDE (rev 1).
      Medium devsel.  Fast back-to-back capable.  Master Capable.  Latency=32.
      I/O at 0x860 [0x861].
  Bus  0, device   7, function  2:
    USB Controller: Intel 82371AB PIIX4 USB (rev 1).
      Medium devsel.  Fast back-to-back capable.  IRQ 11.  Master Capable.  Latency=32.
      I/O at 0xece0 [0xece1].
  Bus  0, device   7, function  3:
    Bridge: Intel 82371AB PIIX4 ACPI (rev 1).
      Medium devsel.  Fast back-to-back capable.

I'd be happy to send you any other info that could help.

Cheers,

Mike

Something to try...

Re: Question: More info... (Mike Rudgyard)
Date: 1999, Dec 30
From: David Hinds <dhinds@pcmcia.sourceforge.org> 

Try getting the latest version of tulip-diag from Donald Becker's web
site, then use it to write the EEPROM on the card, and see if that
helps.

-- Dave

Ok: Success !!

Re: Something to try... (David Hinds)
Date: 2000, Jan 10
From: Mike Rudgyard MikeR

Tried your suggestion (and updated to pcmcia3.18 and the latest version of tulip.c).....

... and it seems to work fine !!!

I'll let you know if I have any problems in the coming weeks.

Thanks for the help !

Mike

Question: I'd like your success

Re: Ok: Success !! (Mike Rudgyard)
Date: 2000, Feb 17
From: Kurt Atkinson kjwa

Dear Mike,

I seem to be having a similar problem with the same card. I'm using a generic make laptop with an O2Micro bridge. Could you possibly give some more details of how you solved your problem so I can have a go also? I've read the preceeding messages but am a little lost. Any help will be much appreciated.

kURT <<()>>

Sad: Same thing happens with Intel PRO/100 LAN+Modem56 CardBus II card

Re: Question: Intel EtherExpress PRO/100 Cardbus 32 (Mike Rudgyard)
Date: 1999, Dec 07
From: Wayne Scott wscott

I just got a Intel Pro/100 LAN+Modem combo card and it has the exact same symptoms. Any help would be appreciated.

My logs look just like the other guys, but I also get these messages: 

  eth0: Tx hung, 13 vs. 0.
  eth0: 21140 transmit timed out, status ffffffff, SIA ffffff.... (all 'f's)

Let me know if I can send anything to help debug.

-Wayne

It's the chipset

Re: Sad: Same thing happens with Intel PRO/100 LAN+Modem56 CardBus II card (Wayne Scott)
Date: 2000, Apr 22
From: John Kilpatrick <john@hypergeek.net>

The whole problem with that card is that it is based on the Intel i82559 chipset. The only similarity it has to the Xircom is the shape. :-)

There is a patch out there (David was kind enough to send it to me) but I can't seem to get it compiled. Still working on it.

Intel EtherExpress PRO/100 Cardbus 32

[ Add Message ]  to: "Intel EtherExpress PRO/100 Cardbus 32"

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