Next-in-Thread Next Message

Question Using regular kernel tulip driver with pcmcia-cs 

Forum: PCMCIA Network Adapter Issues
Date: 2000, Mar 31
From: RichardA

Hello,

I'm trying to get my SMC CardBus card, which uses a DEC "tulip" chip, to work on my laptop.

I have already tried pcmcia-cs 3.1.13 with the 2.3.99-pre2 kernel and the tulip 0.91g-ppc driver from pcmcia-cs, i.e. the standalone PCMCIA support, for which I disabled PCMCIA in the kernel. Unfortunately, this version of the tulip code does not work with my card.

However, there is also the different version of the tulip code which comes with the kernel and is supposed to support "regular" PCI NICs as well as CardBus cards. I have compiled a 2.3.99-pre2 kernel and pcmcia-cs in attempt to use it for my card.

I enabled "hot-swappable" (yes), "PCMCIA" (module) and "CardBus" (yes) support in the kernel configuration as well as choosing the regular tulip DS2x14x driver in "network devices". pcmcia-cs did not compile any of its drivers, which is fine since I only need the kernel tulip driver.

Now, when I try to use the kernel PCMCIA code, it decides to exclude more memory ranges than the standalone version. This results in my card not being identified. Instead, it is listed as an "anonymous memory" card.

Here are kernel logs for the two cases. First, the way it looks when PCMCIA support in the kernel is disabled and the standalone pcmcia-cs is used:

Mar 24 21:07:37 elessar pcmcia: Starting PCMCIA services:
Mar 24 21:07:37 elessar pcmcia:  modules
Mar 24 21:07:37 elessar kernel: Linux PCMCIA Card Services 3.1.13
Mar 24 21:07:37 elessar kernel:   kernel build: 2.3.99-pre2 #8 Fri Mar 24 18:54:56 CET 2000
Mar 24 21:07:37 elessar kernel:   options:  [pci] [cardbus]
Mar 24 21:07:37 elessar kernel: Intel PCIC probe: PCI: Assigned IRQ 10 to device 00:03.1 [PIIX-NEW]
Mar 24 21:07:37 elessar kernel:
Mar 24 21:07:37 elessar kernel:   O2Micro OZ6836/OZ6860 PCI-to-CardBus at slot 00:03, mem 0x10000000
Mar 24 21:07:37 elessar kernel:     host opts [0]: [ring] [pci+isa] [pci irq 10] [lat 168/176] [bus
1/2]
Mar 24 21:07:37 elessar kernel:     host opts [1]: [ring] [pci+isa] [pci irq 10] [lat 168/176] [bus
3/4]
Mar 24 21:07:37 elessar kernel:     ISA irqs (default) = 3,4,5,7,9,12 PCI status changes
Mar 24 21:07:37 elessar pcmcia:  cardmgr.
Mar 24 21:07:37 elessar cardmgr[280]: starting, version is 3.1.13
Mar 24 21:07:37 elessar rc: Starting pcmcia succeeded
Mar 24 21:07:37 elessar cardmgr[280]: watching 2 sockets
Mar 24 21:07:37 elessar kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x1000-0x104f
Mar 24 21:07:37 elessar kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x100-0x107 0x200-0x207 0
x220-0x22f 0x300-0x307 0x378-0x37f 0x388-0x38f 0x398-0x39f 0x4d0-0x4d7
[snip]
Mar 24 21:08:36 elessar cardmgr[280]: initializing socket 0
Mar 24 21:08:36 elessar cardmgr[280]: socket 0: SMC EZ CardBus 10/100 PC Card
Mar 24 21:08:36 elessar kernel: cs: cb_alloc(bus 1): vendor 0x1011, device 0x0019
Mar 24 21:08:36 elessar kernel: ROM image dump:
Mar 24 21:08:36 elessar kernel:   image 0: 0x000000-0x0001ff, signature PCIR
Mar 24 21:08:36 elessar cardmgr[280]: executing: 'insmod /lib/modules/2.3.99-pre2/pcmcia/cb_enabler.
o'
Mar 24 21:08:36 elessar cardmgr[280]: executing: 'insmod /lib/modules/2.3.99-pre2/pcmcia/tulip_cb.o'
Mar 24 21:08:36 elessar kernel: cs: cb_config(bus 1)
Mar 24 21:08:36 elessar kernel:   fn 0 bar 1: io 0x400-0x47f
Mar 24 21:08:36 elessar kernel:   fn 0 bar 2: mem 0xa00c0000-0xa00c03ff
Mar 24 21:08:36 elessar kernel:   fn 0 rom: mem 0xa0080000-0xa00bffff
Mar 24 21:08:36 elessar kernel: cs: cb_enable(bus 1)
Mar 24 21:08:36 elessar kernel:   bridge io map 0 (flags 0x21): 0x400-0x47f
Mar 24 21:08:36 elessar kernel:   bridge mem map 0 (flags 0x1): 0xa0080000-0xa00c0fff
Mar 24 21:08:36 elessar kernel: tulip_reap()
Mar 24 21:08:36 elessar kernel: tulip_attach(bus 1, function 0)
Mar 24 21:08:36 elessar 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)
Mar 24 21:08:36 elessar kernel: eth0: Digital DS21143 Tulip rev 65 at 0x400, 00:E0:29:55:E1:12, IRQ
10.
Mar 24 21:08:36 elessar kernel: eth0:  EEPROM default media type Autosense.
Mar 24 21:08:36 elessar kernel: eth0:  Index #0 - Media MII (#11) described by a 21142 MII PHY (3) b
lock.
Mar 24 21:08:36 elessar kernel: eth0:  MII transceiver #1 config 3000 status 7809 advertising 00a1.
Mar 24 21:08:36 elessar kernel: eth0:  Advertising 01e1 on PHY 1, previously advertising 00a1.
Mar 24 21:08:36 elessar kernel: eth0:  Advertising 01e1 (to advertise is 01e1).
Mar 24 21:08:36 elessar cardmgr[280]: executing: './network start eth0'
[ping local machine]
Mar 24 21:11:36 elessar kernel: spurious 8259A interrupt: IRQ7.

