DescriptionAntoine Saroufim
2019-09-01 09:22:16 UTC
Created attachment 1610473[details]
Logs
1. Please describe the problem:
After a kernel update, the DaulShock 4 controller no longer provides any input. It connects but its led color does not change and it does not provide any input events whatsoever.
The only relevant logs are:
sony 0005:054C:09CC.0006: Failed to get calibration data from Dualshock 4
sony 0005:054C:09CC.0006: failed to claim input
kernel device:+hid:0005:054C:09CC.0006
2. What is the Version-Release number of the kernel:
kernel-5.3.0-0.rc6.git0.1.fc31.x86_64
3. Did it work previously in Fedora? If so, what kernel version did the issue
Yes, it worked previously and it started appearing with kernel-5.3.0-0.rc6.git0.1.fc31.x86_64
4. Can you reproduce this issue? If so, please provide the steps to reproduce
the issue below:
Simply pairing the device and connecting it produces this problem
5. Does this problem occur with the latest Rawhide kernel? To install the
Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
``sudo dnf update --enablerepo=rawhide kernel``:
I haven't tried the rawhide kernel.
6. Are you running any modules that not shipped with directly Fedora's kernel?:
No, I have a stock Fedora Silverblue system
7. Please attach the kernel logs. You can get the complete kernel log
for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
issue occurred on a previous boot, use the journalctl ``-b`` flag.
Attached
Additional info: My phone can still pair with Fedora just fine. The controller can pair with my phone just fine. It's when the controller tries to pair with Fedora that I experience the issue so I'm assuming that there is no fault with the hardware of either one. I have also tried resetting the controller and pairing it again multiple times with no luck.
I've run into the same issue on Arch Linux while running mainline kernels.
5.3-rc5 was fine, rc6 and rc7 are broken. The controller still works fine when connected with a USB cable.
I've bisected the regression and submitted a fix upstream [1].
[1] https://lore.kernel.org/patchwork/patch/1125039/
If you're going to monitor this, you should probably watch the second version of the patch [1].
If I remember, I will post here once it gets merged.
[1] https://lore.kernel.org/patchwork/patch/1125068/
Created attachment 1610473 [details] Logs 1. Please describe the problem: After a kernel update, the DaulShock 4 controller no longer provides any input. It connects but its led color does not change and it does not provide any input events whatsoever. The only relevant logs are: sony 0005:054C:09CC.0006: Failed to get calibration data from Dualshock 4 sony 0005:054C:09CC.0006: failed to claim input kernel device:+hid:0005:054C:09CC.0006 2. What is the Version-Release number of the kernel: kernel-5.3.0-0.rc6.git0.1.fc31.x86_64 3. Did it work previously in Fedora? If so, what kernel version did the issue Yes, it worked previously and it started appearing with kernel-5.3.0-0.rc6.git0.1.fc31.x86_64 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Simply pairing the device and connecting it produces this problem 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: I haven't tried the rawhide kernel. 6. Are you running any modules that not shipped with directly Fedora's kernel?: No, I have a stock Fedora Silverblue system 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. Attached Additional info: My phone can still pair with Fedora just fine. The controller can pair with my phone just fine. It's when the controller tries to pair with Fedora that I experience the issue so I'm assuming that there is no fault with the hardware of either one. I have also tried resetting the controller and pairing it again multiple times with no luck.