unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Adam Bolte <abolte@systemsaviour.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Kernel module arguments and custom /proc settings
Date: Thu, 28 Jul 2016 23:09:31 +1000	[thread overview]
Message-ID: <20160728130831.GA32364@dragon> (raw)
In-Reply-To: <87oa5lh2c7.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1575 bytes --]

Sorry for the delay in my response. I've only just found the time to
try your suggestion and reply.

On Mon, Jul 25, 2016 at 10:47:36PM +0200, Ludovic Courtès wrote:
> Could you try writing the following in /run/modprobe.d/fan.conf:
> 
> --8<---------------cut here---------------start------------->8---
> options thinkpad_acpi fan_control=1
> --8<---------------cut here---------------end--------------->8---
> 
> and then rebooting?
> 
> If everything goes well, this .conf file will be taken into account when
> udev asks to load ‘thinkpad_acpi’.

I can confirm that this worked fine. Thanks!


> Eventually we should provide a way to specify /run/modprobe.d entries
> via the ‘operating-system’ config, though.

Sounds good. As someone who comes from a background in configuration
management, I would much rather have the entire system configuration
defined in a state configuration file than do manual once-off edits
(which is a part of what has attracted me to the project).

Now I just need to figure out how to set /proc entries on boot. I
guess I need to write a "service" for that, although I'm currently a
complete a noob at Scheme. Actually, that's why I purchased this X60
100% free software-compatible laptop - so I could better experiment
and learn these technologies.

Ultimately there are a number of programs I use under Debian which I
would like to create Guix packages for when I'm more comfortable with
how it all works. Then it's just a matter of finding the time to read
and experiment. :)

Cheers,
Adam

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-07-28 13:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-24  4:05 Kernel module arguments and custom /proc settings Adam Bolte
2016-07-25 20:47 ` Ludovic Courtès
2016-07-28 13:09   ` Adam Bolte [this message]
2016-07-28 15:24     ` Ludovic Courtès
2016-07-25 21:09 ` Andreas Enge
2016-07-28 13:13   ` Adam Bolte

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160728130831.GA32364@dragon \
    --to=abolte@systemsaviour.com \
    --cc=help-guix@gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).