Forcing hid_tmff_new to be used for the T248 wheel #127
Comments
|
sdl2-jstest does show the wheel and doing the test for it, moving the wheel does register the movement, but this is the only thing that does, every game both native Linux and in Steam/Proton doesn't register the wheel movements. Pedals are hit or miss on being picked up. |
|
That's pretty weird, thanks for the report.
No link, but regardless I'm not sure the best way forward would be to force bind devices to this driver.
Shows Anycase, as for actual troubleshooting, which distro are you using and what happens if you unplug all other joysticks? |
|
Ah, here's the link: https://unix.stackexchange.com/questions/134878/make-linux-load-specific-driver-for-given-device-realtek-nic It does talk about using the bind/unbind for the driver. I'm using Gentoo with a 6.11.9-gentoo-x86_64 kernel. Removing the other devices doesn't seem to help with getting the wheel motion recognized. I tried in SuperTuxKart. The pedals are recognized, but not the steering wheel itself. |
|
Thanks for the info. I've heard of some games being confused by multiple different joysticks sending input at the same time, so glad that doesn't seem to be the case. Oh, I just noticed, you're the one who opened up the issue about Gentoo last time, hello again! I still have the VM I set up last time, I'll have a go at booting it and see if I can replicate. I don't think I ever tried running any games in the VM so if this turns out to be a 'followup' of sorts, sorry, apparently didn't do my due diligence last time. |
|
Cool deal, let me know if you need any of the USE flag settings I have or any other debugging I can send over. |
|
I've tried some additional things without success, but figure they should be mentioned here. I use Hyprland in Wayland, so I was thinking that it might be part of the problem (it still might be at this point) so I've tried to run the games through gamescope to see if the wheel would be picked up any differently, but no change. https://github.com/ValveSoftware/gamescope The wheel in Farming Simulator 25 still gets registered as the "X" button, and the brake pedal gets registered as the "Y" button. The accelerate pedal seems to get registered as a pedal. No improvement in this case. The T248 wheel is the Xbox version, I'm always seeing those button names shown in the games. Also, I had tried the install the Windows drivers for the wheel via protontricks as was suggested in the README, that was before opening this issue and I didn't notice anything change. Here's the listing of the packages and versions of (relevant) Hyprland and Wayland things I have installed currently: |
|
Thanks for the extra info, I just got a desktop up and running, intending to try some games. SuperTuxKart has some issues compiling shaders, probably something weird with the VM but might still take a little while to sort out. I have the PS version of the T248, have you tried setting it to PC mode? I'd be a bit surprised if it did anything but at least it's something you can try while I'm trying to replicate. I might also have a look at Wayland at some point, I guess it could bring with it some input handling differences though I wouldn't necessarily hold my breath.
Missed this message the first time around but USE flags would be helpul, yes please. |
|
|
The wheel is set for PC mode. |
|
Alright, took a while to get VirGL set up but I can say I've at least partially replicated the issue. |
|
Hello again, been a while. No real progress so far, unfortunately. I noticed that SpeedDreams did actually pick up some input, but for whatever reason it's treating the axes as buttons and effectively only reacting to when the wheel is turned all the way to the left or the right. I'm a bit stumped as to why, since SpeedDreams uses SDL, but neither I might look into if maybe SDL is initialized somehow differently between |
|
Slight update, SpeedDreams started working after I deleted its config directory, |
|
Glad to hear that you're able to replicate what I was experiencing. It is definitely weird that low-level utils will see wheel as a range whereas all the games themselves will see it as mere binary buttons. I'll update to the latest 6.12 kernel this weekend and see how that works out for reference. |
|
I didn't get around to testing this last week, but I was able to tonight. Using the latest commit, 11cca6d as of right now, and a 6.12.6 kernel from the gentoo-sources "package" I am able to get the wheel working in 'Super Tux Kart' and 'American Truck Simulator', both native Linux games. In 'American Truck Simulator' I got the wheel to register with the game after turning the wheel all way in one direction until it reached the end of the wheel's mechanical limitation. No amount of lesser turns in either direction got it to register. Once that was seen, then the wheel is super sensitive in the game to the slightest movements. (IIRC, I did the same procedure in Super Tux Kart and got it to register, but the sensitivity in game is very low and I don't see a way of changing it in game.) On the Proton side: Farming Simulator 25 is still a no-go. The wheel will only register for turning to the right, but not the left. Even the pedals act up when they are applied. IIRC, I did install the Thrustmaster drivers in Proton via protontricks previously. Also to note, I'm not using gamescope anymore for the Windows games since Wayland support in Proton has gotten better. (I've set Steam to use the new "Proton Hotfix" branch for all my games now.) Definitely making progress and getting some good wins in. Merry Christmas and Happy Yule! |
|
For Farming Simulator 25, I did try adding |
I'm having a problem where the T248 wheel is not acting like it's using the correct kernel driver. It shows it being picked up in dmesg but lsmod is not showing it's used. lshw is showing the usbhid driver being used. According to this StackExchange post, there is a way of forcing a PCI device to use a specific driver, but I'm not seeing anything in the corresponding /sys/bus/usb/drivers that looks like kernel module.
Here's my kernel seeing the device and loading the module:
This is lshw showing the driver as usbhid:
Listing of /sys/bus/usb/drivers:
The text was updated successfully, but these errors were encountered: