| Age | Commit message (Collapse) | Author |
|---|
|
This removal is part of a process to decomission Distribution channel.
---
The ultimate goal is to move useful code from Distribution channel to either Sovereign or Deployment channels.
Everything else will be deleted and ultimately will be removed from network.
---
The (suweren system) module was imported in aisaka, akashi and ayase systems.
---
All these imports are deleted.
---
After this (suweren system) module can be deleted from Distribution channel.
|
|
This replacement is part of a process to decomission Deployment channel.
---
The ultimate goal is to move useful code from Deployment channel to either Sovereign or Deployment channels.
Everything else will be deleted and ultimately will be removed from network.
---
The replaced reference is a useless indirection.
---
The direct object from upstream Guix channel is used instead.
---
This is the last variable from (suweren system) module gone.
|
|
This replacement is part of a process to decomission Deployment channel.
---
The ultimate foal is to move useful code from Deployment channel to either Sovereign or Deployment channels.
Everything else will be deleted and ultimately the entire channel will be removed from network.
---
The replaced refences are already defined in Sovereign channel.
---
The definitions from Sovereign channel are used in place of the old ones.
---
The Sovereign definition is exactly the same as on in Distribution channel.
|
|
This replacement is part of a process to decomission Deployment channel.
---
The ultimate goal is to move useful code from Deployment channel to either Sovereign or Deployment channels.
Everything else will be deleted and ultimately the entire channel will be removed from network.
---
The replaced refences are already defined in Sovereign channel.
---
The definitions from Sovereign channel are used in place of the old ones.
---
The Sovereign definition is slightly more complete (with explicit charset field), but functionally the same as the old one.
|
|
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.
|
|
All operating-system records are configured to prepend default labels with respective host names.
-----
Some minor adaptations had to performed.
|
|
|
|
|
|
|
