Persistent Black Screen / GUI Initialization Failure after NVIDIA v580+ Installation on Fedora 43 (KDE)

I am experiencing a persistent Black Screen of Death (BSOD) immediately after installing the NVIDIA proprietary drivers (v580+) via RPM Fusion. The system completely fails to load the Graphical User Interface (GUI) and hangs during the display server initialization. Initial Fedora Install: During the initial Fedora 43 installation, the standard “Try Fedora” option in GRUB resulted in a black screen. I had to use the “Troubleshooting” (basic graphics) option to successfully complete the installation. Cross-Distribution Issue: Initially, I suspected this might be a Fedora-specific bug. However, when I attempted to install the CachyOS LTS release as an alternative, I encountered the exact same installation and post-installation black screen issue. Access: Successfully accessed the system via TTY (Runlevel 3) using the nomodeset 3 kernel parameter. Driver Status: Verified the driver status using nvidia-smi. The table reports correctly and detects the GPU, indicating the driver is loaded and functioning at the system level, but the GUI fails to render. Attempted Fixes: * Re-generated the initramfs using dracut. Forced SDDM to use X11 instead of Wayland. Current State: Despite these steps, the system remains stuck in a persistent login-loop/black-screen state upon regular boot.

System Specifications: Laptop Model: HP Victus 16-s0051nt (892P9EA) CPU: AMD Ryzen 7 7840HS (with Radeon 780M Integrated Graphics) GPU: NVIDIA GeForce RTX 4050 Laptop GPU (6GB) - Hybrid Graphics Setup

Additional info is always required.
This would be a good start.

As well as the very first topic under *Start Here at the beginning page when first connecting to this forum.

1 Like

The result I got with inxi -Fzxx is as follows.

