Full use of Deepin Linux Entertainment, work, study (3)--Wireless card and Bluetooth device driver

1. Exception Description

In front of Muzi already talked about the graphics driver and CPU microcode patch update, today the wood to talk about the adaptation of Bluetooth and wireless card device driver problem, it is not only suitable for the new driver installation, but also suitable for driving abnormal repair. By default, the wooden sub-notebook installed Deepin Linux is self-driven, just in the process of tossing the exception, so there is a need to repair the driving process, the following wood is simple to share with you about the wireless card and Bluetooth device drivers of those things. Note: The Muzi wireless card and Bluetooth device are on the same module.
Today, a very strange thing happened, the notebook started to find the Bluetooth mouse is not possible, check the control center corresponding to the Bluetooth management button is not, let Muzi very strange. Restart the notebook also do not, so began to troubleshoot the problem, and repair Bluetooth device driver, in the process of use, the wooden son not only has the problem of Bluetooth device abnormality, also appeared the problem of wireless network card equipment anomalies, but muzi are used the same method to repair, in the case of abnormal, You will find that there is no Bluetooth or wireless card icon in the control center. As shown in the following:

2. Troubleshooting Process1) Detect Bluetooth service

First detects whether the Bluetooth service starts normally, detects that the service is started normally, and restarts the service is not effective.
SYSTEMCTL Status Bluetooth
Bluetooth.service-bluetooth Service
Loaded:loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset:enabled)
Active:active (running) since Fri 2018-04-13 14:08:38 CST; 30min ago
DOCS:MAN:BLUETOOTHD (8)
Main pid:829 (BLUETOOTHD)
Status: "Running"
Tasks:1 (limit:4915)
CGroup:/system.slice/bluetooth.service
└─829/usr/lib/bluetooth/bluetoothd

2) Detecting kernel loading module

To view the system kernel loading module, the Bluetooth module is loaded.
Lsmod | grep Blue
Bluetooth 634880 Btrtl,hci_uart,btintel,btqca,bnep,btbcm,btusb
Ecdh_generic 24576 1 bluetooth
Rfkill 28672 8 bluetooth,dell_laptop,cfg80211
CRC16 16384 2 BLUETOOTH,EXT4

3) Detect soft and hard switch

Check to see if the system turns on the soft or hard switch, turn off the Bluetooth module, Rfkill is a sub-interface provided by the Linux kernel for switching control of Wi-Fi, Bluetooth, 3G and 4G devices, and the result is that there is no Bluetooth device at all.
sudo rfkill list
0:phy0:wireless LAN
Soft Blocked:no
Hard Blocked:no
Look at this situation is not loaded module succeeded. So want to modprobe Btusb load the module to see if OK, found that after loading or not, uninstall the kernel Bluetooth module Rmmod bluetooth and then reload the Bluetooth module to the core Insmod Bluetooth.

4) Boot log detection

The log information is then retrieved, and DMESG is used to detect the information when the system is powered on.
DMESG | Egrep-i ' Blue|firm '
[14.374064] BLUETOOTH:HCI UART protocol Marvell registered
[14.741564] Request_firmware:ath10k/pre-cal-pci-0000:02:00.0.bin
[14.741954] Ath10k_pci 0000:02:00.0:firmware:failed to load Ath10k/pre-cal-pci-0000:02:00.0.bin (-2)
[14.741958] ATH10K_PCI 0000:02:00.0:direct firmware load for Ath10k/pre-cal-pci-0000:02:00.0.bin failed with error-2
[14.741961] Request_firmware:ath10k/cal-pci-0000:02:00.0.bin
[14.741970] Ath10k_pci 0000:02:00.0:firmware:failed to load Ath10k/cal-pci-0000:02:00.0.bin (-2)
[14.741972] ATH10K_PCI 0000:02:00.0:direct firmware load for Ath10k/cal-pci-0000:02:00.0.bin failed with error-2
[14.741974] Request_firmware:ath10k/qca6174/hw3.0/firmware-6.bin
[14.742930] Ath10k_pci 0000:02:00.0:firmware:direct-loading firmware Ath10k/qca6174/hw3.0/firmware-6.bin
[14.743438] Ath10k_pci 0000:02:00.0:firmware ver WLAN. Rm.4.4-00022-qcarmswpz-2 API 6 features WOWLAN,IGNORE-OTP CRC32 4d458559
[14.807142] Request_firmware:ath10k/qca6174/hw3.0/board-2.bin
[14.807740] Ath10k_pci 0000:02:00.0:firmware:direct-loading firmware Ath10k/qca6174/hw3.0/board-2.bin
[55.479518] Bluetooth:bnep (Ethernet Emulation) ver 1.3
[55.479519] BLUETOOTH:BNEP Filters:protocol Multicast
[55.479521] BLUETOOTH:BNEP Socket layer initialized
        In the log, the wooden son found two error messages, the two error message is clearly at the time of the system startup, the driver load is a problem. To find a problem, to solve the problem is simple.

