RADII(1)

💅 RADII(1) — the glow-up edition

okay so bestie, this is the manual page for RADII(1) from the General Commands Manual — and no, that's not a typo, the page is called RADII but the command you actually type is rhel-drivers. we love a stage name 💖. anyway, sit down, grab a strawberry drink 🍓, and let me tell you about the girl who installs your GPU drivers the right way.

---

✨ NAME ✨

rhel-drivers — install and manage hardware driver stacks. that's it. that's the whole personality. 🫶

---

🌸 SYNOPSIS 🌸

rhel-drivers install --auto-detect
rhel-drivers install vendor[:version] ...

rhel-drivers remove --all
rhel-drivers remove vendor[:version] ...

rhel-drivers list [--available] [--installed]

rhel-drivers --help
rhel-drivers --version

like, there's genuinely nothing scary here. it's giving "four verbs, no drama". 👑

---

🦋 DESCRIPTION 🦋

rhel-drivers installs, removes, and queries hardware driver stacks for GPUs and AI accelerators, using packages that are available through the system's configured software repositories. no cap. 💅

here's the iconic part: instead of invoking vendor-provided installer scripts (we do NOT do sketchy mystery downloads, bestie, not after last time 😭), rhel-drivers relies entirely on repository-managed packages. this means driver components get installed, upgraded, and removed using the exact same mechanisms as the rest of the system — and driver updates follow normal package management workflows. so when your package manager is having its main-character moment, the drivers come along for the ride. ✨

drivers may be supplied by the base distribution or by additional repositories configured by the administrator. for example, a system may use a hardware vendor repository alongside the distribution's own repositories, and rhel-drivers will select drivers from whichever sources are enabled. iykyk — it just picks from what's on the menu. 🎀

the simplest way to install drivers is:

rhel-drivers install --auto-detect

in this mode, rhel-drivers attempts to detect accelerator hardware present in the system and installs the default driver stack for each detected device vendor. one command, all your detected faves get the install treatment. 🌈

real talk though — hardware detection is performed on a best-effort basis. because detection relies on available system information and known device mappings, it may fail to recognize some devices, or may produce incomplete results in unusual configurations. so don't come for her if your weird rig doesn't show up. she tried. 🙈

drivers may also be selected explicitly by specifying a vendor identifier. and yes, the --force option allows installation to proceed even if the detected hardware does not appear to match the requested driver — it's the "bestie, i know what i'm doing" flag. 🔥

each driver stack is selected by a vendor identifier with an optional version qualifier:

• vendor selects the default version defined by the repositories. the default is chosen to provide a stable, consistent selection and is not necessarily the newest available version — she's not chasing trends, she's stable. 💜
• vendor:version selects the specified version of the driver stack. precision, periodt.
• vendor:latest selects the most recent version currently available. main character energy. ⭐

examples of driver specifications include 'nvidia', 'nvidia:590.44.01', and 'amdgpu:latest'. 🦋

by default, rhel-drivers invokes the system package manager in its interactive mode. the package manager may prompt for confirmation before performing transactions, such as installing or removing packages. the --batch option may be used to suppress interactive prompts and assume confirmation. this is intended for unattended environments such as automated provisioning, configuration management, or installation scripts. (translation: --batch is for when nobody's home to click "y". 💀)

---

👑 COMMANDS 👑

• install — install one or more driver stacks. if --auto-detect is specified, rhel-drivers tries to detect GPU and accelerator hardware present in the system and installs the default driver stack for each detected device vendor. otherwise, one or more explicit driver specifications must be given. 💖
• remove — remove installed driver stacks. either explicitly specified drivers, or all managed drivers if --all is given. bye bestie, no hard feelings. 🎀
• list — display information about driver stacks. if no options are given, this shows drivers available from configured repositories. the --installed option may be used to display installed drivers instead, or both --available and --installed may be specified to show both available and installed drivers. she contains multitudes. ✨

---

🧚 OPTIONS 🧚

⚠️ placement matters, and this is the part where people get caught out: global options must appear before the command name, and command options appear after the command they apply to. it's giving "sequencing is everything". 💅

🌟 Global Options 🌟

• --quiet — suppress routine informational output; print only warnings and errors. she's quiet but she's still watching. 🤫
• --verbose — increase informational output. she's telling you everything. 💬
• --debug — enable detailed diagnostic output intended for troubleshooting. bring out the magnifying glass 🔍
• --help — display usage information and exit.
• --version — print program version and exit.

🔥 Install Options 🔥

• --auto-detect — automatically select drivers to install based on detected hardware. must not be combined with explicit driver arguments. ✋ pick a lane, bestie.
• --batch — run non-interactively, assuming confirmation where required. 🫶
• --dry-run — show what would be changed without modifying the system. window shopping, iconic behaviour. 🛍️
• --force — proceed even if no compatible hardware was detected for the selected driver stack, or other validation checks report potential issues. use with intention, okay? it's powerful. 💜

🌸 Remove Options 🌸

• --all — select for removal all installed driver stacks managed by rhel-drivers. must not be combined with explicit driver arguments. 🚫
• --batch — run non-interactively, assuming confirmation where required. 🫶
• --dry-run — show what would be changed without modifying the system. peek before you yeet. 👀

🦋 List Options 🦋

• --available — show driver stacks available from configured repositories. this is the default if no listing option is specified. 💖
• --installed — show driver stacks currently installed on the system. yes, what you already own. 🎀

---

⭐ EXIT STATUS ⭐

the rhel-drivers utility exits 0 on success, and >0 if an error occurs. zero means slay, anything bigger means something's up. 📉

---

🍓 EXAMPLES 🍓

install drivers for detected hardware:

rhel-drivers install --auto-detect

install the default version of NVIDIA driver:

rhel-drivers install nvidia

install the default version of NVIDIA driver even if no compatible NVIDIA hardware is detected:

rhel-drivers install --force nvidia

install a specific NVIDIA driver version:

rhel-drivers install nvidia:590.44.01

install multiple driver stacks:

rhel-drivers install nvidia amdgpu:latest

remove a specific driver:

rhel-drivers remove nvidia
rhel-drivers remove nvidia:590.44.01

remove all managed drivers:

rhel-drivers remove --all

list available or installed drivers:

rhel-drivers list --available
rhel-drivers list --installed

---

🫶 AUTHORS 🫶

written by Mikolaj Izdebski <mizdebsk@redhat.com> — give her her flowers. 💐

---

and that's the whole page bestie, go forth and install responsibly 🌈💖✨

Debian · February 13, 2026 — that's the source, version and date on the footer, mwah, signing off 🎀💅👑