From: Andries Brouwer <aebr@win.tue.nl>
To: Meelis Roos <mroos@linux.ee>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Strange atkbd messages with missing keyboard
Date: Thu, 12 Feb 2004 15:46:56 +0100 [thread overview]
Message-ID: <20040212154656.A2460@pclin040.win.tue.nl> (raw)
In-Reply-To: <Pine.GSO.4.44.0402121600030.22808-100000@math.ut.ee>; from mroos@linux.ee on Thu, Feb 12, 2004 at 04:18:43PM +0200
On Thu, Feb 12, 2004 at 04:18:43PM +0200, Meelis Roos wrote:
> I get strange messages on bootup when there is no keyboard attached
> (Intel 430TX chipset on a Tyan S1573 mainboard) - it tells about unknown
> keys pressed.
>
> When no keyboard and no mouse is plugged in:
>
> serio: i8042 AUX port at 0x60,0x64 irq 12
> atkbd.c: Unknown key pressed (raw set 0, code 0x17e on isa0060/serio1).
> atkbd.c: Use 'setkeycodes 7e <keycode>' to make it known.
> serio: i8042 KBD port at 0x60,0x64 irq 1
> atkbd.c: Unknown key released (translated set 0, code 0x7e on isa0060/serio0).
> atkbd.c: Use 'setkeycodes 7e <keycode>' to make it known.
Yes - most people see such messages involving 7a, where the
actual code is 0xfa = ACK.
You see 7e, the actual code is 0xfe = NACK, the error report
from the keyboard interface.
It is a kernel flaw that these ACK and NACK are not recognized
for what they are.
next prev parent reply other threads:[~2004-02-12 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 14:18 Meelis Roos
2004-02-12 14:46 ` Andries Brouwer [this message]
2004-02-12 21:36 ` Vojtech Pavlik
2004-02-13 13:12 ` Meelis Roos
2004-02-13 18:27 ` Dmitry Torokhov
2004-02-13 18:57 ` Vojtech Pavlik
2004-02-13 22:46 ` Dmitry Torokhov
2004-02-14 9:59 ` Vojtech Pavlik
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=20040212154656.A2460@pclin040.win.tue.nl \
--to=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
/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®