PS3 Sixaxis controller/joystick usb stopped working, regression in linux-image-extra-3.13.0-27-generic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
After applying upgrades to my 14.04 installations and rebooting, suddenly the sony sixaxis usb joystick/controller input device which I use a lot will now no longer appear as a joystick device. It happens on at least two machines with the newest 14.04 updates as of a couple of days ago. See below for kernel messages.
I believe the actual kernel error message for this bug is:
"Jun 5 11:36:51 machine kernel: [47062.524566] sony 0003:054C:
After looking at the kernel sources I believe this is a problem with the hid_sony kernel module. The changelog for linux-image-
The same bug/regression, it appears, was reported on askubuntu.com some days ago, see this link:
http://
Version information:
$ lsb_release -d
Description: Ubuntu 14.04 LTS
$ uname -a
Linux valley 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
# dpkg -S /lib/modules/
linux-image-
dmesg:
Jun 5 11:36:50 machine kernel: [47062.360175] usb 2-1.1.3.1: new full-speed USB device number 19 using ehci-pci
Jun 5 11:36:51 machine kernel: [47062.486789] usb 2-1.1.3.1: New USB device found, idVendor=054c, idProduct=0268
Jun 5 11:36:51 machine kernel: [47062.486797] usb 2-1.1.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jun 5 11:36:51 machine kernel: [47062.486802] usb 2-1.1.3.1: Product: PLAYSTATION(R)3 Controller
Jun 5 11:36:51 machine kernel: [47062.486806] usb 2-1.1.3.1: Manufacturer: Sony
Jun 5 11:36:51 machine kernel: [47062.498624] sony 0003:054C:
Jun 5 11:36:51 machine kernel: [47062.524383] input: Sony PLAYSTATION(R)3 Controller as /devices/
Jun 5 11:36:51 machine kernel: [47062.524563] sony 0003:054C:
Jun 5 11:36:51 machine kernel: [47062.524566] sony 0003:054C:
Jun 5 11:36:51 machine kernel: [47062.556374] sony: probe of 0003:054C:0268.000E failed with error -38
Jun 5 11:36:51 machine mtp-probe: checking bus 2, device 19: "/sys/devices/
Jun 5 11:36:51 machine mtp-probe: bus: 2, device: 19 was not an MTP device
Brad Figg (brad-figg) wrote : Missing required logs. | #1 |
Changed in linux (Ubuntu): | |
status: | New → Incomplete |
tags: | added: trusty |
oh (oystein-homelien) wrote : | #2 |
I am unable to run this command because I don't have access to the relevant machine now and I believe also there is enough information/logs in the bug report to reproduce and/or fix the bug.
PS: It happens on several machines, with several different sixaxis controllers.
I will try to change the status to "Confirmed".
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
oh (oystein-homelien) wrote : | #3 |
I booted one of the machines on kernel 3.13.0-24-generic and the sixaxis device now works (no error message in dmesg and appears as /dev/input/js0). I have tried -26, -27 and -29 and the bug is in those but not in -24, as far as I can see.
Joseph Salisbury (jsalisbury) wrote : | #4 |
Would it be possible for you to test the latest upstream stable kernel? Refer to https:/
If this bug is fixed in the mainline kernel, please add the following tag 'kernel-
If the mainline kernel does not fix this bug, please add the tag: 'kernel-
If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".
Thanks in advance.
[0] kernel.
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
status: | Confirmed → Incomplete |
tags: | added: kernel-da-key needs-bisect regression-update |
Levi Bard (taktaktaktaktaktaktaktaktaktak) wrote : | #5 |
I can confirm that this bug affects me as well with -29, but not with -24.
I tried the 03131102 mainline kernel, but the DKMS step failed for nvidia-337 with that one.
James McNabb (hemihua) wrote : | #6 |
Same problem for me too. Just got a new HDD and installed Ubuntu 14.04 (used to run Debian testing, controller used to autodetect and work correctly when plugged in). Wouldn't recognise the controller, syslog had the following info when I plug in the controller:
Jun 7 17:56:39 Hemi kernel: [ 596.260269] usb 7-2: new full-speed USB device number 3 using uhci_hcd
Jun 7 17:56:40 Hemi kernel: [ 596.684014] usb 7-2: New USB device found, idVendor=054c, idProduct=0268
Jun 7 17:56:40 Hemi kernel: [ 596.684020] usb 7-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jun 7 17:56:40 Hemi kernel: [ 596.684023] usb 7-2: Product: PLAYSTATION(R)3 Controller
Jun 7 17:56:40 Hemi kernel: [ 596.684026] usb 7-2: Manufacturer: Sony
Jun 7 17:56:40 Hemi kernel: [ 596.720038] sony 0003:054C:
Jun 7 17:56:40 Hemi kernel: [ 596.764039] input: Sony PLAYSTATION(R)3 Controller as /devices/
Jun 7 17:56:40 Hemi kernel: [ 596.764694] sony 0003:054C:
Jun 7 17:56:40 Hemi kernel: [ 596.764699] sony 0003:054C:
Jun 7 17:56:40 Hemi mtp-probe: checking bus 7, device 3: "/sys/devices/
Jun 7 17:56:40 Hemi kernel: [ 596.784474] sony: probe of 0003:054C:0268.0006 failed with error -38
Jun 7 17:56:40 Hemi mtp-probe: bus: 7, device: 3 was not an MTP device
Julian Alarcon (julian-alarcon) wrote : apport information | #7 |
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=
InstallationDate: Installed on 2014-02-16 (111 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140216)
MachineType: Dell Inc. Dell System Vostro 3450
Package: linux (not installed)
ProcFB:
0 inteldrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.127.2
Tags: trusty
Uname: Linux 3.13.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/26/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.name: 0K8WHD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Dell System Vostro 3450
dmi.sys.vendor: Dell Inc.
tags: | added: apport-collected |
Julian Alarcon (julian-alarcon) wrote : AlsaInfo.txt | #8 |
Julian Alarcon (julian-alarcon) wrote : BootDmesg.txt | #9 |
Julian Alarcon (julian-alarcon) wrote : CRDA.txt | #10 |
Julian Alarcon (julian-alarcon) wrote : CurrentDmesg.txt | #11 |
Julian Alarcon (julian-alarcon) wrote : IwConfig.txt | #12 |
Julian Alarcon (julian-alarcon) wrote : Lspci.txt | #13 |
Julian Alarcon (julian-alarcon) wrote : Lsusb.txt | #14 |
Julian Alarcon (julian-alarcon) wrote : ProcCpuinfo.txt | #15 |
Julian Alarcon (julian-alarcon) wrote : ProcEnviron.txt | #16 |
Julian Alarcon (julian-alarcon) wrote : ProcInterrupts.txt | #17 |
Julian Alarcon (julian-alarcon) wrote : ProcModules.txt | #18 |
Julian Alarcon (julian-alarcon) wrote : PulseList.txt | #19 |
Julian Alarcon (julian-alarcon) wrote : RfKill.txt | #20 |
Julian Alarcon (julian-alarcon) wrote : UdevDb.txt | #21 |
Julian Alarcon (julian-alarcon) wrote : UdevLog.txt | #22 |
Julian Alarcon (julian-alarcon) wrote : WifiSyslog.txt | #23 |
Julian Alarcon (julian-alarcon) wrote : | #24 |
Hi!
I got the same problem. I just attached more information. This is the syslog iutput:
Jun 7 12:54:28 devolo wpa_supplicant[
Jun 7 12:54:56 devolo kernel: [ 104.606913] usb 2-1.3: new full-speed USB device number 5 using ehci-pci
Jun 7 12:54:56 devolo kernel: [ 104.749919] usb 2-1.3: New USB device found, idVendor=054c, idProduct=0268
Jun 7 12:54:56 devolo kernel: [ 104.749931] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jun 7 12:54:56 devolo kernel: [ 104.749937] usb 2-1.3: Product: PLAYSTATION(R)3 Controller
Jun 7 12:54:56 devolo kernel: [ 104.749942] usb 2-1.3: Manufacturer: Sony
Jun 7 12:54:56 devolo mtp-probe: checking bus 2, device 5: "/sys/devices/
Jun 7 12:54:56 devolo mtp-probe: bus: 2, device: 5 was not an MTP device
Jun 7 12:54:56 devolo kernel: [ 104.804576] sony 0003:054C:
Jun 7 12:54:56 devolo kernel: [ 104.847547] input: Sony PLAYSTATION(R)3 Controller as /devices/
Jun 7 12:54:56 devolo kernel: [ 104.847941] sony 0003:054C:
Jun 7 12:54:56 devolo kernel: [ 104.847945] sony 0003:054C:
Jun 7 12:54:56 devolo kernel: [ 104.879133] sony: probe of 0003:054C:0268.0003 failed with error -38
Let me know if you more info. I will try mainline kernels.
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
Julian Alarcon (julian-alarcon) wrote : | #25 |
Ok, I just tested 4 different kernels from mainline http://
v3.13-trusty
v3.13.3-trusty
v3.13.6-trusty
v3.13.11-trusty
And all of them works! I got this message in /var/log/syslog
Jun 7 13:21:05 devolo kernel: [ 194.737714] usb 2-1.3: USB disconnect, device number 5
Jun 7 13:21:09 devolo kernel: [ 199.292548] usb 2-1.3: new full-speed USB device number 6 using ehci-pci
Jun 7 13:21:09 devolo kernel: [ 199.435734] usb 2-1.3: New USB device found, idVendor=054c, idProduct=0268
Jun 7 13:21:09 devolo kernel: [ 199.435738] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jun 7 13:21:09 devolo kernel: [ 199.435740] usb 2-1.3: Product: PLAYSTATION(R)3 Controller
Jun 7 13:21:09 devolo kernel: [ 199.435741] usb 2-1.3: Manufacturer: Sony
Jun 7 13:21:09 devolo kernel: [ 199.470403] sony 0003:054C:
Jun 7 13:21:09 devolo kernel: [ 199.513611] input: Sony PLAYSTATION(R)3 Controller as /devices/
Jun 7 13:21:09 devolo kernel: [ 199.513941] sony 0003:054C:
Jun 7 13:21:09 devolo mtp-probe: checking bus 2, device 6: "/sys/devices/
Jun 7 13:21:09 devolo mtp-probe: bus: 2, device: 6 was not an MTP device
Already test the ps3 controller with jstest-gtk and worked fine.
Also, I tested Ubuntu kernels:
3.13.0-26-generic
3.13.0-27-generic
3.13.0-29-generic
Same problem as initialy reported. Seems to be a problem with Ubuntu kernel, not upstream.
Joseph Salisbury (jsalisbury) wrote : Test with newer development kernel (3.13.0-24.46) | #26 |
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.
With the recent release of this Ubuntu release, would like to confirm if this bug is still present. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following commands in a terminal window:
sudo apt-get update
sudo apt-get dist-upgrade
If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.
If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.
Thank you for your help, we really do appreciate it.
Changed in linux (Ubuntu): | |
status: | Confirmed → Incomplete |
tags: | added: kernel-request-3.13.0-24.46 |
Roberto Maurizzi (r-maurizzi) wrote : | #27 |
Kernel Version: 3.13.0-29.53
Jun 15 01:48:48 bebop kernel: [644505.504141] usb 3-3: new full-speed USB device number 11 using xhci_hcd
Jun 15 01:48:48 bebop kernel: [644505.538650] usb 3-3: New USB device found, idVendor=054c, idProduct=0268
Jun 15 01:48:48 bebop kernel: [644505.538660] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jun 15 01:48:48 bebop kernel: [644505.538665] usb 3-3: Product: PLAYSTATION(R)3 Controller
Jun 15 01:48:48 bebop kernel: [644505.538669] usb 3-3: Manufacturer: Sony
Jun 15 01:48:48 bebop kernel: [644505.550542] sony 0003:054C:
Jun 15 01:48:48 bebop kernel: [644505.576407] input: Sony PLAYSTATION(R)3 Controller as /devices/
Jun 15 01:48:48 bebop kernel: [644505.576940] sony 0003:054C:
Jun 15 01:48:48 bebop kernel: [644505.576945] sony 0003:054C:
Jun 15 01:48:48 bebop kernel: [644505.592553] sony: probe of 0003:054C:0268.0008 failed with error -38
Bug still present
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
Joseph Salisbury (jsalisbury) wrote : | #28 |
@Julian, can you confirm if the bug exists on 3.13.11.2:
http://
If the bug does not exist on that upstream kernel, we will have to perform a kernel bisect on the Ubuntu kernels to see if a SAUCE patch introduced this.
Roberto Maurizzi (r-maurizzi) wrote : | #29 |
@salisbury, I tested 3.13.11-
Jun 21 14:55:29 bebop kernel: [ 365.133571] usb 3-3: USB disconnect, device number 3
Jun 21 14:55:34 bebop kernel: [ 370.168060] usb 3-3: new full-speed USB device number 4 using xhci_hcd
Jun 21 14:55:34 bebop kernel: [ 370.202363] usb 3-3: New USB device found, idVendor=054c, idProduct=0268
Jun 21 14:55:34 bebop kernel: [ 370.202366] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jun 21 14:55:34 bebop kernel: [ 370.202367] usb 3-3: Product: PLAYSTATION(R)3 Controller
Jun 21 14:55:34 bebop kernel: [ 370.202369] usb 3-3: Manufacturer: Sony
Jun 21 14:55:34 bebop kernel: [ 370.214032] sony 0003:054C:
Jun 21 14:55:34 bebop kernel: [ 370.239601] input: Sony PLAYSTATION(R)3 Controller as /devices/
Jun 21 14:55:34 bebop kernel: [ 370.239804] sony 0003:054C:
Jun 21 14:55:34 bebop mtp-probe: checking bus 3, device 4: "/sys/devices/
Jun 21 14:55:34 bebop mtp-probe: bus: 3, device: 4 was not an MTP device
hunter (theprinceofhesh) wrote : | #30 |
Please god fix this! The steam summer sale is killing me because im ONLY BUYING CONTROLLER GAMES! GAH!
[13978.653617] usb 1-1.3: New USB device found, idVendor=054c, idProduct=0268
[13978.653623] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[13978.653626] usb 1-1.3: Product: PLAYSTATION(R)3 Controller
[13978.653628] usb 1-1.3: Manufacturer: Sony
[13978.688277] sony 0003:054C:
[13978.731239] input: Sony PLAYSTATION(R)3 Controller as /devices/
[13978.731580] sony 0003:054C:
[13978.731585] sony 0003:054C:
[13978.754765] sony: probe of 0003:054C:0268.0007 failed with error -38
joseangelmadrid (joseangelmadrid) wrote : apport information | #31 |
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=
InstallationDate: Installed on 2014-04-18 (67 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: ASUSTeK COMPUTER INC. N56VZ
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.127.3
Tags: trusty
Uname: Linux 3.13.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/02/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N56VZ.215
dmi.board.
dmi.board.name: N56VZ
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: N56VZ
dmi.product.
dmi.sys.vendor: ASUSTeK COMPUTER INC.
joseangelmadrid (joseangelmadrid) wrote : AlsaInfo.txt | #32 |
joseangelmadrid (joseangelmadrid) wrote : BootDmesg.txt | #33 |
joseangelmadrid (joseangelmadrid) wrote : CRDA.txt | #34 |
joseangelmadrid (joseangelmadrid) wrote : CurrentDmesg.txt | #35 |
joseangelmadrid (joseangelmadrid) wrote : IwConfig.txt | #36 |
joseangelmadrid (joseangelmadrid) wrote : Lspci.txt | #37 |
joseangelmadrid (joseangelmadrid) wrote : Lsusb.txt | #38 |
joseangelmadrid (joseangelmadrid) wrote : ProcCpuinfo.txt | #39 |
joseangelmadrid (joseangelmadrid) wrote : ProcEnviron.txt | #40 |
joseangelmadrid (joseangelmadrid) wrote : ProcInterrupts.txt | #41 |
joseangelmadrid (joseangelmadrid) wrote : ProcModules.txt | #42 |
joseangelmadrid (joseangelmadrid) wrote : PulseList.txt | #43 |
joseangelmadrid (joseangelmadrid) wrote : RfKill.txt | #44 |
joseangelmadrid (joseangelmadrid) wrote : UdevDb.txt | #45 |
joseangelmadrid (joseangelmadrid) wrote : UdevLog.txt | #46 |
joseangelmadrid (joseangelmadrid) wrote : WifiSyslog.txt | #47 |
Steven Brown (steven-w-j-brown) wrote : | #48 |
@jsalisbury, I can also confirm that kernel 3.13.11-
hunter (theprinceofhesh) wrote : | #49 |
Bug also exists in kernel version 3.13.0-30-generic
results from dmesg after plugging in controller in 3.13.0-30-generic:
[ 30.004372] usb 1-1.3: new full-speed USB device number 4 using ehci-pci
[ 30.147393] usb 1-1.3: New USB device found, idVendor=054c, idProduct=0268
[ 30.147399] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 30.147402] usb 1-1.3: Product: PLAYSTATION(R)3 Controller
[ 30.147405] usb 1-1.3: Manufacturer: Sony
[ 30.182194] sony 0003:054C:
[ 30.225093] input: Sony PLAYSTATION(R)3 Controller as /devices/
[ 30.225580] sony 0003:054C:
[ 30.225582] sony 0003:054C:
[ 30.244499] sony: probe of 0003:054C:0268.0007 failed with error -38
ProfessorKaos64 (mdeguzis) wrote : | #50 |
Same error as #49 @hunter:
Kernel: 3.13.0-30-generic
This is really holding up my RetroRig project : (https:/
Please, please, help.
[ 327.993910] sony 0003:054C:
[ 328.043114] sony 0003:054C:
[ 328.043119] sony 0003:054C:
[ 328.076291] sony: probe of 0003:054C:0268.0005 failed with error -38
[ 1047.573150] sony 0003:054C:
[ 1047.617683] sony 0003:054C:
[ 1047.617688] sony 0003:054C:
[ 1047.636242] sony: probe of 0003:054C:0268.0006 failed with error -38
ProfessorKaos64 (mdeguzis) wrote : | #51 |
Still exists in 3.13.0-31-generic as well. (trusty-proposed)
[ 109.778489] sony 0003:054C:
[ 109.828401] sony 0003:054C:
[ 109.828406] sony 0003:054C:
[ 109.864280] sony: probe of 0003:054C:0268.0005 failed with error -38
Brandon (brandon-lee-mcanally) wrote : | #52 |
Had the same problem with Kernel 3.13.0-30. I upgraded the kernel to 3.14 from linux-image-
brandon@Desktop:~$ uname -a
Linux Desktop 3.14.0-
Peter Björling (peter-bjoerling) wrote : | #53 |
I'm having this problem with the 3.13.0-30-generic kernel
[ 1045.796741] usb 1-1.2.4: New USB device found, idVendor=054c, idProduct=0268
[ 1045.796747] usb 1-1.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1045.796750] usb 1-1.2.4: Product: PLAYSTATION(R)3 Controller
[ 1045.796752] usb 1-1.2.4: Manufacturer: Sony
[ 1045.831274] sony 0003:054C:
[ 1045.874178] input: Sony PLAYSTATION(R)3 Controller as /devices/
[ 1045.874464] sony 0003:054C:
[ 1045.874467] sony 0003:054C:
[ 1045.912728] sony: probe of 0003:054C:0268.0005 failed with error -38
ProfessorKaos64 (mdeguzis) wrote : | #54 |
I can also confirm the 3.14 kernel fixes this regression and I have tested this for about a week on the LTS 14.04 base install.
dualshock3nerd (dualshock3nerd) wrote : | #55 |
- ps3-1326725.diff Edit (75.7 KiB, text/plain)
I did a manual bisect of the ubuntu trusty kernel tree and the last "good" (controller working) commit is:
commit 73ffcac5867519f
Author: Jiri Kosina
HID: hidraw: make comment more accurate and nicer
The first sure "bad" (controller not working) commit I found is:
commit 6d8e891822be26e
Author: Frank Praznik
HID: Add transport-driver callbacks to the hid_ll_driver struct
Between those two commits there are three more commits.
I could not test by cheking out these three commits one by one because the kernel failed to build.
Here they are:
commit c96bd945d3061dc
Author: Benjamin Tissoires
HID: add inliners for ll_driver transport-layer callbacks
commit b0eff3d87fabad1
Author: Benjamin Tissoires
HID: i2c-hid: implement ll_driver transport-layer callbacks
commit aa6c390c4d59c9f
Author: Benjamin Tissoires
HID: remove hid_get_raw_report in struct hid_device
I then tried to revert these commits in order:
c96bd945d3061dc
b0eff3d87fabad1
aa6c390c4d59c9f
And, after rebuilding the kernel, the controller worked again.
The problem is that those commits (among many others) were pushed to fix http://
By doing so many heavy changes to hid were made.
This broke the hid-sony kernel driver.
After further research I found that the same author of those commits (Benjamin Tissoires) submitted a patch that supposedly fixed the issue:
https:/
So I tried to backport that patch.
To make my life easier I fetched the latest version of these files directly from https:/
drivers/
drivers/
drivers/
And added only a couple of lines to these files:
drivers/
drivers/
include/linux/hid.h
Recompiled and it worked.
I tested both dualshock 3 and dualshock 4 via usb. Both working.
If anyone would like to test it:
git clone git://kernel.
cp ps3-1326725.diff ubuntu-trusty
cd ubuntu-trusty
git apply ps3-1326725.diff
and recompile the kernel.
I added the patch as an attachment.
Whether to apply/rewrite/
I Hope this is useful.
Please don't make me recompile the kernel another 20+ times. :)
tags: | added: patch |
Joseph Salisbury (jsalisbury) wrote : | #56 |
Sorry for the delay. It would be good to know if the fix in 3.14 already made it's way into the upstream 3.13.11.5 stable kernel. It can be downloaded from:
http://
Can you give that kernel a try and post back?
dualshock3nerd (dualshock3nerd) wrote : | #57 |
@jsalisbury
I can confirm that the controller is indeed working with that kernel.
It seems that the fix is already there.
ProfessorKaos64 (mdeguzis) wrote : | #58 |
@dualshock3nerd
Does this mean that a normal 14.04 LTS user can perform a dist-upgrade and get to this kernel level? I currently upgrade users in a project I maintain to 3.14, and doing it the "proper way" would be nice.
dualshock3nerd (dualshock3nerd) wrote : | #59 |
...or much more likely that the bug was never there in the first place... :(
Looking into /usr/src/
To be more precise I'm talking about some of the changes in this commit:
commit aa6c390c4d59c9f
Author: Benjamin Tissoires
HID: remove hid_get_raw_report in struct hid_device
I can see that "hid_get_
while, for instance, in /usr/src/
That leads me to believe that the fix from 3.14 is not there because the bug itself is not there either.
The bug was caused by backporting some synaptics hid driver from upstream to the trusty kernel.
That's why the ubuntu trusty kernel is affected while 3.13 mainline is not.
ProfessorKaos64 (mdeguzis) wrote : | #60 |
I did get a report that 3.13.0-32 was released into the mainline, you can upgrade to it, but it was help back for me, and I had to specify to install the new kernel.
ProfessorKaos64 (mdeguzis) wrote : | #61 |
I just upgraded to 3.13.0-32, and jstest-gtk still shows no controller (of course, I am pressing the PS button, I know).
Cruxic (cruxic) wrote : | #62 |
I had this problem but got my controller working by installing the "trusty" 3.14.1 kernel from http://
It's was mostly painless by following this guide: https:/
(Search for "python kmpd.py")
Hugo Costelha (hugo-costelha) wrote : | #63 |
The problem also exists in Ubuntu 12.04.5 (kernel 3.13.0-34-generic).
Joseph Salisbury (jsalisbury) wrote : | #64 |
The Trusty kernel now has the 3.13.11.6 upstream updates. However, as suggested by dualshock3nerd in comment #59, the bug may never have been introduced in mainline, only trusty.
It would be great if you could apply the latest trusty updates, to get the 3.13.11.6 updates and see if this bug still exists. If it does, we can investigate further.
dualshock3nerd (dualshock3nerd) wrote : | #65 |
@jsalisbury
Current trusty 3.13.0-34 is affected.
I then tested latest 3.13.0-35 from trusty proposed repository and the bug is still there.
Even 3.13.0-35.62 from trusty git repo suffers from the same bug.
Unsurprisingly, mainline 3.13.11.6 is not affected by this bug at all.
dualshock3nerd (dualshock3nerd) wrote : | #66 |
- sixaxis-trusty.patch Edit (3.0 KiB, text/plain)
I took some more time to research and I wrote a proper patch this time.
It's just six lines of code.
What this patch does is basically restore "hid_get_
All the lines that are added by this patch were previously removed by this commit:
commit aa6c390c4d59c9f
Author: Benjamin Tissoires
HID: remove hid_get_raw_report in struct hid_device
More in depth description:
The field "hid_get_
The hid-sony kernel driver in 3.13 relied on that field because the ps3 controller needs special quirks in order to set it's operational mode.
Function "hid_hw_
This patch fixes the issue in a much cleaner way and leaves the changes necessary to fix bug http://
To anyone willing to test it and report back:
git clone git://kernel.
cp sixaxis-
cd ubuntu-trusty
git apply sixaxis-
CONCURRENCY_
After that, install the deb packages created and reboot using the new kernel.
@jsalisbury
I hope this helps to finally put an end to our investigation.
ProfessorKaos64 (mdeguzis) wrote : | #67 |
@dualshock3nerd
Why apply a patch that adds a new kernel, if 3.14 works well? An inplace solution that follows the normal kernel updates is what I think most are looking for. Maybe I am looking at that wrong and you meant for the upstream folks to take that and apply it to current trusty kernel code.
In any case, great work.
dualshock3nerd (dualshock3nerd) wrote : | #68 |
@mdeguzis
Thank you and yes: you read that wrong :)
A patch like this is meant to be applied to current ubuntu 14.04 kernel (3.13).
When I wrote "using the new kernel" i meant "using the new kernel image that you just built yourself with the commands above".
Writing this patch is all I can do for now. Whether to include this patch or an alternative solution to ubuntu standard updates is ubuntu kernel team's call.
Straximus (straximus) wrote : | #69 |
@dualshock3nerd
Followed your instructions, but my compile ended with the following:
CC fs/dcookies.o
LD fs/built-in.o
make[1]: Leaving directory `/home/
make: *** [debian/
Emanem (em4n3m) wrote : | #70 |
@straximus
Compiling a kernel and installing it is something you should be comfy. I suggest you document yourself before you undertake this task (you know, in case of issues and whatnot...)
Emanem (em4n3m) wrote : | #71 |
@dualshock3nerd
Compiled without issues, I hope this gets included in the next kernel official release.
dualshock3nerd (dualshock3nerd) wrote : | #72 |
@em4n3m
Awesome, thank you for confirming this.
@straximus
My bad: I should have mentioned that, to compile your own kernel, you need some packages installed first and maybe some other requirements to meet.
I can't see the actual compilation error in that output but, if it's the first time you compile a kernel on that machine, you probably just miss some packages installed.
Please refer to Ubuntu wiki pages like
https:/
https:/
(Warning: these are not for beginners and they might be outdated!)
Anyway thank you for taking the time to try this :)
Straximus (straximus) wrote : | #73 |
@dualshock3nerd
Thanks for the links. I got things sorted and compiled the kernel without issue. Everything is working as expected now. Thanks for the patch! :)
Emanem (em4n3m) wrote : | #74 |
@all
Do we know if any action is being taken for the next patch?
Thanks,
em4n3m
Joseph Salisbury (jsalisbury) wrote : | #75 |
It might be worth sending the latest patch to the ubuntu kernel team mailing list:
<email address hidden>
And also cc the engineer that resolved bug 1305522
<email address hidden>
That way the patch can be reviewed and possibly considered for an SRU.
AceLan Kao (acelankao) wrote : | #76 |
Hi, I read the patch on #66, it looks very neat and fair enough.
dualshock3nerd, after you applied the patch, you have to do the following steps to build a formal patch
1. git add -u
2. git commit -a -e -s
Write the subject and comment for your patch, it will be more clear to add "UBUNTU: SAUCE: " in the subject
And you should put "BugLink: https:/
3. git format-patch -1
4. the send out the patch which git generate to <email address hidden>
dualshock3nerd (dualshock3nerd) wrote : | #77 |
Thanks for the directions!
I just sent the patch to the ubuntu kernel mailing list.
I hope git send-email formatted it right :)
Joseph Salisbury (jsalisbury) wrote : | #78 |
@dualshock3nerd
I haven't seen the email come across the ubuntu kernel mailing list yet. Can you see if you have any errors in your mail client?
dualshock3nerd (dualshock3nerd) wrote : | #79 |
@jsalisbury
Not only I forgot to subscribe to the mailing list but I even forgot to ask if it's required in order to send emails to it.
Wanted to ask because I didn't know if that was implied. Must be because of it I wonder?
Anyway I tried git send-email multiple times before sending it and it indeed works.
dualshock3nerd (dualshock3nerd) wrote : | #80 |
I sent it again and now it got through without issues.
Thank you for your patience.
Joseph Salisbury (jsalisbury) wrote : | #81 |
I don't think you need to be subscribed to send a mail to the list. I'll ask one of the list administrators about that.
James Hughes (james-hughes) wrote : | #82 |
@dualshock3nerd I just sent a reply to your kernel mailing list posting with what I believe to be an alternate fix.
I’ve run into this issue when using the DK1 and DK2. As I mentioned on the list, I’ve resolved the feature report issue by patching my 3.13.0-34 kernel with commit 975a68327 from mainline upstream. I've already patched and tested my kernel using 975a68327 -- if someone could test to see if 975a68327 also works for the sixaxis controller, it may be easier to get the patch accepted since it is already upstream.
dualshock3nerd (dualshock3nerd) wrote : | #83 |
@james-hughes
Thank you for pointing out mainline commit 975a68327.
I tested it for a while and I can confirm that applying that patch solves all of trusty's Sixaxis/Dualshock3 issues.
If it solves Oculus Rift's issues too I hope that the mainline patch is accepted.
ProfessorKaos64 (mdeguzis) wrote : | #84 |
Fixed for me here. Thanks!
laurence (loz-r) wrote : | #85 |
Did anything happen here
I'm believe I'm still experiencing this bug in 3.13.0-45
dualshock3nerd (dualshock3nerd) wrote : | #86 |
@laurence
Nope. Everything is working fine for me on 3.13.0-45.74
With the controller connected via USB, did you try pressing the central PS button before testing it with a program like jstest-gtk?
Does the command 'dmesg | grep sony' in terminal spit out something like "sony: probe of 0003:054C:0268.000E failed with error -38"?
If that's the case maybe you should be posting on bug #1353021 (this is a duplicate).
If not, then it's probably not this bug.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1326725
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.