Re: [BUG] capslock works across all keyboards but LED does not

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media Devel]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Linux Wireless Networking]     [Linux Omap]

  Powered by Linux