Eu tenho um Acer Aspire VN7-571G-56EF rodando 16.04, atualizado de 14.04.5 e nunca consegui fazer o bluetooth funcionar. lista de rfkill tudo mostra tudo está bem:
rfkill list all
0: acer-wireless: Wireless LAN
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
MAS ...
uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth
me dá:
Linux compooper 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:0123]
Kernel driver in use: r8169
Kernel modules: r8169
03:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 20)
Subsystem: Foxconn International, Inc. QCA6174 802.11ac Wireless Network Adapter [105b:e08e]
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci
Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 004: ID 04f2:b469 Chicony Electronics Co., Ltd
Bus 001 Device 003: ID 0489:e092 Foxconn / Hon Hai
Bus 001 Device 002: ID 8087:8001 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy (MTP)
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[ 8.926314] Bluetooth: Core ver 2.21
[ 8.927640] Bluetooth: HCI device and connection manager initialized
[ 8.933129] Bluetooth: HCI socket layer initialized
[ 8.933134] Bluetooth: L2CAP socket layer initialized
[ 8.933146] Bluetooth: SCO socket layer initialized
[ 9.443693] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 9.443696] Bluetooth: BNEP filters: protocol multicast
[ 9.443700] Bluetooth: BNEP socket layer initialized
[ 9.464267] Bluetooth: RFCOMM TTY layer initialized
[ 9.464276] Bluetooth: RFCOMM socket layer initialized
[ 9.464282] Bluetooth: RFCOMM ver 1.11
[ 1.126114] [Firmware Bug]: ACPI(PXSX) defines _DOD but not _DOS
[ 7.571059] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin failed with error -2
bluetooth 520192 31 bnep,btbcm,btrtl,btusb,rfcomm,btintel
É evidente que estou recebendo um "bug de firmware", mas não tenho certeza do que fazer para corrigi-lo. Qualquer ajuda seria muito apreciada.
Obrigado, @ Jeremy31. Eu segui suas instruções e as coisas estão melhores, mas recebo as seguintes mensagens de falha, bug e firmware agora:
Linux compooper 4.8.0-040800-generic #201610022031 SMP Mon Oct 3 00:32:57 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:0123]
Kernel driver in use: r8169
Kernel modules: r8169
03:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 20)
Subsystem: Foxconn International, Inc. QCA6174 802.11ac Wireless Network Adapter [105b:e08e]
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci
Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 004: ID 04f2:b469 Chicony Electronics Co., Ltd
Bus 001 Device 006: ID 0489:e092 Foxconn / Hon Hai
Bus 001 Device 002: ID 8087:8001 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[ 10.767266] Bluetooth: Core ver 2.21
[ 10.767280] Bluetooth: HCI device and connection manager initialized
[ 10.767589] Bluetooth: HCI socket layer initialized
[ 10.767591] Bluetooth: L2CAP socket layer initialized
[ 10.767603] Bluetooth: SCO socket layer initialized
[ 10.876730] Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00000200.bin
[ 10.876733] Bluetooth: hci0: QCA: patch rome 0x200 build 0x299, firmware rome 0x200 build 0x111
[ 10.957650] Bluetooth: hci0: using NVM file: qca/nvm_usb_00000200.bin
FAIL? -> [ 12.877045] Bluetooth: hci0: Failed to send body at 4 of 1859 (-32)
FAIL? -> [ 12.878461] Bluetooth: hci0: Failed to access otp area (-32)
[ 13.235593] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 13.235594] Bluetooth: BNEP filters: protocol multicast
[ 13.235598] Bluetooth: BNEP socket layer initialized
[ 23.281766] Bluetooth: hci0: using NVM file: qca/nvm_usb_00000200.bin
[ 23.656660] Bluetooth: RFCOMM TTY layer initialized
[ 23.656665] Bluetooth: RFCOMM socket layer initialized
[ 23.656676] Bluetooth: RFCOMM ver 1.11
[ 7932.541075] Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00000200.bin
[ 7932.541077] Bluetooth: hci0: QCA: patch rome 0x200 build 0x299, firmware rome 0x200 build 0x111
[ 7932.595265] Bluetooth: hci0: using NVM file: qca/nvm_usb_00000200.bin
BUG? -> [ 1.890954] [Firmware Bug]: ACPI(PXSX) defines _DOD but not _DOS
FAIL? -> [ 9.519461] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:03:00.0.bin failed with error -2
FAIL? -> [ 9.519479] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin failed with error -2
[ 9.541919] ath10k_pci 0000:03:00.0: firmware ver SW_RM.1.1.1-00157-QCARMSWPZ-1 api 5 features ignore-otp,no-4addr-pad crc32 10bf8e08
[ 10.876733] Bluetooth: hci0: QCA: patch rome 0x200 build 0x299, firmware rome 0x200 build 0x111
CRASH? -> [ 7929.883576] ath10k_pci 0000:03:00.0: firmware crashed! (uuid n/a)
[ 7929.883965] ath10k_pci 0000:03:00.0: firmware ver SW_RM.1.1.1-00157-QCARMSWPZ-1 api 5 features ignore-otp,no-4addr-pad crc32 10bf8e08
[ 7929.886178] ath10k_pci 0000:03:00.0: firmware register dump:
[ 7932.541077] Bluetooth: hci0: QCA: patch rome 0x200 build 0x299, firmware rome 0x200 build 0x111
bluetooth 548864 51 btrtl,btintel,bnep,btbcm,rfcomm,btusb
rfkill 24576 14 bluetooth,acer_wmi,cfg80211
crc16 16384 2 bluetooth,ext4
Alguma opinião?
Oi @ Jeremy31 e @LiveWireBT!
Então, depois de alguns meses usando o novo kernel, voltei para o 4.4. Infelizmente 4,8 e acima me deu problemas constantes com meu mouse, wifi, hibernação, suspensão, etc. Basicamente eu poderia conectar em casa, fechar minha tampa e ir trabalhar, mas então não veria a rede de trabalho - apenas a rede doméstica iria mostrar na lista de redes Wi-Fi disponíveis e o computador nunca realmente suspenso. Apenas continuou com a tampa fechada. Downgrade de 4.9 para 4.8 retornou suspensão, mas ainda os problemas de wifi. Atualizar para 4,10 foi apenas um pesadelo, então voltei rapidamente para 4,8. Eu percebi que ter BT não é tão importante quanto ter um sistema estável que não vai me causar problemas todos os dias, mas ainda gostaria de ter o BT de volta, já que eu o uso para conferência de trabalho. Então acho que vou ter que pedir para consertar o kernel 4.4.
Obrigado a todos por sua ajuda!