[SOLVED] USB Gamepad recognized by Plasma 5 but no longer by Steam/antimicro

RadicalDreamer · 06-26-2020, 02:02 AM

It was working fine a few days ago. Plasma 5 picks it up and key presses (check attached screenshot). Steam says "No Controllers Detected." antimicro says "No Joysticks have been found."

RadicalDreamer · 06-26-2020, 03:00 PM

I tried the gamepad with antimicro on 14.2 and it works. It was working earlier this week on my Current install. Could an update earlier this week affected it?

Pixxt · 06-28-2020, 07:29 AM

Same thing here with my XBOX 360 controller. It works with KDE input settings and a couple of emulators and games, but does work not in steam or a couple other games and emulators. All were working fine before my updating current today after about 10 days from last update

Alien Bob · 06-28-2020, 08:13 AM

Some 32bit compatibility package missing from the multiib set (assuming you are on 64bit Slackware)?

RadicalDreamer · 06-28-2020, 11:46 AM

I have all of multilib installed except "alsa-plugins-compat32-1.2.2-x86_64-1compat32."

Code:

bash-5.0# dmesg | grep Smart
[    9.359475] usb 3-1.4: Product: SmartJoy PLUS Adapter
[   10.430698] input: Gamtec.,Ltd SmartJoy PLUS Adapter as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.4/3-1.4:1.0/0003:0925:0005.0006/input/input25
[   10.434933] smartjoyplus 0003:0925:0005.0006: input,hidraw5: USB HID v1.00 Joystick [Gamtec.,Ltd SmartJoy PLUS Adapter] on usb-0000:00:1a.0-1.4/input0
[   10.439015] smartjoyplus 0003:0925:0005.0006: Force feedback for SmartJoy PLUS PS2/USB adapter

Alien Bob · 06-28-2020, 12:37 PM

I meant, perhaps there's a 32bit Slackware package that I omitted and that I still need to add to the multilib 'compat32' set?

RadicalDreamer · 06-28-2020, 02:05 PM

Quote:

Originally Posted by Alien Bob

I meant, perhaps there's a 32bit Slackware package that I omitted and that I still need to add to the multilib 'compat32' set?

I don't think it is that unless something new added to Slackware changed something but I don't understand how that could affect antimicro? antimicro stopped picking up the gamepad and I built that as 64 bit. On a relative's computer I have Slackware Current64 installed too with multilib and Plasma 5 and it hasn't been updated since last weekend. antimicro picks up my gamepad on it. antimicro binds keyboard keys to gamepad buttons. I installed the updated Steam slackbuild this week and udev is complaining about:

Code:

bash-5.0# dmesg | grep steam
[    4.009782] udevd[234]: invalid key/value pair in file /lib/udev/rules.d/60-steam-input.rules on line 42, starting at character 82 ('u')
[    4.025663] udevd[235]: invalid key/value pair in file /lib/udev/rules.d/60-steam-input.rules on line 42, starting at character 82 ('u')
[    7.363302] udevd[708]: invalid key/value pair in file /lib/udev/rules.d/60-steam-input.rules on line 42, starting at character 82 ('u')
[   17.500501] udevd[709]: invalid key/value pair in file /lib/udev/rules.d/60-steam-input.rules on line 42, starting at character 82 ('u')

I think that has been there for awhile. That is what the slackbuild installed. I haven't touched them.

Code:

bash-5.0# lsusb
Bus 004 Device 004: ID 0925:0005 Lakeview Research Gamtec.,Ltd SmartJoy PLUS Adapter

Pixxt · 06-28-2020, 02:05 PM

According to https://bbs.archlinux.org/viewtopic.php?id=256943 the new libwacom in current is the problem and patching with https://github.com/sbstnk/libwacom/c...8bca923ae6ecb1 per https://git.archlinux.org/svntogit/p...c4a09cfeb25905 solves the problem.

Pixxt · 06-28-2020, 02:51 PM

In /lib/udev/rules.d/65-libwacom.rules line 22 change

Code:

ENV{ID_INPUT_JOYSTICK}="0", ENV{ID_INPUT_JOYSTICK}=""

to this

Code:

ENV{ID_INPUT_JOYSTICK}=="0", ENV{ID_INPUT_JOYSTICK}=""

and reboot.

Everything now works as it should, at least on my end.

RadicalDreamer · 06-28-2020, 03:34 PM

Quote:

Originally Posted by Pixxt

In /lib/udev/rules.d/65-libwacom.rules line 22 change

Code:

ENV{ID_INPUT_JOYSTICK}="0", ENV{ID_INPUT_JOYSTICK}=""

to this

Code:

ENV{ID_INPUT_JOYSTICK}=="0", ENV{ID_INPUT_JOYSTICK}=""

and reboot.

Everything now works as it should, at least on my end.

Yes that worked!

RadicalDreamer · 06-28-2020, 07:13 PM

Thanks for the libwacom update! I'm marking this as solved.