From owner-freebsd-current@FreeBSD.ORG  Thu Oct 18 14:57:35 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 4FC7B16A417
	for <current@freebsd.org>; Thu, 18 Oct 2007 14:57:35 +0000 (UTC)
	(envelope-from brucec@muon.bluestop.org)
Received: from muon.bluestop.org (muon.bluestop.org [IPv6:2001:41c8:1:548a::2])
	by mx1.freebsd.org (Postfix) with ESMTP id E752C13C45D
	for <current@freebsd.org>; Thu, 18 Oct 2007 14:57:34 +0000 (UTC)
	(envelope-from brucec@muon.bluestop.org)
Received: by muon.bluestop.org (Postfix, from userid 1000)
	id B877E3017A; Thu, 18 Oct 2007 15:57:33 +0100 (BST)
Date: Thu, 18 Oct 2007 15:57:33 +0100
From: bruce@cran.org.uk
To: Petr Holub <hopet@ics.muni.cz>
Message-ID: <20071018145733.GA28398@muon.bluestop.org>
References: <012101c81193$54e2bef0$5317fb93@KLOBOUCEK>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <012101c81193$54e2bef0$5317fb93@KLOBOUCEK>
User-Agent: Mutt/1.5.13 (2006-08-11)
Cc: current@freebsd.org
Subject: Re: USB keyboard leds gone wild on 7.0-PRERELEASE
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2007 14:57:35 -0000

On Thu, Oct 18, 2007 at 04:29:46PM +0200, Petr Holub wrote:
> Hi,
> 
> another report of weird behavior on 7.0-PRERELEASE.
> After booting up the machine with IBM ThinkPad USB
> keyboard, it shows NumLock correctly turned on. However,
> after pushing any key that should change led status,
> it starts to show a state that doesn't make any sense
> (e.g. after pressing NumLock, NumLock led is correctly
> turned off but also ScrollLock and CapsLock are turned
> on - this is just led problem, the state of the keyboard
> is OK). The same keyboard works just fine with
> 6.2-RELEASE.

I reported this last month - see the thread "USB keyboard status
indicators not working".

--
Bruce

> 
> FreeBSD fbsd-7.fi.muni.cz 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #5: Thu Oct 18 1
> 1:07:20 CEST 2007     toor@fbsd-7.fi.muni.cz:/usr/obj/usr/src/sys/FBSD7  i386
> 
> dmesg part of the keyboard:
> uhub7: <Lite-On Tech USB 1.1 2 port downstream low-power hub, class 9/0, rev 1.1
> 0/2.01, addr 2> on uhub1
> uhub7: 4 ports with 2 removable, bus powered
> ukbd0: <Lite-On Tech IBM USB Keyboard with UltraNav, class 0/0, rev 1.10/1.16, a
> ddr 3> on uhub7
> kbd2 at ukbd0
> uhid0: <Lite-On Tech IBM USB Keyboard with UltraNav, class 0/0, rev 1.10/1.16, a
> ddr 3> on uhub7
> ums0: <Synaptics Inc. Composite TouchPad / TrackPoint, class 0/0, rev 1.10/0.20,
>  addr 4> on uhub7
> ums0: 3 buttons.
> ums1: <Synaptics Inc. Composite TouchPad / TrackPoint, class 0/0, rev 1.10/0.20,
>  addr 4> on uhub7
> ums1: 3 buttons.
> 
> Petr
> 
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>