orinoco_cs driver problem: device initialization failure

I have a Dell 600m for which I purchased a TrueMobile 1150 mini-pci
wirelesscard. I have been tyring to use the 2.4.22. From what I've
read, others have gotten the device working with the orinoco_cs
module.

The following dmesg output summarizes my problem - it appears to be a
timeout during a register reset in hermes.c.


hermes.c: 4 Dec 2002 David Gibson <(E-Mail Removed)>
orinoco.c 0.13d (David Gibson <(E-Mail Removed)> ...)
orinoco_cs.c 0.13d (David Gibson <(E-Mail Removed)> ...)
hermes @ IO 0x100: Timeout waiting for card to reset (reg=0x0000)!
eth1: failed to initialize firmware (err = -110)
orinoco_cs: register_netdev() failed

Does this indicate bad hardware? unsupported hardware? anything?

Any help is appreciated.

For reference, I have already tried:
+ kernel 2.6.0-test4
+ pcmcia-cs drivers
+ linux-wlan-ng

The same problem appears with all of the above drivers.

cardctl ident produces:

Socket 0:
no product info available
Socket 1:
product info: "O2Micro", "SmartCardBus Reader", "V1.0"
manfid: 0xffff, 0x0001
Socket 2:
product info: "Lucent Technologies", "WaveLAN/IEEE", "Version
01.01", ""
manfid: 0x0156, 0x0002
function: 6 (network)

I don't know anything about your card in particular, but if you think
it works with orinoco_cs, then please try this, and report back to the
group with your results:

Run:
cardctl ident

This will give you the manfid of your card.

Then, in /etc/pcmcia/config.opts, add a line that looks like this:

card "Orinoco Card" manfid 0x123, 0x123 bind "orinoco_cs"

Of course, use the manfid you received from the "cardctl ident"
command instead of 0x123, 0x123.

Then reboot. I'm sure there's a more "Linux-like" way to make it take
effect, but this is the way I know.

After that, your card should be detected by the system and given the
correct driver.

Shawn

(E-Mail Removed) (Shawn Milo) wrote in message news:<(E-Mail Removed). com>...
> Run:
> cardctl ident

Output:

Socket 0:
no product info available
Socket 1:
product info: "O2Micro", "SmartCardBus Reader", "V1.0"
manfid: 0xffff, 0x0001
Socket 2:
product info: "Lucent Technologies", "WaveLAN/IEEE", "Version
01.01", ""
manfid: 0x0156, 0x0002
function: 6 (network)

So, manufacturer id = 0x0156, 0x0002

> Then, in /etc/pcmcia/config.opts, add a line that looks like this:
>
> card "Orinoco Card" manfid 0x123, 0x123 bind "orinoco_cs"

/etc/pcmcia/config has the following (part of pcmcia-cs config):

card "Intersil PRISM2 11 Mbps Wireless Adapter"
manfid 0x0156, 0x0002
bind "orinoco_cs"

> After that, your card should be detected by the system and given the
> correct driver.

The orinoco_cs driver is being loaded.

The driver is having problems. I don't know if it's driver problems
or hardware problems.

On Sun, 07 Sep 2003 08:17:03 -0700, Michael Smith typed:

> product info: "Lucent Technologies", "WaveLAN/IEEE", "Version
> 01.01", ""
> manfid: 0x0156, 0x0002
> function: 6 (network)

I use this very same card. All you need to do is edit the
/etc/pcmcia/config file;

card "Lucent Technologies WaveLAN/IEEE Adapter"
version "Lucent Technologies", "WaveLAN/IEEE" bind "wvlan_cs"

(watch for word warp the third line is bind...)

And make the appropriate change in /etc/modules.conf or /etc/modprobe.conf

alias ethX wvlan_cs



--
If it's Thursday it must be Micro$oft patching day!!!

Lenard <lenard@127.0.0.1> wrote in message news:<pan.2003.09.07.15.37.49.839786@127.0.0.1>...

> I use this very same card. All you need to do is edit the
> /etc/pcmcia/config file;
>
> card "Lucent Technologies WaveLAN/IEEE Adapter"
> version "Lucent Technologies", "WaveLAN/IEEE" bind "wvlan_cs"

I tried wvlan_cs from pcmcia-cs 3.2.4 with kernel 2.4.22 and am still
having problems. The driver loads, but seems to have a problem
interfacing with the hardware.

The dmesg output looks like the following:

