Rocky-Scripts is a set of bash scripts that turn a fresh Rocky Linux install into a usable NVIDIA workstation: drivers, then KDE Plasma or GNOME, without retyping the same CRB / EPEL / RPM Fusion / DKMS novel every time. The current target in the repo is Rocky Linux 10.2, installed as Server without GUI. You boot to a TTY on purpose, clone the repo, and run one script.
I am not liable for data loss. Take backups before you let a script own dnf and your kernel modules. Read the NVIDIA section below before you pick a script — Turing-and-newer versus Pascal is not a taste preference, it is which driver package exists.
Why it exists
Rocky is the RHEL-like desktop I still recommend when someone wants an el-style workstation: long support, familiar dnf, NVIDIA that is not a random AUR snapshot. The pain is not Anaconda. The pain is everything after: enable repos, blacklist nouveau, get a module that matches the card, then install a desktop and SDDM/GDM so you are not stuck on a TTY forever.
Doing that by hand is a teaching video. Doing it the second time on a spare machine is what scripts are for. The Rocky 9.3 install guide on this site is the old, expanded, do-it-yourself path (Server, KDE, NVIDIA, Resolve, VMware, Brave, OBS). It is still there because people land on the 9.3 video. New boxes should use this repo, not the 9.3 command list.
NVIDIA: which script family
NVIDIA split driver support around the GSP (GPU System Processor).
Modern (nvidia-open) — what the main production scripts use. Tested on a 5060 Ti. Architectures: Blackwell (RTX 50), Ada (40), Ampere (30), Turing (20-series / GTX 16).
Legacy (cuda-drivers) — older cards without the open module: Volta, Pascal (GTX 10), Maxwell (GTX 9). These scripts are labeled Legacy and are experimental. A tester found the legacy path needs the -580 driver line to work properly. If you have that hardware and can test, say so on socials; I cannot own every generation of card in the lab.
Wrong family = black screen or a module that never builds. Check the GPU generation before you chmod +x.
How to try it
- Download the Rocky Linux 10.2 DVD ISO from the official download page.
- In Anaconda, Software Selection: Server (without GUI). If you install a desktop from the installer, you are not on the path these scripts expect.
- Reboot to the TTY, log in, then:
sudo dnf install git -y
git clone https://github.com/TheLinuxITGuy/Rocky-Scripts.git && cd Rocky-Scripts
chmod u+x *.sh
./"KDE - NVIDIA Install.sh"Use the GNOME-named script instead if you want GNOME. Use the Legacy script only if your GPU is in the older list above.
- Let it run. Reboot when it tells you. Confirm
nvidia-smibefore you celebrate. Then install Resolve / OBS / browsers the way you usually do — the script’s job is drivers + desktop, not your entire app list.
Video for the current Rocky 10 + NVIDIA path: YouTube walkthrough. If the README and this page disagree after a repo bump, believe the README.
How it fits the rest of the site
- Historical 9.3 by-hand: The Ultimate Rocky Linux Install Guide
- Arch/Omarchy NVIDIA and Resolve: Arch workstation, Resolve on Omarchy
- “I wanted a friendlier desktop than el9”: Mint 22.3 vs Fedora 44
Homelab DNS still belongs on CoreOS, not on the Rocky workstation you just put KDE on.
What this is not
Not a Kickstart for a 200-node fleet. Not Fedora, not Alma’s installer, not a Secure Boot signing service. Scripts assume you can get to a TTY as a user with sudo. They will not save a forgotten Anaconda disk layout.