All of lore.kernel.org
 help / color / mirror / Atom feed
* [BUG] capslock works across all keyboards but LED does not
@ 2012-10-17 12:44 Ming Lei
  2012-10-17 17:30 ` Dmitry Torokhov
  0 siblings, 1 reply; 9+ messages in thread
From: Ming Lei @ 2012-10-17 12:44 UTC (permalink / raw)
  To: Dmitry Torokhov; +Cc: linux-input

Hi,

There is one report on the below problem:[1]

        - connect one usb keyboard into laptop
        - press capslock on internal ps/2 keyboard
        - input from both two keyboards  becomes upper case state
        - but only capslock led is on in ps/2 keyboard and not on in
usb keyboard

or
        - connect one usb keyboard into laptop
        - press capslock on usb keyboard
        - input from both two keyboards  becomes upper case state
        - but only capslock led is on in usb keyboard and not on in
internal ps/2 keyboard

No such problem on windows, and capslock input is always consistent with the led
state on both keyboards.

I can reproduce the above problem 100% on my T410 laptop.

[1], https://bugs.launchpad.net/ubuntu/+source/linux/+bug/830063

Thanks,
--
Ming Lei

^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: [BUG] capslock works across all keyboards but LED does not
  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
  0 siblings, 1 reply; 9+ messages in thread
From: Dmitry Torokhov @ 2012-10-17 17:30 UTC (permalink / raw)
  To: Ming Lei; +Cc: linux-input

Hi Ming,

On Wednesday, October 17, 2012 08:44:12 PM Ming Lei wrote:
> Hi,
> 
> There is one report on the below problem:[1]
> 
>         - connect one usb keyboard into laptop
>         - press capslock on internal ps/2 keyboard
>         - input from both two keyboards  becomes upper case state
>         - but only capslock led is on in ps/2 keyboard and not on in
> usb keyboard
> 
> or
>         - connect one usb keyboard into laptop
>         - press capslock on usb keyboard
>         - input from both two keyboards  becomes upper case state
>         - but only capslock led is on in usb keyboard and not on in
> internal ps/2 keyboard
> 
> No such problem on windows, and capslock input is always consistent with the
> led state on both keyboards.
> 
> I can reproduce the above problem 100% on my T410 laptop.

I see it is broken in X, but it works for me if I am using the console.
Does it work for you as well if you switch into the console? If so then
you need to file a bug against X.

Thanks.

-- 
Dmitry

^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: [BUG] capslock works across all keyboards but LED does not
  2012-10-17 17:30 ` Dmitry Torokhov
@ 2012-10-22  1:42   ` Ming Lei
  2012-10-22 15:54     ` Dmitry Torokhov
  0 siblings, 1 reply; 9+ messages in thread
From: Ming Lei @ 2012-10-22  1:42 UTC (permalink / raw)
  To: Dmitry Torokhov; +Cc: linux-input

Hi Dmitry,

On Thu, Oct 18, 2012 at 1:30 AM, Dmitry Torokhov
<dmitry.torokhov@gmail.com> wrote:
>
> I see it is broken in X, but it works for me if I am using the console.
> Does it work for you as well if you switch into the console? If so then
> you need to file a bug against X.

Thanks for your reply.

Unluckily, it becomes worse if I switch to console and capslock leds
in both keyborads are not changed but the function is OK.

So you mean the led is controlled by user-space totally? and Kernel
doesn't handle the case?

Thanks,
--
Ming Lei

