Hello. This is my first post here but I've been using Linux pretty consistently for 20 years now. Wasn't sure where to turn on this one. As far as I can tell, I'm looking for udev help.

I've got a fresh install of Linux Mint 20.1 (Xfce). It's going to be kind of half-ass arcade cabinet set-up. I've got some nice fightsticks that were made for the Wii, using its "classic controller" port. A company called Mayflash makes adapters to interface 2 of these controllers to PC (USB).

I have Mayflash's PC045 (wired) and PC047 (wireless). The wired one works for the first controller only (the second oddly registers directional input as the first controller while the buttons are totally ignored) and the wireless one works fine. Waste of batteries and introduces a bit of input lag though. I only got that one because for a time the PC045 gave a blue screen of death in Windows. That was fixed at some point and these days the PC045 works perfectly in Windows, plug and play.

I came across instructions on getting this company's Gamecube adapter to be recognized by udev and tried those out with the PC045's numbers I found with dmesg, but that didn't do anything. I guess the adapter had no trouble being recognized anyhow... udev just doesn't seem to realize it's for 2 controllers and not 1.

The PC045 wasn't on the market long before being replaced by another Mayflash adapter with the same functionality, the PC052. I'm thinking getting that for $20 might sort this out. But that's no fun (and no guarantee). I'm curious what the heck the difference might be as far as Linux is concerned. Is there some way I could tell udev to treat the PC045 as a PC052? Are these things "known" in udev or is this whole thing (and the past Windows crashes) caused by the PC045 trying to identify itself in some wacky, obscure way?

For what it's worth, the game frontend RetroArch lets you choose between input drivers (udev, linuxraw, parport, sdl2, and hid). Changing from udev didn't seem to affect anything.

Cheers!

To fix or diagnose something like this, you need to get exact. My not very precise understanding (in no particular order) is

1. You insert something
2. It's interrogated and results are posted in dmesg
3. Module & firmware are loaded as required
4. A udev device is assigned, allowing you access
5. programs can deal with it.

Post the output of dmesg as your device is connected.

1 members found this post helpful.

Thank you. Dunno what to make of the output. Any insights much appreciated.

dmesg | grep Mayflash
[ 2.332529] usb 3-2.4: Product: Mayflash Wii Classic Controller
[ 2.332531] usb 3-2.4: Manufacturer: Mayflash.,Ltd
[ 2.343313] input: Mayflash.,Ltd Mayflash Wii Classic Controller as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2.4/3-2.4:1.0/0003:0925:03E8.0008/input/input20
[ 2.343432] hid-generic 0003:0925:03E8.0008: input,hidraw5: USB HID v1.01 Joystick [Mayflash.,Ltd Mayflash Wii Classic Controller] on usb-0000:00:14.0-2.4/input0
[99135.923189] usb 3-2.4: Product: Mayflash Wii Classic Controller
[99135.923190] usb 3-2.4: Manufacturer: Mayflash.,Ltd
[99135.935563] input: Mayflash.,Ltd Mayflash Wii Classic Controller as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2.4/3-2.4:1.0/0003:0925:03E8.000B/input/input31
[99135.935759] hid-generic 0003:0925:03E8.000B: input,hidraw5: USB HID v1.01 Joystick [Mayflash.,Ltd Mayflash Wii Classic Controller] on usb-0000:00:14.0-2.4/input0
[100300.203560] usb 3-2.4: Product: Mayflash Wii Classic Controller
[100300.203561] usb 3-2.4: Manufacturer: Mayflash.,Ltd
[100300.210421] input: Mayflash.,Ltd Mayflash Wii Classic Controller as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2.4/3-2.4:1.0/0003:0925:03E8.000C/input/input32
[100300.210616] hid-generic 0003:0925:03E8.000C: input,hidraw5: USB HID v1.01 Joystick [Mayflash.,Ltd Mayflash Wii Classic Controller] on usb-0000:00:14.0-2.4/input0
[101175.461903] usb 3-2.4: Product: Mayflash Wii Classic Controller
[101175.461905] usb 3-2.4: Manufacturer: Mayflash.,Ltd
[101175.474238] input: Mayflash.,Ltd Mayflash Wii Classic Controller as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2.4/3-2.4:1.0/0003:0925:03E8.000F/input/input35
[101175.474584] hid-generic 0003:0925:03E8.000F: input,hidraw5: USB HID v1.01 Joystick [Mayflash.,Ltd Mayflash Wii Classic Controller] on usb-0000:00:14.0-2.4/input0
[102235.547796] usb 3-2.4: Product: Mayflash Wii Classic Controller
[102235.547798] usb 3-2.4: Manufacturer: Mayflash.,Ltd
[102235.560522] input: Mayflash.,Ltd Mayflash Wii Classic Controller as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2.4/3-2.4:1.0/0003:0925:03E8.0010/input/input36
[102235.617619] hid-generic 0003:0925:03E8.0010: input,hidraw5: USB HID v1.01 Joystick [Mayflash.,Ltd Mayflash Wii Classic Controller] on usb-0000:00:14.0-2.4/input0
[102752.920216] usb 3-2.4: Product: Mayflash Wii Classic Controller
[102752.920218] usb 3-2.4: Manufacturer: Mayflash.,Ltd
[102752.931132] input: Mayflash.,Ltd Mayflash Wii Classic Controller as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2.4/3-2.4:1.0/0003:0925:03E8.0011/input/input37
[102752.931438] hid-generic 0003:0925:03E8.0011: input,hidraw5: USB HID v1.01 Joystick [Mayflash.,Ltd Mayflash Wii Classic Controller] on usb-0000:00:14.0-2.4/input0

You need to give a little more information, and a much smaller clip from dmesg. That post was from time 2 to time 102752 of dmesg and only the lines that had Mayflash in them.

I suggest you remove the controller, wait a time and look at dmesg so you can see the ending time on what is there now. Then plug in the controller and give us everything new that results from dmesg as the controller is configured. This limits the time span as well as providing all the dmesg detail for that time span.

Just as a suggestion as well. Please enclose everything you post from terminal output within code tags so it is easier to read. As you are typing your post, the "go advanced" button on the bottom will give you more options on the top bar. Then the "#" on the top bar will give the code tags and simply paste your input between the provided tags.

1 members found this post helpful.

Thanks, gotcha. Here is that!

I did a quick search for "linux mayflash wii controller module" and got loads of relevant hits. I suggest you have a good read as there appears to be helpful advice.

1 members found this post helpful.

Thanks, your search terms led me to a thread on the Batocera forums about the same adapter. It seems it was the same issue until the guy recompiled kernel module hid-sjoy to tell it to treat that specific adapter as 2 inputs and not 1. Per my dmesg output, I'm guessing I need to do that for hid-generic? I'll look up guidance on how to do this in Ubuntu. I don't seem to have hid-sjoy in play at all.

(the stuff about hid-quirks on there won't apply for these sticks)

Cheers

Back to add solution I found via here. Just had to add the following to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub:

usbhid.quirks=0×0925:0×03e8:0×040

Apparently it’s a typical Linux “quirk” when two controllers are using one USB.