[Prism54-users] WG511 mgmt response timeout problem

[Andy Boff]

Hi,

I've been trying to get my Netgear WG511 working under linux. The card works 
fine under WinXP Home. I've tried drivers 1.1, 1.2, cvs20040701 and 
cvs20040702 (both downloaded using the cvs-latest link). All were compiled 
from the tarball, rather than patching the kernel. The stock 2.6.6 kernel 
driver also appears to have the same problem.

When I plug the card in, I get the following:

Jul  2 23:03:37 eriador Loaded prism54 driver, version 1.2
Jul  2 23:03:37 eriador PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
Jul  2 23:03:37 eriador eth1: prism54 driver detected card model: Netgear 
WG511
Jul  2 23:03:38 eriador net.agent[10982]: add event not handled
Jul  2 23:03:40 eriador eth1: islpci_open()
Jul  2 23:03:40 eriador eth1: resetting device...
Jul  2 23:03:40 eriador eth1: uploading firmware...
Jul  2 23:03:40 eriador eth1: firmware uploaded done, now triggering reset...
Jul  2 23:03:40 eriador eth1: expecting oid 0xff020003, received 0x2009806.
Jul  2 23:03:41 eriador eth1: timeout waiting for mgmt response
Jul  2 23:03:41 eriador eth1: expecting oid 0x10000002, received 0x0.
Jul  2 23:03:42 eriador eth1: timeout waiting for mgmt response
Jul  2 23:03:42 eriador eth1: expecting oid 0x12000002, received 0x10000002.
Jul  2 23:03:43 eriador eth1: timeout waiting for mgmt response
Jul  2 23:03:43 eriador eth1: expecting oid 0x12000007, received 0x38300000.
Jul  2 23:03:44 eriador eth1: timeout waiting for mgmt response
Jul  2 23:03:44 eriador eth1: expecting oid 0xff02000f, received 0x12000007.
Jul  2 23:03:46 eriador eth1: timeout waiting for mgmt response
Jul  2 23:03:46 eriador eth1: expecting oid 0xff020003, received 0xff02000f.
Jul  2 23:03:47 eriador eth1: timeout waiting for mgmt response
Jul  2 23:03:47 eriador eth1: mgt_commit has failed. Restart the device
Jul  2 23:03:48 eriador eth1: errant PIMFOR application frame
Jul  2 23:03:48 eriador eth1: timeout waiting for mgmt response 1000, 
triggering device
Jul  2 23:03:49 eriador eth1: timeout waiting for mgmt response
Jul  2 23:03:49 eriador eth1: expecting oid 0x10000002, received 0x19000001.
Jul  2 23:03:50 eriador eth1: timeout waiting for mgmt response
Jul  2 23:03:50 eriador eth1: expecting oid 0x12000002, received 0x59c90010.
Jul  2 23:03:51 eriador eth1: timeout waiting for mgmt response
Jul  2 23:03:51 eriador eth1: expecting oid 0x12000007, received 0x12000002.
Jul  2 23:03:52 eriador eth1: timeout waiting for mgmt response
Jul  2 23:03:52 eriador eth1: expecting oid 0xff02000f, received 0x12000007.
Jul  2 23:03:53 eriador eth1: timeout waiting for mgmt response
Jul  2 23:03:53 eriador eth1: mgt_commit has failed. Restart the device
Jul  2 23:03:53 eriador eth1: expecting oid 0x12000003, received 0x0.
Jul  2 23:03:55 eriador eth1: timeout waiting for mgmt response
Jul  2 23:03:55 eriador eth1: no PIMFOR header found
Jul  2 23:03:55 eriador eth1: timeout waiting for mgmt response 1000, 
triggering device
Jul  2 23:03:56 eriador eth1: timeout waiting for mgmt response
Jul  2 23:03:56 eriador eth1: Out of memory, cannot handle oid 0x75746572
Jul  2 23:03:56 eriador eth1: timeout waiting for mgmt response 1000, 
triggering device
Jul  2 23:03:57 eriador eth1: timeout waiting for mgmt response

Looking at the messages, it looks like the messages are out of sync. I'm 
guessing for whatever reason, the driver has detected a null (0x0) at 
23:03:41, and that's put the rest of the oids out of sync. I'm then guessing 
that the reason for the mgmt timeout is because of the oids being out of 
sync.

Other system info: Gentoo Linux, running kernel 2.6.6, love sources patchset 
(based on the mm patches). If you need any more information, I should be able 
to pass it on. Laptop is an Acer Aspire 1350. I've seen some forum posts 
suggest using the acerhk driver. I'm using the latest version of that driver, 
but I'm not clear how that would affect this card, given the WG511 is a 
PCMCIA card.

Anybody got any ideas why this is happening? When I get a connection up, it 
sustains for about 5 minutes, and then I start to get destination host 
unreachable errors. Most of the time it takes 10 or so inserts and ejects of 
the card to get it to connect. With Windows, the connection comes up first 
time, and the connection is sustained, with a 100% reported signal strength 
(it's right next to the AP).

I'd be grateful if anyone can help me out. I've not been able to find anything 
that's got it working yet.