Review your favorite Linux distribution.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 02-19-2021, 01:57 PM   #1
LQ Newbie
Registered: Feb 2021
Distribution: Slackware64-current / Plasma
Posts: 1

Rep: Reputation: Disabled
64-current: Bluedevil won't list PlayStation3 bluetooth controller (but it still connects)

Hey, since some few updates ago (2 or 3, unfortunately i didn't took note in which version exactly it broke), the bluetooth applet on KDE plasma5, which I assume is bluedevil, stopped listing my PS3 controller. It lists everything else except the controller, but if I turn the controller on it connects normally even though still not being listed (the taskbar icon even change to device connected symbol). In blueman-applet it appears normally, so whenever I need to manually disconnect it to save battery I have to open bluemancon and do it from there.

It worked fine previously on bluedevil, I haven't changed anything from the usual I've being using for my 64-current machine for years: everything default except I compile bluez myself with sixaxis support and kernel with tkg's fsync patch.

Have you ever seen anything like that? Any clues? Thanks!

EDIT 1: I forgot to mention I have this udev rule in /etc/udev/rules.d:

# DualShock 3 over USB
KERNEL=="hidraw", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="0268", MODE="0666"

# DualShock 3 over Bluetooth
KERNEL=="hidraw*", KERNELS=="*054C:0268*", MODE="0666"

After updating bluez to 5.56 (from current's official sources, build-1, but recompiled with support for sixaxis), bluez-firmware to 1.2 (build-4), bluedevil to 5.21.1 (build-1) and kernel to 5.10.18 (recompiled with fsync patch), the joystick controllers now are no longer named Sony PLAYSTATION(R)3 Controller, but were renamed to SHANWAN PS3 Gamepad. Still they are not listed in the regular devices list with other bluetooth devices.

And now its worst: they connect but the led lights on the controller get unstable, all blinking and shutting off (despite the controller still being connected) instead of keeping one light on according to the controller number.

I'm starting to wonder if it has something to do with the fact that PS3 controllers, contrary to PS4 controllers, need to be first plugged with a usb cord to authorize device and thereafter are connected wireless normally via bluetooth by turning it on. If i force add new devices button, with its list of previously known devices, it asks me to input the pin on the device, but obviously it is impossible in a controller.

Last edited by rinza; 02-27-2021 at 09:28 PM. Reason: Changes after update


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] BlueDevil (Bluetooth) Not working properly after Upgrading to KDE Plasma n4rf Slackware 1 08-19-2016 07:54 AM
slackware CURRENT bluedevil-wizard = segmentation fault USUARIONUEVO Slackware 2 07-19-2015 09:17 PM
[SOLVED] bluetooth with bluedevil davepi Linux - Hardware 1 11-16-2012 01:40 PM
Bluetooth DUN (Dial Up Network) + Bluedevil & Blueman. cwizardone Slackware 25 10-30-2011 08:22 AM
Streaming media from Linux box to Playstation3 isolier Linux - Newbie 1 02-02-2008 07:06 PM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:08 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration