I can confirm that the issue can be reproduced on fresh installed ubuntu
17.04.

-- 
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/1665589

Title:
  Killer 1535 802.11 2×2 Wi-Fi + BT 4.1 controller can't discover MS
  Mobile Mouse 3600

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I saw number of posts here about Mobile Mouse 3600 but sadly none of
  them helped me to debug the issue.

  I have Killer 1535 card on my Dell XPS 13. According to specs it's
  Bluetooth 4.1 device. Mobile Mouse 3600 is Bluetooth Low Energy device
  of version 4.0.

  In theory these two devices should be able to communicate.
  Unfortunately they don't :(

  I'm on Ubuntu MATE 16.10 but I also tested it on Linux Mint 18 and
  Element OS. I have bluez 5.41 installed.

  Here is what info I have abut my devices

  usb-devices | awk '/e301/' RS=

      T:  Bus=01 Lev=01 Prnt=01 Port=02 Cnt=03 Dev#=  4 Spd=12  MxCh= 0
      D:  Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
      P:  Vendor=0cf3 ProdID=e301 Rev=00.01
      C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
      I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
      I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

  
  hciconfig -a | grep HCI

      HCI Version: 4.1 (0x7)  Revision: 0x0

  lsusb | grep Ath

      Bus 001 Device 004: ID 0cf3:e301 Atheros Communications, Inc.

  `sudo hcitool lescan` finds nothing.

  After clean installation `dmesg | grep ath10` gives

      [   14.979939] ath10k_pci 0000:3a:00.0: enabling device (0000 -> 0002)
      [   14.981966] ath10k_pci 0000:3a:00.0: pci irq msi oper_irq_mode 2 
irq_mode 0 reset_mode 0
      [   15.263691] ath10k_pci 0000:3a:00.0: Direct firmware load for 
ath10k/pre-cal-pci-0000:3a:00.0.bin failed with error -2
      [   15.263709] ath10k_pci 0000:3a:00.0: Direct firmware load for 
ath10k/cal-pci-0000:3a:00.0.bin failed with error -2
      [   15.263734] ath10k_pci 0000:3a:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
      [   15.263736] ath10k_pci 0000:3a:00.0: could not fetch firmware file 
'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
      [   15.440154] ath10k_pci 0000:3a:00.0: qca6174 hw3.2 target 0x05030000 
chip_id 0x00340aff sub 1a56:1535
      [   15.440156] ath10k_pci 0000:3a:00.0: kconfig debug 0 debugfs 1 tracing 
1 dfs 0 testmode 0
      [   15.440582] ath10k_pci 0000:3a:00.0: firmware ver 
WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad 
crc32 75dee6c5
      [   15.532098] ath10k_pci 0000:3a:00.0: board_file api 2 bmi_id N/A crc32 
6fc88fe7
      [   17.658135] ath10k_pci 0000:3a:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 
cal otp max-sta 32 raw 0 hwcrypto 1
      [   17.770412] ath10k_pci 0000:3a:00.0 wlp58s0: renamed from wlan0

  My WiFi works. I can also pair Bluetooth keyboard. Since I don't
  really know how device drivers work in Linux I noticed line with error
  about `firmware-5.bin` in output of dmesg. So I took missing file from
  https://github.com/kvalo/ath10k-
  firmware/tree/master/QCA6174/hw3.0/4.4. It turned out to be bad idea
  because it botched wifi/bluetooth completely. Here is what I had in
  log

      [    3.519354] ath10k_pci 0000:3a:00.0: enabling device (0000 -> 0002)
      [    3.521259] ath10k_pci 0000:3a:00.0: pci irq msi-x interrupts 8 
irq_mode 0 reset_mode 0
      [    3.765880] ath10k_pci 0000:3a:00.0: Direct firmware load for 
ath10k/cal-pci-0000:3a:00.0.bin failed with error -2
      [    3.831220] ath10k_pci 0000:3a:00.0: failed to fetch board data for 
ath10k/QCA6174/hw3.0 from bus=pci,bmi-chip-id=0,bmi-board-id=0/board-2.bin
      [    5.887772] ath10k_pci 0000:3a:00.0: Unknown eventid: 90118
      [    5.887786] ath10k_pci 0000:3a:00.0: qca6174 hw3.2 (0x05030000, 
0x00340aff bmi 0:0) fw WLAN.RM.4.4-00022-QCARMSWPZ-2 fwapi 5 bdapi 1 htt-ver 
3.32 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 features 
wowlan,ignore-otp
      [    5.887789] ath10k_pci 0000:3a:00.0: debug 0 debugfs 1 tracing 1 dfs 0 
