Fedora 17 and Sixaxis Dualshock Controller

Phobeus · #1 9th June 2012, 06:12 PM

HI guys,

I am trying currently to get a Sony Playstation Sixaxis Dualshock Controller attached to my F17 multimedia system. However, add the moment, I am failing terribily as the device doesn't seems to be connected to the system and I cannot get it working either the bluetooth nor the usb way. I am really hoping that someone else might have a similiar setup and performed some tests, I am really open for any idea.

The connection itself seems to be absolutely fine. When the device is attached to USB, in dmesg I can see the device is recognized by the system:
---
[ 2067.283259] input: Sony PLAYSTATION(R)3 Controller as /devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.0/input/input17
[ 2067.284665] sony 0003:054C:0268.000A: input,hiddev0,hidraw2: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-0000:00:1d.2-2/input0
---
However, it seems like no device is created and its not useable as a gamepad either. I am not sure, what actually is missing here.

When doing the bluetooth style, I compiled the latest version of "sixpair" and was able to attach it to a bluetooth device of the system. When pressing the PS button, the controller starts to blink and some seconds laster, kbluetooth is notificating that a new device was found. Its recognized as playstation controller. However, after a few seconds, the connection breaks and its trying to reattach the device again showing a notification. This actually seems to be running in a loop.

I am not sure, why both ways seems to fail using it as a gamepad. Any ideas?

Phobeus · #2 16th June 2012, 08:11 PM

Allright. If anyone runs into a similiar issue. It seems like the latest version of Fedora doesn't include all kernel modules required to bind the gamepad via usb. This was actually the reason for not getting the device anyhow to running, even as it was detected successfully. Just add the package " kernel-modules-extra" via yum and the device is ready to use.

Getting it run with bluetooth seems to be still tricky. The device tries to contact the PC, but something is going wrong with the handshaking.

Code:

[root@phobos tmp]# hcidump -t -x -i hci1
HCI sniffer - Bluetooth packet analyzer ver 2.2
device: hci1 snap_len: 1028 filter: 0xffffffffffffffff
2012-06-16 21:05:14.720066 > HCI Event: Connect Request (0x04) plen 10
    bdaddr 60:38:0E:39:5F:37 class 0x000508 type ACL
2012-06-16 21:05:14.720238 < HCI Command: Accept Connection Request (0x01|0x0009) plen 7
    bdaddr 60:38:0E:39:5F:37 role 0x00
    Role: Master
2012-06-16 21:05:14.721998 > HCI Event: Command Status (0x0f) plen 4
    Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
2012-06-16 21:05:14.881018 > HCI Event: Role Change (0x12) plen 8
    status 0x00 bdaddr 60:38:0E:39:5F:37 role 0x00
    Role: Master
2012-06-16 21:05:14.916012 > HCI Event: Connect Complete (0x03) plen 11
    status 0x00 handle 1 bdaddr 60:38:0E:39:5F:37 type ACL encrypt 0x00
2012-06-16 21:05:14.916085 < HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
    handle 1
2012-06-16 21:05:14.919016 > ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 17 scid 0x00d5
2012-06-16 21:05:14.919025 > HCI Event: Connection Packet Type Changed (0x1d) plen 5
    status 0x00 handle 1 ptype 0x3318
    Packet type: DM1 DH1 2-DH3 2-DH5 3-DH3 3-DH5 
2012-06-16 21:05:14.919036 < ACL data: handle 1 flags 0x00 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x00d5 result 1 status 0
      Connection pending - No futher information available
2012-06-16 21:05:14.919039 < ACL data: handle 1 flags 0x00 dlen 10
    L2CAP(s): Info req: type 2
2012-06-16 21:05:14.920998 > HCI Event: Command Status (0x0f) plen 4
    Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1
2012-06-16 21:05:14.921999 > HCI Event: Read Remote Supported Features (0x0b) plen 11
    status 0x00 handle 1
    Features: 0xfc 0x07 0x82 0x7e 0x08 0x18 0x00 0x80
2012-06-16 21:05:14.922027 < HCI Command: Remote Name Request (0x01|0x0019) plen 10
    bdaddr 60:38:0E:39:5F:37 mode 2 clkoffset 0x0000
2012-06-16 21:05:14.923997 > HCI Event: Command Status (0x0f) plen 4
    Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
