Ubuntu 20.04 64 bits how install PS3 controller driver and remove qtsixa ?

aug7744

Member
Joined
Aug 12, 2020
Messages
87
Reaction score
10
Credits
875
I use Lubuntu 20.04 64 bit.
I had manually installed sixad_1.5.1+git20130130-0 and libusb-0.1-4_0.1.12 using deb packages because I could not get them using apt-get for Ubuntu 20.04.
I has two PS3 controllers.
After installing qtsiax the controller was connected and finally the LED was ON.
I had started one emulator and all buttons and analog controls had input, but the left analog up and down are inverted.
After a few minutes the left and right analog controls no longer had input for the emulator. It worked fine for a few minutes and then stopped.
Now the controller LED is off.
After I connected the second controller and the LED was ON, but no input.
Both controllers are displayed in command to display USB devices, but only the last tested controller display LED is on.
I do not understand if sixad_1.5.1+git20130130-0 and libusb-0.1-4_0.1.12 are compatible with Ubuntu 20.04 being that in deb package details it does not say it is for Ubuntu 20.04.

How do I remove both sixad_1.5.1+git20130130-0 and libusb-0.1-4_0.1.12 ?
What is the correct driver to install in Ubuntu 20.04 ?

Thanks for reply.
 


Lord Boltar

Well-Known Member
Joined
Nov 24, 2020
Messages
1,008
Reaction score
649
Credits
7,462
You should not need any drivers when pairing the to bluetooth those drivers are you are using are deprecated

Code:
sudo apt-get install bluez
- note this maybe already installed
Code:
systemctl enable bluetooth
Code:
systemctl start bluetooth
Code:
systemctl status bluetooth
Code:
bluetoothctl
Code:
agent on
Code:
default-agent
Code:
power on
Code:
discoverable on
Code:
pairable on
Code:
scan on

After executing the preceding commands, press the “PS3” button (logo’ed button) on the controller and the console prompt you to authorize it. Simply type “yes” and hit enter, your controller should now be paired.
 
OP
A

aug7744

Member
Joined
Aug 12, 2020
Messages
87
Reaction score
10
Credits
875
Thanks for your reply.
I not use bluetooth. the connection is wired.
Reading the qtsixa manual.pdf say that is only for bluetooth and not for wired and thus your post above mean not need qtsixa.
Unhappily not is being easy to connect PS3 controller using wired and working in Linux. Not is simple.
Thanks for any reply .
 

Lord Boltar

Well-Known Member
Joined
Nov 24, 2020
Messages
1,008
Reaction score
649
Credits
7,462
Is your controller a dual shock 3 or 4? both work with HIDAPI
If you have Synaptic Package Manager installed open it and look for -
libhidapi-libusb0, libhidapi-highdraw0, python3-hidapi
and install them then reboot then plug your controller back in
 
Last edited:
OP
A

aug7744

Member
Joined
Aug 12, 2020
Messages
87
Reaction score
10
Credits
875
DS3.
HIDAPI need to be installed ? Not is included in Ubuntu 20.04 ?
Is possible get using apt-get ?
 

Souza_sza

New Member
Joined
Oct 16, 2021
Messages
11
Reaction score
0
Credits
86
No it is not installed by default use Synaptic Package Manager
Code:
sudo apt install synaptic
If you do not have it then search for the 3 files
Hi!
i coudn't install this one libhidapi-highdraw0, i'm using mint 20.2. Would you know the reason? Thanks
 

Souza_sza

New Member
Joined
Oct 16, 2021
Messages
11
Reaction score
0
Credits
86
Thank you very much, but it seems I still with a non funcional joystick.
 

Lord Boltar

Well-Known Member
Joined
Nov 24, 2020
Messages
1,008
Reaction score
649
Credits
7,462
There is only one more trick I know of to get it working
1) install xboxdrv from the Synaptic Package Manager or with
Code:
sudo apt-get install xboxdrv
2) start xboxdrv with
Code:
sudo xboxdrv --detach-kernel-driver
3) If you press the Playstation button, the computer will receive its input and simulate it as an Xbox 360 controller, which should work the same as the playstation controller.

You can test the functionality of your controller through Jstest-gtk
Code:
sudo apt-get install jstest-gtk
now I am out of ideas
 

Souza_sza

