From owner-freebsd-bugs Tue Oct 22 21:10:06 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA01322 for bugs-outgoing; Tue, 22 Oct 1996 21:10:06 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA01315; Tue, 22 Oct 1996 21:10:02 -0700 (PDT) Date: Tue, 22 Oct 1996 21:10:02 -0700 (PDT) Message-Id: <199610230410.VAA01315@freefall.freebsd.org> To: freebsd-bugs Cc: From: Bruce Evans Subject: Re: kern/1868: keyboard leds Reply-To: Bruce Evans Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/1868; it has been noted by GNATS. From: Bruce Evans To: FreeBSD-gnats-submit@FreeBSD.org, julian@current1.whistle.com Cc: Subject: Re: kern/1868: keyboard leds Date: Wed, 23 Oct 1996 13:57:50 +1000 >>Synopsis: system knows it has no keyboard but complains leds won't work > During the probe, pcvt says: >pcvt: doreset() - Caution - no PC keyboard detected! >vt0 at 0x60-0x6f irq 1 on motherboard >Keyboard LED command not ACKed (responses 0xfe 0xfe) >Keyboard LED command not ACKed (responses 0xfe 0xfe) >Keyboard LED command not ACKed (responses 0xfe 0xfe) >Keyboard LED command not ACKed (responses 0xfe 0xfe) >Keyboard LED command not ACKed (responses 0xfe 0xfe) >Keyboard LED command not ACKed (responses 0xfe 0xfe) >Keyboard LED command not ACKed (responses 0xfe 0xfe) >Keyboard LED command not ACKed (responses 0xfe 0xfe) >Keyboard LED command not ACKed (responses 0xfe 0xfe) > >well, DUH! maybe that's because there is no keyboard, >as mentioned in the previous row?? It doesn't know. The keyboard might have been plugged in between the time when it not detected and the time when the LED commands are issued, although this is unlikely during the boot. >bde added the led changes Previously it told me that I had no keyboard, and didn't print anything for the LED errors, but I had a keyboard, and everything except setting the LEDs worked. Bruce