Bug 1479089
| Summary: | 8bitdo SFC30 controller not registering after plugging in | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ernesto Gutierrez <ernesto.g3> | ||||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 26 | CC: | ernesto.g3, gansalmon, ichavero, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2018-05-20 16:50:57 UTC | Type: | Bug | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
Created attachment 1310386 [details]
evtest output
Created attachment 1310387 [details]
hid-recorder
Created attachment 1310388 [details]
journalctl on motherboard
As can be seen from the different logs, other than the journalctl entries; the device is not registered by evtest or hid-recorder On a fresh F25 install, the controller worked just fine. We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs. Fedora 26 has now been rebased to 4.15.4-200.fc26. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 27, and are still experiencing this issue, please change the version to Fedora 27. If you experience different issues, please open a new bug report for those. This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Issue is 'kind of' fixed in F27. If you leave the controller plugged in and reboot the machine, fedora will detect the joystick as /dev/input/js0 as expected. Not perfect but at least you can get it to work that way. FYI bluetooth connection does work out of the box. |
Created attachment 1310385 [details] journalctl on monitor Description of problem: The 8bitdo SFC30 controller does not work after it is plugged in with the USB cable. No js0 entry is created under /dev/input Version-Release number of selected component (if applicable): 4.11.11-300.fc26.x86_64 and all kernels under F26, latest kernel in F25 How reproducible: 100% Steps to Reproduce: 1. Connect controller to the system using USB cable Actual results: No js0 entry exists in /dev/input Expected results: js0 should exist in /dev/input Additional info: I'm attaching different logs after I plug in the controller for your analysis: - journalctl - evtest - hid-recorder /proc/bus/input/devices does not list the device either I get a slightly different output in journalctl depending on where i plug in the controller: monitor vs motherboard. I've provided both logs.