New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ds4drv auto start not working #172
Comments
Same issue here, I solved it creating a systemd service.
(I've written it down from memory, forgive the possible misprints.) |
+1 Definitely solved my problem. I made one slight change:
|
No need to do a reboot after enabling the service.
I would prefer the above configuration with the an additional I am unsure but user space systemd services should go to My proposal for the file:
|
I think this service is included on repo, so it can be closed |
So I’ve followed all directions to include adding “ /usr/local/bin/ds4drv & “ to the rc.local file by going to “ sudo nano /etc/rc.local” and saved it with ctr+o /etc/rc.local
BUT whenever I reboot the Raspberry Pi the drivers / ds4drv won’t start unless I manually start it from the terminal with a “Sudo Ds4drv”
I’ve checked by running “jstest /dev/input/js0” in terminal when I reboot the Pi and attempt to pair the controller.
And
I’ve verified the /etc/rc.local file retained the changes and still has the “/usr/local/bin/ds4drv & “ line in it.
Only after doing “Sudo ds4drv” will the controller connect and then jstest work.
Not to sure why this is happening. I’ve tried to trouble shoot it to the best of my own abilities.
I’d like to get it to automatically connect if a controller is in pairing mode.
The text was updated successfully, but these errors were encountered: