From owner-freebsd-bugs Wed Oct 23 13:18:15 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA08273 for bugs-outgoing; Wed, 23 Oct 1996 13:18:15 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA08251 for ; Wed, 23 Oct 1996 13:18:09 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.6/8.7.3) with SMTP id MAA10655; Wed, 23 Oct 1996 12:28:28 -0700 (PDT) Message-ID: <326E7151.41C67EA6@whistle.com> Date: Wed, 23 Oct 1996 12:26:09 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Bruce Evans CC: freebsd-bugs@freefall.freebsd.org Subject: Re: kern/1868: keyboard leds References: <199610230410.VAA01315@freefall.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bruce Evans wrote: > > 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. COuldn't it be less verbose if there's a chance that there is no keyboard? this really is not urgent or important.. just a comment that people have been making.. (they are coming up to me and saying "I have a problem with my machine, it's giving me new error messages" as they normally run with no keyboard) > > Bruce