Xbox Controller not working on Rocky Linux 10.2

Hi, this is my first post here. Hope I am doing something right. I’ve been trying to get my Xbox PowerA Wired Controller to work with the system. it shows that it is connected via notification, it also shows on lsusb. But it doesn’t actually work(The LED light doesn’t even come on). I have a GameSir cyclone 2 too and everything works except the Xbox Preset so I figure it’s just an xbox controller problem.

I have searched online and they said I should install xpad, tried it but apparently it’s not in the repo (either that or I don’t know how to). They also said xpadneo but I can’t find that either. I thought I could find a solution here but it seems no one has asked for 10.2. Could anyone help me please?

According to https://pkgs.org/search/?q=xpad the packages are available in a third-party repository called Terra.

Install instructions for using that repository here: Installing | Terra Documentation

Maybe that will help.

Hi @KenStacks ! I’ve had this exact issue, and there are a couple of workarounds available. You may have to get your hands dirty though…

The issue stems from the Rocky kernel, being a Red Hat Enterprise clone, does not include the xpad driver, one of the main kernel drivers for gamepads. You can either grab the driver and build it yourself, or switch to a different, more “mainstream” kernel:

  1. Build the Driver

You can grab the code from here: https://github.com/paroj/xpad

You’ll need some packages installed to make it work: gcc make automake kernel-headers kernel-devel

It’s as simple as opening a terminal in the code’s folder and:

make

sudo insmod ./xpad.ko

2. Switch to another kernel
This is a little more involved, generally I recommend ELRepo if you want to run a different upstream kernel on your Rocky system: https://elrepo.org/wiki/doku.php?id=start

It involves adding their repository and installing the kernel packages: I think the “mainline” 7.2.x is currently available for Rocky 10.

Note both of these methods requires secureboot to be turned off on your system. Alternate kernels and self-built drivers are not signed with a Microsoft-trusted key, and your system will refuse to load them with secureboot enforced.