Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nvidia open: driver won't start after update 570.124.04 #387592

Closed
3 tasks done
LachCrafter opened this issue Mar 6, 2025 · 9 comments
Closed
3 tasks done

nvidia open: driver won't start after update 570.124.04 #387592

LachCrafter opened this issue Mar 6, 2025 · 9 comments
Labels
0.kind: bug Something is broken

Comments

@LachCrafter
Copy link

Nixpkgs version

  • Unstable (25.05)

Describe the bug

The operating system will load but the drivers won't on startup.
When I switch to a tty, the nvidia drm gives the an error shown down below.

Steps to reproduce

  1. install the latest open nvidia driver package on nixos-unstable
  2. restart

Expected behaviour

The drivers load

Screenshots

No response

Relevant log output

[drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip Event timout on head 1

Additional context

No response

System metadata

  • system: "x86_64-linux"
  • host os: Linux 6.13.5, NixOS, 25.05 (Warbler), 25.05beta762848.d69ab0d71b22
  • multi-user?: yes
  • sandbox: yes
  • version: nix-env (Nix) 2.24.12
  • channels(root): "nixos"
  • nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Notify maintainers

No response

I assert that this issue is relevant for Nixpkgs

Is this issue important to you?

Add a 👍 reaction to issues you find important.

@LachCrafter LachCrafter added the 0.kind: bug Something is broken label Mar 6, 2025
@gtebbutt
Copy link

gtebbutt commented Mar 6, 2025

I'm getting a similar issue with a slightly different error on the same driver version:

[    6.599434] [drm] [nvidia-drm] [GPU ID 0x00000300] Loading driver
[    7.459290] [drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000300] Failed to allocate NvKmsKapiDevice
[    7.459999] [drm:nv_drm_register_drm_device [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000300] Failed to register device

Looks like there are one or two reports of similar problems in the NVIDIA forum, but I couldn't see any helpful answers there.

@LachCrafter
Copy link
Author

Fixed for me in latest kernel release.

@ajgon
Copy link
Member

ajgon commented Mar 16, 2025

@LachCrafter Can you say which driver and which kernel did you use? I tried both nvidia stable and latest with most recent pkgs.linuxPackages_6_12 (which is 6.12.19) and pkgs.linuxPackages_6_13 (which is 6.13.7) from nix "unstable" branch, and still getting this error.

@gtebbutt
Copy link

Not OP, but I'm no longer getting the error I mentioned above, or any dmesg error I can see - I'm now using driver 570.124.04 on kernel 6.12.17 (clean install from nixos-unstable about a week ago). I'm also not getting any display output at all after the scroll of boot text, so there's definitely still something wrong on my install, though; same config was working fine using nixpkgs 24.11 on an older GPU.

I'm using it for CUDA work, and running that over SSH seems fine even without the display working, so I haven't done any real debugging beyond that yet. Was planning to try reinstalling once NVIDIA release the next iteration of the driver.

@LachCrafter
Copy link
Author

LachCrafter commented Mar 17, 2025

This seems to start happening too after a restart when changing the display refresh rate.
It seems to be an issue mostly with the driver.

@LachCrafter LachCrafter reopened this Mar 17, 2025
@LachCrafter
Copy link
Author

LachCrafter commented Mar 19, 2025

Nvidia released the 570.133.07 driver yesterday, it provides a few fixes. I will give it a try.

@ajgon
Copy link
Member

ajgon commented Mar 19, 2025

570.133.07 worked for me without any issues, so looks like it was a bug in a driver 🥳

@gtebbutt
Copy link

gtebbutt commented Mar 20, 2025

Also now working on 570.133.07, but I did initially need to set

services.xserver.resolutions = [
    {
      x = 1024;
      y = 786;
    }
  ];

in order to get any display output. Changing it to 1920x1080 after gnome had loaded was then fine, but trying 4K hard crashed the system (couldn't even SSH in to reboot, needed to physically power off). That last issue could plausibly be a flaky HDMI cable given that it's now stable at 1080p with the new driver, where previously I wasn't able to get a display output at all.

@LachCrafter
Copy link
Author

The new release fixed my initial issue too. I'm closing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.kind: bug Something is broken
Projects
None yet
Development

No branches or pull requests

3 participants