From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Ming Lei <ming.lei@canonical.com>
Cc: linux-input@vger.kernel.org
Subject: Re: [BUG] capslock works across all keyboards but LED does not
Date: Tue, 23 Oct 2012 10:48:34 -0700 [thread overview]
Message-ID: <20121023174834.GB649@core.coreip.homeip.net> (raw)
In-Reply-To: <CACVXFVMbc3eBMj4gcAVDZjB4SJYwbLeVzUi13C62FMVYymgFug@mail.gmail.com>
On Tue, Oct 23, 2012 at 09:20:17AM +0800, Ming Lei wrote:
> 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
Hmm, this looks correct. Do you have similar issues on any other boxes
or only your laptop? Does the LED state propagate between 2 USB
keyboards if you plug in both of them? What does /proc/bus/input/devices
show?
Thanks.
--
Dmitry
next prev parent reply other threads:[~2012-10-23 17:48 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
2012-10-23 17:48 ` Dmitry Torokhov [this message]
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=20121023174834.GB649@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=ming.lei@canonical.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.