oversteer T128 not showing up

Hi I am using the driver that most people recommend for the t128 and trying to use oversteer to see if it showing up but I do not see it up here it says no device found am I doing something wrong

Apr 01 '25 14:04 charlesmckee47

For compatibility reasons, Oversteer only supports a set of devices listed in the README. You might have everything correctly setup but your wheel isn't in the list.

Apr 01 '25 14:04 berarma

Please, can you post the USB vendor/product id displayed with the command lsusb?

Have you installed hid-tmff2?

I'm guessing that wheel can have more than one id and the driver might change it.

Apr 05 '25 07:04 berarma

Here it is (sorry for the late reply ) I believe I have hid tmff 2 install properly but I'm not 100% sure I don't know how to tell I am a Linux noob I just wanted if I could figure it out and get rid of fucking windows as I'm tired of their bloated operating system Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0aa7 Intel Corp. Wireless-AC 3168 Bluetooth Bus 001 Device 003: ID 048d:8297 Integrated Technology Express, Inc. IT8297 RGB LED Controller Bus 001 Device 004: ID 044f:b69c ThrustMaster, Inc. Thrustmaster T128X GIP Racing Wheel Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 05e3:0764 Genesys Logic, Inc. USB Storage

Jul 02 '25 04:07 charlesmckee47

I don't know if this will matter but I have Linux mint as the operating system

Jul 02 '25 04:07 charlesmckee47

Hi,

Just wanted to report I have a similar issue. I installed hid-tmff2 driver and oversteer last night. Initially, everything worked fine. Oversteer detected the wheel as 'Thrustmaster Advanced Racer' and it worked in all games and played until 2AM. However, in the morning when I started my PC, Oversteer says no devices available. Now in CLI, the wheel shows as T128X not the previous 'Advanced Racer'

OS Linux Mint

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0b05:1a52 ASUSTek Computer, Inc. USB Audio Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 005: ID 046d:0825 Logitech, Inc. Webcam C270 Bus 001 Device 006: ID 145f:0317 Trust Trust Deskset Bus 001 Device 007: ID 046d:c246 Logitech, Inc. Gaming Mouse G300 Bus 001 Device 008: ID 044f:b69c ThrustMaster, Inc. Thrustmaster T128X GIP Racing Wheel Bus 001 Device 009: ID 0489:e0e2 Foxconn / Hon Hai Wireless_Device Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 006 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Aug 23 '25 13:08 parallax78

@charlesmckee47, please, unsubscribe if you're not longer interested.

@parallax78 , it seems some TM models can have several different IDs depending on configuration. I'll see if I can gather a list of IDs and include it. But I don't know why yours changed overnight. It might be something with the drivers not loading correctly.

Aug 27 '25 15:08 berarma

Is there any way that it would be possible to get it added to oversteer

Aug 27 '25 16:08 charlesmckee47

here is the bus of my new linux being Debian Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 044f:b69c ThrustMaster, Inc. Thrustmaster T128X GIP Racing Wheel Bus 001 Device 003: ID 046d:c339 Logitech, Inc. PRO League of Legends Bus 001 Device 004: ID 046d:c539 Logitech, Inc. Lightspeed Receiver Bus 001 Device 005: ID 8087:0aa7 Intel Corp. Wireless-AC 3168 Bluetooth Bus 001 Device 006: ID 048d:8297 Integrated Technology Express, Inc. IT8297 RGB LED Controller Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Aug 27 '25 16:08 charlesmckee47

I'll add it later but that doesn't mean inputs will be recognized correctly.

Aug 27 '25 17:08 berarma

If you could that would be great because I managed to get the driver that you've already added support for a few other steering wheels with to load and work like the game is recognizing it

Sep 10 '25 23:09 charlesmckee47

Hi @charlesmckee47, I have the same issue as you had. What drivers did you install?

Sep 30 '25 18:09 GrimaldiWilliam

Hi @charlesmckee47, I have the same issue as you had. What drivers did you install?

https://github.com/Kimplul/hid-tmff2 this is the driver I use though overster technically doesn't support it so it will see it

Sep 30 '25 18:09 charlesmckee47

Damn, they are the same driver that i've installed. Maybe it's because I'm on Fedora/KDE and not on Linux Mint?