cs: memory probe 0xa0000000-0xa0ffffff: clean.
wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.6
wvlan_cs: (c) Andreas Neuhaus <(E-Mail Removed)>
cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x3c0-0x3df
0x4d0-0x4d7
cs: IO port probe 0x0380-0x03bf: clean.
cs: IO port probe 0x03e0-0x04cf: clean.
cs: IO port probe 0x04d8-0x04ff: clean.
cs: IO port probe 0x0a00-0x0aff: clean.
cs: IO port probe 0x0c00-0x0cff: clean.
wvlan_cs: index 0x01: Vcc 3.3, irq 11, io 0x0100-0x013f
wvlan_cs: Registered netdevice eth1
wvlan_cs: MAC address on eth1 is 00 00 00 00 00 00
wvlan_cs: Found firmware 0x0 (vendor 0) - Firmware capabilities :
0-0-0-0-0
wvlan_cs: Initialization failed!

Clearly, the firmware capabilities and MAC address look suspicious.

I have tried excluding the io range it chooses (in
/etc/pcmcia/config.opts), but that didn't make a difference.

iwconfig will execute, but the card settings never change.

Google searches suggest that the dmesg output means the card isn't
supported by the driver, and often the advice is to use orinico_cs -
but that's where I started.

Still looking for a magic bullet.


For reference /proc/interrupts shows the following:

CPU0
0: 29058 XT-PIC timer
1: 564 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 0 XT-PIC ehci_hcd
8: 2 XT-PIC rtc
9: 5 XT-PIC acpi, usb-uhci, i82365
10: 18368 XT-PIC usb-uhci, usb-uhci, eth0,
radeon@PCI:1:0:0
11: 2 XT-PIC i82365, wvlan_cs
12: 255 XT-PIC PS/2 Mouse
14: 3752 XT-PIC ide0
15: 7 XT-PIC ide1
NMI: 0
ERR: 0

On Mon, 08 Sep 2003 15:55:42 -0700, Michael Smith typed:

> I tried wvlan_cs from pcmcia-cs 3.2.4 with kernel 2.4.22 and am still
> having problems. The driver loads, but seems to have a problem
> interfacing with the hardware.
>
> The dmesg output looks like the following:
>
> cs: memory probe 0xa0000000-0xa0ffffff: clean. wvlan_cs: WaveLAN/IEEE
> PCMCIA driver v1.0.6 wvlan_cs: (c) Andreas Neuhaus
> <(E-Mail Removed)> cs: IO port probe 0x0100-0x04ff: excluding
> 0x378-0x37f 0x3c0-0x3df 0x4d0-0x4d7
> cs: IO port probe 0x0380-0x03bf: clean. cs: IO port probe 0x03e0-0x04cf:
> clean. cs: IO port probe 0x04d8-0x04ff: clean. cs: IO port probe
> 0x0a00-0x0aff: clean. cs: IO port probe 0x0c00-0x0cff: clean. wvlan_cs:
> index 0x01: Vcc 3.3, irq 11, io 0x0100-0x013f wvlan_cs: Registered
> netdevice eth1
> wvlan_cs: MAC address on eth1 is 00 00 00 00 00 00 wvlan_cs: Found
> firmware 0x0 (vendor 0) - Firmware capabilities : 0-0-0-0-0 wvlan_cs:
> Initialization failed!
>
> Clearly, the firmware capabilities and MAC address look suspicious.

Agreed, what I'm seeing;

Sep 8 16:05:24 LAPTOP1700 cardmgr[2605]: socket 0: Lucent Technologies
WaveLAN/IEEE Adapter Sep 8 16:05:24 LAPTOP1700 kernel: cs: IO port probe
0x0100-0x04ff: excluding 0x378-0x37f 0x4d0-0x4d7 Sep 8 16:05:24
LAPTOP1700 kernel: cs: IO port probe 0x0380-0x04cf: clean. Sep 8 16:05:24
LAPTOP1700 kernel: cs: IO port probe 0x04d8-0x04ff: clean. Sep 8 16:05:24
LAPTOP1700 kernel: cs: IO port probe 0x0800-0x08ff: clean. Sep 8 16:05:24
LAPTOP1700 kernel: cs: IO port probe 0x0a00-0x0aff: clean. Sep 8 16:05:24
LAPTOP1700 kernel: cs: IO port probe 0x0c00-0x0cff: clean. Sep 8 16:05:24
LAPTOP1700 kernel: wvlan_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f
Sep 8 16:05:24 LAPTOP1700 kernel: wvlan_cs: Registered netdevice eth1 Sep
8 16:05:24 LAPTOP1700 kernel: wvlan_cs: MAC address on eth1 is 00 02 2d
01 1d 6b Sep 8 16:05:24 LAPTOP1700 kernel: wvlan_cs: Found firmware
0x60004 (vendor 1) - Firmware capabilities : 1-0-1-1-1



