PS4 controller doesn't get recognized on my computer

Hello Garuda users.

My ps4 controller doesn't get recognized by my computer even though it does on my friends laptop using same cable(he is using manjaro, but don't think that's relevant). I had no problems previously in fact haven't touched my controller for 5month and changed nothing since then. I didn't really know where to post this, so if this post is inappropriate I'll delete it.

BTW I am using Garuda KDE Gaming for 8 months. It is awesome haven't had issues so far and I don't think distro has anything to do with this problem IMO it must be some powersave issue, but can't figure out exactly what it is.
P.S all usb ports seem to be working fine.

System:
Kernel: 5.15.77-1-lts arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
root=UUID=26c9cf0e-2a45-4920-bdf2-0049acb7afeb rw [email protected]
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
loglevel=3 pci=noaer
Desktop: KDE Plasma v: 5.26.2 tk: Qt v: 5.15.7 info: latte-dock
wm: kwin_x11 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Laptop System: ASUSTeK product: ASUS TUF Gaming A17 FA706II_FA706II
v: 1.0 serial: <filter>
Mobo: ASUSTeK model: FA706II v: 1.0 serial: <filter>
UEFI: American Megatrends v: FA706II.316 date: 03/12/2021
Battery:
ID-1: BAT1 charge: 38.0 Wh (100.0%) condition: 38.0/48.1 Wh (78.9%)
volts: 12.6 min: 11.7 model: ASUS A32-K55 type: Li-ion serial: N/A
status: full
CPU:
Info: model: AMD Ryzen 5 4600H with Radeon Graphics socket: FP6 bits: 64
type: MT MCP arch: Zen 2 gen: 3 level: v3 note: check built: 2020-22
process: TSMC n7 (7nm) family: 0x17 (23) model-id: 0x60 (96) stepping: 1
microcode: 0x8600104
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: 8 MiB desc: 2x4 MiB
Speed (MHz): avg: 3000 min/max: 1400/3000 boost: enabled
base/boost: 3000/4000 scaling: driver: acpi-cpufreq governor: performance
volts: 1.2 V ext-clock: 100 MHz cores: 1: 3000 2: 3000 3: 3000 4: 3000
5: 3000 6: 3000 7: 3000 8: 3000 9: 3000 10: 3000 11: 3000 12: 3000
bogomips: 71864
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 mitigation: untrained return thunk; SMT enabled with STIBP
protection
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: Retpolines, IBPB: conditional, STIBP:
always-on, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA TU117M [GeForce GTX 1650 Ti Mobile] vendor: ASUSTeK
driver: nvidia v: 520.56.06 alternate: nouveau,nvidia_drm non-free: 515.xx+
status: current (as of 2022-10) arch: Turing code: TUxxx
process: TSMC 12nm built: 2018-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 8
link-max: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0
chip-ID: 10de:1f95 class-ID: 0300
Device-2: AMD Renoir vendor: ASUSTeK driver: amdgpu v: kernel
arch: GCN-5.1 code: Vega-2 process: TSMC n7 (7nm) built: 2018-21 pcie:
gen: 4 speed: 16 GT/s lanes: 16 ports: active: eDP-1 empty: HDMI-A-1
bus-ID: 05:00.0 chip-ID: 1002:1636 class-ID: 0300 temp: 40.0 C
Device-3: IMC Networks USB2.0 HD UVC WebCam type: USB driver: uvcvideo
bus-ID: 1-4:2 chip-ID: 13d3:56a2 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.5
compositor: kwin_x11 driver: X: loaded: amdgpu,nvidia
unloaded: modesetting,nouveau alternate: fbdev,nv,vesa dri: radeonsi
gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: eDP-1 mapped: eDP model: AU Optronics 0x479d built: 2019
res: 1920x1080 hz: 120 dpi: 128 gamma: 1.2 size: 382x215mm (15.04x8.46")
diag: 438mm (17.3") ratio: 16:9 modes: max: 1920x1080 min: 640x480
OpenGL: renderer: AMD Radeon Graphics (renoir LLVM 14.0.6 DRM 3.42
5.15.77-1-lts) v: 4.6 Mesa 22.2.1 direct render: Yes
Audio:
Device-1: NVIDIA vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
gen: 1 speed: 2.5 GT/s lanes: 8 link-max: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:10fa class-ID: 0403
Device-2: AMD Renoir Radeon High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 05:00.1 chip-ID: 1002:1637 class-ID: 0403
Device-3: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: DekTec Digital
Video B.V. driver: N/A alternate: snd_pci_acp3x, snd_rn_pci_acp3x,
snd_pci_acp5x pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 05:00.5
chip-ID: 1022:15e2 class-ID: 0480
Device-4: AMD Family 17h/19h HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 05:00.6 chip-ID: 1022:15e3 class-ID: 0403
Sound API: ALSA v: k5.15.77-1-lts running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.59 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp2s0 state: down mac: <filter>
Device-2: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter
vendor: AzureWave driver: rtw_8822ce v: kernel modules: rtw88_8822ce pcie:
gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 03:00.0
chip-ID: 10ec:c822 class-ID: 0280
IF: wlp3s0 state: up mac: <filter>
Drives:
Local Storage: total: 1.38 TiB used: 400.64 GiB (28.4%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Micron
model: 2210 MTFDHBA512QFD size: 476.94 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: P6MA001 temp: 43.9 C scheme: GPT
SMART: yes health: PASSED on: 226d 21h cycles: 1,413 read-units: 23,386,265
[11.9 TB] written-units: 37,060,636 [18.9 TB]
ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000LM035-1RK172
family: Mobile HDD size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B sata: 3.1 speed: 6.0 Gb/s type: HDD rpm: 5400
serial: <filter> rev: 0001 temp: 37 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 226d 15h cycles: 1392
read: 4.18 TiB written: 7.6 TiB Old-Age: g-sense error rate: 498 Pre-Fail:
attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97
Partition:
ID-1: / raw-size: 476.64 GiB size: 476.64 GiB (100.00%) used: 333.74 GiB
(70.0%) fs: btrfs block-size: 4096 B 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 block-size: 512 B dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 476.64 GiB size: 476.64 GiB (100.00%) used: 333.74
GiB (70.0%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2
maj-min: 259:2
ID-4: /var/log raw-size: 476.64 GiB size: 476.64 GiB (100.00%) used: 333.74
GiB (70.0%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2
maj-min: 259:2
ID-5: /var/tmp raw-size: 476.64 GiB size: 476.64 GiB (100.00%) used: 333.74
GiB (70.0%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2
maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 30.78 GiB used: 2 MiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 44.5 C mobo: N/A gpu: amdgpu temp: 40.0 C
Fan Speeds (RPM): cpu: 2300
Info:
Processes: 300 Uptime: 19m wakeups: 3 Memory: 30.78 GiB used: 5.89 GiB
(19.1%) Init: systemd v: 251 default: graphical tool: systemctl
Compilers: gcc: 12.2.0 clang: 14.0.6 Packages: pm: pacman pkgs: 1948
libs: 528 tools: octopi,paru Shell: garuda-inxi (sudo) default: Bash
v: 5.1.16 running-in: konsole inxi: 3.3.22
Garuda (2.6.9-1):
System install date:     2022-07-24
Last full system update: 2022-11-06
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       No/Undetected
Snapshots:               Snapper
Failed units:

Does it work using Bluetooth? My personal experience is that a DS4 controller always works fine with Linux using BT but almost never when using an USB cable (not unless you add some utility to map the buttons, etc, it is like it is not recognized properly, but it may work with some emulators, for instance, that map the controls). If the controller was paired and it is not working, remove it and pair again.

Hmm, that's weird: @MANTISxB has a similar issue, with a controller not being detected over USB (theirs is working over over USB-C only, thread here: Controller works when connected with USB C to USB C, but not USB 2/3.0 - #3 by MANTISxB).

Your post makes it sound like the controller was working fine, but out of the blue stopped--is that right?

My first thought would be a kernel update broke something, but my recommendation would have been to switch to the LTS kernel and I see you have already done that. :thinking:

4 Likes

Yes that is the case. I'll read the thread and update

Tried with bluetooth and it works without any problems. Weird, that with cable it has issues. Might be cable problem, but again it worked on my my friends computer with the same cable without any problem. Thank you for your reply.

Hey, I have the same issue with a fightstick. Xbox controllers work as intended. My fightsticks only work via USB-C to USB-C.

I have tried multiple cables and they all function on Windows 10 and 11 without issue. Even in VM.

Ill keep monitoring this thread for any fixes as ive "fixed" mine by just using a USB-C cable for the time being while playing on Garuda.

I also tried on Zen and LTS with no change. My other controllers all work via cable and BT, just not my Snackbox Micro. Even my PS4 HORI RAP-N works, just not this snackbox. Anything USB-C does not function unless in the USB-C slot.

I just tried connecting my Splatoon controller via USB-C. Same issue here. Wired HORI switch controller works as intended.

weird.

Please, to avoid confusion here, with different hardware, you should open a separate thread where you can then also post your garuda-inxi.

I did. Was just letting the other user know that im running into the same issue as I was tagged earlier in the thread. :slight_smile:

Apologies there.

1 Like

Seems me and deepl translated it wrong, sorry :slight_smile:

1 Like