zoggins
commented
4 years ago root password isn't documented but if you login as debian/temppwd you can
sudo su into root and change the password to what ever you want. What
image are you using? This is the wired Pro, not the Pro+? THat is odd
that it shows up as a Xbox 360 controller. Let me see what I debug on my
end. I don't have a Pro, but I can get one to test.
On Sat, Oct 19, 2019 at 12:23 AM mn1213 notifications@github.com wrote:
I have a wired 8bitdo SN30 Pro -> Beaglebone Green -> Nintendo Switch (via. StarTech Dual A to Micro B cable USB2HAUBY1).
The controller powers on as player one (in spite of other controllers) and rumbles momentarily. Neither the Switch or the RetroSpy client can read inputs from the controller. It does not seem to matter in which order I connect everything.
dmesg logs the device as a 360 pad on connect. Rarely, it shows up as a Pro Controller for just a second.
[ 410.120831] usb 1-1: New USB device found, idVendor=057e, idProduct=2009 [ 410.120853] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 410.120862] usb 1-1: Product: Pro Controller [ 410.120871] usb 1-1: Manufacturer: Nintendo Co., Ltd. [ 410.120879] usb 1-1: SerialNumber: 000000000001 [ 410.144662] input: Nintendo Co., Ltd. Pro Controller as /devices/platform/ocp/47400000.usb/47401c00.usb/musb-hdrc.1/usb1/1-1/1-1:1.0/0003:057E:2009.0001/input/input2 [ 410.148793] hid-generic 0003:057E:2009.0001: input,hidraw0: USB HID v1.11 Joystick [Nintendo Co., Ltd. Pro Controller] on usb-musb-hdrc.1-1/input0 [ 411.490604] usb 1-1: USB disconnect, device number 4 [ 412.253553] usb 1-1: new full-speed USB device number 5 using musb-hdrc [ 412.410380] usb 1-1: New USB device found, idVendor=045e, idProduct=028e [ 412.410402] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 412.410411] usb 1-1: Product: Controller [ 412.410419] usb 1-1: Manufacturer: Controller [ 412.410427] usb 1-1: SerialNumber: Controller [ 412.427481] input: Microsoft X-Box 360 pad as /devices/platform/ocp/47400000.usb/47401c00.usb/musb-hdrc.1/usb1/1-1/1-1:1.0/input/input3
$ lsusb Bus 001 Device 013: ID 045e:028e Microsoft Corp. Xbox360 Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Any advice on troubleshooting the issue would be greatly appreciated!
(Also, is the root password documented, and is there an equivalent to jstest in this image?)
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/zoggins/RetroSpy/issues/97?email_source=notifications&email_token=AE2CEVT3OTRW6Y2774JYDV3QPKYWPA5CNFSM4JCOTI7KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HS463RA, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE2CEVVJO5675GUJCM2KKL3QPKYWPANCNFSM4JCOTI7A .
mn1213
40wattrange
I have a wired 8bitdo SN30 Pro -> Beaglebone Green -> Nintendo Switch (via. StarTech Dual A to Micro B cable USB2HAUBY1).
The controller powers on as player one (in spite of other controllers) and rumbles momentarily. Neither the Switch or the RetroSpy client can read inputs from the controller. It does not seem to matter in which order I connect everything.
dmesg logs the device as a 360 pad on connect. Rarely, it shows up as a Pro Controller for just a second.
Any advice on troubleshooting the issue would be greatly appreciated!
(Also, is the root password documented, and is there an equivalent to jstest in this image?)