Best Sim Racing Wheels for Linux: Mainline FFB vs DKMS Drivers

Picking the best racing wheel for Linux comes down to a question the box never answers: is the force feedback driver already in your kernel? Moza bases work with the stock kernel on any current distro, and the Xbox edition of the Logitech G923 gets there after a one-time USB mode switch. Thrustmaster and Fanatec bases still need out-of-tree drivers that you rebuild with DKMS after every kernel update, and on a PC with Secure Boot those drivers won’t load until you enroll a signing key.

Original content from computingforgeeks.com - post 179408

That split decides more than torque or pedal feel, so we ranked six wheels by how much work they take on Linux, then by what they cost. We built hid-tmff2, hid-fanatecff and new-lg4ff, read the device tables of the in-kernel drivers, and set up Oversteer and Boxflat from Flathub. Prices and stock below were checked in October 2026, the same week we ran every driver build on a Fedora 45 VM with Secure Boot left on.

Best racing wheel for Linux: the quick picks

For most people we’d buy the Moza R5 bundle. It is a 5.5 Nm direct drive base with a wheel and two pedals, its force feedback runs on the in-kernel hid-universal-pidff driver, and on Amazon it costs about the same as a gear-driven Logitech. Here’s where each pick wins, with rough price bands because wheel prices move weekly before Black Friday:

• Best overall: Moza R5 Bundle, about $330 to $420. Direct drive, mainline force feedback since kernel 6.15, Boxflat for settings.
• Best budget: Moza R3 Bundle, about $250 to $350. The cheapest direct drive kit here, and it undercuts the G29.
• Best gear-driven wheel: Logitech G923 for Xbox and PC, about $300 to $400. Three pedals and a mainline driver once a usb_modeswitch rule flips it into PC mode.
• Best used-market favourite: Logitech G29, about $250 to $350. Works on every distro, but the stock driver only plays constant force.
• Best Thrustmaster: Thrustmaster T300RS GT, about $400 to $500. Belt-driven feel, and the T300RS is one of the two wheels the hid-tmff2 maintainer tests on.
• Best upgrade path: Fanatec CSL DD 5 Nm base, about $350 to $450 for the base alone. The deepest rim and pedal catalogue, through the hid-fanatecff DKMS driver.

If you don’t want to babysit kernel modules or USB rules, stop at the two Mozas: they’re the only picks that need nothing beyond a current kernel. The G923 needs one udev rule written once. The G29 upgrade, the Thrustmaster and the Fanatec all rely on a DKMS driver, which works well once it’s set up, but it’s your job to keep it working across kernel updates.

Mainline FFB vs DKMS: the picks at a glance

The driver column matters more than the torque column. A mainline driver ships signed inside your distro’s kernel package, so it survives updates and Secure Boot without any action from you. A DKMS driver gets rebuilt from source after each kernel update, which works until the day an upstream kernel change breaks the build and your wheel goes dead until the maintainer catches up:

Wheel	Drive and torque	Pedals	Linux FFB driver	In mainline?	Settings app
Moza R5 Bundle	Direct drive, 5.5 Nm	2 (Hall)	hid-universal-pidff	Yes, 6.15 (backported to 6.12.24, 6.13.12, 6.14.3)	Boxflat
Moza R3 Bundle	Direct drive, 3.9 Nm	2 (Hall)	hid-universal-pidff	Yes, same kernels	Boxflat
Logitech G923 Xbox/PC	Gear, dual motor	3	hid-logitech-hidpp	Yes, since 6.3 (plus a usb_modeswitch rule)	Oversteer
Logitech G29	Gear, dual motor	3	hid-logitech (lg4ff)	Yes, constant force only	Oversteer
Thrustmaster T300RS GT	Dual belt, 25 W brushless	3 (T3PA-GT)	hid-tmff2	No, DKMS	Oversteer
Fanatec CSL DD	Direct drive, 5 Nm (8 Nm with Boost Kit)	None, base only	hid-fanatecff	No, DKMS	Oversteer, sysfs

Torque figures come from the manufacturers’ spec pages. Thrustmaster does not publish a torque number for the T300RS GT, and Logitech’s 2.3 Nm marketing figure for the G923 isn’t measured the same way as a direct drive peak, so we left both out rather than compare unlike numbers. No wheel was plugged into the lab VM. What we tested is the part a review on Windows can’t tell you: which module claims each wheel’s USB ID in a current kernel, and whether the out-of-tree drivers build and load on it.

