Skip to main content

Fedora rebuild NVidia drivers

 

Rebuilding NVIDIA Drivers on Fedora After Updates

If you’re running Fedora with NVIDIA proprietary drivers, you’ve probably run into this situation: screen does not work properly.

The fix is simple, but easy to forget. This post is here so future-you (and others) don’t waste time rediscovering it.

The Command You’re Looking For

sudo akmods --rebuild --force

That’s it.

This command forces a rebuild of kernel modules managed by akmods, including NVIDIA drivers.

When Should You Run It?

Typically, you’ll need this after:

  • A kernel upgrade
  • An update of one of these packages:
    • akmod-nvidia
    • xorg-x11-drv-nvidia-cuda

Why? Because NVIDIA drivers are built as kernel modules, and they must match your currently running kernel. When Fedora updates the kernel, the modules may not yet be compiled for it — or something may have gone wrong during automatic build.

What’s Happening Under the Hood

Fedora uses akmods (Automatic Kernel Module Build Service) to compile kernel modules on your machine.

In theory, this happens automatically in the background after updates. In practice:

  • The build may fail silently
  • You may reboot too quickly before the build completes
  • Dependencies may not be fully ready

Running the command manually ensures everything is rebuilt correctly for your current kernel.

Typical Recovery Workflow

When things are weird after an update:

  1. Boot into your system (even if degraded)
  2. Open a terminal

  3. Run:

    sudo akmods --rebuild --force
  4. Wait for the build to complete

  5. Reboot:

    sudo reboot

Popular posts from this blog

Undefined global vim

Defining vim as global outside of Neovim When developing plugins for Neovim, particularly in Lua, developers often encounter the "Undefined global vim" warning. This warning can be a nuisance and disrupt the development workflow. However, there is a straightforward solution to this problem by configuring the Lua Language Server Protocol (LSP) to recognize 'vim' as a global variable. Getting "Undefined global vim" warning when developing Neovim plugin While developing Neovim plugins using Lua, the Lua language server might not recognize the 'vim' namespace by default. This leads to warnings about 'vim' being an undefined global variable. These warnings are not just annoying but can also clutter the development environment with unnecessary alerts, potentially hiding other important warnings or errors. Defining vim as global in Lua LSP configuration to get rid of the warning To resolve the "Undefined global vi...
Read more

CopilotChat GlobFile Configuration

CopilotChat GlobFile Configuration Want to feed multiple files into GitHub Copilot Chat from Neovim without listing each one manually? Let's add a tiny feature that does exactly that: a file glob that includes full file contents . In this post, we'll walk through what CopilotChat.nvim offers out of the box, why the missing piece matters, and how to implement a custom #file_glob:<pattern> function to include the contents of all files matching a glob. Using Copilot Chat with Neovim CopilotChat.nvim brings GitHub Copilot's chat right into your editing flow. No context switching, no browser hopping — just type your prompt in a Neovim buffer and let the AI help you refactor code, write tests, or explain tricky functions. You can open the chat (for example) with a command like :CopilotChat , then provide extra context using built-in functions. That “extra context” is where the magic really happens. Built-in functio...
Read more

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo...
Read more