From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] ddcutil: udev rule
Date: Mon, 01 Mar 2021 11:46:00 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29152@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]
New issue by dkwo on void-packages repository
https://github.com/void-linux/void-packages/issues/29152
Description:
With `kernel 5.11` and `ddcutil 1.0.1` it's now possible to control external display connected via docking station.
When running `ddcutil`, at the moment it is necessary to use `sudo/doas`, as no rules are in place.
In fact, `ddctutil environment` suggests:
```
Configuration suggestions:
Issue:
Group i2c does not exist.
Suggestion:
Create group i2c. To create group i2c, use command:
sudo groupadd --system i2c
Assign /dev/i2c-N devices to group i2c by adding a rule to /etc/udev/rules.d
Add the current user to group i2c:
sudo usermod -G i2c -a <username>
After this, you will have to logout and login again.
The changes to the user's group list are not read until a new login.
```
Is it fine to ship a new `udev` rule with `ddcutil`, something like the suggested
```
$ cat /usr/share/ddcutil/data/45-ddcutil-i2c.rules
# On some distributions, package i2c-tools provides a udev rule.
# For example, on Ubuntu, see 40-i2c-tools.rules.
# Assigns the i2c devices to group i2c, and gives that group RW access:
KERNEL=="i2c-[0-9]*", GROUP="i2c", MODE="0660"
# Gives everyone RW access to the /dev/i2c devices:
# KERNEL=="i2c-[0-9]*", MODE="0666"
```
Or what is the correct approach?
next reply other threads:[~2021-03-01 10:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 10:46 dkwo [this message]
2021-03-11 19:55 ` ericonr
2021-03-12 10:21 ` dkwo
2021-03-12 15:20 ` ericonr
2021-03-15 9:20 ` dkwo
2021-08-27 17:39 ` [ISSUE] [CLOSED] " ericonr
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29152@inbox.vuxu.org \
--to=dkwo@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).