戴尔XPS 13(9370)蓝牙问题


13

我的预装Ubuntu的新Dell XPS 13(9370)上的蓝牙模块存在以下问题。

蓝牙模块由于某种原因被禁用。蓝牙设备(键盘和鼠标)仅在工作过程中停止工作,蓝牙指示灯熄灭并且该模块也在rfkill列表中。

要使其恢复工作,我需要重新启动计算机,启动BIOS,禁用Bluetooth模块并重新启用它。之后,蓝牙模块再次可用。真烦人。

发生这种情况时我的系统日志:

Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB disconnect, device number 3
Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 22
Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch Status...
Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch Status.
Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root.
Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 21
Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers.
Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets.
Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths.
Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System.
Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default.
Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms.
Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSource
Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSink
Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default.
Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System.
Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets.
Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown.
Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths.
Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session...
Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers.
Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root.
Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 12120 (kill).
Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers.
Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets.
Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths.
Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System.
Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default.
Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms.
Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown.
Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session...
Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default.
Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System.
Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers.
Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths.
Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets.
Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 12133 (kill).
Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c11 of user root.
Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
Apr 11 12:25:46 visyu-albatross systemd[12140]: Reached target Sockets.
Apr 11 12:25:46 visyu-albatross systemd[12140]: Reached target Paths.
Apr 11 12:25:46 visyu-albatross systemd[12140]: Reached target Timers.
Apr 11 12:25:46 visyu-albatross systemd[12140]: Reached target Basic System.
Apr 11 12:25:46 visyu-albatross systemd[12140]: Reached target Default.
Apr 11 12:25:46 visyu-albatross systemd[12140]: Startup finished in 15ms.
Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
Apr 11 12:25:46 visyu-albatross systemd[12140]: Reached target Shutdown.
Apr 11 12:25:46 visyu-albatross systemd[12140]: Starting Exit the Session...
Apr 11 12:25:46 visyu-albatross systemd[12140]: Stopped target Default.
Apr 11 12:25:46 visyu-albatross systemd[12140]: Stopped target Basic System.
Apr 11 12:25:46 visyu-albatross systemd[12140]: Stopped target Paths.
Apr 11 12:25:46 visyu-albatross systemd[12140]: Stopped target Timers.
Apr 11 12:25:46 visyu-albatross systemd[12140]: Stopped target Sockets.
Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
Apr 11 12:25:46 visyu-albatross systemd[1]: user@0.service: Start request repeated too quickly.
Apr 11 12:25:46 visyu-albatross systemd[1]: Failed to start User Manager for UID 0.
Apr 11 12:25:46 visyu-albatross systemd[12140]: Received SIGRTMIN+24 from PID 12148 (kill).
Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c12 of user root.
Apr 11 12:25:46 visyu-albatross systemd[1]: Stopped User Manager for UID 0.
Apr 11 12:25:46 visyu-albatross systemd[1]: Removed slice User Slice of root.
Apr 11 12:25:47 visyu-albatross systemd[1]: Created slice User Slice of root.
Apr 11 12:25:47 visyu-albatross systemd[1]: Starting User Manager for UID 0...
Apr 11 12:25:47 visyu-albatross systemd[1]: Started Session c13 of user root.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Reached target Timers.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Reached target Sockets.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Reached target Paths.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Reached target Basic System.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Reached target Default.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Startup finished in 17ms.
Apr 11 12:25:47 visyu-albatross systemd[1]: Started User Manager for UID 0.
Apr 11 12:25:47 visyu-albatross systemd[1]: bluetooth.target: Unit not needed anymore. Stopping.
Apr 11 12:25:47 visyu-albatross systemd[1]: Stopped target Bluetooth.
Apr 11 12:25:47 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
Apr 11 12:25:47 visyu-albatross systemd[12167]: Reached target Shutdown.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Stopped target Default.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Stopped target Basic System.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Stopped target Timers.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Stopped target Paths.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Stopped target Sockets.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Starting Exit the Session...
Apr 11 12:25:47 visyu-albatross systemd[12167]: Received SIGRTMIN+24 from PID 12184 (kill).
Apr 11 12:25:47 visyu-albatross systemd[1]: Stopped User Manager for UID 0.
Apr 11 12:25:47 visyu-albatross systemd[1]: Removed slice User Slice of root.
Apr 11 12:25:48 visyu-albatross org.gnome.Terminal[2417]: ** (gnome-terminal-server:12197): WARNING **: Unable to set locale modifiers with XSetLocaleModifiers()

我已经尝试了不同的方法:

  1. 在中禁用TLP和为蓝牙禁用TLP /etc/default/tlp
  2. 将BIOS更新到版本1.2.1
  3. 将此行设置为ath10k的modprobe: echo "options ath10k_core skip_otp=y" > /etc/modprobe.d/ath10k.conf
  4. 更新linux-firmware软件包,如此处所述:https : //www.killernetworking.com/driver-downloads/kb/faq/1-killer-1535-1525-1435-in-ubuntu-debian

到目前为止,这些都没有帮助。

据我所知,它是以下硬件:QCA 6174 Killer Qualcomm / QCA 1535 Killer Qualcomm

通常,我将这两个蓝牙设备配对并连接:

  • 罗技K810键盘
  • Logitech MX Anywhere2鼠标

这看起来非常像硬件问题。
guntbert

@guntbert你为什么这么认为?
TIIUNDER

因为(以我的经验),当组件反复出现故障但在重启/重启后又恢复时,很少有其他原因。
guntbert

我在Archlinux中也遇到了同样的问题,所有内容也都进行了更新。如果我知道了,我会让你知道。
凯尔·麦吉尔

