Hi all,

I need help on getting my Orinoco Gold Card to work.

Recently, I switched from a WaveLan Silver Card to an Orinoco Gold Card for my wireless connection at work. The WaveLan was working okay though it was kind of flaky sometimes with connections being dropped. After switching to the Gold Card, I have more problems. For some reason, after a session of using the Gold Card successfully, I cannot get the PCMCIA device to free up its resource at the end of the day when I shutdown. When I reboot the next time, my machine would hang at the following message:

pcmcia: Yenta IRQ list 0a98, PCI irq10
Socket status: 30000007

In order to fix this problem, I would have to turn the machine off, and restart the boot in the Interactive mode, which allows me to specify to not start the PCMCIA service. Once I log in, I did the following as root:

/etc/init.d/pcmcia stop

The command would hang and then eventually output the following message to the console:

Shutting down PCMCIA services: cardmgr modulesds: Device or resource busy
yenta_socket: Device or resource busy
pcmcia_core: Device or resource busy

Eventually after a few (interactive) reboots, and perhaps using wired connection (via eth0) during my subsequent sessions, I would be able to get past the PCMCIA problem and start up the PCMCIA service.

Inserting the Gold Card at this point into my eth1 slot would work. But when I shutdown, the same problem/cycle would occur.

So, what do I have to do to get the Gold Card to work properly on my machine? I have read somewhere in the forum that I need to remake the kernel and module in order to get the Orinoco Card to work. Someone else suggests tweaking the kernel config files.

Either way, I have no idea what the proper steps I need to take to fix the problem. Can someone please help by telling me (in detail instructions) what I need to do? If the reply is too long, could you please reply by sending me an email at mli@fgm.com?

I much appreciate any help I can get to solve this problem.

Thanks in advance.

This sounds like an older firmware bug, or too old of a driver:

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

What version of the driver are you running, and what firmware, both are reported on module load in dmesg and splattered all accross /var/log/blah.

Cheers,

Finegan

Hi, thank you for your help. This is what was logged in dmesg

Linux Kernel Card Services 3.1.22
options: [pci] [cardbus] [pm]
PCI: Found IRQ 10 for device 02:04.0
PCI: Sharing IRQ 10 with 00:1d.0
PCI: Sharing IRQ 10 with 01:00.0
Yenta IRQ list 0a98, PCI irq10
Socket status: 30000411
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.
hermes.c: 5 Apr 2002 David Gibson <hermes@gibson.dropbear.id.au>
orinoco.c 0.11b (David Gibson <hermes@gibson.dropbear.id.au> and others)
orinoco_cs.c 0.11b (David Gibson <hermes@gibson.dropbear.id.au> and others)
divert: allocating divert_blk for eth1
eth1: Station identity 001f:0001:0008:0048
eth1: Looks like a Lucent/Agere firmware version 8.72
eth1: Ad-hoc demo mode supported
eth1: IEEE standard IBSS ad-hoc mode supported
eth1: WEP supported, 104-bit key
eth1: MAC address 00:02:2D:A5:CBF
eth1: Station name "HERMES I"
eth1: ready
eth1: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f

Thanks so much.

Dude, you're running the brand new firmware and a new enough version of the driver so its not any of the common bugs I come accross on day to day... You might want to check through the mailing list for the orinoco driver over at sourceforge, and if there's no similiar problems, subscribe and post the problem there, you'll probably get a reply from David Gibson about it within a day or so, its a nice low-volume list.

Cheers,

Finegan