nixos-search VS steam-devices

For me, https://search.nixos.org/ is a better aid than the wiki. Often the right keyword in the NixOS packages or modules search will lead me right to the obvious and simple answer that I couldn't find elsewhere.

Does https://search.nixos.org/ pull from nixpkgs, the Nix User Repository, or both?

Just go to search.nixos.org, open the option you would like to see more of, and click on the link behind "Declared in".

I've done a nix-env query, and checked in https://search.nixos.org but can't seem to find any SAR package, nor any google search that gave any hints to see if it might be part of another system utility package...

If you want to install a package, search for it at https://search.nixos.org

The gnome system monitor is gnome.gnome-system-monitor for example https://search.nixos.org/packages?channel=23.05&show=gnome.g...

search.nixos.org also includes flakes that people PR into the index via GitHub at https://github.com/NixOS/nixos-search/issues

ps: $ nix search exists via experimental flags https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3...

Idk about ec_sys, I couldn't find it on search.nixos.org, but since it's a kernel module it might just come with the kernel idk.

I rarely think to look at flakes by their source, actually. I have a Nixpkgs clone that I jump into for anything super ad-hoc but most of the time I'm just doing REPL, :lf ./. and mashing tab-completion. That's usually to make sure the thing I'm after exists in one of the large package sets like node, vimPlugins, or similar, and that I got the name right - which could probably be answered just as easily with https://search.nixos.org/ .

search.nixos.org

if you mean this ( https://github.com/ValveSoftware/steam-devices/blob/master/60-steam-input.rules ) in /etc/udev/rules.d , yes i did

Create an udev rule for the device, you can copy the rule for your device from here.

I am attempting to play Spelunky with a controller but I am not having any luck. Spelunky has a platinum rating on protondb and runs as expected. I am in a flatpak and I did install the udev rules from valve if any of that makes a difference. My controller works fine in native games.

I solved the problem by copying the 60-steam-input.rules file to the folder: /etc/udev/rules.d

this is their Github: https://github.com/ValveSoftware/steam-devices

steam maintains udev rules for controllers that might help: https://github.com/ValveSoftware/steam-devices/blob/master/60-steam-input.rules

Here is my open PR for the hori alpha for reference: https://github.com/ValveSoftware/steam-devices/pull/42/files

To use a controller with the Steam flatpak, you need to layer the steam-devices package from RPM Fusion, or download the udev rules from upstream and install them to /etc/udev/rules.d/ (which is what I did).

> The effort you need to go through to actually use these depends on how your distribution handles the file permissions of /dev/uinput. Some of them have it as root:input, in which case you just need to usermod -a -G input and then relog to get it working. Others have it as root:root so you either need to go do some reconfigurations to change its permissions or live with running the software using it as root.

There's a trick to that. The TL;DR is "install the steam-devices package or similar" (https://github.com/ValveSoftware/steam-devices/), which adds the following udev rule (and others, but this is the relevant one):

  # Steam Controller udev write access