5) Reload Drive

        Re-install Bluetooth driver, here to explain is that many notebooks are network cards and Bluetooth module together, this time if there is no way to see the Bluetooth module does not know what model, you can view the Wireless module model, and then the entire wireless module driver replacement (including the Bluetooth module driver), This should solve the problem.
#查看无线模块型号
Lspci | grep Wireless
02:00.0 network Controller:qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
Here the wooden son can see the corresponding model is qca6174
#下载对应驱动
Download the latest firmware and unzip the content:
https://codeload.github.com/kvalo/ath10k-firmware/zip/master
#进入无线驱动目录 (different wireless modules will not be the same, but all in the/lib/firmwareh directory)
cd/lib/firmware/ath10k
#删除原有驱动
RM-RF QCA6174
#复制最新驱动进去
cp-rf/home/liwenbin/downloads/ath10k-firmware-master/qca6174./
#进入对应目录, rename the drive module name.
CD qca6174/hw3.0
MV Firmware-4.bin_wlan. Rm.2.0-00180-qcarmswpz-1 Firmware-4.bin
Then shut down, reboot, you can identify the Bluetooth module, the Bluetooth device will be able to work properly.
At this time the wooden children to see the corresponding module already exists.
0:hci0:bluetooth
Soft Blocked:no
Hard Blocked:no
1:phy0:wireless LAN
Soft Blocked:no
Hard Blocked:no
        By contrast Muzi found that the previous Bluetooth module has less load of the HIDP and Rfcomm two protocols. The RFCOMM protocol is the communication protocol for Bluetooth devices, and HIDP is the basic support protocol.
Lsmod | grep Blue
Bluetooth 634880 Btrtl,hidp,hci_uart,btintel,btqca,bnep,btbcm,rfcomm,btusb
Ecdh_generic 24576 1 bluetooth
Rfkill 28672 8 bluetooth,dell_laptop,cfg80211
CRC16 16384 2 BLUETOOTH,EXT4

3, energy-saving control

Just talked about a rfkill command, in fact, through this command can be turned off the wireless or Bluetooth devices when necessary to save equipment power, to soft-shut the Bluetooth module as an example:
#关闭蓝牙模块
Rfkill Block 0 #0为设备ID号
#检测是否关闭
Rfkill List
0:hci0:bluetooth
Soft Blocked:yes
Hard Blocked:no
1:phy0:wireless LAN
Soft Blocked:no
Hard Blocked:no
#开启蓝牙模块
Rfkill unblock 0
#检测是否开启
Rfkill List
0:hci0:bluetooth
Soft Blocked:no
Hard Blocked:no
1:phy0:wireless LAN
Soft Blocked:no
Hard Blocked:no

4, written in the last

Each laptop wireless card or Bluetooth module device manufacturers are not the same, but the solution is the same way of thinking and methods, but the drive is different. The wood son here provides three commonly used network card manufacturer's drive Broadcom, Killer, Realtek.
Broadcom:https://github.com/winterheart/broadcom-bt-firmware
Killer:https://codeload.github.com/kvalo/ath10k-firmware/zip/master
Realtek:https://github.com/lwfinger/rtlwifi_new
The same Broadcom drive is stored in the/lib/firmware directory BRCM.
For Realtek to be different, you can download the corresponding driver and then execute the following command:
Make
sudo make install
sudo modprobe rtl8192de

Full use of Deepin Linux Entertainment, work, study (3)--Wireless card and Bluetooth device driver