Saitek

Saitek copied to clipboard

Hey, I'm using Manjaro with XFCE (installed from manjaro-architect) with R.A.T 3 mouse and everytime on every boot the script starts working only after typing sudo udevadm control --reload and sudo udevadm trigger. From the README I understood that those commands should be a one-time operation, but I did not find any way to avoid executing them on every boot (including making a systemd service and shell script to be launched).

This is the case on at least 3 kernels and about 10-15 versions of Manjaro.

More system info: CPU: i7-6700k GPU: Gigabyte GeForce GTX 1060 6GB RAM: 8GB Patriot Viper DDR4 3000MHz MoBo: ASRock Fatal1ty Z170 Gaming K4 Keyboard: QPAD MK-50 OS: Dualboot Manjaro+Windows (on 2 separate drives) (please don't kill me)

If you need any more information please let me know.

Thanks in advance!

Open a terminal and type:

vdir /etc/udev/rules.d/90-ratctl.rules

Maybe is related to the owner (must be root and not your user name). Change it, if is necessary.

If you want run the script on boot, is not necessary create a bash script. Just go to System > Preferences > Startup applications. Add. Then fill this fields (Example):

Name: ratctl Command: python3 /path/to/ratctl.py Comment: Tool for configure Mad Catz R.A.T 3 under GNU/Linux.

Tuxkernel...

Well, that is... strange, to say the least. Those commands are only necessary to avoid rebooting the first time (or maybe even just unplugging & re-plugging the mouse), they shouldn't even be necessary in the first place.

could you paste the output of ls -l /etc/udev.d/ ? Maybe you put them in the wrong place, or with the wrong permissions? Though then it shouldn't work at all :thinking:

Maybe just maybe that directory isn't mounted at boot when those rules are checked. Or maybe they aren't present in the initramfs and are not executed later for some reason? I would need more info on this one, though I am probably not the best person for providing an answer.

Try to first have a look at the udev log. If really needed, you could try to enable debug logging, but I am not sure that will be easy to read, nor that it will be helpful.

Exactly @MayeulC , that's very strange. @czarnobylu try a new reinstallation, checking paths and upload your outputs. Tell us if was successful.