# Changing Xbox controller driver

**URL:** https://universal-blue.discourse.group/t/changing-xbox-controller-driver/3444
**Category:** Bazzite
**Created:** [August 7, 2024, 7:34pm UTC](https://universal-blue.discourse.group/t/changing-xbox-controller-driver/3444 "2024-08-07T19:34:55Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![impulse](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/impulse/32/2945_2.png) [@impulse](https://universal-blue.discourse.group/u/impulse)
#### Post date: [August 7, 2024, 7:34pm UTC](https://universal-blue.discourse.group/t/changing-xbox-controller-driver/3444/1 "2024-08-07T19:34:55Z")

</div>

Not sure where to post this at. Is there a way that you could add, change, or update the driver for xbox controllers to the xbox series x driver? When you do a fresh install of the OS it defaults the driver to xbox 360. Steam does not let you change this. Is it hard coded somewhere ??? Thank you for all of your hard work! Amazing team!!! Love the OS!!!

---

<div class="post-metadata">

### Author: ![Slippery](https://avatars.discourse-cdn.com/v4/letter/s/85e7bf/32.png) [@Slippery](https://universal-blue.discourse.group/u/Slippery)
#### Post date: [August 10, 2024, 4:06pm UTC](https://universal-blue.discourse.group/t/changing-xbox-controller-driver/3444/2 "2024-08-10T16:06:52Z")

</div>

Are you connecting the controller, with bluetooth, the dongle, or USB? I think Bazzite uses the `xone` driver to connect with the dongle. Not sure about bluetooth. USB uses `xpad`, which only supports wired Xbox One and Xbox 360, and defaults to the latter for unrecognized devices. That might be what’s happening. I assume there’s a compatibility reason for Bazzite not using regular `xone` and `xpad-noone` like Nobara.

---

<div class="post-metadata">

### Author: ![impulse](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/impulse/32/2945_2.png) [@impulse](https://universal-blue.discourse.group/u/impulse)
#### Post date: [August 13, 2024, 1:31am UTC](https://universal-blue.discourse.group/t/changing-xbox-controller-driver/3444/3 "2024-08-13T01:31:48Z")

</div>

I’m using a USB Bluetooth adapter. I have uninstalled all drivers that for the xbox controller, reinstalled the latest drivers for the xbox series x controller. I’ve used xpad and several other controller config softwares. The system sees the controller, I can get readouts through the terminal showing the controller inputs in real time. The problem is with Steam. It is some how hard coded to an xbox 360 controller. I have no clue how to override this. I have been through all of the config files and manually set it to my controller. It still defaults to a 360 controller.

---

<div class="post-metadata">

### Author: ![aenect](https://avatars.discourse-cdn.com/v4/letter/a/edb3f5/32.png) [@aenect](https://universal-blue.discourse.group/u/aenect)
#### Post date: [October 3, 2024, 2:20pm UTC](https://universal-blue.discourse.group/t/changing-xbox-controller-driver/3444/4 "2024-10-03T14:20:40Z")

</div>

I’m having an issue with (two) xbox controllers disconnecting when using a bluetooth adapter. I have tried two controllers, two adapters, have updated my controllers via windows 11 separately, but get consistent 4-5 second disconnects on the controller every so often. I’m 4-5 feet away from the adapter with no obstructions. Anyone else run into this issue on Bazzite OS? It seems to be a bluetooth stack issue potentially.

---

<div class="post-metadata">

### Author: ![bertybassett](https://avatars.discourse-cdn.com/v4/letter/b/c77e96/32.png) [@bertybassett](https://universal-blue.discourse.group/u/bertybassett)
#### Post date: [November 27, 2024, 10:45am UTC](https://universal-blue.discourse.group/t/changing-xbox-controller-driver/3444/5 "2024-11-27T10:45:24Z")

</div>

> [@Slippery](#):
>
> Nobara

I get the same, changing the dongle to a different chipset helped a little now I can go 50 minutes or so

---

<div class="post-metadata">

### Author: ![MalvoTheReal](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/malvothereal/32/10362_2.png) [@MalvoTheReal](https://universal-blue.discourse.group/u/MalvoTheReal)
#### Post date: [September 4, 2026, 10:57am UTC](https://universal-blue.discourse.group/t/changing-xbox-controller-driver/3444/6 "2026-09-04T10:57:10Z")

</div>

My system dont see my Xbox controller, but i found a way to fix it, the problem mainly was in Privacy setting at: /etc/bluetooth/main.conf and BLE mode on my usb bluetooth adapter, as Xbox controllers use BLE mode to pair. Here is what helps, i find that fix with chatgpt and ask him to make a tuto:

Xbox Controller not detected over Bluetooth on Bazzite/Linux — fix for CSR/Barrot `0a12:0001`

I ran into an issue on **Bazzite KDE** where an Xbox Wireless Controller worked perfectly over USB and also connected normally over Bluetooth in Windows, but Bazzite/Linux could not detect it at all.

Bluetooth adapter:

```auto

```

```auto
ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle

```

However, `bluetoothctl show` reported manufacturer `2279`, which means this is actually one of the **Barrot-based adapters** that identifies itself using the old CSR USB ID.

The following errors appeared during scanning:

```auto

```

```auto
org.bluez.Error.InProgress

```

and with `btmgmt`:

```auto

```

```auto
Unable to start discovery. status 0x0d (Invalid Parameters)

```

### What fixed it

In my case, the problem was related to Bluetooth Privacy.

Open:

```auto

```

```auto
sudo nano /etc/bluetooth/main.conf

```

Under the `[General]` section, set:

```auto

```

```auto
Privacy = off

```

Important: if you previously had:

```auto

```

```auto
Privacy = network

```

replace it with `off`.

Save the file and restart Bluetooth:

```auto

```

```auto
sudo systemctl restart bluetooth

```

Then reset the Bluetooth controller settings with:

```auto

```

```auto
sudo btmgmt power off
sudo btmgmt privacy off
sudo btmgmt le on
sudo btmgmt bredr on
sudo btmgmt power on

```

Check the current state:

```auto

```

```auto
sudo btmgmt info

```

Under `current settings`, the regular `privacy` flag should no longer be present.

`ll-privacy` may still remain — that is fine.

### Test Xbox Controller discovery

Put the Xbox Controller into pairing mode so the Xbox button is flashing rapidly.

Run an LE-only scan:

```auto

```

```auto
sudo btmgmt find -l

```

After applying the fix, my controller immediately appeared:

```auto

```

```auto
name Xbox Wireless Controller
type LE Public

```

So BLE discovery was finally working correctly.

### Pair the controller

Stop the low-level scan:

```auto

```

```auto
sudo btmgmt stop-find

```

Then start:

```auto

```

```auto
bluetoothctl

```

Inside `bluetoothctl`, run:

```auto

```

```auto
power on
agent on
default-agent
scan le

```

Once the Xbox Controller appears, note its MAC address, for example:

```auto

```

```auto
68:6C:E6:59:1C:43

```

Then run:

```auto

```

```auto
pair 68:6C:E6:59:1C:43
trust 68:6C:E6:59:1C:43
connect 68:6C:E6:59:1C:43

```

You can verify the connection with:

```auto

```

```auto
info 68:6C:E6:59:1C:43

```

A successful result should look similar to:

```auto

```

```auto
Paired: yes
Bonded: yes
Trusted: yes
Connected: yes

```

After that, the Xbox Controller should work normally over Bluetooth in Bazzite/Steam.

### Short version

If Bazzite/Linux detects your adapter as:

```auto

```

```auto
0a12:0001 Cambridge Silicon Radio

```

but cannot find your Xbox Controller, try:

```auto

```

```auto
# /etc/bluetooth/main.conf

[General]
Privacy = off

```

Then run:

```auto

```

```auto
sudo systemctl restart bluetooth

sudo btmgmt power off
sudo btmgmt privacy off
sudo btmgmt le on
sudo btmgmt bredr on
sudo btmgmt power on

sudo btmgmt find -l

```

**In my case, disabling Bluetooth Privacy immediately fixed BLE scanning, and the Xbox Wireless Controller became visible and connected successfully.**

One more note: run `btmgmt` commands with `sudo`. Without it, you may get:

```auto

```

```auto
status 0x14 (Permission Denied)

```

Also, if the controller is detected with a very weak RSSI such as `-90` to `-100`, keep it close to the Bluetooth dongle during the first pairing attempt.
