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

T300 RS Driver Issue #88

Closed
FelipeMelon opened this issue Apr 1, 2024 · 19 comments
Closed

T300 RS Driver Issue #88

FelipeMelon opened this issue Apr 1, 2024 · 19 comments

Comments

@FelipeMelon
Copy link

So, I tried updating the driver in windows virtual machine, however I ended up in my wheel being named Thrustmaster T300 RS bootloader and I don't know what to do now. I'd be grateful for any help.

@Kimplul
Copy link
Owner

Kimplul commented Apr 1, 2024

Pretty sure you just need to reattach the wheel to the Windows VM.

@FelipeMelon
Copy link
Author

So, I’ve tried it but I don’t think that the VM recognises that the usb is reattached it only works if I attach it before launching the VM

@Kimplul
Copy link
Owner

Kimplul commented Apr 1, 2024

Interesting. Last time I went through the update procedure the firmware updater waited until I reattached the wheel in its bootloader mode, and then it just finished normally. If you restarted the VM or the update procedure in the middle of this, I guess the installer might've gotten confused? Not sure. Anycase, there's a guide on Thrustmaster's site for what to do if you're stuck in the bootloader mode: https://ts.thrustmaster.com/download/accessories/Manuals/T300RS/T300RS_Bootloader_Method.pdf

@FelipeMelon
Copy link
Author

Alright, I’ll try that. Just in case, is there a way to reset the wheel to factory settings?

@Kimplul
Copy link
Owner

Kimplul commented Apr 1, 2024

As in resetting to the firmware version that the wheel came with in the box? No, not that I'm aware of. The Thrustmaster tools don't seem to have any way to select previous firmware versions.

@FelipeMelon
Copy link
Author

Ok, so it seems like windows VM doesn't recognise the bootloader as a usb device even after switching to different usb ports. It is however recognised on my linux system.

@Kimplul
Copy link
Owner

Kimplul commented Apr 1, 2024

Do you mean that you can't attach the bootloader device to the VM or that Windows/the update utility doesn't recognize the device?

@FelipeMelon
Copy link
Author

I was able to attach it to VM but windows itself didn't recognise it.

@Kimplul
Copy link
Owner

Kimplul commented Apr 1, 2024

Just to clarify, are you referring to the red text in step 7 of the pdf? The firmware update program is not showing anything? Or that the device doesn't show up in device manager under Windows?

Which virtual machine/frontend are you using, virt-manager? How are you attaching the USB device?

@FelipeMelon
Copy link
Author

FelipeMelon commented Apr 1, 2024

I am using virt-manager, I switched from Virtualbox and at least now I am getting an error message when I am trying to redirect usb device (the t300 bootloader) and it says:spice client error quark:Could not redirect USB Device [044f:b66c0] at 1-41: error resetting device LIBUSB_ERROR_NOT_FOUND (0) so I think that's the key problem.

Edit: All other USB devices are working like normal, I can attach them to windows without issues it's only the wheel.

@Kimplul
Copy link
Owner

Kimplul commented Apr 1, 2024

I am using virt-manager, I switched from Virtualbox and at least now I am getting an error message when I am trying to redirect usb device (the t300 bootloader) and it says:spice client error quark:Could not redirect USB Device [044f:b66c0] at 1-41: error resetting device LIBUSB_ERROR_NOT_FOUND (0) so I think that's the key problem.

Seems reasonable. I've personally used virt-manager so I know that it at least CAN work, but can't really say I've seen anything like that unfortunately. Googling around I can see some bug reports about something similar, but they've been patched so not entirely sure what this is about. Which distro and version of virt-manager/qemu are you using?

@FelipeMelon
Copy link
Author

I am using Linux Mint 21.2 Cinnamon, and virt-manager version is 4.0.0

@Kimplul
Copy link
Owner

Kimplul commented Apr 1, 2024

I seem to be running virt-manager 4.1.0 on Debian Testing, but I can try out Mint and see if I can replicate.

@FelipeMelon
Copy link
Author

Did you see any progress?

@Kimplul
Copy link
Owner

Kimplul commented Apr 1, 2024

Not yet, as I'm unfortunately not home right now, but will be tomorrow. Probably should've mentioned that, come to think of it.

@FelipeMelon
Copy link
Author

FelipeMelon commented Apr 1, 2024

Yeah that's no problem, I have no idea what to do anyway. Also, I updated mint cinammon to the newest version meaning 21.3

@FelipeMelon
Copy link
Author

I have solved the issue, by downloading Windows 10 on a separate drive and getting the firmware over there. No solution found for the VM problem though.

@Kimplul
Copy link
Owner

Kimplul commented Apr 2, 2024

Very pragmatic.

Unfortunately, I wasn't able to replicate, so really not sure what the VM issue might be. Could be worth opening a bug report for?

@FelipeMelon
Copy link
Author

I'll submit a bug-report relatively soon, I'm taking a break after troubleshooting for a whole day. I really hope it will help some ppl in the future. :)

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