802.11g wrote:

> I've compiled kernel 2.4.25, without PCMCIA support. Then, I compiled
> pcmcia-cs-3.2.7, and installed everything.

Why did you do this? The pcmcia-cs drivers are deprecated.

> Adapter now gets recognized, and I get following output when starting
> PCMCIA service:

> Apr 6 17:14:55 amber kernel: Linux PCMCIA Card Services 3.2.7
> Apr 6 17:14:55 amber kernel: kernel build: 2.4.25 #3 Tue Apr 6 17:08:21 CEST 2004
> Apr 6 17:14:55 amber kernel: options: [pci] [cardbus] [apm]
> Apr 6 17:14:55 amber kernel: Intel ISA/PCI/CardBus PCIC probe:
> Apr 6 17:14:55 amber kernel: Ricoh RL5C475 rev 80 PCI-to-CardBus at slot 01:08, mem 0xe2000000
> Apr 6 17:14:55 amber kernel: host opts [0]: [isa irq] [io 3/6/1] [mem 3/6/1] [pci irq 5] [lat 32/32] [bus 2/2]
> Apr 6 17:14:55 amber kernel: ISA irqs (default) = 3,4,7,9 PCI status changes

You would need to load the i82365 module with "irq_mode=0". This is
documented in the PCMCIA-HOWTO in the section on PCI card readers.

> However, I can't manage to have PCMCIA cards recognized. With Senao cards,
> I get all kinds of errors (with hostap driver). I've tried to use
> linux-wlan-ng driver as well (with kernel PCMCIA support compiled, so that
> it uses yenta), but it didn't work as well.

"all kinds of errors" is not sufficiently descriptive to be helpful.

Whatever Linux distribution you had, probably came preinstalled with
PCMCIA drivers, including an orinoco_cs driver. You probably should
have tried that standard setup, before installing pcmcia-cs and
fiddling with alternative drivers.

> Now, I've tried to insert a normal network card (Linksys PCM200 v1), and
> I'm experiencing wierd things. Basically, when I start PCMCIA service and
> try to do lspci, I get:

> [root@amber root]# lspci
> pcilib: Cannot open /proc/bus/pci/02/00.0
> lspci: Unable to read 64 bytes of configuration space.

This is a problem with the pcmcia-cs drivers on 2.4 kernels. Live
with it; it only affects 'lspci' as far as I know. By the way, you
did not mention whether the card actually works or not.

> Apr 6 17:57:10 amber kernel: eth1: Asix AX88790: io 0x300, irq 5, hw_addr FF:FF:FF:FF:FF:FF
> Apr 6 17:57:10 amber kernel: No MII transceivers found!

> Hardware address is screwed up, and "No MII transceivers found!" message
> is even scarier, I guess.

Interesting. I haven't seen those errors before.

> Does anyone have a clue on what I might try in order to make cards work in
> this adapter? Was the "include memory ..." directive correct, or I need to
> include/exclude some other memory ranges as well?

I'd suggest starting out by reverting to the kernel PCMCIA subsystem
and then describing how each card behaves on that normal setup. Your
memory range addition looks good to me.

-- Dave

On Tue, 06 Apr 2004 16:21:19 +0000, dhind wrote:


Dave,

Thanks for such a prompt response. Much appreciated.

>> I've compiled kernel 2.4.25, without PCMCIA support. Then, I compiled
>> pcmcia-cs-3.2.7, and installed everything.
>
> Why did you do this? The pcmcia-cs drivers are deprecated.

Right. I'm bit lost now I was under impression that PCMCIA support in
kernel is not as "advanced" as pcmcia-cs, so I used to disable PCMCIA in
kernel, and always used (on laptops, mostly) pcmcia-cs.

