[SOLVED] Could someone help me troubleshoot my DualShock 4 controller? :(

[MandSpades]

So, I bought a PS4 controller on a nearby shop, an official one at that, and have been trying to make it work. Initially it would pllug, light up the yellow light on the controller and then do absolutely nothing and not get recognized by Steam.

After attempting to follow this guide though I don't know how well I followed it, I now... have managed to get my controller to STILL not be recognized by Steam, but at least audio works when I plug my earphone on it! So clearly something must have changed, but IDK how much.

Can somebody with a deeper understanding of the ways of Linux help me troubleshoot this and find out confused is going on?

If this helps, I did not reboot the PC as the guide asks (as a matter of fact, my PC has been on for seven days as of right now, Neofetch tells me as much) but did run the command that was supposed to make that unnecessary. I'm also running the Flatpak version of Steam and it's possible that everyone else was running the non-Flatpak version, but I have both installed and that one didn't recognize it either!

I am willing to dump any diagnostic results necessary, just gimme the terminal commands or whatever and I'll cooperate. I just really want to get my games running!

EDIT: SOLUTIONS BELOW!! THERE ARE TWO POSSIBLE SOLUTIONS ONE MAY USE FOR THIS PROBLEM!

1. Update the kernel to 6.2.0 using Mainline
2. Download sc-controller from github as an AppImage and force Linux to think your DualShock is an XBox controller

[MandSpades]

Bump...?
I actually don't know if I'm allowed to bump on this thread.
Please help.

[MandSpades]

I made a post in what I thought was the correct board for this, but I guess it isn't since nobody whatsoever showed up to help. So could somebody help me?

So, I bought a PS4 controller on a nearby shop, an official one at that, and have been trying to make it work. Initially it would pllug, light up the yellow light on the controller and then do absolutely nothing and not get recognized by Steam.

After attempting to follow this guide though I don't know how well I followed it, I now... have managed to get my controller to STILL not be recognized by Steam, but at least audio works when I plug my earphone on it! So clearly something must have changed, but IDK how much.

Can somebody with a deeper understanding of the ways of Linux help me troubleshoot this and find out confused is going on?

If this helps, I did not reboot the PC as the guide asks (as a matter of fact, my PC has been on for seven days as of right now, Neofetch tells me as much) but did run the command that was supposed to make that unnecessary. I'm also running the Flatpak version of Steam and it's possible that everyone else was running the non-Flatpak version, but I have both installed and that one didn't recognize it either!

I am willing to dump any diagnostic results necessary, just gimme the terminal commands or whatever and I'll cooperate. I just really want to get my games running!

[SMG]

Moderator note: Duplicate topics merged.

I made a post in what I thought was the correct board for this, but I guess it isn't since nobody whatsoever showed up to help.

Please follow forum rules and [8] Do Not Cross-Post. Create only one topic for an issue.

Also in the forum rules are instructions for [10] Bumping.

• Posting one word to bump a topic is generally discouraged. Try to research the problem and be patient for a solution. If nobody has responded within 48 hours, you may bump the topic to promote attention.
• To bump a topic, scroll to the bottom of the topic and click Bump topic, by Board index, Subscribe topic, and Bookmark topic (the Bump topic link will appear 48 hours after the last response).

Your topic is not even 24 hours old so the Bump topic option is not yet available. Give people a chance to respond.

[MandSpades]

Sorry... But that means that this is the correct board to post this on, right?!

I got weirded out by the fact I usually get instant replies and this time it took 1day+ and there's still nobody around.

[SMG]

Sorry... But that means that this is the correct board to post this on, right?!

I'll move the topic to Gaming because you mention the problem is getting it to work with Steam.

I got weirded out by the fact I usually get instant replies and this time it took 1day+ and there's still nobody around.

There might be only a limited number of people with a DualShock 4 controller. And maybe some only have time on the weekends to help. It really depends on the question and who is available as to how fast you might receive a response.

[MandSpades]

I see! Thanks. That explains why they're taking quite a while to show up. :C

[SMG]

I see! Thanks. That explains why they're taking quite a while to show up. :C

Did you try searching the forum for Dualshock? I found several topics. Maybe something in one of those will help. If not, you should probably provide more information about your install.
<SOLVED> DualShock 4 not working
Upgraded to LM 21 - Now unable to pair DualShock 4 controller

[MiZoG]

Post the output inxi -Fxxxrza. Use "Code" tags (the </> symbol in your message toolbar).
You haven't told us yet: your controller is connected via usb or bluetooth?
Is it recognized outside Steam? In Supertuxkart or other open-source n free game you might be inclined to install and test...
The official deb installer from steam has always worked great for me on Linux MInt BTW.
Perhaps -don't really know- you have to give extra permissions to Steam flatpak with a tool like flatseal.
But, first, you have to make sure the controller is detected by the system.

[MandSpades]

Post the output inxi -Fxxxrza. Use "Code" tags (the </> symbol in your message toolbar).
You haven't told us yet: your controller is connected via usb or bluetooth?

It's connected by USB (USB-A to Micro USB). Here goes the dump:

Code: Select all

System:
  Kernel: 6.0.0-1014-oem x86_64 bits: 64 compiler: N/A
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1014-oem
    root=UUID=461cf3d8-5837-4113-96a6-c432363bc34e ro
    resume=UUID=461cf3d8-5837-4113-96a6-c432363bc34e resume_offset=31948800
    quiet splash
  Desktop: Cinnamon 5.6.8 tk: GTK 3.24.33 wm: muffin dm: LightDM 1.30.0
    Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: TUF GAMING A520M-PLUS II v: Rev X.0x
    serial: <superuser required> UEFI: American Megatrends v: 2811
    date: 01/04/2023
CPU:
  Info: model: AMD Ryzen 5 5500 bits: 64 type: MT MCP arch: Zen 3
    family: 0x19 (25) model-id: 0x50 (80) stepping: 0 microcode: 0xA50000D
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
    L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 3535 high: 4217 min/max: 400/4267 boost: enabled
    scaling: driver: amd-pstate governor: schedutil cores: 1: 3518 2: 4199
    3: 3374 4: 3373 5: 3373 6: 3373 7: 3499 8: 4217 9: 3374 10: 3374 11: 3374
    12: 3374 bogomips: 86244
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  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: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: always-on, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Navi 23 [Radeon RX 6600/6600 XT/6600M] vendor: ASRock
    driver: amdgpu v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
    active: DP-1 empty: DP-2,DP-3,HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:73ff
    class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati
    unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu 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: DisplayPort-0 mapped: DP-1 model: MO-HSN-24C serial: <filter>
    built: 2021 res: 1920x1080 dpi: 92 gamma: 1.2 size: 530x300mm (20.9x11.8")
    diag: 609mm (24") ratio: 16:9 modes: max: 1920x1080 min: 720x400
  OpenGL:
    renderer: AMD Radeon RX 6600 (navi23 LLVM 15.0.6 DRM 3.48 6.0.0-1014-oem)
    v: 4.6 Mesa 22.2.5 direct render: Yes
Audio:
  Device-1: AMD Navi 21 HDMI Audio [Radeon RX 6800/6800 XT / 6900 XT]
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 03:00.1 chip-ID: 1002:ab28 class-ID: 0403
  Device-2: AMD Renoir Radeon High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 0b:00.1 chip-ID: 1002:1637
    class-ID: 0403
  Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s bus-ID: 0b:00.6 chip-ID: 1022:15e3 class-ID: 0403
  Device-4: Sony DualShock 4 [CUH-ZCT2x] type: USB
    driver: snd-usb-audio,usbhid bus-ID: 1-3:13 chip-ID: 054c:09cc
    class-ID: 0300 serial: <filter>
  Sound Server-1: ALSA v: k6.0.0-1014-oem running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 09:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: enp9s0 state: down mac: <filter>
  Device-2: TP-Link Archer T4U ver.3 type: USB driver: rtl88x2bu
    bus-ID: 5-2:2 chip-ID: 2357:0115 class-ID: 0000 serial: <filter>
  IF: wlxd03745d29f99 state: up mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
  IF-ID-2: wg-mullvad state: unknown speed: N/A duplex: N/A mac: N/A
Drives:
  Local Storage: total: 476.94 GiB used: 307.5 GiB (64.5%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 model: NVME SSD 512GB size: 476.94 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4
    type: SSD serial: <filter> rev: VC0S036H temp: 39.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 476.44 GiB size: 467.89 GiB (98.21%)
    used: 307.49 GiB (65.7%) fs: ext4 block-size: 4096 B dev: /dev/nvme0n1p2
    maj-min: 259:2
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
    used: 6.1 MiB (1.2%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1
    maj-min: 259:1
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 20 GiB used: 5.2 MiB (0.0%) priority: -2
    file: /swapfile
Sensors:
  System Temperatures: cpu: N/A mobo: N/A gpu: amdgpu temp: 54.0 C
    mem: 58.0 C
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Repos:
  Packages: 2894 apt: 2867 lib: 1448 flatpak: 27
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/danielrichter2007-grub-customizer-jammy.list
    1: deb [arch=amd64 signed-by=/etc/apt/keyrings/danielrichter2007-grub-customizer-jammy.gpg] https://ppa.launchpadcontent.net/danielrichter2007/grub-customizer/ubuntu jammy main
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
    1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb https://mirror.ufam.edu.br/linuxmint-packages vera main upstream import backport
    2: deb https://mirror.uepg.br/ubuntu jammy main restricted universe multiverse
    3: deb https://mirror.uepg.br/ubuntu jammy-updates main restricted universe multiverse
    4: deb https://mirror.uepg.br/ubuntu jammy-backports main restricted universe multiverse
    5: deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  Active apt repos in: /etc/apt/sources.list.d/librewolf.sources
    1: deb [arch=amd64] https://deb.librewolf.net vera main
  Active apt repos in: /etc/apt/sources.list.d/winehq-jammy.sources
    1: deb [arch=amd64 i386] https://dl.winehq.org/wine-builds/ubuntu jammy main
  Active apt repos in: /etc/apt/sources.list.d/winehq-kinetic.sources
    1: deb [arch=amd64 i386] https://dl.winehq.org/wine-builds/ubuntu kinetic main
Info:
  Processes: 376 Uptime: 2d 41m wakeups: 0 Memory: 15.42 GiB
  used: 4.84 GiB (31.4%) Init: systemd v: 249 runlevel: 5 tool: systemctl
  Compilers: gcc: 11.3.0 alt: 11/12 Shell: Bash v: 5.1.16
  running-in: gnome-terminal inxi: 3.3.13

Is it recognized outside Steam? In Supertuxkart or other open-source n free game you might be inclined to install and test...
The official deb installer from steam has always worked great for me on Linux MInt BTW.

It prevents all audio output from anywhere else and allows me to listen to stuff like YouTube videos only through the controller. Does this already count? I'll download the game now.
Edit: I download the .tar.xz directly from the site. The controller doesn't get recognized!

Perhaps -don't really know- you have to give extra permissions to Steam flatpak with a tool like flatseal.
But, first, you have to make sure the controller is detected by the system.

Will download this as well, right now!
Edit: Downloaded this one. Weirdly enough, GPU acceleration seems to be DISABLED on my Steam client? o_O It sure works for the games lmao
Idk what to change, though. Also, it doesn't pick up on my dark theme ç-ç

[MiZoG]

According to Arch wiki you have to "connect your controller via USB and press the PS button" (emphasis mine - PS Button is something you haven't mentioned so far)

Perhaps you should start with a clean slate by removing/disabling the script you have already tried to apply.

There are some people that fault their cables but the idea is that the PS4 controller should work OOB.

It prevents all audio output from anywhere else and allows me to listen to stuff like YouTube videos only through the controller. Does this already count?

It does not necessarily count. Anyway configure preferred audio output in your sound settings. Pavucontrol, if you install it, will perhaps give you more control over your audio output channels.

Steam in any variant is not the most optimized application on Linux for sure.

Irrelevant to your current issue:
Remove winehq repo for Ubuntu Kinetic! sudo rm -fv /etc/apt/sources.list.d/winehq-kinetic.sources
And FYI Grub Customizer: why you shouldn't use it. But don't go uninstall it for now.

[MandSpades]

According to Arch wiki you have to "connect your controller via USB and press the PS button" (emphasis mine - PS Button is something you haven't mentioned so far)

Perhaps you should start with a clean slate by removing/disabling the script you have already tried to apply.

Uh, should I just delete the file it created? I think all it does is create that file... I think. The script is linked on the first post of this thread.
Also, I did press the PS button. It really doesn't seem to do anything at all.

There are some people that fault their cables but the idea is that the PS4 controller should work OOB.

It prevents all audio output from anywhere else and allows me to listen to stuff like YouTube videos only through the controller. Does this already count?

It does not necessarily count. Anyway configure preferred audio output in your sound settings. Pavucontrol, if you install it, will perhaps give you more control over your audio output channels.

Steam in any variant is not the most optimized application on Linux for sure.

Oh. Okay. Will install it now.
Edit: Installed. I now have the Dualshock 4 on and it gets recognized as an audio device but is not in use.

Irrelevant to your current issue:
Remove winehq repo for Ubuntu Kinetic! sudo rm -fv /etc/apt/sources.list.d/winehq-kinetic.sources
And FYI Grub Customizer: why you shouldn't use it. But don't go uninstall it for now.

Removed!

[MandSpades]

So, what do I do now? Delete the files? And...?

[MandSpades]

Bruh, I even bumped this on the weekend and nobody showed up x-x I wonder if something happened.

[SMG]

Does the controller show up if you run xinput and lsusb?

This web article How to Set Up and Use Game Controllers on Linux and the first link I provided earlier both mention using bluetooth instead of the usb cable. I don't know what might be different about that unless the usb is not showing in the data I requested.

[MandSpades]

Does the controller show up if you run xinput and lsusb?

This web article How to Set Up and Use Game Controllers on Linux and the first link I provided earlier both mention using bluetooth instead of the usb cable. I don't know what might be different about that unless the usb is not showing in the data I requested.

Sorry I took long to respond. Will soon try out this article.

Here's xinput before plugging on the controller:

Code: Select all

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ SEMICO USB Keyboard Consumer Control    	id=9	[slave  pointer  (2)]
⎜   ↳ SINOWEALTH Mouse Gamer Husky Frost      	id=12	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Power Button                            	id=7	[slave  keyboard (3)]
    ↳ SEMICO USB Keyboard                     	id=8	[slave  keyboard (3)]
    ↳ SEMICO USB Keyboard System Control      	id=10	[slave  keyboard (3)]
    ↳ SEMICO USB Keyboard                     	id=11	[slave  keyboard (3)]
    ↳ SINOWEALTH Mouse Gamer Husky Frost Keyboard	id=13	[slave  keyboard (3)]
    ↳ Eee PC WMI hotkeys                      	id=14	[slave  keyboard (3)]
    ↳ SEMICO USB Keyboard Consumer Control    	id=15	[slave  keyboard (3)]

Here's xinput after plugging on the controller:

Code: Select all

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ SEMICO USB Keyboard Consumer Control    	id=9	[slave  pointer  (2)]
⎜   ↳ SINOWEALTH Mouse Gamer Husky Frost      	id=12	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Power Button                            	id=7	[slave  keyboard (3)]
    ↳ SEMICO USB Keyboard                     	id=8	[slave  keyboard (3)]
    ↳ SEMICO USB Keyboard System Control      	id=10	[slave  keyboard (3)]
    ↳ SEMICO USB Keyboard                     	id=11	[slave  keyboard (3)]
    ↳ SINOWEALTH Mouse Gamer Husky Frost Keyboard	id=13	[slave  keyboard (3)]
    ↳ Eee PC WMI hotkeys                      	id=14	[slave  keyboard (3)]
    ↳ SEMICO USB Keyboard Consumer Control    	id=15	[slave  keyboard (3)]

And here's lsusb before plugging on the controller:

Code: Select all

Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 002: ID 2357:0115 TP-Link Archer T4U ver.3
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 258a:1007 SINOWEALTH Mouse Gamer Husky Frost
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 1a2c:4c5e China Resource Semico Co., Ltd USB Keyboard
Bus 001 Device 002: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

And lsusb AFTER plugging on the controller:

Code: Select all

Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 002: ID 2357:0115 TP-Link Archer T4U ver.3
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 258a:1007 SINOWEALTH Mouse Gamer Husky Frost
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 1a2c:4c5e China Resource Semico Co., Ltd USB Keyboard
Bus 001 Device 007: ID 054c:09cc Sony Corp. DualShock 4 [CUH-ZCT2x]
Bus 001 Device 002: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[SMG]

I found this Dualshock 4 controller (Wired/USB): shows up in lsusb, but not in /dev/input - on both of my arch setups where someone found they bought a fake controller. However, it appears they have a slightly different model based on the lsusb info.

I did a search on your info and found this HID Bluetooth device fails to connect However, I also found Does not support model CUH-ZCT2E #164 which indicates a patch is needed if connecting through usb. (Patch is not needed if connecting through bluetooth.)

This information indicates one must configure the controller in Steam, but I don't know if that info is still valid.

All I am finding are people connecting successfully through bluetooth. I don't know if that is a possible option for you.

[MandSpades]

I found this Dualshock 4 controller (Wired/USB): shows up in lsusb, but not in /dev/input - on both of my arch setups where someone found they bought a fake controller. However, it appears they have a slightly different model based on the lsusb info.

I did a search on your info and found this HID Bluetooth device fails to connect However, I also found Does not support model CUH-ZCT2E #164 which indicates a patch is needed if connecting through usb. (Patch is not needed if connecting through bluetooth.)

This information indicates one must configure the controller in Steam, but I don't know if that info is still valid.

All I am finding are people connecting successfully through bluetooth. I don't know if that is a possible option for you.

I just bought an adapter, and here are my results from the following commands:

/etc/init.d/bluetooth status

Code: Select all

● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2023-05-31 15:36:11 -03; 40s ago
       Docs: man:bluetoothd(8)
   Main PID: 878 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 18771)
     Memory: 1.8M
        CPU: 22ms
     CGroup: /system.slice/bluetooth.service
             └─878 /usr/lib/bluetooth/bluetoothd

May 31 15:36:11 arthur-System-Product-Name systemd[1]: Starting Bluetooth service...
May 31 15:36:11 arthur-System-Product-Name bluetoothd[878]: Bluetooth daemon 5.64
May 31 15:36:11 arthur-System-Product-Name systemd[1]: Started Bluetooth service.
May 31 15:36:11 arthur-System-Product-Name bluetoothd[878]: Starting SDP server
May 31 15:36:11 arthur-System-Product-Name bluetoothd[878]: Bluetooth management interface 1.22…ized
Hint: Some lines were ellipsized, use -l to show in full.

blueman-manager

Code: Select all

blueman-manager 15.38.39 ERROR    Manager:147 on_dbus_name_appeared: Default adapter not found, trying first available.
blueman-manager 15.38.39 ERROR    Manager:151 on_dbus_name_appeared: No adapter(s) found, exiting

lsusb

Code: Select all

Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 002: ID 2357:0115 TP-Link Archer T4U ver.3
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 003 Device 002: ID 258a:1007 SINOWEALTH Mouse Gamer Husky Frost
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 1a2c:4c5e China Resource Semico Co., Ltd USB Keyboard
Bus 001 Device 002: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[SMG]

Code: Select all

Bus 003 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

It seems others have run into issues with this dongle.
This bug report Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) #1379 has a link to How do I get my bluetooth device working?.

There are also some tips of what to check in this topic How do I make my USB Bluetooth dongle work? (Can't init device hci0: Connection timed out (110)).

I do not normally help troubleshoot bluetooth issues so my ability to help is limited. (Bluetooth issues are normally handled in the Networking forum.)

[MandSpades]

Code: Select all

Bus 003 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

It seems others have run into issues with this dongle.
This bug report Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) #1379 has a link to How do I get my bluetooth device working?.

There are also some tips of what to check in this topic How do I make my USB Bluetooth dongle work? (Can't init device hci0: Connection timed out (110)).

I do not normally help troubleshoot bluetooth issues so my ability to help is limited. (Bluetooth issues are normally handled in the Networking forum.)

Is it fine for me to make a post specifically about the bluetooth dongle while linking to this post (to say that this extra problem was encountered while troubleshooting the DS4)?

Also, my diagnostic results are slightly different from those shown on the second link!

dmesg | grep BlueTooth

Code: Select all

[    9.307028] Bluetooth: Core ver 2.22
[    9.307050] Bluetooth: HCI device and connection manager initialized
[    9.307054] Bluetooth: HCI socket layer initialized
[    9.307055] Bluetooth: L2CAP socket layer initialized
[    9.307058] Bluetooth: SCO socket layer initialized
[    9.391922] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds and force-suspending once...
[    9.769945] Bluetooth: hci0: HCI Delete Stored Link Key command is advertised, but not supported.
[    9.769953] Bluetooth: hci0: HCI Set Event Filter command not supported.
[   11.878038] Bluetooth: hci0: command 0x0c5a tx timeout
[   11.878038] Bluetooth: hci0: Opcode 0x c5a failed: -110
[   12.107925] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   12.107928] Bluetooth: BNEP filters: protocol multicast
[   12.107932] Bluetooth: BNEP socket layer initialized
[  318.223233] Bluetooth: hci0: command 0x1001 tx timeout
[  326.413779] Bluetooth: hci0: CSR: Local version failed (-110)
[  326.413786] Bluetooth: hci0: HCI Delete Stored Link Key command is advertised, but not supported.
[  326.413787] Bluetooth: hci0: HCI Set Event Filter command not supported.

hciconfig -a hci0

Code: Select all

hci0:	Type: Primary  Bus: USB
	BD Address: 00:1A:7D:DA:71:13  ACL MTU: 679:8  SCO MTU: 48:16
	DOWN 
	RX bytes:531 acl:0 sco:0 events:23 errors:0
	TX bytes:327 acl:0 sco:0 commands:24 errors:0
	Features: 0xbf 0x3e 0x4d 0xfa 0xdb 0x3d 0x7b 0xc7
	Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
	Link policy: RSWITCH SNIFF 
	Link mode: PERIPHERAL ACCEPT 

sudo hciconfig hci0 up

Code: Select all

Can't init device hci0: Connection timed out (110)

Am soon gonna try the workarounds from the first reply... if that's a good idea?

Here's what the diagnostic shows, also different from the reply...

sudo btmon (then running "sudo hciconfig hci0 up" at the same time)

Code: Select all

Bluetooth monitor ver 5.64
= Note: Linux version 6.0.0-1017-oem (x86_64)                                              0.215178
= Note: Bluetooth subsystem version 2.22                                                   0.215179
= New Index: 00:1A:7D:DA:71:13 (Primary,USB,hci0)                                   [hci0] 0.215180
@ MGMT Open: bluetoothd (privileged) version 1.22                                 {0x0001} 0.215181
@ RAW Open: hciconfig (privileged) version 2.22                                   {0x0002} 6.982291
= Open Index: 00:1A:7D:DA:71:13                                                     [hci0] 7.097870
= Index Info: 00:1A:7D:DA:71:13 (Cambridge Silicon Radio)                           [hci0] 7.097875
< HCI Command: Read Local Version Information (0x04|0x0001) plen 0               #1 [hci0] 7.097891
= Close Index: 00:1A:7D:DA:71:13                                                   [hci0] 17.149033
@ RAW Close: hciconfig                     

Hmm, the answer seems to involve RECOMPILING A KERNEL MODULE with every kernel update. I suppose there is a better alternative?

I also ran this sequence of commands from the second answer to apparently reboot my bluetooth module, but it seems to do nothing:

Code: Select all

sudo rmmod btusb
sudo modprobe btusb
sudo service bluetooth restart

Uh-oh, after doing a bunch of these stuff, running hciconfig -a hci0 again shows an entirely different and probably worse result!

Code: Select all

hci0:	Type: Primary  Bus: USB
	BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
	DOWN 
	RX bytes:0 acl:0 sco:0 events:0 errors:0
	TX bytes:6 acl:0 sco:0 commands:2 errors:0
	Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
	Packet type: DM1 DH1 HV1 
	Link policy: 
	Link mode: PERIPHERAL ACCEPT 

Oh, and now attempting lsusb just makes it hang forever without results, though ctrl+c does kill it... Oh, man, I'll just go to sleep and check on this tomorrow!