You are not logged in.

#1 2020-10-15 19:45:37

fileserverpls
Member
Registered: 2018-10-21
Posts: 15

Unable to get data from game cube controller using Piranha adapter

Issue

I bought a Piranha GameCube Controller Adapter today because I want to play some game cube games in Dolphin Emulator. I have an old original game cube controller connected into it and the adapter connected to USB.

What I have tried

I have tried to restart and re plug every single cord in different USB inputs, etc.
I have switched it to "PC" and I have tried to switch it to Switch adapter as well but that does not change anything.
I have downloaded jstest and jstest-gtk in order to test the controller and I believe it identifies /dev/input/js0 but no data shows in the programs.
I have added myself to input
I have ran sudo fftest /dev/input/by-id/usb-*event-joystick
I have modprobe'd usbhid and joydev
I have tried restarting, re-configuring, re-calibrating, etc. These things change nothing.
I have tried doing everything above running sudo as well

Edit:
I have Linux hardened on my system, and it keeps messing with modprobe (i.e I can't run virtualbox because it utilizes modprobe to install some things. Modprobe does not give out errors when I try to use it though)

Last edited by fileserverpls (2020-10-15 20:00:55)

Offline

#2 2020-10-16 08:37:47

fileserverpls
Member
Registered: 2018-10-21
Posts: 15

Re: Unable to get data from game cube controller using Piranha adapter

I have now tried to follow dolphin-emu.org where they say I should add the following to /etc/udev/rules.d/51-gcadapter.rules and then execute "sudo udevadm control --reload-rules"


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

This did not change anything and it seems as if it is for another device and it obviously did not work for me. I have libusb if anyone was wondering that. A restart does not change anything either.

Last edited by fileserverpls (2020-10-16 08:39:18)

Offline

#3 2020-10-16 09:20:03

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 10,831

Re: Unable to get data from game cube controller using Piranha adapter

Can you reproduce on non hardened? It often has patches that make things like these more difficult by design and it's not really intended as a general purpose desktop kernel.

That said, inofficial knock offs often have weird quirks, FWIW my official Nintendo WiiU adapter works without issue.

Also when switched to Switch mode it should by default only work in dolphin and it's not expected to be generally usable on the rest of the system, it's not clear to me whether you've simply tried setting things up in Dolphin.

Also maybe post

lsusb
dmesg 

(... from both modes)

Last edited by V1del (2020-10-16 09:21:37)

Offline

#4 2020-10-16 11:24:22

fileserverpls
Member
Registered: 2018-10-21
Posts: 15

Re: Unable to get data from game cube controller using Piranha adapter

lsusb

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0079:1846 DragonRise Inc. GameCube Controller Adapter
Bus 001 Device 003: ID 046d:c051 Logitech, Inc. G3 (MX518) Optical Mouse
Bus 001 Device 002: ID 045e:0752 Microsoft Corp. Wired Keyboard 400
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

dmesg has hundredths of lines but these are the last, and it repeats basically the same thing over and over again.

[ 2050.468097] kauditd_printk_skb: 75 callbacks suppressed
[ 2050.468101] audit: type=1130 audit(1602847102.034:33568): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2050.472028] audit: type=1131 audit(1602847102.037:33569): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[ 2050.714291] audit: type=1130 audit(1602847102.277:33570): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2050.714371] audit: type=1131 audit(1602847102.277:33571): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2050.718069] audit: type=1130 audit(1602847102.284:33572): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2050.726402] audit: type=1131 audit(1602847102.291:33573): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[ 2050.964568] audit: type=1130 audit(1602847102.527:33574): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2050.964581] audit: type=1131 audit(1602847102.527:33575): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2050.968528] audit: type=1130 audit(1602847102.534:33576): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2050.982894] audit: type=1131 audit(1602847102.547:33577): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[ 2055.472209] kauditd_printk_skb: 76 callbacks suppressed
[ 2055.472210] audit: type=1131 audit(1602847107.037:33654): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[ 2055.714619] audit: type=1130 audit(1602847107.281:33655): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2055.714631] audit: type=1131 audit(1602847107.281:33656): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2055.718090] audit: type=1130 audit(1602847107.284:33657): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2055.726630] audit: type=1131 audit(1602847107.291:33658): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[ 2055.964419] audit: type=1130 audit(1602847107.527:33659): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2055.964676] audit: type=1131 audit(1602847107.531:33660): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2055.968425] audit: type=1130 audit(1602847107.534:33661): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2055.972055] audit: type=1131 audit(1602847107.537:33662): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[ 2056.061431] audit: type=1101 audit(1602847107.627:33663): pid=27600 uid=1000 auid=1000 ses=1 subj==unconfined msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="usrname" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 2056.276646] Lockdown: systemd-modules: unsigned module loading is restricted; see man kernel_lockdown.7
[ 2056.291640] Lockdown: systemd-modules: unsigned module loading is restricted; see man kernel_lockdown.7
[ 2056.302197] Lockdown: systemd-modules: unsigned module loading is restricted; see man kernel_lockdown.7
[ 2057.235018] Lockdown: systemd-modules: unsigned module loading is restricted; see man kernel_lockdown.7
[ 2057.246832] Lockdown: systemd-modules: unsigned module loading is restricted; see man kernel_lockdown.7
[ 2057.257071] Lockdown: systemd-modules: unsigned module loading is restricted; see man kernel_lockdown.7
[ 2057.770073] Lockdown: systemd-modules: unsigned module loading is restricted; see man kernel_lockdown.7
[ 2057.783886] Lockdown: systemd-modules: unsigned module loading is restricted; see man kernel_lockdown.7
[ 2057.794216] Lockdown: systemd-modules: unsigned module loading is restricted; see man kernel_lockdown.7
[ 2060.482822] kauditd_printk_skb: 88 callbacks suppressed
[ 2060.482827] audit: type=1131 audit(1602847112.047:33752): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[ 2060.714299] audit: type=1130 audit(1602847112.277:33753): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2060.714351] audit: type=1131 audit(1602847112.277:33754): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2060.718086] audit: type=1130 audit(1602847112.284:33755): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2060.722052] audit: type=1131 audit(1602847112.287:33756): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[ 2060.964359] audit: type=1130 audit(1602847112.527:33757): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2060.964473] audit: type=1131 audit(1602847112.531:33758): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2060.968222] audit: type=1130 audit(1602847112.534:33759): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2060.976423] audit: type=1131 audit(1602847112.541:33760): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[ 2061.214560] audit: type=1130 audit(1602847112.777:33761): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=red comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2062.276737] Lockdown: systemd-modules: unsigned module loading is restricted; see man kernel_lockdown.7
[ 2062.291712] Lockdown: systemd-modules: unsigned module loading is restricted; see man kernel_lockdown.7
[ 2062.302250] Lockdown: systemd-modules: unsigned module loading is restricted; see man kernel_lockdown.7

Offline

#5 2020-10-16 11:40:50

fileserverpls
Member
Registered: 2018-10-21
Posts: 15

Re: Unable to get data from game cube controller using Piranha adapter

I just noticed something! I opened dolphin-emu and press Calibrate on either sticks it does nothing for me but in the bottom right corner there is a "Options" tab and a box that says "Always Connected" and it is checked. Next to it is a button with three dots. If I press these three dots a menu opens up for the controller I have selected. Every button have the value 0 but when I move the C stick or the control stick the values of the attributes "Axis 0-, Axis 0+" etc changes, meaning it obviously detects the controller! Any ideas why the controller is detected in this weird off to the side menu but not detected in game, in any joystick configuration program or in the calibration of dolphin-emu?

Offline

#6 2020-10-16 12:11:51

fileserverpls
Member
Registered: 2018-10-21
Posts: 15

Re: Unable to get data from game cube controller using Piranha adapter

After installing xf86-input-joystick and hid-nintendo-dkms I can move the mouse pointer using the stick controller. However the only buttons that actually work is L and R and I am unable to have it connected and do anything because it constantly scrolls. There is nothing wrong with the controller and it works perfectly fine connected to an actual game cube. Any ideas on how to correctly map the keys and stop it from continuously scrolling left?

Offline

#7 2020-10-16 12:13:29

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 10,831

Re: Unable to get data from game cube controller using Piranha adapter

With the adapter in Switch mode you should simply be able to select the "Gamecube Adapter for Wii-U" control option and it should work if this thing passes it's information through properly.

The reason why this works there and not anywhere is that Dolphin has it's own driver for setting this up. And FWIW most of the tools you used to check might use outdated paths/devices that aren't  necessarily still populated. check with something like libinput debug-events whether it registers debug events (... that on the other hand I'd only expect to be visible in some shape if switched to the PC mode)

Edit: You need to config xorg to ignore the device for controlling the mousepointer, check the xorg log for the identified name and then add a configlet disabling it, e.g. I use the https://aur.archlinux.org/packages/wii-u-gc-adapter/ package for when I want generic controller support which includes

Section "InputClass"
        Identifier "Wii U GameCube Adapter Blacklist"
        MatchProduct "Wii U GameCube Adapter Port "
        Option "Ignore" "on"
EndSection

to ignore it for the xorg server

Last edited by V1del (2020-10-16 12:19:32)

Offline

#8 2020-10-16 16:42:49

fileserverpls
Member
Registered: 2018-10-21
Posts: 15

Re: Unable to get data from game cube controller using Piranha adapter

I deleted and undid everything I had done up to this point, restarted and opened dolphin-emu. Same result. Then I pressed the configuration of the mappings and actually configured the whole thing. Apparently it was mapped to a keyboard by default despite being a profile for Game Cube controller. This meant that it was probably working all along, it was just not configured to the controller actions but rather keyboard buttons LOL. It took a few seconds for the controller action to register but once it was registered it worked flawlessly! Thanks for your involvement and ideas smile

Offline

Board footer

Powered by FluxBB