Joystick issues - obscure Wii adapter
by barnw0l from LinuxQuestions.org on (#5F0Y5)
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!
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!