^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: [BUG] capslock works across all keyboards but LED does not
  2012-10-22  1:42   ` Ming Lei
@ 2012-10-22 15:54     ` Dmitry Torokhov
  2012-10-23  1:20       ` Ming Lei
  0 siblings, 1 reply; 9+ messages in thread
From: Dmitry Torokhov @ 2012-10-22 15:54 UTC (permalink / raw)
  To: Ming Lei; +Cc: linux-input

On Mon, Oct 22, 2012 at 09:42:17AM +0800, Ming Lei wrote:
> Hi Dmitry,
> 
> On Thu, Oct 18, 2012 at 1:30 AM, Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
> >
> > I see it is broken in X, but it works for me if I am using the console.
> > Does it work for you as well if you switch into the console? If so then
> > you need to file a bug against X.
> 
> Thanks for your reply.
> 
> Unluckily, it becomes worse if I switch to console and capslock leds
> in both keyborads are not changed but the function is OK.
> 
> So you mean the led is controlled by user-space totally? and Kernel
> doesn't handle the case?

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?

Thanks.

-- 
Dmitry

^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: [BUG] capslock works across all keyboards but LED does not
  2012-10-22 15:54     ` Dmitry Torokhov
@ 2012-10-23  1:20       ` Ming Lei
  2012-10-23 17:48         ` Dmitry Torokhov
  0 siblings, 1 reply; 9+ messages in thread
From: Ming Lei @ 2012-10-23  1:20 UTC (permalink / raw)
  To: Dmitry Torokhov; +Cc: linux-input

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

^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: [BUG] capslock works across all keyboards but LED does not
  2012-10-23  1:20       ` Ming Lei
@ 2012-10-23 17:48         ` Dmitry Torokhov
  2012-10-24  0:39           ` Ming Lei
  0 siblings, 1 reply; 9+ messages in thread
From: Dmitry Torokhov @ 2012-10-23 17:48 UTC (permalink / raw)
  To: Ming Lei; +Cc: linux-input

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

^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: [BUG] capslock works across all keyboards but LED does not
  2012-10-23 17:48         ` Dmitry Torokhov
@ 2012-10-24  0:39           ` Ming Lei
  2012-10-24  5:24             ` Dmitry Torokhov
  0 siblings, 1 reply; 9+ messages in thread
From: Ming Lei @ 2012-10-24  0:39 UTC (permalink / raw)
  To: Dmitry Torokhov; +Cc: linux-input

On Wed, Oct 24, 2012 at 1:48 AM, Dmitry Torokhov
<dmitry.torokhov@gmail.com> wrote:
>
> 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

I only have one laptop at hand, :-(

> keyboards if you plug in both of them? What does /proc/bus/input/devices

I only have one usb keyboard too, :-(

The LED state becomes off once I switched to console via pressing 'ctrl+alt+F1',
and it will keep off even though CAPSLOCK is pressed on either usb keyboard
or ps/2 keyboard.

The above can be observed on 3.6 kernel and several precious kernel.
(distribution is Ubuntu 12.04)

> show?

[tom@linux-2.6-omap]$cat /proc/bus/input/devices
I: Bus=0019 Vendor=0000 Product=0005 Version=0000
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input0
U: Uniq=
H: Handlers=event0
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0019 Vendor=0000 Product=0003 Version=0000
N: Name="Sleep Button"
P: Phys=PNP0C0E/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input1
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=3
B: KEY=4000 0 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
U: Uniq=
H: Handlers=kbd event2
B: PROP=0
B: EV=3
B: KEY=10000000000000 0

I: Bus=0011 Vendor=0001 Product=0001 Version=ab54
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input3
U: Uniq=
H: Handlers=sysrq kbd event3
B: PROP=0
B: EV=120013
B: KEY=402000000 3803078f800d001 feffffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=046d Product=c045 Version=0110
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:1a.0-1.1/input0
S: Sysfs=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/input/input4
U: Uniq=
H: Handlers=mouse0 event4
B: PROP=0
B: EV=17
B: KEY=ff0000 0 0 0 0
B: REL=143
B: MSC=10

I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input5
U: Uniq=
H: Handlers=kbd event5
B: PROP=0
B: EV=3
B: KEY=3e000b00000000 0 0 0

I: Bus=0019 Vendor=17aa Product=5054 Version=4101
N: Name="ThinkPad Extra Buttons"
P: Phys=thinkpad_acpi/input0
S: Sysfs=/devices/platform/thinkpad_acpi/input/input6
U: Uniq=
H: Handlers=rfkill kbd event6
B: PROP=0
B: EV=33
B: KEY=18040000 0 10000000000000 0 101501b00102004 8000000001104000
e000000000000 0
B: MSC=10
B: SW=8

I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input7
U: Uniq=
H: Handlers=mouse1 event7
B: PROP=9
B: EV=b
B: KEY=6420 30000 0 0 0 0
B: ABS=260800011000003

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/input8
U: Uniq=
H: Handlers=event8
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/input9
U: Uniq=
H: Handlers=event9
B: PROP=0
B: EV=21
B: SW=10

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/input10
U: Uniq=
H: Handlers=event10
B: PROP=0
B: EV=21
B: SW=4

I: Bus=0003 Vendor=17ef Product=480f Version=2345
N: Name="Integrated Camera"
P: Phys=usb-0000:00:1a.0-1.6/button
S: Sysfs=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input11
U: Uniq=
H: Handlers=kbd event11
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0011 Vendor=0002 Product=000a Version=0000
N: Name="TPPS/2 IBM TrackPoint"
P: Phys=synaptics-pt/serio0/input0
S: Sysfs=/devices/platform/i8042/serio1/serio2/input/input12
U: Uniq=
H: Handlers=mouse2 event12
B: PROP=0
B: EV=7
B: KEY=70000 0 0 0 0
B: REL=3


Thanks,
--
Ming Lei

^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: [BUG] capslock works across all keyboards but LED does not
  2012-10-24  0:39           ` Ming Lei
@ 2012-10-24  5:24             ` Dmitry Torokhov
  2012-10-26  0:56               ` Ming Lei
  0 siblings, 1 reply; 9+ messages in thread
From: Dmitry Torokhov @ 2012-10-24  5:24 UTC (permalink / raw)
  To: Ming Lei; +Cc: linux-input

On Wed, Oct 24, 2012 at 08:39:51AM +0800, Ming Lei wrote:
> On Wed, Oct 24, 2012 at 1:48 AM, Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
> >
> > 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
> 
> I only have one laptop at hand, :-(
> 
> > keyboards if you plug in both of them? What does /proc/bus/input/devices
> 
> I only have one usb keyboard too, :-(
> 
> The LED state becomes off once I switched to console via pressing 'ctrl+alt+F1',
> and it will keep off even though CAPSLOCK is pressed on either usb keyboard
> or ps/2 keyboard.
> 
> The above can be observed on 3.6 kernel and several precious kernel.
> (distribution is Ubuntu 12.04)

Do you have thinkpads platform driver loaded? What happens if you boot
with it blacklisted?

Thanks.

-- 
Dmitry

^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: [BUG] capslock works across all keyboards but LED does not
  2012-10-24  5:24             ` Dmitry Torokhov
@ 2012-10-26  0:56               ` Ming Lei
  0 siblings, 0 replies; 9+ messages in thread
From: Ming Lei @ 2012-10-26  0:56 UTC (permalink / raw)
  To: Dmitry Torokhov; +Cc: linux-input

On Wed, Oct 24, 2012 at 1:24 PM, Dmitry Torokhov
<dmitry.torokhov@gmail.com> wrote:

> Do you have thinkpads platform driver loaded? What happens if you boot
> with it blacklisted?

Looks no change after blacklisting 'thinkpad_acpi' module.


Thanks,
--
Ming Lei

^ permalink raw reply	[flat|nested] 9+ messages in thread
end of thread, other threads:[~2012-10-26  0:56 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2012-10-24  0:39           ` Ming Lei
2012-10-24  5:24             ` Dmitry Torokhov
2012-10-26  0:56               ` Ming Lei

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.