protonscr

[Regression] Dualsense touchpad is acting as a mouse again on SteamDeck

steamclosed Distro Family: SteamOSGeneral controller / Steam Input
ValveSoftware/steam-for-linux#9597 · opened 2023-06-15 by FrogTheFrog · updated 2024-10-27 · 8 comments · github
FFrogTheFrog 2023-06-15 github

Your system information

  • Steam client version (build number or date): the big update of June 15, 2023
  • Distribution (e.g. Ubuntu): SteamDeck (SteamOS 3.4.8)
  • Opted into Steam client beta?: No
  • Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

It seems that Dualsense touchpad acting as a mouse is a known issue and has been fixed in the past:
image

However, after the June 15, 2023 update, it is again acting as a mouse on SteamDeck. I have performed a factory reset just to make sure this issue is not caused by anything I did.

Steps for reproducing this issue:

  1. Connect Dualsense controller to SteamDeck.
  2. Navigate to Settings -> Controller -> Select PS5 Controller -> Begin Test
  3. Notice how touchpad registers as a mouse and the image does not show where you are touching it.

Additional notes/Workaround:

It seems that restarting the Steam client fixes the issue. This can be done by:

  • Going to the desktop mode and back.
  • Enabling the developer menu (in system settings) and clicking the newly available "Restart Steam" power option.
  • Calling the SteamClient.User.StartRestart() via chromium thingy.
RRodoMa92 2023-06-15 github

Can confirm the same on my end.

PPhilomorph 2023-07-09 github

The timing of this corresponds roughly to another Dual Sense regression:

https://github.com/ValveSoftware/steam-for-linux/issues/9739

So it looks like multiple issues - possibly related?

FFrogTheFrog 2023-11-21 github

There seems to be something wrong with hid_playstation module.
If the kernel loads it on demand when the controller is connected, then you have these sony controller related issues.

However, if you do a sudo modprobe hid_playstation before the DualSense controller is connected, then everything is fine.

A temporary (until SteamOS is updated) solution is to simply load it at boot time by creating this file:
/usr/lib/modules-load.d/hid-playstation.conf:

# load this module at boot as otherwise the DS4 and DualSense controllers have issues
hid_playstation

@kisak-valve sorry to ping you, but would it be possible to update the internal tracker (or whatever you guys are using) with this info? Maybe the devs could add this simple workaround at least until a proper solution is found.

FFrogTheFrog 2023-11-21 github

For normal users who want this fixed more permanently (until SteamDeck is factory-reset):

  • Open Konsole
  • Set sudo password if you haven't already by typing in the passwd command
  • Paste this one-liner into the Konsole and provide the sudo password
printf "# load this module at boot time as otherwise the DS4 and DualSense controllers have issues\nhid_playstation\n" | sudo tee /etc/modules-load.d/hid-playstation.conf > /dev/null
  • Reboot SteamDeck

To remove the workaround, simply delete the file:

sudo rm /etc/modules-load.d/hid-playstation.conf
Eendrift 2023-11-22 github

You don't need to disable steamos-readonly, you can just drop the file in /etc/modules-load.d/ instead.

FFrogTheFrog 2023-11-22 github

You don't need to disable steamos-readonly, you can just drop the file in /etc/modules-load.d/ instead.

Updated the command. Thanks!

I assume that /etc/modules-load.d/ is also wiped during SteamOS update, right?

RRodoMa92 2023-11-22 github

You don't need to disable steamos-readonly, you can just drop the file in /etc/modules-load.d/ instead.

Updated the command. Thanks!

I assume that /etc/modules-load.d/ is also wiped during SteamOS update, right?

No, it's an overlay fs, so it should be sticking correctly.

FFrogTheFrog 2024-10-27 github

As of 3.6.19, the hid driver is being loaded by default, so I'm closing this issue.

Upstream links