Sep 30 '25 19:09 GrimaldiWilliam

It now the divver at this point its the app

Sep 30 '25 20:09 charlesmckee47

I had the same problem , and found this to be the real issue: The solution of blacklisting the xpad-driver worked for me.

Oct 05 '25 16:10 jarlrasm

I had the same problem , and found this to be the real issue: The solution of blacklisting the xpad-driver worked for me.

Thank you @jarlrasm this worked perfectly! I needed another reboot but, after this, it worked

Oct 08 '25 16:10 GrimaldiWilliam

I had the same problem , and found this to be the real issue: The solution of blacklisting the xpad-driver worked for me.

That works to get the steering wheel working but then it kills all my Xbox controllers via USB

Oct 08 '25 20:10 charlesmckee47

This problem it easy to solve if you don't need wheel and controller together: create a .sh that remove the file when you connect the controller and create the file when the wheel is connected. It isn't the perfect solution but it works til they solve the bug

Oct 09 '25 09:10 GrimaldiWilliam

This problem it easy to solve if you don't need wheel and controller together: create a .sh that remove the file when you connect the controller and create the file when the wheel is connected. It isn't the perfect solution but it works til they solve the bug

That might be easy for you but I'm not a coder pretty much half the stuff I get is either from online or it's super basic to the point I can actually type it out

Oct 09 '25 15:10 charlesmckee47

This problem it easy to solve if you don't need wheel and controller together: create a .sh that remove the file when you connect the controller and create the file when the wheel is connected. It isn't the perfect solution but it works til they solve the bug

That might be easy for you but I'm not a coder pretty much half the stuff I get is either from online or it's super basic to the point I can actually type it out

Ah sorry, i created the code for file.sh for you:

Copy this code in a text file named as you want but the file extension must be .sh (for example blacklist-xpad.sh)

if grep -q "^b" /etc/modprobe.d/blacklist-xpad.conf; then
    sudo sed -i "s/blacklist xpad/#blacklist xpad/" /etc/modprobe.d/blacklist-xpad.conf
    echo "Xpad enable, wheel will not works"
elif grep -q "^#b" /etc/modprobe.d/blacklist-xpad.conf; then
    sudo sed -i "s/#blacklist xpad/blacklist xpad/" /etc/modprobe.d/blacklist-xpad.conf
    echo "Xpad disable, wheel will works"
else
  echo "blacklist-xpad.conf is wrong"
fi

Change the permission to execute the file. If it is named, blacklist-xpad.sh, do this in terminal: sudo chmod +x blacklist-xpad.sh
Now, when you double click the file it disable xpad if it enable, and enable xpad if it disable. Remember that you need to be root to execute this file. In terminal you can simply do this: sudo ./path/to/blacklist-xpad.sh

Oct 09 '25 18:10 GrimaldiWilliam

This problem it easy to solve if you don't need wheel and controller together: create a .sh that remove the file when you connect the controller and create the file when the wheel is connected. It isn't the perfect solution but it works til they solve the bug

That might be easy for you but I'm not a coder pretty much half the stuff I get is either from online or it's super basic to the point I can actually type it out

Ah sorry, i created the code for file.sh for you:

Copy this code in a text file named as you want but the file extension must be .sh (for example blacklist-xpad.sh)
if grep -q "^b" /etc/modprobe.d/blacklist-xpad.conf; then
    sudo sed -i "s/blacklist xpad/#blacklist xpad/" /etc/modprobe.d/blacklist-xpad.conf
    echo "Xpad enable, wheel will not works"
elif grep -q "^#b" /etc/modprobe.d/blacklist-xpad.conf; then
    sudo sed -i "s/#blacklist xpad/blacklist xpad/" /etc/modprobe.d/blacklist-xpad.conf
    echo "Xpad disable, wheel will works"
else
  echo "blacklist-xpad.conf is wrong"
fi
Change the permission to execute the file. If it is named, blacklist-xpad.sh, do this in terminal: sudo chmod +x blacklist-xpad.sh

Now, when you double click the file it disable xpad if it enable, and enable xpad if it disable. Remember that you need to be root to execute this file. In terminal you can simply do this: sudo ./path/to/blacklist-xpad.sh

running as root and its not working

Oct 14 '25 22:10 charlesmckee47