Skip to content
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

Xbox wireless controller (from xbox series X) wont pair in Bazzite-deck-gnome: 39 #575

Closed
GotBearHeart opened this issue Nov 22, 2023 · 6 comments

Comments

@GotBearHeart
Copy link

Hello,
The xbox wireless controller can not be paired over bluetooth on an freshly installed Bazzite-deck-gnome.

Reproduction step:

  1. press the xbox wireless controller "pairing button" till the xbox icon flashes rapidly (activated pairing mode)
  2. in game mode or desktop mode, open "settings" app, navigate to "bluetooth" section
  3. "xbox wireless controller" appears in the found device
  4. click the device to start pairing
  5. --> failure, after some time, the pairing is not successful without error popup --> xbox wireless controller device remains "not set up".

rpm-ostree output:

`rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck-gnome:latest
Digest: sha256:b7c54d8286dac4571bf866d7ae274d6cb49682556db2651a101f1a9f17f7649d
Version: 39.20231120.0 (2023-11-21T03:00:24Z)
Initramfs: '-I /etc/crypttab /etc/modprobe.d/amdgpu.conf /etc/modprobe.d/deck-blacklist.conf'

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck-gnome:39
Digest: sha256:b7c54d8286dac4571bf866d7ae274d6cb49682556db2651a101f1a9f17f7649d
Version: 39.20231120.0 (2023-11-21T03:00:24Z)
Initramfs: '-I /etc/crypttab /etc/modprobe.d/amdgpu.conf /etc/modprobe.d/deck-blacklist.conf'
`

@castrojo castrojo transferred this issue from ublue-os/main Nov 22, 2023
@beefchimi
Copy link

I have the exact same issue, with the following exception:

  • I first installed 38 a few months ago.
  • Could pair my bluetooth mouse without issue.
    • XBox Elite Wireless Controller Series 2 however could not pair.
  • Controller was able to pair after following these instructions: Gamepad/Controllers do not work out of the box #299
  • However, I reported on a separate issue relating to the controller disconnecting: [Controller] Xbox Elite Series 2 rumble/vibration #418
  • I managed to get a Windows 10 PC to update the firmware of the controller (now on version `5.17.3202.0)
  • After updating the firmware, I was no longer able to pair the controller, getting the same issue as you.
  • I rebased to v39 hoping that would solve the issue...
    • Sadly, still the same issue.

@GotBearHeart
Copy link
Author

Today I stumbled upon a solution by trying to use command line method of pairing, instead of using settings UI:
Following xpadneo github page

Connection

sudo bluetoothctl

  • [bluetooth]# scan on
  • wait until all available devices are listed (otherwise it may be hard to identify which one is the gamepad)
  • push the connect button on upper side of the gamepad, and hold it down until the light starts flashing fast
  • wait for the gamepad to show up in bluetoothctl, remember the address (e.g. C8:3F:26:XX:XX:XX)
  • [bluetooth]# scan off to stop scanning as it may interfere with properly pairing the controller
  • [bluetooth]# pair <MAC>
  • [bluetooth]# trust <MAC>
  • [bluetooth]# connect <MAC> (should usually not be needed but there are open bugs)
  • The <MAC> parameter is optional if the command line already shows the controller name

You know that everything works fine when you feel the gamepad rumble ;)

@beefchimi
Copy link

beefchimi commented Nov 25, 2023

Sadly, this method did not work for me 😭 I simply get Device <MAC> is not available.

I believe I followed your instructions exactly. I've pasted the Konsole lines for reference, just in case. In the snippet below, I have replaced all MAC addresses with <HIDDEN-ADDRESS>. In the case of the Xbox address, I replaced it with <HIDDEN-ADDRESS-I-WANT>. But when typing the command, I did in fact use the correct address. I also removed a few lines I believe were unrelevant (just lots of [NEW] address lines).

beefchimi@fedora:/var/home/beefchimi$ sudo bluetoothctl
Agent registered
[MX Master 3S M]# scan on
hci0 type 7 discovering on
Discovery started
[CHG] Controller <HIDDEN-ADDRESS> Discovering: yes
[NEW] Device <HIDDEN-ADDRESS>
hci0 type 7 discovering off
hci0 type 7 discovering on
hci0 type 7 discovering off
[DEL] Device <HIDDEN-ADDRESS>
hci0 type 7 discovering on
[CHG] Device <HIDDEN-ADDRESS> RSSI: 0xffffffb5 (-75)
hci0 type 7 discovering off
hci0 type 7 discovering on
[NEW] Device <HIDDEN-ADDRESS-I-WANT> Xbox Wireless Controller
[MX Master 3S M]# scan off
hci0 type 7 discovering off
Discovery stopped
[CHG] Device <HIDDEN-ADDRESS> RSSI is nil
[MX Master 3S M]# pair <HIDDEN-ADDRESS-I-WANT>
Device <HIDDEN-ADDRESS-I-WANT> not available
[MX Master 3S M]# trust <HIDDEN-ADDRESS-I-WANT>
Device <HIDDEN-ADDRESS-I-WANT> not available
[MX Master 3S M]# connect <HIDDEN-ADDRESS-I-WANT>
Device <HIDDEN-ADDRESS-I-WANT> not available
[MX Master 3S M]# 
quit

@ParetoOptimalDev
Copy link

I simply get Device is not available.

@beefchimi Just hold the "connect" button on the top of your controller untilt he light flashes.

@JaCh0o
Copy link

JaCh0o commented Dec 10, 2023

Same here, I can connect controller in gamepad steam but still doesn't work, no keys are responding

@Razuuu
Copy link

Razuuu commented Dec 15, 2023

Same here with "Xbox Wireless Controller"
It's connected, displayed in Steam but no button works. If turning the controller off and on it wont connect again
Even lights still blinking
Edit: Holy shit what? Updated the controller via a Windows PC and now it works?!

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants