Frequent Total Display Loss / Black Screen with NVIDIA RTX 3060 Ti on Fedora KDE (Requires Hard Reset)

Ask Fedora
, , ,
1

Body:

Hi everyone,

I am experiencing a severe and frustrating issue with my Fedora installation (KDE Plasma) where my display completely cuts off (Black Screen / No Signal), forcing me to hard reset the system. I would appreciate any help or guidance on how to properly diagnose and fix this.

My Hardware & Environment:

  • OS: Fedora Linux (KDE Plasma desktop environment)
  • GPU: NVIDIA GeForce RTX 3060 Ti (Using proprietary drivers)
  • Triggers: The crash happens randomly but frequently during hardware-accelerated web browsing and when running 3D applications/games (such as Roblox via Wine/Proton or Besiege).

The Problem Description:

When the crash occurs, the monitor suddenly loses the video signal entirely and goes black. The PC components stay powered on, and background audio sometimes continues for a moment, but the GPU completely stops outputting any display.

What I Have Attempted During the Crash:

  1. TTY Switching: I tried switching to a virtual terminal using Ctrl + Alt + F3 (and other F-keys) to kill the offending processes, but the monitor remains completely black with “No Signal”. The display pipeline seems entirely frozen.
  2. Display Manager Restart: I attempted to blindly restart the display manager, suspecting a Wayland/X11 session crash using:Bashsudo systemctl restart sddmHowever, because the display output is completely dead, this does not recover the monitor signal.
  3. Magic SysRq (REISUB): In some instances, the system is so heavily locked up that even the REISUB key combination fails, forcing me to use the physical power button to hard reset, which I want to avoid to prevent data corruption.

Troubleshooting & Context:

  • I suspect an issue with the current kernel module integration or a severe conflict between the proprietary NVIDIA driver and the display server (especially under Wayland configuration parameters).
  • I’ve tried switching sessions and keeping configurations clean, but heavy GPU tasks consistently trigger this driver kilitlenmesi (lockup).

Could anyone guide me on which log files to inspect (e.g., specific journalctl flags or Xorg/Wayland crash logs) right after a forced reboot to catch the exact error line? Are there known kernel parameters or stable driver rollbacks recommended for the RTX 3060 Ti on Fedora right now?

Thanks in advance for your support!

2

Hello, and welcome to the Fedora forum.

When not installed yet, install inxi in the terminal: sudo dnf install inxi
Perform: inxi -Fzxx
(select and copy the command plus the complete output (shift ctrl c) from terminal,
in your answer click on </>, then right-click on the line in blue and type ctrl v).
I also have an RTX 3060 and I have no problems with it, I am using KDE (be it in Kinoite) and I use Wayland. I installed the open Nvidia drivers from RPM Fusion.
How did you install the Nvidia drivers?

3

Hi, thanks for the quick and helpful reply!

You hit the nail on the head. I checked my inxi output, and as you suspected, I am indeed running the traditional proprietary Nvidia driver (v: 595.80) under a Wayland session (kwin_wayland) on Fedora 44. This explains why my configuration has been clashing so badly, while your setup with the open-source kernel modules runs flawlessly.

Here is the complete output of my inxi -Fzxx to give you the full picture:

