mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Sandall <eric@sandall.us>
To: otto.wyss@orpatec.ch
Cc: "'linux-kernel'" <linux-kernel@vger.kernel.org>
Subject: Re: USB-keyboard not recognized when not connected during startup
Date: Tue, 11 Nov 2003 17:56:38 -0800	[thread overview]
Message-ID: <1068602198.3fb193567bcc7@horde.sandall.us> (raw)
In-Reply-To: <3FAFDA82.864DC1BE@orpatec.ch>

Quoting Otto Wyss <otto.wyss@orpatec.ch>:
> Please CC, I'm not subscribed.
> 
> I use an USB-keyboard via an USB-switchbox on 2 computers (PC and Mac).
> When I boot into Windows or MacOS9 it doesn't matter whether my USB is
> connected, the keyboard gets recognized when the connection happens. Not
> so on Linux (PC), there the keyboard gets only recognized if it's
> connected during startup. If I forget to switch the keyboard to the PC
> before I start Linux, it isn't recognized and unusable. This is mostly
> annoying because I can't get rid of my AT-keyboard and just use the
> USB-keyboard, a none working keyboard is identical to a system crash!
> When the USB-keyboard is connected during startup everything is okay.
> 
> I've seen this behavior with my Debian (sarge) system running my own
> built kernel 2.4.21 with USB input and keyboard drivers compiled in. I
> also see this problem when running Knoppix live CD, therefore it's
> common to any Debian based system, probably to any Linux system.
> 
> Is this problem, not recognizing an USB-keyboard when not connected
> during startup, know and is there a solution for it? Is there a solution
> in the upcoming 2.6 kernel? 
> 
> If anyone wants to test this and has a desktop system with USB, just
> disconnect your normal keyboard, start the system and connect an
> USB-keyboard after the login prompt is shown. You could use the keyboard
> of a Mac if you don't have any. Also your kernel has to have
> USB-input/USB-HID and USB-keyboard support compiled in.
> 
> O. Wyss

Have you tried installing hotplug? That should automatically load the
modules/devices needed when you plug it in after boot.

-sandalle

-- 
PGP Key Fingerprint:  FCFF 26A1 BE21 08F4 BB91  FAED 1D7B 7D74 A8EF DD61
http://search.keyserver.net:11371/pks/lookup?op=get&search=0xA8EFDD61

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS/E/IT$ d-- s++:+>: a-- C++(+++) BL++++VIS>$ P+(++) L+++ E-(---) W++ N+@ o?
K? w++++>-- O M-@ V-- PS+(+++) PE(-) Y++(+) PGP++(+) t+() 5++ X(+) R+(++)
tv(--)b++(+++) DI+@ D++(+++) G>+++ e>+++ h---(++) r++ y+
------END GEEK CODE BLOCK------

Eric Sandall                     |  Source Mage GNU/Linux Developer
eric@sandall.us                  |  http://www.sourcemage.org/
http://eric.sandall.us/          |  SysAdmin @ Inst. Shock Physics @ WSU
http://counter.li.org/  #196285  |  http://www.shock.wsu.edu/

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

  reply	other threads:[~2003-11-12  3:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-10 18:35 Otto Wyss
2003-11-12  1:56 ` Eric Sandall [this message]
2003-11-12 17:08   ` Otto Wyss
2003-11-14  1:45 ` Greg KH
2003-11-15 10:47   ` Otto Wyss

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=1068602198.3fb193567bcc7@horde.sandall.us \
    --to=eric@sandall.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=otto.wyss@orpatec.ch \
    /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®