Comment 28 for bug 362875

In summary of my last 2 comments: all people commenting on this report are not necessarily experiencing the same bug. They just all happen to be using Ralink-based USB devices which share a driver/firmware framework. The issues could be related but not necessarily.

I am marking this "Incomplete" until we have a set of good information regarding a related issue on the most recent Ubuntu distribution with proper logs, etc. That means something like the following:

1) Describe in detail how you reproduce your issue (i.e., step-by-step)
2) Describe your system, giving Ubuntu version, etc.
3) Provide the output from the following commands in your comment or as separate attachments:
dmesg
lsusb
uname -a
lsusb -vv
dkpg -l | grep linux-firmware

If we find more than one set of valid logs that represent distinct issues, then we should file new, separate bug reports.

(BTW, the logs attached by Andrea Carpineti are totally worthless; they are not related to this bug and seem to apply to a Broadcom chip, not Ralink)