Fedora 44: Black screen after NVIDIA driver reinstallation

Ask Fedora
,
1

Hello,
I am experiencing a black screen on boot after attempting to perform a clean reinstallation of my NVIDIA drivers.
System Details:

  • OS: Fedora 44

  • GPU: GTX 4070 laptop
    Issue Description:
    I recently installed a Razer control application, which led to my system failing to detect an external monitor and the NVIDIA GPU itself. I attempted to resolve this by performing a clean purge and reinstall of the drivers.
    Steps Taken:

  • Purged existing NVIDIA drivers:
    sudo dnf remove ‘nvidia’ --exclude=nvidia-gpu-firmware

  • Removed NVIDIA-related kernel parameters from the boot configuration.

  • Reinstalled the drivers via RPM Fusion:
    sudo dnf install akmod-nvidia xorg-x11-drv-nvidia-cuda

Current Behavior:
The system boots past the initial splash screen, but the display remains black and I cannot reach the desktop environment.
Logs:
I have captured the logs from the most recent boot attempt here:

Could you please help me identify what might be failing during the graphics initialization process? Any advice on further diagnostic steps or recovery would be greatly appreciated.
Thank you.

Update so i able to pinpoint new thing, this happen only when connected to external monitor
if i boot this without external monitor it boot fine, the second i connect external monitor gnome began to crash

*edit add new info

2

Gnome shell crashes repeatedly.

Mutter also complains about Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Not hardware accelerated and it also states EGL failures libEGL warning: egl: failed to create dri2 screen… then Gnome-shell blows it brains out with an ABRT.

Looks like you’re using an i915 chipset and an nvidia chipset too; do you get the same crash if you just ise the Nv card for output, and don’t use the integrated i915?

3

To be clear, did you also remove the problem Razer application?

4

Do you have any guide to on how to do this, is it just use switch on bios or something else?

5

Yeah I did, completely remove including openrazer too just to be safe. I’ve also read some source of the app and didn’t find any lead on the cause.

6

Afraid not - I don’t have either an Nv card any longer nor do I have any CPU with integrated graphics.

7

Btw I used bios way and switch to use Nvidia only and it boot normally
I think I have problem with my Nvidia

8

Whatever open source driver in use for the iGPU can break nvidia loading, it’s more likely fedora released a bum kernel.

9

Update so i able to pinpoint new thing, this happen only when connected to external monitor
if i boot this without external monitor it boot fine, the second i connect external monitor gnome began to crash