New Member
Joined
Oct 16, 2021
Messages
11
Reaction score
0
Credits
86
There is only one more trick I know of to get it working
1) install xboxdrv from the Synaptic Package Manager or with
Code:
sudo apt-get install xboxdrv
2) start xboxdrv with
Code:
sudo xboxdrv --detach-kernel-driver
3) If you press the Playstation button, the computer will receive its input and simulate it as an Xbox 360 controller, which should work the same as the playstation controller.

You can test the functionality of your controller through Jstest-gtk
Code:
sudo apt-get install jstest-gtk
now I am out of ideas
I've tried that one before. I don't understand why it only works when connected with the cable. so I disconnect and press ps it fails.
 
OP
A

aug7744

Member
Joined
Aug 12, 2020
Messages
87
Reaction score
10
Credits
875
The dependencies are
libhidapi-dev
libhidapi-hidraw
libhidapi-libusb

Avoid qtsixa because will create problems.
The PS3 drivers are in OS. Only need plug the controller and press PS button.

Thanks for all replies.
 

Fanboi

Well-Known Member
Joined
Apr 16, 2021
Messages
358
Reaction score
270
Credits
4,288
Regarding your axis issue, can calibrate it in jstest-gtk. You can save/restore settings via jscal-store and jscal-restore. You'll be able to find it on modern distros under /dev/jsX where X is the number enumerated. Of note, some Wacom devices may be misidentified as joysticks. You can fix this, but you don't need to.
 

Souza_sza

New Member
Joined
Oct 16, 2021
Messages
11
Reaction score
0
Credits
86
Regarding your axis issue, can calibrate it in jstest-gtk. You can save/restore settings via jscal-store and jscal-restore. You'll be able to find it on modern distros under /dev/jsX where X is the number enumerated. Of note, some Wacom devices may be misidentified as joysticks. You can fix this, but you don't need to.

Man... it's hard
~$ bluetoothctl
Agent registered
[bluetooth]# scan
[bluetooth]# scan on
Discovery started
[CHG] Controller 80:2B:F9:A7:BD:0A Discovering: yes
[CHG] Device A0:5A:5C:5D:2A:27 Connected: yes
[NEW] Device 58:7F:C0:06:C3:AF 58-7F-C0-06-C3-AF
[Pro Controller]# trust A0:5A:5C:5D:2A:27
Changing A0:5A:5C:5D:2A:27 trust succeeded
[CHG] Device A0:5A:5C:5D:2A:27 Connected: no
[bluetooth]#
 

KGIII

Super Moderator
Staff member
Gold Supporter
Joined
Jul 23, 2020
Messages
4,064
Reaction score
3,737
Credits
32,636
I use Lubuntu 20.04 64 bit.

I don't have an answer for you. I just happened to notice that you said 20.04.

You moved up from 18.04! LOL I just recently (on another site) used you (not by name) as a reference for someone who was sticking with 18.04.
 

Fanboi

Well-Known Member
Joined
Apr 16, 2021
Messages
358
Reaction score
270
Credits
4,288
Man... it's hard
~$ bluetoothctl
Agent registered
[bluetooth]# scan
[bluetooth]# scan on
Discovery started
[CHG] Controller 80:2B:F9:A7:BD:0A Discovering: yes
[CHG] Device A0:5A:5C:5D:2A:27 Connected: yes
[NEW] Device 58:7F:C0:06:C3:AF 58-7F-C0-06-C3-AF
[Pro Controller]# trust A0:5A:5C:5D:2A:27
Changing A0:5A:5C:5D:2A:27 trust succeeded
[CHG] Device A0:5A:5C:5D:2A:27 Connected: no
[bluetooth]#
Not exactly what I was talking about (connectivity). I meant to address your axis issue since others have already given you information about connections.

Once connected, run: sudo apt-get install jstest-gtk -y && jjstest-gtk &
Right. you will see a window with anything considered a controller (this can include Wacoms, just ignore). Make note of each controller;s enumeration, eg: "js0". I'll name your controllers J1 and J2 for ease..
Select J1 and you'll see a test screen. Move all axes and buttons around. Note any other issues besides your inverted axis. Now, if you could post a screenshot of
Select "cmcalibration". Now a window pops up. We can ignore the fine-tuning and focus on the problem. As you can see, there's an "invert" box next to each axis. Check that and you're fixed.
Now exit jstest.
Remember I told you to note the device nodes for J1 and J2? Good. Use the following command:

jscal-store /dev/input/<J1's node>
jscal-restore /dev/input/<J2's node>


Changes are not persistant each reboot. To solve this, a simple startup script:

