Closed ettmetal closed 2 years ago
What version of hid-nintendo are you using? Are you using the dkms module or building it into the kernel yourself?
Also I assume you're building joycond including this patch? https://github.com/DanielOgorchock/joycond/commit/0ae9c8fc07260786d86b19ca43525422073fe8a9
I thought that patch was backwards compat with the older hid-nintendo naming scheme for the leds, but maybe I broke it.
I'm using dkms, dkms-hid-nintendo v3.1. I didn't see that had been updated, I'll give it a try
Yes, the version of joycond I was building included that patch
It looks like updating hid-nintendo worked, it seems the change wasn't backward compatible as you hoped. Thanks for pointing me in the right direction, though :)
May I suggest adding a hid-nintendo version to the readme? If nothing else to remind impatient folks like myself that there is a dependency here, and we should go check it before disturbing you. Thanks for the hard work :D
Hello, i get the exact same issue using the current master-branch of joycond and dkms-hid-nintendo 3.2 i use manjaro-linux with kernel 5.14. Is there anything i can miss during the installation or should i use an older #commit to avoid this issue??
I found the problem... dkms-hid-nintendo was not installed, but the package-manager prompted install successful. I was missing the linux-headers.
I don't know how else to explain the issue. When connecting a joycon (L or R), bluetooth settings report that it is connected but instead of all lights blinking as expected with joycond, they continues to ping-pong up and down.
running
sudo journalctl -u joycond --follow
shows many lines of output like(real values redacted)
At first, I thought the "//" was maaaybe a mistake, so I changed phys_ctlr.cpp:35 to not add a slash before
devpath
, but after recompiling I get the same output (with one less slash).