I've read README-2.4, but I'm still not sure if I need pcmcia-cs or not.
Since you're the authority on the subject, can you clarify this? Do I
need, at all, pcmcia-cs when using kernel 2.4.24 (don't have hostap pathes
for 2.4.25, so I'd try this again as well) or 2.4.25?

> You would need to load the i82365 module with "irq_mode=0". This is
> documented in the PCMCIA-HOWTO in the section on PCI card readers.

Yes, I've tried using

PCIC_OPTS="irq_mode=0"

in /etc/sysconfig/pcmcia, but it didn't work for me. But I will use it
again, since I presume you know very well what you are talking about

>> However, I can't manage to have PCMCIA cards recognized. With Senao cards,
>> I get all kinds of errors (with hostap driver). I've tried to use
>> linux-wlan-ng driver as well (with kernel PCMCIA support compiled, so that
>> it uses yenta), but it didn't work as well.
>
> "all kinds of errors" is not sufficiently descriptive to be helpful.

Basically, those errors were hostap/linux-wlan-ng related (not being able
to find PDA, read firmware, etc.), so I didn't think it was relevant.
Since 2 other cards (network cards) didn't work either, I assumed it was
PCMCIA related, not hostap/linux-wlan-ng related.

I've posted a question about those errors to hostap mailing list, so I'll
see if someone had similar experiences.

> Whatever Linux distribution you had, probably came preinstalled with
> PCMCIA drivers, including an orinoco_cs driver. You probably should
> have tried that standard setup, before installing pcmcia-cs and
> fiddling with alternative drivers.

This is RH9, but kernel is compiled by me, and pcmcia packages removed
long ago. I've compiled everything by myself. But now that you've
mentioned I might not need pcmcia-cs, I'll try to recompile kernel with
PCMCIA support and drivers enabled (will apply hostap patches first).

>> [root@amber root]# lspci
>> pcilib: Cannot open /proc/bus/pci/02/00.0
>> lspci: Unable to read 64 bytes of configuration space.
>
> This is a problem with the pcmcia-cs drivers on 2.4 kernels. Live
> with it; it only affects 'lspci' as far as I know. By the way, you
> did not mention whether the card actually works or not.

The Linksys card didn't work with pcmcia-cs. When I used PCMCIA in kernel,
I didn't have tulip_cb driver (since it's part of pcmcia-cs). But I guess
if I compile PCMCIA kernel support and enable tulip driver that comes with
kernel, it might work. Will try it later.

>> Apr 6 17:57:10 amber kernel: eth1: Asix AX88790: io 0x300, irq 5, hw_addr FF:FF:FF:FF:FF:FF
>> Apr 6 17:57:10 amber kernel: No MII transceivers found!
>
>> Hardware address is screwed up, and "No MII transceivers found!" message
>> is even scarier, I guess.
>
> Interesting. I haven't seen those errors before.

Neither have I I used that card in laptop, and it worked just fine
before. But when I used it in PCMCIA/PCI adapter, this error popped up. I
assumed something with adapter configuration/settings was wrong.

> I'd suggest starting out by reverting to the kernel PCMCIA subsystem
> and then describing how each card behaves on that normal setup. Your
> memory range addition looks good to me.

Thanks. I will, indeed, try what you said. I mean, now that
you've suggested this, I know I am on the right track, so I'll try
whatever I can and see if I have success.

Thanks once again for your help

On Tue, 06 Apr 2004 16:21:19 +0000, dhind wrote:

> I'd suggest starting out by reverting to the kernel PCMCIA subsystem
> and then describing how each card behaves on that normal setup. Your
> memory range addition looks good to me.
>
> -- Dave

Dave,

A small followup.

I've put the PCMCIA cards into the laptop, and all of them work fine. So,
the problem is Ricoh based PCMCIA-PCI adapter (I guess).

All the things I've tried (using pcmcia-cs, using kernel PCMCIA stuff,
using "irq_mode=0") didn't bring any results.

What could I possibly do, in order to figure out what the problem is, and
which settings I could tweak? I wouldn't mind digging into code and
modifying things either, but I'd need some pointers (since I haven't
looked at pcmcia-cs or kernel pcmcia code ever).

Do you reckon tweaking anything in BIOS could give any results? If so,
what should I play with?

Thanks in advance.

802.11g wrote:
> On Tue, 06 Apr 2004 16:21:19 +0000, dhind wrote:

>> I'd suggest starting out by reverting to the kernel PCMCIA subsystem
>> and then describing how each card behaves on that normal setup. Your
>> memory range addition looks good to me.
>>
>> -- Dave

> All the things I've tried (using pcmcia-cs, using kernel PCMCIA stuff,
> using "irq_mode=0") didn't bring any results.

> What could I possibly do, in order to figure out what the problem is, and
> which settings I could tweak? I wouldn't mind digging into code and
> modifying things either, but I'd need some pointers (since I haven't
> looked at pcmcia-cs or kernel pcmcia code ever).

You should do exactly what I said: with the kernel PCMCIA subsystem,
describe the behavior of each of your cards with specificity. So far,
you have not done that.

-- Dave

On Wed, 07 Apr 2004 16:00:53 +0000, dhind wrote:

> You should do exactly what I said: with the kernel PCMCIA subsystem,
> describe the behavior of each of your cards with specificity. So far,
> you have not done that.

Dave,

I have recompiled the kernel (2.4.25, with hostap patch only). PCMCIA-PCI
adapter in question is Ricoh based. This is what lspci says about it:

01:08.0 CardBus bridge: Ricoh Co Ltd RL5c475 (rev 80)
Subsystem: CARRY Computer ENG. CO Ltd: Unknown device 0101
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Latency: 168
Interrupt: pin A routed to IRQ 5
Region 0: Memory at e2000000 (32-bit, non-prefetchable)
Bus: primary=01, secondary=02, subordinate=02, sec-latency=176
Memory window 0: e2001000-e2002000 (prefetchable)
Memory window 1: e2003000-e2004000
I/O window 0: 0000c000-0000c403
I/O window 1: 0000c800-0000cc03
BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt- PostWrite+
16-bit legacy interface ports at 0001

/etc/sysconfig/pcmcia contains:

PCMCIA=yes
PCIC=i82365
PCIC_OPTS="irq_mode=0"
CORE_OPTS=
CARDMGR_OPTS=

I have also tried removing "irq_mode=0", but results were the same.

These cards work okay in Laptop (Toshiba Presario 700), for example.

These are the results:

1. Linksys PCM200 Ethernet network adapter

Worked okay. I could bring the interface up, and use it.

[root@amber root]# cardctl ident
Socket 0:
product info: "Linksys", "EtherFast Integrated 10/100 CardBus PC
Card(PCM200)", "V1.0", "" manfid: 0x13d1, 0xab02
function: 6 (network)
[root@amber root]#

Apr 8 14:27:17 amber kernel: Linux Kernel Card Services 3.1.22
Apr 8 14:27:17 amber kernel: options: [pci] [cardbus] [pm]
Apr 8 14:27:17 amber kernel: Intel ISA PCIC probe: not found.
Apr 8 14:27:17 amber kernel: Yenta ISA IRQ mask 0x0000, PCI irq 5
Apr 8 14:27:17 amber kernel: Socket status: 30000820
Apr 8 14:27:17 amber kernel: cs: cb_alloc(bus 2): vendor 0x1737, device 0xab09
Apr 8 14:27:17 amber kernel: PCI: Failed to allocate resource 6(e2020000-e2004fff) for 02:00.0
Apr 8 14:27:17 amber kernel: PCI: Enabling device 02:00.0 (0000 -> 0003)
Apr 8 14:27:17 amber cardmgr[5119]: watching 1 socket
Apr 8 14:27:17 amber kernel: cs: IO port probe 0x0c00-0x0cff: clean.
Apr 8 14:27:17 amber kernel: cs: IO port probe 0x0800-0x08ff: clean.
Apr 8 14:27:17 amber kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x290-0x297 0x378-0x37f 0x4d0-0x4d7
Apr 8 14:27:17 amber kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Apr 8 14:27:17 amber cardmgr[5120]: socket 0: CardBus hotplug device
Apr 8 14:27:17 amber /etc/hotplug/pci.agent: Setup tulip for PCI slot 02:00.0
Apr 8 14:27:17 amber kernel: Linux Tulip driver version 0.9.15-pre12 (Aug 9, 2002)
Apr 8 14:27:17 amber kernel: PCI: Setting latency timer of device 02:00.0 to 64
Apr 8 14:27:17 amber kernel: eth1: ADMtek Comet rev 17 at 0xc000, 00:04:5A:A2:B7:FA, IRQ 5.
Apr 8 14:27:17 amber /etc/hotplug/net.agent: invoke ifup eth1
Apr 8 14:27:18 amber devlabel: devlabel service started/restarted


2. SureCom EP-427X Ethernet network adapter

Does not work. Seems like module is loaded, but MAC address is set to
FF:FF:FF:FF:FF:FF and error messages show up. If I bring the interface up,
I can see no traffic on it with tcpdump (and I'm connected to port which
is in port mirroring mode, and I always see *lots* of traffic).

[root@amber root]# cardctl ident
Socket 0:
product info: "CouplerlessPCMCIA", "100BASE" manfid: 0xffff, 0x1090
function: 6 (network)
[root@amber root]#

Apr 8 14:40:04 amber kernel: Linux Kernel Card Services 3.1.22
Apr 8 14:40:04 amber kernel: options: [pci] [cardbus] [pm]
Apr 8 14:40:04 amber kernel: Intel ISA PCIC probe: not found.
Apr 8 14:40:04 amber kernel: Yenta ISA IRQ mask 0x0000, PCI irq 5
Apr 8 14:40:04 amber kernel: Socket status: 30000410
Apr 8 14:40:04 amber cardmgr[5816]: watching 1 socket
Apr 8 14:40:04 amber kernel: cs: IO port probe 0x0c00-0x0cff: clean.
Apr 8 14:40:04 amber kernel: cs: IO port probe 0x0800-0x08ff: clean.
Apr 8 14:40:04 amber kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x290-0x297 0x378-0x37f 0x4d0-0x4d7
Apr 8 14:40:04 amber kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Apr 8 14:40:04 amber kernel: cs: memory probe 0xe2000000-0xe2ffffff: excluding 0xe2000000-0xe20fffff
Apr 8 14:40:04 amber cardmgr[5817]: socket 0: NE2000 Compatible Fast Ethernet
Apr 8 14:40:05 amber kernel: eth1: Asix AX88790: io 0x300, irq 5, hw_addr FF:FF:FF:FF:FF:FF
Apr 8 14:40:05 amber kernel: No MII transceivers found!
Apr 8 14:40:05 amber /etc/hotplug/net.agent: invoke ifup eth1
Apr 8 14:40:30 amber kernel: eth1: interrupt(s) dropped!

3. Intersil Prism 2.5 (Senao) Wireless PCMCIA Adapter

Does not work. I've tried linux-wlan-ng and hostap drivers.

[root@amber root]# cardctl ident
Socket 0:
product info: "INTERSIL", "HFA384x/IEEE", "Version 01.02", ""
manfid: 0x0156, 0x0002
function: 6 (network)
[root@amber root]#

linux-wlan-ng driver:

Apr 8 14:57:35 amber kernel: Linux Kernel Card Services 3.1.22
Apr 8 14:57:35 amber kernel: options: [pci] [cardbus] [pm]
Apr 8 14:57:35 amber kernel: Intel ISA PCIC probe: not found.
Apr 8 14:57:35 amber kernel: Yenta ISA IRQ mask 0x0000, PCI irq 5
Apr 8 14:57:35 amber kernel: Socket status: 30000810
Apr 8 14:57:36 amber cardmgr[6258]: watching 1 socket
Apr 8 14:57:36 amber kernel: cs: IO port probe 0x0c00-0x0cff: clean.
Apr 8 14:57:36 amber kernel: cs: IO port probe 0x0800-0x08ff: clean.
Apr 8 14:57:36 amber kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x290-0x297 0x378-0x37f 0x4d0-0x4d7
Apr 8 14:57:36 amber kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Apr 8 14:57:36 amber kernel: cs: memory probe 0xe2000000-0xe2ffffff: excluding 0xe2000000-0xe20fffff
Apr 8 14:57:36 amber cardmgr[6259]: socket 0: Intersil PRISM2 Reference Design 11Mb/s 802.11b WLAN Card
Apr 8 14:57:36 amber kernel: prism2cs_init: prism2_cs.o: 0.2.1-pre20 Loaded
Apr 8 14:57:36 amber kernel: prism2cs_init: dev_info is: prism2_cs
Apr 8 14:57:36 amber kernel: prism2_cs: index 0x01: Vcc 3.3, irq 5, io 0x0100-0x013f
Apr 8 14:57:36 amber /etc/hotplug/wlan.agent: WLAN startup on null (null)
Apr 8 14:57:36 amber /etc/hotplug/net.agent: invoke ifup wlan0
Apr 8 14:57:36 amber /etc/hotplug/wlan.agent: WLAN register on wlan0 (prism2_cs)
Apr 8 14:57:36 amber /etc/hotplug/wlan.agent: WLAN Hotplug bypassed for pcmcia
Apr 8 14:57:36 amber kernel: ip_tables: (C) 2000-2002 Netfilter core team
Apr 8 14:57:36 amber /etc/hotplug/wlan.agent: WLAN p80211 starting!
Apr 8 14:57:37 amber cardmgr[6259]: executing: './wlan-ng start wlan0 2>&1'
Apr 8 14:57:37 amber cardmgr[6259]: + modprobe: Can't locate module wlan0
Apr 8 14:57:37 amber wland[6328]: wland daemon init successful
Apr 8 14:57:37 amber wland[6328]: netlink socket opened and bound successfully
Apr 8 14:57:37 amber kernel: hfa384x_docmd_wait: hfa384x_cmd timeout(1), reg=0xffff.
Apr 8 14:57:37 amber cardmgr[6259]: + message=lnxreq_ifstate
Apr 8 14:57:37 amber cardmgr[6259]: + ifstate=fwload
Apr 8 14:57:37 amber cardmgr[6259]: + resultcode=success
Apr 8 14:57:37 amber kernel: prism2mgmt_readpda: hfa384x_drvr_readpda() failed, result=-110
Apr 8 14:57:37 amber cardmgr[6259]: + load_cardpda failed, exiting.
Apr 8 14:57:37 amber cardmgr[6259]: + Unknown prism2 hardware type , assuming SSF
Apr 8 14:57:37 amber kernel: hfa384x_docmd_wait: hfa384x_cmd timeout(1), reg=0xffff.
Apr 8 14:57:37 amber kernel: hfa384x_cmd_access: Call to hfa384x_docmd_wait failed (-110 0)
Apr 8 14:57:37 amber kernel: hfa384x_drvr_ramdl_enable: Genesis mode failed
Apr 8 14:57:37 amber cardmgr[6259]: + prism2dl: warning: Failed to find PDR for plugrec 0x0003.
Apr 8 14:57:37 amber cardmgr[6259]: + prism2dl: warning: Failed to find PDR for plugrec 0x0005.
Apr 8 14:57:37 amber cardmgr[6259]: + prism2dl: warning: Failed to find PDR for plugrec 0x0006.
Apr 8 14:57:37 amber cardmgr[6259]: + prism2dl: warning: Failed to find PDR for plugrec 0x0007.
Apr 8 14:57:37 amber cardmgr[6259]: + prism2dl: warning: Failed to find PDR for plugrec 0x0008.
Apr 8 14:57:37 amber cardmgr[6259]: + prism2dl: warning: Failed to find PDR for plugrec 0x0402.
Apr 8 14:57:37 amber cardmgr[6259]: + prism2dl: warning: Failed to find PDR for plugrec 0x0403.
Apr 8 14:57:37 amber cardmgr[6259]: + prism2dl: warning: Failed to find PDR for plugrec 0x0404.
Apr 8 14:57:37 amber cardmgr[6259]: + prism2dl: warning: Failed to find PDR for plugrec 0x0408.
Apr 8 14:57:37 amber kernel: prism2mgmt_readpda: hfa384x_drvr_readpda() failed, result=-61
Apr 8 14:57:37 amber cardmgr[6259]: + prism2dl: warning: Failed to find PDR for plugrec 0x0001.
Apr 8 14:57:37 amber kernel: hfa384x_docmd_wait: hfa384x_cmd timeout(1), reg=0xffff.
Apr 8 14:57:37 amber cardmgr[6259]: + prism2dl: writeimage()->xxxdl_state msg indicates failure, w/ resultcode=11, aborting download.
Apr 8 14:57:37 amber kernel: hfa384x_drvr_start: Initialize command failed.
Apr 8 14:57:37 amber cardmgr[6259]: + prism2dl: Failed to ramwrite image data for /etc/wlan//prism2_pm.hex, exiting.
Apr 8 14:57:37 amber kernel: hfa384x_drvr_start: Failed, result=-110
Apr 8 14:57:37 amber cardmgr[6259]: + Processing PDR file: /etc/wlan//prism2_ssf.pda
Apr 8 14:57:37 amber kernel: prism2sta_ifstate: hfa384x_drvr_start() failed,result=-110
Apr 8 14:57:37 amber cardmgr[6259]: + Couldn't fetch PRI-SUP info
Apr 8 14:57:37 amber cardmgr[6259]: + Warning: RAM load only, PDA changes will NOT be written to flash.
Apr 8 14:57:37 amber cardmgr[6259]: + Reading S-record file /etc/wlan//prism2_pm.hex...
Apr 8 14:57:37 amber cardmgr[6259]: + NIC ID: 0 v0.0.0
Apr 8 14:57:37 amber cardmgr[6259]: + MFI ID: 0 v0 0->0
Apr 8 14:57:37 amber cardmgr[6259]: + CFI ID: 0 v0 0->0
Apr 8 14:57:37 amber cardmgr[6259]: + PRI ID: 0x254a v10965 49171->35740
Apr 8 14:57:37 amber cardmgr[6259]: + Version: ID 0x15 1.1.2
Apr 8 14:57:37 amber cardmgr[6259]: + Compat: Role 0 Id 0x3 v2 4->4
Apr 8 14:57:37 amber cardmgr[6259]: + Compat: Role 0x1 Id 0x2 v2 1->1
Apr 8 14:57:37 amber cardmgr[6259]: + Seq: 0
Apr 8 14:57:37 amber cardmgr[6259]: + Platform: ID 0x800e 1.0.0
Apr 8 14:57:37 amber cardmgr[6259]: + Platform: ID 0x8015 1.0.0
Apr 8 14:57:37 amber cardmgr[6259]: + Platform: ID 0x8019 1.0.0
Apr 8 14:57:37 amber cardmgr[6259]: + Platform: ID 0x801d 1.0.0
Apr 8 14:57:37 amber cardmgr[6259]: + Platform: ID 0x8024 1.0.0
Apr 8 14:57:37 amber cardmgr[6259]: + name inforec len 7
Apr 8 14:57:37 amber cardmgr[6259]: + load_cardpda failed, exiting.
Apr 8 14:57:37 amber cardmgr[6259]: + Failed to enable the device, resultcode= implementation_failure .
Apr 8 14:57:42 amber cardmgr[6259]: + wlanctl-ng: No such device
Apr 8 14:57:42 amber cardmgr[6259]: + error: Autojoin indicated failure!
Apr 8 14:57:42 amber kernel: ip_tables: (C) 2000-2002 Netfilter core team
Apr 8 14:57:42 amber cardmgr[6259]: + /sbin/ifup wlan0
Apr 8 14:57:42 amber cardmgr[6259]: + SIOCSIFFLAGS: No such device
Apr 8 14:57:42 amber cardmgr[6259]: + Failed to bring up wlan0.

hostap driver:

Apr 8 15:01:45 amber kernel: Linux Kernel Card Services 3.1.22
Apr 8 15:01:45 amber kernel: options: [pci] [cardbus] [pm]
Apr 8 15:01:45 amber kernel: Intel ISA PCIC probe: not found.
Apr 8 15:01:45 amber kernel: Yenta ISA IRQ mask 0x0000, PCI irq 5
Apr 8 15:01:45 amber kernel: Socket status: 30000810
Apr 8 15:01:46 amber cardmgr[6901]: watching 1 socket
Apr 8 15:01:46 amber kernel: cs: IO port probe 0x0c00-0x0cff: clean.
Apr 8 15:01:46 amber kernel: cs: IO port probe 0x0800-0x08ff: clean.
Apr 8 15:01:46 amber kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x290-0x297 0x378-0x37f 0x4d0-0x4d7
Apr 8 15:01:46 amber kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Apr 8 15:01:46 amber kernel: cs: memory probe 0xe2000000-0xe2ffffff: excluding 0xe2000000-0xe20fffff
Apr 8 15:01:46 amber cardmgr[6902]: socket 0: Senao SL-2011CD/SL-2011CDPLUS
Apr 8 15:01:46 amber kernel: hostap_crypt: registered algorithm 'NULL'
Apr 8 15:01:46 amber kernel: hostap_cs: CVS (Jouni Malinen )
Apr 8 15:01:46 amber kernel: hostap_cs: setting Vcc=33 (constant)
Apr 8 15:01:46 amber kernel: hostap_cs: CS_EVENT_CARD_INSERTION
Apr 8 15:01:46 amber kernel: hostap_cs: setting Vcc=33 (from config)
Apr 8 15:01:46 amber kernel: Checking CFTABLE_ENTRY 0x01 (default 0x01)
Apr 8 15:01:46 amber kernel: IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
Apr 8 15:01:46 amber kernel: io->flags = 0x0046, io.base=0x0000, len=64
Apr 8 15:01:46 amber kernel: hostap_cs: Registered netdevice wifi0
Apr 8 15:01:46 amber kernel: hostap_cs: index 0x01: Vcc 3.3, irq 5, io 0x0100-0x013f
Apr 8 15:01:46 amber kernel: wifi0: __hfa384x_cmd_no_wait(6) - timeout - reg=0xffff
Apr 8 15:01:46 amber kernel: hostap_cs: first command failed - assuming card does not have primary firmware
Apr 8 15:01:46 amber kernel: wifi0: init command completed too quickly - retrying
Apr 8 15:01:46 amber kernel: wifi0: __hfa384x_cmd_no_wait(6) - timeout - reg=0xffff
Apr 8 15:01:46 amber kernel: hostap_cs: first command failed - assuming card does not have primary firmware
Apr 8 15:01:46 amber kernel: prism2_hw_init: initialized in 0 ms
Apr 8 15:01:46 amber kernel: wifi0: prism2_enable_aux_port - timeout - reg=0xffff
Apr 8 15:01:46 amber kernel: wifi0: prism2_enable_aux_port - timeout - reg=0xffff
Apr 8 15:01:46 amber kernel: wifi0: valid PDA not found
Apr 8 15:01:46 amber kernel: SWSUPPORT0 write/read failed: FFFF != 8A32
Apr 8 15:01:46 amber kernel: hostap_cs: Initialization failed
Apr 8 15:01:46 amber kernel: prism2_config() failed
Apr 8 15:01:46 amber /etc/hotplug/net.agent: invoke ifup wifi0

