no controllers found after update

nik2208

@mitu on console it behaves exactly the same

mitu

@nik2208 said in no controllers found after update:

on console it behaves exactly the same

How about jstest ? Does it work without sudo ?

nik2208

@mitu trying to. How is SDL involved in gamepad recognition process? can any conflict on sdl cause gamepads not to be recognized?

nik2208

@mitu actually a new udev rule to access inputs devices as user has solved the issue.
Can't imagine what process could have changed such setting to make it suddenly stop working

mitu

@nik2208 said in no controllers found after update:

@mitu actually a new udev rule to access inputs devices as user has solved the issue.

Which rule ? Can you be more specific ? I'd like to understand how is related to a RetroPie/RaspiOS upgrade.

nik2208

@mitu said in no controllers found after update:

Which rule ?

nicola@raspberrypi:~ $ ls -la /etc/udev/rules.d/
totale 24
drwxr-xr-x 2 root root 4096  5 giu 17.59 .
drwxr-xr-x 4 root root 4096 25 mar 11.42 ..
-rw-r--r-- 1 root root 2095 15 mag 17.55 72-moltengamepad.rules
-rw-r--r-- 1 root root 1743 13 nov  2023 99-com.rules
-rw-r--r-- 1 root root   47  5 giu 17.56 99-gamepad.rules
-rw-r--r-- 1 root root   47  9 mag 21.34 99-input.rules

99-gamepad.rules is the rule I've added.

99-input.rules is

SUBSYSTEM=="input", GROUP="input", MODE="0660"

but actually seems not to do the job.

The new rule is
99-gamepad.rules

KERNEL=="js[0-9]*", MODE="0660", GROUP="input"

mitu

@nik2208 said in no controllers found after update:

99-gamepad.rules is the rule I've added.

Hm, I have only 99-input.rules and I have no issue with acces. In addition to that, /dev/input/jsX devices are not used by EmulationStatoin and SDL, the /dev/input/eventX inodes are used.

nik2208

@mitu also evtest started back working without sudo, before adding this new rule, evtest showed me the controller only in superuser mode

mitu

@nik2208 I don't see how the new rule would make evtest work, since it applies only to [/dev/input/]jsX devices, while evtest only looks at /dev/input/eventX nodes.

I don't think your issue is from upgrade, but from some other configuration/permissions you have applied.

nik2208

@mitu i really havent installed/applied things

@mitu said in no controllers found after update:

I don't see how the new rule would make evtest work

I'm not that keen on kernel device hierarchy, can it be that events kernel entry points rely on available inputs (which in case of the missing udev rule aren't available)?
What I am sure abt and can replicate it, is that without the rule evtest doenst show the gamepad as normal user, while it shows it as super user.

One more think I've noticed is my raspios keep asking me to update sdl and sdl-dev library which were not automatically updated by apt ugrade, and that for some reason the retropie installation start from source and compiles everything, which it didn't seem to happen the first time I've installed it (but I'm not sure abt that)

mitu

I'm not that keen on kernel device hierarchy, can it be that events kernel entry points rely on available inputs (which in case of the missing udev rule aren't available)?

It's the other way around - kernel input events are the lowest level, upon which higher level APIs are built (i.e. joystick or gamepad APIs).

What I am sure abt and can replicate it, is that without the rule evtest doenst show the gamepad as normal user, while it shows it as super user.

I cannot replicate it, but I'm not running the same configuration as yours (i.e. desktop environment and extra udev rules from MoltenGamepad).

One more think I've noticed is my raspios keep asking me to update sdl and sdl-dev library which were not automatically updated by apt ugrade, and that for some reason the retropie installation start from source and compiles everything, which it didn't seem to happen the first time I've installed it (but I'm not sure abt that)

That's ok and it's not a cause for your issue.