As per bug #203196, which fixed the issue for a different device, the KY-BT100 bluetooth adapter spams syslog due to a buggy SCO support. This patch fixes the issue by changing the already existing blacklist entry in the kernel driver file (drivers/bluetooth/hci_usb.c). I have tested it on my own hardware (x86) and it works fine. If you people help me to report this to upstream myself, this will be my first kernel patch. :-) Reproducible: Always
Created attachment 173996 [details, diff] kernel patch which corrects the blacklist entry
(In reply to comment #0) I am sorry I forgot to add that the patch has been made upon gentoo-sources-2.6.26-r3 and not the vanilla kernel sources.
Many thanks for this patch :)
Yes, thanks for submitting your patch :) With regards to getting this fix upstream -- basic guidelines are in the kernel documentation file linux/Documentation/SubmittingPatches, have you read that yet?
Hmm. I am start thinking that I am not facing the same problem. Dmesg output is clear but /var/log/messages is full of crap. Dec 2 12:08:27 Raptor hci_scodata_packet: hci0 SCO packet for unknown connection handle 92 Dec 2 12:08:27 Raptor hci_scodata_packet: hci0 SCO packet for unknown connection handle 92 Dec 2 12:08:27 Raptor hci_scodata_packet: hci0 SCO packet for unknown connection handle 92 Dec 2 12:08:27 Raptor hci_scodata_packet: hci0 SCO packet for unknown connection handle 92 Dec 2 12:08:27 Raptor hci_scodata_packet: hci0 SCO packet for unknown connection handle 92 Dec 2 12:08:27 Raptor hci_scodata_packet: hci0 SCO packet for unknown connection handle 92 etc etc etc... The patch didnt work for this problem... So is that true? Am I facing a different problem?
Markos, you have a different broken device so you need a different patch. Please open your own bug report. Thanks!
oh well Take a look here ( lsusb output ) Bus 002 Device 002: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter I do have the same device ( or at least I think I do ) . The patch applies for the same vendor and device id as mine ...
OK, sorry, bad assumption on my part then. Let's discuss this on IRC (I want to check that you are patching correctly)
The patch did work for me at last. Thanks Daniel. Luca, did you looked the documentation and submit the patch or not? If not , we can commit it on your behalf. Thanks
(In reply to comment #9) > Luca, did you looked the documentation and submit the patch or not? If not , we > can commit it on your behalf. Yeah, I read the kernel docs (shame on me for not looking at the most obvious place!) but yesterday was a full day to make the patch as they want it. I'll likely do it tomorrow, since today I'll be out of reach of this computer the whole day.
Luca, did you have any luck submitting this bug on kernel bugzilla?
(In reply to comment #11) > Luca, did you have any luck submitting this bug on kernel bugzilla? http://marc.info/?l=linux-kernel&m=122843361518488&w=2 I could finally do it yesterday. :-)
Luca, according to LKML there is already a newer version for bluetooth usb drivers in kernel. Please try to disable to old one and enable the new Mine is like that now # # Bluetooth device drivers # # CONFIG_BT_HCIUSB is not set CONFIG_BT_HCIBTUSB=y I m gonna do a couple of tests and then report back to LKML that it works Thanks
Unfortunatelly this driver doesnt work for me. The device cannot be recongnised. Please let me know if it works on you
Actually the driver works perfect on gentoo-sources-2.6.27-rX ( basically on every 2.6.27 kernel ) On 2.6.26 there is no support for our device Here is the commit that adds support for our device http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.27.y.git;a=commitdiff;h=cfeb414537b1d7c23ba202f198fa4154cd5a4856 This patch is going to be on the next gentoo-sources-2.6.26 ( if there is one ) Thanks
We've requested that 2.6.27 will be marked stable, and won't be doing any more 2.6.26 releases, so we can mark this as fixed.
