| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As mentioned in the initial commit (e73fcff03faed773df2500965cb9c4a4fc),
the machine was only temporary as a substitute for tishtushi.
Since slylandro had a pretty slow dual core CPU and its own quirks, this
was never a long-term solution and for the time being my intentions are
to work with dnyarri's new hardware until I have a less annoying setup
when I'm on the road again.
While writing this message, slylandro just died a gruesome death with
"cryptsetup erase", followed by "blkdiscard" on the whole drive.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
| |
After all the goal was to move all hardware specific stuff to the actual
machine definition, which includes the boot loader.
Since GRUB is enabled by default but with a higher priority value, we
now no longer need to mkForce-disable the option for machines using
systemd-boot.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
| |
The new hardware for dnyarri no longer contains an Intel CPU, so apart
from switching the microcode updates to AMD I also removed the setting
from the base profile because it clearly doesn't belong there.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
Since Tishtushi had a SSD failure and thus became a majoor nuisance to
work with, I got a temporary laptop from someone (since I don't know
whether they want to be mentioned, I leave out their name for now) in
order to be able to be more productive than waiting for several seconds
for a 1 KiB text file to be saved.
Right now, I'm not sure whether any firmware is needed for the temporary
laptop, so this is a hardware configuration just to get started with a
proper Hydra channel.
Signed-off-by: aszlig <aszlig@nix.build>
|
