nixos

1262 readers

1 users here now

All about NixOS - https://nixos.org/

founded 4 years ago

How do I add a udev rule in NixOS to set my AMD GPU's performance level to 'high' ? (lemmings.world)

submitted 8 months ago by [email protected] to c/[email protected]

4 comments fedilink hide all child comments

So I have been experiencing screen blackout when I use any refresh rate above 60Hz. On Arch I was able to solve this by setting a udev rule as mentioned in this ArchWiki article but it seems like I can't do the same in NixOS using the traditional way. Is there anything I need to add in the configuration.nix file to achieve the same ?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 7 months ago (1 children)

Hi, hope you've found a solution by now. Came across this thread randomly, thought I'd share.

  services.udev.extraRules = ''
    SUBSYSTEM=="drm", KERNEL=="card0", DRIVERS=="amdgpu", ATTR{device/power_dpm_force_performance_level}="high"          
  '';

I'm using an RX6700XT iirc, been having issues with it since day one. Somewhat random DE crashes. For the longest time I ran with only this, and not the above:

      kernelParams = [     # https://gitlab.freedesktop.org/drm/amd/-/issues/1974
      "nvme_load=YES"
      "amdgpu.ppfeaturemask=0xfffd3fff"
      "amdgpu.noretry=0"
      "amdgpu.lockup_timeout=1000"
      "amdgpu.gpu_recovery=1"
      "amdgpu.audio=0"
    ];

disclaimer: I've no idea what this does but it works for me

I'm not sure if the high-power udev rule improved anything, but for me electricity is cheap and my will to troubleshoot ran out.

right now I'm having issues with my monitors blinking at times. My 2nd monitor especially, sometimes 10 'disconnects' in less than a minute, but often hours without a single one.

I've kinda settled on just accepting not knowing exactly what's wrong, cause I'm not sure if it's a bad GPU, bad config, wayland or hyprland screwing me over, and I'm kinda more overwhelmed by learning it than the problem itself.

hope this is of value for someone!

[–] [email protected] 2 points 7 months ago

I added the udev rule, but the issue was still happening when I resume after a suspend.

Strangely enough, I have not seen the issue since a clean install with only hyrpland (no Desktop environment installed alongside). No change to the rest of my config.

I had the same experience on Arch as well.