emilyst
commented
1 year ago Hi,
First of all, this driver is much appreciated, as I was previously using a really janky workaround for my N64 NSO controller with the Steam input driver which had odd button mapping and control stick range issues.
I'm so glad this module helped you. It makes my day. :)
However, I'm having some issues with bluetooth pairing. I can pair the controller and connect the first time with no issues. However, any subsequent connection attempts will not work. I need to completely unpair and re-pair the controller for it to work again.
I haven't encountered this issue. I wanted to see if I could reproduce, but I'm having a hard time getting Bluetooth working properly on my system at the moment. (Unrelated to this.)
Do you get any interesting output from the kernel when you disconnect and attempt to reconnect? (For example, with journalctl -b -e -k.)
I have a hunch that it's not correctly terminating the connection when turning off the controller, as each time I do this process and reconnect, the controller gets the next player input (i.e. on first attempt the player one LED lights up on the controller, on second attempt the player two LED lights up, etc.)
I understand why you would think that, but the LED behavior is something I inherited from the mainline kernel module. It doesn't properly keep track of connections and instead merely increments the number until it wraps back to 1. It is something I've meant to fix, but which has not been a huge priority. The Sony driver probably does what I want, so I could probably copy that sometime.
It's still true there may be some issue when disconnecting and reconnecting in my driver, but the LEDs aren't an indicator of it.
Any thoughts as to why this might be happening? I'm on Manjaro Linux and installed using DPKG as per the instructions, ran modprobe hid-nx, etc. I know bluetooth receivers are notoriously troublesome from device to device, so I'm not convinced my motherboard's bluetooth (which I'm using) is any good.
I am honestly not sure what is causing this. The fact is that little of the behavior within the driver module actually handles Bluetooth stuff. The kernel subsystems for Bluetooth or USB all just sort of forward things to the HID layer, where this driver picks up and attempts to handle it. (There's some Bluetooth specific stuff, but not a lot.)
For purposes of diagnosing, it would be interesting if you could find any interesting output in the system journal.
I would also be interested in knowing if a different Switch controller (like the Switch Pro controller, or a Joy-Con, if you have any handy) exhibit the issue here, or if it's specific to the N64 controller. If the latter, we know the issue is probably either with the controller (unlikely) or my driver (more likely). If the former, it's some issue in your PC hardware or the kernel.
I'm also not getting rumble in Retroarch, though I am getting it in fftest, so I'm pretty sure I'm just using the wrong Retroarch input/controller driver.
Oof, yeah, this is probably an issue with the indirection through the Steam layer, since Steam doesn't really know about my driver. When there's rumble, it has to come from the RetroArch core (which one are you using, by the way?), through to the RetroArch virtual device, to the core input driver, to SDL, to Steam, then to the kernel driver layer. It's a lot of hurdles, and I wouldn't be shocked if the rumble information is getting lost somewhere along the way.
If you want to test this out, you can try switching RetroArch from using the sdl input core to something like udev. It'll require you to reconfigure the controller, but then you can test it without Steam being in the way.
Thanks for any help you can provide.
Thanks again for this useful report. If you can get the additional information or try out some more testing, I would appreciate it. This is unfortunately part of using an "experimental" driver—sometimes you have to experiment. Thanks for bearing with me.
SuperSamus
Leaguesman
tmarki
nfp0
Hi,
First of all, this driver is much appreciated, as I was previously using a really janky workaround for my N64 NSO controller with the Steam input driver which had odd button mapping and control stick range issues.
However, I'm having some issues with bluetooth pairing. I can pair the controller and connect the first time with no issues. However, any subsequent connection attempts will not work. I need to completely unpair and re-pair the controller for it to work again. I have a hunch that it's not correctly terminating the connection when turning off the controller, as each time I do this process and reconnect, the controller gets the next player input (i.e. on first attempt the player one LED lights up on the controller, on second attempt the player two LED lights up, etc.)
Any thoughts as to why this might be happening? I'm on Manjaro Linux and installed using DPKG as per the instructions, ran modprobe hid-nx, etc. I know bluetooth receivers are notoriously troublesome from device to device, so I'm not convinced my motherboard's bluetooth (which I'm using) is any good.
I'm also not getting rumble in Retroarch, though I am getting it in fftest, so I'm pretty sure I'm just using the wrong Retroarch input/controller driver.
Thanks for any help you can provide.