From: "Marco d'Itri" <md@Linux.IT>
To: linux-hotplug@vger.kernel.org
Subject: Bug#567237: udev: Same problem, slightly different solution
Date: Mon, 22 Mar 2010 14:56:08 +0000 [thread overview]
Message-ID: <20100322145608.GA6590@bongo.bofh.it> (raw)
This is related to the patch which was merged a few days ago, but I
can't see how it could work since "logitech" does not appear to be a
valid method.
----- Forwarded message from Stefan Haun <tux@tuxathome.de> -----
Subject: Bug#567237: udev: Same problem, slightly different solution
Reply-To: Stefan Haun <tux@tuxathome.de>, 567237@bugs.debian.org
From: Stefan Haun <tux@tuxathome.de>
To: Debian Bug Tracking System <567237@bugs.debian.org>
Package: udev
Version: 151-3
Severity: normal
Despite the aforementioned changes the problem still existed on my system.
Instead of the proposed replacement, I am currently using the following line
in 70-hid2hci.rules (row 15):
RUN += "hid2hci --method=logitech --mode=hid --devpath=%p"
I am not sure whether this has been a problem with the arguments or there
have been some changes in the hid2hci tool which are not yet applied to my
system, however with these parameters my keyboard is up and running again.
----- End forwarded message -----
--
ciao,
Marco
reply other threads:[~2010-03-22 14:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100322145608.GA6590@bongo.bofh.it \
--to=md@linux.it \
--cc=linux-hotplug@vger.kernel.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).