this post was submitted on 15 Oct 2025
37 points (95.1% liked)

Linux Gaming

28065 readers
162 users here now

Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.

This page can be subscribed to via RSS.

Original /r/linux_gaming pengwing by uoou.

No memes/shitposts/low-effort posts, please.

That includes posts generated by LLMs. It doesn’t matter if you “don’t have the time” or “would’ve written the same anyway”, or if “everyone’s doing it geez get with the times”.

For now it’ll also include “AI”-assisted projects that haven't had at least two months of (public, verifiable) dev time behind them.

Resources

Help:

Launchers/Game Library Managers:

General:

Discord:

IRC:

Matrix:

Telegram:

founded 3 years ago
MODERATORS
monolalia@lemmy.world
37
8BitDo controllers? (lemmy.world)
submitted 1 year ago by ArchmageAzor@lemmy.world to c/linux_gaming@lemmy.world
37 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
[–] ArchmageAzor@lemmy.world 2 points 1 year ago (1 children)

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

[–] mouse@midwest.social 1 points 1 year 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"