All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor@insightbb.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Pete Zaitcev <zaitcev@redhat.com>, Jiri Kosina <jkosina@suse.cz>,
	linux-usb-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, stuard_hayes@dell.com
Subject: Re: usb hid: reset NumLock
Date: Mon, 2 Apr 2007 00:10:47 -0400	[thread overview]
Message-ID: <200704020010.48991.dtor@insightbb.com> (raw)
In-Reply-To: <84144f020704010449w2ba342a3qf3025425e84ad2ce@mail.gmail.com>

Hi Pekka,

On Sunday 01 April 2007 07:49, Pekka Enberg wrote:
> On 3/30/07, Pete Zaitcev <zaitcev@redhat.com> wrote:
> > Dell people (Stuart and Charles) complained that on some USB keyboards,
> > if BIOS enables NumLock, it stays on even after Linux has started. Since
> > we always start with NumLock off, this confuses users. Quick double dab
> > at NumLock fixes it, but it's not nice.
> 
> What I am seeing on my Thinkpad is that when I boot _without_ an USB
> keyboard NumLock is enabled. Switching to virtual console and back to
> X fixes it which is why I have never bothered to debug it further.
> Perhaps this is related? Should I give your patch a spin to see if it
> fixes the problem?
> 

Are you saying that NumLock LED is lit or that keyboard is in NumLock
state? Does the same happen if you boot with init=/bin/bash?

-- 
Dmitry

      parent reply	other threads:[~2007-04-02  4:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-30 17:59 usb hid: reset NumLock Pete Zaitcev
2007-03-30 18:14 ` Dmitry Torokhov
2007-03-30 19:54   ` Pete Zaitcev
2007-03-30 20:29     ` Dmitry Torokhov
2007-03-31 19:35 ` Jiri Kosina
2007-03-31 22:43   ` Pete Zaitcev
2007-04-02  5:24   ` Pete Zaitcev
2007-04-02 14:48     ` Jiri Kosina
2007-04-02 23:12       ` Pete Zaitcev
2007-04-03  5:04         ` Dmitry Torokhov
2007-04-03  6:24           ` Pete Zaitcev
2007-04-03  8:52         ` Jiri Kosina
2007-04-03  8:57           ` [linux-usb-devel] " Robert Marquardt
2007-04-03  9:32             ` Jiri Kosina
2007-04-05  3:24           ` Dmitry Torokhov
2007-04-05  8:50             ` Jiri Kosina
2007-04-05 20:38               ` Pete Zaitcev
2007-04-05 20:54                 ` Dmitry Torokhov
2007-04-05 21:22                   ` Pete Zaitcev
2007-04-01 11:49 ` Pekka Enberg
2007-04-01 16:16   ` Pete Zaitcev
2007-04-02  4:10   ` Dmitry Torokhov [this message]

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=200704020010.48991.dtor@insightbb.com \
    --to=dtor@insightbb.com \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=penberg@cs.helsinki.fi \
    --cc=stuard_hayes@dell.com \
    --cc=zaitcev@redhat.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.