Package Details: sixpair 1.8-4

Git Clone URL: (read-only, click to copy)
Package Base: sixpair
Description: Associate PS3 Sixaxis controller to system bluetoothd via USB
Upstream URL:
Licenses: GPL
Submitter: None
Maintainer: ultraviolet
Last Packager: ultraviolet
Votes: 42
Popularity: 0.000668
First Submitted: 2008-08-15 14:35
Last Updated: 2015-07-07 21:47

Latest Comments

1 2 Next › Last »

prototypesolar commented on 2021-07-09 19:58

In 2021 this package stopped working, due to missing hcitool. You can fix this by downloading the hci tool from . configure this, then complie the hcitool file,

then move it to /bin it should work now'

it atleast did for me

LizziAS commented on 2021-03-26 07:56

Have you seen that since bluez was updated that the name of our controllers is now different and after pairing them they no longer connect. after blinking fast they blink slow and they never fix on just one of the 4 controller lights, 1,2,3 or 4. I said something to the bluez dev but i have not seen a fix so i thought i would mention it here.

ultraviolet commented on 2015-03-18 15:01

@weirddan455 thanks, fixed now. i never would have noticed because i'm not very frugal with my dependencies :3

weirddan455 commented on 2015-03-17 10:00

libusb-compat should be a full runtime dependency, not just a buildtime one. Without it, running the sixpair command fails with the following error:

sixpair: error while loading shared libraries: cannot open shared object file: No such file or directory

justin8 commented on 2014-06-09 07:22

This has the wrong checksum for sixpair.c, and also it is missing a dependency on bluez-utils. It fails to run without it.

bickman2k commented on 2014-05-21 01:15

sixpair.c has a new checksum from the website. Not sure if the version has changed. 0a9f03cd08f1483341f60c9b7cf5204c is the new checksum for sixpair.c. No other md5s changed.

bluerider commented on 2014-03-06 21:46

@ultraviolet: I fixed my issue. I used sixpair to change the bluetooth master, then I ran $ hcidump -t -X and located the bluetooth address of the controller. I then used bluetoothctl to trust the bluetooth address of the device when it was connecting. I let it stop trying to connect, once I pressed the PS button again it asked to pair and synced.

bluerider commented on 2014-03-04 19:09

@ultraviolet : Oh no, I just used sixpair to change the bluetooth master to my PC, then I attempted to connect the controller via bluetooth (in gnome-bluetooth and bluetoothctl). The device showed up but would disconnect rather quickly. In bluetoothctl, I manually trusted the device (w/o pin pairing) and the device still disconnected. I figured since bluez and the kernel has upstream sixaxis support, it would be more plug and play.

ultraviolet commented on 2014-03-04 03:58

have you thoroughly read/followed the source link? i've never had any issues with bluetooth-only mode on my system.

bluerider commented on 2014-03-04 03:11

I was wondering how to use this a sixaxis controller solely over bluetooth. The controller keeps connecting/disconnecting for me.