From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] linux6.1: enable /proc/i8k for i8kutils package
Date: Thu, 16 Feb 2023 12:46:12 +0100 [thread overview]
Message-ID: <20230216114612.AMvqo37oiyLHrfb11pbtzxOmbgVey08GhwlJvT69eo4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42277@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
Closed issue by michael-db on void-packages repository
https://github.com/void-linux/void-packages/issues/42277
Description:
### Is this a new report?
Yes
### System Info
Void 6.1.11_1 x86_64 GenuineIntel uptodate rrFF
### Package(s) Affected
linux6.1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
Not an upstream bug, but a misconfiguration resulting from a change, e.g.,
https://bbs.archlinux.org/viewtopic.php?pid=2039030#p2039030
### Expected behaviour
`modprobe i8k` (or dell_smm_hwmon) should result in a file `i8k` appearing in `/proc`.
This is needed for the programs of the i8kutils package.
### Actual behaviour
```
i8kctl fan
can't open /proc/i8k: No such file or directory
```
### Steps to reproduce
On an x86_64 system, `xbps-install i8kutils` and `i8kctl fan`.
The cause of the problem took some time to discover, but the fix is simple. I will make a pull request.
next prev parent reply other threads:[~2023-02-16 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 8:22 [ISSUE] " michael-db
2023-02-16 6:27 ` michael-db
2023-02-16 11:46 ` sgn [this message]
2023-02-16 16:38 ` michael-db
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230216114612.AMvqo37oiyLHrfb11pbtzxOmbgVey08GhwlJvT69eo4@z \
--to=sgn@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).