The problem is that there seem to be two devices using the same vendor and model string. We have the info for the bluetooth dongle (0x050d:0x0121, Class=224 (wireless), SubClass=1 (radio) and Protocol=1 (bluetooth) from the lsusb output). The whole thing has to be fixed in the driver and the following patch could be a start. However, this has to be done upstream. Even more because the quick approach below (if it works) would be the wrong direction. Rather than checking special non- working cases, I guess it would make sense to extend the matching criteria more specifically to the supported classes. But that would be the decission of the maintainer anyways.
USB PEGASUS DRIVER P: Petko Manolov M: [EMAIL PROTECTED] L: [EMAIL PROTECTED] L: [EMAIL PROTECTED] W: http://pegasus2.sourceforge.net/ S: Maintained ** Attachment added: "This could be a start for fixing the driver" http://launchpadlibrarian.net/12134300/pegasus-belkin-quirk.patch -- Belkin USB bluetooth device loads wrong module https://bugs.launchpad.net/bugs/140511 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
