Re-connection and driver binding issues #91
Comments
so it gets stuck in a connected/unconnected loop when trying to connect it again (via bluetoothctl), right? |
Well yeah, sort of? And yes, I rebooted. ;) |
|
A connection loop is mostly caused by ERTM,
Thanks! |
I have to thank you. :) |
|
Okay so ERTM is disabled, that's right. What's in the folder /etc/modprobe.d/? If there is anything called xpadneo..., then please Show me it's content too :) |
Yes, there's a file with that name. |
|
okay, so it is not a problem while installing the driver, all files are where they should be. If so, then please run
|
That's output number one, none of both vibrate, even though the driver to one of them is set correctly, the other one just doesn't have a driver set. :( That's the output after I shut them down and connected them again: Now the black controller vibrated, the red one didn't. |
|
Oh and btw., I thought for about 10 minutes that I destroyed it completely, cause I updated my kernel and that's why the driver wasn't loaded, even though it said that (program identified that it was installed on old kernel). So it would be cool, if the driver was directly activated in a new kernel. ;) |
|
This driver is using DKMS which does, if you system is healthy, automatically rebuild the driver on every kernel update. If this doesn't work, then it is another issue - most probably not caused by a broken driver but a broken system. Your output is showing that you do a lot of things which are not correct, therefore let's try it again, step by step: Firstly, please start |
atar-axis
changed the title
Oh Ok, good to know that my five days old system is already broken, even though every other kernel module updated just fine, but OK, you're the dev. :D Here you go: |
|
I am not saying that the root cause is a broken system, but ist is not very unlikely. Btw, just because your system is "new" it does not mean that there aren't bugs and compatibility problems in it... Anyways, if the update of the module fails ever again, then please copy the output and open a new issue.
please run the following in now please remove reboot Tell me if you are ready to proceed |
I'm ready to go on now. |
|
If you haven't already, please reboot your system now. For the next step: |
I've already rebooted and yes. |
|
Please update the firmware of both gamepads! Do not(!) connect them via bluetooth to any other system, use a cable please (in Windows you need an USB connection anyway). |
I "updated" it, it already was latest firmware. |
|
okay fine - as said, this is not a problem - updating poved to be effective on setting back the internals to the default state. We already fixed a bunch of problems this way. Now please reinstall xpadneo and give me the output. Reboot afterwards. |
Here you go: |
|
again: if you haven't rebooted yet, please reboot now. After that, please run Give me the output ;) |
|
|
okay this is the first problem, the gamepad should not exist anymore since we removed it. |
As far as I could notice, a device that was found by the bluetooth manager is automatically added. |
|
what does |
I added |
|
Okay, let's keep that in mind for now. Please run |
|
|
Sorry for delay, here you go: Was bound to Xpad (red controller) |
|
Perfect, so it Looks like it is solved now :) |
|
Yep, seems so. :) Now we just need a USB dongle that can handle initial connection AND stable, lag free connection or the wireless dongle working. :D Btw. do you know if there's anyone trying to make it work? O.o |
|
concerning the connection issues: @ugly95 sent me two of his Sticks, i will have a look once they arrive. Concerning the WiFi dongle: See the Wiki Page Here on GitHub, it's complicated... |
|
Just want to add that I'm affected by this as well. I'm on Linux MInt 19.1 and using a custom Kernel 5.0 This is my device: I've used the files in your zip and I get this output: |
|
Did it work once you replaced the Files? |
|
No, it does not work properly. It is in a loop for a very long time until it connects eventually or the gamepad gives up and turn itself off: |
|
Please remove the What kind of BT do you use? onboard? USB dongle? |
|
This is the output: I'm using a USB dongle (this one to be precise). |
|
#93 Tell me if it works |
|
I didn't had problems prior Kernel 5.0 with this dongle and xpadneo, it could take up to 20 seconds by times, but never ran into these long loops. Is there a dongle you can recommend? Anyway, that command works pretty well, thanks. |
|
Hum, that's interesting... I will try to automate the connection. Gimme some time. At the moment it looks like the CSR dongle is the most reliable one - once connected. That's at least what @ugly95 observed |
|
Which is my experience as well, didn't had any disconnects or lags. Neither in Windows nor in Linux. The script works absolutely perfect for me. I have to wait around 1 second after the light turns on, when I fire it then up it will connect the controller instantly. |
|
Thanks, can you give me the ouput of |
|
|
Thanks! added it here: #93 |
|
This is the output: ./debug.sh
I'm using a USB dongle (this one to be precise). Doesn't have ERTM to be disabled? O.o |
|
According to Amazon, where I bought it, the Chip is CSR8510A10. However, I can not confirm that in any way, as even the package doesn't note which chip is being used. @germangoergs That Y means it's disabled. |
|
Yeah, misleading... Sorry |
|
Oh OK, sorry. 😅 |
thanks! |
|
Ohh, I can confirm the chip, it's noted in the kernel log: So me and @germangoergs have the same chip. |
|
Updated! Thanks. |
* changed udev rule as a result of #91 * Fix: udev script wasn't copied * Fix: Remove udev script too * satisfy shellcheck * Update VERSION
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:
Expected behavior
A clear and concise description of what you expected to happen.
The controller should be connected immediately again
Screenshots/Gifs
If applicable, add screenshots or animated gifs to help explain your problem.
System information
Please enable debugging output https://atar-axis.github.io/xpadneo/index.html#debugging
and add at least the following outputs
uname -aLinux 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/Linuxdmesgsudo find "/sys/kernel/debug/hid/" -name "0005:045E:*" -exec sh -c 'echo "{}" && head -1 "{}/rdesc" | tee /dev/tty | cksum && echo' \;[no output]
Additional context
Add any other context about the problem here.
You still did a great job, I hope you can make the "real" wireless adapter work. :)
The text was updated successfully, but these errors were encountered: