about summary refs log tree commit diff
path: root/machines/devhell/herja.nix
Commit message (Collapse)AuthorAgeFilesLines
* machines/devhell: maxJobs -> max-jobsdevhell2022-03-021-2/+2
|
* treewide: Rename packagesdevhell2022-03-021-2/+2
| | | | More packages have been renamed recently.
* {machines,modules}/devhell: nix.* -> nix.settingsdevhell2022-02-011-2/+2
| | | | | Second attempt at getting this right. Step 1: Read the thrown assertions. Step 2: Don't be tired. Step 3: Test changes.
* Revert "treewide: rename nix.* to nix.settings.*"devhell2022-02-011-3/+1
| | | | This reverts commit 20ee65d79602b6412994dc52907715b274daeebe.
* Revert "machines/herja: Up maxJobs to 16"devhell2022-02-011-1/+1
| | | | This reverts commit 2332e49b29528325ad1ff2bc0a279275c08ea266.
* machines/herja: Up maxJobs to 16devhell2022-01-301-1/+1
| | | | Dunno why it was at 8, but 16 is what it should be.
* treewide: rename nix.* to nix.settings.*devhell2022-01-301-1/+3
| | | | | This must have been a recent change where an assert is now thrown because some nix.* settings have been regrouped as nix.settings.*
* {machines,modules}/devhell: Switch to Nix 2.4devhell2021-11-151-3/+0
| | | | | This commit also includes a bit of drying the `auto-optimise-store` Nix option.
* machines/herja: Remove thermalddevhell2021-09-251-1/+0
| | | | | | I didn't notice this at first, but `thermald` only really works for Intel CPUs. This is an AMD machine, and the daemon can't find anything to work with, so there's no point in keeping it enabled here.
* machines/{herja,gunnr}: Remove BFQ IO Schedulerdevhell2021-07-031-1/+0
| | | | | | | | | Both, `herja` and `gunnr` have no spinning rust in them, and so they won't need bfq anymore. According to this old benchmark, the `none` scheduler works overall better for most workloads than other schedulers[1]. [1]: https://www.phoronix.com/scan.php?page=article&item=linux-56-nvme&num=1
* machines/herja: Remove ROCm in OpenGLdevhell2021-06-131-2/+0
| | | | | As it turns out, rocm isn't supported on integrated Ryzen GPUs. No point of having it around on herja then.
* machines/devhell: services.gnome3 -> gnomedevhell2021-05-171-1/+1
| | | | It's been renamed recently and throws a warning saying as much.
* Revert "machines/herja: Add pulseaudio for pactl"devhell2021-04-181-1/+0
| | | | | | | There's no need for this as I've reverted back to `pulseaudio` for the time being. This reverts commit a520414825f672eadd25017f06bf13fb9de2db8d.
* machines/herja: Add pulseaudio for pactldevhell2021-04-171-0/+1
| | | | | | | | While I'm generally happy with `pipewire`, some things broke, such as volume control. I've tried to fix it using a range of front-ends for PA, but so far only `pactl` seems to be behaving correctly (but broke mic mute again). I might have to switch back to PA in the end as it's also broken my setup on gunnr somewhat.
* machines/herja: Force use of amdgpudevhell2021-04-171-2/+4
| | | | | | | Every boot the kernel will silently dump some a trace referencing an issue with AMDGPU. Some sleuthing suggests that the module needs to be loaded much earlier. Funnily NixOS actually has a wiki specifically on AMDGPU, so these settings have been taken from there.
* machines/herja: Switch back to iwddevhell2021-04-071-3/+2
| | | | | | | | Finally, after a lot of hussle with the IT department they've come to the conclusion that, in fact, their eduroam cert was not generated properly thereby preventing me from using iwd. It looks like this only affected a minority of devices (presumably those with proper implementation).
* machines/{gunnr,herja}: Unify opengl.extraPackagesdevhell2021-04-041-1/+0
|
* machines/*: Default to original configurationdevhell2021-03-251-1/+0
| | | | Let's keep it simple, everything else seems to just end in tears.
* machines/devhell: Once again remove syncthing dataDirdevhell2021-03-191-1/+0
| | | | Sigh.
* machines/devhell: Change syncthing dataDirdevhell2021-03-191-1/+1
| | | | | So the previous idea didn't work as expected, instead I'm going to use the directory name Syncthing would use anyway.
* Revert "machines/devhell: Remove syncthing dataDir"devhell2021-03-191-0/+1
| | | | This reverts commit d46aa4ec882dcb9ac0e09da6e1aecb361d90d287.
* machines/devhell: Remove syncthing dataDirdevhell2021-03-191-1/+0
| | | | | This doesn't seem to work properly, Syncthing will still add its default `Sync` directory.
* machines/herja: Disable light programdevhell2021-03-041-1/+1
| | | | | | | | | I've been using `illum` to make the screen brightness keys work on this machine. It's better than invoking light manually or via a xbindrc call. Although, `illum` is a bit outdated in nixpkgs, and I'm guessing that's the reason why it crashes when the machine boots. After restarting the service it's fine. If `illum` isn't updated in nixpkgs soon, I'll have a look at it.
* Revert "machines/herja: Add non-functioning mute btn event"devhell2021-03-011-10/+0
| | | | | | `xbindkeys` seems to be the solution, at least via user-space. This reverts commit 59dbc84cb214ed3df6506e95d3bf59b89f9d3548.
* machines/herja: Add non-functioning mute btn eventdevhell2021-03-011-0/+10
| | | | | | For some reason this doesn't work yet. It works fine when run manually as root or my own user, but when acpid runs it nothing happens. Dunno yet why.
* machines/herja: Replace unnecessary cups packagesdevhell2021-02-251-1/+1
| | | | No more Brother crap.
* machines/herja: add rocm-opencl-icddevhell2021-02-251-1/+6
| | | | I don't know what I'm doing, but it's fun.
* machines/herja: Add "sometimes" different ethdevhell2021-02-231-0/+1
| | | | | So, turns out that enp6s0f3u1 sometimes also is initialised as enp6s0f4u1. Why? WHyyyyyyyyy?????
* machines/herja: Fix external eth interface namedevhell2021-02-231-1/+1
| | | | Dunno why I thought it was the former.
* machines/herja: Add Ethernet dongle interfacedevhell2021-02-221-0/+1
| | | | | The T14s is an awesome machine, but unfortunately it needs an Ethernet dongle.
* machines/herja: Fine-tune configurationdevhell2021-02-081-24/+17
| | | | | | | | After some experimentation and looking at the NixOS' hardware repo, this configuration seems to work quite well. There are no major issues to worry about for now. This is also the first machine where `fwupd` is available and working.
* machines: Add herjadevhell2021-02-011-0/+197
Shiny new machine needs NixOS love. <3