Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

X-Arcade Trimode PCB in Xinput mode not functioning #1988

Closed
prof-kayos opened this issue Dec 16, 2024 · 1 comment
Closed

X-Arcade Trimode PCB in Xinput mode not functioning #1988

prof-kayos opened this issue Dec 16, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@prof-kayos
Copy link

Describe the bug

When connecting a X-Arcade Trimode PCB in Xinput mode to the system, it is detected but does not function. Tested in Windows w/o issue.

Product in question:
https://support.xgaming.com/support/solutions/articles/12000051721-tri-mode-pcb

Have validated it is not functioning in the Gamepad Test Tool under Desktop mode as well

Appreciate any assistance in resolving as I'd love to get this up and running on my arcade cabinet

lsusb

bazzite@bazzite:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 011: ID 045e:02d1 Microsoft Corp. Xbox One Controller
Bus 001 Device 012: ID 045e:02d1 Microsoft Corp. Xbox One Controller

journalctl

Dec 16 12:14:33 bazzite kernel: usb 1-9: new full-speed USB device number 16 using xhci_hcd
Dec 16 12:14:34 bazzite kernel: usb 1-9: New USB device found, idVendor=045e, idProduct=02d1, bcdDevice= 1.02
Dec 16 12:14:34 bazzite kernel: usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec 16 12:14:34 bazzite kernel: usb 1-9: Product: Controller
Dec 16 12:14:34 bazzite kernel: usb 1-9: Manufacturer: Microsoft
Dec 16 12:14:34 bazzite kernel: usb 1-9: SerialNumber: 7EED8C846656
Dec 16 12:14:34 bazzite kernel: input: Microsoft X-Box One pad as /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.0/input/input57
Dec 16 12:14:34 bazzite mtp-probe[20396]: checking bus 1, device 16: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9"
Dec 16 12:14:34 bazzite mtp-probe[20396]: bus: 1, device: 16 was not an MTP device
Dec 16 12:14:34 bazzite kernel: pcieport 0000:00:1c.6: AER: Correctable error message received from 0000:00:1c.6
Dec 16 12:14:34 bazzite kernel: pcieport 0000:00:1c.6: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Dec 16 12:14:34 bazzite kernel: pcieport 0000:00:1c.6:   device [8086:a116] error status/mask=00000001/00002000
Dec 16 12:14:34 bazzite kernel: pcieport 0000:00:1c.6:    [ 0] RxErr                  (First)
Dec 16 12:14:34 bazzite (udev-worker)[20382]: input57: Process '/bin/input-remapper-control --command autoload --device ' failed with exit code 2.
Dec 16 12:14:34 bazzite kernel: pcieport 0000:00:1c.6: AER: Correctable error message received from 0000:00:1c.6
Dec 16 12:14:34 bazzite kernel: pcieport 0000:00:1c.6: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Dec 16 12:14:34 bazzite kernel: pcieport 0000:00:1c.6:   device [8086:a116] error status/mask=00000001/00002000
Dec 16 12:14:34 bazzite kernel: pcieport 0000:00:1c.6:    [ 0] RxErr                  (First)
Dec 16 12:14:34 bazzite kernel: pcieport 0000:00:1c.6: AER: Correctable error message received from 0000:00:1c.6
Dec 16 12:14:34 bazzite kernel: pcieport 0000:00:1c.6: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Dec 16 12:14:34 bazzite kernel: pcieport 0000:00:1c.6:   device [8086:a116] error status/mask=00000001/00002000
Dec 16 12:14:34 bazzite kernel: pcieport 0000:00:1c.6:    [ 0] RxErr                  (First)
Dec 16 12:14:35 bazzite (udev-worker)[20380]: js0: Process '/bin/input-remapper-control --command autoload --device /dev/input/js0' failed with exit code 5.
Dec 16 12:14:35 bazzite kernel: pcieport 0000:00:1c.6: AER: Correctable error message received from 0000:00:1c.6
Dec 16 12:14:35 bazzite kernel: pcieport 0000:00:1c.6: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Dec 16 12:14:35 bazzite kernel: pcieport 0000:00:1c.6:   device [8086:a116] error status/mask=00000001/00002000
Dec 16 12:14:35 bazzite kernel: pcieport 0000:00:1c.6:    [ 0] RxErr                  (First)
Dec 16 12:14:35 bazzite (udev-worker)[20382]: event3: Process '/bin/input-remapper-control --command autoload --device /dev/input/event3' failed with exit code 5.
Dec 16 12:14:35 bazzite mtp-probe[20425]: checking bus 1, device 16: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9"
Dec 16 12:14:35 bazzite mtp-probe[20425]: bus: 1, device: 16 was not an MTP device
Dec 16 12:14:35 bazzite kernel: pcieport 0000:00:1c.6: AER: Correctable error message received from 0000:00:1c.6
Dec 16 12:14:35 bazzite kernel: pcieport 0000:00:1c.6: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Dec 16 12:14:35 bazzite kernel: pcieport 0000:00:1c.6:   device [8086:a116] error status/mask=00000001/00002000
Dec 16 12:14:35 bazzite kernel: pcieport 0000:00:1c.6:    [ 0] RxErr                  (First)
Dec 16 12:14:35 bazzite kernel: pcieport 0000:00:1c.6: AER: Correctable error message received from 0000:00:1c.6
Dec 16 12:14:35 bazzite kernel: pcieport 0000:00:1c.6: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Dec 16 12:14:35 bazzite kernel: pcieport 0000:00:1c.6:   device [8086:a116] error status/mask=00000001/00002000
Dec 16 12:14:35 bazzite kernel: pcieport 0000:00:1c.6:    [ 0] RxErr                  (First)
Dec 16 12:14:35 bazzite kernel: input: Microsoft X-Box 360 pad 0 as /devices/virtual/input/input58
Dec 16 12:14:36 bazzite kernel: pcieport 0000:00:1c.6: AER: Correctable error message received from 0000:00:1c.6
Dec 16 12:14:36 bazzite kernel: pcieport 0000:00:1c.6: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Dec 16 12:14:36 bazzite kernel: pcieport 0000:00:1c.6:   device [8086:a116] error status/mask=00000001/00002000
Dec 16 12:14:36 bazzite kernel: pcieport 0000:00:1c.6:    [ 0] RxErr                  (First)
Dec 16 12:14:36 bazzite (udev-worker)[20382]: input58: Process '/bin/input-remapper-control --command autoload --device ' failed with exit code 2.

What did you expect to happen?

X-Input to function inside of Steam

Output of rpm-ostree status

Deployments:
  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:84712e223557d8eb2c3d0ba7fc39070715f6ba796463326405de4bd7d9116a10
                  Version: 41.20241216 (2024-12-16T05:01:17Z)
                     Diff: 107 upgraded

● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:0cd31e35ae9391e7c75c7abe986da65fd8868546783acaf945eec8e77db79d9a
                  Version: 41.20241211 (2024-12-11T07:34:35Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:7552ff702817c06e3c84f6177985b44013b578e57fbe193c19fca823de5dfadd
                  Version: 40.20240914.0 (2024-09-15T21:07:53Z)

Hardware

Dell Optiplex 7040 with external 600w PSU and AMD RX 580 8GB video

Extra information or context

No response

@dosubot dosubot bot added the bug Something isn't working label Dec 16, 2024
@prof-kayos
Copy link
Author

After deeper investigation , issue was resolved by switching to standard RS232 to USB adapter from controller. Please close.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant