about summary refs log tree commit diff
path: root/modules
Commit message (Collapse)AuthorAgeFilesLines
* Remove/rename occurences of kde5aszlig2017-03-021-1/+1
| | | | | | | | | | | | | | This fixes the attributes accordingly to the following two upstream commits: * NixOS/nixpkgs@f21d4d00152726c02f870cb20faba4aca18ef49a * NixOS/nixpkgs@8eb4d2afbc1d61d316073f25f5885a46ccb37ea2 The first renames desktopManager.kde5 to desktopManager.plasma5 and the second one removes the kde5 attribute from the top-level packages set and puts applications in kdeApplications instead. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* machines/labnet: move wifi from base to labtopsProfpatsch2017-02-232-4/+5
| | | | | Non-laptop machines should not connect to the wifi automatically (they probably don’t even have a wifi module …)
* machines/profpatsch: enable tmpOnTmpfs by defaultProfpatsch2017-02-231-0/+4
|
* don’t start stackenblocken on bootOpenlab Hannswurscht2017-02-161-1/+1
|
* core/tests: Add a few missing callSubTests testsaszlig2017-02-161-0/+7
| | | | | | | | | | | | Haha, so that's what I got from introducing callSubTests in NixOS/nixpkgs@b3337edd0b77f04d0abe4a29642a5e4fdb4ad692. While in general this is an improvement, it makes it harder for vuizvui to gather tests that were added or removed. Maybe we should write an updater for this soon. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* core/tests: Update upstream NixOS testsaszlig2017-02-161-11/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | New tests as of NixOS/nixpkgs@b207bf523b8c49b037a4a87456d61f63043cd2c6: * containers-extra_veth * containers-hosts * containers-macvlans * containers-physical_interfaces * containers-tmpfs * glance * hound * keystone * leaps * mongodb * nat.firewall-conntrack * pam-oath-login * samba * sddm The following tests were removed: * kde4 * panamax I've also added a few checks on whether containers are actually enabled, because some tests like containers-bridge would run if containers with a bridge were defined but enableContainers was false. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* modules/fish/fasd: fix fish script bugProfpatsch2017-02-101-1/+1
| | | | | The function invocation apparently got less lenient, the function name *must* come first now, before any arguments.
* profiles/workstation: Make a few pkgs lazyaszlig2017-02-083-28/+32
| | | | | | | | Most of these packages I don't need for daily work and thus only clutter up the closure paths of those systems, so let's put them into lazyPackages. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* modules/core: Add a new module for lazy packagesaszlig2017-02-082-0/+68
| | | | | | | | | | | | | This allows to add packages to vuizvui.lazyPackages which then aren't directly installed onto the system but instead built by the Hydra and only fetched from it as soon as a binary of one of these packages is executed. Doing this only within a NixOS module however isn't enough, because by default gc-keep-outputs is false, so a garbage collect on the Hydra instance would remove the packages we wrap in vuizvui.lazyPackages. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* core/common: Revert force rebuilding GHC+packages.aszlig2017-02-071-8/+0
| | | | | | | | | | | | | | This reverts commit a93b7583084ff9084d73873d80d8dc428406593c. The issue isn't completely resolved but most of the packages should have been fixed that tripped the nondeterministic behaviour, see: https://ghc.haskell.org/trac/ghc/ticket/4012#comment:232 After having done some tests in the past I didn't stumble on this problem anymore so far, so let's give it a try. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* programs/gajim: Disable tests expected to failaszlig2017-02-071-0/+6
| | | | | | | | | We inject our own declarative config into Gajim by patching the source, which unfortunately kills a few tests which assume the default configuration, especially in terms of the GUI (for example the Vuizvui config has a single window GUI). Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* profiles/base: Fix build of nix-replaszlig2017-02-071-2/+5
| | | | | | | | Since NixOS/nix@21948deed99a3295e4d5666e027a6ca42dc00b40 nix::Pid::wait() no longer takes a boolean argument and is now blocking by default. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* modules/multipath-vpn: disable, definition brokenProfpatsch2017-02-051-1/+2
| | | | Apparently the defined options are now out-of-date.
* profiles/managed: Add simple-scanaszlig2017-01-191-0/+2
| | | | | | | Might be a good idea to have an actual application that can be used to scan stuff (apart from Gimp and others with SANE support). Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* t100ha: Rebase drm.patch against kernel 4.9.4aszlig2017-01-191-28/+16
| | | | | | | | | | | | | The following commit was introduced in kernel 4.9.3: * ASoC: cht_bsw_rt5645: Fix leftover kmalloc https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.3 This is the only commit that was dropped (because it was applied upstream) during this rebase. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* t100ha: Rebase drm.patch against kernel 4.9.4aszlig2017-01-191-41/+7
| | | | | | | | | | | | | | | | The following two commits were introduced in kernel 4.9.2: * drm/i915/dsi: Do not clear DPOUNIT_CLOCK_GATE_DISABLE from vlv_init_display_clock_gating * drm/i915/dsi: Fix chv_exec_gpio disabling the GPIOs it is setting See https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.2 for a full change log. So we no longer need these commits anymore, because they were applied upstream. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* aszlig/kernel: Fix up BFQ patch for kernel 4.10aszlig2017-01-121-2/+6
| | | | | | | | | | | | | First of all, using .patch from the GitHub compare view is not going to work because the concatenated diffs are in reverse order for use within "git apply". And the second thing why it's not working is that the patch has a hunk that changes the version in Makefile to add an extra version -rc1-bfq, which would only apply for kernel 4.10-rc1 but not for subsequent release canidates. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* machines/meshuggah: Set cyan color in promptaszlig2017-01-121-1/+13
| | | | | | | | | | | This is mainly to distinguish the prompt color from my workstations so it's clearly obvious that I'm working on meshuggah rather than say mmrnmhrm. We needed to add another option to the zsh module so that we can easily override machine colors for other machines as well. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* aszlig/kernel: Update BFQ to v8r7 for 4.10-rc1aszlig2017-01-121-2/+10
| | | | | | | | | | | | | The patch is from https://github.com/linusw/linux-bfq/tree/bfq-v8. It's a combined patch until the parent of the branch's head, because the latest commit is a work-in-progress commit. I have only tested evaluation and didn't test whether the patch actually applies yet, because the machines currently using the BFQ patch are broken because the old BFQ patch no longer applies for kernel 4.10. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* machines/managed: Implement a preliminary profileaszlig2017-01-022-0/+40
| | | | | | | | | | | | Currently I just needed to support HP printers and scanners among all the managed machines, so I thought it would be a good oportunity to start a common profile for end user machines. Right now there isn't that much factored out yet, but instead of copy & pasting the printer/scanner config into all three machines I'm putting it into the profile. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* hardware/t100ha: Remove workaround for vblankaszlig2016-12-171-20/+0
| | | | | | With the latest patches, this is no longer needed. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* hardware/t100ha: Fix install of brcmfmac paramsaszlig2016-12-171-1/+1
| | | | | | | | | Regression introduced by 4a27d62243942c4be181c7129fb532a709a15a8e. I've removed the fwbase variable in this commit, so the kernel is unable to completely load the WiFi firmware. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* hardware/t100ha: Switch to kernel 4.9aszlig2016-12-151-1/+1
| | | | | | | | After fixing the issues left we had since version 4.8, we can now safely switch to the latest mainline kernel. Turns out that the system is now a lot more stable and triggers less warnings and errors in dmesg. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* hardware/t100ha: Add patch for SST soundaszlig2016-12-152-3/+5640
| | | | | | | | | | | | | | This is essentially a backport of @plbossart's "experimental/codecs" branch against Linux 4.9. The original repository can be found at: https://github.com/plbossart/sound/commits/experimental/codecs Thanks to him for doing a lot of work on getting sound working for these CherryTrail devices. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* hardware/t100ha: Add Linux 4.9 fixes for intel DRMaszlig2016-12-153-226/+769
| | | | | | | | | | | | | | | | | | This is essentially a cherry-pick of the three commits mentioned in: https://bugs.freedesktop.org/show_bug.cgi?id=97529#c33 Plus a backport against Linux 4.9 of the following patch: https://bugs.freedesktop.org/attachment.cgi?id=128410 (essentially https://patchwork.freedesktop.org/series/16242/) And also the backlight.patch (a PMIC hack) we had before all combined into one patch, which now should fix the following bug: https://bugs.freedesktop.org/show_bug.cgi?id=97529 Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* Move taalo-build to workstation profileaszlig2016-12-151-0/+2
| | | | | | | I need this on all my machines, so nix-env'ing it on every machine on demand was getting tedious over time. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* programs/vim: Disable mouse supportaszlig2016-11-291-0/+1
| | | | | | | This one is annoying and it seems to be enabled by default in recent Vim versions, so let's get rid of it. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* dnyarri/mmrnmhrm: Switch to generic kernelaszlig2016-11-281-43/+20
| | | | | | | | | | | | | | | | | I've been patching these machines up since ages and I'm tired now to do both kernel configs *again* for the recent kernel versions. Of course, in the long run I still want them to have their customized kernel, but right now it's better to have a recent generic kernel rather than have a fucked up custom kernel. Also, this removes all that cruft for the Intel HDA pinning on dnyarri, because the machine now has two X-Fi sound cards. Both machines probably won't boot now, so we'll have to adjust a few things very soon. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* modules/gnupg: Support --supervised since 2.1.16aszlig2016-11-282-20/+52
| | | | | | | | | | | | | | | | | | | | | | | | See the release announcement at: https://lists.gnupg.org/pipermail/gnupg-announce/2016q4/000398.html Unfortunately we still need the wrapper, because we need to pick up the PID of the socket endpoint in order to gather various information we can pass to pinentry (which then for example can recognize that the actual SSH client is using X or is using a particular TTY). On the upside however, this is a step into a direction I didn't imagine to happen anytime soon, given the following statement from Werner Koch back then: https://lists.gnupg.org/pipermail/gnupg-devel/2014-November/029104.html However I don't think the way I'm picking up the PID and doing inspection of /proc/PID is going to happen in upstream GnuPG anytime soon. But after cleaning up and doing it as a patch I might now consider upstreaming it. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* modules/git: Fix/flesh out type for Git configaszlig2016-11-091-2/+3
| | | | | | | | | | | | | | We need to properly separate attrsOf from the nested attrsOf because otherwise the either type isn't able to distinguish between both types during merging of the subtypes. Now we have sub sections which is '[section "subsection"]' in Git's config syntax and attrsOf (attrsOf ...) on our side and simple sections like '[section]' which is just a plain attrsOf. This way we have an additional type constraint in that we can't mix up subsections with sections by the same name. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* profiles/packages: Revert using Chromium stableaszlig2016-11-091-1/+1
| | | | | | | | | This reverts commit 1fb2981f660b2155331cdac1b28640ba7c6b4786. Since NixOS/nixpkgs@c67a7ee73156796187894c63386b1a78e5902ea5, the Chromium beta channel builds fine again, so let's go back to beta. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* hardware/t100ha: Switch to use boot.kernelPatchesaszlig2016-10-271-12/+12
| | | | | | | | | | | | | | The implementation of boot.kernelPatches uses .override and passes back the original kernelPatches attribute to the patches that are going to be added from boot.kernelPatches. However, the T100HA module already uses .override to pass these patches but without re-using the existing patches. So instead of just adding preexisting patches to the kernelPatches attribute, let's just switch to boot.kernelPatches, which should also allow overrides and introspection from different NixOS modules. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* hardware/t100ha: Fix evaluation erroraszlig2016-10-271-1/+1
| | | | | | | The right attribute is vuizvui.kernel.linux_4_7 and not vuizvui.linux_4_7. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* hardware/t100ha: Bring back Linux 4.7.10aszlig2016-10-271-1/+1
| | | | | | | | | | | | | | Removed in NixOS/nixpkgs@b3f7d626c164ae591a067f78bfcbb06fc3a588b9. We are currently stuck in 4.7 with the T100HA because of this upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=97529 So let's bring back the expression for Linux 4.7 until there is time for debugging the mentioned bug. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* pkgs: Rename "kpatches" directory to "kernel"aszlig2016-10-271-1/+1
| | | | | | | | | This now should reflect "all things kernel" and thus could not only contain patches but other things. If we have so many patches that it makes sense to namespace them further, we can still use kernel/patches for that purpose which is way better than "kpatches". Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* modules/i3/conky: Fix weather URLaszlig2016-10-181-1/+1
| | | | | | | The URL has changed, see brndnmtthws/conky#325 for the fix in upstream conky. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* Revert "runCommand -> runCommandCC"aszlig2016-10-171-2/+0
| | | | | | | | | | | | | This reverts commit e3f8d28d6be67257d70035d122263f3a35adc438 and my attempts to mitigate this in 0a50f5fab1abf2e70fd5d7a2dd717c2f2c1b983b and 3b91f25b37ea709f5c86e38a50061199bbed5341. Vuizvui is a repository for experimental stuff, but NOT a dumpster. So please refrain from pushing waste into this repository, like markers for a failed merge. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @Profpatsch
* Fix evaluation of module listaszlig2016-10-171-1/+2
| | | | | | | | | | | Regression introduced by e3f8d28d6be67257d70035d122263f3a35adc438. Another time where a commit references files without actually adding them. So let's remove the missing module from the module list and let only those machines break which are actually using it. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @Profpatsch
* runCommand -> runCommandCCProfpatsch2016-10-151-0/+1
|
* hardware/t100ha: Fix support for SDIO WiFi cardaszlig2016-10-133-0/+64
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | While I had terse Internet connectivity these days, I haven't checked T100HA hardware related news/patchs very often. Meanwhile a small patch by @tagorereddy popped up on hadess/rtl8723bs#80 which works around the SDIO detection. On some devices the BIOS has an option to map the SDIO controller to PCI instead of ACPI, but the T100HA doesn't have this option. IIUC the issue here is that the controller is already being attached via PCI device ID 80862280, which prevented the platform device from being attached via ACPI. The patch circumvents that by removing PCI device ID 80862280 while probing for ACPI devices in SDHCI (yes, very hacky but works) and forces the ACPI platform device to be initialized if the HID is 80860F14:02. I've rebased and tidied up the original patch a bit to prevent warnings during build. Other than this patch, we now need to add the right firmware and the corresponding parameters to hardware.firmware, so that the actual driver for the WiFi card can be loaded. The firmware parameters are stored in EFI on the host itself: /sys/firmware/efi/efivars/nvram-74b00bd9-805a-4d61-b51f-43268123d113 So I added a copy of it to prevent impurities. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* profiles/packages: Temporarily use Chromium stableaszlig2016-10-131-1/+1
| | | | | | | | | | Chromium's beta channel doesn't build for quite a while because the GYP stuff is heavily broken in beta and dev and we need to move to GN instead. So until that's done I'm going with the stable channel for now. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* kernel: Switch to use boot.kernelPatchesaszlig2016-10-132-10/+4
| | | | | | | | Since NixOS/nixpkgs@da36847d925058fd86f027b64cc712c57be11ad8 we no longer need so much cruft to specify kernel patches, so let's switch to boot.kernelPatches instead of the hackery we had so far. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* programs/gnupg: Use runCommandCC for wrappersaszlig2016-10-091-2/+2
| | | | | | | | | | Since NixOS/nixpkgs@97bfc2fac92d90c668ae1ec078356d0bd0a9ddb7, runCommand uses stdenvNoCC, so we don't have a compiler available anymore. However, there is now a runCommandCC function which does exactly what we want. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* gajim: Revert "Fix against GnuPG 2.1.13"aszlig2016-10-092-62/+1
| | | | | | | | | This reverts commit f0003b92674a1f4555dd14ffa271622a3889cd84. Gajim 0.16.6 has been released last week and it includes a fix for GnuPG 2, so we no longer need this patch. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* hardware/t100ha: Pin kernel to Linux 4.7aszlig2016-09-161-21/+1
| | | | | | | | | Kernel 4.8 currently has an Intel GFX regression right now, so let's keep it at kernel 4.7 until we have properly bisected the issue and/or have a fix for this. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Upstream issue: https://bugs.freedesktop.org/show_bug.cgi?id=97529
* profiles/workstation: Remove RXVT-specific optionsaszlig2016-09-121-11/+0
| | | | | | | I didn't use RXVT for years now, so it doesn't make sense to set options for it here. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* modules/gnupg: Fix path to libsystemd.soaszlig2016-09-111-1/+1
| | | | | | | The systemd library has been splitted off into a different output in NixOS/nixpkgs@78178d5854901e1b17a14bce3fe43515984b7b91. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* core/tests: Add and remove upstream NixOS testsaszlig2016-09-111-6/+10
| | | | | | | | | | | | | | | | | New tests as of NixOS/nixpkgs@4ac7b7d5deb4a2ccf291c1251ff7515f1ab17c82: * nixos.kde5 * nixos.ferm * nixos.quagga The following tests were removed: * nixos.dockerRegistry * nixos.sddm The test for SDDM is now included within the KDE5 test. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* hardware/rtl8192cu: Update to latest Git masteraszlig2016-09-072-19/+2
| | | | | | | The upstream repository now has support for kernel 4.x, so we no longer need the patch. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* hardware/rtl8192cu: Disable some hardening flagsaszlig2016-09-071-0/+2
| | | | | | | | These flags are applied via the kernel config, so if we add it using our compiler wrapper the kernel build process is unable to detect these flags and the build will fail. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-30 22:03:23 +0000