nfp0

> journalctl prints it out. @a-priestley Really? I've been using `journalctl -u bluetooth.service -b` after the disconnect happens and I don't see that message anywhere. Am I targeting the correct...

@a-priestley Even with that command, I don't get the error. You did not get that error while using it through Steam, did you? I've raised -p to 4 and I...

@tmarki Pairing issues are unlikely to be related to this driver. Kernel 5.10 is indeed a very old kernel, and kernels since 6.8 already include the features of this driver,...

I don't think you need this driver to use the SNES controller, as it's detected as a standard HID device. It won't be set to high-report mode, but it should...

> However, the reconnect problem still persist, I have to re-pair every time to be able to use it, which means it's unrelated to this module, so this issue could...

@pwallner Does it have the same product id and device name as the 3B?

> Right now, the only real solution I can think of would be to report customized names for the devices, based on the driver's knowledge of the device types. This...

> In order for me to distinguish them, I wrote code in the driver to use the reported _type_ most of the time. This is a value that the device...

Please disregard my previous post. I only now realized I had the [hid-nintendo-nso-dkms](https://aur.archlinux.org/packages/hid-nintendo-nso-dkms) driver installed and not this one.

~I have tested with my N64 controllers and everything seems to be working correctly.~ **EDIT: Please ignore this post and read my next one. I was using a different driver.**...