0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesn't work with 3.11 or 3.13 kernels
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | linux (Ubuntu) |
Medium
|
Unassigned | ||
Bug Description
SRU Justification:
Impact: Bluetooth device stopped working. Device support regression.
Fix: Upstream, f9f462faa02777f
Testcase: Comment #10
Original Description:
Bluetooth device stopped working after upgrading ubuntu to 13.10.
~$ lsusb:
Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
~$ hciconfig
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1B:10:00:0F:46 ACL MTU: 1017:8 SCO MTU: 64:0
DOWN
RX bytes:457 acl:0 sco:0 events:16 errors:0
TX bytes:68 acl:0 sco:0 commands:16 errors:0
~$ hcitool dev
Devices:
device simply doesnt appear on bluetooth manager. blueman UI is broken.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-
ProcVersionSign
Uname: Linux 3.11.0-4-generic x86_64
NonfreeKernelMo
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
Date: Fri Sep 6 22:32:45 2013
HibernationDevice: RESUME=
IwConfig:
eth0 no wireless extensions.
lo no wireless extensions.
MachineType: MEGAWARE MW-H61M-2H
MarkForUpload: True
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 1.113
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to saucy on 2013-08-23 (15 days ago)
dmi.bios.date: 08/28/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5 MW
dmi.board.
dmi.board.name: MW-H61M-2H
dmi.board.vendor: MEGAWARE
dmi.board.version: v1.3 - 17/07/2012 - MWX
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: MEGAWARE
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: MW-H61M-2H
dmi.product.
dmi.sys.vendor: MEGAWARE
| Changed in linux (Ubuntu): | |
| status: | New → Confirmed |
| Christopher M. Penalver (penalvch) wrote : Re: Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesnt work on ubuntu 13.10 | #3 |
jorge Alexandre, could you please test the latest upstream kernel available following https:/
kernel-
kernel-
where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-
This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-
If the mainline kernel does not fix this bug, please add the following tags:
kernel-
kernel-
As well, please remove the tag:
needs-upstream-
Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.
| tags: |
added: needs-upstream-testing regression-release removed: bluetooth bluez |
| Changed in linux (Ubuntu): | |
| status: | Confirmed → Incomplete |
Just tested this:
http://
bug isn't fixed.
| tags: |
added: kernel-bug-exists-upstream kernel-bug-exists-upstream-v3.11-saucy removed: needs-upstream-testing |
| Changed in linux (Ubuntu): | |
| status: | Incomplete → Confirmed |
| Christopher M. Penalver (penalvch) wrote : | #5 |
jorge Alexandre, the next step is to bisect from the previously working release to Saucy, in order to identify the offending commit. Could you please do this following https:/
| Changed in linux (Ubuntu): | |
| status: | Confirmed → Incomplete |
it worked on v3.9.11-saucy and on v3.10-rc1-saucy it stopped working.
thats the bisection right? the good release succeded by the bad one.
which tag i am supposed to add now?
Thank you for your patience.
| Changed in linux (Ubuntu): | |
| status: | Incomplete → Confirmed |
| tags: | added: bisect-done |
| Christopher M. Penalver (penalvch) wrote : | #7 |
jorge alexandre, now that you found the kernel version regression, one would need to commit bisect between those two versions to identify the commit that caused this regression via https:/
| tags: |
added: performing-bisect removed: bisect-done |
| Changed in linux (Ubuntu): | |
| status: | Confirmed → Incomplete |
| Changed in linux (Ubuntu): | |
| importance: | Undecided → Medium |
unfortunately, i dont have the knowledge necessary to commit bisect between those versions yet.
I've never used git.
Is there a more basic tutorial?
thanks for the replies
| Christopher M. Penalver (penalvch) wrote : | #9 |
jorge alexandre, the article previously mentioned is that basic tutorial.
| Aditya (code-aditya) wrote : | #10 |
I am also affected by this bug after upgrading to Saucy. I am following the instructions mentioned at https:/
I have downloaded and installed the kernals from https:/
- 3.9.0-7.15 works for me
- 3.10.0-0.6 doesn't work
So, the issue is between these two releases. For further commit bisecting, I have downloaded the git repository of `ubuntu-saucy` by running:
$ git clone git://kernel.
To see how many commits are there in between, I run the following command:
$ git log --oneline Ubuntu-
Its output is:
14802 117434 922801
Please, help me further. Are there 14802 commits?
Aditya, please file a new report so this may tracked to the hardware this is being plugged into via a terminal:
ubuntu-bug linux
| Aditya (code-aditya) wrote : | #12 |
@Christopher
Thanks for your reply. I have filed LP Bug #1245150 in this regard.
| tags: | added: needs-bisect |
| Zsoltee (zsoltee-the-programmer) wrote : | #13 |
What do you think, can you solve the problem?
Zsoltee, so your hardware may be tracked, could you please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux
For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https:/
Ubuntu Kernel Team: https:/
Ubuntu Community: https:/
When opening up the new report, please feel free to subscribe me to it.
Thank you for your understanding.
| Aditya (code-aditya) wrote : | #15 |
I have been facing the similar issue.. There is a patch available on Kernel Bug Tracker over here: https:/
| Margarita Manterola (marga-9) wrote : | #16 |
Trusty is still affected by this bug. Please apply the patch to the trusty kernel.
| Changed in linux (Ubuntu): | |
| status: | Incomplete → Confirmed |
I have the same device: "Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)".
I updated to trusty yesterday, so bluetooth is not working now.
| Christopher M. Penalver (penalvch) wrote : Re: 0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesnt work on ubuntu 13.10 | #18 |
Margarita Manterola / Philipp Kern / Sebastián Perruolo, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux
For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https:/
Ubuntu Kernel Team: https:/
Ubuntu Community: https:/
When opening up the new report, please feel free to subscribe me to it.
Thank you for your understanding.
Helpful bug reporting tips:
https:/
| summary: |
- Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesnt work on ubuntu - 13.10 + 0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesnt work on + ubuntu 13.10 |
| Changed in linux (Ubuntu): | |
| status: | Confirmed → Incomplete |
Christopher, I uploaded a new report https:/
| Margarita Manterola (marga-9) wrote : | #20 |
I really don't understand why this need of asking users to file duplicate bugs. This is a bug with a specific piece of hardware. Any user that has this piece of hardware is affected. Why do you want one bug per user? This makes it much harder to track the progress on the issue... For example, on the bug Sebastian filed, someone asked him since when was this happening, which was already answered here (since 13.10).
Also, that other bugs includes the information that this is fixed in v3.15-rc3-utopic, but this bug doesn't, because of the absurd split in information.
| summary: |
- 0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesnt work on - ubuntu 13.10 + 0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesn't work + with 3.11 or 3.13 kernels |
| Margarita Manterola (marga-9) wrote : | #21 |
Adding more information from other sources.
The bugzilla bug (https:/
This is the commit where it's fixed:
https:/
It was applied on 2014-01-04 for the 3.14 kernel. Getting this patch backported to 3.13 will likely fix it for Trusty.
| Margarita Manterola (marga-9) wrote : | #22 |
My link was to specific file in the commit, but from it you can get to the whole patch. Link to the full patch:
https:/
| Changed in linux (Ubuntu): | |
| status: | Incomplete → Confirmed |
| assignee: | nobody → Rafael David Tinoco (inaddy) |
| description: | updated |
| Rafael David Tinoco (inaddy) wrote : | #23 |
Attaching patch that is being sent to Kernel Team by e-mail.
| tags: | added: patch |
| Rafael David Tinoco (inaddy) wrote : | #24 |
Both commits:
f9f462faa02777f
81cac64ba258ae8
together seem to address this issue...
First time they appeared was: v3.14-rc1. The second one's description is:
"""
There exists a set of Bluetooth USB devices that show up on the USB
bus as 0a12:0001 and identify themselves as devices from CSR. However
they are not. When sending Read Local Version command they now have
a split personality and say they are from Broadcom.
< HCI Command: Read Local Version Information (0x04|0x0001) plen 0
> HCI Event: Command Complete (0x0e) plen 12
Read Local Version Information (0x04|0x0001) ncmd 1
status 0x00
HCI Version: 2.0 (0x3) HCI Revision: 0x3000
LMP Version: 2.0 (0x3) LMP Subversion: 0x420b
Manufacturer: Broadcom Corporation (15)
The assumption is that they are neither CSR nor Broadcom based devices
and that they are designed and manufactured by someone else.
For the most parts they follow the Bluetooth HCI specification and
can be used as standard Bluetooth devices. However they have the
minor problem that the Delete Stored Link Key command is not working
as it should.
During the Bluetooth controller setup, this command is needed if
stored link keys are supported. For these devices it has to be
assumed that this is broken and so just set a quirk to clearly
indicate the behavior. After that the setup can just proceed.
Now the trick part is to detect these faulty devices since we do
not want to punish all CSR and all Broadcom devices. The original
devices do actually work according to the specification.
What is known so far is that these broken devices set the USB bcdDevice
revision information to 1.0 or less.
T: Bus=02 Lev=01 Prnt=01 Port=08 Cnt=03 Dev#= 9 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0a12 ProdID=0001 Rev= 1.00
S: Manufacturer=
S: Product=Bluetooth V2.0 Dongle
T: Bus=05 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0a12 ProdID=0001 Rev= 0.07
In case of CSR devices, the bcdDevice revision contains the firmware
build ID and that is normally a higher value. If the bcdDevice revision
is 1.0 or less, then an extra setup stage is checking if Read Local
Version returns CSR manufacturer information. If not then it will be
assumed that this is a broken device and the Delete Stored Link Key
command will be marked as broken.
Signed-off-by: Marcel Holtmann <email address hidden>
Signed-off-by: Johan Hedberg <email address hidden>
"""
Building a kernel from ubuntu-trusty tree with both patches for testing.
Will provide public PPA soon.
* Will rely on community tests to suggest fix to stable-kernel team *
| Rafael David Tinoco (inaddy) wrote : | #26 |
Ok, here it goes... whoever suffers from this issue please do test kernel available from this PPA:
ppa:inaddy/
And provide feedback if it solves this issue. As soon as I get testing results I'll sent a SRU request
for the stable kernel team to include this into Trusty's kernel.
| Aditya (code-aditya) wrote : | #27 |
@Rafael
I have added your ppa but when I run `sudo apt update && sudo apt upgrade` it only offers me to upgrade `linux-libc-dev` package and nothing else. Is that good? I suppose it should offer me to update 4-5 linux related packages from your repository and have I haven't installed the update.
Right now I am running the mainline kernel version 3.14.15.
=======
$ uname -a
Linux aditya-desktop 3.14.15-
=======
$ dpkg -l | grep "linux\-[a-z]*\-"
ii linux-headers-
ii linux-headers-
ii linux-headers-
ii linux-headers-
ii linux-headers-
rc linux-image-
ii linux-image-
ii linux-image-
rc linux-image-
ii linux-image-
ii linux-image-generic 3.13.0.32.38 i386 Generic Linux kernel image
ii linux-libc-dev:i386 3.13.0-32.57 i386 Linux Kernel Headers for development
ii linux-sound-base 1.0.25+
=======
Let me know if I should install it..
| Rafael David Tinoco (inaddy) wrote : Re: [Bug 1221995] 0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesn't work with 3.11 or 3.13 kernels | #28 |
You are using 3.14 and I have created a patched 3.13 version. You have to install linux-image-
-Rafael
On Aug 03, 2014, at 03:53 PM, Aditya <email address hidden> wrote:
> @Rafael
>
> I have added your ppa but when I run `sudo apt update && sudo apt
> upgrade` it only offers me to upgrade `linux-libc-dev` package and
> nothing else. Is that good? I suppose it should offer me to update 4-5
> linux related packages from your repository and have I haven't installed
> the update.
>
> Right now I am running the mainline kernel version 3.14.15.
>
| Aditya (code-aditya) wrote : | #29 |
@Rafael,
I have uninstalled the mainline kernel v3.14.15 and booted into v3.13.0-32, but still it only offers me to upgrade `linux-libc-dev` and nothing else.
$ uname -a
Linux aditya-desktop 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:12 UTC 2014 i686 athlon i686 GNU/Linux
$ dpkg -l | grep "linux\-[a-z]*\-" | awk '{print $2}'
linux-headers-
linux-headers-
linux-headers-
linux-image-
linux-image-
linux-image-
linux-image-
linux-image-generic
linux-libc-dev:i386
linux-sound-base
| Rafael David Tinoco (inaddy) wrote : | #30 |
Since this is a test-only kernel you can install it directly:
# apt-get install linux-image-
and it will get the kernel from the appropriate PPA:
inaddy@
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools
linux-
The following NEW packages will be installed:
linux-
0 upgraded, 1 newly installed, 0 to remove and 20 not upgraded.
Need to get 15.1 MB of archives.
After this operation, 42.0 MB of additional disk space will be used.
Get:1 http://
...
| Aditya (code-aditya) wrote : | #31 |
@Rafael,
I manually installed the `linux-
Moreover, the kernel creates additional problems. It doesn't recognize my mouse and the display is stretched on the monitor with lower resolution.
In short, the package doesn't work. Let me know if you need any assistance.
| Margarita Manterola (marga-9) wrote : | #32 |
You need to install the image-extra package.
| Rafael David Tinoco (inaddy) wrote : | #33 |
Marga,
Could you confirm if this fixes the issue for me ? So I can propose this SRU to our kernel team ?
Thank you!
| exzemat (exzemat) wrote : | #34 |
I tested lastest mainline linux-headers-
my Cambridge Silicon Radio bluetooth dongle zork on this kernel.
I make a rapport to complet.
| exzemat (exzemat) wrote : | #35 |
lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 2548:1002
Bus 003 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
hciconfig
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1B:10:00:2A:EC ACL MTU: 1017:8 SCO MTU: 64:0
UP RUNNING PSCAN
RX bytes:512 acl:0 sco:0 events:23 errors:0
TX bytes:336 acl:0 sco:0 commands:23 errors:0
hcitool scan
Scanning ...
04:FE:31:47:71:15 GT-B2710()
uname -r
3.17.0-
| Rafael David Tinoco (inaddy) wrote : | #36 |
I'm holding until I can get a feedback on the hot fixed kernel I have provided into PPA. Marga said to Aditya to install extra kernel package and we haven't heart if it worked or not. After confirmation... if positive I'll ask kernel team to SRU the fix, if negative I'll dig into upstream code to cherry-pick the fix.
Thank you.
-Rafael
| Kedar Patil (patilkedar) wrote : | #37 |
Hi Rafael,
The kernel from your ppa is not working for me. I installed:
$ sudo add-apt-repository ppa:inaddy/
$ sudo apt-get install linux-image-
$ sudo apt-get install linux-image-
# rebooted into linux-image-
$ uname -a
Linux soni 3.13.0-33-generic #58hf00069767v2
$ lsusb
Bus 002 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
$ hciconfig
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1B:10:00:2A:EC ACL MTU: 1017:8 SCO MTU: 64:0
DOWN
RX bytes:494 acl:0 sco:0 events:20 errors:0
TX bytes:75 acl:0 sco:0 commands:20 errors:0
$ hcitool scan
Device is not available: No such device
Thanks,
Kedar
| Rafael David Tinoco (inaddy) wrote : | #38 |
Perfect. I'll dig into upstream changes to provide another built kernel based on -stable version.
Let you all know soon.
Tks
-Rafael
| Rafael David Tinoco (inaddy) wrote : | #39 |
Kedar: Could you test the following kernel:
Ubuntu-
(lts-backport-
Easier for me to cherry-pick something that was already fixed for Utopic.
Thank you!
-Rafael
| Walter Lapchynski (wxl) wrote : | #40 |
@inaddy, which kernel are you suggesting to test from where? i can't find it in the ppa or anywhere in the repos, but i have the hardware and the same problem on 3.13.0-43-generic in trusty.
Walter Lapchynski, he's referring to:
apt-cache policy linux-generic-
linux-generic-
Installed: 3.16.0.28.21
Candidate: 3.16.0.28.21
Version table:
3.16.0.29.22 0
400 http://
*** 3.16.0.28.21 0
500 http://
500 http://
100 /var/lib/
| Walter Lapchynski (wxl) wrote : | #42 |
I didn't have a chance to test that last night but I tried the same hardware on a Kubuntu Trusty with 3.13.0-40-generic and had no problem. Worked right out of the box. Are we *sure* this is a kernel issue?
| Walter Lapchynski (wxl) wrote : | #43 |
No luck on linux-generic-
| tags: |
added: kernel-bug-exists-upstream-3.11 needs-upstream-testing removed: kernel-bug-exists-upstream kernel-bug-exists-upstream-v3.11-saucy |
| Kedar Patil (patilkedar) wrote : | #44 |
@Rafael,
The linux-generic-
$ sudo apt-get install linux-generic-
<reboot>
$ uname -a
Linux soni 3.16.0-28-generic #38-Ubuntu SMP Sat Dec 13 16:13:28 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release --all
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.1 LTS
Release: 14.04
Codename: trusty
$ apt-cache policy linux-generic-
linux-generic-
Installed: 3.16.0.28.21
Candidate: 3.16.0.28.21
Version table:
*** 3.16.0.28.21 0
500 http://
500 http://
100 /var/lib/
$ lsusb | grep Bluetooth
Bus 001 Device 003: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
$ hciconfig
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1B:10:00:2A:EC ACL MTU: 1017:8 SCO MTU: 64:0
DOWN
RX bytes:494 acl:0 sco:0 events:20 errors:0
TX bytes:75 acl:0 sco:0 commands:20 errors:0
$ hcitool scan
Device is not available: No such device
| Kedar Patil (patilkedar) wrote : | #45 |
After upgrading the kernel using software updater today I found that "hcitools scan" has stopped saying "no such device". However the scan does not find any bluetooth devices. I tried with a phone and a tablet.
$ uname -a
Linux soni 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64
$ sudo dmesg -c > /dev/null
# plug in the BT dongle at this point
$ lsusb | grep "luetooth"
Bus 002 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 003: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
$ hciconfig
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1B:10:00:2A:EC ACL MTU: 1017:8 SCO MTU: 64:0
UP RUNNING PSCAN
RX bytes:512 acl:0 sco:0 events:23 errors:0
TX bytes:336 acl:0 sco:0 commands:23 errors:0
$ hcitool scan
Scanning ...
$ echo $? # Nothing happened so see if there is error code...
0
$ dmesg
[ 899.894436] usb 2-1.7: new full-speed USB device number 4 using ehci-pci
[ 900.056153] usb 2-1.7: New USB device found, idVendor=0a12, idProduct=0001
[ 900.056158] usb 2-1.7: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 900.056160] usb 2-1.7: Product: Bluetooth V2.0 Dongle
[ 900.056163] usb 2-1.7: Manufacturer: Bluetooth v2.0
-Kedar
| Watcharapol Tadtiang (aborigines) wrote : | #46 |
this bug cause kernel module btusb not autoload.
$ lsb_release --all
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.2 LTS
Release: 14.04
Codename: trusty
$ uname -r
3.16.0-31-generic
$ lsusb | grep Bluetooth
Bus 007 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
$ hciconfig
$ hcitool scan
Device is not available: No such device
$ lsmod |grep btusb
$ sudo modprobe btusb
$ lsmod |grep btusb
btusb 32497 0
bluetooth 446409 22 bnep,btusb,rfcomm
$ hcitool dev
Devices:
hci0 00:1A:7D:DA:71:10
good luck .
| Bleish (manubia) wrote : | #47 |
I have btusb module loaded, but bug goes on.
bleish@edesktop ~ $ uname -r
3.11.0-12-generic
bleish@edesktop ~ $ lsusb | grep Bluet
Bus 003 Device 010: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
bleish@edesktop ~ $ lsmod | grep btusb
btusb 28267 0
bluetooth 371874 12 bnep,btusb,rfcomm
bleish@edesktop ~ $ hcitool dev
Devices:
bleish@edesktop ~ $ hcitool scan
Device is not available: No such device
bleish@edesktop ~ $
| Changed in linux (Ubuntu): | |
| assignee: | Rafael David Tinoco (inaddy) → nobody |
| Julian Lam (julian-lam) wrote : | #48 |
This bug affects me, and I can attempt patches/fixes if any are still outstanding?
| Julian Lam (julian-lam) wrote : | #49 |
Confirming that updating to a 3.16 kernel does not resolve the issue:
$ uname -a
Linux arya 3.16.0-38-generic #52~14.04.1-Ubuntu SMP Fri May 8 09:43:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
| Rafael David Tinoco (inaddy) wrote : | #50 |
Julian,
If you are willing to help, could you check 3.19 ?
To have all latest kernels (3.13, 3.16 and 3.19) you can use the following PPA (for testing purposes only):
https:/
Thank you
| Thomas Becker (peterlwl) wrote : | #51 |
I can confirm this. I have:
3.19.0-15-generic kernel
and this device is down most of the time. But it was at one time up ... dont know why :(
| Norbert (asterix52) wrote : | #52 |
I have now this problem with kernel 4.0 and 4.1 (wily).
On my system it works fine with kernel 3.19
| Norbert (asterix52) wrote : | #53 |
For kernel 4.1 is there a bugreport:
https:/
Is some able to build new kernel modules with that patch?
I too observe this bug, not sure when it came - I use my BT dongle (LogiLink) infrequently. But I have a gut feeling it came after I went from Linux Mint 16, to Linux Mint 17 (both Mate distribution).
My uname -a:
Linux xxxxxxx-
| Changed in linux (Ubuntu): | |
| status: | Confirmed → Triaged |
This change was made by a bot.