inxi -Fzxx result:
System:
Kernel: 6.19.7-288.fc43.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
Machine:
Console: tty 1 DM: SDDM Distro: Fedora Linux 43 (KDE Plasma Desktop Edition)
Type: Laptop System: HP product: Victus by HP Gaming Laptop : Type1ProductConfig Id serial: <superuser required> Chassis: type: 18 serial: <superuser required>
Mobo: HP model: 8BD4 : 79.57 serial: <superuser required> part-nu: 892P9EA#ABB Firmware: UEFI
vendor: Insyde v: F.38 date: 87/10/2025
Battery:
ID-1: BAT1 charge: 62.5 Wh (100%) condition: 62.5/83 Wh (75.3%) volts: 12.63 min: 11.58
model: Hewlett-Packard PABAS8241231 serial: <filter> charging: status: full cycles: N/A
CPU:
Info: 8-core model: AMD Ryzen 7 7816HS w Radeon 780M Graphics bits: 64 type: MT MCP arch: Zen 4
rev: 1 cache: L1: 512 KiB L2: 8 MiB L3: 16 MIB
Speed (MHz): aug: 1181 min/max: 419/5138 boost: enabled cores: 1: 1101 2: 1181 3: 1181 4: 1181 5: 1101 6: 1181 7: 1181 8: 1181 9: 1101 18: 1181 11: 1101 12: 1101 13: 1181 14: 1181 15: 1101
16: 1181 bogomips: 121360
Flags-basic: aux avx2 ht Im nx pae sse sse2 sse3 sse4_1 sse4_2 ssela ssse3 sum
Graphics:
Device-1: NUIDIA AD107M [GeForce RTX 1050 Max-Q Mobile] vendor: Hewlett-Packard driver: nuidia v: 595.45.84 arch: Lovelace pcie: speed: 2.5 GT/s lanes: 8 ports: active: HDMI-A-1 empty: none
bus-ID: 01:08.8 chip-ID: 10de: 28a1
Device-2: Advanced Micro Devices [AMD/ATI] Phoenixi vendor: Hewlett-Packard driver: N/A arch: RDNA-3 pcie: speed: 16 GT/s lanes: 16 bus-ID: 05:08.0 chip-ID: 1002: 15bf
Device-3: Quanta HP True Vision FHD Camera driver: uvcvideo type: USB rev: 2.8 speed: 488 Mb/s
lanes: 1 bus-ID: 3-1:2 chip-1D: 0488:5487
Display: unspecified server: X.org : 1.21.1.21 with: Xwayland v: 24.1.9 driver: X:
loaded: modesetting, nvidia alternate: fbdev, nouveau, no, vesa dri: radeonsi
gpu: nvidia, nvidia-nuswitch tty: 240x67
Monitor-1: HDMI-A-1 model: GRUNDIG TU res: 1920x1080 dpi: 48 diag: 1388mm (54.6")
Monitor-2: Unknown-1 size-res: N/A in console
API: EGL v: 1.5 platforms: device: 0 drv: nuidia device: 2 drv: surast gbm: drv: nvidia surfaceless: dro: nuidia inactive wayland, x11, device-1
API: OpenGL: 4.6.0 compat-v: 4.5 vendor: mesa v: 25.3.6 note: console (EGL sourced) renderer: NVIDIA GeForce RTX 4050 Laptop GPU/PCIe/SSE2, 11ompipe (LLUM 21.1.8 256 bits)
API: Vulkan : 1.4.341 surfaces: N/A device: 8 type: discrete-gpu driver: nuidia device-ID: 10de: 28a1 device: 1 type: cpu driver: mesa llumpipe device-ID: 10005:0000 Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console, kscreen-doctor
gpu: noidia-settings,noidia-smi wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
Device-1: NVIDIA AD187 High Definition Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 8 bus-ID: 01:00.1 chip-ID: 10de: 22be
Device-2: Advanced Micro Devices [AMD/ATI Radeon High Definition Audio
vendor: Hewlett-Packard driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
bus-ID: 05:00.1 chip-ID: 1002:1640
Device-3: Advanced Micro Devices [AMD] Audio Coprocessor vendor: Hewlett-Packard driver: and pci_ps v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 85:88.5 chip-ID: 1022:15e2
Device-4: Advanced Micro Devices [AMD] Ryzen HD Audio vendor: Hewlett-Packard
driver: snd hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 05:00.6
chip-ID: 1822:15e3
API: ALSA v: k6.19.7-288.fc43.x86_64 status: kernel-api
Server-1: PipeWire v: 1.4.18 status: off with: 1: pipewire-pulse status: off 2: wireplumber
Network:
status: off 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
Device-1: MEDIATEK MT7921 882.11ax PCIe Wireless Network Adapter (Filogic 3381 vendor: Azurellave driver: mt7921e v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 82:00.0 chip-ID: 14c3:7961 IF: wlol state: doum mac: <filter>
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard
driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 2008 bus-ID: 83:00.0
chip-ID: 18ec: 8168
IF: enol state: up speed: 100 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: IMC Networks Wireless Device driver: btusb v: 8.8 type: USB rev: 2.1 speed: 488 Mb/s
Janes: 1 bus-ID: 1-5:2 chip-ID: 1343:3567
Report: btmgmt ID: hcio rfk-id: 0 state: up address: <filter> bt-v: 5.3 Imp-v: 12
Drives:
Local Storage: total: 953.87 GiB used: 7.02 GiB (0.7%)
ID-1: /dev/nomeni vendor: Samsung model: MZJL21T@HDLU-00BH1 size: 953.87 GiB speed: 63.2 Gb/s
lanes: 4 serial: <filter> temp: 26.9 C
Partition:
ID-1:/ size: 198 GiB used: 6.48 GiB (3.3%) fs: btrfs dev: /dev/ηυηεθη1p6
ID-2: /boot size: 1.9 GiB used: 470.9 MiB (24.2%) fs: ext4 dev: /dev/nume0n1p4 ID-3: /boot/efi size: 196 MiB used: 83.9 MiB (42.8%) fs: ufat dev: /dev/numeon1p1
ID-4: /home size: 198 GiB used: 6.48 G1B (3.3%) fs: btrfs dev: /dev/nume@n1p6
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 8 KiB (0.0%) priority: 100 dev: /dev/zram
Sensors:
System Temperatures: cpu: 33.2 C mobo: 29.8 C gpu: nvidia temp: 34 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GIB note: est. available: 14.89 GiB used: 1.26 GiB (8.5%)
Processes: 311 Power: uptime: 4m wakeups: 8 Init: systemd v: 258 default: graphical Packages: pm: rpm pkgs: N/A note: see-rpm Compilers: gcc: 15.2.1 Shell: Bash v: 5.3.0 rumming-in: tty 1 inxi: 3.3.40

I apologize for the mistake in my forum post. I was in a bit of a panic and rushed after struggling with this issue for long hours. Have a great day.

NUIDIA looks a bit strange :slight_smile:

Have you used OCR to capture this output from a screen?

A more convenient way of sharing data between devices is:

inxi -Fzxx | fpaste

That will upload the data to a CentOS pastebin and give you a URL, so you can go to that URL on another device and get the text output.

1 Like

Thank you for the additional info.

That definitely looks strange.

  1. nuidia vs nvidia
  2. Version 595.45.84 is not yet released for fedora AFAIK. The latest in the rpmfusion repos is 580.126.18 with 580.142 soon to be released (not yet in the rpmfusion testing repo).

I do see that the 595.45.04 version of akmod-nvidia is available in the rpmfusion testing repo for f44, but not for f43.

I am guessing that you installed the driver from some other location and to confirm please post the output of dnf list --installed \*nvidia\* by copy and paste. Make it appear exactly as seen on screen (preformatted text) by placing a [ ``` ] on the line immediately before you paste the text then also on the line following the pasted text. (Or by highlighting the text after it is pasted then click the </> button on the toolbar)

After pulling the NVIDIA driver from the RPM repository and still getting the same black screen error, I added the repo from https://developer.download.nvidia.com/compute/cuda/repos/fedora43/x86_64/cuda-fedora43.repo and installed the packages from there. Installed packages:

kmod-nvidia-latest-dkms.x86_64 3:595.45.04-1.fc43 cuda-fedora43-x86_64
libnvidia-cfg.x86_64           3:595.45.04-1.fc43 cuda-fedora43-x86_64
libnvidia-fbc.x86_64           3:595.45.04-1.fc43 cuda-fedora43-x86_64
libnvidia-gpucomp.x86_64       3:595.45.04-1.fc43 cuda-fedora43-x86_64
libnvidia-ml.x86_64            3:595.45.04-1.fc43 cuda-fedora43-x86_64
nvidia-driver.x86_64           3:595.45.04-1.fc43 cuda-fedora43-x86_64
nvidia-driver-cuda.x86_64      3:595.45.04-1.fc43 cuda-fedora43-x86_64
nvidia-driver-cuda-libs.x86_64 3:595.45.04-1.fc43 cuda-fedora43-x86_64
nvidia-driver-libs.x86_64      3:595.45.04-1.fc43 cuda-fedora43-x86_64
nvidia-kmod-common.noarch      3:595.45.04-1.fc43 cuda-fedora43-x86_64
nvidia-libXNVCtrl.x86_64       3:595.45.04-1.fc43 cuda-fedora43-x86_64
nvidia-modprobe.x86_64         3:595.45.04-1.fc43 cuda-fedora43-x86_64
nvidia-persistenced.x86_64     3:595.45.04-1.fc43 cuda-fedora43-x86_64
nvidia-settings.x86_64         3:595.45.04-1.fc43 cuda-fedora43-x86_64
xorg-x11-nvidia.x86_64         3:595.45.04-1.fc43 cuda-fedora43-x86_64

Additionally, I used OCR to obtain the inxi output here is the corrected result:

System:
  Host: 192.168.1.42 Kernel: 6.19.7-200.fc43.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
  Console: tty 1 DM: SDDM Distro: Fedora Linux 43 (KDE Plasma Desktop Edition)
Machine:
  Type: Laptop System: HP product: Victus by HP Gaming Laptop v: Type1ProductConfigId
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: HP model: 8BD4 v: 79.57 serial: <superuser required> part-nu: 892P9EA#AB8 Firmware: UEFI
    vendor: Insyde v: F.30 date: 07/10/2025
Battery:
  ID-1: BAT1 charge: 62.5 Wh (100%) condition: 62.5/83 Wh (75.3%) volts: 12.62 min: 11.58
    model: Hewlett-Packard PABAS0241231 serial: 41167 charging: status: full cycles: N/A
CPU:
  Info: 8-core model: AMD Ryzen 7 7840HS w/ Radeon 780M Graphics bits: 64 type: MT MCP arch: Zen 4
    rev: 1 cache: L1: 512 KiB L2: 8 MiB L3: 16 MiB
  Speed (MHz): avg: 1101 min/max: 419/5138 boost: enabled cores: 1: 1101 2: 1101 3: 1101 4: 1101
    5: 1101 6: 1101 7: 1101 8: 1101 9: 1101 10: 1101 11: 1101 12: 1101 13: 1101 14: 1101 15: 1101
    16: 1101 bogomips: 121372
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Phoenix1 vendor: Hewlett-Packard driver: N/A
    arch: RDNA-3 pcie: speed: 16 GT/s lanes: 16 bus-ID: 05:00.0 chip-ID: 1002:15bf
  Device-2: Quanta HP True Vision FHD Camera driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s
    lanes: 1 bus-ID: 3-1:2 chip-ID: 0408:5487
  Display: unspecified server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9 driver: X:
    loaded: modesetting,nvidia alternate: fbdev,nouveau,nv,vesa dri: radeonsi gpu: N/A tty: 240x67
  Monitor-1: Unknown-1 size-res: N/A in console
  API: EGL v: 1.5 platforms: device: 0 drv: swrast surfaceless: drv: swrast
    inactive: gbm,wayland,x11
  API: OpenGL v: 4.5 vendor: mesa v: 25.3.6 note: console (EGL sourced) renderer: llvmpipe
    (LLVM 21.1.8 256 bits)
  API: Vulkan v: 1.4.341 surfaces: N/A device: 0 type: cpu driver: mesa llvmpipe
    device-ID: 10005:0000
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
    gpu: nvidia-settings,nvidia-smi wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Radeon High Definition Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 05:00.1
    chip-ID: 1002:1640
  Device-2: Advanced Micro Devices [AMD] Audio Coprocessor vendor: Hewlett-Packard
    driver: snd_pci_ps v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 05:00.5 chip-ID: 1022:15e2
  Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 05:00.6
    chip-ID: 1022:15e3
  API: ALSA v: k6.19.7-200.fc43.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.4.10 status: off with: 1: pipewire-pulse status: off 2: wireplumber
    status: off 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
Network:
  Device-1: MEDIATEK MT7921 802.11ax PCIe Wireless Network Adapter [Filogic 330] vendor: AzureWave
    driver: mt7921e v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 14c3:7961
  IF: wlo1 state: down mac: 12:a5:35:fd:77:80
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard
    driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 03:00.0
    chip-ID: 10ec:8168
  IF: eno1 state: up speed: 100 Mbps duplex: full mac: bc:0f:f3:60:09:4f
Bluetooth:
  Device-1: IMC Networks Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1 speed: 480 Mb/s
    lanes: 1 bus-ID: 1-5:2 chip-ID: 13d3:3567
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: 10:68:38:40:11:4C bt-v: 5.3 lmp-v: 12
Drives:
  Local Storage: total: 953.87 GiB used: 7.02 GiB (0.7%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVL21T0HDLU-00BH1 size: 953.87 GiB speed: 63.2 Gb/s
    lanes: 4 serial: S6Z3NE0W401396 temp: 36.9 C
Partition:
  ID-1: / size: 198 GiB used: 6.48 GiB (3.3%) fs: btrfs dev: /dev/nvme0n1p6
  ID-2: /boot size: 1.9 GiB used: 470.9 MiB (24.2%) fs: ext4 dev: /dev/nvme0n1p4
  ID-3: /boot/efi size: 196 MiB used: 83.9 MiB (42.8%) fs: vfat dev: /dev/nvme0n1p1
  ID-4: /home size: 198 GiB used: 6.48 GiB (3.3%) fs: btrfs dev: /dev/nvme0n1p6
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 41.5 C mobo: 41.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB note: est. available: 14.89 GiB used: 935.6 MiB (6.1%)
  Processes: 294 Power: uptime: 2m wakeups: 0 Init: systemd v: 258 default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm Compilers: gcc: 15.2.1 Shell: Bash v: 5.3.0
    running-in: tty 1 inxi: 3.3.40

If you search back on the forum about f43 and black screen issues you will find 2 possible recommendations for fixes (which works seems to depend upon hardware.)

This only applies when using the rpmfusion repo to install the nvidia driver AFAIK.

One is to add nomodeset to the kernel command line during boot and the other is to remove rhgb from the kernel command line.

Editing the kernel command line during boot is simply done by holding down the shift key during boot so the grub menu displays. Once the menu is seen then press e (for edit) and on the line that begins with linux either add or remove the option noted. Continuing boot will show if that attempt succeeded or failed.

If it succeeds then a permanent change can be done with a simple command.
sudo grubby --update-kernel=ALL --remove-args="rhgb" to remove the option
or
sudo grubby --update-kernel=ALL --args="nomodeset" to add the option

Many users have seen problems with using nvidia drivers from the nvidia sites, including all the cuda-fedoraXX-x86_64 repos. Those same drivers are tweaked and tested on fedora before release when installed from rpmfusion.

1 Like

I have successfully removed the previous NVIDIA drivers and installed the RPM Fusion version (580.126.18). However, the issue persists. I can only access the desktop by using the nomodeset kernel parameter. When I boot with nomodeset, my screen brightness is stuck at a low level and I cannot change the refresh rate (Hz). The main reason I’m trying to install these drivers is to fix these display issues and get full hardware acceleration. journalctl shows that the driver is initialized, but I get the error: [drm] Cannot find any crtc or sizes. I can only reach the desktop using nomodeset, which disables the driver’s features.

Is the driver actually loading?
Please post the output of lsmod | grep -E "nvidia|nouveau" after booting with “nomodeset”

Have you tried removing the ‘rhgb’ ?

Also please provide a new result of running dnf list --installed \*nvidia\* as well as sudo dmesg | grep -iE "nouveau|nvidia"

Output of lsmod | grep -E "nvidia|nouveau":

nvidia_uvm           4210688  0
nvidia_drm            159744  55
nvidia_modeset       2265088  5 nvidia_drm
nvidia              15896576  258 nvidia_uvm,nvidia_modeset
drm_ttm_helper         20480  2 amdgpu,nvidia_drm
video                  81920  2 amdgpu,nvidia_modeset
 

Output of dnf list --installed *nvidia*:

Kurulu paketler
akmod-nvidia.x86_64                       3:580.126.18-1.fc43 rpmfusion-nonfree-nvidia-driver
kmod-nvidia-6.19.8-200.fc43.x86_64.x86_64 3:580.126.18-1.fc43 @commandline
libva-nvidia-driver.x86_64                0.0.16-1.fc43       updates
nvidia-modprobe.x86_64                    3:580.126.18-1.fc43 rpmfusion-nonfree-nvidia-driver
nvidia-persistenced.x86_64                3:580.126.18-1.fc43 rpmfusion-nonfree-nvidia-driver
nvidia-settings.x86_64                    3:580.126.18-1.fc43 rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia.x86_64                3:580.126.18-1.fc43 rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-cuda.x86_64           3:580.126.18-1.fc43 rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-cuda-libs.x86_64      3:580.126.18-1.fc43 rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-kmodsrc.x86_64        3:580.126.18-1.fc43 rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-libs.x86_64           3:580.126.18-1.fc43 rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-power.x86_64          3:580.126.18-1.fc43 rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-xorg-libs.x86_64      3:580.126.18-1.fc43 rpmfusion-nonfree-nvidia-driver 

Output of dmesg | grep -iE "nouveau|nvidia":

[    0.000000] Command line: BOOT_IMAGE=(hd0,gpt4)/vmlinuz-6.19.8-200.fc43.x86_64 root=UUID=6ea97b7d-6bd0-449c-9e00-40c624b38ab6 ro rootflags=subvol=root quiet splash rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 nomodeset
[    0.025712] Kernel command line: BOOT_IMAGE=(hd0,gpt4)/vmlinuz-6.19.8-200.fc43.x86_64 root=UUID=6ea97b7d-6bd0-449c-9e00-40c624b38ab6 ro rootflags=subvol=root quiet splash rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 nomodeset
[    4.857792] nvidia: loading out-of-tree module taints kernel.
[    4.857804] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[    4.981316] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[    4.984710] nvidia 0000:01:00.0: enabling device (0000 -> 0003)
[    4.984931] nvidia 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none
[    5.099977] nvidia-modeset: Loading NVIDIA UNIX Open Kernel Mode Setting Driver for x86_64  580.126.18  Release Build  (dvs-builder@U22-I3-H04-01-6)  Wed Feb 11 18:19:14 UTC 2026
[    5.103432] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[    6.414810] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/0000:01:00.1/sound/card1/input16
[    6.414903] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.1/0000:01:00.1/sound/card1/input17
[    6.414976] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.1/0000:01:00.1/sound/card1/input18
[    6.415046] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.1/0000:01:00.1/sound/card1/input19
[    7.972685] [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 1
[    8.063460] nvidia 0000:01:00.0: [drm] fb1: nvidia-drmdrmfb frame buffer device

I gathered all the diagnostic information above by booting into the system using the nomodeset parameter. Additionally, I am facing an issue where the GRUB loader remains below the ‘Windows Boot Manager’ in the BIOS boot priority. Despite my attempts to change the boot order in the BIOS settings, I haven’t been able to fix it.

I have also noticed a specific behavior with the display: in distributions like Bazzite, when I connect an external monitor, the second screen works perfectly, but the laptop’s primary (internal) screen remains blank/inactive. On my current Fedora installation, the system fails to boot or display anything at all unless I use the nomodeset flag.

Also, yes, I have removed before rhgb. My GRUB configuration is currently: GRUB_CMDLINE_LINUX="quiet splash rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1"

Thank you in advance for your help.

You can remove that from your kernel command line with sudo grubby --update-kernel=ALL --remove-args="nvidia-drm.modeset=1"

That should eliminate the need to use nomodeset. The two options conflict.

The issue with boot order should be able to be resolved in bios. You will have to work on that. Usually by highlighting one of the options you should be able to move it up or down in the listing (often with a + or - key)

Have you tried initializing the amdgpu and nvidia driver at the same time?
ommit amdgpu driver from the initramfs and try starting the system using that initramfs.

i.e

sudo dracut --omit-drivers  amdgpu  /boot/initramfs-$(uname -r)-test.img

restart and change the initrd line in grub accordingly.

1 Like

I was having the same problem as OP. I have similar specs and had similar outcomes when attempting to remove rhgb or add nomodeset, but your solution worked for me. This is my first time posting, so I’m not exactly sure what info would be helpful to other future readers of this thread. Here are my hardware specs, but I’d be happy to upload more context on the specifics of my configuration if it’d be helpful.

important parts of inxi -Fzxx:
CPU:

Info: 8-core model: AMD Ryzen 7 7800X3D bits: 64 type: MT MCP arch: Zen 4 rev: 2 cache:
    L1: 512 KiB L2: 8 MiB L3: 96 MiB
  Speed (MHz): avg: 3585 min/max: 426/5053 boost: enabled cores: 1: 3585 2: 3585 3: 3585 4: 3585
    5: 3585 6: 3585 7: 3585 8: 3585 9: 3585 10: 3585 11: 3585 12: 3585 13: 3585 14: 3585 15: 3585
    16: 3585 bogomips: 134151
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm

Graphics:

Device-1: NVIDIA AD104 [GeForce RTX 4070] vendor: ASUSTeK driver: nouveau v: kernel
    arch: Lovelace pcie: speed: 16 GT/s lanes: 8 ports: active: DP-4,DP-6 empty: DP-5,HDMI-A-2
    bus-ID: 01:00.0 chip-ID: 10de:2786
  Device-2: Advanced Micro Devices [AMD/ATI] Raphael vendor: Gigabyte driver: amdgpu v: kernel
    arch: RDNA-2 pcie: speed: 16 GT/s lanes: 16 ports: active: none empty: DP-1, DP-2, DP-3,
    HDMI-A-1, Writeback-1 bus-ID: 10:00.0 chip-ID: 1002:164e temp: 31.0 C
  Display: unspecified server: Xwayland v: 24.1.9 driver: gpu: nouveau tty: 320x90
  Monitor-1: DP-4 model: VG27AQL1A res: 2560x1440 dpi: 109 diag: 685mm (27")
  Monitor-2: DP-6 model: VG27AQL1A res: 2560x1440 dpi: 109 diag: 685mm (27")
  API: EGL v: 1.5 platforms: device: 0 drv: zink device: 1 drv: radeonsi device: 2 drv: swrast
    gbm: drv: zink surfaceless: drv: zink inactive: wayland,x11
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 25.3.6 note: console (EGL sourced)
    renderer: zink Vulkan 1.4(NVIDIA GeForce RTX 4070 (NVK AD104) (MESA_NVK)), AMD Ryzen 7 7800X3D
    8-Core Processor (radeonsi raphael_mendocino LLVM 21.1.8 DRM 3.64 6.19.8-200.fc43.x86_64),
    llvmpipe (LLVM 21.1.8 256 bits)
  API: Vulkan Message: No Vulkan data available.
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
    gpu: nvidia-settings,nvidia-smi wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr

Output of lsmod | grep -E "nvidia|nouveau", which I believe confirms that the hardware is really using Nvidia drivers:

nvidia_uvm           4210688  0
nvidia_drm            159744  133
nvidia_modeset       2265088  62 nvidia_drm
nvidia              15896576  1174 nvidia_uvm,nvidia_modeset
drm_ttm_helper         20480  3 amdgpu,nvidia_drm
video                  81920  2 amdgpu,nvidia_modeset

Here’s the output of sudo grubby --info=DEFAULT on my system:

index=0
kernel="/boot/vmlinuz-6.19.8-200.fc43.x86_64"
args="ro rootflags=subvol=root rd.luks.uuid=luks-a630f3d7-0887-4b24-bf3f-0240ad831b04 rhgb quiet $tuned_params rd.driver.blacklist=nouveau,nova_core modprobe.blacklist=nouveau,nova_core nvidia.NVreg_EnableGpuFirmware=0"
root="UUID=7012e7cb-9b12-455a-b4aa-816083bb3a98"
initrd="/boot/initramfs-6.19.8-200.fc43.x86_64-test.img $tuned_initrd"
title="Fedora Linux (6.19.8-200.fc43.x86_64) 43 (KDE Plasma Desktop Edition)"
id="473d8e7263d3415ca0c9a200254a1148-6.19.8-200.fc43.x86_64"

Yours should look similar

To make the changes in @anotheruser’s post persistent, you can run:

sudo grubby --update-kernel="vmlinuz-<output of uname -r>" --initrd="/boot/initramfs-<output of uname -r>-test.img $tuned_initrd"
Make sure you’re replacing the values in <output of uname -r> with the actual value you get wehn you run the command uname -r

Edit: Don’t do this ^

please do not change the grub config!
What I meant was to interrupt the boot process at the grub stage and change the name of the initramfs in the grub editor. This is a one time change only to test if this works.

To make the change permanent create a file in /etc/dracut.conf.d/ - the file name is up to you as long as it ends with .conf - with the content

omit_drivers+=" amdgpu "

see man dracut.conf for details.

then run sudo dracut -f to regenerate the initramfs and reboot.
Delete the old test initramfs from /boot .

Oh, good to know! What’s the harm in editing the grub config? Will it break on a kernel update or something?

Also, I’m assuming you mean /etc/dracut.conf.d/ right? I’m not seeing a /etc/dracut.d/. The man page also seems to support that /etc/dracut.conf.d/ is correct (See FILES section).

One more thing, it seems like running sudo dracut -f changes the grub config to initrd=“/boot/initramfs-6.19.8-200.fc43.x86_64.img”. Previously, it ended with “$tuned_initrd” (see previous post), which was a part of the initial configuration after a fresh install with no modification. Do you think that’s something that should be added back? If so, it doesn’t seem like there’s any option other than editing the grub config.

Edit:
Rebooted without issue despite not having the $tuned_initrd in there, so I guess I don’t need it.

That tuning parameter variable is empty unless you shove something in it. Appending a blank variable to a string results in “the string” so the two lines are equivalent for you.

1 Like

it makes no sense to change the default filename of the initramfs.
What would happen when a new kernel get installed. You’d have to manually create the initrams to omit the amdgpu driver again.

yes! It was late and I was tired. UTC+1
Thanks.

Out of interest, The initramfs still has the nouveau driver but not the amdgpu driver.
Try booting with the kernel args “rd.driver.blacklist=nouveau,nova_core modprobe.blacklist=nouveau,nova_core” removed.

I think it’s safe to also omit the nouveau and nova_core driver. This will also reduce the file size of the initramfs files

Is this really required on your system?

not true if you do this

@computersavvy , Context!
try reading between the lines, or please read through the entire thread first before giving in to the urgent temptation to click that Reply button and stating the obvious.

1 Like

You’re definitely right about not needing nvidia.NVreg_EnableGpuFirmware=0. I removed that from the grub config and everything works fine.

Removing “rd.driver.blacklist=nouveau,nova_core modprobe.blacklist=nouveau,nova_core”, however, makes it boot into black screen (after putting creds into the login screen) that I can’t do anything from (not even open up a console with alt+f3). To get some more info about what’s happening, I booted into multi-user mode by appending systemd.unit=multi-user.target to the end of the args in the grub config then ran a few commands.

lsmod | grep -E “nvidia|nouveau”:

nouveau              4005888  0
drm_ttm_helper         20480  3 amdgpu,nouveau
ttm                   135168  3 amdgpu,drm_ttm_helper,nouveau
gpu_sched              69632  2 amdgpu,nouveau
i2c_algo_bit           20480  2 amdgpu,nouveau
drm_gpuvm              57344  1 nouveau
drm_exec               12288  3 drm_gpuvm,amdgpu,nouveau
mxm_wmi                12288  1 nouveau
drm_display_helper    344064  2 amdgpu,nouveau
video                  81920  2 amdgpu,nouveau
wmi                    32768  5 video,gigabyte_wmi,wmi_bmof,mxm_wmi,nouveau

dmesg | grep -IE “nvidia|nouveau”

Output
[    4.993026] nouveau 0000:01:00.0: NVIDIA AD104 (194000a1)
[    5.473858] nouveau 0000:01:00.0: gsp: RM version: 570.144
[    5.562747] nouveau 0000:01:00.0: bios: version 95.04.3e.80.a6
[    5.576030] nouveau 0000:01:00.0: vgaarb: deactivate vga console
[    6.447802] nouveau 0000:01:00.0: drm: VRAM: 12282 MiB
[    6.447807] nouveau 0000:01:00.0: drm: GART: 536870912 MiB
[    6.463867] nouveau 0000:01:00.0: drm: MM: using COPY for buffer copies
[    6.502284] nouveau 0000:01:00.0: [drm] Registered 4 planes with drm panic
[    6.511607] [drm] Initialized nouveau 1.4.1 for 0000:01:00.0 on minor 0
[    6.519080] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[    6.519088] nouveau 0000:01:00.0: [drm] *ERROR* DP-1: invalid native reply 0x03
[    6.536469] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[    6.536476] nouveau 0000:01:00.0: [drm] *ERROR* DP-1: invalid native reply 0x03
[    6.553936] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[    6.553943] nouveau 0000:01:00.0: [drm] *ERROR* DP-1: invalid native reply 0x03
[    6.559618] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[    6.559630] nouveau 0000:01:00.0: [drm] *ERROR* DP-3: invalid native reply 0x03
[    6.577091] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[    6.577098] nouveau 0000:01:00.0: [drm] *ERROR* DP-3: invalid native reply 0x03
[    6.594450] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[    6.594457] nouveau 0000:01:00.0: [drm] *ERROR* DP-3: invalid native reply 0x03
[    6.595786] fbcon: nouveaudrmfb (fb0) is primary device
[    6.692734] nouveau 0000:01:00.0: [drm] fb0: nouveaudrmfb frame buffer device
[    6.715577] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[    6.715580] nouveau 0000:01:00.0: [drm] *ERROR* DP-1: invalid native reply 0x03
[    6.735629] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[    6.735632] nouveau 0000:01:00.0: [drm] *ERROR* DP-1: invalid native reply 0x03
[    6.753110] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[    6.753112] nouveau 0000:01:00.0: [drm] *ERROR* DP-1: invalid native reply 0x03
[    6.760564] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[    6.760566] nouveau 0000:01:00.0: [drm] *ERROR* DP-3: invalid native reply 0x03
[    6.777885] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[    6.777886] nouveau 0000:01:00.0: [drm] *ERROR* DP-3: invalid native reply 0x03
[    6.795326] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[    6.795328] nouveau 0000:01:00.0: [drm] *ERROR* DP-3: invalid native reply 0x03
[    6.896775] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[    6.896779] nouveau 0000:01:00.0: [drm] *ERROR* DP-1: invalid native reply 0x03
[    6.914035] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[    6.914038] nouveau 0000:01:00.0: [drm] *ERROR* DP-1: invalid native reply 0x03
[    6.931238] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[    6.931240] nouveau 0000:01:00.0: [drm] *ERROR* DP-1: invalid native reply 0x03
[    6.936591] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[    6.936594] nouveau 0000:01:00.0: [drm] *ERROR* DP-3: invalid native reply 0x03
[    6.953806] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[    6.953809] nouveau 0000:01:00.0: [drm] *ERROR* DP-3: invalid native reply 0x03
[    6.971212] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[    6.971215] nouveau 0000:01:00.0: [drm] *ERROR* DP-3: invalid native reply 0x03
[   21.665398] nvidia: loading out-of-tree module taints kernel.
[   21.762062] nvidia-nvlink: Nvlink Core is being initialized, major device number 510
[   21.764971] NVRM: GPU 0000:01:00.0 is already bound to nouveau.
[   21.765927] nvidia-nvlink: Unregistered Nvlink Core, major device number 510
[   21.984094] nvidia-nvlink: Nvlink Core is being initialized, major device number 510
[   21.986188] NVRM: GPU 0000:01:00.0 is already bound to nouveau.
[   21.986892] nvidia-nvlink: Unregistered Nvlink Core, major device number 510
[   22.116268] snd_hda_intel 0000:01:00.1: bound 0000:01:00.0 (ops nv50_audio_component_bind_ops [nouveau])
[   24.146901] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[   24.146908] NVRM: GPU 0000:01:00.0 is already bound to nouveau.
[   24.149547] nvidia-nvlink: Unregistered Nvlink Core, major device number 509
[   32.033129] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[   32.033133] nouveau 0000:01:00.0: [drm] *ERROR* DP-1: invalid native reply 0x03
[   32.050803] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[   32.050806] nouveau 0000:01:00.0: [drm] *ERROR* DP-1: invalid native reply 0x03
[   32.068187] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[   32.068189] nouveau 0000:01:00.0: [drm] *ERROR* DP-1: invalid native reply 0x03
[   32.073724] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[   32.073727] nouveau 0000:01:00.0: [drm] *ERROR* DP-3: invalid native reply 0x03
[   32.091263] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[   32.091266] nouveau 0000:01:00.0: [drm] *ERROR* DP-3: invalid native reply 0x03
[   32.108698] nouveau 0000:01:00.0: gsp: cli:0xc1d00001 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[   32.108700] nouveau 0000:01:00.0: [drm] *ERROR* DP-3: invalid native reply 0x03

Not quite sure I understand what’s going on with these error messages, but it seems like unless you explicitly tell the system not to use nouveau at boot, things break. I can’t say I’m particularly surprised since the args that blacklist nouveau get added to the grub config automatically when you follow the rpm-fusion instructions.