Bug 1479089 - 8bitdo SFC30 controller not registering after plugging in
8bitdo SFC30 controller not registering after plugging in
Status: NEW
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2017-08-07 18:44 EDT by Ernesto Gutierrez
Modified: 2017-08-07 18:47 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
journalctl on monitor (1.84 KB, text/plain)
2017-08-07 18:44 EDT, Ernesto Gutierrez
no flags Details
evtest output (894 bytes, text/plain)
2017-08-07 18:44 EDT, Ernesto Gutierrez
no flags Details
hid-recorder (241 bytes, text/plain)
2017-08-07 18:45 EDT, Ernesto Gutierrez
no flags Details
journalctl on motherboard (938 bytes, text/plain)
2017-08-07 18:46 EDT, Ernesto Gutierrez
no flags Details

  None (edit)
Description Ernesto Gutierrez 2017-08-07 18:44:03 EDT
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):
and all kernels under F26, latest kernel in F25

How reproducible:

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.
Comment 1 Ernesto Gutierrez 2017-08-07 18:44 EDT
Created attachment 1310386 [details]
evtest output
Comment 2 Ernesto Gutierrez 2017-08-07 18:45 EDT
Created attachment 1310387 [details]
Comment 3 Ernesto Gutierrez 2017-08-07 18:46 EDT
Created attachment 1310388 [details]
journalctl on motherboard
Comment 4 Ernesto Gutierrez 2017-08-07 18:47:23 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.