From: Ming Lei <ming.lei@canonical.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: [BUG] capslock works across all keyboards but LED does not
Date: Tue, 23 Oct 2012 09:20:17 +0800 [thread overview]
Message-ID: <CACVXFVMbc3eBMj4gcAVDZjB4SJYwbLeVzUi13C62FMVYymgFug@mail.gmail.com> (raw)
In-Reply-To: <20121022155446.GB13791@core.coreip.homeip.net>
On Mon, Oct 22, 2012 at 11:54 PM, Dmitry Torokhov
<dmitry.torokhov@gmail.com> wrote:
>
> Keyboard LEDs are controlled by the kernel unless console is in the raw
> mode (X), in which case it is left to userspace. I see it on my box that
> sync between keyboards is broken while I am in X (so it is X problem)
> and works when I am in text console (so I do not see the kernel
> problem).
>
> Since it does not work for you in text console either your setup must be
> different than mine. If you switch to a text console and do
>
> sudo lsof /dev/input/event*
>
> what do you see?
- lsof output from text console
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/tom/.gvfs
Output information may be incomplete.
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
upowerd 2956 root 13r CHR 13,64 0t0 7050 /dev/input/event0
- lsof output from X
[tom@~]$sudo lsof /dev/input/event*
[sudo] password for tom:
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/tom/.gvfs
Output information may be incomplete.
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
Xorg 2110 root 12u CHR 13,66 0t0 7052 /dev/input/event2
Xorg 2110 root 13u CHR 13,70 0t0 10099 /dev/input/event6
Xorg 2110 root 14u CHR 13,65 0t0 7051 /dev/input/event1
Xorg 2110 root 15u CHR 13,71 0t0 13213 /dev/input/event7
Xorg 2110 root 16u CHR 13,67 0t0 7058 /dev/input/event3
Xorg 2110 root 19u CHR 13,69 0t0 7255 /dev/input/event5
Xorg 2110 root 52u CHR 13,73 0t0 27009 /dev/input/event9
upowerd 2956 root 13r CHR 13,64 0t0 7050 /dev/input/event0
Thanks,
--
Ming Lei
next prev parent reply other threads:[~2012-10-23 1:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 12:44 [BUG] capslock works across all keyboards but LED does not Ming Lei
2012-10-17 17:30 ` Dmitry Torokhov
2012-10-22 1:42 ` Ming Lei
2012-10-22 15:54 ` Dmitry Torokhov
2012-10-23 1:20 ` Ming Lei [this message]
2012-10-23 17:48 ` Dmitry Torokhov
2012-10-24 0:39 ` Ming Lei
2012-10-24 5:24 ` Dmitry Torokhov
2012-10-26 0:56 ` Ming Lei
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=CACVXFVMbc3eBMj4gcAVDZjB4SJYwbLeVzUi13C62FMVYymgFug@mail.gmail.com \
--to=ming.lei@canonical.com \
--cc=dmitry.torokhov@gmail.com \
--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).