Madcatz TE/SE PS3 pc incompatibility is not a hardware issue. They work on Linux

So like many others my Madcatz SE fight stick doesn’t work on my windows PC. People were saying it was a chipset issue. Many people bought PCI usb ports with compatible chipsets to get them to work. To my surprise when I tried the stick on a Kubuntu (modified version of Ubuntu, a linux distribution) it worked right out the gate! No driver install was needed to get it recognized. So the whole chipset, usb 1.0 story people have been talking about is nonsense.

So the question is, is there anything that can be done now that we know it’s not a hardware problem?

Are you running Intel chipset? If so, you completely missed the boat…

We can’t exactly conclude anything until you give the exact specifications of the USB port used.

The hardware issue is was observed to be because the 1st generation MadCatz PS3 PCB for the TE/SE (everything before the TE-S which had the 2nd gen PCB) was designed to run on the UHCI USB 1.1 interface and not the more common OHCI, which is why people were recommending getting a UHCI PCI USB card. Unless you can show that a 1st generation PS3 PCB is running on Kubuntu on an OHCI USB port, you haven’t disproven anything.

EDIT: This might be due to the port being a USB 3 port which uses xHCI which is supposedly compatible with both UHCI and OHCI, but that still doesn’t get over the fact that for USB 1.1 it still is a hardware issue since the host controller interface is on the board.

I’m using a haswell pentium.

Some of the USB ports show up as EHCI and others are just named Generic USB hub in device manager. I also have 2 USB3.0 ports but none of my PC’s ports work with the stick in Windows 7,only in Kubuntu. Is there a way to get a more detailed view of what type of USB ports my computer has?

Another thing is what does the stick appear as to Windows, 1st gen PS3 PCBs (the ones that don’t work) appear as “PC USB Wired Stick 8838”.

Slightly related question.

Was this issue resolved in the current generation of sticks (Pro/KE) ? Or do they also not function with some Intel powered computers?

Read my previous posts.

Oh, sorry about that. I missed it on the first read-through.

Thanks!

It shows as ‘PC USB Wired Stick 8818’ (8818 instead of 8838 because it’s a SE stick) in windows, on Kubuntu it shows under the same name under the ‘system settings -> input devices, joystick’ section. In the terminal using lsusb it shows as ‘8818 Mad Catz, Inc. Street Fighter IV Arcade FightStick (PS3)’.

Another thing to note. On my old 775 socket system (don’t have it anymore) the stick worked fine under windows 7.

Yeah, see, that’s why YOU had no issues. People using Nvidia chipsets on the other hand…

Then why doesn’t it work in windows?

Drivers.

Also the issue with older Mad Catz SE and the TE round 1 and Round 1 was they used UHCI protocols, which are Intel proprietor USB protocols.
Later sticks switched to OHCI.

AMD, nVdida and some other motherboards lack the UHCI protocols which are hard written in the USB controller chip on the motherboard.
Ether you have a UCHI compliant USB controller on your motherboard or I call Shenanigans on this whole thread (as either there a software workaround you are not telling us or you are a complete twit and have no idea what is in your PC).

Well, this is weird. Thanks to your post I decided to look for UHCI controller drivers. Found this: http://batcmd.com/windows/7/services/usbuhci/. Ran the bat file and rebooted. And the stick worked in 1 specific port! Reconnected the stick in the same port to make sure it worked right and it didn’t work anymore. I’ve had this same problem on an Android TV HDMI device. The stick worked once (after spamming buttons like a madman) and never again after that. Now I’m not even sure if the bat file even did anything. In kubuntu the stick works 100% of the time so I don’t think the stick or the usb cable are faulty. What the hell is wrong here? Oh, and trust me, I’m not making this up.

EHCI (USB 2.0) and xHCI (USB 3.0) should recognize both UCHI and OHCI. So there’s most likely an issue with Windows that isn’t an issue with Linux.

You could install a zero delay usb encoder, $10 and about as easy as it gets.

But that’s not the point here. We’re trying to see if there is a software workaround to get the 1st generation MadCatz PS3 PCB to work on USB 3.0 (xHCI) since that doesn’t use separate OHCI/UHCI controllers for USB 1.0.

Microsoft?

I get that, I just wanted the OP to be aware that there’s another inexpensive option if he hits a wall here.

Hey, did anyone possibly get further with this? I can confirm that my PS3 Mad Catz TE-S stick that does not normally work with Windows works fine when I use it on jstest-gtk on Linux Mint 17. My mobo is a H87M Pro4 (Intel chipset), and the stick works fine in Linux connected in the USB3.0 port. I’ve tried disabling Enhanced Power Management and USB Selective Suspend in Windows, but none of those seemed to work. I looked into upgrading/reinstalling the USB Controller Host Drivers, but apparently Windows 8.1 uses its own universal drivers instead of manufacturer-specific drivers. I’ve also tried the link here: http://batcmd.com/windows/7/services/usbuhci/, except I used the Windows 8 batch file instead of the Windows 7 batch file, but that did not seem to work for me.

I’m mostly curious at this point. I have a perfectly working 360 stick that I use with the PC that I’m happy with, but would be thrilled if anyone somehow managed to find out more about this.

Wait a moment, before you hijack this thread…

The PS3 Mad Catz TE-S does work with Windows Xp, Win 7, Win 8, Win 8.1 and win 10 tech preview. It is the PS3 versions Mad Catz Round 1 and Round 2 TE (SF IV, MvC, Blazblue, Comic Com and Femme Fatile) and the SE which will not work on most non-Intel motherboards, a work around is installing a PCI USB card that supports UHCI.

"apparently Windows 8.1 uses its own universal drivers instead of manufacturer-specific drivers"
Not completely true, then again most PS3 wired controllers are HOD class devices and their are no manufacturer-specific drivers
Also USB 3.0 is natively supported in Win 8 on-wards, 3.0 is not supported natively on Win 7 and required a specific manufacturer driver which may or may not work.

Also the link you provided is partially incorrect, since Windows Vista Drivers do not run on the kernel level (they run now on the application level) and neither would the USB Universal Host Controller Miniport Driver.
Last OS that the USB driver ran on the kernel level is XP.