| Age | Commit message (Collapse) | Author |
|---|
|
This reverts commit 82a3d8b78629c66ebe2c0ace462d32532ac30e9f.
|
|
Akashi system needs to have fan control enabled and customized.
By default, the firmware fails to adequately cool the computer which results in thermal throttling.
---
The goal is to have the laptop fan run at high speed at all times, regardless of CPU temperature.
---
[x] Enable fan control in thinkpad_acpi module.
[x] Set fan speed to level 5.
---
This commit adds an appropriate entry to the kernel command line to set the fan speed level.
---
Akashi system will now adequately cool itself in most circumstances.
|
|
Akashi system needs to have fan control enabled and customized.
By default, the firmware fails to adequately cool the computer which results in thermal throttling.
-----
The goal is to have the laptop fan run at high speed at all times, regardless of CPU temeperature.
-----
[X] Enable fan control in thinkpad_acpi module.
[ ] Set fan speed to level 5.
-----
This commit adds an appropriate entry to the kernel command line to enable fan control.
The goal of the series is now to set level 5 fan speed, as it is more pleasing to the ear.
-----
Akashi system will now allow fan control without havind to reload thinkpad_acpi module.
|
|
Akashi system needs to have fan control enabled and customized.
By default, the firmware fails to adequately cool the computer which results in thermal throttling.
-----
The goal is to have the laptop fan run at full throttle at all times, regardless of CPU temeperature.
-----
[ ] Enable fan control in thinkpad_acpi module.
[ ] Set fan speed to full throttle.
-----
This commit configures a custom guix configuration for Akashi system in order to set up a testing loop with a staging branch.
Additional modules need to be imported in order to facilitate this change.
-----
Akashi system will now pull the staging branch of Deployment channel during updates.
|
|
The (sovereign channels) defines a new, simpler guix channel.
|
|
|
|
All operating-system records are configured to prepend default labels with respective host names.
-----
Some minor adaptations had to performed.
|
|
The purpose of the test subdomain is to try out changes in nginx configuration.
As such, directories should not be created for the sake of the test subdomain.
Instead, the test subdomain should point to a subdomain currently needing testing.
|
|
|
|
|
|
|
|
The root user need access to openssl command in order to manipulate ca secrets.
|
|
No functional changes are introduced.
This is purely visual improvement.
|
|
|
|
The current system configuration of aisaka uses an old custom home environment from before a unified one was developed.
As it is no longer useful, the (home-services) procedure definition is removed from the module.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The prototype of the client certificate authentication is suboptimal.
The use of a private certificate authority for server authentication causes unnecessary security warnings when loading the subdomain with an unauthenticated browser.
Any browser in its default configuration has no right to understand the private certificate authority used for the client and server certificates.
It is possible to mix Let’s Encrypt certificates with a private certificate authority to implement the authentication.
None of the previously found client authentication guides mentioned that server authentication can use an authority chain different to client authentication.
This change takes advantage of this separation of concerns by using a Let’s Encrypt certificate for the test subdomain server, while keeping the private certificate for client authentication.
|
|
|
|
|
|
This reverts commit ba64ebfe587f05c734f24ace507d22629d350cd8.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The indirect bindings force the Sovereign channel to unnecessarily depend on Nonguix.
|
|
The indirect bindings force the Sovereign channel to unnecessarily depend on Nonguix.
|
|
|
