Repository navigation
Installation
On most distributions the driver installs with one command. Most people want the desktop app, which installs everything in one go. If you prefer scripts, or run a headless box (a computer with no desktop), there is a command-line path too.
The driver supports the Logitech RS50, the G PRO Racing Wheel (both the Xbox/PC and PS/PC versions), and the G923 (both editions, with its own feature set; see G923). If you have a G920 or G29, those keep working with the in-tree kernel driver, the one that ships with Linux itself. This project does not touch them.
G923 owners: the install below is the same. There is nothing extra to do.
The Xbox edition also wants the usb_modeswitch package (the distro
packages recommend it). That package lets the wheel leave its console-only
boot mode. Details are on the G923 page. The RS50 Xbox edition
wants the same package for the same reason. It boots as 046d:c275 and
speaks the console's protocol. On every plug-in it is switched to
046d:c276. After that it is an ordinary RS50 to everything here.
The settings app is logi-wheel and the window is logi-wheel-gui.
logi-dd and logi-dd-gui remain as symlinks (a symlink is a name that
points at another file). The driver, logi-ffb and logi-tf-sim keep
their names. ("dd" meant direct drive. The app now configures the
gear-driven G923 too.)
Existing installs upgrade in place. The new packages replace the old ones
through your package manager. logi-dd and logi-dd-gui stay behind as
symlinks, so old scripts, launch options and desktop shortcuts keep
working. The first time the app needs them, it copies your profiles and
tf-sim.conf from ~/.config/logi-dd to ~/.config/logi-wheel. The old
files stay where they are.
-
Most people: the desktop app. Install
logi-wheel-gui. You get everything (the driver, the settings app, and the game helpers) from one package. You do the rest from inside the app. The terminal is needed for the single install command only. Start here. - Prefer the command line, or running headless? Skip to Manual / command-line install. It covers the from-source script, the individual packages and the health check.
Install the logi-wheel-gui package for your distribution. It pulls in the
driver and the helpers automatically. So this one command installs the
whole stack and adds a menu entry:
| Distribution | Install |
|---|---|
| Arch, CachyOS, Manjaro |
paru -S logi-wheel-gui (AUR, or your AUR helper) |
| Debian, Ubuntu, Mint, Pop!_OS | download the .debs from Releases, then sudo apt install ./logitech-trueforce-dkms_*.deb ./logi-wheel_*.deb ./logi-wheel-gui_*.deb
|
| Fedora, Nobara | sudo dnf copr enable mescon/logitech-trueforce && sudo dnf install akmod-logitech-trueforce logi-wheel-gui |
| openSUSE | OBS repo home:mescon, then sudo zypper install logi-wheel-gui
|
| Bazzite, Silverblue, Kinoite | atomic; see the atomic section below |
| SteamOS (Steam Deck) | read-only and replaced on update; see the SteamOS section below |
| Others | build from source (in the manual section below) |
Step by step, for each distribution:
Arch, CachyOS, Manjaro
- Run
paru -S logi-wheel-gui, or use your own AUR helper. (The AUR is the Arch User Repository.)
Debian, Ubuntu, Mint, Pop!_OS
- Download the
.debfiles from Releases. - In the download folder, run
sudo apt install ./logitech-trueforce-dkms_*.deb ./logi-wheel_*.deb ./logi-wheel-gui_*.deb.
Fedora, Nobara
- Run
sudo dnf copr enable mescon/logitech-trueforce. (COPR is Fedora's user package service.) - Run
sudo dnf install akmod-logitech-trueforce logi-wheel-gui.
openSUSE
- Add the OBS repo
home:mescon. (OBS is the openSUSE Build Service.) - Run
sudo zypper install logi-wheel-gui.
Bazzite, Silverblue, Kinoite
- Follow the atomic section below.
SteamOS (Steam Deck)
- Follow the SteamOS section below.
Others
- Build from source. See the manual section below.
- Plug in the wheel.
- Open logi-wheel-gui from your applications menu.
No terminal step is needed. The package sets up permissions, so the app can control the wheel as your normal user. Everything else lives in the app:
- Info / Testing, the page it opens on: your wheel's name, serial and firmware, a live input tester, and the guarded force and TrueForce self-tests.
- Setup page: force feedback, TrueForce and per-game setup (see below).
- The other pages: rotation range, strength, LIGHTSYNC LEDs, response curves and profiles. Settings your wheel does not have are simply not shown.
See Configuring the Wheel for a tour of the app. See Force Feedback in Games for what force feedback and TrueForce are, and how to set up each game.
If that first page names your wheel, the driver loaded. To check from a
terminal instead, run sudo dmesg | grep -iE 'rs50|g pro|g923'. It shows
the same thing. (dmesg prints the kernel log.)
Safety: this is a direct-drive wheel. It produces up to 8 Nm. Keep hands clear, or hold the rim, whenever the driver loads, the wheel replugs, or profiles switch. The wheel can rotate under power.
Everything below is for people who prefer scripts, want the individual packages, or run a headless or SSH-only box with no desktop. It installs the same software. You drive it from the terminal app and sysfs (the kernel's settings file tree) instead of the desktop app.
Every channel builds the same three packages from this one repository. Dependencies pull the rest automatically, so you normally install just one:
| Package | Contents | Install it when |
|---|---|---|
logitech-trueforce-dkms (akmod on Fedora) |
the kernel driver + udev rules | you only want the wheel to work; games and sysfs are enough |
logi-wheel |
the terminal settings app, logi-ffb (force feedback for DirectInput games), logi-tf-sim (the simulated-TrueForce background helper), and the tool that installs Logitech's TrueForce files into your games |
a headless or terminal-first setup; depends on the driver package |
logi-wheel-gui |
the desktop settings app, menu entry and icon | a desktop; depends on logi-wheel, so this one package installs everything |
All channels are based on DKMS (akmod on Fedora). DKMS rebuilds the kernel module for each new kernel, so a kernel upgrade needs nothing from you.
For a box with no desktop, install logi-wheel instead of logi-wheel-gui.
It carries the terminal app and every helper:
| Distribution | Install |
|---|---|
| Arch, CachyOS, Manjaro |
paru -S logi-wheel (pulls the driver too) |
| Debian, Ubuntu, Mint, Pop!_OS | download the .debs from Releases, then sudo apt install ./logitech-trueforce-dkms_*.deb ./logi-wheel_*.deb
|
| Fedora, Nobara | sudo dnf copr enable mescon/logitech-trueforce && sudo dnf install akmod-logitech-trueforce logi-wheel |
| openSUSE | OBS repo home:mescon, then sudo zypper install logi-wheel
|
| NixOS | see NixOS below: one option in your configuration installs everything |
Step by step, for each distribution:
Arch, CachyOS, Manjaro
- Run
paru -S logi-wheel. It pulls the driver too.
Debian, Ubuntu, Mint, Pop!_OS
- Download the
.debfiles from Releases. - In the download folder, run
sudo apt install ./logitech-trueforce-dkms_*.deb ./logi-wheel_*.deb.
Fedora, Nobara
- Run
sudo dnf copr enable mescon/logitech-trueforce. - Run
sudo dnf install akmod-logitech-trueforce logi-wheel.
openSUSE
- Add the OBS repo
home:mescon. - Run
sudo zypper install logi-wheel.
NixOS
- Follow NixOS below. One option in your configuration installs everything.
Then, on every distribution:
- Plug in the wheel.
- Check
dmesgfor a line naming your wheel model:RS50 (native):,RS50 (G PRO compatibility mode):,G PRO:, orForce feedback support for G923 (classic mode)on a G923.
The udev rule makes the wheel settings writable for your user automatically. (udev is the service that sets device permissions.) No group membership or extra step is needed.
NixOS is packaged as a flake (a Nix project with pinned inputs). There is nothing to build by hand, and nothing to rebuild after a kernel upgrade. The module is built against whichever kernel your configuration selects, and it comes along with the system.
- Add the repository as an input:
# flake.nix
{
inputs = {
nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
logitech-trueforce.url = "github:mescon/logitech-trueforce-linux-driver";
logitech-trueforce.inputs.nixpkgs.follows = "nixpkgs";
};
outputs = { self, nixpkgs, ... }@inputs: {
nixosConfigurations.my-machine = nixpkgs.lib.nixosSystem {
system = "x86_64-linux";
specialArgs = { inherit inputs; };
modules = [ ./configuration.nix ];
};
};
}- Import the module and turn it on:
# configuration.nix
{ inputs, ... }:
{
imports = [ inputs.logitech-trueforce.nixosModules.default ];
hardware.logitech-trueforce.enable = true;
}- Run
nixos-rebuild switch. - Plug the wheel in.
- Check
dmesgas above.
That single option installs the kernel module, the udev rules, the settings apps and every helper. That includes the helpers games load themselves: the SDK proxy, the telemetry relay and the truck-sim plugin. As on every other distribution, you still have to supply one thing yourself: Logitech's own SDK DLLs (the Windows library files from Logitech's software kit). They cannot be redistributed. See Force Feedback in Games.
Two NixOS-specific notes:
- The helpers live under the package's own
share/logitech-trueforcedirectory, not/usr/share. The apps look there too. -
sudo ./tools/setup.shis the from-source route. It is not the way in on NixOS, because it writes to/etcand/usr. Use the module. To place the relay into a game's Proton prefix (the folder where Proton keeps a game's Windows files), use the settings app's per-game "Install relay" button.
NixOS support was contributed by @zarilion in #55.
One command does it all: the DKMS module, udev permissions, and the module load. If Logitech's TrueForce files are in place (see Force Feedback in Games), it also adds TrueForce support to every Steam game's Proton folder.
- Clone the repository and run the setup script:
git clone https://github.com/mescon/logitech-trueforce-linux-driver.git
cd logitech-trueforce-linux-driver
sudo ./tools/setup.shIt is safe to run again after a git pull or a kernel update. It ends
with a health check.
- Run the health check alone at any time, as your normal user:
./tools/setup.sh doctorEvery line should say PASS. Warnings tell you exactly what to run.
- Replug the wheel's USB cable.
- Check the kernel log:
sudo dmesg | grep -iE 'rs50|g pro|g923' # expect a line naming your wheelBuilding the Rust apps (logi-wheel, logi-wheel-gui, logi-ffb,
logi-tf-sim) from source needs Rust 1.88 or newer (1.92 for the GUI). On
distributions whose packaged rustc is older, install the toolchain with
rustup first. The prebuilt packages do not need Rust
at all. See Building and Contributing for details.
setup.sh stops before touching anything when cargo is missing. It fails
when the apps do not build. An app left over from an older build, next to a
new module, is a fault, not an install. It can look exactly like a driver
bug. sudo ./tools/setup.sh --without-apps installs the module alone, when
that is what you mean. Every app and the module carry the same build stamp.
logi-tf-sim --version prints it in parentheses, and dmesg shows the
module's. doctor fails when they were not built from the same source.
tools/dkms-update.sh rebuilds the apps after the module for the same
reason, unless given --module-only.
Safety: this is a direct-drive wheel. It produces up to 8 Nm. Keep hands clear, or hold the rim, whenever the driver loads, the wheel replugs, or profiles switch. The wheel can rotate under power.
On rpm-ostree systems (where the base system is a read-only image) DKMS
does not apply. Instead you build a kmod RPM once, in a toolbox. A
kmod RPM is a package that holds a prebuilt kernel module. A toolbox is a
mutable Fedora container that shares the host kernel. Then you layer the
RPM onto the base image. Verified on Fedora Silverblue 44.
- Create and enter a toolbox:
toolbox create -y logitech-build
toolbox enter logitech-build- Inside the toolbox, install the build tools, fetch the source and build the kmod:
sudo dnf install -y rpm-build make gcc kmodtool kernel-rpm-macros \
elfutils-libelf-devel git kmod "kernel-devel-$(uname -r)"
git clone https://github.com/mescon/logitech-trueforce-linux-driver.git
cd logitech-trueforce-linux-driver
VER=0.16.0 # match the upstream_ver line in the spec
mkdir -p ~/rpmbuild/SOURCES
git archive --prefix=logitech-trueforce-linux-driver-$VER/ \
-o ~/rpmbuild/SOURCES/logitech-trueforce-kmod-$VER.tar.gz HEAD
rpmbuild -bb packaging/akmods/logitech-trueforce-kmod.spec \
--define "kernels $(uname -r)"
exit- On the host (not in the toolbox), layer the resulting RPMs and reboot:
sudo rpm-ostree install \
~/rpmbuild/RPMS/x86_64/kmod-logitech-trueforce-*.rpm \
~/rpmbuild/RPMS/noarch/logitech-trueforce-kmod-common-*.rpm
sudo systemctl reboot- After the reboot, plug the wheel in. The module auto-loads.
- Confirm with
modinfo hid-logitech-dd.
Notes:
-
After a kernel update, rebuild. A static kmod does not rebuild itself
the way DKMS does. Repeat the toolbox build and run
rpm-ostree installagain, before you reboot into the new kernel. -
Bazzite ships a custom uBlue kernel. So
kernel-devel-$(uname -r)is not in the standard Fedora repos. Enable uBlue's akmods repo inside the toolbox first (sudo dnf copr enable ublue-os/akmods). Then run the same steps.
Confirmed on a Deck. The driver builds and loads, and the apps run. A G923 was bound and configured this way. What nobody has reported yet is force feedback in an actual game on one. If you try it, say what happened in issue #68. That is what turns this section into a supported path.
Three things make SteamOS different from ordinary Arch:
- The root filesystem is read-only until you unlock it.
-
A SteamOS update replaces
/usr. The driver, the apps and the udev rules all live there. So a system update removes them, and you reinstall. There is no way around that from our side. Plan for it instead. - The package database and keyring often start empty, because nothing is expected to be installed this way.
Do not build from the AUR here. SteamOS ships libraries without the
.pc files that describe them. So pkg-config (the tool a build uses to
find libraries) cannot find fontconfig, zlib, expat and the rest. The build
fails before it reaches anything of ours. Those files are only needed to
compile. The prebuilt packages run fine. That is why the binary
repository is the route.
- Unlock the filesystem and set up the package keyring:
sudo steamos-readonly disable
sudo pacman-key --init
sudo pacman-key --populate archlinux holo-
Add the signed repository exactly as in the Arch section of the README, including trusting the signing key.
-
Install the packages:
sudo pacman -Sy logi-wheel-gui logitech-trueforce-dkms- Install the kernel headers (see below for why):
sudo pacman -S "linux-neptune-$(uname -r | sed -n 's/.*neptune-\([0-9]*\).*/\1/p')-headers"- Check what you got:
modinfo hid-logitech-dd | head -3The kernel headers. The driver is a DKMS module, so it needs the
headers for the running kernel. (Headers are the files that describe the
kernel to a build.) SteamOS does ship them, one package per kernel series.
It already has dkms and gcc (confirmed on SteamOS 3.8.1x, kernel
6.16.12-valve24.5, in issue #68). The series number is in uname -r. The
command in step 4 lets the shell work the name out, instead of guessing it.
If that name comes out empty, pacman -Ss linux-neptune | grep -i header
lists them all, and uname -r says which series you are on.
The window needs 0.38.2 or newer. Before that, it was built against a
glibc (the core C library) newer than SteamOS ships. It would not start at
all, with libm.so.6: version 'GLIBC_2.43' not found. The terminal app was
never affected.
After every SteamOS update, repeat the install. Keep the commands in a
script under /home, which survives. Anything under /usr does not.
Do this one first. Put this in each sim's Steam launch options (Properties, General, Launch Options):
logi-launch %command%
Whichever wheel you have, that is the whole per-game setup. It works out what the game needs on the wheel you have plugged in, and applies it. Then turn Steam Input off for the game (Properties, Controller). That is the one thing it cannot do for you.
Then:
- Set your rotation range and strength: Configuring the Wheel.
- What that launch option actually does, and how to do it by hand: Force Feedback in Games.
- On a G923, the wheel-specific details: G923.
- Anything off: Troubleshooting.