4. OvisLink WL-5400PCM (Intersil Prism GT) Wireless PCMCIA adapter

Does not work. It doesn't get recognized, but I am not sure what I could
do to fix this. I use driver from prism54.org.

It is recognized as D-Link card by lspci:

02:00.0 Network controller: Harris Semiconductor D-Links DWL-g650 A1 (rev 01)
Subsystem: Unknown device 17cf:0014
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Interrupt: pin A routed to IRQ 5
Capabilities: [dc] Power Management version 1
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

[root@amber pcmcia]# cardctl ident
Socket 0:
no product info available
[root@amber pcmcia]# dump_cis
Socket 0:
no CIS present
[root@amber pcmcia]#

Apr 8 15:08:40 amber kernel: Linux Kernel Card Services 3.1.22
Apr 8 15:08:40 amber kernel: options: [pci] [cardbus] [pm]
Apr 8 15:08:40 amber kernel: Intel ISA PCIC probe: not found.
Apr 8 15:08:40 amber kernel: Yenta ISA IRQ mask 0x0000, PCI irq 5
Apr 8 15:08:40 amber kernel: Socket status: 30000820
Apr 8 15:08:40 amber kernel: cs: cb_alloc(bus 2): vendor 0x1260, device 0x3890
Apr 8 15:08:40 amber kernel: PCI: Failed to allocate resource 0(e2004000-e2004fff) for 02:00.0
Apr 8 15:08:40 amber kernel: PCI: Enabling device 02:00.0 (0000 -> 0002)
Apr 8 15:08:40 amber cardmgr[7017]: watching 1 socket
Apr 8 15:08:40 amber kernel: cs: IO port probe 0x0c00-0x0cff: clean.
Apr 8 15:08:40 amber kernel: cs: IO port probe 0x0800-0x08ff: clean.
Apr 8 15:08:40 amber kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x290-0x297 0x378-0x37f 0x4d0-0x4d7
Apr 8 15:08:40 amber kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Apr 8 15:08:40 amber cardmgr[7018]: socket 0: CardBus hotplug device
Apr 8 15:08:41 amber /etc/hotplug/pci.agent: ... no modules for PCI slot 02:00.0

