From: phodina <phodina@protonmail.com>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: Tobias Geerinckx-Rice <me@tobias.gr>, help-guix <help-guix@gnu.org>
Subject: Re: Corefreq: How to specify output in OS definition
Date: Mon, 26 Dec 2022 18:11:50 +0000 [thread overview]
Message-ID: <Q-xEfL6KTCzks5AJhjw1uhQjR-YbnDcZAff_mH6RPz0ay0_Enuzmr9ThhlhnLFU36bbZG5N_KmGZi4hJfGdkrvYxw0DvgjKaFrw4xTYYM4Q=@protonmail.com> (raw)
In-Reply-To: <Y6mcNoObuyuzhczi@3900XT>
Hello Efraim,
> I was able to get it to say it would be added when I added the following
> to my OS config:
>
> (kernel-loadable-modules (list `(,corefreq "linux-module")))
>
> I didn't actually try building or running it though.
Adding this line to OS definition fixes the initial issue.
However, you still need to manually add the kernel module and start the corefreqd daemon as a root.
```
$ corefreq-cli
Daemon connection error code 2
corefreq-ro-shm: 'No such file or directory' @ line 19075
$ corefreqd
corefreqd execution error code 13
Permission denied @ line 8002
$ sudo -E corefreqd
Password:
Driver connection error code 2
/dev/corefreqk: 'No such file or directory' @ line 7998
$ sudo -E modprobe corefreqk
$ sudo -E corefreqd &
CoreFreq Daemon 1.90.1 Copyright (C) 2015-2022 CYRIL INGENIERIE
$ corefreq-cli
# Now it launches :-)
```
So maybe a service would be handy, what do you think?
----
Petr
next prev parent reply other threads:[~2022-12-26 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-24 22:24 Corefreq: How to specify output in OS definition phodina via
2022-12-24 22:47 ` Tobias Geerinckx-Rice
2022-12-26 13:05 ` Efraim Flashner
2022-12-26 18:11 ` phodina [this message]
2022-12-27 6:56 ` Efraim Flashner
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='Q-xEfL6KTCzks5AJhjw1uhQjR-YbnDcZAff_mH6RPz0ay0_Enuzmr9ThhlhnLFU36bbZG5N_KmGZi4hJfGdkrvYxw0DvgjKaFrw4xTYYM4Q=@protonmail.com' \
--to=phodina@protonmail.com \
--cc=efraim@flashner.co.il \
--cc=help-guix@gnu.org \
--cc=me@tobias.gr \
/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).