新信息:如前所述,重新启动无济于事,但关闭机器(关机)然后再次打开,即可重新启用Bluetooth模块,而无需进入BIOS。
TIIUNDER

Answers:


7

我也遇到了同样的问题,并且我认为使用最新的Windows驱动程序中包含的文件更新蓝牙固件可以改善此问题。我的MD5:

sonic@sonic-XPS-13-9370:/lib/firmware/qca$ md5sum *usb*302*
067fb95e8501bad2683df07d23539e7d  nvm_usb_00000302.bin
b3e2784b16b5b0cf5defa7eb9115956d  nvm_usb_00000302.bin_orig
c9d6334b547a92817458de10243f398c  rampatch_usb_00000302.bin
86c377ab7b2c24cc12cea5e79f71d610  rampatch_usb_00000302.bin_orig

顺便说一句,一个更简单的解决方法是拔下电源并执行挂起/恢复周期。
至少我的是1435年杀手。


更多信息将是很好。你从哪儿得到司机的?您如何使用驱动程序更新蓝牙固件的?
TIIUNDER

我得到了这个驱动程序:dell.com/support/home/de/de/dedhs1/drivers/…您甚至不需要Windows从.exe中提取固件,只需在Ubuntu中双击以启动Archive Manager,解压缩drivers/Production/Windows10-x64/Bluetooth_driver并用相应的MD5覆盖/lib/firmware/qca(备份后)。
Sven Killig '18

我现在已经尝试了好几天,而且似乎很有效
TIIUNDER

1
警告:我的Ubuntu刚刚安装了linux-firmware软件包的更新,该更新取消了我的更改。我的/etc/rc.local现在包含:echo bluetooth ; cp -p /opt/Bluetooth_driver/ramps_0x00000302_48.dfu /lib/firmware/qca/nvm_usb_00000302.bin ; cp -p /opt/Bluetooth_driver/AthrBT_0x00000302.dfu /lib/firmware/qca/rampatch_usb_00000302.bin
Sven Killig '18

顺便说一句:/etc/rc.local在默认情况下不可用,但在Ubuntu 18.04中仍然有效,当1)存在2)可执行3)以shebang
开头

6

在Ubuntu 18.04上更新Sven Killig对Dell XPS 9370的回答:

司机:

https://www.dell.com/support/home/uk/zh-CN/ukbsdt1/drivers/driversdetails?driverId=1JVK3

要覆盖的文件:

AthrBT_0x00000302.dfu (size 40876) -> rampatch_usb_00000302.bin (size 32940)
ramps_0x00000302_48.dfu (size 1982) -> nvm_usb_00000302.bin (size 1953)

复制后列出:

067fb95e8501bad2683df07d23539e7d  /lib/firmware/qca/nvm_usb_00000302.bin
b3e2784b16b5b0cf5defa7eb9115956d  /lib/firmware/qca/nvm_usb_00000302.bin.orig
47ed34d8b6af11d71036aa44314e32d3  /lib/firmware/qca/rampatch_usb_00000302.bin
86c377ab7b2c24cc12cea5e79f71d610  /lib/firmware/qca/rampatch_usb_00000302.bin.orig

1
我整理了一个脚本来自动修补文件:gist.github.com/jinnko/4b9af7dacb6e9841a63a76a78b14f4a8
JinnKo

0

另一个线程中,有报告说更新到较新的内核(4.17或更高版本)也可以解决该问题。

要在Ubuntu 18.04上执行此操作,请运行命令:sudo apt install linux-generic-hwe-18.04,然后重新启动。

我只是这样做而已;因此,如果它不起作用,我会报告。

我还可以确认,作为一种解决方法,挂起(Fn+ End[🌙])笔记本电脑,然后在拔掉电源的情况下将其唤醒,通常可以可靠地重新启用WiFi和蓝牙功能。


使用内核4.18.0-20-通用#21〜18.04.1-Ubuntu无法解决问题:(
JinnKo

0

找到了很多解决方案。只有一个工作!我使用的命令是

modprobe btusb && systemctl start bluetooth

您可能需要root权限。

我在这个论坛上找到它。

您可能已经知道,蓝牙在睡眠时会关闭/消失。为此,锻炼是添加一个脚本以在睡眠前关闭蓝牙,并在睡眠后重新打开蓝牙。

我将粘贴答案

只需将任何名称的可执行脚本放在/ lib / systemd / system-sleep /中。

#!/bin/sh
if [ "$1" = "pre" ]; then
  systemctl stop bluetooth && rmmod btusb
elif [ "$1" = "post" ]; then
  modprobe btusb && systemctl start bluetooth
fi

希望它也对您有用!

另外,仅供参考,这是我的系统信息。

系统信息


0

接受的解决方案对我不起作用(或者至少不能孤立地起作用)。dmesg关于缺少名称完全不同的固件文件存在错误。

我正在eoan(19.10)上,并在这里基于https://bbs.archlinux.org/viewtopic.php?id=198865找到一个解决方案。

下载链接很糟糕,所以我从https://drivers.softpedia.com/get/BLUETOOTH/Broadcom/Broadcom-Micro-size-USB-to-Bluetooth-Dongle-Driver-12011010-for-Windows-获得了CAB文件81-64-bit.shtml。您需要cabextract提取它。

那我要做

sudo hex2hcd BCM20702A1_001.002.014.1443.1572.hex -o /lib/firmware/brcm/BCM20702A1-0a5c-216f.hcd

然后重启


By using our site, you acknowledge that you have read and understand our Cookie Policy and Privacy Policy.
Licensed under cc by-sa 3.0 with attribution required.