Arch Linux User Repository

It has been working correctly after a "uninstall, reboot, install, reboot" process, though I don't know the reason. Thanks a lot for your help @marmis anyway

@vollowx I can still be firmware related, if you're missing linux-firmware-* packages for your hardware. AFAIK the most common Bluetooth hardwares are from Intel (linux-firmware-intel, MediaTek (linux-firmware-mediatek) and RealTek (linux-firmware-realtek).

Bluetooth: display as Xbox 360

That means it's (very likely) using the hid-xpadneo module.

(it was Xbox Series X yesterday)

Then it wasn't using xpadneo (probably falling back to the hid_microsoft module).

no rumbling at all, not to mention trigger force feedback, which I think means that it isn't controlled by xpadneo

Not sure about trigger force feedback, but rumbling should work on xpadneo (it does for me).

Wired: basic functions only, no features from xpadneo

Expected. Wired is handled by the (traditional) xpad module.

You should maybe try connecting your controller on another machine, preferably Windows or an Xbox. You could also update the controller firmware there, it might help with some issues. See Update your Xbox Wireless Controller. Funnily, that Microsoft page has a small mistake about their own controller: it says that "[the original Xbox Wireless Controller] has a small, circular 3.5-mm port on the bottom of the controller (if your controller has this port, you can only update via USB cable)", but it's the other way around: First Generation (2013) didn't have the phone jack and could not be updated wirelessly, all other versions (2015+) have both features.

I just reinstalled the whole system so it should not be the firmware problem. The situation now is

Bluetooth: display as Xbox 360 (it was Xbox Series X yesterday), no rumbling at all, not to mention trigger force feedback, which I think means that it isn't controlled by xpadneo Wired: basic functions only, no features from xpadneo

Also, @vollowx, xpadneo is not used for cable connection. The kernel uses xpad for that instead. And, yes, xpadneo always reports the device as "Xbox 360 Controller", doesn't matter the model or even the vendor. That is apparently just cosmetic, and the supported features are reported correctly for that device (see issues #397, #423, #457, #469 and #549). This behavior may change for version 0.11.

@vollowx I was testing my controller in some games here, no issue so far. I don't think this is a packaging issue.

If it was working yesterday, but not today, then I don't think it is a controller issue either, although it's still possible. Was there a kernel or firmware update recently for you? There have been some extra splitting of linux-firmware-* recently (see a15b5f9c) and you could be missing some required packages if you're not using linux-firmware.

If that's not the case, you can try uninstalling xpadneo-dkms temporarily, and see if the controller connects via Bluetooth using the in-tree kernel driver, xpad (actually, it's hid_microsoft for Bluetooth), just to check if it is related to xpadneo or not. If you're still having issues after that, then it might be something in the hardware. To check the controller hardware, try connecting it to another Bluetooth device, like your phone. Same thing with your Bluetooth controller, try connecting another device on it. Even if both setups work, a hardware/firmware issue is still possible.

Last thing you could try is a complete power cycle of both your controller and computer. Disconnect everything, remove batteries or let them discharge, force them on after discharged to clear any stored electricity from capacitors and then try bringing connecting them again. This worked for me on my last Bluetooth issue, and is the last thing I have in mind for an issue like yours.

@marmis I successfully loaded the module, and the gamepad stuck at a reconnecting loop. I'm using Xbox Series X on Bluetooth so it should be properly supported, and just yesterday it behaved normally, connected and rumbled immediately after turning it on. The following is how bluetoothctl outputs

hci0 AC:8E:BD:44:4F:F2 type LE Public disconnected with reason 3
[CHG] Device AC:8E:BD:44:4F:F2 ServicesResolved: no
[SIGNAL] org.bluez.Device1.Disconnected org.bluez.Reason.Remote Connection terminated by remote user
[CHG] Device AC:8E:BD:44:4F:F2 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
hci0 AC:8E:BD:44:4F:F2 type LE Public connected eir_len 14

I also tried to connect with a cable, it gets no rumbling when connected, nor the trigger force feedback, so I think it isn't loaded by xpadneo

@vollowx systemd-boot or any other bootloader shouldn't affect this. First of all, xpadneo is NOT loaded by default. The module uses a system to bind itself to specific supported devices, and is only loaded when these devices are connected. It is possible to always load it on boot via mkinitcpio configuration, but even then the bootloader should not affect how it is loaded.

Now, about the issue, you can check if the modules are installed like this:

ls /usr/lib/modules/*/updates/dkms/hid-xpadneo.ko.zst

If you see it there, then you can try loading them manually with sudo modprobe hid-xpadneo, then verify it with lsmod | grep xpadneo. If the module loads correctly with modprobe, but doesn't load automatically when the device is connected, it may be because your device or connection is not supported.

Edit: you may also need to update your firmware.

I've tried reinstalling linux linux-zen and their headers, dkms and xpadneo-dkms, and still xpadneo doesn't appear in lsmod. I'm using systemd boot, not sure if this is related to my problem.

sudo dkms status outputs

hid-xpadneo/v0.9.7, 6.15.6-arch1-1, x86_64: installed
hid-xpadneo/v0.9.7, 6.15.6-zen1-1-zen, x86_64: installed

and when installing xpadneo-dkms there are some strange outputs

(3/4) Install DKMS modules
==> dkms install --no-depmod hid-xpadneo/v0.9.7 -k 6.15.6-arch1-1
Deprecated feature: CLEAN (/usr/src/hid-xpadneo-v0.9.7/dkms.conf)
==> dkms install --no-depmod hid-xpadneo/v0.9.7 -k 6.15.6-zen1-1-zen
Deprecated feature: CLEAN (/var/lib/dkms/hid-xpadneo/v0.9.7/source/dkms.conf)

@brody Yeah, you're right. I dropped it, but pkgrel was not changed because it doesn't affect the final package.

I'm now preparing for the next xpadneo major release. The build process seems to have changed a bit, and it'll probably require PKGBUILD changes too. Not sure when that will land, though.