PlaintextSystem: Kernel: 7.0.14-201.fc44.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 16.1.1 Desktop: KDE Plasma v: 6.7.1 tk: Qt v: N/A wm: kwin_wayland dm: N/A Distro: Fedora Linux 44 (KDE Plasma Desktop Edition) Machine: Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required> Mobo: ASUSTeK model: TUF GAMING B550M-PLUS (WI-FI) v: Rev X.0x serial: <superuser required> part-nu: SKU Firmware: UEFI vendor: American Megatrends v: 3621 date: 01/13/2025 CPU: Info: 6-core model: AMD Ryzen 5 5600 bits: 64 type: MT MCP arch: Zen 3+ rev: 2 cache: L1: 384 KiB L2: 3 MiB L3: 32 MiB Speed (MHz): avg: 3327 min/max: 566/4471 boost: enabled cores: 1: 3327 2: 3327 3: 3327 4: 3327 5: 3327 6: 3327 7: 3327 8: 3327 9: 3327 10: 3327 11: 3327 12: 3327 bogomips: 84000 Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: NVIDIA GA104 [GeForce RTX 3060 Ti Lite Hash Rate] vendor: ASUSTeK driver: nvidia v: 595.80 arch: Ampere pcie: speed: 2.5 GT/s lanes: 16 ports: active: DP-2 empty: DP-1, DP-3, HDMI-A-1, HDMI-A-2 bus-ID: 07:00.0 chip-ID: 10de:2489 Display: wayland server: X.org v: 1.21.1.23 with: Xwayland v: 24.1.12 compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting alternate: fbdev,nouveau,nv,vesa gpu: nv_platform,nvidia,nvidia-nvswitch display-ID: 0 Monitor-1: DP-2 model: Samsung LS24AG32x res: 1920x1080 hz: 165 dpi: 93 diag: 604mm (23.8") API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia x11: drv: nvidia inactive: device-1 API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: nvidia mesa v: 595.80 glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 display-ID: :0.0 API: Vulkan v: 1.4.341 surfaces: N/A device: 0 type: discrete-gpu driver: nvidia device-ID: 10de:2489 device: 1 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: NVIDIA GA104 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 07:00.1 chip-ID: 10de:228b Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 09:00.4 chip-ID: 1022:1487 Device-3: Weltrend H2002U PRO driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 3-2:2 chip-ID: 040b:2804 API: ALSA v: k7.0.14-201.fc44.x86_64 status: kernel-api Server-1: PipeWire v: 1.6.7 status: active with: 1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin Network: Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2723 IF: wlp5s0 state: down mac: <filter> Device-2: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel pcie: speed: 5 GT/s lanes: 1 port: f000 bus-ID: 06:00.0 chip-ID: 10ec:8125 IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter> IF-ID-1: docker0 state: down mac: <filter> Bluetooth: Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-5:2 chip-ID: 8087:0029 Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: <filter> bt-v: 5.2 lmp-v: 11 Drives: Local Storage: total: 523.07 GiB used: 105.65 GiB (20.2%) ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 500GB size: 465.76 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 40.9 C ID-2: /dev/sda vendor: SanDisk model: USB 3.2Gen1 size: 57.3 GiB type: USB rev: 3.2 spd: 5 Gb/s lanes: 1 serial: <filter> Partition: ID-1: / size: 463.17 GiB used: 104.81 GiB (22.6%) fs: btrfs dev: /dev/nvme0n1p3 ID-2: /boot size: 1.9 GiB used: 838.2 MiB (43.1%) fs: ext4 dev: /dev/nvme0n1p2 ID-3: /boot/efi size: 598.8 MiB used: 20 MiB (3.3%) fs: vfat dev: /dev/nvme0n1p1 ID-4: /home size: 463.17 GiB used: 104.81 GiB (22.6%) fs: btrfs dev: /dev/nvme0n1p3 Swap: ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0 Sensors: System Temperatures: cpu: 43.2 C mobo: N/A Fan Speeds (rpm): N/A Info: Memory: total: 32 GiB available: 31.24 GiB used: 4.68 GiB (15.0%) Processes: 413 Power: uptime: 18m wakeups: 0 Init: systemd v: 259 default: graphical Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 50 Compilers: gcc: 16.1.1 Shell: Bash v: 5.3.9 running-in: konsole inxi: 3.3.40

Could you please guide me on the safest way to completely remove this traditional proprietary driver and switch over to the open-source Nvidia kernel modules (akmod-nvidia-open) package from RPM Fusion? I want to make sure I don’t break my current desktop session or end up with a blinking cursor on boot.

Thank you so much for your support!

4

akmod-nvidia-open is obsolete now. The akmod-nvidia package should automatically install the open-kernel modules on supported cards like yours.

To check which flavour of the driver you have:

modinfo -l nvidia

If you see “Dual MIT/GPL” then you have the open-kernel driver.

5

It appears that your system is set for plaintext on the toolbar (the far left button on the toolbar as shown

image
Please switch it to markdown as shown in the next image then post the inxi output again so we can see it exactly as formatted on your screen.
image

Plaintext removes all the on-screen formatting and actually converts everything to one continuous single line of text so it becomes almost impossible to read and interpret.

This from your post above
sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: NVIDIA GA104 [GeForce RTX 3060 Ti Lite Hash Rate] vendor: ASUSTeK driver: nvidia v: 595.80 arch: Ampere pcie: speed: 2.5 GT/s lanes: 16 ports: active: DP-2 empty: DP-1, DP-3, HDMI-A-1, HDMI-A-2 bus-ID: 07:00.0 chip-ID: 10de:2489 Display: wayland server: X.org v: 1.21.1.23 with: Xwayland v: 24.1.12 compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting alternate: fbdev,nouveau,nv,vesa gpu: nv_platform,nvidia,nvidia-nvswitch display-ID: 0 Monitor-1: DP-2 model: Samsung LS24AG32x res: 1920x1080 hz: 165 dpi: 93 diag: 604mm (23.8") API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia x11: drv: nvidia inactive: device-1 API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: nvidia mesa v: 595.80 glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 display-ID: :0.0 API: Vulkan v: 1.4.341 surfaces: N/A device: 0 type: discrete-gpu driver: nvidia device-ID: 10de:2489 device: 1 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: NVIDIA GA104 High Definition Audio vendor:

as compared to this

Graphics:
  Device-1: NVIDIA GA106 [Geforce RTX 3050] vendor: Micro-Star MSI
    driver: nvidia v: 595.80 arch: Ampere pcie: speed: 16 GT/s lanes: 8 ports:
    active: DP-1 empty: DP-2,DP-3,HDMI-A-1 bus-ID: 06:00.0 chip-ID: 10de:2507
  Device-2: ARC Camera driver: snd-usb-audio,uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 3-2.3:5 chip-ID: 05a3:9331
  Display: wayland server: X.org v: 1.21.1.23 with: Xwayland v: 24.1.12
    compositor: gnome-shell driver: X: loaded: modesetting,nvidia
    alternate: fbdev,nouveau,nv,vesa gpu: nv_platform,nvidia,nvidia-nvswitch
    display-ID: 0
  Monitor-1: DP-1 model: LG (GoldStar) TV SSCR2 res: 3840x2160 hz: 30
    dpi: 61 diag: 1836mm (72.3")
  API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: swrast
    gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia x11:
    drv: nvidia inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: nvidia mesa v: 595.80
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3050/PCIe/SSE2
    display-ID: :0.0
  API: Vulkan v: 1.4.341 surfaces: N/A device: 0 type: discrete-gpu
    driver: nvidia device-ID: 10de:2507 device: 1 type: cpu
    driver: mesa llvmpipe device-ID: 10005:0000
  Info: Tools: api: eglinfo, glxinfo, vulkaninfo de: gnome-monitor-config
    gpu: nvidia-settings,nvidia-smi wl: wayland-info,wlr-randr x11: xdriinfo,
    xdpyinfo, xprop, xrandr

Removing a driver that was installed using the nvidia .run file is the same as installing it. Run the exact same command but add uninstall following the command on cli.

Before you do that please verify what is actually installed with an rpm.
dnf list --installed \*nvidia\*
If that shows nothing but the nvidia-gpu-firmware package then the driver is likely installed directly from an nvidia .run file. If it shows a list of packages then please post the result here so we can see the output before doing anything else.

Configuration to use the rpmfusion repo for installation is actually quite simple.
Run dnf repolist and if it shows the rpmfusion-nonfree and rpmfusion-nonfree-updates repos you are already configured to install the driver from rpmfusion.

If those 2 repos are not shown then configure them for use as shown here.
Installing the nvidia drivers from rpmfusion is shown here (but you must remove and drivers installed directly from nvidia before installing from rpmfusion)

6

Thanks for your reply.

I have re-run the requested commands and here are the results.

inxi -Fzxx

System:
  Kernel: 7.0.14-201.fc44.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 16.1.1
  Desktop: KDE Plasma v: 6.7.1 wm: kwin_wayland
  Distro: Fedora Linux 44 (KDE Plasma Desktop Edition)

Graphics:
  Device-1: NVIDIA GA104 [GeForce RTX 3060 Ti Lite Hash Rate]
    driver: nvidia v: 595.71.05
    pcie: speed: 2.5 GT/s lanes: 16
    active: DP-2
  Display: wayland
  Monitor-1: Samsung LS24AG32x
    resolution: 1920x1080 @ 165 Hz

(Full inxi output attached above.)

Installed NVIDIA packages

dnf list --installed "*nvidia*"

The system is using the RPM Fusion NVIDIA driver packages:

  • akmod-nvidia 595.71.05
  • xorg-x11-drv-nvidia 595.71.05
  • xorg-x11-drv-nvidia-libs
  • xorg-x11-drv-nvidia-cuda
  • nvidia-settings
  • nvidia-persistenced
  • etc.

So the driver was not installed using the NVIDIA .run installer.

Enabled repositories

dnf repolist

RPM Fusion repositories are enabled:

  • rpmfusion-free
  • rpmfusion-free-updates
  • rpmfusion-nonfree
  • rpmfusion-nonfree-nvidia-driver
  • rpmfusion-nonfree-steam

PCIe link status

I also checked the PCIe link:

sudo lspci -vv -s 07:00.0 | grep LnkSta

Output:

LnkSta: Speed 2.5GT/s (downgraded), Width x16
LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+ EqualizationPhase1+

One additional observation that may be relevant:

The display loss is often triggered when a Discord notification appears. The system itself continues running (I can still hear audio), but the monitor loses signal and I have to perform a hard reset. The same issue also happens in games such as War Thunder, Sober, and Minecraft with shaders enabled.

Please let me know what you would like me to check next.

One additional note: I installed the NVIDIA driver using an RPM Fusion installation guide on YouTube, not by downloading and running NVIDIA’s official .run installer.

Based on the installed packages (akmod-nvidia, xorg-x11-drv-nvidia, etc.), it appears the driver is indeed installed from the RPM Fusion repositories rather than the NVIDIA .run installer.

I performed an OCCT VRAM test and it completed without any errors, so VRAM does not appear to be faulty.

I also tested with FurMark. The first three benchmark runs completed successfully, but during the fourth consecutive run the display suddenly went black and never recovered. The system appeared to continue running (audio continued), but I had to perform a hard reset.

7

It does seem you may have installed the driver, but since you failed to include the output of dnf list --installed \*nvidia\* we cannot tell the exact versions and repo it was installed from.

When we ask for the details it is always expected that you would run the given command then post its output instead of a paraphrased interpretation. This would allow us to see details you may not manually include.

I can only assume, from the version you stated that the driver was installed from the rpmfusion-nonfree-nvidia-driver repo, which contains the driver version 595.71.05 that was available when fedora 44 was first released.

I suggest that you upgrade the nvidia driver using the command
sudo dnf upgrade \*nvidia\* --refresh --repo rpmfusion-nonfree-updates which should install the 595.80 version of the driver to replace the 595.71.05 version currently installed.

8

Looking back at the output of dnf repolist, it looks like rpmfusion-nonfree-updates isn’t enabled on this system.

It would be good to first run this to ensure that all the expected RPMFusion repos are there:

sudo dnf install https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm https://mirrors.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm
9

Hi everyone, thanks a lot for the quick support and suggestions!

I ran the commands to ensure the repositories are installed, and it turns out they are already present on my system. Here is the output:

Plaintextanilcemresacak@fedora:~$ sudo dnf install https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm https://mirrors.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm Updating and loading repositories: Repositories loaded. Package "rpmfusion-free-release-44-3.noarch" is already installed. Package "rpmfusion-nonfree-release-44-3.noarch" is already installed. Nothing to do.

I also checked my installed NVIDIA packages as requested. They are currently sitting at version 595.71.05:

Plaintextanilcemresacak@fedora:~$ dnf list --installed \*nvidia\* Installed packages (available for reinstall, available for upgrade) akmod-nvidia.x86_64 3:595.71.05-1.fc44 rpmfusion-nonfree-nvidia-driver kmod-nvidia-7.0.14-201.fc44.x86_64.x86_64 3:595.71.05-1.fc44 @commandline nvidia-gpu-firmware.noarch 20260622-1.fc44 updates nvidia-modprobe.x86_64 3:595.71.05-1.fc44 rpmfusion-nonfree-nvidia-driver nvidia-persistenced.x86_64 3:595.71.05-1.fc44 rpmfusion-nonfree-nvidia-driver nvidia-settings.x86_64 3:595.71.05-1.fc44 rpmfusion-nonfree-nvidia-driver xorg-x11-drv-nvidia.x86_64 3:595.71.05-1.fc44 rpmfusion-nonfree-nvidia-driver xorg-x11-drv-nvidia-cuda.x86_64 3:595.71.05-1.fc44 rpmfusion-nonfree-nvidia-driver xorg-x11-drv-nvidia-cuda-libs.i686 3:595.71.05-1.fc44 rpmfusion-nonfree-nvidia-driver xorg-x11-drv-nvidia-cuda-libs.x86_64 3:595.71.05-1.fc44 rpmfusion-nonfree-nvidia-driver xorg-x11-drv-nvidia-kmodsrc.x86_64 3:595.71.05-1.fc44 rpmfusion-nonfree-nvidia-driver xorg-x11-drv-nvidia-libs.i686 3:595.71.05-1.fc44 rpmfusion-nonfree-nvidia-driver xorg-x11-drv-nvidia-libs.x86_64 3:595.71.05-1.fc44 rpmfusion-nonfree-nvidia-driver xorg-x11-drv-nvidia-power.x86_64 3:595.71.05-1.fc44 rpmfusion-nonfree-nvidia-driver xorg-x11-drv-nvidia-xorg-libs.x86_64 3:595.71.05-1.fc44 rpmfusion-nonfree-nvidia-driver

Since the repos are already active, should I proceed directly with the sudo dnf upgrade \*nvidia\* --refresh --repo rpmfusion-nonfree-updates command to get the 595.80 version, or is there anything else I need to configure first regarding the PCIe downgrade issue (LnkSta: Speed 2.5GT/s)?

10

Something is strange, because your earlier dnf repolist command showed that rpmfusion-nonfree-updates was missing.

Can you show the output of:

dnf repolist --disabled

to see if it is present but disabled?

That shouldn’t be an issue. It’s normal that the card goes down to 2.5GT/s when its utilisation is low.

11

Hi again,

As requested, I ran the dnf repolist --disabled command. You were absolutely right; it looks like rpmfusion-nonfree-updates is currently sitting in the disabled list.

Here is the full output:

Plaintextanilcemresacak@fedora:~$ dnf repolist --disabled repo id repo name copr:copr.fedorainfracloud.org:phracek:PyCharm Copr repo for PyCharm owned by phracek docker-ce-stable-source Docker CE Stable - Sources docker-ce-test Docker CE Test - x86_64 docker-ce-test-source Docker CE Test - Sources fedora-cisco-openh264-debuginfo Fedora 44 openh264 (From Cisco) - x86_64 - Debug fedora-cisco-openh264-source Fedora 44 openh264 (From Cisco) - x86_64 - Source fedora-debuginfo Fedora 44 - x86_64 - Debug fedora-source Fedora 44 - Source google-chrome google-chrome rpmfusion-free-debuginfo RPM Fusion for Fedora 44 - Free - Debug rpmfusion-free-source RPM Fusion for Fedora 44 - Free - Source rpmfusion-free-updates-debuginfo RPM Fusion for Fedora 44 - Free - Updates Debug rpmfusion-free-updates-source RPM Fusion for Fedora 44 - Free - Updates Source rpmfusion-free-updates-testing RPM Fusion for Fedora 44 - Free - Test Updates rpmfusion-free-updates-testing-debuginfo RPM Fusion for Fedora 44 - Free - Test Updates Debug rpmfusion-free-updates-testing-source RPM Fusion for Fedora 44 - Free - Test Updates Source rpmfusion-nonfree-debuginfo RPM Fusion for Fedora 44 - Nonfree - Debug rpmfusion-nonfree-nvidia-driver-debuginfo RPM Fusion for Fedora 44 - Nonfree - NVIDIA Driver Debug rpmfusion-nonfree-nvidia-driver-source RPM Fusion for Fedora 44 - Nonfree - NVIDIA Driver Source rpmfusion-nonfree-source RPM Fusion for Fedora 44 - Nonfree - Source rpmfusion-nonfree-steam-debuginfo RPM Fusion for Fedora 44 - Nonfree - Steam Debug rpmfusion-nonfree-steam-source RPM Fusion for Fedora 44 - Nonfree - Steam Source rpmfusion-nonfree-updates RPM Fusion for Fedora 44 - Nonfree - Updates rpmfusion-nonfree-updates-debuginfo RPM Fusion for Fedora 44 - Nonfree - Updates Debug rpmfusion-nonfree-updates-source RPM Fusion for Fedora 44 - Nonfree - Updates Source rpmfusion-nonfree-updates-testing RPM Fusion for Fedora 44 - Nonfree - Test Updates rpmfusion-nonfree-updates-testing-debuginfo RPM Fusion for Fedora 44 - Nonfree - Test Updates Debug rpmfusion-nonfree-updates-testing-source RPM Fusion for Fedora 44 - Nonfree - Test Updates Source updates-debuginfo Fedora 44 - x86_64 - Updates - Debug updates-source Fedora 44 - Updates Source updates-testing Fedora 44 - x86_64 - Test Updates updates-testing-debuginfo Fedora 44 - x86_64 - Test Updates Debug updates-testing-source Fedora 44 - Test Updates Source

Could you please let me know the correct command to enable the rpmfusion-nonfree-updates repository permanently, so I can finally proceed with the sudo dnf upgrade \*nvidia\* command to get the 595.80 driver?

12 
sudo dnf config-manager setopt rpmfusion-nonfree-updates.enabled=1
13

Awesome, that did the trick!

I ran sudo dnf config-manager setopt rpmfusion-nonfree-updates.enabled=1 and successfully enabled the repository.

I am now running sudo dnf upgrade \*nvidia\* --refresh and it is finally pulling the 595.80 driver updates. Once the installation is complete, I will reboot, let akmods do its thing, and test if the black screen / 2.5GT/s downgrade issue still happens under load (like in FurMark).

I will report back with the results shortly. Thank you so much for catching that disabled repo!

14

Please stop posting text as Plaintext.
It eliminates the formatting seen on-screen and makes many things almost unreadable by compressing spaces, and tabs into one single space, as well as making a full paragraph into one single line by eliminating the newline character.

I mentioned in my post 5 above how to change that so it shows as preformatted text instead of plain text.

This is much more readable

$ sudo dnf install https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm https://mirrors.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm
Updating and loading repositories:
Repositories loaded.
 https://mirrors.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-44.noarch.rpm                                                 100% |  15.2 KiB/s |  11.5 KiB |  00m01s
 https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-44.noarch.rpm                                                       100% |  14.9 KiB/s |  11.5 KiB |  00m01s
Package "rpmfusion-free-release-44-3.noarch" is already installed.
Package "rpmfusion-nonfree-release-44-3.noarch" is already installed.

Nothing to do.
17

The application keeps crashing whenever I try to run it with shaders. The same error occurred again, and it closes unexpectedly right after loading

18

Hi everyone, just checking in to see if there are any fresh ideas on what to check next

Just to quickly summarize: The system is now running the updated 595.80 driver from RPM Fusion, but heavy loads (like FurMark) still trigger a complete black screen that requires a hard reset. I tried checking the logs from the crashed session, but there are absolutely no errors recorded right before the crash. The system locks up so instantly that it can’t even write the failure to the disk.

Since we’ve ruled out the driver version and the logs are empty, what would be the best path forward? Are there any specific kernel parameters (maybe related to Wayland/X11 or NVIDIA power management) I should try adding? Alternatively, would it be useful to monitor the system via SSH from my phone or another laptop to catch the exact error right as the screen goes black?

I am ready to try any new diagnostic steps you can throw my way. Thanks! @computersavvy , @pg-tips , @jandemus

19

That’s a good idea. Use journalctl -f in the SSH session and see if this shows anything revealing.

20

Does this card fail in this way when simply using it normally, to render straight non-3d output to a screen or is it only when hammering it with a stress test.

If so, I’d be inclined to suspect thermals.

What does nvidia-smi tell you about it when thrashing the nuts off it?

21

No, it doesn’t crash during normal use or basic 3D rendering. For example, playing vanilla Minecraft works perfectly fine. However, the moment I enable shaders in Minecraft, the system crashes.

I’ve tested this in other games as well; whenever there are heavy lighting effects or shadows involved, it seems to trigger what I suspect is a driver conflict. I never experienced this issue when I was using Windows.

Additionally, FurMark behavior is inconsistent. Sometimes the stress test runs completely fine without any issues, while other times it completely fails to start and crashes the system right away.

22

Does this still happen with the updated drivers?

If so, it sounds like there are two separate issues:

  1. In some situations you lose the display but the system is still running.
  2. In other scenarios, the machine completely dies without even logging anything.

Like @anothermindbomb said, #2 might be down to thermals (or perhaps voltage / power issues) if it happens when under heavy load.

#1 is probably different if just getting a Discord notification can trigger it.