| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
The URL has changed, see brndnmtthws/conky#325 for the fix in upstream
conky.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
The systemd library has been splitted off into a different output in
NixOS/nixpkgs@78178d5854901e1b17a14bce3fe43515984b7b91.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
The upstream repository now has support for kernel 4.x, so we no longer
need the patch.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
I'm regularily using rsync and xhost sometimes, but the latter is a very
small package, so I don't mind having it in systemPackages.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
The "docdev" output has been removed in upstream nixpkgs at commit
NixOS/nixpkgs@e84a3524b5eaa03521bfbd5c67caec883ef76011.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
| |
I'v been regularily adding those packages to my user environment, so
let's add them to systemPackages so they are available all the time.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
People needed it, so now it goes into the config.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
I'm not sure whether this was a single setting in the configuration file
prior to Starbound version 1.0 but it has more settings now that affect
how those safety checks are performed.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
| |
This option has been added in the nightly prior to Starbound 1.0.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
| |
These options are only a one-off setting that's causing the player and
universe files to be cleared on server startup. The service populates
all options declaratively while this option is something that IMHO
doesn't fall into this category, not to mention I fail to see why this
would have an advantage over deleting those files using the command
line.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
The new option seems to be allowAssetsMismatch and the checkAssetsDigest
doesn't seem to be referenced anywhere in the Starbound binaries except
within the default configuration templates.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
This one was a bit difficult to find on the web so I had to ask in IRC
(person and channel not to be disclosed here) for what this option does
exactly.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
This option is no longer used in version 1.0.5. I've searched the server
binary for anything related to this and in older versions there even was
UpnpHolepuncher, which is now gone entirely.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
| |
The semantics of the boot configuration has changed in version 1.0 and
also in the way we package Starbound, so we no longer need to use jq to
mix in our values and can specify the entire bootconfig in the service
module.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
The Steam version is old anyway and since we've reached 1.0 there is no
point in extracting it from Steam anymore.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using xset for DPMS control only works as soon as we have an X session,
but we want to work around the issue as early as possible so let's set
it in preDeviceCommands.
The program here directly uses the ioctls to blank/unblank the current
console without enums/constants (14 is blank and 4 is unblank) because
it's just a workaround and supposed to go away in the near future.
If we'd wanted to use the constants from tiocl.h, we'd have to add
dependencies on Linux headers, but I'm lazy right now ;-)
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
| |
This reverts commit bafb5933654cdb7e35f0c54418bdd0dcb999f98c.
We can finally drop that patch, because the issue has been fixed
upstream already.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
| |
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 3f0a9e8002802e5a772b7582f8254c92d7a2a4d5.
It's now possible to disable support and tests for containers simply by
using config.boot.enableContainers in the machine config, because that's
the super option that enables all the container-related services and
tools in upstream NixOS and it's also enabled by default.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
| |
New tests are since NixOS/nixpkgs@4f796c28d57887cc9812190bc99fb45b2a.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
| |
This was a copy & paste error by me, because I copied the options out of
an existing configuration, which contained the CONFIG_ prefixes. Within
extraConfig of the generic kernel builder, we only use the names without
prefixes.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 9d4575855bf1ae2136d85a2d0aa7b5ede50cfc67.
The upstream issue systemd/systemd#3735 has been fixed and it got
included in systemd version 331.
Since NixOS/nixpkgs@51871dfb3777 we're also on version 331, so we
no longer need this patch in Vuizvui.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts the following commits:
4f4c778e424e72d51242dbfadde0a2a806efb68b
22fac6bad53e797ca84d7c7ac7e0fca3c0a912c8
We can now move Tomahawk back to the corresponding profiles/machines,
because the build has been fixed in f7e934e74595a0d7524159d6faa1b2bb5d.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
| |
Let's enable the options that *should* work with this kind of hardware
regardless whether it's currently working in mainline. It doesn't make a
huge difference to the kernel configuration prior to this change, but
let's better compile in these options rather than wondering why some
hardware isn't working.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
This is to get a first working channel for bootstrapping. Fixing the
test is the long-term goal of course, so this is only temporarily.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
Due to bandwidth constraints I'm not using Tomahawk at the moment and I
don't have time to investigate the current build failure.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
Gah, yes, I'm still waking up and my eyes are not working already...
Accidentally copy & pasted tho wrong hash in there.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|