What makes us different from other similar websites? › Forums › Tech › 8-Bitdo M30 [Linux Configure]
Tagged: 8-bitdo, 8-bitdo Controller, 8-bitdo m30, Linux, m30
- This topic has 1 reply, 1 voice, and was last updated 6 days, 17 hours ago by
thumbtak.
Viewing 2 posts - 1 through 2 (of 2 total)
-
AuthorPosts
-
November 25, 2025 at 4:13 am #8267
thumbtakModerator
- Update your package list:
$ sudo apt updateor$ sudo dnf update
- Install the required tools:
$ sudo apt install dkms git bluez bluez-toolsor$ sudo dnf install dkms git bluez bluez-tools
- Download and Install xpadneo:
$ cd /tmp/$ git clone https://github.com/atar-axis/xpadneo.git$ cd xpadneo$ sudo ./install.sh
- Reboot:
$ sudo shutdown -r now
- Connect:
- Plug in the controller via USB
- Press and hold the tiny button at the top
- Unplug the controller via USB
- Depress the tiny button at the top
- Look for pairing light
- Open Bluetooth software
- Search for the device
- Trust the device
- Connect the device
December 4, 2025 at 7:48 pm #8348
thumbtakModeratorBluetooth Connection Fix Summary
The primary issue I was having is the Bluetooth service ($ bluetoothd) logging a “Rejected connection from !bonded device” error, meaning your system was refusing to complete the secure pairing process.Key Steps:
- Mode Check: We ensured the 8BitDo M30 was powered on in the START + B (D-Input/Android) mode, which is optimal for Linux.
- Identification: We used
$ bluetoothctl devicesto find and confirm the controller’s correct MAC address (xx:xx:xx:xx:xx:xx), discarding the incorrect one from the logs. - Forced Bonding: We used the following sequence in
bluetoothctlto manually override the pairing failure and create a permanent, trusted connection:$ remove [MAC address]: Cleared any corrupted, partial pairing keys from the system.$ pair [MAC address]: Initiated a fresh, successful secure pairing.$ trust [MAC address]: Crucially, this command told the system to accept connections from the M30 permanently, resolving the “Rejected connection” error.$ connect [MAC address]: Established the final, successful connection.
This process bypassed the GUI pairing failures and forced the necessary security keys to be stored, allowing the controller to connect wirelessly.
- Update your package list:
-
AuthorPosts
Viewing 2 posts - 1 through 2 (of 2 total)
- You must be logged in to reply to this topic.
