Skip to content
This repository was archived by the owner on Aug 3, 2023. It is now read-only.
This repository was archived by the owner on Aug 3, 2023. It is now read-only.

DualSense support #10

Closed
Closed

Description

@loveisfoss

Hey, thanks for this awesome piece of work!

What does the following mean?
hid-playstation - DualSense controller (Note: not in mainline kernel yet as of now)

Using Debian bookworm with kernel 5.16. The DualSense controller is working without problems, generally. I suppose DualSense support has been included in kernel 5.16, is this right? But when trying to use evdevhook:

$ ./evdevhook
Connected motion devices:
$

...shows no motion devices.

$ ./evdevhook ./config_templates/playstation.json
...stays here forever and does nothing.

After a little web searching I wondered if I should modprobe the playstation module (although the controller is working fine already), but I got this:

$ sudo modprobe hid-playstation
modprobe: FATAL: Module hid-playstation not found in directory /lib/modules/5.16.0-1-amd64

Any ideas?

Activity

  1. v1993 commented on Feb 20, 2022

    @v1993
    Owner

    I'm not quite sure about current status of dualsense support in linux kernel - I don't own dualsense myself (nor plan to get one). When the quoted sentence was being written a separate DKMS module still was requires for DS5 support - that's what I know.

    You can try running sudo chmod a+rw /dev/input/event* and checking if motion device appears after that - if it does, you need to set up udev rule for access, if it does not - you need to install DKMS module. Sadly, I don't really have time to help in depth with either outcome - you'll have to figure those out yourself.

    Finally, check out #3 and edit mapping in ./config_templates/playstation.json to what is suggested there (it also contains an explanation why I haven't added this manually... yet) to have motion work correctly.

  2. loveisfoss commented on Feb 20, 2022

    @loveisfoss
    Author

    Thanks for your reply! Here come some observations.

    The driver hid-playstation seems to be present on kernel 5.15 and not on kernel 5.16 in my Debian installation. A notable difference is that the moving of cursor by touchpad can be used when booting with kernel 5.15 but not with 5.16.

    On kernel 5.16
    The controller seemed to work without problems. Even native motion controls of DualSense work on yuzu (the native one, named sdl - not with DSU). So, it seems that something has possibly changed on kernel 5.16 and the module hid-playstation is not used anymore, but the controller is working without problems (minus the touchpad cursor control). It is not being detected by evdevhook, though.

    On kernel 5.15:
    The module hid-playstation exists and is being loaded AFTER the controller is being paired/connected to the pc. If one does lsmod | grep -i playstation without having the controller connected, it is not going to show anything. But the module is being loaded normally after the controller is connected and you can see it by doing lsmod.

    The command you mention is needed in my case.
    sudo chmod a+rw /dev/input/event*
    After doing this, evdevhook detects the motion device of DualSense (but only on kernel 5.15 where the module hid-playstation exists).

    Tested on yuzu and it works (meaning not the native one, named sdl - but through DSU).

    Tested on cemu/cemuhook (running with wine/lutris) and it seems to be detected in the cemuhook submenu. It is not working in-game though and the option to use motion controls ingame is grayed out. This may have to do with my lutris/wine implementation, I may look into it later. @Mrbinaer how did you make it work on cemu? Do you run cemu with wine?

  3. v1993 commented on Feb 20, 2022

    @v1993
    Owner

    On cemu you must use gamepad for gyro to work. I'd also recomment against using cemuhook, especially that now cemu supports software video decoding, removing the last issue cemuhook solved.

    No idea what's the deal with kernel module status, sadly.

  4. Repository owner locked and limited conversation to collaborators on Feb 20, 2022
  5. converted this issue into a discussion #11 on Feb 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions