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

Wii U Gamecube Adapter not recognized on reboot #13039

Open
mad4gith opened this issue Dec 3, 2024 · 2 comments
Open

Wii U Gamecube Adapter not recognized on reboot #13039

mad4gith opened this issue Dec 3, 2024 · 2 comments

Comments

@mad4gith
Copy link

mad4gith commented Dec 3, 2024

Batocera build version

40 2024/08/01 01:28

Your architecture

x86_64

Your Graphic Processor Unit(s) (GPU)

Integrated AMD Vega Graphic card. Ryzen 5 PRO 2400GE

Issue description

Wii U Adapter is not recognized after reboot.
Unplug and plug it again let it to be recognized again.

Detailed reproduction steps

I've installed Batocera extracting the img and flashing it into an SSD connected to mi mini PC via USB to SATA adapter.
I've installed the CRT official script.
I've plugged the Wii U adapter into the USB port and was able to use it.
I rebooted Batocera and the adapter was not recognized.
Unplug the adapter from USB and plug it again (same port) let it to be recognized and work again.

Details of any attempts to fix this yourself

In the version 39 I wrote a script (custom.sh) that execute udevadm trigger afer ES loading, because this seems to solve the issue.
In version 40 this is not working anymore.
udevadm is just restarting ES, but the adapter is still not recognized.
After reboot lsusb is showing the adapter, but evtest is not.
image
image
If I unplug and plug again (the USB plug, leaving the GC pad inserted in port 1 of the Adapter) evtest is showing up the adapter:
image

Details of any modifications you have made to Batocera.

Installed the CRT official script.
Modified batocera-boot.conf for sharedevice=DEVICES

Logs and data

batocera-support-20241203204150.tar.gz

@DubaiShark
Copy link

DubaiShark commented Dec 26, 2024

Can you check here if that will work for you?

That’s what I fear. It’s a configuration handled entirely by Dolphin, yet the way Batocera assigns other controllers to Dolphin is by utilising its controller profiles. So if you’re using an ordinary GameCube for Wii U adapter, this gets bypassed.

It might be possible to activate passthrough in a similar fashion to Bluetooth passthrough with udev rules: https://wiki.batocera.org/systems:wii#using_bluetooth_passthrough, https://wiki.dolphin-emu.org/index.php?title=How_to_use_the_Official_GameCube_Controller_Adapter_for_Wii_U_in_Dolphin#Linux and finally https://wiki.batocera.org/udev_rules

Taken from this page

https://forum.batocera.org/d/6509-official-gamecube-wiiu-adapter/3

@mad4gith
Copy link
Author

mad4gith commented Jan 8, 2025

Thank you very much.

I write down the process in order to help other people that could search for this issue.

  1. Create file 51-gcadapter.rules in /userdata/system/udev/rules.d/
  2. Open that file and paste the following into it:

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="057e", ATTRS{idProduct}=="0337", MODE="0666"

  1. Restart PC

(Batocera v40)

(source in the link reported in the last comment)

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