第一步：启用 RPM Fusion 仓库

RPM Fusion 提供了 Fedora 官方不包含的软件包，包括 NVIDIA 专有驱动。

# 启用 free 和 nonfree 仓库
sudo dnf install -y https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
sudo dnf install -y https://mirrors.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm
# 更新包列表
sudo dnf makecache

第二步：安装 NVIDIA 驱动

P104-100 属于 Pascal 架构，支持较新的驱动版本。推荐安装 nvidia-driver 包（自动选择合适版本）。

第三步：禁用 Nouveau 开源驱动（关键步骤）

Fedora 默认使用开源的 nouveau 驱动，必须禁用，否则会与专有驱动冲突。

# 创建黑名单配置文件
echo "blacklist nouveau" | sudo tee /etc/modprobe.d/blacklist-nouveau.conf
echo "options nouveau modeset=0" | sudo tee -a /etc/modprobe.d/blacklist-nouveau.conf
# 重新生成 initramfs（移除 nouveau 模块）
sudo dracut --force

20250917 1413

第四步：重启系统

sudo reboot ...

以下是在 Fedora 42 上安装 NVIDIA P104 - 100 显卡驱动的一种较为简单的方法记录：

步骤一：准备工作

1. 更新系统： 在终端中运行以下命令，确保系统软件包是最新的。

sudo dnf update -y

1. 禁用 Nouveau 驱动： Nouveau 是开源的 NVIDIA 驱动，与官方闭源驱动可能存在冲突，需要先禁用它。

编辑 /etc/default/grub 文件：

sudo nano /etc/default/grub

在 GRUB_CMDLINE_LINUX 行中添加 rd.driver.blacklist=nouveau nouveau.modeset=0，例如：

GRUB_CMDLINE_LINUX="rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet rd.driver.blacklist=nouveau nouveau.modeset=0"

保存并退出 nano 编辑器（按 Ctrl + X，然后按 Y 确认保存，再按回车键）。

更新 GRUB 配置：

sudo grub2 - mkconfig - o /boot/grub2/grub.cfg

步骤二：安装驱动

1. 添加 RPM Fusion 仓库： RPM Fusion 提供了一些 Fedora 官方仓库中没有的软件包，包括 NVIDIA 官方驱动。 运行以下命令启用 RPM Fusion 的非自由和免费仓库：

sudo dnf install https://download1.rpmfusion.org/free/fedora/rpmfus... -E %fedora).noarch.rpm https://download1.rpmfusion.org/nonfree/fedora/rpm... -E %fedora).noarch.rpm

1. 安装驱动： 可以使用 dnf 命令直接搜索并安装适用于 NVIDIA P104 - 100 的驱动程序。由于 P104 - 100 属于较老的显卡型号，可能需要安装较旧版本的驱动。 首先，查找可用的 NVIDIA 驱动版本：

sudo dnf search nvidia - driver

然后，根据搜索结果选择合适的驱动版本进行安装，例如：...

journalctl -u NetworkManager.service

查看网络日志,看到有

Cannot pre-load keyfile (/home/vincent/.cert/nm-openvpn/v-tls-crypt.pem)

Exiting due to fatal error

谷歌搜到结果是https://ciko.io/posts/openvpn_issues/