Code:
#! /bin/sh
jscal-restore /dev/input/<node for J1>
jscal-restore /dev/input/<node for J2>

Note: you may have issues with Wacom tablets connected as device enumeration is not 100% a guaranteed order. If this is the case, search for linux wacom joystick problem online. There are plenty posts about how to fix this with modprobe rules.

Protip: If your controller becomes unresponsive after a while of not being used, running jscal will wake it.
 
Last edited:

Souza_sza

New Member
Joined
Oct 16, 2021
Messages
11
Reaction score
0
Credits
86
Not exactly what I was talking about (connectivity). I meant to address your axis issue since others have already given you information about connections.

Once connected, run: sudo apt-get install jstest-gtk -y && jjstest-gtk &
Right. you will see a window with anything considered a controller (this can include Wacoms, just ignore). Make note of each controller;s enumeration, eg: "js0". I'll name your controllers J1 and J2 for ease..
Select J1 and you'll see a test screen. Move all axes and buttons around. Note any other issues besides your inverted axis. Now, if you could post a screenshot of
Select "cmcalibration". Now a window pops up. We can ignore the fine-tuning and focus on the problem. As you can see, there's an "invert" box next to each axis. Check that and you're fixed.
Now exit jstest.
Remember I told you to note the device nodes for J1 and J2? Good. Use the following command:

jscal-store /dev/input/<J1's node>
jscal-restore /dev/input/<J2's node>


Changes are not persistant each reboot. To solve this, a simple startup script:

Code:
#! /bin/sh
jscal-restore /dev/input/<node for J1>
jscal-restore /dev/input/<node for J2>

Note: you may have issues with Wacom tablets connected as device enumeration is not 100% a guaranteed order. If this is the case, search for linux wacom joystick problem online. There are plenty posts about how to fix this with modprobe rules.

Protip: If your controller becomes unresponsive after a while of not being used, running jscal will wake it.


Actually, even following the instructions, I still have a connection problem. my device is recognized and connected, right after disconnected for no apparent reason.

~$ bluetoothctl
Agent registered
[bluetooth]# agent on
Agent is already registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# discoverable on
Changing discoverable on succeeded
[bluetooth]# pairable on
Changing pairable on succeeded
[NEW] Device A0:5A:5C:5D:2A:27 Pro Controller
[Pro Controller]# pairable on
Changing pairable on succeeded
[Pro Controller]# scan on
Discovery started
[CHG] Controller 80:2B:F9:A7:BD:0A Discovering: yes
[CHG] Device A0:5A:5C:5D:2A:27 Connected: no
[DEL] Device A0:5A:5C:5D:2A:27 Pro Controller
[bluetooth]# pairable on
Changing pairable on succeeded
[bluetooth]# scan on
[NEW] Device A0:5A:5C:5D:2A:27 Pro Controller
[CHG] Device A0:5A:5C:5D:2A:27 Connected: no
[DEL] Device A0:5A:5C:5D:2A:27 Pro Controller
[NEW] Device A0:5A:5C:5D:2A:27 Pro Controller
[CHG] Device A0:5A:5C:5D:2A:27 Connected: no
[DEL] Device A0:5A:5C:5D:2A:27 Pro Controller
 

Fanboi

Well-Known Member
Joined
Apr 16, 2021
Messages
358
Reaction score
270
Credits
4,288
Did you:

pair A0:5A:5C:5D:2A:27
trust A0:5A:5C:5D:2A:27

before connect -ing?
Reset and try that.
 

Souza_sza

New Member
Joined
Oct 16, 2021
Messages
11
Reaction score
0
Credits
86
Did you:

pair A0:5A:5C:5D:2A:27
trust A0:5A:5C:5D:2A:27


before connect -ing?
Reset and try that.

[Pro Controller]# pair A0:5A:5C:5D:2A:27
Attempting to pair with A0:5A:5C:5D:2A:27
[Pro Controller]# trust A0:5A:5C:5D:2A:27
Changing A0:5A:5C:5D:2A:27 trust succeeded
[CHG] Device A0:5A:5C:5D:2A:27 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
 

Souza_sza

New Member
Joined
Oct 16, 2021
Messages
11
Reaction score
0
Credits
86
# HCId options
options {
autoinit yes;
security auto;
pairing multi;
passkey “1234”;
}
This thing means something?
 
$100 Digital Ocean Credit
Get a free VM to test out Linux!

Members online


Latest posts

Top