From owner-freebsd-current@FreeBSD.ORG Wed May 10 00:01:45 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D8AC16A43A for ; Wed, 10 May 2006 00:01:45 +0000 (UTC) (envelope-from caelian@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D2FE43D5F for ; Wed, 10 May 2006 00:01:39 +0000 (GMT) (envelope-from caelian@gmail.com) Received: by py-out-1112.google.com with SMTP id e30so1885637pya for ; Tue, 09 May 2006 17:01:38 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:to:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=oIvcIpRl34CucNxjg/dTEQliT6umIpQ8l4l7pzskJfkbIz9VAacbPTHdenasKnm8OV6sD1lA57FuJsEkaAnSI5s4RWglmolRKKVnE0nNwExeh5WVPL09Lqol43udL5fJkRuk5sjuClfWRVpyuc4GxUYxlJcXmCl4OHsrIngShXM= Received: by 10.35.66.13 with SMTP id t13mr2327680pyk; Tue, 09 May 2006 17:01:38 -0700 (PDT) Received: from synergy.odyssey.homeunix.org ( [68.190.230.198]) by mx.gmail.com with ESMTP id v53sm208965pyv.2006.05.09.17.01.35; Tue, 09 May 2006 17:01:37 -0700 (PDT) From: Pascal Hofstee To: current@freebsd.org Content-Type: text/plain Date: Tue, 09 May 2006 17:01:30 -0700 Message-Id: <1147219290.1410.6.camel@synergy.odyssey.homeunix.org> Mime-Version: 1.0 X-Mailer: Evolution 2.7.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Subject: kbdmux oddity ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 May 2006 00:01:46 -0000 Hi, I recently decided to add kbdmux support to my default kernel config since i noticed at times that upon kernel panics and similar events my USB keyboard goes dead. Today i got to actually installing a kbdmux enabled kernel and came to the conclusion that even though keys like Capslock, Numlock and Scrolllock perform the functions they're supposed to do, the keyboard leds seem to arbitrarily decide wether or not they want to toggle on/off. on console i noticed that usually after hitting e.g. caps lock a few times the leds decdide to "work with me again" and toggle on/off accordingly .. until i hit any actual textual input .. at which point the previous eratic behavior has resurfaced. Similar problems exist in X as well ... though seem to be even more eratic there. Removing kbdmux from my kernel seems to restore normality again. Am i the only one seeing these problems ? It's on FreeBSD/amd64 7.0-CURRENT .. no PS/2 keyboard attached only a single USB keyboard. -- Pascal Hofstee