Can't discover my bluetooth headphones

Hello all,
I am a total newbie to Linux but I have not been able to find a forum post or wiki resource to help me with my Dell XPS 13 not being able to even detect my bluetooth headphones. My laptop can recognized other devices, it works with my dualshock 3 but none of my headphones. Any help or resource is appreciated.

Kernel: 5.14.16-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=44a32cbf-aba4-4b1d-94a4-86b5d4a46482
rw [email protected] quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 loglevel=3
Desktop: KDE Plasma 5.23.3 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:   Type: Laptop System: Dell product: XPS 13 9343 v: N/A serial: <filter> Chassis: type: 9
serial: <filter>
Mobo: Dell model: 0TM99H v: A00 serial: <filter> UEFI: Dell v: A20 date: 06/06/2019
Battery:   ID-1: BAT0 charge: 13.7 Wh (59.1%) condition: 23.2/52.7 Wh (44.1%) volts: 7.5 min: 7.6
model: SMP DELL RWT1R43 type: Li-poly serial: <filter> status: Discharging
CPU:       Info: Dual Core model: Intel Core i5-5200U bits: 64 type: MT MCP arch: Broadwell family: 6
model-id: 3D (61) stepping: 4 microcode: 2F cache: L2: 3 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 17558
Speed: 2195 MHz min/max: 500/2700 MHz Core speeds (MHz): 1: 2195 2: 2195 3: 2211 4: 2195
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:  Device-1: Intel HD Graphics 5500 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0
chip-ID: 8086:1616 class-ID: 0300
Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 2-5:3
chip-ID: 0bda:5682 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org 1.21.1.1 compositor: kwin_x11 driver: loaded: intel
unloaded: modesetting alternate: fbdev,vesa display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 168 s-size: 290x170mm (11.4x6.7") s-diag: 336mm (13.2")
Monitor-1: eDP1 res: 1920x1080 dpi: 168 size: 290x170mm (11.4x6.7") diag: 336mm (13.2")
OpenGL: renderer: Mesa Intel HD Graphics 5500 (BDW GT2) v: 4.6 Mesa 21.2.4 direct render: Yes
Audio:     Device-1: Intel Broadwell-U Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:03.0
chip-ID: 8086:160c class-ID: 0403
Device-2: Intel Wildcat Point-LP High Definition Audio vendor: Dell driver: snd_hda_intel
v: kernel bus-ID: 00:1b.0 chip-ID: 8086:9ca0 class-ID: 0403
Sound Server-1: ALSA v: k5.14.16-zen1-1-zen running: yes
Sound Server-2: JACK v: 1.9.19 running: no
Sound Server-3: PulseAudio v: 15.0 running: no
Sound Server-4: PipeWire v: 0.3.39 running: yes
Network:   Device-1: Broadcom BCM4352 802.11ac Wireless Network Adapter vendor: Dell driver: wl v: kernel
modules: bcma bus-ID: 02:00.0 chip-ID: 14e4:43b1 class-ID: 0280
IF: wlp2s0 state: up mac: <filter>
Bluetooth: Device-1: Broadcom BCM20702A0 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 2-3:2
chip-ID: 0a5c:216f class-ID: fe01 serial: <filter>
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:    Local Storage: total: 238.47 GiB used: 38.49 GiB (16.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD PM851 M.2 2280 256GB size: 238.47 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 5D0Q
scheme: GPT
Partition: ID-1: / raw-size: 238.21 GiB size: 238.21 GiB (100.00%) used: 38.49 GiB (16.2%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.45%) used: 562 KiB (0.2%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 238.21 GiB size: 238.21 GiB (100.00%) used: 38.49 GiB (16.2%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 238.21 GiB size: 238.21 GiB (100.00%) used: 38.49 GiB (16.2%)
fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 238.21 GiB size: 238.21 GiB (100.00%) used: 38.49 GiB (16.2%)
fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:      Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 7.67 GiB used: 2 MiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:   System Temperatures: cpu: 65.0 C mobo: 46.0 C sodimm: SODIMM C
Fan Speeds (RPM): cpu: 0
Info:      Processes: 207 Uptime: 5m wakeups: 1 Memory: 7.67 GiB used: 2.84 GiB (37.0%) Init: systemd
v: 249 tool: systemctl Compilers: gcc: 11.1.0 clang: 12.0.1 Packages: pacman: 1442 lib: 444
Shell: fish v: 3.3.1 default: Bash v: 5.1.8 running-in: konsole inxi: 3.3.08

What kind of headphones are they? Have you been able to pair them with other things (your phone perhaps)?

Are you on 5.14 on purpose, or have you not updated in a while? I would start by doing the update (just type update into the terminal), then power off, wait a second, then boot back up and try to pair the headphones again.

2 Likes

They are Sony WH-1000XM4s. I can connect them to my phone no problem. I just updated the system but I still can't discover my headphones. The bluetooth address doesn't even show up when I try to add a new device.

Last kernel version is 5.16.1-zen1, please update first.

And welcome to the forum :slight_smile:

1 Like

Your headphones look like they do their first device pairing automatically, but after that you have to hold down the power button for seven seconds to get back into pairing mode for any additional devices.

Are you getting the headphones into the pairing mode, with the voice guidance and the blue light blinking and all?

2 Likes

Yeah that's what I've been doing.

Also test other kernels, Bluetooth breaks regularly on kernel updates. The LTS kernel is the first one you should try.

2 Likes

It sounds like Bluetooth is not broken, as his BT dualshock controller is working.

@tastickfan what's the output of dmesg | grep blue?

I've seen many cases in the past year where most Bluetooth devices were working fine, but BT headphones could not connect on a specific kernel, (yet another kernel it worked fine). Bluetooth functionality breaks quite regularly on kernel updates. That is why my first suggestion on many BT threads is to test alternate kernels.

2 Likes

You know what? That actually makes sense because the headphones are constantly being released with new bluetooth protocols, while a controller or mouse or something would probably just have plain ordinary BT.

From the Sony WH-1000XM4 website:

"LDAC transmits approximately three times more data (at the maximum transfer rate of 990 kbps) than conventional BLUETOOTH® audio..."

1 Like
dmesg: read kernel buffer failed: Operation not permitted

:point_up: Should be sudo.

1 Like
[    6.127771] Bluetooth: Core ver 2.22
[    6.127801] Bluetooth: HCI device and connection manager initialized
[    6.127806] Bluetooth: HCI socket layer initialized
[    6.127809] Bluetooth: L2CAP socket layer initialized
[    6.127814] Bluetooth: SCO socket layer initialized
[    6.373122] Bluetooth: hci0: BCM: chip id 63
[    6.373991] Bluetooth: hci0: BCM: features 0x07
[    6.389970] Bluetooth: hci0: ian-xps13
[    6.389976] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[    6.393759] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[    6.393763] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0a5c-216f.hcd'
[    6.393765] Bluetooth: hci0: BCM: 'brcm/BCM-0a5c-216f.hcd'
[    6.942377] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    6.942382] Bluetooth: BNEP filters: protocol multicast
[    6.942386] Bluetooth: BNEP socket layer initialized
[   11.278627] Bluetooth: RFCOMM TTY layer initialized
[   11.278636] Bluetooth: RFCOMM socket layer initialized
[   11.278642] Bluetooth: RFCOMM ver 1.11
[   62.254591] Bluetooth: hci0: BCM: chip id 63
[   62.255493] Bluetooth: hci0: BCM: features 0x07
[   62.271464] Bluetooth: hci0: ian-xps13
[   62.271471] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[   62.276910] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[   62.276914] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0a5c-216f.hcd'
[   62.276916] Bluetooth: hci0: BCM: 'brcm/BCM-0a5c-216f.hcd'
[  909.827772] Bluetooth: hci0: BCM: chip id 63
[  909.828858] Bluetooth: hci0: BCM: features 0x07
[  909.847886] Bluetooth: hci0: BCM20702A
[  909.847936] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[  909.851054] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[  909.851069] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0a5c-216f.hcd'
[  909.851070] Bluetooth: hci0: BCM: 'brcm/BCM-0a5c-216f.hcd'
[ 2091.508136] Bluetooth: hci0: BCM: chip id 63
[ 2091.509095] Bluetooth: hci0: BCM: features 0x07
[ 2091.529072] Bluetooth: hci0: BCM20702A
[ 2091.529098] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[ 2091.530137] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[ 2091.530144] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0a5c-216f.hcd'
[ 2091.530146] Bluetooth: hci0: BCM: 'brcm/BCM-0a5c-216f.hcd'
[ 4826.706880] Bluetooth: hci0: BCM: chip id 63
[ 4826.707977] Bluetooth: hci0: BCM: features 0x07
[ 4826.725980] Bluetooth: hci0: BCM20702A
[ 4826.726009] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[ 4826.726923] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[ 4826.726927] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0a5c-216f.hcd'
[ 4826.726929] Bluetooth: hci0: BCM: 'brcm/BCM-0a5c-216f.hcd'
[ 5080.774802] Bluetooth: hci0: BCM: chip id 63
[ 5080.775689] Bluetooth: hci0: BCM: features 0x07
[ 5080.791693] Bluetooth: hci0: BCM20702A
[ 5080.791699] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[ 5080.792753] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[ 5080.792765] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0a5c-216f.hcd'
[ 5080.792766] Bluetooth: hci0: BCM: 'brcm/BCM-0a5c-216f.hcd'

The error message below could mean you have firmware issues:

Your BCM20702A1 bluetooth chip requires installation of one of these proprietary firmware packages:

or:

Reinstall whichever of the broadcom firmware package above you are using, and then reboot. If there is no improvement after re-installation, then uninstall whichever package you are currently using, and then install the alternate firmware package I have listed. Reboot after the new firmware package has been installed.


You should also ensure your bios is up to date.


We are now on post 14 of your help request, and you have still not responded to the first question/suggestion put to you on post 2.

This query was put to you a day ago on the first response on this thread. Since then, several moderators (@SGS and myself) have asked you to update your system and install an alternate kernel. You have responded 4 times since these suggestions were put to you. In none of your 4 responses since yesterday have you confirmed if you have implemented the suggestions put to you by 3 different forum assistants.

I realize you are new to Linux, but this behavior is simply unacceptable on our forum. If you want help, you are expected to provide full feedback to any and all questions and suggestions put to you. This is just common courtesy, but that is not the main reason for this expectation. Your issue will, likely never get resolved (or it will take far longer) if you fail to confirm what you have tested and the results of all troubleshooting suggestions.

If your next post on this thread does not contain information on whether you have fully updated your system and tested at least the LTS kernel, (preferably others as well) your thread will be locked (as this thread is pointless without proper feedback from you). I have also given you new suggestions in this post, please provide feedback on my new suggestions as soon as you get a chance to test them out.

I appreciate the fact you are new here, but you are still expected to be cooperative with forum assistants, regardless of how inexperienced you are.

4 Likes

nah I just forgot to update. I'm still learning Linux.

My apologies. Please forgive my lack of response. I truly appreciate everyone's help and patience. I'm learning as I go and will be more thorough and consistent with my forum activity in the future. I updated my firmware, installed the two firmware updates with no luck. I'm going to try the LTS Kernel now.

sudo dmesg | grep Bluetooth
[    6.174245] Bluetooth: Core ver 2.22
[    6.174274] Bluetooth: HCI device and connection manager initialized
[    6.174278] Bluetooth: HCI socket layer initialized
[    6.174281] Bluetooth: L2CAP socket layer initialized
[    6.174286] Bluetooth: SCO socket layer initialized
[    6.373045] Bluetooth: hci0: BCM: chip id 63
[    6.374362] Bluetooth: hci0: BCM: features 0x07
[    6.390504] Bluetooth: hci0: ian-xps13
[    6.390509] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[    6.391887] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[    6.391890] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0a5c-216f.hcd'
[    6.391891] Bluetooth: hci0: BCM: 'brcm/BCM-0a5c-216f.hcd'
[    6.991826] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    6.991830] Bluetooth: BNEP filters: protocol multicast
[    6.991836] Bluetooth: BNEP socket layer initialized
[   11.268833] Bluetooth: RFCOMM TTY layer initialized
[   11.268840] Bluetooth: RFCOMM socket layer initialized
[   11.268855] Bluetooth: RFCOMM ver 1.11
1 Like

Ok I tried the LTS Kernel to no avail. I'm not sure if I updated my bluetooth firmware correctly though. I think this might be a lost cause in that my laptop's bluetooth module is too old for my headphones. I really appreciate everyone's time and help.

Kernel: 5.15.16-1-lts x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
root=UUID=44a32cbf-aba4-4b1d-94a4-86b5d4a46482 rw [email protected]
quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 loglevel=3
Desktop: KDE Plasma 5.23.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11
vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Laptop System: Dell product: XPS 13 9343 v: N/A
serial: <superuser required> Chassis: type: 9 serial: <superuser required>
Mobo: Dell model: 0TM99H v: A00 serial: <superuser required> UEFI: Dell
v: A20 date: 06/06/2019
Battery:
ID-1: BAT0 charge: 7.8 Wh (33.6%) condition: 23.2/52.7 Wh (44.1%)
volts: 7.4 min: 7.6 model: SMP DELL RWT1R43 type: Li-poly serial: <filter>
status: Discharging
CPU:
Info: model: Intel Core i5-5200U bits: 64 type: MT MCP arch: Broadwell
family: 6 model-id: 0x3D (61) stepping: 4 microcode: 0x2F
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
L3: 3 MiB desc: 1x3 MiB
Speed (MHz): avg: 2193 high: 2195 min/max: 500/2700 scaling:
driver: intel_cpufreq governor: performance cores: 1: 2195 2: 2189 3: 2195
4: 2195 bogomips: 17558
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel HD Graphics 5500 vendor: Dell driver: i915 v: kernel
bus-ID: 00:02.0 chip-ID: 8086:1616 class-ID: 0300
Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo
bus-ID: 2-5:3 chip-ID: 0bda:5682 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org 1.21.1.3 compositor: kwin_x11 driver:
loaded: intel unloaded: modesetting alternate: fbdev,vesa display-ID: :0
screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2")
s-diag: 582mm (22.9")
Monitor-1: eDP1 res: 1920x1080 dpi: 168 size: 290x170mm (11.4x6.7")
diag: 336mm (13.2")
Message: Unable to show advanced data. Required tool glxinfo missing.
Audio:
Device-1: Intel Broadwell-U Audio vendor: Dell driver: snd_hda_intel
v: kernel bus-ID: 00:03.0 chip-ID: 8086:160c class-ID: 0403
Device-2: Intel Wildcat Point-LP High Definition Audio vendor: Dell
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:9ca0
class-ID: 0403
Sound Server-1: ALSA v: k5.15.16-1-lts running: yes
Sound Server-2: PulseAudio v: 15.0 running: no
Sound Server-3: PipeWire v: 0.3.43 running: yes
Network:
Device-1: Broadcom BCM4352 802.11ac Wireless Network Adapter vendor: Dell
driver: N/A modules: bcma bus-ID: 02:00.0 chip-ID: 14e4:43b1 class-ID: 0280
Bluetooth:
Device-1: Broadcom BCM20702A0 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 2-3:2 chip-ID: 0a5c:216f class-ID: fe01 serial: <filter>
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 238.47 GiB used: 50.29 GiB (21.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Samsung
model: SSD PM851 M.2 2280 256GB size: 238.47 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter>
rev: 5D0Q scheme: GPT
Partition:
ID-1: / raw-size: 238.21 GiB size: 238.21 GiB (100.00%)
used: 50.29 GiB (21.1%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.45%)
used: 562 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 238.21 GiB size: 238.21 GiB (100.00%)
used: 50.29 GiB (21.1%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 238.21 GiB size: 238.21 GiB (100.00%)
used: 50.29 GiB (21.1%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 238.21 GiB size: 238.21 GiB (100.00%)
used: 50.29 GiB (21.1%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 7.67 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 63.0 C pch: 59.0 C mobo: 47.0 C sodimm: SODIMM C
Fan Speeds (RPM): cpu: 3581
Info:
Processes: 193 Uptime: 0m wakeups: 1 Memory: 7.67 GiB
used: 1.63 GiB (21.2%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.1.0 clang: 13.0.0 Packages: 1476 pacman: 1468 lib: 448 flatpak: 8
Shell: fish v: 3.3.1 default: Bash v: 5.1.16 running-in: konsole
inxi: 3.3.12

╭─[email protected] in ~ took 1s
╰─λ sudo dmesg | grep Bluetooth
[sudo] password for ian:
[   10.356584] Bluetooth: Core ver 2.22
[   10.356610] Bluetooth: HCI device and connection manager initialized
[   10.356614] Bluetooth: HCI socket layer initialized
[   10.356617] Bluetooth: L2CAP socket layer initialized
[   10.356622] Bluetooth: SCO socket layer initialized
[   11.056246] Bluetooth: hci0: BCM: chip id 63
[   11.057238] Bluetooth: hci0: BCM: features 0x07
[   11.073239] Bluetooth: hci0: ian-xps13
[   11.073244] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[   11.243971] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[   11.243977] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0a5c-216f.hcd'
[   11.243979] Bluetooth: hci0: BCM: 'brcm/BCM-0a5c-216f.hcd'
[   12.063891] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   12.063896] Bluetooth: BNEP filters: protocol multicast
[   12.063901] Bluetooth: BNEP socket layer initialized
[   16.921155] Bluetooth: RFCOMM TTY layer initialized
[   16.921163] Bluetooth: RFCOMM socket layer initialized
[   16.921168] Bluetooth: RFCOMM ver 1.11

It does look like there is a BIOS update (October 2019) for your laptop you can install. It's kind of a hail mary for the BT issue, but it looks like a security patch so you should probably do it anyway when you get a chance.

https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=w5c0w&oscode=wt64a&productcode=xps-13-9343-laptop

2 Likes

This is what Wine dumped out at me. Am I reading this right that the update is in 32-bit for a 64-bit CPU?

Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x004352a8).
Register dump:
 CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
 EIP:004352a8 ESP:0032fbcc EBP:0032fea0 EFLAGS:00010246(  R- --  I  Z- -P- )
 EAX:00000000 EBX:00000000 ECX:68c8aa52 EDX:80000000
 ESI:00000001 EDI:0032fc04
Stack dump:
0x0032fbcc:  00464088 00000000 0032fbe0 004356ab
0x0032fbdc:  00000000 00000000 004356db 00000000
0x0032fbec:  00000000 7ffd1000 cbcac9c8 cfcecdcc
0x0032fbfc:  d3d2d100 00c71590 00000000 00000000
0x0032fc0c:  00000000 00466778 00000000 00000000
0x0032fc1c:  00000000 0046d620 1b1a1918 00000001
Backtrace:
=>0 0x004352a8 in 9343_a20 (+0x352a8) (0x0032fea0)
  1 0x0044999d in 9343_a20 (+0x4999d) (0x0032ff30)
  2 0x7b62dd50 ActivateActCtx+0x23440() in kernel32 (0x0032ff48)
  3 0x7bc57857 A_SHAFinal+0x37ee7() in ntdll (0x0032ff5c)
  4 0x7bc57f10 A_SHAFinal+0x385a0() in ntdll (0x0032ffec)
0x004352a8 9343_a20+0x352a8: movl	0x0(%eax),%ecx
Modules:
Module	Address			Debug info	Name (15 modules)
PE	00400000-00475000	Export          9343_a20
PE	61740000-61782000	Deferred        advapi32
PE	62fc0000-6304d000	Deferred        rpcrt4
PE	63480000-6348c000	Deferred        version
PE	66b00000-66b3e000	Deferred        win32u
PE	6a280000-6a32c000	Deferred        msvcrt
PE	6bc00000-6bc2c000	Deferred        sechost
PE	6bcc0000-6bd3f000	Deferred        setupapi
PE	6c9c0000-6ca46000	Deferred        gdi32
PE	6ed00000-6ef3e000	Deferred        user32
PE	70b40000-70c17000	Deferred        ucrtbase
PE	71200000-7121c000	Deferred        imm32
PE	7b000000-7b0e9000	Deferred        kernelbase
PE	7b600000-7b81a000	Dwarf           kernel32
PE	7bc00000-7bca2000	Dwarf           ntdll
Threads:
process  tid      prio (all id:s are in hex)
00000038 services.exe
	0000003c    0
	00000040    0
	0000004c    0
	00000050    0
	0000006c    0
	0000007c    0
	000000a8    0
	000000c0    0
	000000d8    0
	00000110    0
00000044 winedevice.exe
	00000048    0
	00000054    0
	00000058    0
	0000005c    0
	00000060    0
	000000cc    0
00000064 winedevice.exe
	00000068    0
	00000070    0
	00000074    0
	00000078    0
	00000088    0
	0000008c    0
	00000090    0
00000080 explorer.exe
	00000084    0
	0000009c    0
	000000a0    0
00000094 plugplay.exe
	00000098    0
	000000ac    0
	000000b0    0
	000000b4    0
000000b8 svchost.exe
	000000bc    0
	000000c4    0
	000000c8    0
000000d0 rpcss.exe
	000000d4    0
	000000dc    0
	000000e0    0
	000000e4    0
	000000e8    0
	000000ec    0
	000000f0    0
000000fc (D) Z:\tmp\mozilla_ian0\9343_A20.exe
	00000100    0 <==
	00000124    0
00000108 winedevice.exe
	0000010c    0
	00000114    0
	00000118    0

System information:
    Wine build: wine-7.0-rc5
    Platform: i386 (WOW64)
    Version: Windows 7
    Host system: Linux
    Host version: 5.16.2-zen1-1-zen

Wine? What are you doing with Wine?

I'm not sure what that output is. What are you trying to do?

Edit:

Is that the BIOS update? That update cannot be installed in Linux, you have to go into the UEFI BIOS menu and install it there.

First you need to format a flash drive as FAT32 and save the update file (uncompressed) on the flash drive. Then reboot your machine, and the moment you see the Dell logo pop up you hit F12 to get into the UEFI BIOS menu.

There should be an option in the menu called "BIOS flash" or "BIOS update", something along those lines. You may have to disable secure boot to get into it (you can disable secure boot from the BIOS menu as well, it may be on a different screen). Also it might insist that you plug in your laptop before it lets you do the update.

With any luck, your BIOS will be nice and modern and recognize what you are doing and try to help you. I've never had that experience; if yours looks anything like mine you will see a kind of bizarre looking, super basic file manager where you can navigate into a few folders to look for the update file you saved to the disk. On mine the drives were named fs0, fs1, fs2, etc and my EFI partition was on there along with the flash drive. I think any FAT32 partitions it can find will be in there. Just look around until you find the file, it should be all by itself and not buried in any folders or anything (heads-up: it might be named differently than you remember).

Once you find it and confirm you want to update you should be all set.

1 Like