DanielOgorchock / joycond

userspace daemon to combine joy-cons from the hid-nintendo kernel driver
GNU General Public License v3.0
373 stars 71 forks source link

Does not pair on Arch #83

Open FtK259 opened 3 years ago

FtK259 commented 3 years ago

I think I'm missing something here. I cannot pair the switch pro controller both on wired or Bluetooth mode. I'm using Manjaro Linux with 5.14.10-1-MANJARO kernel, so I think I do not need hid-nintendo-dkms, then I installed only the joycond-git package.

Bluetooth: I press the pair top bottom on the pro controller, it connects as "Pro Controller (/dev/input/js0)" and the LEDs still blinking (I think it is what is it is supposed to do). However, both L + R and [+] + [-] button combination do nothing. The LEDs still blinking and nothing changes on the Linux input devices. I can even play dinput based games, but the LEDs still blinking and I cannot play xinput based games (including Steam itself and big picture) because I cannot choose virtual controller pair mode.

Wired: I connect the controller on the PC and nothing happens. The battery charge LED turns on, but Linux doesn't recognize it. If a press any button on the control the LEDs will start blinking and it tries to connect using Bluetooth, despite being connected with a USB cable. The pairs button combinations does nothing.

What I'm doing wrong?

golgor commented 2 years ago

Maybe you already solved the issue, but I had similar issues. I tried installing and removing in a number of different ways and never got it working. I plugged in my Controllers (Nintendo Switch Pro) and I didn't get any indication at all.

Then I decided to compile and install both hid-nintendo-dkms and Joycond from source instead and all of the sudden everything started working as expected. A few seconds after plugging in my controllers I get the indication on the Player LEDs and pairing with L + R and [+] + [-] is working fine.

No idea if there are some issues with the Arch-packages, though I did notice that they were quite a few commits behind on for example Joycond. I hope this helps someone!

xlash123 commented 2 years ago

Maybe you already solved the issue, but I had similar issues. I tried installing and removing in a number of different ways and never got it working. I plugged in my Controllers (Nintendo Switch Pro) and I didn't get any indication at all.

Then I decided to compile and install both hid-nintendo-dkms and Joycond from source instead and all of the sudden everything started working as expected. A few seconds after plugging in my controllers I get the indication on the Player LEDs and pairing with L + R and [+] + [-] is working fine.

No idea if there are some issues with the Arch-packages, though I did notice that they were quite a few commits behind on for example Joycond. I hope this helps someone!

That did it for me too. It was weird, because I already had gotten this to work, but I needed to reinstall both of those to get it to work again.

Edit: I also run Manjaro (5.16.2-1), and Linux 5.16 now has the hid-nintendo driver built-in, but looking at the Manjaro repo, and it looks like they have it disabled in the config... So for now, it looks like hid-nintendo-dkms is still required on Manjaro. I believe vanilla Arch would not have to install that package.

golgor commented 2 years ago

That did it for me too. It was weird, because I already had gotten this to work, but I needed to reinstall both of those to get it to work again.

Edit: I also run Manjaro (5.16.2-1), and Linux 5.16 now has the hid-nintendo driver built-in, but looking at the Manjaro repo, and it looks like they have it disabled in the config... So for now, it looks like hid-nintendo-dkms is still required on Manjaro. I believe vanilla Arch would not have to install that package.

Are you sure about the Manjaro not having the driver active? I removed both the Kernel Mod and Joycond and my controllers are working good, at least when plugged in via USB-C (Bluetooth is behaving wierd, but that shouldn't hid-nintendo driver be responsible for).

They are directly identified as a Input Device and I can see when I press buttons etc. when I plug them in and Steam also identifies them correctly.

Apteryks commented 2 months ago

As it pairs on my system, which is not Arch, I guess this should be reported against Arch instead.