Skip to main content

Fix a USB Game Controller Disconnecting When Idle

I have a USB game controller that works flawlessly during gameplay, but it keeps disconnecting and reconnecting every ~40 seconds whenever it is left idle. While it is mostly harmless in practice, it is annoying to see the kernel messages are flooded with messages about the game controller.

Many online resources, such as the Arch Wiki, suggest disabling USB autosuspend to fix this. Unfortunately, that didn’t solve the issue in my case. I suspect the controller expects to be continuously polled rather than entering a power-saving state, especially since it immediately tries to reconnect after dropping.

Since I primarily use this controller by passing it through to a VM, I needed a way to manually manage its connection state. Here is the workaround that eventually did the trick:

  • Add the following rule to udev. This ensures the controller is ignored by the host system upon connection. ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="xxxx", ATTR{idProduct}=="xxxx", PROGRAM="systemctl is-active --quiet my-gaming-vm.service", ATTR{authorized}="0"
    • Note the PROGRAM condition in the udev rule, it is needed because the VM might not grab the device fast enough (e.g. due to a slow boot), in which case the game controller will disconnect and reconnect. In this case we don’t want to write 0 to authorized.
  • Write 1 to <DEV_PATH>/authorized right before booting the VM. This authorizes the controller so it can be successfully forwarded.
  • Write 0 to <DEV_PATH>/authorized after the VM shuts down. This disconnects the driver once again.

How to Find DEV_PATH

In the steps above, <DEV_PATH> refers to the device path of the USB controller. Normally, this can be conveniently found by following the symbolic link in /dev/input/by-id. However, because we are forcefully disconnecting the device by writing to authorized, that standard method won’t work here.

One can find the <DEV_PATH> by traversing and matching /sys/bus/usb/devices/*/{idVendor,idProduct}, but a much cleaner approach is to create a custom symbolic link using udev.

Add the following rule (note that there is no ACTION condition): SUBSYSTEM=="usb", ATTR{idVendor}=="xxxx", ATTR{idProduct}=="xxxx", SYMLINK+="my-controller"

With this rule in place, I can easily obtain the correct device path as: /sys$(udevadm info --query=path --name=/dev/my-controller)

Alternative Solutions (Untested)

  • The xone driver handles device polling differently and may resolve the issue natively.
  • Run cat /dev/input/by-id/my-controller > /dev/null as a background process to keep the device active.
  • Use usbguard to manually allow/deny the device.
Labels:

Comments

Post a Comment

Popular posts from this blog

A Rocky Migration: Moving from docker-compose to Podman and gVisor

I've been running a few containers for several years. They were all running under rootless Docker with a single user. Initially, I planned to  migrate the containers to VMs , but I couldn't get a stable workflow after about two months of effort. Later,  gVisor caught my attention , and I decided to migrate to Podman with gVisor instead. The new plan is to run each container with  --userns=auto  and use Quadlet for systemd integration. This approach provides better isolation and makes writing firewall rules easier. I'm now close to migrating all my containers. Here are a couple of rough edges I'd like to share. Network Layout I compared  various networking options  and spent a few hours trying the one-interface-per-group approach before giving up. I settled on a single macvlan network and decided to use static IP addresses for my containers. To prevent a randomly assigned IP address from conflicting with a predefined one, I allocated a large IP range for my ...
Post a Comment
Read More »

GameConqueror 0.09 -- Linux Game Hacking Tool

If you are a game hacker If you've been looking for a `CheatEngine for Linux` Then you can't miss this. ============================================== GameConqueror is a game hacking tool for linux, it's written in PyGTK and uses scanmem as its backend. It's supposed to be with most useful features of CheatEngine for Linux. Currently, I've implemented almost everything about scanning, involving variant data types and scan types: Data Types: int{8/16/32/64}, float{32/64}, unknown type(int or float) and unknown width(will try each of them), byte array and string Scan Types: equal, greater, less, changed, unchanged, increased(by), decreased(by) This should be enough for most cases, so I decided to release it at the current status. ============================================= Here's how you can get it PPA (for Ubuntu users) https://launchpad.net/~coolwanglu/+archive/scanmem (I've not test it in 32bit environments or Jaunty, do please inform me if it doe...
Post a Comment
Read More »

Fix Google Security Code

Google Security Code (http://g.co/sc) is one type of 2-step verification. This is particularly useful when security keys and passkeys are not available. I have been using it in my LXC containers, until today I found out that it stopped working. It just kept saying "The code is invalid". It is easy to rule out some factors: The code works on other browsers on my laptop. The code works on other devices that are directly connected to the router. So it appears that Google also checks IP addresses besides the security code. Recently I have IPv6 enabled, so most devices that are directly connected to the router have both IPv4 and IPv6 addresses. But  I only enabled IPv4 for my LXC containers. So I guess when a code is generated by device A and used by device B, Google should be able to check that device A and device B are closely located. But in my case, IPv6 address appears on device A but not on device B, which may look suspicious. To fix the problem, I just needed to disable IPv...
Post a Comment
Read More »