Just rebooted:

$ sudo hciconfig -a
hci0:   Type: BR/EDR  Bus: USB
        BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
        DOWN 
        RX bytes:0 acl:0 sco:0 events:0 errors:0
        TX bytes:6 acl:0 sco:0 commands:2 errors:0
        Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
        Packet type: DM1 DH1 HV1 
        Link policy: 
        Link mode: SLAVE ACCEPT 
$ lsusb
Bus 006 Device 004: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth

So it is detected, but still cannot be controlled

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1541392

Title:
  AR3011 Bluetooth not starting after being stoped (but detected)

Status in bluez package in Ubuntu:
  New

Bug description:
  kernel : 4.2.0-27
  onboard bluetooth controller : AR3011
  The Bluetooth was working great. I deactivated the bluetooth via the 
indicator, and then, impossible to start it. Neither from the settings 
bluetooth interface, neither via hciconfig. The service was of course started 
without problems.
  The device was well recognized and started, could find which usb port and 
everything. However hciconfig could not see it:

  $ hciconfig -a hci0                                                           
                                                                                
                                                                             
  hci0:   Type: BR/EDR  Bus: USB
          BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
          DOWN 
          RX bytes:0 acl:0 sco:0 events:0 errors:0
          TX bytes:12 acl:0 sco:0 commands:4 errors:0

  Of course I restarted the system, tried purging all bluetooth related 
packages, tried installing blueman. Nothing would make it start.
  Finally I found this thread of arch linux :
  https://bbs.archlinux.org/viewtopic.php?id=171357

  So basically I shut down the computer, waited a while, started the computer 
and the bluetooth is functional again.
  I will try reproducing the bug. I tried, but it did not happen again. Maybe 
it's because I was listening music, lost signal, came back to the pc and closed 
bluetooth.

  Any thoughts of what is this caused by?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1541392/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to