38
8BitDo controllers? (lemmy.world)
submitted 11 months ago by to c/linux_gaming@lemmy.world
36 comments fedilink hide all child comments
 

I have an 8BitDo Pro 2 controller I've used a bunch without issue on Windows, now I'm moving to Linux (Mint specifically) and I'm having trouble getting the controller to work. It's supposed to work with Linux, but I can't get it to work. Steam doesn't detect the controller in its settings.

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 2 points 11 months ago (1 child)

I did all that, but it's still no different than before. It still only works by cable.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 11 months ago

    The last thing I can suggest are the last two comments on the steam-devices repo: https://github.com/ValveSoftware/steam-devices/issues/64#issuecomment-3092449971

    Try adding these to a file such as /etc/udev/rules.d/71-8bitdo-pro-2.rules

    # 8bitdo pro 2 bluetooth hidraw
ACTION!="remove", KERNEL=="hidraw*", KERNELS=="*2DC8:6006*", MODE="0660", TAG+="uaccess"

    and/or

    ACTION!="remove", KERNEL=="hidraw*", KERNELS=="*2DC8:6012*", MODE="0660", TAG+="uaccess"

    The reason I added ACTION!="remove" is due to a recent change with systemd.

    ACLs for device nodes requested by "uaccess" udev tag are now always applied/updated by systemd-udevd through "uaccess" udev builtin, and systemd-logind no longer applies/updates ACLs but triggers "change" uevents to make systemd-udevd apply/update ACLs. Hence, the "uaccess" udev tag should be set not only on "add" action but also on "change" action, and it is highly recommended that the rule is applied all actions except for "remove" action.

    Recommended example:

    ACTION!="remove", SUBSYSTEM=="hidraw", TAG+="uaccess"

    The following example does not work since v258:

    ACTION=="add", SUBSYSTEM=="hidraw", TAG+="uaccess"

  • permalink
  • fedilink
  • source
  • parent