Announcement

Collapse
No announcement yet.

Linux 6.2 Adds Sony DualShock 4 Controller Support To Newer PlayStation Driver

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • marlock
    replied
    Originally posted by AlanTuring69 View Post
    This is great and all but when can I run Linux on the controller?
    It's probably running BSD

    Leave a comment:


  • AlanTuring69
    replied
    This is great and all but when can I run Linux on the controller?

    Leave a comment:


  • Linuxxx
    replied
    Originally posted by marlock View Post

    I'm curious about the current state of:
    - rumble ("stereo vs. mono", intensity)
    - gyro
    - force feedback
    - speaker
    - mic
    - button press intensity
    - force feedback (and its intensity)
    - battery level
    - firmware updates

    I used a DualSense with Steam early on (the extra controller arrived before the console so I just had to test it ) and none of the above existed iirc.

    PS: is there even any game that's able to use all of these on linux if it's all supported by the kernel/driver stack?
    Atleast Sony's PC ports of Spider-Man & Uncharted 4, but PS5's DualSense controller needs to be plugged in via USB, which sucks!

    Leave a comment:


  • marlock
    replied
    Originally posted by Danny3 View Post
    Great!
    I hope now they work to add support also for the other things that are still not supported on these controllers when they're connected to a Linux computer compared to a PlayStation devices.
    I'm curious about the current state of:
    - rumble ("stereo vs. mono", intensity)
    - gyro
    - force feedback
    - speaker
    - mic
    - button press intensity
    - force feedback (and its intensity)
    - battery level
    - firmware updates

    I used a DualSense with Steam early on (the extra controller arrived before the console so I just had to test it ) and none of the above existed iirc.

    PS: is there even any game that's able to use all of these on linux if it's all supported by the kernel/driver stack?
    Last edited by marlock; 18 December 2022, 12:14 PM.

    Leave a comment:


  • marlock
    replied
    Also global driver support can't be confused for userspace interaction...

    apps like "SC Controller" allows several controllers to work to interact with the OS and any app without Steam running in the background, but it's needed because Gnome, KDE and etc do not support controller input themselves and require controller input translation into keyboard and/or mouse input.

    The kernel recognition of the device happens regardless of the DE not knowing what to do with it, and apps should pick up on it if they have controller support.

    As for steam-devices being needed, IMHO this is an old issue of linux distros caring too little about controller udev rules so a third-party focused on gaming (aka Valve) ends up needing to provide an optional package for it...

    I have hope that Valve's partnership with KDE devs will spur more interest towards controllers being recognized by DEs as proper input for driving the OS. KDE's "Plasma Bigscreen" looks promising, but I'd love if this eventually includes "desktop" DEs not just specialty ones.

    In any case, SC Controller is a pretty viable stopgap measure and is deeply customizable (albeit not as deep as Steam's customization, which is just THE most flexible thing ever)

    Leave a comment:


  • skeevy420
    replied
    Originally posted by bple2137 View Post

    Maybe those rules are part of some packages that I always install, like steam-devices. I don't know why I don't have to use them. Maybe it's a different variant/revision of the controller.
    By one minute. ONE MINUTE

    Some distributions pull those in automagically when you install Steam. Usually installing Steam is good enough....unless you do it from Flatpak where it'll prompt you to install steam-devices or something equivalent.
    Last edited by skeevy420; 18 December 2022, 09:50 AM.

    Leave a comment:


  • skeevy420
    replied
    Statix

    You can use game-devices-udev get the hookup on controller udev rules. It's also in the AUR since you're on Manjaro. Another all-in-one alternative is to use Steam's udev rules.

    Remember to like and subscribe, guys.

    And if you really like that, you'll really enjoy this content from my sponsor, Marijuana.

    Leave a comment:


  • bple2137
    replied
    Originally posted by Linuxxx View Post

    Here, copy & paste the following (fully) into the terminal:



    Now execute the following:
    Code:
    sudo udevadm control --reload-rules
    Replug your DS4 controller & thank me later...

    Nah, just kidding, no need to do so!
    Maybe those rules are part of some packages that I always install, like steam-devices. I don't know why I don't have to use them. Maybe it's a different variant/revision of the controller.

    Leave a comment:


  • Linuxxx
    replied
    Originally posted by Statix View Post

    I am using the latest Manjaro (tried many others) release thus I expected it to work out of the box, but for some reason it is no go for me. When I connect via bluetooth or USB, only the trackpad works. The D-pad, joysticks and buttons aren't recognized. I am using Epic Games via Lutris which doesn't have PS4 controller support like Steam to play games. No matter how I launch the game only the trackpad works (In this case playing Control). To get the PS4 controller to work fully (no rumble) I have to invoke ds4drv --hidraw through the terminal before I launch the game.
    Here, copy & paste the following (fully) into the terminal:

    cat << EOF | sudo tee /etc/udev/rules.d/99-ds4-controllers.rules
    # DualShock 4 over USB
    KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="05c4", MODE="0666"

    # DualShock 4 Wireless Adapter over USB
    KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="0ba0", MODE="0666"

    # DualShock 4 Slim over USB
    KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="09cc", MODE="0666"

    # DualShock 4 over Bluetooth
    KERNEL=="hidraw*", KERNELS=="*054C:05C4*", MODE="0666"

    # DualShock 4 Slim over Bluetooth
    KERNEL=="hidraw*", KERNELS=="*054C:09CC*", MODE="0666"
    ‚ÄčEOF
    Now execute the following:
    Code:
    sudo udevadm control --reload-rules
    Replug your DS4 controller & thank me later...

    Nah, just kidding, no need to do so!

    Leave a comment:


  • Statix
    replied
    Originally posted by bple2137 View Post

    I don't know what you're talking about. For me it doesn't matter how I run a game, most of them just pick it up without issues whether it's Lutris, Heroic, Bottles, native games, RetroArch and virtually any app that can use controller that I know of. It doesn't matter if it's cable or BT. I never used the ds4drv. I run bleeding edge distro, but I have it for 2 years at this point and it was always plug and play literally.

    Actually I'm afraid I'll have to use something like ds360 emulator now as I do with the DualSense (hid-playstation) if I want to use anything but Steam. It works, but it's an extra step. If I use it directly it's mapped incorrectly.
    I am using the latest Manjaro (tried many others) release thus I expected it to work out of the box, but for some reason it is no go for me. When I connect via bluetooth or USB, only the trackpad works. The D-pad, joysticks and buttons aren't recognized. I am using Epic Games via Lutris which doesn't have PS4 controller support like Steam to play games. No matter how I launch the game only the trackpad works (In this case playing Control). To get the PS4 controller to work fully (no rumble) I have to invoke ds4drv --hidraw through the terminal before I launch the game.

    Leave a comment:

Working...
X