Re: WG511 mgmt response timeout problem
Andy Boff <[email protected]>
| Newsgroups | gmane.linux.drivers.prism54.user |
|---|---|
| Organization | University Of York |
| Message-ID | <[email protected]> |
On Saturday 03 July 2004 18:06, Richard Atterer wrote: > Have you tried all the different firmware versions? Preferably, search > through your Windows installation for the right .arm file. Using the latest cvs (03/07/2004), and the firmware from the Windows install, I get... Jul 3 23:20:49 eriador Loaded prism54 driver, version 1.2 Jul 3 23:20:49 eriador PCI: Enabling device 0000:02:00.0 (0000 -> 0002) Jul 3 23:20:49 eriador eth1: prism54 driver detected card model: Netgear WG511 Jul 3 23:20:49 eriador net.agent[11143]: add event not handled Jul 3 23:20:51 eriador eth1: islpci_open() Jul 3 23:20:51 eriador eth1: resetting device... Jul 3 23:20:51 eriador eth1: uploading firmware... Jul 3 23:20:51 eriador eth1: firmware uploaded done, now triggering reset... Jul 3 23:20:51 eriador eth1: expecting oid 0xff020003, received 0x2008c06. Jul 3 23:20:53 eriador eth1: timeout waiting for mgmt response Jul 3 23:20:53 eriador eth1: errant PIMFOR application frame Jul 3 23:20:53 eriador eth1: timeout waiting for mgmt response 1000, triggering device Jul 3 23:20:54 eriador eth1: timeout waiting for mgmt response Jul 3 23:20:54 eriador eth1: expecting oid 0x12000002, received 0x10000002. Jul 3 23:20:55 eriador eth1: timeout waiting for mgmt response Jul 3 23:20:55 eriador eth1: expecting oid 0x12000007, received 0x0. Jul 3 23:20:56 eriador eth1: timeout waiting for mgmt response Jul 3 23:20:56 eriador eth1: expecting oid 0xff02000f, received 0x12000007. Jul 3 23:20:57 eriador eth1: timeout waiting for mgmt response Jul 3 23:20:57 eriador eth1: Out of memory, cannot handle oid 0x00000000 Jul 3 23:20:57 eriador eth1: timeout waiting for mgmt response 1000, triggering device Jul 3 23:20:58 eriador eth1: timeout waiting for mgmt response Jul 3 23:20:58 eriador eth1: mgt_commit has failed. Restart the device Jul 3 23:20:59 eriador eth1: expecting oid 0xff020003, received 0x0. Jul 3 23:21:00 eriador eth1: timeout waiting for mgmt response Jul 3 23:21:00 eriador eth1: errant PIMFOR application frame Jul 3 23:21:01 eriador eth1: timeout waiting for mgmt response 1000, triggering device Jul 3 23:21:02 eriador eth1: timeout waiting for mgmt response Jul 3 23:21:02 eriador eth1: expecting oid 0x12000002, received 0x10000002. Jul 3 23:21:03 eriador eth1: timeout waiting for mgmt response Jul 3 23:21:03 eriador eth1: expecting oid 0x12000007, received 0x12000002. Jul 3 23:21:04 eriador eth1: timeout waiting for mgmt response Jul 3 23:21:04 eriador eth1: expecting oid 0xff02000f, received 0x12000007. Jul 3 23:21:05 eriador eth1: timeout waiting for mgmt response Jul 3 23:21:05 eriador eth1: mgt_commit has failed. Restart the device Jul 3 23:21:05 eriador eth1: expecting oid 0x12000003, received 0x0. Jul 3 23:21:06 eriador eth1: timeout waiting for mgmt response Jul 3 23:21:06 eriador eth1: expecting oid 0x12000002, received 0x4000000. Jul 3 23:21:07 eriador eth1: timeout waiting for mgmt response Any more ideas? I'm stumped. I don't know why the card isn't returning what the driver expects, but looking at it, I would have expected a lot of the oids to line up if the 0x0 was ignored or discarded. Andy