Enable repositories
Customers enable Partner Repositories content on a registered RHEL system, then install packages with DNF. For NVIDIA drivers on RHEL 9.8 or RHEL 10.2 previously delivered through Extensions or Supplementary, see Partner repository migration.
Until subscription-manager lists these repositories natively, create a dedicated repository file under /etc/yum.repos.d/. Do not edit redhat.repo by hand — subscription-manager may overwrite it.
Prerequisites
- The system is registered with Red Hat (
subscription-manager status). - You have the repository base URL for the required content, architecture, and RHEL release.
- You can locate entitlement certificates under
/etc/pki/entitlement/.
Example repository file
Replace certificate paths and confirm the baseurl for your architecture and stream. Save as a file such as /etc/yum.repos.d/partner-nvidia-cuda.repo:
[partner-nvidia-cuda-rhel10-x86_64]
name=NVIDIA CUDA (Partner Repositories)
baseurl=https://packages.redhat.com/partner-repositories/@partner-repos-nvidia-rm/cuda-monorepo-rhel-10-candidate/custom-1-x86_64/
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-partner-nvidia-cuda-1
sslverify=1
sslcacert=/etc/rhsm/ca/redhat-uep.pem
sslclientcert=/etc/pki/entitlement/REPLACE.pem
sslclientkey=/etc/pki/entitlement/REPLACE-key.pem
Finding entitlement certificates:
ls /etc/pki/entitlement/*.pem | grep -v key
Use the matching *-key.pem beside the client certificate you select.
Install packages
sudo dnf makecache
sudo dnf install <package-name>
Package verification
Import the partner public key from the GPG keys page (one key per partner or product), then verify packages with rpm --checksig. See that page for downloadable key files and fingerprints.
Note
Exact repository identifiers and entitlement mapping will be finalized with customer access. Treat example paths as illustrative until general availability.