Re: Netgear WG511 problems

> > I've spent about 6 hours today on this (so far), so as you can imagine
> > I'm not very happy right now.
> > I bought this card because it seemed to be extremely well supported
> > under Linux, so I wasn't 
> > anticipating any trouble. However, the only way I can get it to work is
> > using Linuxants DriverLoader
> > and the Windows driver. 
> > 
> > What I've done so far:
> > - configured the kernel according to the README on prism54.org
> > - loaded the necessary modules (also tried compiling everything in)
> > - tried configuring interface with scripts and manually with iwconfig
> > - tried a couple of different kernel versions (2.6.8.1-ck3 and vanilla
> > 2.6.7)
> > - various suggestions found on Google
> > 
> > I'm not getting anywhere at all, so hopefully someone can tell me what's
> > happening. The following
> > is my dmesg output, starting with the card being removed and inserted.
> > It appears to load the firmware 
> > correctly at least, but after that I have no idea what it's doing:
> > 
> > Assuming someone else called the IRQ
> > eth1: hot unplug detected
> > eth1: removing device
> > eth1: islpci_close ()
> > PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
> > eth1: prism54 driver detected card model: Netgear WG511
> > eth1: islpci_open()
> > eth1: resetting device...
> > eth1: uploading firmware...
> > eth1: firmware uploaded done, now triggering reset...
> > eth1: device soft reset timed out
> > eth1: timeout waiting for mgmt response 1000, trigging device
> > eth1: timeout waiting for mgmt response
> > eth1: timeout waiting for mgmt response 1000, trigging device
> > eth1: timeout waiting for mgmt response
> > eth1: timeout waiting for mgmt response 1000, trigging device
> > eth1: timeout waiting for mgmt response
> > eth1: timeout waiting for mgmt response 1000, trigging device
> > eth1: timeout waiting for mgmt response
> > eth1: mgmt tx queue is still full
> > ........
> > eth1: mgmt tx queue is still full
> > eth1: mgmt tx queue is still full
> > eth1: mgmt tx queue is still full
> > eth1: mgmt tx queue is still full
> > eth1: mgmt tx queue is still full
> > eth1: mgmt tx queue is still full
> > eth1: mgmt tx queue is still full
> > eth1: mgmt tx queue is still full
> > eth1: mgmt tx queue is still full
> > eth1: mgmt tx queue is still full
> > eth1: mgt_commit has failed. Restart the device 
> > eth1: mgmt tx queue is still full
> > 
> > The card works fine in Windows, and works in Linux with the Windows
> > drivers. Distro is Gentoo. If
> > any other information would be helpful please let me know.
> > 
> I seem to have the same problem at this point (fixed 2 other FC2 related 
> errors yesterday). I've got the prism54 (isl3890) chipset on a smc2802w 
> pci card. I don't get some of the messages you do, but I'm guessing 
> that's because you're pcmcia and I'm pci. I think the critical point of 
> failure (first error message) is the "soft reset timed out". What's 
> curious (odd) to me is that when looking at the syslog in real time 
> (tail -f) the message occurs very quickly (seems immediate). I've tried 
> kernels 2.6.5 and 2.6.8 (stock, from RH) so far.
> 
> As Red Green would say, "remember, I'm pulling for you; we're all in 
> this together". Hopefully we'll post the solution here when we find it.

Nice to know I'm not the only one :) I've just tried the 2.6.7-bk3
kernel, which
has the 1.2 version of the driver (the others I've used had 1.1) and I
get a kernel
oops from ifconfig partway through the dmesg output in my first email.
If the text
of the oops would be useful I'll post it tomorrow, I need to get some
sleep right now.
-- 
http://www.fastmail.fm