Having problems getting prism2_pci module to load:

/lib/modules/2.4.19/net/prism2_pci.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.4.19/net/prism2_pci.o: insmod /lib/modules/2.4.19/net/prism2_pci.o failed
/lib/modules/2.4.19/net/prism2_pci.o: insmod prism2_pci failed

Card & drivers installed OK on WinXP (but firmware update wouldn't start so I don't know which version).

Tried with linux-wlan-ng 0.1.14 & 0.1.15-pre7 - all with the same result.

lspci -v gives:

00:0c.0 Network controller: BROADCOM Corporation: Unknown device 4301 (rev 01)
Subsystem: Unknown device 1737:4301
Flags: bus master, fast devsel, latency 64, IRQ 5
Memory at f4000000 (32-bit, non-prefetchable) [size=8K]
Capabilities: [40] Power Management version 2

Shouldn't this say Intersil? Have linksys changed the chipset?

I'm having the same problem. I surely would hate to find out that the chipset has been changed and Linksys didn't bother to tell anyone.l

I think that is indeed the case, the lspci from a WMP11 prism based card will have "Intersil" plastered accross it somewhere. I don't know anything about the broadcom chipset, Jean's page might.

Cheers,

Finegan

Bad news confirmed. Here are the pictures:

http://intimate.handhelds.org/jacques/wmp11v2.7/

Keith

Go figure, the only thing that comes up in www.google.com/linux when plugging in "wmp11 broadcom" or "wmp11 v2.7" is this thread.

Great... Nothing obn Jean's page about this chipset at all...

Cheers,

Finegan

Terrific. Linksys's web site still claims the linux-wlan driver works:

http://www.linksys.com/download/driver.asp?dlid=57

I believe it's going into the linux-wlan-ng FAQ - people should see it there.

Too late for me - my supplier is being very unsympathetic about any return.

Keith

I've ran into the same problem with the broadcom chipset wmp11 v2.7 and called linksys and they said they were working on a driver for it. So who knows how long that will take. If anyone has any work arounds for it I would love to hear them.

I have the WMP11 in my router running like clockwork, however I did not do the install my buddy did and he has no idea how he got it working. I installed RH7.3 on my wife's machie and when to get the wireless working (on another WMP11) and I get it working but I'm getting alot of bad data back on pings and web sites stall when I try to load them.

I had to tweak alot to get this far, I'm thinking I'm very tired and just missing something. I'll keep you all posted when it get it working what to do to make it work.

Anyone know if it's possible to use Linux to push a firmware update onto one of these cards?
I have a couple of these (prism2 version) installed with firmware 1.4.2 and I'm told I should update to at least 1.4.9 to make them work reliably with HOSTAP.
But I don't have a Windows box. Any suggestions?
Thanks!

I've got an ancient WPC11 v.1 with the very old firmware, 0.81 ish (the numbering chema is different for the PCMCIA card though), in a PLX adapter running fine with the host_ap modules. I'de test it first before trying to flash the firmware under linux. Under windows its safe... well as safe as anything under windows, but the only firmware dropper I know of for these cards under Linux comes with... or is somehow part of, I don't know if its still in the source pack, with the wlan-ng project's prism2_X modules.

Remember a lot of the FUD out there could just be someone not knowing how to set up their WLAN properly. If you can't get throughput of at least 200K/sec through the air, then yeah, then there's probably something kinking it up.

Cheers,

Finegan

Thanks for the info. I'm actually using hostap instead of wlan-ng (the primary reason for this is that for my card the former can be readily added to a stock Mandrake kernel and the latter can't).
The problems I'm having have to do with startup. When the init scripts fire up the card, it seems to come up in a bad state. I can usually make it work by executing some set of iwconfig commands, but doing them in the init script right after starting hostap_pci doesn't work reliably. Typically, I fail to get a connection to the AP or something like that.
But once I get the card up, it works like a champ.
I have heard the same concern about flashing the firmware. In fact, as far as I can tell, the tool for doing that, prism2dl, has been removed from the linux-ng distribution.
While it's easy to get a PCMCIA card flashed by a buddy with a Windows box, it's a lot harder to do that for a PCI card. :-(
Here's the sort of stuff that dmesg shows me:
hostap_crypt: registered algorithm 'NULL'
hostap_pci: hostap_pci.c 0.0.0 2002-10-12 (SSH Communications Security Corp, Jouni Malinen)
hostap_pci: (c) Jouni Malinen <jkmaline@cc.hut.fi>
PCI: Found IRQ 10 for device 00:0b.0
hostap_pci: Registered netdevice wlan0
prism2_hw_init()
prism2_hw_config: initialized in 18512 iterations
wlan0: hfa384x_get_rid - RID len mismatch: rid=0xfd0b, len=10 (expected 8)
Could not get RID for component NIC
wlan0: PRI: id=0x15 v1.1.0
wlan0: STA: id=0x1f v1.4.2
wlan0: defaulting to host-based encryption as a workaround for firmware bug in Host AP mode WEP
wlan0: Warning: secondary station firmware version 1.4.2 does not seem to work in Host AP mode
wlan0: hfa384x_cmd: entry still in list? (entry=d6bb0ae0, type=0, res=0)
wlan0: hfa384x_cmd: command was not completed (res=0, entry=d6bb0ae0, type=0, cmd=0x0002, param0=0x0000)
wlan0: MAC port 0 reseting failed
hostap_pci: hardware initialization failed
hostap_pci: Netdevice wlan0 unregistered
hostap_pci: No devices found, driver not installed.
hostap_crypt: unregistered algorithm 'NULL' (deinit)
hostap_crypt: registered algorithm 'NULL'
hostap_pci: hostap_pci.c 0.0.0 2002-10-12 (SSH Communications Security Corp, Jouni Malinen)
hostap_pci: (c) Jouni Malinen <jkmaline@cc.hut.fi>
PCI: Found IRQ 10 for device 00:0b.0
hostap_pci: Registered netdevice wlan0
prism2_hw_init()
prism2_hw_config: initialized in 18515 iterations
wlan0: NIC: id=0x8013 v1.0.0
wlan0: PRI: id=0x15 v1.1.0
wlan0: STA: id=0x1f v1.4.2
wlan0: hfa384x_get_rid - RID len mismatch: rid=0xfdc1, len=8 (expected 2)
wlan0: defaulting to host-based encryption as a workaround for firmware bug in Host AP mode WEP
wlan0: Warning: secondary station firmware version 1.4.2 does not seem to work in Host AP mode
wlan0: hfa384x_get_rid - RID len mismatch: rid=0xfc06, len=6 (expected 2)
wlan0: hfa384x_get_rid - RID len mismatch: rid=0xfd42, len=8 (expected 6)
wlan0: hfa384x_cmd: entry still in list? (entry=d6bb0ae0, type=0, res=0)
wlan0: hfa384x_cmd: command was not completed (res=0, entry=d6bb0ae0, type=0, cmd=0x0002, param0=0x0000)
wlan0: MAC port 0 reseting failed
hostap_pci: hardware initialization failed
hostap_pci: Netdevice wlan0 unregistered
hostap_pci: No devices found, driver not installed.
hostap_crypt: unregistered algorithm 'NULL' (deinit)
hostap_crypt: registered algorithm 'NULL'
hostap_pci: hostap_pci.c 0.0.0 2002-10-12 (SSH Communications Security Corp, Jouni Malinen)
hostap_pci: (c) Jouni Malinen <jkmaline@cc.hut.fi>
PCI: Found IRQ 10 for device 00:0b.0
hostap_pci: Registered netdevice wlan0
prism2_hw_init()
prism2_hw_config: initialized in 18517 iterations
wlan0: hfa384x_get_rid - RID len mismatch: rid=0xfd0b, len=10 (expected 8)
Could not get RID for component NIC
wlan0: PRI: id=0x15 v1.1.0
wlan0: hfa384x_get_rid - RID len mismatch: rid=0xfdc1, len=8 (expected 2)
wlan0: STA: id=0x1f v1.4.2
wlan0: hfa384x_get_rid - RID len mismatch: rid=0xfc06, len=8 (expected 2)
wlan0: defaulting to host-based encryption as a workaround for firmware bug in Host AP mode WEP
wlan0: Warning: secondary station firmware version 1.4.2 does not seem to work in Host AP mode
wlan0: hfa384x_get_rid - RID len mismatch: rid=0xfc84, len=36 (expected 2)
wlan0: hfa384x_get_rid - RID len mismatch: rid=0xfc09, len=4 (expected 2)
wlan0: LinkStatus=2 (Disconnected)
wlan0: Intersil Prism2.5 PCI: mem=0xe3000000, irq=10
prism2: wlan0: operating mode changed 3 -> 2
wlan0: LinkStatus=2 (Disconnected)


Note the complaint about the firmware. Not sure about that hostap mode, since I'm not trying to use it in AP mode. But it's a later iwconfig command that switches to Managed mode.
Cheers,
R

The fine folks at broadcom claim linux support for their wireless chipset here: http://www.broadcom.com/products/94306.html

Of course theres no information on where to get said drivers.

Although I know it's bad form to respond to one's own posting, I thought it might help others to know how I solved my problem.

answer: for the wmp11, the orinoco driver distributed with Mandrake (and probably Red Hat, too), works fine.

Cheers,
R

What version of Mandrake are you using? What kernel version? are you using pcmcia-cs? Are you sure your wmp11 is broadcom based?

I really need to get this card working on linux...

Thanks!