public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Khalid Aziz <khalid@fc.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] AT Keyboard not present?
Date: Fri, 07 Sep 2001 20:09:34 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805143@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805137@msgid-missing>

The problem gets worse when you do not have a PS2 controller on the
machine at all. Kernel spews out a screenful of this message as it boots
up. An easy way to get rid of these messages is to undefine
KBD_REPORT_TIMEOUTS in pc_keyb.h. This still does not get rid of the
delays caused by the timeouts. If I could figure out a way to reliably
determine if the PS2 controller exists or not, I would like to get rid
of the delays as well.

--
Khalid 


Johannes Erdfelt wrote:
> 
> On Fri, Sep 07, 2001, Krishnakumar B <kitty@cs.wustl.edu> wrote:
> > On Friday, 7 September 2001, KOCHI Takayoshi wrote:
> > > Recently I noticed
> > >
> > > keyboard: Timeout - AT keyboard not present?
> >
> > I guess this happens because you are using a USB keyboard and the kernel
> > looks for a PS/2 keyboard. New machines from Dell ship with a USB keyboard
> > by default. Till the USB modules are loaded, I see this error (once or
> > twice). Once the USB modules are loaded, this message disappears. Is there
> > any way to prevent this happening ? I saw that when using RedHat's kernel,
> > this message doesn't show up. What do I need to suppress this message if I
> > have a USB keyboard ?
> 
> The only way to supress the message is to hack it out of the kernel.
> 
> The message comes from the fact the BIOS does legacy device emulation
> for USB keyboards and mice. I think the ia64 BIOS supports this as well.
> However, the emulation isn't perfect and will cause messages like this.
> 
> When the HC driver loads, it turns this off and natively handles the USB
> keyboard.
> 
> The real fix is to use USB drivers as early as possible. The emulation
> wasn't designed to be perfect.
> 
> JE
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64

-- 

==================================
Khalid Aziz                              Linux Systems Operation R&D
(970)898-9214                                        Hewlett-Packard
khalid@fc.hp.com                                    Fort Collins, CO


  parent reply	other threads:[~2001-09-07 20:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-07 17:49 [Linux-ia64] AT Keyboard not present? KOCHI Takayoshi
2001-09-07 19:05 ` Krishnakumar B
2001-09-07 19:36 ` Johannes Erdfelt
2001-09-07 19:55 ` Krishnakumar B
2001-09-07 20:02 ` Johannes Erdfelt
2001-09-07 20:09 ` Khalid Aziz [this message]
2001-09-07 20:12 ` KOCHI Takayoshi
2001-09-10  8:46 ` Martin Wilck
2001-09-10 21:43 ` Michael Madore
2001-09-10 22:10 ` Luck, Tony
2001-09-10 23:28 ` David Mosberger
2001-09-19 13:35 ` Richard Hirst
2001-09-19 21:49 ` David Mosberger
2001-09-19 22:27 ` Richard Hirst
2001-09-20 22:56 ` Richard Hirst
2001-09-21 15:44 ` David Mosberger

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=marc-linux-ia64-105590698805143@msgid-missing \
    --to=khalid@fc.hp.com \
    --cc=linux-ia64@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