modprobe prism54 gives:

Apr 8 15:16:07 amber kernel: Loaded prism54 driver, version 1.1
Apr 8 15:16:07 amber kernel: prism54: PCI device memory region not configured; fix your BIOS or CardBus bridge/drivers

If any more details are needed, or if there is anything else that I could
try, let me know.

Thanks.

On Thu, 08 Apr 2004 15:22:30 +0200, 802.11g wrote:

Small followup to my own post:

> On Wed, 07 Apr 2004 16:00:53 +0000, dhind wrote:
>
>> You should do exactly what I said: with the kernel PCMCIA subsystem,
>> describe the behavior of each of your cards with specificity. So far,
>> you have not done that.
>
> Dave,
>
> I have recompiled the kernel (2.4.25, with hostap patch only).



> Apr 8 15:08:40 amber kernel: Linux Kernel Card Services 3.1.22
> Apr 8 15:08:40 amber kernel: options: [pci] [cardbus] [pm]
> Apr 8 15:08:40 amber kernel: Intel ISA PCIC probe: not found.
> Apr 8 15:08:40 amber kernel: Yenta ISA IRQ mask 0x0000, PCI irq 5
> Apr 8 15:08:40 amber kernel: Socket status: 30000820
> Apr 8 15:08:40 amber kernel: cs: cb_alloc(bus 2): vendor 0x1260, device 0x3890
> Apr 8 15:08:40 amber kernel: PCI: Failed to allocate resource 0(e2004000-e2004fff) for 02:00.0
> Apr 8 15:08:40 amber kernel: PCI: Enabling device 02:00.0 (0000 -> 0002)
> Apr 8 15:08:40 amber cardmgr[7017]: watching 1 socket
> Apr 8 15:08:40 amber kernel: cs: IO port probe 0x0c00-0x0cff: clean.
> Apr 8 15:08:40 amber kernel: cs: IO port probe 0x0800-0x08ff: clean.
> Apr 8 15:08:40 amber kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x290-0x297 0x378-0x37f 0x4d0-0x4d7
> Apr 8 15:08:40 amber kernel: cs: IO port probe 0x0a00-0x0aff: clean.
> Apr 8 15:08:40 amber cardmgr[7018]: socket 0: CardBus hotplug device
> Apr 8 15:08:41 amber /etc/hotplug/pci.agent: ... no modules for PCI slot 02:00.0
>
> modprobe prism54 gives:
>
> Apr 8 15:16:07 amber kernel: Loaded prism54 driver, version 1.1
> Apr 8 15:16:07 amber kernel: prism54: PCI device memory region not configured; fix your BIOS or CardBus bridge/drivers

I've stopped pcmcia service and restarted it few minutes later, and I
got:

Apr 8 15:33:13 amber kernel: Linux Kernel Card Services 3.1.22
Apr 8 15:33:13 amber kernel: options: [pci] [cardbus] [pm]
Apr 8 15:33:13 amber kernel: Intel ISA PCIC probe: not found.
Apr 8 15:33:13 amber kernel: Yenta ISA IRQ mask 0x0000, PCI irq 5
Apr 8 15:33:13 amber kernel: Socket status: 30000820
Apr 8 15:33:13 amber kernel: cs: cb_alloc(bus 2): vendor 0x1260, device 0x3890
Apr 8 15:33:13 amber kernel: PCI: Failed to allocate resource 0(e2006000-e2004fff) for 02:00.0
Apr 8 15:33:13 amber kernel: PCI: Enabling device 02:00.0 (0000 -> 0002)
Apr 8 15:33:13 amber cardmgr[9018]: watching 1 socket
Apr 8 15:33:13 amber kernel: cs: IO port probe 0x0c00-0x0cff: clean.
Apr 8 15:33:13 amber kernel: cs: IO port probe 0x0800-0x08ff: clean.
Apr 8 15:33:13 amber kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x290-0x297 0x378-0x37f 0x4d0-0x4d7
Apr 8 15:33:13 amber kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Apr 8 15:33:13 amber cardmgr[9019]: socket 0: CardBus hotplug device
Apr 8 15:33:13 amber /etc/hotplug/pci.agent: Setup prism54 for PCI slot 02:00.0
Apr 8 15:33:13 amber kernel: Loaded prism54 driver, version 1.1
Apr 8 15:33:13 amber kernel: PCI: Unable to reserve mem region #1:fffff000@e2006000 for device 02:00.0
Apr 8 15:33:13 amber kernel: PCI: Unable to reserve mem region #1:fffff000@e2006000 for device 02:00.0
Apr 8 15:33:13 amber kernel: prism54: pci_request_regions failure (rc=-16)
Apr 8 15:33:13 amber insmod: /lib/modules/2.4.25/kernel/drivers/net/wireless/prism54/prism54.o: init_module: No such device
Apr 8 15:33:13 amber insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Apr 8 15:33:13 amber insmod: /lib/modules/2.4.25/kernel/drivers/net/wireless/prism54/prism54.o: insmod /lib/modules/2.4.25/kernel/drivers/net/wireless/prism54/prism54.o failed
Apr 8 15:33:13 amber insmod: /lib/modules/2.4.25/kernel/drivers/net/wireless/prism54/prism54.o: insmod prism54 failed
Apr 8 15:33:13 amber /etc/hotplug/pci.agent: ... can't load module prism54
Apr 8 15:33:13 amber /etc/hotplug/pci.agent: missing kernel or user mode driver prism54
Apr 8 15:33:13 amber devlabel: devlabel service started/restarted

802.11g wrote:

> I have also tried removing "irq_mode=0", but results were the same.

Leave it out; the yenta driver doesnt recognize or need that option.

> 1. Linksys PCM200 Ethernet network adapter
> Worked okay. I could bring the interface up, and use it.

That's good...

> 2. SureCom EP-427X Ethernet network adapter
> Does not work.

Now I see the problem. Edit /etc/pcmcia/config.opts and comment out
all the "include port ..." lines, and instead add:

include port 0xc000-0xcfff

The problem is that the CardBus bridge is behind a PCI-to-PCI bridge
that only forwards a limited range of IO port accesses.

> 3. Intersil Prism 2.5 (Senao) Wireless PCMCIA Adapter
> Does not work. I've tried linux-wlan-ng and hostap drivers.

This one should also be fixed by the "include port" change.

> 4. OvisLink WL-5400PCM (Intersil Prism GT) Wireless PCMCIA adapter
....
> Apr 8 15:08:40 amber kernel: PCI: Failed to allocate resource 0(e2004000-e2004fff) for 02:00.0
....
> Apr 8 15:16:07 amber kernel: prism54: PCI device memory region not configured; fix your BIOS or CardBus bridge/drivers

This part is a tricky one. It is a bug in the kernel's PCI resource
allocation code. It tries to allocate CardBus memory resources from
whatever memory ranges happened to be allocated for the bridge device
by the BIOS at power-up time; but in this case, those memory windows
are too small. There isn't a simple fix for this and I don't have a
good suggestion for what to do about it; you can report it on the
linux-kernel mailing list.

- Dave

On Fri, 09 Apr 2004 04:13:50 +0000, dhind wrote:

>> 2. SureCom EP-427X Ethernet network adapter
>> Does not work.
>
> Now I see the problem. Edit /etc/pcmcia/config.opts and comment out
> all the "include port ..." lines, and instead add:
>
> include port 0xc000-0xcfff
>
> The problem is that the CardBus bridge is behind a PCI-to-PCI bridge
> that only forwards a limited range of IO port accesses.

Dave,

Thanks

This worked. Wireless card (Prism 2.5) works just fine now. Will try
another network card tomorrow (but I presume it'll work too).

>> 4. OvisLink WL-5400PCM (Intersil Prism GT) Wireless PCMCIA adapter
> ...
>> Apr 8 15:08:40 amber kernel: PCI: Failed to allocate resource 0(e2004000-e2004fff) for 02:00.0
> ...
>> Apr 8 15:16:07 amber kernel: prism54: PCI device memory region not configured; fix your BIOS or CardBus bridge/drivers
>
> This part is a tricky one. It is a bug in the kernel's PCI resource
> allocation code. It tries to allocate CardBus memory resources from
> whatever memory ranges happened to be allocated for the bridge device
> by the BIOS at power-up time; but in this case, those memory windows
> are too small. There isn't a simple fix for this and I don't have a
> good suggestion for what to do about it; you can report it on the
> linux-kernel mailing list.

Ok, thanks for the details. I will try to post it to the list.

Thanks once again for your help. Much appreciated