# journalctl -u NetworkManager
nm-openvpn\[19642\]: Cannot pre-load keyfile (/home/user/.vpn/tlscrypt.pem

The problem for me was thatSELinuxdenied openvpn access to the key file. You can check all SELinux denials by runningausearch -m avc. By runningsetenforce 0, SELinux can be disabled temporarily. As a permanent fix, add an allow rule to SELinux as described inthis post....

journalctl -u NetworkManager.service

Cannot pre-load keyfile (/home/vincent/.cert/nm-openvpn/v-tls-crypt.pem)

Sep 20 03:32:26 Elive-7897 nm-openvpn[35213]: Exiting due to fatal error

ep 20 03:30:32 Elive-7897 NetworkManager[11150]:   [1758310232.2881] device (enp3s0): state change: ip-config -> ip-check (reason 'none',>
Sep 20 03:30:32 Elive-7897 NetworkManager[11150]:   [1758310232.2896] device (enp3s0): state change: ip-check -> secondaries (reason 'none>
Sep 20 03:30:32 Elive-7897 NetworkManager[11150]:   [1758310232.2897] device (enp3s0): state change: secondaries -> activated (reason 'non>
Sep 20 03:30:32 Elive-7897 NetworkManager[11150]:   [1758310232.2900] manager: NetworkManager state is now CONNECTED_SITE
Sep 20 03:30:32 Elive-7897 NetworkManager[11150]:   [1758310232.2903] device (enp3s0): Activation: successful, device activated.
Sep 20 03:30:32 Elive-7897 NetworkManager[11150]:   [1758310232.2908] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 20 03:30:32 Elive-7897 NetworkManager[11150]:   [1758310232.2910] manager: startup complete
Sep 20 03:32:19 Elive-7897 NetworkManager[11150]:   [1758310339.2961] agent-manager: agent[0a37ccea101f695d,:1.180/org.freedesktop.nm-appl>
Sep 20 03:32:26 Elive-7897 NetworkManager[11150]:   [1758310346.1008] vpn[0x5630755f6100,f6819905-08f9-4cea-9c6e-3658ca043f85,"v"]: starti>
Sep 20 03:32:26 Elive-7897 NetworkManager[11150]:   [1758310346.1011] audit: op="connection-activate" uuid="f6819905-08f9-4cea-9c6e-3658ca>
Sep 20 03:32:26 Elive-7897 nm-openvpn[35213]: Cannot pre-load keyfile (/home/vincent/.cert/nm-openvpn/v-tls-crypt.pem)
Sep 20 03:32:26 Elive-7897 nm-openvpn[35213]: Exiting due to fatal error
Sep 20 03:32:26 Elive-7897 NetworkManager[11150]:   [1758310346.2106] vpn[0x5630755f6100,f6819905-08f9-4cea-9c6e-3658ca043f85,"v"]: dbus: >
Sep 20 03:32:26 Elive-7897 NetworkManager[11150]:   [1758310346.2107] vpn[0x5630755f6100,f6819905-08f9-4cea-9c6e-3658ca043f85,"v"]: dbus: >
Sep 20 03:49:06 Elive-7897 NetworkManager[11150]:   [1758311346.8902] manager: (singbox_tun): new Tun device (/org/freedesktop/NetworkMana>
Sep 20 03:49:06 Elive-7897 NetworkManager[11150]:   [1758311346.9317] device (singbox_tun): state change: unmanaged -> unavailable (reason>
Sep 20 03:49:06 Elive-7897 NetworkManager[11150]:   [1758311346.9321] device (singbox_tun): state change: unavailable -> disconnected (rea>
Sep 20 03:49:06 Elive-7897 NetworkManager[11150]:   [1758311346.9325] device (singbox_tun): Activation: starting connection 'singbox_tun' >
Sep 20 03:49:06 Elive-7897 NetworkManager[11150]:   [1758311346.9325] device (singbox_tun): state change: disconnected -> prepare (reason >
Sep 20 03:49:06 Elive-7897 NetworkManager[11150]:   [1758311346.9327] device (singbox_tun): state change: prepare -> config (reason 'none'>
Sep 20 03:49:06 Elive-7897 NetworkManager[11150]:   [1758311346.9328] device (singbox_tun): state change: config -> ip-config (reason 'non>
Sep 20 03:49:06 Elive-7897 NetworkManager[11150]:   [1758311346.9329] device (singbox_tun): state change: ip-config -> ip-check (reason 'n>
Sep 20 03:49:06 Elive-7897 NetworkManager[11150]:   [1758311346.9772] device (singbox_tun): state change: ip-check -> secondaries (reason >
Sep 20 03:49:06 Elive-7897 NetworkManager[11150]:   [1758311346.9774] device (singbox_tun): state change: secondaries -> activated (reason>
Sep 20 03:49:06 Elive-7897 NetworkManager[11150]:   [1758311346.9777] device (singbox_tun): Activation: successful, device activated.

20250920 0430 ...