Skip to main content

DualSense: PS5 Bazzite Deck

Pair in Game Mode, not in the desktop: the desktop's Bluetooth settings don't complete the pairing with a DualSense.

PS5 Bazzite Deck has two ways to use one controller in both the PS5 OS and Linux. ps5-bt-address status shows which one is on.

Shared pairing (address off)Linux-only address (address on)
Default onSlim (MediaTek), from v2.8.1original PS5 (IW620) and PS5 Pro
Pairingone, made in the PS5 OS; Linux gets it at every start through the loaderone in the PS5 OS and one in Linux, on two controller profiles
NeedsPS5 Bazzite Deck v2.9 or newer and bazzite-bootc-loader v2.9 or newera DualSense with profiles (its software 0630, PS5 system software 12.00)
Warm reboots on the IW620workrestarts go through the PS5 OS

The setting is stored in the install's /etc: it stays through updates, but a reflash or switching from Legacy to bootc starts from the default again. Check it after either.

Shared pairing​

The loader hands the PS5 OS's active pairings to Linux at every start, and ps5-bt-import adds them to Linux's Bluetooth settings before Bluetooth starts. The controller then connects in both systems without pairing again.

  1. On an original PS5 or a Pro, in Linux: ps5-bt-address off. On a Slim it's already off.
  2. Start Linux with bazzite-bootc-loader v2.9 or newer (bazzite-bootc-loader-v2.9.elf and later, from the releases).
  3. Power off. In the PS5 OS, check that the controller connects; pair it there if not.
  4. Start Linux with the loader and press the PS button: it connects.

Check it: ps5-bt-address status says off, and journalctl -b -u ps5-bt-import -o cat reports the pairings it brought over. If it says no pairing export from the loader, an older loader started Linux.

  • Pair in the PS5 OS, not in Linux. A pairing made in Linux replaces the PS5 OS's, and the next start through the loader brings the PS5 OS's back.
  • A newly paired controller comes over at the next start through the loader. A warm reboot keeps the pairings Linux already has.
  • Controllers paired in Linux while the address was on stop connecting after the switch: pair them in the PS5 OS, then start Linux with the loader.
  • Not with the boot files on the console's own storage (ps5-m2-install --boot): Linux can't read the pairings the loader leaves there.

Linux-only address​

A boot-time service (ps5-bt-addr, ps5-bt-pro-addr on the Pro) gives Linux an address of its own, with its own pairing on a second controller profile. Turn it on with ps5-bt-address on, then power off and start with the loader.

  1. Make sure the controller is paired with the PS5 OS on one profile.
  2. In Linux, hold PS + Square (or another face button than the PS5's): the controller switches to that profile and blinks fast if it holds no pairing yet. If it doesn't blink fast, hold PS + Create until it does (on the PS5's profile, that would replace the PS5's pairing).
  3. Pair it in Game Mode's Bluetooth settings.
  4. From then on, hold PS + the profile's button for 2 to 3 seconds to switch: the PS5's profile in the PS5 OS, the Linux profile in Linux.
  • bluetoothctl and the Bluetooth settings still show the original address; the chip and the DualSense use the new one (ps5-bt-address status shows it).
  • In rest mode both profiles can wake the PS5; once it has started, only the PS5 profile connects.
  • IW620 (original PS5): while the address is on, sudo reboot silently does a normal restart through the PS5 OS, even with ps5-warm-reboot on: the chip doesn't survive a warm reboot with the changed address. For warm reboots, use the shared pairing.
  • With the address off and a loader older than v2.9, a controller paired in the PS5 OS reaches Linux with a key Linux doesn't have and is refused in a loop, see Controller refused in a loop.

How the address is set per chip, and the pitfalls found in testing, are on Bluetooth.