From: JBKingdon <JBKingdon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [libsigrok] 61-libsigrok-uaccess.rules udev rule doesn't work correctly
Date: Sat, 18 Mar 2023 21:04:00 +0100 [thread overview]
Message-ID: <20230318200400.VOnI2U2PZ41koDaMBJhPdI2rEXmpYHOcXmSPrJpo2SU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23580@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
New comment by JBKingdon on void-packages repository
https://github.com/void-linux/void-packages/issues/23580#issuecomment-1474974796
Comment:
Since this issue is one of the top hits for people searching for sigrok udev problems, I thought it might be useful to add this. I couldn't get the existing udev rules from the contrib directory working on RHEL 8.7, and unfortunately I find the udev system a little difficult to figure out. I eventually gave up and created a smaller udev rule for the specific device I have and this works for me, with <mygroup> replaced with the default group for my userid. I created this as `/usr/lib/udev/rules.d/99-dslogic.rules`
```
ACTION!="add|change", GOTO="libsigrok_rules_end"
SUBSYSTEM!="usb|usbmisc|usb_device|hidraw", GOTO="libsigrok_rules_end"
# DreamSourceLab DSLogic Plus
ATTRS{idVendor}=="2a0e", ATTRS{idProduct}=="0020", MODE="0660", GROUP="<mygroup>"
LABEL="libsigrok_rules_end"
```
prev parent reply other threads:[~2023-03-18 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 3:00 [ISSUE] " Gigahawk
2022-04-07 1:58 ` [ISSUE] [CLOSED] " abenson
2023-03-18 20:04 ` JBKingdon [this message]
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=20230318200400.VOnI2U2PZ41koDaMBJhPdI2rEXmpYHOcXmSPrJpo2SU@z \
--to=jbkingdon@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).