(various versions of the tulip driver have failed in weird & wonderful ways. The kernel one seems to be most actively developed ATM, which is why I want to try it. BTW, /proc/interrupts shows that IRQ 7 is indeed not used.)

For the second case, with PCMCIA support in the kernel, the following is logged:

Mar 24 22:20:56 elessar pcmcia: Starting PCMCIA services:
Mar 24 22:20:56 elessar pcmcia:  modules
Mar 24 22:20:56 elessar kernel: Linux PCMCIA Card Services 3.1.11
Mar 24 22:20:56 elessar kernel:   kernel build: 2.3.99-pre2 #1 Fri Mar 24 22:02:38 CET 2000
Mar 24 22:20:56 elessar kernel:   options:  [pci] [cardbus] [pm]
Mar 24 22:20:56 elessar kernel: Intel PCIC probe:
Mar 24 22:20:56 elessar kernel:   Intel i82365sl A step ISA-to-PCMCIA at port 0x3e0 ofs 0x00, 2 sock
ets
Mar 24 22:20:56 elessar kernel:     host opts [0]: none
Mar 24 22:20:56 elessar kernel:     host opts [1]: none
Mar 24 22:20:56 elessar kernel:     ISA irqs (scanned) = 3,4,5,7 polling interval = 1000 ms
Mar 24 22:20:56 elessar pcmcia:  cardmgr.
Mar 24 22:20:56 elessar rc: Starting pcmcia succeeded
Mar 24 22:20:56 elessar cardmgr[280]: starting, version is 3.1.11
Mar 24 22:20:57 elessar cardmgr[280]: watching 2 sockets
Mar 24 22:20:57 elessar kernel: cs: IO port probe 0x1000-0x17ff: clean.
Mar 24 22:20:57 elessar kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x100-0x107 0x200-0x207 0
x220-0x22f 0x300-0x307 0x378-0x37f 0x388-0x38f 0x398-0x39f 0x4d0-0x4d7
[snip]
Mar 24 22:21:55 elessar kernel: cs: memory probe 0x0d0000-0x0dffff: excluding 0xdc000-0xdffff
Mar 24 22:21:55 elessar kernel: cs: memory probe 0x0c0000-0x0cffff: excluding 0xc0000-0xcbfff
Mar 24 22:21:55 elessar cardmgr[280]: initializing socket 0
Mar 24 22:21:55 elessar cardmgr[280]: socket 0: Anonymous Memory
Mar 24 22:21:55 elessar cardmgr[280]: module /lib/modules/2.3.99-pre2/pcmcia/memory_cs.o not availab
le
Mar 24 22:21:56 elessar cardmgr[280]: get dev info on socket 0 failed: Resource temporarily unavaila
ble

AFAICT the memory ranges reported in the "memory probe" messages are not used by anything else!

Is the differing behaviour due to a difference between the pcmcia-cs 3.1.11 in the kernel and the 3.1.13 I used for the first case above? What can I do to fix the problem?

My /etc/pcmcia/config.opts for both cases was:

include port 0x100-0x4ff, port 0x1000-0x17ff
include memory 0xc0000-0xfffff, memory 0xa0000000-0xa0ffffff
exclude irq 4
exclude irq 7
card "SMC EZ CardBus 10/100 PC Card"
  manfid 0x01bf, 0x2220
  bind "tulip_cb"

When the above things failed, I tried to make the standalone pcmcia-cs load and use the kernel tulip driver. However, I don't really know how I am supposed to do this. I tried changing my /etc/pcmcia/config.opts file to load the normal tulip driver like this:

include port 0x100-0x4ff, port 0x1000-0x17ff
include memory 0xc0000-0xfffff, memory 0xa0000000-0xa0ffffff
exclude irq 4
exclude irq 7
device "tulip2_cb"
  class "network" module "cb_enabler", "net/tulip"                                                                               opts "tulip_debug=6"
card "SMC EZ CardBus 10/100 PC Card"
  manfid 0x01bf, 0x2220
  bind "tulip2_cb"

Not very surprisingly, this doesn't work; the kernel tulip driver just complains I/O ports (0x80@0x0) unavailable, aborting and refuses to load.

At this point I'm really stuck. I have been trying to get this card to work for four months now - any help would be very much appreciated!!

Thanks for reading this far,
Even more thanks for any help you can give,

  Richard

Next-in-Thread Next Message

Messages Inline: 1 All Outline: 1 2 All

1. None Configuration on 2.3.* by David Hinds, 2000, Mar 31

Add Message to: "Using regular kernel tulip driver with pcmcia-cs"

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