-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trying to set up xpadneo on Raspberry Pi 2 running buster with kernel 6.6 #497
Comments
Here's the module build log +
|
I guess this is the issue - see
rpi-source outputs:
|
Tried to point
But it didn't work:
|
FWIW, got it working with the same version of xpadneo running the same Pi 2 under bookworm with kernel 6.6.31+rpt-rpi-v7 (got a completely fresh installation on separate SD card for testing). Controller paired successfully without any noticeable issues. Relevant info - module details:
from bluetoothctl:
Also, on this kernel I didn't have to play with disabling ERTM or doing any other custom stuff, things just worked out of the box. The Would still love to see it working under buster... |
TWIMC, if you're on buster and trying to use rpi-source to get latest kernel sources matching your updated kernel, you'll likely need this one - RPi-Distro/rpi-source#35. |
I encounter the same issue I am trying to bypass, but different versions of some things, however vermagic still 5.10 matching your problematic example exactly When pairing Xbox Series X it also throws:
But my vermagic version is the same: ( 5.10.103-v7l+ SMP)
I followed your lead and wiped the sd, starting with fresh brandnew version of raspian, installed retropie and then xpadneo ontop of that, When trying to connect now, the status is continually flipping:
no messages in I try using hid-xpadneo to get some output but get the module not found error like I think you might be mentioning here:
When manually attempting connection with my other remote I get
I am working through troubleshooting steps and will report back : https://atar-axis.github.io/xpadneo/#troubleshooting |
For me, the issue was partly because my kernel was version 8, and when running the two commands I got a complaint.
Then xpadneo was running, but it still took me a lot of connection attempts to get them paired. Finally when they reported as paired I would reboot the bluetooth service
I also followed a reddit user's guide to modify some additional things: 1.Enabling uhid First we need to enable the UserspaceHID if we don't do that the Controller won't connect properly and begins to connect and disconnect in a cycle and the Xbox Button will keep flashing All you need to do is edit/create /etc/bluetooth/input.conf with your editor of choice (I prefer nano) In there paste this:
We need to set some settings in the main bluetooth config file so xpadneo will work as intended and we also need to address the input lag Problem all you need to do is editing /etc/bluetooth/main.conf pasting in this:
Install bluez bluez-utils and dkms beforehand git clone https://github.com/atar-axis/xpadneo.git Afterwards Reboot your system
|
Version of xpadneo
Controller Model
Connection mode
Installed Software
Protocol Information
Please help us identify at which layer the problem can be found if you want
to report mapping errors or if the controller fails to be detected:
evtest
is showing issues (describe the issues below)BTN_NORTH
andBTN_WEST
are intentionally swappedjstest
is showing issues (describe the issues below)gamepad-tool
is showing issues (post console output below)Please describe how it is failing below in the next sections.
Severity / Impact
Describe the Bug
I'm trying to set up an Xbox Wireless Controller with Raspberry Pi 2 running Raspbian 10 (buster) with latest available kernel (6.6.51-v7+). The final goal is to install RetroPie on that device, hence the choice of buster (RetroPie fails to install flawlessly on bullseye and newer releases).
I was using exactly that controller with exactly that Pi 2, but with another USB bluetooth adapter a few years back with either RetroPie own image, or Raspbian stretch with RetroPie installed manually - can not recall these days, but the thing is that it worked pretty well.
Now I'm using TP-Link UB400 adapter, and unfortunately it does not work with buster running original kernel (5.10.103) - device itself is visible, bluetooth service is running, but no BT devices can be found during scanning; i.e. the adapter is completely blind.
Things go better with the latest kernel I was able to install with
rpi-update
- 6.6.51. Adapter is visible and I can see all my BT devices in scanning mode, including Xbox controller.However, when I try to actually pair and connect to the controller, literally nothing happens - it continues to blink with the X button and does not do rumble, while in
bluetoothctl
I can see that it is connected and paired, e.g.:I have tried to remove and re-pair it multiple times, the result is the same.
Then, I tried to figure out why it could happen and found out really weird thing: after rebooting I can't see
uhid
orhid-xpadneo
modules loaded:But when I try to load xpadneo manually, I get this:
I did not have any errors while installing the module with install.sh.
Steps to Reproduce
So, here's how I reached the above described stage:
2023-05-03-raspios-buster-armhf-lite.img
(https://downloads.raspberrypi.com/raspios_oldstable_lite_armhf/images/raspios_oldstable_lite_armhf-2023-05-03/).6.6.51-v7+ #1799 SMP Thu Sep 26 16:09:25 BST 2024 armv7l GNU/Linux
(withrpi-update
).Expected Behavior
Xbox controller able to fully pair to be used in RetroPie.
Screenshots / GIFs / Videos
System Information
Controller and Bluetooth Information
btmon output:
dmesg:
lsusb:
lsusb verbose:
Additional Context
JFTR, with the original 5.10.103 kernel I saw these errors in
systemctl status bluetooth
output:With the 6.6.51 kernel (current setup I'm struggling with) I am seeing this:
Also, after I tried to disable ERTM with this:
and rebooted, I saw these errors a few times in journal logs:
and this one in
bluetoothctl
after yet another remove + reconnect attempt:The text was updated successfully, but these errors were encountered: