Closed TobiPeterG closed 5 years ago
atar-axis
commented
5 years ago Hey there! 1) When did you made the dmesg output? Have you had already connected both gamepads? 2) What happens if you change the order in which you connect the gamepads? Is it always the same (physical) gamepad that doesn't rumble or is it always the second one connected?
TobiPeterG
commented
5 years ago Hey there!
1. When did you made the dmesg output? Have you had already connected both gamepads? 2. What happens if you change the order in which you connect the gamepads? Is it always the same (physical) gamepad that doesn't rumble or is it always the second one connected?
Yep, I think that both should have been connected, but I can gather new dmesg if you want. I took the dmesg right after I had exactly this problem :D
It's always the black one, no matter which I connect first. ;)
atar-axis
commented
5 years ago It's always the black one, no matter which I connect first. ;)
Ah, that's interesting! Could you please do the following for me:
1) Connect both gamepads as always
2) Go to /sys/bus/hid/devices/
3) Show me the output of ls -la in there
4) Open each folder that starts with 0005:045E and show me again the output of ls -la there
atar-axis
commented
5 years ago btw, can you maybe confirm this issue: #89 ?
TobiPeterG
commented
5 years ago It's always the black one, no matter which I connect first. ;)
Ah, that's interesting! Could you please do the following for me:
1. Connect both gamepads as always 2. Go to `/sys/bus/hid/devices/` 3. Show me the output of `ls -la` in there 4. Open each folder that starts with `0005:045E` and show me again the output of `ls -la` there
Oh wait, I was wrong, sorry. This time the red one vibrated, sorry.
So it seems like the second connected vibrates.
/sys/bus/hid/devices> ls -la
insgesamt 0
drwxr-xr-x 2 root root 0 2. Apr 18:27 .
drwxr-xr-x 4 root root 0 2. Apr 18:27 ..
lrwxrwxrwx 1 root root 0 2. Apr 18:27 0003:046D:C335.0003 -> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.3/1-3.3:1.0/0003:046D:C335.0003
lrwxrwxrwx 1 root root 0 2. Apr 18:27 0003:046D:C531.0001 -> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.1/1-3.1:1.0/0003:046D:C531.0001
lrwxrwxrwx 1 root root 0 2. Apr 18:27 0003:046D:C531.0002 -> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.1/1-3.1:1.1/0003:046D:C531.0002
lrwxrwxrwx 1 root root 0 2. Apr 18:31 0005:045E:02FD.0005 -> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.2/1-3.2:1.0/bluetooth/hci0/hci0:62/0005:045E:02FD.0005
lrwxrwxrwx 1 root root 0 2. Apr 18:31 0005:045E:02FD.0006 -> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.2/1-3.2:1.0/bluetooth/hci0/hci0:69/0005:045E:02FD.0006/sys/bus/hid/devices/0005:045E:02FD.0005> ls -la
insgesamt 0
drwxr-xr-x 6 root root 0 2. Apr 18:31 .
drwxr-xr-x 4 root root 0 2. Apr 18:31 ..
-r--r--r-- 1 root root 4096 2. Apr 18:34 country
lrwxrwxrwx 1 root root 0 2. Apr 18:31 driver -> ../../../../../../../../../../../bus/hid/drivers/microsoft
drwxr-xr-x 3 root root 0 2. Apr 18:31 hidraw
drwxr-xr-x 3 root root 0 2. Apr 18:31 input
-r--r--r-- 1 root root 4096 2. Apr 18:34 modalias
drwxr-xr-x 2 root root 0 2. Apr 18:31 power
drwxr-xr-x 3 root root 0 2. Apr 18:31 power_supply
-r--r--r-- 1 root root 4096 2. Apr 18:34 report_descriptor
lrwxrwxrwx 1 root root 0 2. Apr 18:31 subsystem -> ../../../../../../../../../../../bus/hid
-rw-r--r-- 1 root root 4096 2. Apr 18:31 uevent/sys/bus/hid/devices/0005:045E:02FD.0006> ls -la
insgesamt 0
drwxr-xr-x 6 root root 0 2. Apr 18:31 .
drwxr-xr-x 4 root root 0 2. Apr 18:31 ..
-r--r--r-- 1 root root 4096 2. Apr 18:35 country
lrwxrwxrwx 1 root root 0 2. Apr 18:31 driver -> ../../../../../../../../../../../bus/hid/drivers/xpadneo
drwxr-xr-x 3 root root 0 2. Apr 18:31 hidraw
drwxr-xr-x 3 root root 0 2. Apr 18:31 input
-r--r--r-- 1 root root 4096 2. Apr 18:35 modalias
drwxr-xr-x 2 root root 0 2. Apr 18:31 power
drwxr-xr-x 3 root root 0 2. Apr 18:31 power_supply
-r--r--r-- 1 root root 4096 2. Apr 18:35 report_descriptor
lrwxrwxrwx 1 root root 0 2. Apr 18:31 subsystem -> ../../../../../../../../../../../bus/hid
-rw-r--r-- 1 root root 4096 2. Apr 18:31 ueventThese are the outputs. :)
And thanks for providing help. :)
TobiPeterG
commented
5 years ago btw, can you maybe confirm this issue: #89 ?
Unfortunately, I don't know what this "Emulation Station" shall be, sorry. O.o
atar-axis
commented
5 years ago okay perfect, thing is that only one of your gamepads is using the correct driver. The question now is: why?
The one which vibrates is the one which is connected to xpadneo. Can you please make sure that it is always the second one? I need something like a pattern
TobiPeterG
commented
5 years ago okay perfect, thing is that only one of your gamepads is using the correct driver. The question now is: why?
The one which vibrates is the one which is connected to xpadneo. Can you please make sure that it is always the second one? I need something like a pattern
Ok ok, I think I got how it works (mostly).
So it's just the black controller that's vibrating when connected, the red one didn't in like 10 tries, so I think there's just a little probability that the red one will vibrate again, maybe I mixed both up and the black vibrated back then in reality. So it seems that it's the black one.
Interestingly though is that I also saw that my black one was connected, but there wasn't a driver "set" to it. It also didn't vibrate then. A "simple" re-connection fixed that though.
Also, I have no problems connected the controllers, when I set them in pairing mode and connect them manually by pressing "connect" on my PC.
atar-axis
commented
5 years ago I think we can have a look at this issue in the other one, let's try to fix them together. I will close this for now in favor of #91
Describe the bug A clear and concise description of what the bug is.
I do own two Xbox One Controllers, one black and one red (the red can be found here: https://www.amazon.de/dp/B01MY13UKE/ref=twister_B00I03MYC6?_encoding=UTF8&psc=1), the other one was given to me to Christmas. The strange behavior I could notice is that when I connect the black one, it rumbles as it should, but the red one doesn't when connected, even though I checked everything and also re-connected it. But there's no ff.
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 -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 contextAdd any other context about the problem here. You still did a great job, I hope you can make the "real" wireless adapter work. :)