Your distro probably already has the Moza driver. Ubuntu 26.04 LTS ships kernel 7.0, Fedora 45 ships 7.2 and Debian 13 is on a 6.12 point release well past 6.12.24, so all three carry hid-universal-pidff. Older kernels miss it, such as the 6.8 kernel Ubuntu 24.04 originally shipped with. We’d still check rather than assume, and the commands for that are further down.

1. Moza R5 Bundle (best overall)

Moza’s R5 wins because it is the cheapest way to get direct drive force feedback that needs nothing from you on Linux. Moza’s bases speak the standard USB PID force feedback protocol, the same one Simucube and VRS use, and the kernel’s hid-universal-pidff module lists every Moza base from the R3 to the R21 by USB ID. Plug it in on a 6.15 or newer kernel and games see a wheel with force feedback, no package to install.

The bundle pairs the 5.5 Nm base with the 11-inch ES wheel (22 buttons) and the two-pedal SR-P Lite set with Hall sensors, plus a desk clamp. Moza rates the base at 2700 degrees of rotation and a 15-bit encoder. On Amazon the listing sells through Micro Center rather than Amazon itself, at about $330 to $420, so check the seller before you order. Moza lists this bundle as PC only, which is all you need on Linux.

Settings live in Boxflat, a community app that talks to the base over its serial interface and covers rotation, force feedback strength, the wheel’s LEDs and pedal curves. It cannot flash firmware, so a firmware update still means a Windows machine running Moza Pit House. Where the R5 falls short:

• Two pedals only: no clutch, and the SR-P Lite pedals are the part owners upgrade first.
• No PlayStation or Xbox: if the wheel has to move between your PC and a console, look at the Xbox R3 bundle or the T300RS GT.
• Firmware needs Windows: Boxflat configures the base but can’t update it.

Pick the R5 if you sim race on a Linux desktop and want the wheel to keep working through every kernel update without thinking about it.

2. Moza R3 Bundle (best budget)

Moza’s R3 is the budget pick because it costs less than a Logitech G29 and still gets you direct drive. It uses the same hid-universal-pidff driver and the same Boxflat setup as the R5, so everything above about Linux applies unchanged. The difference is the motor: 3.9 Nm peak against 5.5 Nm, which you’ll notice as lighter weight in heavy cars more than as missing detail.

Moza sells the R3 in a PC bundle and an Xbox-compatible bundle, and the base itself is the same 60 W, 15-bit unit with a 1000 Hz USB link. The Amazon listing we link is the PC bundle at about $250 to $350, again sold by Micro Center at the time we checked. That price put it roughly $20 under the G29 on the same day, which is why we’d skip the gear-driven Logitechs for a new Linux build unless you need three pedals in the box.

Its trade-offs are the R5’s plus less torque. Pick the R3 if your budget tops out near $300 or you want an Xbox-compatible base that also runs on Linux with the stock kernel.

3. Logitech G923 Xbox/PC (best gear-driven)

Logitech’s G923 is the best wheel here with three pedals in the box and a mainline driver, but only the Xbox and PC edition. That model (USB ID 046d:c26e) speaks Logitech’s HID++ protocol and is handled by the in-kernel hid-logitech-hidpp module, which gained it in kernel 6.3. The PlayStation and PC edition (c266 and c267) is not in any mainline driver at all. It needs the new-lg4ff DKMS module or a community TrueForce driver, so buying the wrong box turns a udev rule into a kernel module project.

Even the Xbox edition is not plug-and-play. It powers up as 046d:c26d, a console mode with no input device, and only becomes c26e after a USB mode-switch command. The kernel patch that added it says this needs usb_modeswitch with the same magic string as the G920, but the usb-modeswitch-data package that distros ship only carries a rule for the G920 (c261), not the G923. So you install the usb_modeswitch package (usb-modeswitch on Debian and Ubuntu) and write the rule yourself, once: the G923 page in the logitech-trueforce-linux-driver wiki documents a udev rule for it. We had no wheel in the lab to test that step, so treat it as the one manual job this pick needs.