> I have tried excluding the io range it chooses (in
> /etc/pcmcia/config.opts), but that didn't make a difference.

Hmmm..... in /etc/pcmcia try commenting out the two lines that exclude
irq's 3 and 4;

# First built-in serial port
# exclude irq 4
# Second built-in serial port
# exclude irq 3



> iwconfig will execute, but the card settings never change.
>
> Google searches suggest that the dmesg output means the card isn't
> supported by the driver, and often the advice is to use orinico_cs - but
> that's where I started.
>
> Still looking for a magic bullet.
>
>
> For reference /proc/interrupts shows the following:
>
> CPU0
> 0: 29058 XT-PIC timer
> 1: 564 XT-PIC keyboard 2: 0 XT-PIC
> cascade 5: 0 XT-PIC ehci_hcd 8: 2 XT-PIC
> rtc
> 9: 5 XT-PIC acpi, usb-uhci, i82365
> 10: 18368 XT-PIC usb-uhci, usb-uhci, eth0,
> radeon@PCI:1:0:0
> 11: 2 XT-PIC i82365, wvlan_cs 12: 255 XT-PIC
> PS/2 Mouse 14: 3752 XT-PIC ide0 15: 7 XT-PIC
> ide1
> NMI: 0
> ERR: 0


Hmmm..... I've got acpi enabled with kernel-2.4.23pre2;

$ cat /proc/interrupts
CPU0
0: 2180057 IO-APIC-edge timer
1: 2486 IO-APIC-edge keyboard 2: 0 XT-PIC
cascade 3: 90466 IO-APIC-edge wvlan_cs 8: 1
IO-APIC-edge rtc
9: 5 IO-APIC-level acpi
12: 80220 IO-APIC-edge PS/2 Mouse 14: 18038 IO-APIC-edge
ide0
15: 6 IO-APIC-edge ide1
16: 0 IO-APIC-level usb-uhci 17: 96 IO-APIC-level
Intel ICH4 18: 0 IO-APIC-level usb-uhci 19: 0
IO-APIC-level usb-uhci
NMI: 0
LOC: 2180138
ERR: 0
MIS: 0


--
If it's Thursday it must be Micro$oft patching day!!!

See if you have the newest version of the orinoco driver. I know it
had some big issues a few minor versions back.

http://ozlabs.org/people/dgibson/dldwd/

Only suggestion I have, sorry.

(E-Mail Removed) (Michael Smith) wrote in message news:<(E-Mail Removed). com>...
> Lenard <lenard@127.0.0.1> wrote in message news:<pan.2003.09.07.15.37.49.839786@127.0.0.1>...
>
> > I use this very same card. All you need to do is edit the
> > /etc/pcmcia/config file;
> >
> > card "Lucent Technologies WaveLAN/IEEE Adapter"
> > version "Lucent Technologies", "WaveLAN/IEEE" bind "wvlan_cs"
>
> I tried wvlan_cs from pcmcia-cs 3.2.4 with kernel 2.4.22 and am still
> having problems. The driver loads, but seems to have a problem
> interfacing with the hardware.
>
> The dmesg output looks like the following:
>
> cs: memory probe 0xa0000000-0xa0ffffff: clean.
> wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.6
> wvlan_cs: (c) Andreas Neuhaus <(E-Mail Removed)>
> cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x3c0-0x3df
> 0x4d0-0x4d7
> cs: IO port probe 0x0380-0x03bf: clean.
> cs: IO port probe 0x03e0-0x04cf: clean.
> cs: IO port probe 0x04d8-0x04ff: clean.
> cs: IO port probe 0x0a00-0x0aff: clean.
> cs: IO port probe 0x0c00-0x0cff: clean.
> wvlan_cs: index 0x01: Vcc 3.3, irq 11, io 0x0100-0x013f
> wvlan_cs: Registered netdevice eth1
> wvlan_cs: MAC address on eth1 is 00 00 00 00 00 00
> wvlan_cs: Found firmware 0x0 (vendor 0) - Firmware capabilities :
> 0-0-0-0-0
> wvlan_cs: Initialization failed!
>
> Clearly, the firmware capabilities and MAC address look suspicious.
>
> I have tried excluding the io range it chooses (in
> /etc/pcmcia/config.opts), but that didn't make a difference.
>
> iwconfig will execute, but the card settings never change.
>
> Google searches suggest that the dmesg output means the card isn't
> supported by the driver, and often the advice is to use orinico_cs -
> but that's where I started.
>
> Still looking for a magic bullet.
>
>
> For reference /proc/interrupts shows the following:
>
> CPU0
> 0: 29058 XT-PIC timer
> 1: 564 XT-PIC keyboard
> 2: 0 XT-PIC cascade
> 5: 0 XT-PIC ehci_hcd
> 8: 2 XT-PIC rtc
> 9: 5 XT-PIC acpi, usb-uhci, i82365
> 10: 18368 XT-PIC usb-uhci, usb-uhci, eth0,
> radeon@PCI:1:0:0
> 11: 2 XT-PIC i82365, wvlan_cs
> 12: 255 XT-PIC PS/2 Mouse
> 14: 3752 XT-PIC ide0
> 15: 7 XT-PIC ide1
> NMI: 0
> ERR: 0

Lenard <lenard@127.0.0.1> wrote in message news:<pan.2003.09.09.03.16.52.546694@127.0.0.1>...

> Hmmm..... in /etc/pcmcia try commenting out the two lines that exclude
> irq's 3 and 4;
>
> # First built-in serial port
> # exclude irq 4
> # Second built-in serial port
> # exclude irq 3

I have tried commenting out those lines and adding include lines, but
no matter what i82365 and wvlan_cs stay off of irq 3 and 4. IRQ
assignments did move when I tried messing with kernel acpi settings.
Specifically, I tried both pci=noacpi and acpi=off (independent of one
another). Those changes did not help with the wireless module.

I don't know enough about interrupt handling to know if there is any
problem with the ways things are, I just included the /proc/interrupts
data in a previous post hoping someone else could comment. My gut
feeling is that's probably not the problem, but I'd love it if someone
could (1) tell me it is and (2) tell me how to fix it.


I notice this when PCMCIA loads...

PCI: Enabling device 02:01.0 (0000 -> 0002)
PCI: Enabling device 02:01.1 (0000 -> 0002)
Unknown [1217 7113] rev 20 PCI-to-CardBus at slot 02:01, mem
0x10001000
host opts [0]: [pci irq 9] [lat 32/32] [bus 3/6]
host opts [1]: [pci irq 9] [lat 32/32] [bus 7/10]
ISA irqs (default) = 3,4,7,12 PCI status changes
TI 1410 rev 01 PCI-to-CardBus at slot 02:03, mem 0x10003000
host opts [0]: [pci only] [pci irq 11] [lat 32/176] [bus 11/14]
PCI card interrupts, PCI status changes

Is that saying anything surprising or troubling?

(E-Mail Removed) (Phil) wrote in message news:<(E-Mail Removed). com>...
> See if you have the newest version of the orinoco driver. I know it
> had some big issues a few minor versions back.
>
> http://ozlabs.org/people/dgibson/dldwd/
>
> Only suggestion I have, sorry.

Good suggestion. I had been using the version included in the gentoo
pcmcia-cs ebuild. That was orinoco 0.13b. I updated to orinoco 0.13e
(the current release) after your suggestion.

Unfortunately, it didn't resolve the problem.

On Tue, 09 Sep 2003 21:10:49 -0700, Michael Smith typed:

> I have tried commenting out those lines and adding include lines, but no
> matter what i82365 and wvlan_cs stay off of irq 3 and 4. IRQ
> assignments did move when I tried messing with kernel acpi settings.
> Specifically, I tried both pci=noacpi and acpi=off (independent of one
> another). Those changes did not help with the wireless module.
>
> I don't know enough about interrupt handling to know if there is any
> problem with the ways things are, I just included the /proc/interrupts
> data in a previous post hoping someone else could comment. My gut
> feeling is that's probably not the problem, but I'd love it if someone
> could (1) tell me it is and (2) tell me how to fix it.

I did not see in your posted /proc/interrupts any acpi interrupts being
used. Review the output of /proc/interupts that I posted in my earlier
replay.

During the configuration portion of the getting a compiled kernel I made
the following changes in the General Setup Section;

make config / menuconfig / xconfig

PCMCIA/CardBus support - n

Advanced Power Management BIOS Support - n

ACPI Support Section;
ACPI Support - y
CPU Enumeration Only - n
ASUS Laptop Laptop Extras - n
Toshiba Laptop Extras - n
Debug Statements - n
All other settings in this section set to yes

With your Dell laptop you might want to set;

Processor type and features

Dell laptop support - y

When done and booted with the newly compiled kernel build pcmcia modules
from the pcmcia-cs-3.2.4 source.


--
If it's Thursday it must be Micro$oft patching day!!!