From: "Antonino Ingargiola" <tritemio@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: [Possible BUG] Logitech USB keyboard inconsistent led state
Date: Wed, 27 Jun 2007 16:58:21 +0200 [thread overview]
Message-ID: <5486cca80706270758x540f75a9vfdd4aa5b6a7d8e4f@mail.gmail.com> (raw)
Dear Kernel Developers,
I'm using a logitech USB keyboard, I think it's one of the most cheap
and diffuse logitech keyboard models.
I have an inconsistent led state. During boot the NumLock led blinks
several times and is on as boot finishes. However the numeric keypad
works as it was off (no numbers, keypad '.' works as Canc, '0' as Ins
and so on).
To restore a consistent state I have to press one key that change one
of the 3 leds on the keyboards: NumLock, CapsLock or ScrollLock.
Once I pressed one of those key the NumLock led turns off and,
eventually, another led turns on. After this if I press NumLock I have
the keypad enabled.
I'm able to reproduce the problem only once after a system boot (with
or without X). Unplugging the keyboard and unloading/reloading all the
usb stack always gives again a consistent state.
The problem is reproduced with various kernels from 2.6.18 official
debian etch build, until 2.6.22-rc5-cfs-v18-cfs.
Some keyboard info from dmesg:
kernel: usb 1-1.2: new low speed USB device using uhci_hcd and address 5
kernel: usb 1-1.2: Product: USB Multimedia Keyboard
kernel: usb 1-1.2: Manufacturer: BTC
kernel: usb 1-1.2: configuration #1 chosen from 1 choice
kernel: input: BTC USB Multimedia Keyboard as /class/input/input8
kernel: input: USB HID v1.10 Keyboard [BTC USB Multimedia Keyboard] on
usb-0000:00:07.2-1.2
kernel: input: BTC USB Multimedia Keyboard as /class/input/input9
kernel: input,hiddev96: USB HID v1.10 Device [BTC USB Multimedia
Keyboard] on usb-0000:00:07.2-1.2
If you need further information just ask.
Regards,
~ Antonio
next reply other threads:[~2007-06-27 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 14:58 Antonino Ingargiola [this message]
2007-06-27 19:45 ` Jiri Kosina
2007-06-28 7:59 ` Antonino Ingargiola
2007-06-28 17:24 ` Jiri Kosina
2007-06-28 20:09 ` Antonino Ingargiola
2007-06-28 20:38 ` Jiri Kosina
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=5486cca80706270758x540f75a9vfdd4aa5b6a7d8e4f@mail.gmail.com \
--to=tritemio@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®