Playstation 3 joypad issues

[danboid]

I have a few clone PS3 USB joypads which work fine with no config with retroarch under Linux but I've not been able to get any of them working with Haiku's port of retroarch. When I have one of them plugged in the retroarch menu selection scrolls up non-stop. Under Linux, I can navigate the retroarch menus fine using the d-pad with the same joypad.

hrev55742 amd64

[danboid]

Didn't Haiku used to have a tool to test USB joysticks and joypads? I can't see any such tool in recent versions.

[augiedoggie]

Replying to danboid:

Didn't Haiku used to have a tool to test USB joysticks and joypads? I can't see any such tool in recent versions.

There is a ​test app but it's not included with Haiku. You'll have to build it yourself.

[diver]

Do you have an USB2 port?

[danboid]

I thought I did but it seems not. When I connect the pad into one of the black USB ports, I still see XHCI errors in syslog. I went into the BIOS and tried disabling XHCI mode but that stops USB working entirely. I'll have to reset the CMOS now to get it back on its feet.

The BIOS says it only has a XHCI controller.

[danboid]

When I say it stops USB working, I can't use my keyboard under GRUB, Ubuntu or Haiku when I disable XHCI mode.

[waddlesplash]

Please test under a recent nightly and see if there are any differences.

[danboid]

Will do when I can install Haiku again!

https://dev.haiku-os.org/ticket/17673

[danboid]

I've got a few different PS3 clone pads. I tried 2 of them under the latest nightly. One seemed to be recognised in syslog OK but it didn't work properly under MAME (it seems to be sending input continuously, even when I'm not pushing a button) whilst the other PS3 clone pad didn't work at all.

[danboid]

syslog from hrev55971

[waddlesplash]

This ticket is about problems under XHCI but the attached syslog has UHCI errors, which are a quite different problem altogether.

[danboid]

The machine I was using when I originally filed this bug has died.

Are any USB gamepads or joysticks known to work under Haiku with any type of USB controller?

[waddlesplash]

Yes.

Do you have any machines with USB3 to retest with under a recent nightly, especially after hrev56123?

[danboid]

Hi Waddlesplash!

Yes, I've now got a new (old) Haiku box with a couple of USB 3.0 ports.

I have tested two of my clone PS3 pads (both of which work fine under Ubuntu and on my PS3) under 56127. The red one seems like its close to working because it does respond to input when I configure it under mame but the configured inputs aren't correct and I cannot navigate the mame menus using the pad after attempting to configure it.

I have attached a screenshot of the MAME joystick/pad configuration menu after attempting to configure UP, DOWN, LEFT, RIGHT and the 4 main buttons using the red clone PS3 pad. You can see that each one seems to have detected multiple inputs but I only had one USB joypad connected at the time. My other PS3 clone pad, the one with the labelled PS3 button in the middle, doesn't work at all in the MAME joypad config menu.

I've also noticed a couple of issues with MAMEs video output. If I start MAME from the tracker menu, it starts windowed but if I start it from the terminal it starts full screen. Is this by design?

Also, I'm using the failsafe video driver. The first time that I start mame from the terminal after booting, mame opens at 1080 successfully. After quitting mame and loading it again from the terminal, Haiku fails to maintain the 1080 res and drops down to a lower res.

I may need to open a separate ticket for one of both of those mame display issues?

[danboid]

syslog from hrev56127

[danboid]

MAME input config menu attempt

[danboid]

My red PS3 clone pad that almost works under Haiku

[danboid]

My PS3 clone pad that doesn't work at all under Haiku currently

[danboid]

These latest test results / syslog for 56127 were conducted using one of the USB 3.0 ports.

[danboid]

The Haiku desktop (sometimes) fails to redraw itself correctly/fully after quitting out of mame so I have to reboot (or restart tracker?) to get everything to redraw correctly.

[danboid]

Take 2 of h56127 syslog

[danboid]

I think my previous syslog got corrupted so I've uploaded another.

[waddlesplash]

KERN: usb_hid: found quirky device, using patched descriptor
KERN: usb_hid: found SIXAXIS controller, putting it in operational mode
KERN: usb_hid: using joystick in variable mode

That looks normal here.

[waddlesplash]

I don't see any other messages of note in the logs. It may well be that MAME or SDL is not handling the controller correctly, or that our HID driver is to blame, but at any rate this is not an XHCI problem.