While you're here, please consider supporting GamingOnLinux on:
Reward Tiers:
Patreon. Plain Donations: 
PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers:
Patreon. Plain Donations: PayPal.This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
- The "video game preservation service" Myrient is shutting down in March
- Discord delay global rollout of age verification to improve transparency and add more options
- Firefox 148.0 arrives with AI controls
- FINAL FANTASY VII arrives on GOG with a new edition live on Steam too
- SpaghettiKart the Mario Kart 64 fan-made PC port gets a big upgrade
- > See more over 30 days here
How to setup OpenMW for modern Morrowind on Linux / SteamOS and Steam Deck
How to install Hollow Knight: Silksong mods on Linux, SteamOS and Steam Deck- steam overlay performance monitor - issues
- Xpander - Nacon under financial troubles... no new WRC game (?)
- Xpander - Establishing root of ownership for Steam account
- Nonjuffo - Total Noob general questions about gaming and squeezing every oun…
- GustyGhost - Looking for Linux MMORPG sandbox players (Open Source–friendly …
- Jarmer - See more posts
The problem is that the vibration does not work in the correct way, the vibration works at full speed, and for a long time instead of a second or two.
When I connect the controller by the USB cable, I get these messages from dmesg:
[21397.801573] usb 3-2: new full-speed USB device number 5 using xhci_hcd[21397.951098] usb 3-2: New USB device found, idVendor=054c, idProduct=0268, bcdDevice= 1.00
[21397.951103] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[21397.951106] usb 3-2: Product: PS3 GamePad
[21397.951108] usb 3-2: Manufacturer: SHANWAN
[21397.955927] input: SHANWAN PS3 GamePad Motion Sensors as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/0003:054C:0268.0003/input/input29
[21398.013884] input: SHANWAN PS3 GamePad as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/0003:054C:0268.0003/input/input28
[21398.014462] sony 0003:054C:0268.0003: input,hiddev0,hidraw1: USB HID v81.10 Joystick [SHANWAN PS3 GamePad] on usb-0000:00:14.0-2/input0
[21461.499738] usb 3-2: USB disconnect, device number 5
but when it is connected by Bluetooth, I get these messages from dmesg:
[21471.515216] sony 0005:054C:0268.0004: unknown main item tag 0x0[21471.530748] input: Sony PLAYSTATION(R)3 Controller Motion Sensors as /devices/pci0000:00/0000:00:14.0/usb3/3-12/3-12:1.0/bluetooth/hci0/hci0:42/0005:054C:0268.0004/input/input31
[21471.531075] input: Sony PLAYSTATION(R)3 Controller as /devices/pci0000:00/0000:00:14.0/usb3/3-12/3-12:1.0/bluetooth/hci0/hci0:42/0005:054C:0268.0004/input/input30
[21471.531283] sony 0005:054C:0268.0004: input,hidraw1: BLUETOOTH HID v80.00 Joystick [Sony PLAYSTATION(R)3 Controller] on 1c:65:9d:82:b0:1c
I think if Bluez recognizes the controller as [SHANWAN PS3 GamePad] instead of [Sony PLAYSTATION(R)3 Controller], the controller will behave correctly, but how can I do that exactly?
I found a similar issue as mine:
https://forum.batocera.org/d/4471-vibration-generic-ps3-controller
Last edited by torbido on 14 Oct 2020 at 4:07 pm UTC