Comment 5 for bug 721356

First, thank you for the reply. Second, I've installed the windows driver with ndiswrapper so the adaptor is working now, but I wouldn't mind knowing exactly what went wrong.

Meanwhile, no it doesn't entirely make sense that the new link would have caused the failure, but the only other possibilities (that I can think of) are that something else in that day's update caused the problem, or that I did something in the course of installing/trying to figure out Samba--which was really the only thing I think I did on that machine during that uptime. I'm sure I didn't manually open /lib/firmware at any time.

In any case, I thought it could possibly be helpful to someone else to have the event on record.

As to the exact effect on the adaptor: It was working normally, connecting automatically at log in, until the failure which came at the first reboot after the update. At that point the wireless indicator on the panel would "pulse" as if trying to find the signal, and then eventually give up.

Just for fun I'm going to uninstall ndiswrapper and see what happens when I disable the pointer. If I figure out anything stronger than a hypothesis, I'll post it here.

The usb ID is 7392:7811.

Thanks again for your time. No need to reply on my behalf. From here it's just me learning something new.

-z