Comment 19 for bug 125832

Hey, thanks for the patch. I'll give it a go tomorrow.

I'm a little irritated. Another new kernel has been released, and this bug is still unresolved. Hell, a developer hasn't even looked at this bug report, as far as I can tell. I've resorted to using Debian's stock 2.6.22 kernel and it works flawlessly. The whole "incompatible with network-manger" thing is just smoke. A card that that has worked out of the box for the past three releases, and probably more, is now causing hard locks, kernel panics, or is simply unrecognised. Why isn't someone working on this?