Comment 4 for bug 721356

It is not completely clear to me in what exact way it did affect that adapter (worked before and now as described or was not working and is sort of half working now). The only thing done really was to provide a link in /lib/firmware that points now to another directory in there. The question if the adapter has been working before would be whether you ever took a firmware and added it to /lib/firmware manually. Or what happens if you rename or delete that link (what are the startup messages in dmesg). Also what is the exact usb id of that adapter.