Playstation 3 Controller (Dual Shock 3) not working wirelessly anymore

Hello!

It already started some months, ago: My DS3 wouldn’t connect wirelessly anymore. It still works when using the cable.
Back then I installed some other bluetooth package (I think it was bluez from snap) and it was working again.
But for a few days now, it again isn’t working anymore, only through USB.
I fiddled around a lot with the bluetooth packages, and I don’t even know, how it’s supposed to be ‘normally’ (does one still require the older “bluez-ps3”)?

The current problems are:
-Only installing “bluez” from the main repo doesn’t seem to be compatible to the controller. It doesn’t even ask for connecting.
-Installing “bluez-ps3” is not possible, because the build stalls with segfaults

I tried installing:
bluez, blueman, manjaro-pulse from the repo, as these where removed during my experiments.
“Normal” bluetooth devcies are working, but the DS3 is not recognized anymore :frowning:

Also I tried installing the “bluez-plugins”, but this doesn’t work either:
It pretends to be working, the Bluetooth-Legitimation prompt from blueman appers and is asking to trust the controller. I click allow or allow ever, and the controller is shown in the graphical UI. But after disconnecting USB it instantly disappears. When I try to connect by doouble clicking the Controller in the Blueman GUI, Blueman says “Verbindung fehlgeschlagen: Gerät hat nicht geantwortet” (Connection failed, device did not respond). When trying to connect the controller by pressing the PS button, there’s a flod of messages, alternating between “38-CO-96-97-3B-F8 connected” and “38-CO-96-97-3B-F8 disconnected”.

The controller is working normally on a real Playstation 3 and through USB.

Does someone know a solution?

Thank you!

Can someone help me?

Have you read the wiki yet regarding this?

You need bluez, bluez-utils, and bluez-plugins.

On KDE, it also prompts me to Trust & Authorize when I plug in via USB. After I click on that, it will automatically connect via Bluetooth for me.

You can also do it via bluetoothctl, which has also worked for me. I’ve only done that once before though.

2 Likes

Yes, I have these packages installed.
I connect the pad using USB, press the PS button, and get the Trust&Authorize dialog. There I confirm. Then the controller is being shown in blueman as connecting for about 2 seconds, and then disappears again. It was working for a year before…
The bluetooth connection is working fine for my headset, and tje controller is working on the original PS3.

Please provide inxi -Fza

1 Like

Hello!

Tahk you both for help!
Somehow the problem finally got fixed, by me using bluetootctl! ( I didn’t use the command line version, yet.)

All I did was starting bluetoothctl, and insert the Joypad. I plugged toe DS3 into USB, and bluetoothctl asked my in text, whether I wished to trust. I entered ‘yes’ and it connected - and this time it stayed.
After this it also started working using the graphical Bluetootmanager, again.
I also rebooted the whole system, and tried again and again: It’s working normally now…

Using the command line version somehow magically fixed the problem…

:star_struck:

PS:
Still here’s the output of inxi -Fza, in case someone might want to examine similar phenomenons:

System:
  Kernel: 5.13.5-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 
  parameters: BOOT_IMAGE=/vmlinuz-5.13-x86_64 
  root=UUID=b992e7b6-adfa-4b33-ae04-cdf2b9431da2 rw quiet libata.force=noncq 
  apparmor=1 security=apparmor udev.log_priority=3 intel_iommu=on 
  resume=UUID=99a1bc9c-4814-40ae-a653-b1c97e1b8bbd 
  Desktop: Xfce 4.16.0 tk: Gtk 3.24.29 info: xfce4-panel wm: xfwm 4.16.1 
  vt: 7 dm: LightDM 1.30.0 Distro: Manjaro Linux base: Arch Linux 
Machine:
  Type: Laptop System: Hewlett-Packard product: HP EliteBook 8770w 
  v: A1029D1102 serial: <filter> Chassis: type: 10 serial: <filter> 
  Mobo: Hewlett-Packard model: 176C v: KBC Version 50.1F serial: <filter> 
  BIOS: Hewlett-Packard v: 68IAV Ver. F.71 date: 04/19/2019 
Battery:
  ID-1: BAT0 charge: 15.9 Wh (100.0%) condition: 15.9/15.9 Wh (100.0%) 
  volts: 16.1 min: 14.4 model: Hewlett-Packard Primary type: Li-ion 
  serial: <filter> status: Full 
  Device-1: sony_controller_battery_38:c0:96:97:3b:f8 model: N/A serial: N/A 
  charge: N/A status: Discharging 
CPU:
  Info: Quad Core model: Intel Core i7-3720QM bits: 64 type: MT MCP 
  arch: Ivy Bridge family: 6 model-id: 3A (58) stepping: 9 microcode: 21 
  cache: L2: 6 MiB 
  flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 41522 
  Speed: 1453 MHz min/max: 1200/3600 MHz Core speeds (MHz): 1: 1453 2: 1196 
  3: 2802 4: 1197 5: 2152 6: 2723 7: 1197 8: 1203 
  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 status: Vulnerable: No microcode 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: NVIDIA GM107GLM [Quadro M2000M] vendor: Hewlett-Packard 
  driver: nvidia v: 470.57.02 alternate: nouveau,nvidia_drm bus-ID: 01:00.0 
  chip-ID: 10de:13b0 class-ID: 0300 
  Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.16.1 driver: 
  loaded: nvidia display-ID: :0.0 screens: 1 
  Screen-1: 0 s-res: 3840x1080 s-dpi: 88 s-size: 1108x311mm (43.6x12.2") 
  s-diag: 1151mm (45.3") 
  Monitor-1: LVDS-0 res: 1920x1080 hz: 50 dpi: 85 
  size: 576x324mm (22.7x12.8") diag: 661mm (26") 
  Monitor-2: DP-2 res: 1920x1080 dpi: 87 size: 560x320mm (22.0x12.6") 
  diag: 645mm (25.4") 
  OpenGL: renderer: Quadro M2000M/PCIe/SSE2 v: 4.6.0 NVIDIA 470.57.02 
  direct render: Yes 
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio 
  vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 
  chip-ID: 8086:1e20 class-ID: 0403 
  Device-2: C-Media CM106 Like Sound Device type: USB 
  driver: hid-generic,snd-usb-audio,usbhid bus-ID: 3-1.2.3:10 
  chip-ID: 0d8c:0102 class-ID: 0300 
  Sound Server-1: ALSA v: k5.13.5-1-MANJARO running: yes 
  Sound Server-2: JACK v: 1.9.19 running: no 
  Sound Server-3: PulseAudio v: 14.2 running: yes 
  Sound Server-4: PipeWire v: 0.3.32 running: no 
Network:
  Device-1: Intel 82579LM Gigabit Network vendor: Hewlett-Packard 
  driver: e1000e v: kernel port: 3040 bus-ID: 00:19.0 chip-ID: 8086:1502 
  class-ID: 0200 
  IF: enp0s25 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel port: 2000 
  bus-ID: 04:00.0 chip-ID: 8086:08b1 class-ID: 0280 
  IF: wlo1 state: up mac: <filter> 
  Device-3: Realtek RTL8188FTV 802.11b/g/n 1T1R 2.4G WLAN Adapter type: USB 
  driver: N/A bus-ID: 3-2:16 chip-ID: 0bda:f179 class-ID: 0000 
  serial: <filter> 
  IF-ID-1: ALLESLOGO state: unknown speed: 10 Mbps duplex: full mac: N/A 
Bluetooth:
  Device-1: Broadcom HP Portable SoftSailing type: USB driver: btusb v: 0.8 
  bus-ID: 2-1.6:3 chip-ID: 0a5c:21e1 class-ID: fe01 serial: <filter> 
  Report: rfkill ID: hci0 rfk-id: 1 state: up address: see --recommends 
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci 
  v: 3.0 port: 3020 bus-ID: 00:1f.2 chip-ID: 8086.282a rev: 04 
  class-ID: 0104 
Drives:
  Local Storage: total: 2.76 TiB used: 725.75 GiB (25.7%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 2TB 
  size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s 
  type: SSD serial: <filter> rev: 1B6Q scheme: MBR 
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 850 EVO 1TB 
  size: 931.51 GiB block-size: physical: 512 B logical: 512 B 
  speed: 6.0 Gb/s type: SSD serial: <filter> rev: 3B6Q scheme: MBR 
  ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: SanDisk model: Ultra 
  size: 28.64 GiB block-size: physical: 512 B logical: 512 B type: N/A 
  serial: <filter> rev: 1.00 scheme: MBR 
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
Partition:
  ID-1: / raw-size: 79.06 GiB size: 77.57 GiB (98.11%) 
  used: 59.81 GiB (77.1%) fs: ext4 dev: /dev/sda5 maj-min: 8:5 
  ID-2: /boot raw-size: 1024 MiB size: 975.9 MiB (95.30%) 
  used: 202.9 MiB (20.8%) fs: ext4 dev: /dev/sda1 maj-min: 8:1 
  ID-3: /home raw-size: 361.8 GiB size: 355.12 GiB (98.15%) 
  used: 312.01 GiB (87.9%) fs: ext4 dev: /dev/sda6 maj-min: 8:6 
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 32 GiB used: 759 MiB (2.3%) 
  priority: -2 dev: /dev/sda7 maj-min: 8:7 
Sensors:
  System Temperatures: cpu: 52.0 C mobo: 43.0 C gpu: nvidia temp: 45 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 324 Uptime: 8h 11m wakeups: 5 Memory: 19.48 GiB 
  used: 6.07 GiB (31.2%) Init: systemd v: 248 tool: systemctl Compilers: 
  gcc: 11.1.0 alt: 10 clang: 12.0.1 Packages: 1905 note: see --pkg 
  pacman: 1878 lib: 468 flatpak: 18 snap: 9 Shell: Bash v: 5.1.8 
  running-in: xfce4-terminal inxi: 3.3.06 

I’m marking this thread as solved based on the above.
I’m removing the (Solved) tag from the topic as well.

For future threads, make sure you mark them as solved. You can do that yourself by clicking on the hamburger menu at the bottom of every post (except for the OP). The solution option is hidden there.

Thanks.

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

The above seemed to have solved itself, after I paired the controller through command line instead of the UI.
But in fact the problem still is there - it just doesn’t show for devices that already are paired, but there’s same trouble with pairing NEW devices all the time.
I have to use the command line, which might pair the device (from headphones through game controllers) dozens of times, until it works. I have to restart the Bluetooth.service often as it crashes during these tries. Sometimes even restarting the services and reloading the Bluetooth driver (btusb) won’t help and I have to reboot the whole system for trying further.
As now a friend of mine oftens comes with new DS3 controllers for me having them repaired and tested, this is especially painful. It all worked fine, until a few months, ago.

-So, pairing sometimes works using bluetoothctl but it often crashes the Bluetooth.service or even more.
Some example output below:

[bluetooth]# pair 60:38:0E:E3:01:2F
Attempting to pair with 60:38:0E:E3:01:2F
Failed to pair: org.bluez.Error.ConnectionAttemptFailed)
[DEL] Device 60:38:0E:E3:01:2F Sony PLAYSTATION(R)3 Controller'

OR:

'[60-38-0E-E3-01-2F]# connect 60:38:0E:E3:01:2F
Attempting to connect to 60:38:0E:E3:01:2F
[CHG] Device 60:38:0E:E3:01:2F Modalias: usb:v054Cp0268d0100
[CHG] Device 60:38:0E:E3:01:2F UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[CHG] Device 60:38:0E:E3:01:2F UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 60:38:0E:E3:01:2F ServicesResolved: yes
[CHG] Device 60:38:0E:E3:01:2F WakeAllowed: yes
Failed to connect: org.bluez.Error.Failed

Pairing using the GUI (bluetooth-manager) never works anymore.

As it had formerly been requested in the other thread, here’s the output of ’ inxi -Fza again:

System:
  Kernel: 5.13.5-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 
  parameters: BOOT_IMAGE=/vmlinuz-5.13-x86_64 
  root=UUID=b992e7b6-adfa-4b33-ae04-cdf2b9431da2 rw quiet libata.force=noncq 
  apparmor=1 security=apparmor udev.log_priority=3 intel_iommu=on 
  resume=UUID=99a1bc9c-4814-40ae-a653-b1c97e1b8bbd 
  Desktop: Xfce 4.16.0 tk: Gtk 3.24.29 info: xfce4-panel wm: xfwm 4.16.1 
  vt: 7 dm: LightDM 1.30.0 Distro: Manjaro Linux base: Arch Linux 
Machine:
  Type: Laptop System: Hewlett-Packard product: HP EliteBook 8770w 
  v: A1029D1102 serial: <filter> Chassis: type: 10 serial: <filter> 
  Mobo: Hewlett-Packard model: 176C v: KBC Version 50.1F serial: <filter> 
  BIOS: Hewlett-Packard v: 68IAV Ver. F.71 date: 04/19/2019 
Battery:
  ID-1: BAT0 charge: 15.9 Wh (100.0%) condition: 15.9/15.9 Wh (100.0%) 
  volts: 16.1 min: 14.4 model: Hewlett-Packard Primary type: Li-ion 
  serial: <filter> status: Full 
  Device-1: sony_controller_battery_38:c0:96:97:3b:f8 model: N/A serial: N/A 
  charge: N/A status: Discharging 
CPU:
  Info: Quad Core model: Intel Core i7-3720QM bits: 64 type: MT MCP 
  arch: Ivy Bridge family: 6 model-id: 3A (58) stepping: 9 microcode: 21 
  cache: L2: 6 MiB 
  flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 41522 
  Speed: 1453 MHz min/max: 1200/3600 MHz Core speeds (MHz): 1: 1453 2: 1196 
  3: 2802 4: 1197 5: 2152 6: 2723 7: 1197 8: 1203 
  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 status: Vulnerable: No microcode 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: NVIDIA GM107GLM [Quadro M2000M] vendor: Hewlett-Packard 
  driver: nvidia v: 470.57.02 alternate: nouveau,nvidia_drm bus-ID: 01:00.0 
  chip-ID: 10de:13b0 class-ID: 0300 
  Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.16.1 driver: 
  loaded: nvidia display-ID: :0.0 screens: 1 
  Screen-1: 0 s-res: 3840x1080 s-dpi: 88 s-size: 1108x311mm (43.6x12.2") 
  s-diag: 1151mm (45.3") 
  Monitor-1: LVDS-0 res: 1920x1080 hz: 50 dpi: 85 
  size: 576x324mm (22.7x12.8") diag: 661mm (26") 
  Monitor-2: DP-2 res: 1920x1080 dpi: 87 size: 560x320mm (22.0x12.6") 
  diag: 645mm (25.4") 
  OpenGL: renderer: Quadro M2000M/PCIe/SSE2 v: 4.6.0 NVIDIA 470.57.02 
  direct render: Yes 
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio 
  vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 
  chip-ID: 8086:1e20 class-ID: 0403 
  Device-2: C-Media CM106 Like Sound Device type: USB 
  driver: hid-generic,snd-usb-audio,usbhid bus-ID: 3-1.2.3:10 
  chip-ID: 0d8c:0102 class-ID: 0300 
  Sound Server-1: ALSA v: k5.13.5-1-MANJARO running: yes 
  Sound Server-2: JACK v: 1.9.19 running: no 
  Sound Server-3: PulseAudio v: 14.2 running: yes 
  Sound Server-4: PipeWire v: 0.3.32 running: no 
Network:
  Device-1: Intel 82579LM Gigabit Network vendor: Hewlett-Packard 
  driver: e1000e v: kernel port: 3040 bus-ID: 00:19.0 chip-ID: 8086:1502 
  class-ID: 0200 
  IF: enp0s25 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel port: 2000 
  bus-ID: 04:00.0 chip-ID: 8086:08b1 class-ID: 0280 
  IF: wlo1 state: up mac: <filter> 
  Device-3: Realtek RTL8188FTV 802.11b/g/n 1T1R 2.4G WLAN Adapter type: USB 
  driver: N/A bus-ID: 3-2:16 chip-ID: 0bda:f179 class-ID: 0000 
  serial: <filter> 
  IF-ID-1: AL state: unknown speed: 10 Mbps duplex: full mac: N/A 
Bluetooth:
  Device-1: Broadcom HP Portable SoftSailing type: USB driver: btusb v: 0.8 
  bus-ID: 2-1.6:3 chip-ID: 0a5c:21e1 class-ID: fe01 serial: <filter> 
  Report: rfkill ID: hci0 rfk-id: 1 state: up address: see --recommends 
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci 
  v: 3.0 port: 3020 bus-ID: 00:1f.2 chip-ID: 8086.282a rev: 04 
  class-ID: 0104 
Drives:
  Local Storage: total: 2.76 TiB used: 725.75 GiB (25.7%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 2TB 
  size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s 
  type: SSD serial: <filter> rev: 1B6Q scheme: MBR 
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 850 EVO 1TB 
  size: 931.51 GiB block-size: physical: 512 B logical: 512 B 
  speed: 6.0 Gb/s type: SSD serial: <filter> rev: 3B6Q scheme: MBR 
  ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: SanDisk model: Ultra 
  size: 28.64 GiB block-size: physical: 512 B logical: 512 B type: N/A 
  serial: <filter> rev: 1.00 scheme: MBR 
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
Partition:
  ID-1: / raw-size: 79.06 GiB size: 77.57 GiB (98.11%) 
  used: 59.81 GiB (77.1%) fs: ext4 dev: /dev/sda5 maj-min: 8:5 
  ID-2: /boot raw-size: 1024 MiB size: 975.9 MiB (95.30%) 
  used: 202.9 MiB (20.8%) fs: ext4 dev: /dev/sda1 maj-min: 8:1 
  ID-3: /home raw-size: 361.8 GiB size: 355.12 GiB (98.15%) 
  used: 312.01 GiB (87.9%) fs: ext4 dev: /dev/sda6 maj-min: 8:6 
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 32 GiB used: 759 MiB (2.3%) 
  priority: -2 dev: /dev/sda7 maj-min: 8:7 
Sensors:
  System Temperatures: cpu: 52.0 C mobo: 43.0 C gpu: nvidia temp: 45 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 324 Uptime: 8h 11m wakeups: 5 Memory: 19.48 GiB 
  used: 6.07 GiB (31.2%) Init: systemd v: 248 tool: systemctl Compilers: 
  gcc: 11.1.0 alt: 10 clang: 12.0.1 Packages: 1905 note: see --pkg 
  pacman: 1878 lib: 468 flatpak: 18 snap: 9 Shell: Bash v: 5.1.8 
  running-in: xfce4-terminal inxi: 3.3.06

I hope someone can help solving this trouble.
Thank you all in advance! :slight_smile:

  1. In the future, when providing code/output, please copy-paste that output in-between 3 backticks ``` at the beginning and end of the code/text so that the output looks like this:

    Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
    Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
    Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
    Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
    

    instead of like this:

    Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.`

    (as that makes both our lives much easier)

  2. No need to do anything right now as I’m a moderator here on this site and have fixed it for you already. However, in the future I might not see your post so review my RAW edits by pushing the orange pencil in the upper right corner of the post I just fixed. :wink:

  3. Is there any particular reason you’re on the 5.13 Stable Devlopment kernel? If not, please read this (especially the Linux has multiple kernels section) and then install an LTS kernel (5.10 would be high on my list) and then try again…

:+1:

1 Like

Hello!

Yes, there was a reason for me installing the, about a year, ago. I was trying to fix a problem (which I cannot remember what it was anymore) I had then by updating the kernel, but as far as I remember the update didn’t help anyways. So I can try switching back now if you think it could help.
Edit:
I switched back to the LTS-kernel but the symptoms are same as in my first post.

1 Like

Hello, again! :wave:

Failed to connect: org.bluez.Error.NotReady
My controller’s usb port is nearly broken from thousands of times replugging
:frowning:

I gathered some more info:

Sep 12 17:51:10 elite.bnetza.lan kernel: usb 1-1.6: new full-speed USB device number 28 using ehci-pci
Sep 12 17:51:10 elite.bnetza.lan kernel: usb 1-1.6: New USB device found, idVendor=054c, idProduct=0268, bcdDevice= 1.00
Sep 12 17:51:10 elite.bnetza.lan kernel: usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Sep 12 17:51:10 elite.bnetza.lan kernel: usb 1-1.6: Product: PLAYSTATION(R)3 Controller
Sep 12 17:51:10 elite.bnetza.lan kernel: usb 1-1.6: Manufacturer: Sony
Sep 12 17:51:10 elite.bnetza.lan kernel: input: Sony PLAYSTATION(R)3 Controller Motion Sensors as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/0003:054C:0268.0049/input/input188
Sep 12 17:51:10 elite.bnetza.lan kernel: input: Sony PLAYSTATION(R)3 Controller as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/0003:054C:0268.0049/input/input187
Sep 12 17:51:10 elite.bnetza.lan kernel: sony 0003:054C:0268.0049: input,hiddev98,hidraw6: USB HID v81.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-0000:00:1a.0-1.6/input0
Sep 12 17:51:10 elite.bnetza.lan mtp-probe[373486]: checking bus 1, device 28: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6"
Sep 12 17:51:10 elite.bnetza.lan mtp-probe[373486]: bus: 1, device: 28 was not an MTP device
Sep 12 17:51:11 elite.bnetza.lan bluetoothd[369744]: sixaxis: compatible device connected: Sony PLAYSTATION(R)3 Controller (054C:0268 /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/0003:054C:0268.0049/hidraw/hidraw6)
Sep 12 17:51:11 elite.bnetza.lan bluetoothd[369744]: sixaxis: setting up new device
Sep 12 17:51:11 elite.bnetza.lan mtp-probe[373527]: checking bus 1, device 28: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6"
Sep 12 17:51:11 elite.bnetza.lan mtp-probe[373527]: bus: 1, device: 28 was not an MTP device
Sep 12 17:51:11 elite.bnetza.lan upowerd[1212]: treating change event as add on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/0003:054C:0268.0049/power_supply/sony_controller_battery_38:c0:96:97:3b:f8

Any more ideas, please?

Hello! Does updating here actually push my post? :frowning:

Software can do only so much and software solutions for hardware problems are rarely effective: Have the port / plug repaired.

:sob:

:frowning:
Can you help me to get my topic into the forum’s aware ness again?
What should I do?
I read and tried countless solutions, and I am sure there are people who know what the problem is. Bluetooth isn’t so special.
Thank you!

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