Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting the wheel to work in steam #138

Open
Cimmerian-Iter opened this issue Jan 10, 2025 · 3 comments
Open

Getting the wheel to work in steam #138

Cimmerian-Iter opened this issue Jan 10, 2025 · 3 comments

Comments

@Cimmerian-Iter
Copy link

Hello, Now that the first step is done, I'll try getting the wheel to work correctly on my deck

[ 366.496818] usb 1-1.3: USB disconnect, device number 5
[ 369.266438] usb 1-1.3: new full-speed USB device number 6 using xhci_hcd
[ 369.372694] usb 1-1.3: New USB device found, idVendor=044f, idProduct=b65d, bcdDevice= 1.00
[ 369.372706] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 369.372708] usb 1-1.3: Product: Thrustmaster FFB Wheel
[ 369.372710] usb 1-1.3: Manufacturer: Thrustmaster
[ 369.457628] input: Thrustmaster Thrustmaster FFB Wheel as /devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-1/1-1.3/1-1.3:1.0/0003:044F:B65D.000E/input/input44
[ 369.457865] hid-thrustmaster 0003:044F:B65D.000E: input,hidraw2: USB HID v1.00 Gamepad [Thrustmaster Thrustmaster FFB Wheel] on usb-0000:04:00.3-1.3/input0
[ 369.477704] usbhid 1-1.3:1.0: Wheel with (model, attachment) = (0x2, 0x3) is a Thrustmaster T300RS (F1 attachment). attachment_found=1
[ 369.479783] usbhid 1-1.3:1.0: Success, the wheel should have been initialized!
[ 369.568937] usb 1-1.3: USB disconnect, device number 6
[ 370.286576] usb 1-1.3: new full-speed USB device number 7 using xhci_hcd
[ 370.412700] usb 1-1.3: New USB device found, idVendor=044f, idProduct=b66e, bcdDevice= 1.00
[ 370.412712] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 370.412718] usb 1-1.3: Product: Thrustmaster T300RS Racing wheel
[ 370.412723] usb 1-1.3: Manufacturer: Thrustmaster
[ 370.502197] input: Thrustmaster Thrustmaster T300RS Racing wheel as /devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-1/1-1.3/1-1.3:1.0/0003:044F:B66E.000F/input/input45
[ 370.502423] tmff2 0003:044F:B66E.000F: input,hidraw2: USB HID v1.11 Joystick [Thrustmaster Thrustmaster T300RS Racing wheel] on usb-0000:04:00.3-1.3/input0
[ 370.507712] tmff2 0003:044F:B66E.000F: force feedback for T300RS

T300 F1 addon is recognized, but in oversteer I have this message
image

So I can't change much settings.

fftest to see if it works, rumble effect work, the others doesn't but i guess it has to do with this
image

Installed windows driver in steam games but the wheel is simply not detected, not a single input. Using proton-ge, I checked other issue and it's either down to proton version and steam input.

/home/deck/.steam/steam/compatibilitytools.d/GE-Proton9-20/files/bin/wine control joy.cpl shows nothing

Finally tried speed dream. It detect input? but in game nothing moves, no steering no accelerator.

So there's something that prevents access to the wheel correctly? I did the udev rules. But i'm kinda clueless about why i'm not even having correct linux support before tackling windows support.

@Kimplul
Copy link
Owner

Kimplul commented Jan 10, 2025

Sounds very similar to #127, unfortunately I don't have a solution for it at the moment. There was also #132 which I at least initially thought might've been related, but I'm not sure.

@Cimmerian-Iter
Copy link
Author

                    *-usb:2
                         description: Human interface device
                         product: Thrustmaster Thrustmaster T300RS Racing wheel
                         vendor: Thrustmaster
                         physical id: 3
                         bus info: usb@1:1.3
                         logical name: input60
                         logical name: /dev/input/event14
                         logical name: /dev/input/js0
                         version: 1.00
                         capabilities: usb-2.00 usb
                         configuration: driver=usbhid maxpower=100mA speed=12Mbit/s
(deck@steamdeck build)$ ls -l /sys/bus/usb/drivers/
total 0
drwxr-xr-x 2 root root 0 Jan 11 11:03 cdc_acm
drwxr-xr-x 2 root root 0 Jan 11 11:03 cdc_ether
drwxr-xr-x 2 root root 0 Jan 10 21:57 hub
drwxr-xr-x 2 root root 0 Jan 11 11:03 r8152
drwxr-xr-x 2 root root 0 Jan 11 11:03 r8152-cfgselector
drwxr-xr-x 2 root root 0 Jan 11 11:03 r8153_ecm
drwxr-xr-x 2 root root 0 Jan 10 21:57 usb
drwxr-xr-x 2 root root 0 Jan 11 11:03 usbfs
drwxr-xr-x 2 root root 0 Jan 10 21:57 usbhid
drwxr-xr-x 2 root root 0 Jan 11 11:03 usbserial_generic

so it's a case of two driver for a single device and it doesn't pick tmff2 if i understand correctly? the other guy managed to get his T248 working on deck, so i will hope a new deck update comes out, wipe out my rootfs so that i can start clean

@Kimplul
Copy link
Owner

Kimplul commented Jan 11, 2025

so it's a case of two driver for a single device and it doesn't pick tmff2 if i understand correctly?

Not quite, the initial question was how to force hid-tmff2 to be used for the device, but as I pointed out a bit down the thread, this driver is being loaded properly but the input issue is in some other layer, but I don't quite know which or what the issue exactly is.

Please do report back if updating the deck fixes this issue for you, at least it'll be a bit more data to (hopefully) debug further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants