| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
Seems like upstream fixed this header related issue in the meantime (or
someone worked around it in nixpkgs).
|
| |
|
|
|
|
|
|
|
|
| |
This is the old racker machine, but needs to be re-installed (hence the
updated stateVersion) and is renamed more consistently. This has not
much set up yet, trying to get binary cache up for the first install.
cc @aszlig, LMK if this is an unreasonable burden on the builders.
|
|
|
|
| |
I re-created the swap for some reason, so this needs to be reflected.
|
|
|
|
|
|
|
|
|
| |
I've been testing PipeWire on this machine for quite a while and it
works pretty well so far. My goal is to switch all my machines to it,
but since Dnyarri currently has a pretty complicated audio setup I
decided to not make it the default for the workstation profile yet.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
| |
I do have location.latitude and location.longitude set in my workstation
profile, but since Slylandro is a laptop that frequently changes
location it makes sense to automate this in a way that I don't need to
manually set the location every time I switch places.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
While I do use redshift to decrease the brightness at night, I also tend
to sometimes use the laptop when barely awake. Having a convenient CLI
makes it easier to script, eg. "mpv somefile; light -S 0".
The reason why I did not add this to my generic workstation profile is
because my workstations are usually placed in a way that I need to be
awake enough to approach them.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I never got really used to the "buttonareas" click method and while
"clickfinger" does have some disadvantages (eg. dragging is much more
difficult without drag lock), in most other cases I find the clickfinger
method a lot more convenient, since it usually only requires one hand to
operate.
Since we have clickfinger enabled, I also don't see a point in enabling
middle click emulation since three fingers already count for a real
middle click.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
Another one of the attributes that got renamed from xdg_utils to
xdg-utils a while ago[1] and which now[2] throws an evaluation error.
[1]: https://github.com/NixOS/nixpkgs/commit/a6ac3eedbd197746dae3be74d3a
[2]: https://github.com/NixOS/nixpkgs/commit/d06207386df9a53fe01f8a30130
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @sternenseemann
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The gnome3 attribute got renamed a while ago[1] and a recent change[2]
now causes an evaluation error when it's used, so let's rename it to
just "gnome".
[1]: https://github.com/NixOS/nixpkgs/commit/468cb5980b56d348979488a74a9
[2]: https://github.com/NixOS/nixpkgs/commit/d06207386df9a53fe01f8a30130
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
| |
This actually consists of several modules which are of poor code
quality, none of them however are essential for the TUXEDO Pulse 15
because its keyboard backlight is single color so let's drop them since
they just taint the kernel for no reason.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After resume from suspend the NVMe does not wake up again when the
device was put into D3cold. This is something that is worked around by
TUXEDO Tomte[1] via udev rules. However, I personally don't like this
approach and it can lead to race conditions when we're going into
suspend before udev is initialised.
Interestingly, the device does even go into NPSS via APST, but if
changing to D3cold while APST is enabled, the device does not wake up
again.
Right now I just added a new quirk to disable D3cold during device
probe for now, but we could maybe find a better workaround eg. by
disabling APST before D3cold and re-enabling it again. Not sure whether
this is feasible, but since I have limited time right now I can't dig
more into this.
[1]: https://github.com/tuxedocomputers/tuxedo-tomte/commit/2c8d71170868a2663705fbea6ac150eecb96e6ce
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Most of the options in nix.conf are now exposed as a submodule with a
freeform type and since that change[1] got introduced, we get a bunch of
warnings during machine evaluation:
trace: warning: The option `nix.useSandbox' defined in `...' has been renamed to `nix.settings.sandbox'.
trace: warning: The option `nix.maxJobs' defined in `...' has been renamed to `nix.settings.max-jobs'.
trace: warning: The option `nix.buildCores' defined in `...' has been renamed to `nix.settings.cores'.
To shut them up, I went through all machines and modules and renamed the
remaining options that were not renamed back then when @devhell did some
renames in a0297bf921399c3243dcca99626d8697f0735abe.
This was done by looking through the output of:
$ git grep -A 10 '\<nix\(\.\| *=\)' machines modules
After that I tested the contents of the nix.conf of all the machines
against the changes this commit introduced via the following command:
$ nix-build --no-out-link -E '
with import <nixpkgs/lib>;
map (m: m.eval.config.environment.etc."nix/nix.conf".source)
(collect (m: m ? eval) (import ./machines))
'
I've sorted the resulting nix.conf files and diffed on that result and
the only difference that showed up was the following:
allowed-users = *
-auto-optimise-store = false
auto-optimise-store = true
builders-use-substitutes = true
cores = 0
This is because the previous way to generate the config was by
concatenating strings whereas the new way works on an attribute set, so
we get deduplication by design.
[1]: https://github.com/NixOS/nixpkgs/pull/139075
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @devhell
Cc: @Profpatsch
Cc: @sternenseemann
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I already killed that machine on 2022-08-04:
tishtushi[~]0> cryptsetup erase /dev/sda2
WARNING!
========
This operation will erase all keyslots on device /dev/sda2.
Device will become unusable after this operation.
Are you sure? (Type 'yes' in capital letters): YES
tishtushi[~]0> cryptsetup erase /dev/sda3
WARNING!
========
This operation will erase all keyslots on device /dev/sda3.
Device will become unusable after this operation.
Are you sure? (Type 'yes' in capital letters): YES
Since some of the hardware was already broken (touchpad, keyboard, HDD,
SSD and webcam), I hardly doubt that I'll use it again so it makes sense
to remove the config here.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
The machine no longer exists, so it doesn't make sense to continuously
build it on Hydra.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
The amdgpu module is initialised at roughly the same time as the X
server, which sometimes leads into race conditions where X won't start
because the kernel driver is not yet loaded.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
This is a custom kernel module for TUXEDO laptops, which allows to
control the backlight. I haven't played around with its settings yet,
but having the module available helps with that.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
| |
This is needed for the GPU and the WiFi adapter.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
I'm used to a TypeMatrix keyboard, where caps lock is only a small key
on the side instead of being prominently placed atop switch.
Slylandro's internal keyboard however has that pesky caps lock key
directly atop the left shift key and I'm constantly triggering it by
accident.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
This makes the screen readable again, but might get us into trouble when
switching to an external display. Again, similar to enabling bonding in
the previous commit, let's find out :-)
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
| |
This is mainly because I want to have a seamless transition between
both, at least in theory. Whether this will work out to be so smooth
when trying it on various networks out there remains to be seen, but
let's try it :-)
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've already got a temporary laptop back then where I used the same name
and I introduced it in e73fcff03faed773df2500965cb9c4a4fcfbc04d and
subsequently removed it in 240378dcec205b78b32c329ff02eb9bea8af2c11.
With the new permanent hardware having arrived today, I decided to reuse
the name, because it sounds nicer than "tishtushi" (which is my crappy
laptop) and I also like the Slylandro Probes[1] a lot in Star Control.
The configuration here is pretty much bare-bones as we had before with
the temporary hardware and it's essentially a remix between dnyarri and
the old config, more to refine later...
[1]: https://wiki.uqm.stack.nl/Probe
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
| |
See https://github.com/NixOS/nixpkgs/pull/177318 for the lovely change
that causes your locales to disappear.
|
| |
|
| |
|
| |
|
|
|
|
| |
No! bad subvolume! bad!
|
|
|
|
|
|
| |
I had them copied from the wrong module, of course this can’t work.
Since the kernel config & boot loader config is now in thinkpad, this
might just work (famous last words).
|
|
|
|
|
| |
Not sure about the boot loader config, but I guess it’s okay for now,
since it doesn’t diverge anyway.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
I use all of that on a regular basis.
Earlyoom makes sense for any kind of machine without swap, which is
all of my machines.
|
|
|
|
|
| |
I want to have a thinkpad-based server, which will need the
thinkpad-specific stuff but none of the workstation stuff.
|
|
|
|
|
|
|
|
| |
Not updating the microcode on thinkpads is kind of a death sentence
for some kernel updates, so let’s do it by default.
In case somebody uses it for an AMD thinkpad in the future, we might
have to check whether the option creates a problem.
|
|
|
|
|
|
| |
Apparently one of its python dependencies went EOL and everything went
to fuck because python is a crapfest and nixpkgs policies around it
are stupid. yay.
|
| |
|
|
|
|
|
| |
This is not pretty, some of the code lives in vuizvui, some lives in
tvl depot. But at least it seems to work for now :)
|
|
|
|
| |
though the backup service is broken on the machine anyway, idk
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Changes the weechat setup so that I can have multiple instances, each
gets their own unix user & separate weechat instance.
|
| |
|
| |
|