Bug 17148

Summary:	If keyboard is not attached while booting, it is not detected if attached later
Product:	Base System	Reporter:	mb <mb>
Component:	kern	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	Unspecified
Hardware:	Any
OS:	Any

Description mb 2000-03-03 12:40:00 UTC

If keyboard is not attached while booting, it is not detected if
attached later. The keyboard blinks at the same time on all three
leds one time, but is not functional after. Only a reset (soft or hard)
does bring the keyboard back.

boot -v output (if keyboard is connected at boottime) :

atkbdc0: <keyboard controller> (i8042)> at port 0x60-0x6f on isa0
atkbd0: <AT Keyboard> irq 1 on atkdbc0
atkdb: the current kbd controller commend byte 0067
atkdb: keyboard ID 0x41ab (2)
kbdc: RESET_KBD return code:00fa
kbdc:  RESET_KBD return code:00aa
kdb0: atkdb0, AT 101/102 (2), config:0x0, flags:0x3d0000

Fix: 

not known
How-To-Repeat: Remove the keyboard. Turn on the computer and boot FreeBSD. After the
machine is up, attach the keyboard.

Comment 1 wkb 2000-04-05 22:21:56 UTC

PC keyboards were never designed to be [un]plugged with the machine
powered on.
You would not be the first one to blow keyboard fuses or keyboard
controller chips.
The keyboard resetting or not (meaning that its own in-keyboard chips
reset correctly)
depends on the keyboard itself. Some reset all the time, some never,
some sometimes.

In short: don't do that if you prefer your hardware to remain in good
working order.

Wilko
wilko@freebsd.org

[ and before someone tells me: I know most people get away with this.
That does not
make it a good idea ]

Comment 2 mb 2000-04-05 22:35:33 UTC

Hi,

This PR can be closed. It's fixed by Yokota in 4.0 Release.

Martin

Martin Blapp, mb@imp.ch
------------------------------------------------
Improware AG, UNIX solution and service provider
Zurlindenstrasse 29, 4133 Pratteln, Switzerland
Phone: +41 79 370 26 05, Fax: +41 61 826 93 01
------------------------------------------------

On Wed, 5 Apr 2000, Wilko Bulte wrote:

> PC keyboards were never designed to be [un]plugged with the machine
> powered on.
> You would not be the first one to blow keyboard fuses or keyboard
> controller chips.
> The keyboard resetting or not (meaning that its own in-keyboard chips
> reset correctly)
> depends on the keyboard itself. Some reset all the time, some never,
> some sometimes.
> 
> In short: don't do that if you prefer your hardware to remain in good
> working order.
> 
> Wilko
> wilko@freebsd.org
> 
> [ and before someone tells me: I know most people get away with this.
> That does not
> make it a good idea ]
>

Comment 3 Sheldon Hearn 2000-04-07 13:53:05 UTC

On Wed, 05 Apr 2000 14:40:03 MST, Martin Blapp wrote:

>  This PR can be closed. It's fixed by Yokota in 4.0 Release.

Are you sure?  I've seen a number of reports that the problem exists in
4.0-RELEASE as well.  The latest one seems to be PR 17793, but I saw a
better one with some suggestions on how to fix the problem.  I can't
remember the PR number. :-(

Ciao,
Sheldon.

Comment 4 Steve Price freebsd_committer

2000-04-17 17:25:57 UTC

State Changed
From-To: open->closed

Originator notes this problem has been fixed by Yokota in 4.0R.