No bluetooth on Dell XPS 7390 with AX200 after upgrade to 20.04

Bug #1893538 reported by Michael Still
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux-firmware (Ubuntu)
Confirmed
Undecided
Huang Dun

Bug Description

Hi, my Dell XPS 7390 worked just fine with Ubuntu 19.10, but after clean-install upgrading to 20.04 I don't have working bluetooth any more. The machine has an Intel AX200 installed. I'm not sure what details are helpful to provide, so here are some random things, happy to provide more if people can provide hints...

# uname -a
Linux marvin 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

# lspci
00:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem
00:14.0 USB controller: Intel Corporation Device 02ed
00:14.2 RAM memory: Intel Corporation Device 02ef
00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host Controller
00:15.1 Serial bus controller [0c80]: Intel Corporation Comet Lake Serial IO I2C Host Controller
00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface
00:1c.0 PCI bridge: Intel Corporation Device 02bc (rev f0)
00:1c.6 PCI bridge: Intel Corporation Device 02be (rev f0)
00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0)
00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Device 0284
00:1f.3 Audio device: Intel Corporation Device 02c8
00:1f.4 SMBus: Intel Corporation Device 02a3
00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller
01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)
02:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
05:00.0 System peripheral: Intel Corporation JHL6540 Thunderbolt 3 NHI (C step) [Alpine Ridge 4C 2016] (rev 02)
3b:00.0 USB controller: Intel Corporation JHL6540 Thunderbolt 3 USB Controller (C step) [Alpine Ridge 4C 2016] (rev 02)
71:00.0 Non-Volatile memory controller: Micron Technology Inc Device 5410 (rev 01)

# dmesg | grep iwl
[ 8.578338] iwlwifi 0000:02:00.0: enabling device (0000 -> 0002)
[ 8.594306] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-50.ucode failed with error -2
[ 8.594320] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-49.ucode failed with error -2
[ 8.597017] iwlwifi 0000:02:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17
[ 8.597019] iwlwifi 0000:02:00.0: Found debug destination: EXTERNAL_DRAM
[ 8.597020] iwlwifi 0000:02:00.0: Found debug configuration: 0
[ 8.597192] iwlwifi 0000:02:00.0: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm
[ 8.650489] iwlwifi 0000:02:00.0: Detected Killer(R) Wi-Fi 6 AX1650w 160MHz Wireless Network Adapter (200D2W), REV=0x340
[ 8.663161] iwlwifi 0000:02:00.0: Applying debug destination EXTERNAL_DRAM
[ 8.663495] iwlwifi 0000:02:00.0: Allocated 0x00400000 bytes for firmware monitor.
[ 8.829671] iwlwifi 0000:02:00.0: base HW address: 04:ed:33:c0:85:78
[ 8.846912] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0
[ 9.459653] iwlwifi 0000:02:00.0: Applying debug destination EXTERNAL_DRAM
[ 9.626499] iwlwifi 0000:02:00.0: FW already configured (0) - re-configuring

Revision history for this message
bmer (bmerchant8-0) wrote :

I have this issue too with the same laptop and found a workaround. There's a lot of discussion in bugs 1871794 and 1878194 about this (and possibly other Bluetooth chipsets).

It looks like the /lib/firmware/intel/ibt-* firmware and config files are somehow wrong and causing the issue.

This is the problematic log section

Oct 12 08:50:41 xxxxxxxx kernel: [ 8.616248] Bluetooth: hci0: Waiting for firmware download to complete
Oct 12 08:50:41 xxxxxxxx kernel: [ 8.616360] Bluetooth: hci0: Firmware loaded in 1494493 usecs
Oct 12 08:50:41 xxxxxxxx kernel: [ 8.616387] Bluetooth: hci0: Waiting for device to boot
Oct 12 08:50:41 xxxxxxxx kernel: [ 8.630437] Bluetooth: hci0: Device booted in 13726 usecs
Oct 12 08:50:41 xxxxxxxx kernel: [ 8.631010] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
Oct 12 08:50:41 xxxxxxxx kernel: [ 8.631437] Bluetooth: hci0: Failed to send Intel_Write_DDC (-22)

I copied all the /lib/firmware/intel/ibt-* files from an 18.04 installation, regenerated the initramfs, and rebooted. At first I thought it didn't work, but it turns out it doesn't reload the firmware and config on every boot, only, it seems, once a day. The next day I rebooted again and it loaded the firmware, but I didn't get the "Failed to send Intel_Write_DDC" error this time.

Oct 13 08:51:42 brad-XPS kernel: [ 8.651453] Bluetooth: hci0: Waiting for firmware download to complete
Oct 13 08:51:42 brad-XPS kernel: [ 8.652395] Bluetooth: hci0: Firmware loaded in 1506591 usecs
Oct 13 08:51:42 brad-XPS kernel: [ 8.652425] Bluetooth: hci0: Waiting for device to boot
Oct 13 08:51:42 brad-XPS kernel: [ 8.665356] Bluetooth: hci0: Device booted in 12636 usecs
Oct 13 08:51:42 brad-XPS kernel: [ 8.665485] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-firmware (Ubuntu):
status: New → Confirmed
Huang Dun (huangdun)
Changed in linux-firmware (Ubuntu):
assignee: nobody → Huang Dun (huangdun)
Revision history for this message
bmer (bmerchant8-0) wrote :

This is being fixed in 1905214. I've tested the focal-proposed package already and it appears to work fine.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.