2012-06-16 21:05:14.960025 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 1 packets 1
2012-06-16 21:05:14.964025 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 1 packets 1
2012-06-16 21:05:14.997551 > ACL data: handle 1 flags 0x02 dlen 16
    L2CAP(s): Info rsp: type 2 result 0
      Extended feature mask 0x0000
2012-06-16 21:05:14.997602 < ACL data: handle 1 flags 0x00 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x00d5 result 0 status 0
      Connection successful
2012-06-16 21:05:14.997607 < ACL data: handle 1 flags 0x00 dlen 12
    L2CAP(s): Config req: dcid 0x00d5 flags 0x00 clen 0
2012-06-16 21:05:15.014000 > HCI Event: Remote Name Req Complete (0x07) plen 255
    status 0x00 bdaddr 60:38:0E:39:5F:37 name 'PLAYSTATION(R)3 Controller'
2012-06-16 21:05:15.015000 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 1 packets 1
2012-06-16 21:05:15.016031 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 1 packets 1
2012-06-16 21:05:15.107529 > ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0
2012-06-16 21:05:15.107559 < ACL data: handle 1 flags 0x00 dlen 18
    L2CAP(s): Config rsp: scid 0x00d5 flags 0x00 result 0 clen 4
      MTU 672 
2012-06-16 21:05:15.111073 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 1 packets 1
2012-06-16 21:05:15.166280 > ACL data: handle 1 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success
2012-06-16 21:05:15.166399 < ACL data: handle 1 flags 0x00 dlen 5
    L2CAP(d): cid 0x00d5 len 1 [psm 17]
      HIDP: Control: Virtual cable unplug
2012-06-16 21:05:15.166406 < ACL data: handle 1 flags 0x00 dlen 12
    L2CAP(s): Disconn req: dcid 0x00d5 scid 0x0040
2012-06-16 21:05:15.170032 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 1 packets 1
2012-06-16 21:05:15.171031 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 1 packets 1
2012-06-16 21:05:15.442538 > ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x00d5 scid 0x0040
2012-06-16 21:05:15.448908 > ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 19 scid 0x00d6
2012-06-16 21:05:15.448953 < ACL data: handle 1 flags 0x00 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x00d6 result 1 status 2
      Connection pending - Authorization pending
2012-06-16 21:05:15.449083 < ACL data: handle 1 flags 0x00 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x00d6 result 3 status 0
      Connection refused - security block
2012-06-16 21:05:15.453032 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 1 packets 1
2012-06-16 21:05:15.454043 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 1 packets 1
2012-06-16 21:05:15.884044 > HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 1 reason 0x13
    Reason: Remote User Terminated Connection
2012-06-16 21:05:15.976034 > HCI Event: Connect Request (0x04) plen 10
    bdaddr 34:C7:31:2E:0D:A9 class 0x000508 type ACL
2012-06-16 21:05:15.976089 < HCI Command: Accept Connection Request (0x01|0x0009) plen 7
    bdaddr 34:C7:31:2E:0D:A9 role 0x00
    Role: Master
2012-06-16 21:05:15.978034 > HCI Event: Command Status (0x0f) plen 4
    Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
2012-06-16 21:05:16.152048 > HCI Event: Role Change (0x12) plen 8
    status 0x00 bdaddr 34:C7:31:2E:0D:A9 role 0x00
    Role: Master
2012-06-16 21:05:16.157091 > HCI Event: Connect Complete (0x03) plen 11
    status 0x00 handle 1 bdaddr 34:C7:31:2E:0D:A9 type ACL encrypt 0x00
2012-06-16 21:05:16.157181 < HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
    handle 1
[...]
2012-06-16 21:05:16.175079 < ACL data: handle 1 flags 0x00 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0294 result 0 status 0
      Connection successful
2012-06-16 21:05:16.175083 < ACL data: handle 1 flags 0x00 dlen 12
    L2CAP(s): Config req: dcid 0x0294 flags 0x00 clen 0
2012-06-16 21:05:16.179088 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 1 packets 1
2012-06-16 21:05:16.198046 > HCI Event: Remote Name Req Complete (0x07) plen 255
    status 0x00 bdaddr 34:C7:31:2E:0D:A9 name 'PLAYSTATION(R)3 Controller'
2012-06-16 21:05:16.199047 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 1 packets 1
2012-06-16 21:05:16.210272 > ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0
2012-06-16 21:05:16.210290 < ACL data: handle 1 flags 0x00 dlen 18
    L2CAP(s): Config rsp: scid 0x0294 flags 0x00 result 0 clen 4
      MTU 672 
2012-06-16 21:05:16.211289 > ACL data: handle 1 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success
2012-06-16 21:05:16.211387 < ACL data: handle 1 flags 0x00 dlen 5
    L2CAP(d): cid 0x0294 len 1 [psm 17]
      HIDP: Control: Virtual cable unplug
2012-06-16 21:05:16.211390 < ACL data: handle 1 flags 0x00 dlen 12
    L2CAP(s): Disconn req: dcid 0x0294 scid 0x0040
2012-06-16 21:05:16.214036 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 1 packets 1
2012-06-16 21:05:16.215046 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 1 packets 1
2012-06-16 21:05:16.216020 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 1 packets 1
2012-06-16 21:05:16.246523 > ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 19 scid 0x0295
2012-06-16 21:05:16.246553 < ACL data: handle 1 flags 0x00 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0295 result 1 status 2
      Connection pending - Authorization pending
2012-06-16 21:05:16.246628 < ACL data: handle 1 flags 0x00 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0295 result 3 status 0
      Connection refused - security block
2012-06-16 21:05:16.247644 > ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0294 scid 0x0040
2012-06-16 21:05:16.250021 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 1 packets 1
2012-06-16 21:05:16.251039 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 1 packets 1
2012-06-16 21:05:16.655054 > HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 1 reason 0x13
    Reason: Remote User Terminated Connection

The devices seems trying again to handshake for serveral times, until the PC is giving up and hangs up the connection. As it looks like the device shall normally working fine and its no general issue, I am stuck here again as my knowledge about bluetooth is quite limited. If anyone having an idea, what is going wrong, I would really appreciate.

Phobeus · #3 16th March 2013, 12:28 PM

Sorry, that I have to resurrect this thread, but its been still an issue. At the moment, I am running Fedora 18 and still tries to get this running to use the Dualshock Sixaxis for control of a fedora media system. So far, I managed to get the device connected and paired via bluetooth with the computer. Bluetooth shows that the connection with the controller was established and "dmesg" reports:

Quote:

[164363.105183] input: Sony Computer Entertainment Wireless Controller as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.7/2-1.7:1.0/bluetooth/hci0/hci0:21/input27
[164363.106058] hid-generic 0005:0000:0000.000D: input,hidraw5: BLUETOOTH HID v0.00 Joystick [Sony Computer Entertainment Wireless Controller] on 00:26:83:33:0c:a0

That's all. The device seemsa not to be visible to the system as a controller and when using e.g. "system-settings" from KDE, it is shown as device, but no input is received. Using jstest fails as its always pointing to use a "/dev/input<number>" device, but this one is not created. (and I even have somehow the feeling might be outdated as HAL isn't used anymore?). So basically the pairing seems to be running, but for some reason no input device is created. When connecting the device via usb, everything works fine:

Quote:

[164637.321720] usb 1-1.5: new full-speed USB device number 13 using ehci-pci
[164637.429340] usb 1-1.5: New USB device found, idVendor=054c, idProduct=0268
[164637.429342] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[164637.429343] usb 1-1.5: Product: PLAYSTATION(R)3 Controller
[164637.429344] usb 1-1.5: Manufacturer: Sony
[164637.435772] sony 0003:054C:0268.000E: Fixing up Sony Sixaxis report descriptor
[164637.467453] input: Sony PLAYSTATION(R)3 Controller as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input28
[164637.467688] sony 0003:054C:0268.000E: input,hiddev0,hidraw5: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-0000:00:1a.0-1.5/input0
[164638.367622] sony 0003:054C:0268.000F: Fixing up Sony Sixaxis report descriptor
[164638.399705] input: Sony PLAYSTATION(R)3 Controller as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input29
[164638.399986] sony 0003:054C:0268.000F: input,hiddev0,hidraw5: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-0000:00:1a.0-1.5/input0

---
So basically not that much difference. I am seriously running out of ideas as I don't understand e.g. what these messages means or where within the /dev filesystem I can check, that it had been created successfully. So I would appreciate any help and just cannot believe, that I am the only one who tries to operate a sixaxis controller under linux

Many thanks in advance,
Florian