Bluetooth Controller Not reconnecting can only do inital connection

Issues & Assistance Unsupported hardware | Dual boot
1

Hello I've got a DualSense controller (the PS5 controller) that I can do the initial pairing with my bluetooth just fine and it runs like you would want/expect it to. However whenever I either turn off the controller or turn off the pc and turn it back on I have to reconnect it and when I do it tries to but fails giving me the following error in the bluetooth system settings menu:
"br-connection-create-socket"
Does anyone know how to fix this its anoyying having to unpair and repair each time. Thank you for taking the time to read this and reach out! :smiley:

Oh and here is my system specs:

System:
Kernel: 6.0.8-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=8afab8b4-bd89-4267-9d65-f79cbafff52f rw rootflags=subvol=@
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
resume=UUID=667e1ff1-c5e6-4567-af3c-5544d0ad441d loglevel=3
Desktop: KDE Plasma v: 5.26.3 tk: Qt v: 5.15.7 wm: kwin_x11 vt: 1 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: ROG MAXIMUS X HERO (WI-FI AC) v: Rev 1.xx
serial: <superuser required> UEFI: American Megatrends v: 0802
date: 11/01/2017
CPU:
Info: model: Intel Core i7-8700K bits: 64 type: MT MCP arch: Coffee Lake
gen: core 8 level: v3 note: check built: 2018 process: Intel 14nm family: 6
model-id: 0x9E (158) stepping: 0xA (10) microcode: 0xF0
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 800 min/max: 800/4700 scaling: driver: intel_pstate
governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
8: 800 9: 800 10: 800 11: 800 12: 800 bogomips: 88796
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX unsupported
Type: l1tf mitigation: PTE Inversion
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: retbleed mitigation: IBRS
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: IBRS, IBPB: conditional, RSB filling,
PBRSB-eIBRS: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort mitigation: TSX disabled
Graphics:
Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
vendor: Gigabyte driver: amdgpu v: kernel arch: RDNA-1 code: Navi
process: TSMC n7 (7nm) built: 2019-20 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: DP-1,DP-2 empty: DP-3,HDMI-A-1 bus-ID: 03:00.0
chip-ID: 1002:731f class-ID: 0300
Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.5
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting,radeon
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x285mm (40.00x11.22")
s-diag: 1055mm (41.54")
Monitor-1: DP-1 mapped: DisplayPort-0 pos: left model: Asus VG248
serial: <filter> built: 2018 res: 1920x1080 hz: 60 dpi: 92 gamma: 1.2
size: 531x299mm (20.91x11.77") diag: 609mm (24") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
Monitor-2: DP-2 mapped: DisplayPort-1 pos: primary,right model: HP X24ih
serial: <filter> built: 2020 res: 1920x1080 dpi: 93 gamma: 1.2
size: 527x297mm (20.75x11.69") diag: 605mm (23.8") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 Mesa 22.2.3 renderer: AMD Radeon RX 5700 (navi10 LLVM
14.0.6 DRM 3.48 6.0.8-zen1-1-zen) direct render: Yes
Audio:
Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK
driver: snd_hda_intel bus-ID: 1-5:3 v: kernel bus-ID: 00:1f.3
chip-ID: 9886:0038 class-ID: 0300 chip-ID: 8086:a2f0 class-ID: 0403
Device-2: AMD Navi 10 HDMI Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab38
class-ID: 0403
Device-3: Creative Labs driver: snd_hda_intel v: kernel bus-ID: 06:00.0
chip-ID: 1102:0010 class-ID: 0403
Device-4: Astro Gaming MixAmp Pro type: USB
driver: hid-generic,snd-usb-audio,usbhid
Sound API: ALSA v: k6.0.8-zen1-1-zen running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.59 running: yes
Network:
Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter vendor: ASUSTeK
driver: rtw_8822be v: N/A modules: rtw88_8822be pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: d000 bus-ID: 08:00.0 chip-ID: 10ec:b822 class-ID: 0280
IF: wlp8s0 state: down mac: <filter>
Bluetooth:
Device-1: ASUSTek Bluetooth Radio type: USB driver: btusb v: 0.8
bus-ID: 1-13:5 chip-ID: 0b05:185c class-ID: e001 serial: <filter>
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 2.73 TiB used: 654.2 GiB (23.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: SSD 970 EVO Plus 1TB size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 2B2QEXM7 temp: 37.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 1B6Q scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 1B6Q scheme: GPT
Partition:
ID-1: / raw-size: 896.81 GiB size: 896.81 GiB (100.00%)
used: 342.82 GiB (38.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 608 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 896.81 GiB size: 896.81 GiB (100.00%)
used: 342.82 GiB (38.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 896.81 GiB size: 896.81 GiB (100.00%)
used: 342.82 GiB (38.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 896.81 GiB size: 896.81 GiB (100.00%)
used: 342.82 GiB (38.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 34.41 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
ID-2: swap-2 type: zram size: 31.28 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 31.0 C mobo: N/A gpu: amdgpu temp: 51.0 C
mem: 58.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Info:
Processes: 341 Uptime: 12m wakeups: 0 Memory: 31.28 GiB
used: 3.77 GiB (12.1%) Init: systemd v: 252 default: graphical
tool: systemctl Compilers: gcc: 12.2.0 Packages: pm: pacman pkgs: 1593
libs: 524 tools: pamac,paru Shell: fish v: 3.5.1 default: Bash v: 5.1.16
running-in: konsole inxi: 3.3.23
Garuda (2.6.9-1):
System install date:     2022-07-10
Last full system update: 2022-11-16
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       No/Undetected
Snapshots:               Snapper (maybe)
Failed units:
2

Check to see if it is related to this link-layer privacy issue.

From the ArchWiki:

Problems with all BLE devices on kernel 5.9+

Starting with v5.9, the kernel Bluetooth stack tries to use link-layer privacy on BLE connections. If the device works after pairing but does not survive a reboot or suspend, it is probably because of this.

To workaround [3] this issue, open /var/lib/bluetooth/adapter_mac/device_mac/info, remove the following lines, and restart bluetooth.service:

[IdentityResolvingKey]
Key=...

See the relevant discussion on the Arch forum.

3 Likes
3

I had to go out of town today but i should be back on Saturday to try this out to fix it. Thanks for the suggestion!! :smiley:

4

Ive tried this out and each time ive tried and it wont connect still unless i repair it again. Something to note is that the Key= number changed each time for whatever reason too.

5

I am interpreting that instruction to mean the lines should be completely removed, including the line that says [IdentityResolvingKey], and the entirety of the line below it (Key=blahblahblah). Is that what you are trying, and the two lines are being added back after you re-pair?

The wiki also says restart bluetooth.service:

sudo systemctl restart bluetooth.service

One person in the linked discussion noted restarting the service was insufficient, they had to fully reboot but then the issue was resolved.

2 Likes
6

So when I try to pull up the controllers info in the terminal this is what it looks like:

GNU nano 7.0 /var/lib/bluetooth/40:9F:38:A6:AD:C2/7C:66:EF:50:D5:A6/info
[General]
Name=Wireless Controller
Class=0x002508
SupportedTechnologies=BR/EDR;
Trusted=true
Blocked=false
WakeAllowed=true
Services=00001124-0000-1000-8000-00805f9b34fb;00001200-0000-1000-8000-00805f9b34fb;

[DeviceID]
Source=2
Vendor=1356
Product=3302
Version=256
Type=4
PINLength=0

[LinkKey]
Type=4
PINLength=0
Key=353D137F277444C9E00053ECABF67094

...and there is no "Identity resloving key" so im not sure if i did something wrong or not?

7

Have you tried alternate kernels yet?

Bluetooth connectivity breaks pretty regularly when the kernel is updated. I would recommend trying at least the LTS & mainline kernels, (sometimes trying 3 or 4 is required).

1 Like
8

Ill give it a shot and report back once i do!

1 Like
9

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.