Drivers

RakuOS only loads kernel drivers that carry a valid signature. Drivers that aren't part of the Linux kernel itself are built and signed by RakuOS and shipped as rakuos-kmod-* packages, ready for every RakuOS kernel. Nothing is compiled on your PC.

Included in every image

Broadcom Wi-Fi (wl)
v4l2loopback (virtual cameras, for example for OBS)
The NVIDIA driver, on NVIDIA images (see below)

Every other driver is opt-in: you install the ones your hardware needs (see Opt-in drivers).

If something stopped working after an update: images built before 23 October 2026 also included the Xbox controller, racing wheel, AYANEO, capture card and sensor drivers. Newer images leave them out, so after updating you need to install the ones you use from the Drivers page.

NVIDIA

Use an NVIDIA image: it comes with the signed driver built in. In RakuOS System, page System, set Nvidia to:

Nvidia for current cards, or
Nvidia Legacy (580xx driver) for Maxwell, Pascal and Volta cards (GTX 900 and 10 series, Titan V),

then click Switch Image and reboot. See Switching images.

Don't use rakuos setup-nvidia, RPM Fusion's akmod-nvidia or NVIDIA's .run installer: they build the driver on your PC, and that driver won't load.

Opt-in drivers

These drivers are built and signed by RakuOS but not included in the images, so you install the ones you need:

Driver	For	Needs
xone	Xbox wireless adapter, wired Xbox One / Series controllers	Terra
xpadneo	Xbox One / Series controllers over Bluetooth	Terra
xpad-noone	Xbox 360 and original Xbox controllers	Terra
hid-fanatecff	Fanatec racing wheels	Terra
hid-tmff2, t150-driver	Thrustmaster racing wheels (T300RS, T248, TX, TS-XW, T-GT II; T150, TMX)	Terra
new-lg4ff, logitech-trueforce	Logitech racing wheels (G25 to G923; TrueForce)	Terra
ayaneo-leds	RGB lights on AYANEO handhelds	Terra
sc0710	4K capture cards such as the Elgato 4K60 Pro	Terra
nct6687d, ryzen_smu, zenergy	Fan, temperature and CPU power sensors (MSI boards, AMD Ryzen)	Terra
VirtualBox, OpenRazer, MediaTek MT7927, Intel IPU6, Intel Vision, xtables-addons	See below	See below

The easiest way is the Drivers page in RakuOS System: it lists the drivers available for your kernel, says what each is for and which repository it needs, and installs it with one click. Turn the repository on first in the Welcome app's Third-Party Repositories page (see Repositories). Reboot when it asks. The page needs the overlay turned on.

Or install them in a terminal. For the drivers in the table above:

sudo rum config-manager --set-enabled terra
sudo rum install rakuos-kmod-xone      # use the driver's name from the table

VirtualBox, because it brings VirtualBox itself. Turn on RPM Fusion (see Repositories), then:

sudo rum install VirtualBox rakuos-kmod-VirtualBox

OpenRazer, for Razer keyboards and mice. It's left out because it misbehaved with Razer's RGB hub. Turn on Terra, then:

sudo rum install rakuos-kmod-openrazer

MediaTek MT7927 Wi-Fi. It's left out because it caused problems with a MediaTek USB Wi-Fi adapter. If your MT7927 card needs it:

sudo rum install rakuos-kmod-mediatek-mt7927

Intel IPU6 laptop cameras, the built-in camera on many recent Intel laptops. Turn on Terra, then:

sudo rum install rakuos-kmod-intel-ipu6

Some of those laptops also need Intel Vision (the Vision Sensing Controller in front of the camera). Turn on RPM Fusion, then:

sudo rum install rakuos-kmod-intel-vision

xtables-addons, extra firewall matches and targets such as GeoIP blocking. Turn on RPM Fusion, then:

sudo rum install rakuos-kmod-xtables-addons

Images built before 23 October 2026 included the last three; newer ones leave them out.

Reboot after installing any of them. On the staging channel the package names end in -staging (for example rakuos-kmod-VirtualBox-staging); rum list --base | grep rakuos-kmod shows which names your system uses.

How drivers you installed stay up to date

A driver is built for one particular kernel. Drivers that come with RakuOS update together with the system. The ones you installed yourself follow along on their own:

When a system update brings a new kernel, your drivers are switched to the builds for that kernel first, whether you update from the Software Center, RakuOS System or sudo rum system-upgrade. Moving between the stable and staging channels switches them to the matching builds too. After the reboot they're ready for the new kernel.
Otherwise, driver updates only appear when they're for the kernel you're running. When RakuOS rebuilds a driver for the same kernel, it shows up as a normal update. A build for a newer kernel waits until the system update that brings that kernel, so it doesn't show up early in the Software Center or in rum check-upgrade.
A driver's helper packages wait for the driver. Packages a driver needs, such as its firmware or *-kmod-common package, keep their version until the driver itself updates, so the two always match.

If a newer driver is in the repository but isn't offered, it's for a kernel you don't have yet; it arrives with the next system update. Don't force it with rum install or a downloaded RPM: it wouldn't load on the kernel you're running.

If a driver has no build for the new kernel yet, the update says so ("no build for kernel … yet") and carries on; the driver loads again once its build is published and you update.

Don't install akmod or DKMS packages

akmod-* and dkms-* packages build the driver on your PC. That driver isn't signed with the RakuOS key, so the kernel refuses it ("Key was rejected by service"). If you installed any, remove them; for every driver above, the RakuOS package already does the job:

sudo rum remove akmod-<name>     # or dkms-<name>

A driver you need is missing

Ask on Discord or report it with the akmod or DKMS package it comes from, and we'll add it to the signed builds.

Checking

rum list --base | grep rakuos-kmod   # signed drivers that come with RakuOS
rum list | grep rakuos-kmod          # signed drivers you installed yourself
modinfo -F signer <module>           # who signed a driver