testmode 0
      [    8.884160] ath10k_pci 0000:3a:00.0: could not suspend target (-11)
      [    8.966789] ath10k_pci 0000:3a:00.0 wlp58s0: renamed from wlan0
      [   11.178547] ath10k_pci 0000:3a:00.0: Unknown eventid: 90118
      [   14.176459] ath10k_pci 0000:3a:00.0: failed to enable dynamic BW: -11
      [   20.176417] ath10k_pci 0000:3a:00.0: could not suspend target (-11)
      [   22.435758] ath10k_pci 0000:3a:00.0: Unknown eventid: 90118
      [   25.432569] ath10k_pci 0000:3a:00.0: failed to enable dynamic BW: -11
      [   31.432925] ath10k_pci 0000:3a:00.0: could not suspend target (-11)
      [   33.687090] ath10k_pci 0000:3a:00.0: Unknown eventid: 90118
      [   36.684683] ath10k_pci 0000:3a:00.0: failed to enable dynamic BW: -11
      [   42.685119] ath10k_pci 0000:3a:00.0: could not suspend target (-11)
      [   55.191367] ath10k_pci 0000:3a:00.0: Unknown eventid: 90118
      [   58.189447] ath10k_pci 0000:3a:00.0: failed to enable dynamic BW: -11
      [   64.189569] ath10k_pci 0000:3a:00.0: could not suspend target (-11)
      [   66.442090] ath10k_pci 0000:3a:00.0: Unknown eventid: 90118
      [   69.441647] ath10k_pci 0000:3a:00.0: failed to enable dynamic BW: -11
      [   75.441641] ath10k_pci 0000:3a:00.0: could not suspend target (-11)
      [   88.191952] ath10k_pci 0000:3a:00.0: Unknown eventid: 90118
      [   91.190185] ath10k_pci 0000:3a:00.0: failed to enable dynamic BW: -11
      [   97.190065] ath10k_pci 0000:3a:00.0: could not suspend target (-11)
      [   99.444307] ath10k_pci 0000:3a:00.0: Unknown eventid: 90118
      [  102.442543] ath10k_pci 0000:3a:00.0: failed to enable dynamic BW: -11
      [  108.442386] ath10k_pci 0000:3a:00.0: could not suspend target (-11)
      [  121.197006] ath10k_pci 0000:3a:00.0: Unknown eventid: 90118
      [  124.194704] ath10k_pci 0000:3a:00.0: failed to enable dynamic BW: -11
      [  130.194947] ath10k_pci 0000:3a:00.0: could not suspend target (-11)
      [  132.448783] ath10k_pci 0000:3a:00.0: Unknown eventid: 90118
      [  135.447000] ath10k_pci 0000:3a:00.0: failed to enable dynamic BW: -11
      [  141.447142] ath10k_pci 0000:3a:00.0: could not suspend target (-11)
      [  154.184800] ath10k_pci 0000:3a:00.0: Unknown eventid: 90118
      [  157.183488] ath10k_pci 0000:3a:00.0: failed to enable dynamic BW: -11
      [  163.183823] ath10k_pci 0000:3a:00.0: could not suspend target (-11)
      [  165.437951] ath10k_pci 0000:3a:00.0: Unknown eventid: 90118
      [  168.435897] ath10k_pci 0000:3a:00.0: failed to enable dynamic BW: -11
      [  174.436119] ath10k_pci 0000:3a:00.0: could not suspend target (-11)
      [  187.194437] ath10k_pci 0000:3a:00.0: Unknown eventid: 90118
      [  190.192217] ath10k_pci 0000:3a:00.0: failed to enable dynamic BW: -11
      [  196.192281] ath10k_pci 0000:3a:00.0: could not suspend target (-11)
      [  198.440901] ath10k_pci 0000:3a:00.0: Unknown eventid: 90118
      [  201.440446] ath10k_pci 0000:3a:00.0: failed to enable dynamic BW: -11
      [  207.440539] ath10k_pci 0000:3a:00.0: could not suspend target (-11)

  How can I troubleshoot this ? What can I do to make this mouse become
  disoverable ?

  Oh I also tried upgrading bluez to 5.43 but it didn't make any
  difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: bluez 5.41-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CasperVersion: 1.379
  CurrentDesktop: MATE
  Date: Fri Feb 17 09:26:41 2017
  InterestingModules: rfcomm btusb bnep bluetooth
  LiveMediaBuild: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  MachineType: Dell Inc. XPS 13 9360
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:        Type: Primary  Bus: USB
        BD Address: 9C:B6:D0:D1:E1:3A  ACL MTU: 1024:8  SCO MTU: 50:8
        UP RUNNING 
        RX bytes:759 acl:0 sco:0 events:58 errors:0
        TX bytes:4644 acl:0 sco:0 commands:58 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1665589/+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