From: "Kai Wasserbäch" <kai@dev.carbon-project.org>
To: linux-input@vger.kernel.org
Subject: Logitech G710+ unusable without quirk/driver
Date: Wed, 16 Oct 2013 16:50:04 +0200 [thread overview]
Message-ID: <525EA79C.7070802@dev.carbon-project.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]
[Please CC me on all replys, I'm not subscribed to this list.]
Dear Kernel Devs,
I recently tried to use a Logitech G710+ (because of the nice mechanical keys)
with Linux, which is, outside of X (evdev seems to filter this), not possible.
The keyboard spams „6“ to the console. Some searching yielded, that this is a
known problem and based on that information it seems like the problem is, that
the device sends some key down events during initilisation but no key up event.
This means I can't use the device during boot, as I'm unable to enter the
passphrase for my encrypted filesystem. Or later, the non-graphical interface.
There is an out-of-tree driver
(<https://github.com/Wattos/logitech-g710-linux-driver>) which works for the
non-graphical interface; I haven't managed to convince my initrd to properly
load the driver, even though it is included. The author tried to get feedback
from this list, but didn't receive an answer
<http://article.gmane.org/gmane.linux.kernel.input/30258>, but maybe that's a
starting point for getting something working into the kernel.
Is there some kind of quirk flag that can be set during boot, that would make
the keyboard at least usable (obviously without the macro keys, but those aren't
that important to me, so that'd be fine)?
Thank you in advance for fixing this issue!
Kind regards,
Kai Wasserbäch
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 665 bytes --]
reply other threads:[~2013-10-16 14:57 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=525EA79C.7070802@dev.carbon-project.org \
--to=kai@dev.carbon-project.org \
--cc=linux-input@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).