Logitech specs the G923 at 900 degrees lock to lock with a Hall-effect steering sensor, stainless steel paddles and a three-pedal set. Boosted Media’s teardown found the same motors as the G29 and G920, plus TRUEFORCE, a high-frequency haptic layer that Linux games do not drive through the HID++ path. The Xbox/PC edition runs about $300 to $400 on Amazon. Its weak spots on Linux:

• TRUEFORCE stays off: you get regular force feedback, not the haptics Logitech advertises.
• Effect queue lag: the community wheel tracker rates the HID++ wheels Silver because of “queue full” force feedback lag in some games at high frame rates.
• Gear noise and deadzone: it is still a geared wheel, with the notchy feel that drives people to direct drive.

Pick the Xbox/PC G923 if you want a complete wheel and pedal set from one box without a DKMS driver, you’re fine writing one udev rule, and you’d rather have a clutch than direct drive.

4. Logitech G29 (best used-market favourite)

Logitech’s G29 works on more Linux machines than any other wheel because its driver, lg4ff inside the hid-logitech module, has been in the kernel for years. The catch is how little that driver does: it plays only the constant force effect. Spring, damper and friction effects, which many sims use for weight and road feel, need new-lg4ff instead. That’s a DKMS module, and our lab shows it carries a trap on Secure Boot machines.

new-lg4ff installs itself under the name hid-logitech, and DKMS moves the stock module aside to make room. With Secure Boot on and the DKMS key not enrolled, the new module then refuses to load, and the original is no longer in its place either. A G29 owner who installs new-lg4ff for better effects ends up with no driver at all until they enroll the key or remove the package. We walk through both fixes in the Secure Boot section below.

Hardware-wise it’s the G923 without TRUEFORCE: 900 degrees, Hall sensor, three pedals, PlayStation and PC. Keep its PS3/PS4 switch on PS3, because that mode’s USB ID (c24f) is the one the Linux drivers bind. It sells for about $250 to $350 new, and the Xbox twin, the G920, uses the HID++ driver like the G923. Pick the G29 if you already own one or find it cheap secondhand. At new prices the Moza R3 bundle is the better buy on Linux.

5. Thrustmaster T300RS GT (best Thrustmaster)

Thrustmaster’s T300RS GT is the one to buy for Linux because the base T300RS is one of the two wheels the hid-tmff2 maintainer owns and tests (reports say other editions, the GT included, work too), while the T248 sold on Amazon today is a newer revision the driver does not know. The mainline hid-thrustmaster module only switches Thrustmaster wheels out of their startup mode; it has no force feedback at all. In our Fedora 45 lab it claimed a single USB ID, 044f:b65d, the generic ID wheels show before that switch. Force feedback comes from hid-tmff2, built with DKMS.

The module we built from hid-tmff2 0.83 claims three T300RS IDs (044f:b66e, b66f and b66d), the original T248 (b696), the TX, the TS-XW and the TS-PC. The T300RS GT pairs a 25 W brushless motor with a dual-belt drive, which feels smoother than the Logitechs’ gears, and ships with the three-pedal T3PA-GT set. Thrustmaster does not list a torque or rotation figure on its page. It costs about $400 to $500 on Amazon, and the driver’s README spells out three limits:

• Firmware v31 or newer: older firmware is reported not to work, and the update needs Thrustmaster’s Windows tools.
• Effects aren’t a perfect match: the maintainer warns that some effects may differ from the Windows driver, and pedal mapping can be inconsistent between games.
• DKMS and Secure Boot: every kernel update rebuilds the module, and it will not load until you enroll the DKMS key.

