Closed TobiPeterG closed 5 years ago
Ohh, I can confirm the chip, it's noted in the kernel log:
kernel: usb 3-1.4: new full-speed USB device number 11 using xhci_hcd
kernel: usb 3-1.4: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=88.91
kernel: usb 3-1.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
kernel: usb 3-1.4: Product: CSR8510 A10
So me and @germangoergs have the same chip.
Updated! Thanks. I am going to close this issue since the binding problems are solved and the other issues are not related to the driver itself. But I will work in it anyway.
Describe the bug A clear and concise description of what the bug is. When I disconnected my controller or shut my PC down, I'm having some troubles to re-connect it via bluetooth. It shows that it's trying to connect, but goes back to un-connected state and so on. To Reproduce Steps to reproduce the behavior:
System information Please enable debugging output https://atar-axis.github.io/xpadneo/index.html#debugging and add at least the following outputs
uname -a
Linux Tobias-Linux 5.0.3-1-default #1 SMP Fri Mar 22 17:30:35 UTC 2019 (2a31831) x86_64 x86_64 x86_64 GNU/Linux
dmesg
sudo find "/sys/kernel/debug/hid/" -name "0005:045E:*" -exec sh -c 'echo "{}" && head -1 "{}/rdesc" | tee /dev/tty | cksum && echo' \;
[no output] Additional contextAdd any other context about the problem here. You still did a great job, I hope you can make the "real" wireless adapter work. :)