Wheel not initialized properly on reboot

[Kimplul]

          @Kimplul strange. I spent a couple of hours debugging just now.

The wheel shows up in lsusb as 044f:b66e after reboot or cold boot and oversteer works, evtest works, fftest works. Except wine/proton which sees the wheel but does not detect input until after I replug the usb cable. I do see some difference between reboot and replug in the journalctl output, When replugging I see hid-thrustmaster doing some stuff, even though it is blacklisted (confirmed with modprobe --showconfig|grep blacklist). Weird, but the wheel works after replug.

Other stuff I tried: Uninstall steam => no change Add TAG+="seat" to udev rules => no change Add entire vendor class to udev rules => no change Call udevadm trigger after boot => no change Not blacklisting hid-thrustmaster => no change

So I suspect it is not udev related, also because my other controllers (Virpil) work just fine in the wine control panel after a reboot. Instead it looks like the wheel does not get initialized on boot in the same way it gets initialized when replugging after bootup. This then causes wine to not see the wheel as a wheel or something like that.

I have attached relevant journalctl output of boot and replug, maybe you can make something out of it.

reboot.txt replug.txt

Originally posted by @krims0n32 in https://github.com/Kimplul/hid-tmff2/issues/112#issuecomment-2277622615

I moved this to another issue as it seems to be unrelated to #112. Had a quick look at the logs provided and the report seems accurate, but I don't know what would be causing it yet.