User Logs:
--Aug 20 07:49:54 dierz-machine gnome-shell[11047]: Running GNOME Shell (using mutter 50.4) as a Wayland display server
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: Unknown experimental feature 'scale-monitor-framebuffer'
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: pci id for fd 12: 10de:2860, driver (null)
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: pci id for fd 14: 10de:2860, driver (null)
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: pci id for fd 15: 10de:2860, driver (null)
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: pci id for fd 14: 10de:2860, driver (null)
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: pci id for fd 15: 10de:2860, driver (null)
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: Thread 'KMS thread' will be using high priority scheduling
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: libEGL warning: pci id for fd 21: 10de:2860, driver (null)
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: pci id for fd 22: 10de:2860, driver (null)
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: pci id for fd 23: 10de:2860, driver (null)
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: libEGL warning: egl: failed to create dri2 screen
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: libEGL warning: pci id for fd 21: 10de:2860, driver (null)
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: pci id for fd 22: 10de:2860, driver (null)
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: pci id for fd 23: 10de:2860, driver (null)
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: libEGL warning: egl: failed to create dri2 screen
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: libEGL warning: pci id for fd 21: 10de:2860, driver (null)
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: Device '/dev/dri/card0' prefers shadow buffer
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: Added device '/dev/dri/card0' (nvidia-drm) using atomic mode setting.
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: Device '/dev/dri/card1' prefers shadow buffer
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: Added device '/dev/dri/card1' (i915) using atomic mode setting.
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Not hardware accelerated
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: Created gbm renderer for '/dev/dri/card0'
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: Created gbm renderer for '/dev/dri/card1'
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: GPU /dev/dri/card1 selected primary from builtin panel presence
Aug 20 07:49:54 dierz-machine gnome-shell[11047]: Obtained a high priority EGL context
Aug 20 07:49:55 dierz-machine gnome-shell[11047]: Using public X11 display :0, (using unix:/tmp/.X11-unix/X1 for managed services)
Aug 20 07:49:55 dierz-machine gnome-shell[11047]: Using Wayland display name 'wayland-0'
Aug 20 07:49:55 dierz-machine gnome-shell[11047]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
Aug 20 07:49:55 dierz-machine gnome-shell[11047]: Registering session with GDM
Aug 20 07:49:55 dierz-machine gnome-shell[11047]: Extension background-logo@fedorahosted.org already installed in /home/dierz/.local/share/gnome-shell/extensions/background-logo@fedorahosted.org. /usr/share/gnome-shell/extensions/background-logo@fedorahosted.org will not be loaded
Aug 20 07:49:55 dierz-machine gnome-shell[11047]: Extension appindicatorsupport@rgcjonas.gmail.com already installed in /home/dierz/.local/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com. /usr/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com will not be loaded
Aug 20 07:49:55 dierz-machine gnome-shell[11047]: Will monitor session 5
Aug 20 07:49:55 dierz-machine gnome-shell[11047]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Aug 20 07:49:56 dierz-machine gnome-shell[11047]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 20 07:49:56 dierz-machine gnome-shell[11047]: Type GITypeInfo of property NM.Object::client does not match return type GITypeInfo of getter get_client. Falling back to slow path
Aug 20 07:49:56 dierz-machine gnome-shell[11047]: Failed to get METAR data: Unacceptable TLS certificate
Aug 20 07:49:56 dierz-machine gnome-shell[11047]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 20 07:49:56 dierz-machine gnome-shell[11047]: [Custom Command Toggle] Extension enabled | Toggles created: 6 | Detailed logging: false
Aug 20 07:49:56 dierz-machine gnome-shell[11047]: Gio.UnixInputStream has been moved to a separate platform-specific library. Please update your code to use GioUnix.InputStream instead.
0 get() ["resource:///org/gnome/gjs/modules/core/_common.js":190:42]
1 checkCommandOutput() ["file:///home/dierz/.local/share/gnome-shell/extensions/custom-command-toggle@storageb.github.com/extension.js":834:36]
2 setupCheckSync() ["file:///home/dierz/.local/share/gnome-shell/extensions/custom-command-toggle@storageb.github.com/extension.js":771:35]
3 initialSetup() ["file:///home/dierz/.local/share/gnome-shell/extensions/custom-command-toggle@storageb.github.com/extension.js":712:40]
4 enable() ["file:///home/dierz/.local/share/gnome-shell/extensions/custom-command-toggle@storageb.github.com/extension.js":989:22]
5 _callExtensionEnable() ["resource:///org/gnome/shell/ui/extensionSystem.js":264:38]
6 loadExtension() ["resource:///org/gnome/shell/ui/extensionSystem.js":431:32]
7 AsyncFunctionNext() ["self-hosted":800:27]
8 anonymous() ["resource:///org/gnome/shell/ui/init.js":20:20]
Aug 20 07:49:56 dierz-machine gnome-shell[11047]: Failed to get met.no forecast data: Unacceptable TLS certificate
Aug 20 07:49:56 dierz-machine gnome-shell[11047]: [tilingshell] [DefaultMenu] updateMonitorName: monitor=0, x=0, y=0
Aug 20 07:49:56 dierz-machine gnome-shell[11047]: [tilingshell] [DefaultMenu] updateMonitorName: monitorsDetails=[]
Aug 20 07:49:56 dierz-machine gnome-shell[11047]: [tilingshell] [DefaultMenu] updateMonitorName: no match found for monitor 0
Aug 20 07:49:56 dierz-machine gnome-shell[11047]: [tilingshell] [extension] extension is enabled
Aug 20 07:49:57 dierz-machine gnome-shell[11047]: Update check failed: Unacceptable TLS certificate
Aug 20 07:49:57 dierz-machine gnome-shell[11047]: GNOME Shell started at Thu Aug 20 2026 07:49:55 GMT+0700 (Western Indonesia Time)
Aug 20 07:49:57 dierz-machine gnome-shell[11047]: Registering display with GDM
Aug 20 07:49:57 dierz-machine gnome-shell[11047]: [tilingshell] [extension] building a tiling manager for each monitor
Aug 20 07:49:57 dierz-machine gnome-shell[11047]: [tilingshell] [TilingManager 0] Work area for monitor 0: 0 32 2560x1568
Aug 20 07:49:59 dierz-machine gnome-shell[11047]: pci id for fd 98: 10de:2860, driver (null)
Aug 20 07:49:59 dierz-machine gnome-shell[11047]: pci id for fd 49: 10de:2860, driver (null)
Aug 20 07:49:59 dierz-machine gnome-shell[11047]: pci id for fd 100: 10de:2860, driver (null)
Aug 20 07:49:59 dierz-machine gnome-shell[11047]: pci id for fd 49: 10de:2860, driver (null)
Aug 20 07:49:59 dierz-machine gnome-shell[11047]: pci id for fd 100: 10de:2860, driver (null)
Aug 20 07:49:59 dierz-machine gnome-shell[11047]: libEGL warning: pci id for fd 136: 10de:2860, driver (null)
Aug 20 07:49:59 dierz-machine gnome-shell[11047]: pci id for fd 137: 10de:2860, driver (null)
Aug 20 07:49:59 dierz-machine gnome-shell[11047]: pci id for fd 138: 10de:2860, driver (null)
Aug 20 07:49:59 dierz-machine gnome-shell[11047]: libEGL warning: egl: failed to create dri2 screen
Aug 20 07:49:59 dierz-machine gnome-shell[11047]: libEGL warning: pci id for fd 136: 10de:2860, driver (null)
Aug 20 07:49:59 dierz-machine gnome-shell[11047]: pci id for fd 137: 10de:2860, driver (null)
Aug 20 07:49:59 dierz-machine gnome-shell[11047]: pci id for fd 138: 10de:2860, driver (null)
Aug 20 07:49:59 dierz-machine gnome-shell[11047]: libEGL warning: egl: failed to create dri2 screen
Aug 20 07:49:59 dierz-machine gnome-shell[11047]: libEGL warning: pci id for fd 136: 10de:2860, driver (null)
Aug 20 07:49:59 dierz-machine gnome-shell[11047]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Not hardware accelerated
Aug 20 07:49:59 dierz-machine gnome-shell[11047]: Created gbm renderer for '/dev/dri/card0'
Aug 20 07:49:59 dierz-machine gnome-shell[11047]: [tilingshell] [LayoutWidget] relayout not needed
Aug 20 07:49:59 dierz-machine gnome-shell[11047]: [tilingshell] [extension] building a tiling manager for each monitor
Aug 20 07:49:59 dierz-machine gnome-shell[11047]: [tilingshell] [TilingManager 0] Work area for monitor 0: 0 32 2560x1568
Aug 20 07:49:59 dierz-machine gnome-shell[11047]: [tilingshell] [TilingManager 1] Work area for monitor 1: 2560 243 1920x1080
Aug 20 07:50:01 dierz-machine gnome-shell[11047]: intel: the execbuf ioctl keeps returning ENOMEM
Aug 20 07:50:15 dierz-machine gnome-shell[11047]: == Stack trace for context 0x562d44bb8de0 ==
Aug 20 07:50:15 dierz-machine gnome-shell[11047]: #0   562d44c89528 i   resource:///org/gnome/shell/ui/init.js:20 (3069fdc8d8d0 @ 48)
--
11

Not sure why gnome-shell crashes. You may need to report it to the devs: https://gitlab.gnome.org/GNOME/gnome-shell/-/work_items

They’ll want you to provide a stack trace: Stack Traces

p.s. I noticed your firmware is out of date:

Razer Blade 16 - RZ09-0483/SO690, BIOS 2.03 06/04/2024

You may want to go to your laptop’s support page and update all the firmware. Sometimes, unpatched firmware bugs cause unexpected side effects.