Atheros QCA9565 bluetooth hardware not detected

[jackchwang]

I can't open bluetooth in the setting panel,it's gray.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 27 12:01:53 2018
InstallationDate: Installed on 2018-03-15 (43 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307)
InterestingModules: bnep btusb bluetooth
MachineType: Acer TravelMate P257-MG
ProcEnviron:
 LANGUAGE=zh_CN:zh
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=zh_CN.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=cd20b9a0-1844-4466-9658-8981e660c11a ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/27/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.14
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: BA50_BH
dmi.board.vendor: Acer
dmi.board.version: Type2 - A01 Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.14:bd11/27/2015:svnAcer:pnTravelMateP257-MG:pvrV3.72:rvnAcer:rnBA50_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: BDW
dmi.product.name: TravelMate P257-MG
dmi.product.version: V3.72
dmi.sys.vendor: Acer
hciconfig:

[Daniel van Vugt (vanvugt)]

Please try toggling the switch in the header bar to ON (next to the minimize/maximize/close buttons).

If that doesn't work then it appears the problem is that the kernel has not detected your bluetooth hardware (see rfkill.txt above).

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1532267, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.