Hi,

I have trouble with the Linksys WPC11 wireless card and the orinoco driver. It runs fine for a while, gives good speed, but when I apply load it quits on me. iwconfig comes back empty, and my logs show this:

Dec 11 14:49:10 cyburgosl kernel: hermes @ IO 0x100: Error -16 issuing command.
Dec 11 14:49:10 cyburgosl kernel: hermes @ IO 0x100: Error -16 issuing command.
Dec 11 14:49:10 cyburgosl kernel: eth1: Error -110 writing Tx descriptor to BAP
Dec 11 14:49:12 cyburgosl last message repeated 1543 times


Dec 11 16:03:00 cyburgosl kernel: eth1: Error -110 writing Tx descriptor to BAP
Dec 11 16:03:31 cyburgosl last message repeated 23125 times
Dec 11 16:04:01 cyburgosl last message repeated 21247 times

I saw one mention of this error in another thread , but no solutions.

I can reset the card by issueing /etc/init.d/network restart, but it is very annoying.


I have the following setup:

no-name laptop running Mandrake 9, kernel 2.4.19 (tried 2.4.20), orinoco driver 11 (stock mandrake), tried the latest orinoco 13beta driver as well.
I had a hard time getting the wlan-ng drivers to work, and I could not get WEP to work with those drivers, so I would like to stick with the orinoco drivers. They make installation a breeze.

More info:

Dec 11 08:50:27 cyburgosl kernel: Linux Kernel Card Services Kernel Version
Dec 11 08:50:27 cyburgosl kernel: options: [pci] [cardbus] [pm]
Dec 11 08:50:27 cyburgosl kernel: Yenta IRQ list 0098, PCI irq11
Dec 11 08:50:27 cyburgosl kernel: Socket status: 30000010
Dec 11 08:50:27 cyburgosl kernel: cs: IO port probe 0x0c00-0x0cff: clean.
Dec 11 08:50:27 cyburgosl kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x3
78-0x37f 0x480-0x48f 0x4d0-0x4d7
Dec 11 08:50:27 cyburgosl kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Dec 11 08:50:27 cyburgosl kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
Dec 11 08:50:27 cyburgosl kernel: eth1: Channel out of range (0)!
Dec 11 08:50:27 cyburgosl kernel: eth1: Channel out of range (0)!
Dec 11 08:50:28 cyburgosl kernel: eth1: Error -5 setting multicast list.

root:/var/log$ cardctl ident
Socket 0:
product info: "The Linksys Group, Inc.", "Instant Wireless Network PC Card", "ISL37300P", "RevA"
manfid: 0x0274, 0x1613
function: 6 (network)

I have the feeling it is somehow firmware related - googling around for similar problems mentions firmware a lot. I have checked, however, and the card seems to have the latest firmware.

Any clues much appreciated

Thanks,

Erik

Previous thread is the exact same problem that i am having. I see alot of threads for this problem but no answers to fix it. Can anyone point me in the right direction to a fix?

using mandrake 9.0 with wpc11....

Hi,

In the meantime I think I have found the root cause of the problem, but unfortunately not the solution. According to this site (info in Dutch), Linksys have changed the chipset from Intersil PrismII to Broadcom in the latest version of their cards. And I think the PCI cards and the PC cards have the same chipset. I can recall seeing a mention of Broadcom when I tried to get the damn thing to work under Redhat as well.

AFAIK there are no Linux drivers for the Broadcom chipset yet, so it looks like we're stuck with a dud for now...

The issue is that the orinoco modules really don't cover the WPC11 v.3 too well, if they had broadcoms, the modules won't even load.

Lately I've seen a lot of people get much more mileage out of the newer orinoco modules, 2.4.18+19+20 shipped with .11b, .13-beta seems to work fine.

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

Although I just helped one guy who was still getting the same BAP errors, but seems to be doing fine with the host_ap modules:

http://hostap.epitest.fi/

Which work like gangbusters for most people, in any mode, I've used all three.

Orinoco will compile with a simple make, the host_ap is a little more complicated, but not really, and nothing near the mess that the wlan-ng modules are.

Cheers,

Finegan

Hi Finegan,

I tried the latest orinoco modules (orinoco-0.13beta1) with the 1.4.20 kernels, and they still give me trouble. I will test the host_ap modules, see how they behave.

Cheers,

Erik