Skip the cheaper T248 for now, even though it shows up in every console buyer’s guide. Amazon’s PS5 listing now ships the revised T248R, which hid-tmff2 does not support yet (issue #198 is still open), and the tracker carries an open report of an Xbox T248X not detecting the left half of its steering travel. Pick the T300RS GT if you already own Thrustmaster pedals and shifters, or share the wheel with a PlayStation (on PS5 it works with PS4 titles plus a short list of PS5 games that Thrustmaster names on its page). If the wheel only ever touches your Linux PC, the Moza R5 costs less and skips the DKMS step.

6. Fanatec CSL DD (best upgrade path)

Fanatec’s CSL DD is the base to buy if you expect to keep adding rims, pedals and shifters, and you’re comfortable owning a DKMS driver. No mainline module knows Fanatec hardware: on our Fedora 45 kernel, a search of modules.alias for Fanatec’s vendor ID 0eb7 returned zero matches. The community hid-fanatecff driver fills the gap with force feedback, rim LEDs, the rim display and rotation range through sysfs.

Fanatec rates the CSL DD at 5 Nm, or 8 Nm with the Boost Kit 180 power supply, with up to 2520 degrees of rotation. The listing we link is the base alone at about $350 to $450, so you still have to budget for a rim and pedals on top. Fanatec is now owned by Corsair after the old parent company went insolvent in 2024, and the hardware still sells on Amazon US under Corsair. The driver’s README lists the CSL DD, DD Pro and ClubSport DD family among its non-experimental bases, and the base has to be in PC mode. Its downsides:

• Base only: the real cost with a rim and pedals runs well past the Moza R5 bundle.
• Per-game Proton tweaks: Proton 10.0-2 and later read Fanatec bases over hidraw by default, which the driver’s table shows is the better path, but Le Mans Ultimate, rFactor 2 and DiRT Rally 2 each still need their own fix from that table.
• Install script noise on Fedora: the module installs fine, but install.sh ends with two errors because its last step looks for Debian-style /boot/initrd.img-* files and a dkms_autoinstaller helper that Fedora’s DKMS doesn’t ship.

Pick the CSL DD if you want Fanatec’s rim catalogue and plan to upgrade piece by piece. For a first wheel on Linux, a Moza bundle gets you direct drive with less to maintain.

Check which driver your kernel already ships

Before you order, a minute in a terminal tells you whether your kernel has the driver for the wheel you want. Start with the kernel version and Secure Boot state, because those two decide whether a DKMS wheel will need extra work:

uname -r; mokutil --sb-state

Our Fedora 45 VM reported a 7.2 kernel with Secure Boot on, the default on most new laptops and desktops:

7.2.13-300.fc45.x86_64
SecureBoot enabled

Next, ask the Moza driver which devices it claims. A “Module not found” error here means your kernel predates the backports and a Moza wheel will not have force feedback until you upgrade it:

modinfo hid-universal-pidff

The module is in-tree and signed with Fedora’s kernel key, which is why it loads under Secure Boot with no help. Vendor 346E is Moza, and its ten IDs give two each to the R3 (0005, 0015), R5 (0004, 0014), R9, R12 and R16/R21. We trimmed the output to the Moza lines; the full list of 25 also names Asetek, Cammus, PXN, Lite Star, VRS and FFBeast:

filename:       /lib/modules/7.2.13-300.fc45.x86_64/kernel/drivers/hid/hid-universal-pidff.ko.xz
description:    Universal driver for USB PID Force Feedback devices
alias:          hid:b0003g*v0000346Ep00000010
alias:          hid:b0003g*v0000346Ep00000000
alias:          hid:b0003g*v0000346Ep00000016
alias:          hid:b0003g*v0000346Ep00000006
alias:          hid:b0003g*v0000346Ep00000012
alias:          hid:b0003g*v0000346Ep00000002
alias:          hid:b0003g*v0000346Ep00000014
alias:          hid:b0003g*v0000346Ep00000004
alias:          hid:b0003g*v0000346Ep00000015
alias:          hid:b0003g*v0000346Ep00000005
intree:         Y
signer:         Fedora kernel signing key

The Logitech check works the same way. This filters the HID++ driver’s table down to Logitech’s wheel range:

modinfo -F alias hid-logitech-hidpp | grep -i 046Dp0000C2

Two IDs come back: C262 is the G920 and C26E the Xbox/PC G923. The PlayStation G923’s C266 and C267 are missing here and from the stock hid-logitech table too, which is the whole reason we tell you to buy the Xbox box:

hid:b0003g*v0000046Dp0000C26E
hid:b0003g*v0000046Dp0000C262

For Thrustmaster and Fanatec, two quick lookups confirm there is no force feedback driver for you to find in a stock kernel:

modinfo -F alias hid-thrustmaster
grep -ci 0EB7 /lib/modules/$(uname -r)/modules.alias

The Thrustmaster module claims one generic startup ID and nothing else, and the Fanatec count is zero:

hid:b0003g*v0000044Fp0000B65D
0

If those last two results match yours, a Thrustmaster or a CSL DD means building a driver. The next section shows what that looks like on a Secure Boot machine.

Load DKMS wheel drivers with Secure Boot on

The builds themselves were the easy part. Each driver built and installed against the 7.2 kernel in 34 to 39 seconds with DKMS 3.4.4 (pulled from updates-testing, like the kernel), and DKMS signed the modules with a key it generated on the spot. Install the build tools first; on Fedora the headers package has to match the running kernel exactly:

sudo dnf -y install dkms kernel-devel-$(uname -r) git make gcc

Our VM had already pulled a kernel from updates-testing during its first boot, so the first try failed with No match for argument: kernel-devel-7.2.13-300.fc45.x86_64. Adding --enablerepo=updates-testing fixed it. On Debian and Ubuntu, the hid-tmff2 README uses linux-headers-generic and dkms instead. Image-based systems such as Bazzite and Silverblue can’t run DKMS this way, so this section assumes a package-based install. Then build hid-tmff2 the way its README describes:

git clone --recurse-submodules https://github.com/Kimplul/hid-tmff2.git
cd hid-tmff2
sudo ./dkms/dkms-install.sh

Watch the signing lines (we trimmed the first symlink line and the last post-transaction line). DKMS created its own Machine Owner Key and signed the three modules with it, which is necessary but not enough, because the firmware does not trust that key yet:

Sign command: /lib/modules/7.2.13-300.fc45.x86_64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Certificate or key are missing, generating self signed certificate for MOK...

Building module(s).... done.
Signing module /var/lib/dkms/hid-tmff2/0.83/build/deps/hid-tminit/hid-tminit-new.ko
Signing module /var/lib/dkms/hid-tmff2/0.83/build/deps/hid-tminit/usb-tminit-new.ko
Signing module /var/lib/dkms/hid-tmff2/0.83/build/hid-tmff-new.ko
Installing /lib/modules/7.2.13-300.fc45.x86_64/extra/hid-tminit-new.ko.xz
Installing /lib/modules/7.2.13-300.fc45.x86_64/extra/usb-tminit-new.ko.xz
Installing /lib/modules/7.2.13-300.fc45.x86_64/extra/hid-tmff-new.ko.xz
Running depmod... done.

The README also recommends blacklisting the stock hid_thrustmaster module in /etc/modprobe.d/hid_thrustmaster.conf until its own init module is upstreamed, and offers an optional sudo make udev-rules. We did not need either for the build, but with a real wheel plugged in, follow both. The Fanatec and Logitech drivers build the same way. We added --release to the Fanatec installer, a flag in install.sh that builds without debug logging. Its README also says to run sudo udevadm control --reload-rules && sudo udevadm trigger afterwards so its udev rule applies:

git clone https://github.com/gotzl/hid-fanatecff.git
cd hid-fanatecff
sudo ./install.sh --release
sudo git clone https://github.com/berarma/new-lg4ff.git /usr/src/new-lg4ff
sudo dkms install /usr/src/new-lg4ff

Afterwards dkms status listed all three as installed. Loading them is where it went wrong. Each module failed with Key was rejected by service, including the replacement hid-logitech that new-lg4ff had swapped in. The screenshot is rendered from that capture and groups the three rejections together; in the raw log, the hid-logitech attempt came last, after an unload:

The last line explains it: /var/lib/dkms/mok.pub isn’t enrolled, so the kernel’s lockdown refuses anything signed with it. The fix from the DKMS documentation is a one-time enrollment, and it needs you at the physical console because the confirmation screen runs before the OS boots:

1. Run sudo mokutil --import /var/lib/dkms/mok.pub and set a one-time password.
2. Reboot. The blue MOK Manager screen appears; choose Enroll MOK, then Continue, then Yes.
3. Type the password, let the machine reboot, and confirm with mokutil --list-enrolled | grep DKMS.

We couldn’t drive the MOK Manager screen over SSH on the lab VM, so this step comes from the DKMS docs rather than our capture; it’s the same MokManager routine our NVIDIA driver guide for Fedora walks through for akmods, but with a different key, so an enrolled akmods key doesn’t cover DKMS. Once the key is enrolled, every later DKMS rebuild is signed with it and loads without another visit to that screen.

If you installed new-lg4ff and your G29 went dead, removing the package puts the stock driver back. DKMS restores the module it archived, and the in-kernel hid-logitech loaded again on our VM straight after. Take the version from dkms status, since a newer clone carries a newer number than our 0.5.0:

sudo dkms remove new-lg4ff/0.5.0 --all

The restore line is the one to look for (the final post-transaction line is trimmed):

Deleting /lib/modules/7.2.13-300.fc45.x86_64/extra/hid-logitech.ko.xz
Restoring archived original module /lib/modules/7.2.13-300.fc45.x86_64/kernel/drivers/hid/hid-logitech.ko.xz
Running depmod... done.

Deleting module new-lg4ff/0.5.0 completely from the DKMS tree.

Before the removal, the module did add something worth having: its alias table includes the PlayStation G923’s C266 and C267, which the stock table lacks. So new-lg4ff is the route for a PlayStation G923 owner, once the MOK is enrolled.

Set up Boxflat and Oversteer from Flathub

Neither settings app is in Fedora’s repositories, so Flathub is the practical source on every distro. Our Flatpak and Flathub guide covers adding the remote. Install whichever app matches your wheel, or both:

sudo flatpak install -y flathub io.github.berarma.Oversteer io.github.lawstorant.boxflat

Expect the download to take a few minutes, since you also pull the GNOME runtime; on our VM it took about three. flatpak info then reported the versions current on Flathub (trimmed to the name, ID and version lines):

Oversteer - A steering wheel manager
            ID: io.github.berarma.Oversteer
       Version: 0.8.3

Boxflat - Configure Moza Racing hardware
            ID: io.github.lawstorant.boxflat
       Version: v1.37.1

Boxflat talks to a Moza base over a USB serial port, and a sandboxed Flatpak can’t open /dev/ttyACM* unless a udev rule grants access. Boxflat’s README gives this rule, which we wrote to /etc/udev/rules.d/99-boxflat.rules and checked with udevadm verify:

echo 'SUBSYSTEM=="tty", KERNEL=="ttyACM*", ATTRS{idVendor}=="346e", ACTION=="add", MODE="0666", TAG+="uaccess"' | sudo tee /etc/udev/rules.d/99-boxflat.rules
sudo udevadm control --reload-rules

Unplug and replug the base after that. Oversteer has the same need for Logitech, Thrustmaster and Fanatec wheels, and its README lists the udev rule files to install alongside the Flatpak; hid-fanatecff’s installer already drops its own rule in place. Oversteer 0.8.3 sets rotation, autocenter and force feedback gain and stores per-game profiles, but it does not list Moza bases, so Moza owners use Boxflat only. With the wheel configured, our Steam and Proton setup on Fedora covers the game side, and the wheel tracker’s advice there is simple: turn Steam Input off for racing games.

Where each wheel falls short on Linux

No wheel here is free of compromise, and the Linux-specific ones are what decide it for most buyers:

• Moza R5 and R3: firmware updates still need Pit House on Windows, and both bundles ship with two pedals.
• Logitech G923 Xbox/PC: a hand-written usb_modeswitch rule before it shows up, no TRUEFORCE through the mainline driver, and no mainline support at all for the PlayStation edition.
• Logitech G29: the stock driver plays constant force only, and the DKMS fix breaks the wheel on Secure Boot until you enroll a key.
• Thrustmaster T300RS GT: DKMS forever, firmware updates on Windows, and the oldest design on this list.
• Fanatec CSL DD: DKMS forever, base-only pricing, and per-game Proton tweaks.

A few wheels didn’t make the list for Linux reasons. Logitech’s direct drive G PRO and RS50 aren’t in any mainline driver. A young community project, logitech-trueforce-linux-driver, adds them with TrueForce, but you’d depend on a single maintainer, and the TrueForce part needs DLLs copied from a Windows G HUB install, which is too fragile for a gift. Thrustmaster’s cheaper T128 is still listed as experimental in hid-tmff2, and the T248 is out until the T248R revision is supported. Simagic bases need their own out-of-tree driver, while Cammus and Asetek work on the same mainline driver as Moza if you’d rather shop outside these six.

If the wheel is a present for someone who runs Linux and just wants to race, the Moza R5 or R3 bundle is the safe gift, because nothing in it depends on a DKMS build. If you’re also deciding which distro to race on, our Fedora vs Bazzite comparison covers how each handles Steam and kernel updates.