From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 6D3D11381F3 for ; Sun, 2 Dec 2012 15:28:55 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CB00D21C004; Sun, 2 Dec 2012 15:28:36 +0000 (UTC) Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id F315FE058F for ; Sun, 2 Dec 2012 15:27:03 +0000 (UTC) Received: from localhost (66-208-231-133.ubr01a.rte20201.pa.hfc.comcastbusiness.net [66.208.231.133]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0LyFqf-1TBEPI1o97-015D1X; Sun, 02 Dec 2012 10:27:02 -0500 Date: Sun, 2 Dec 2012 09:27:00 -0600 From: Bruce Hill To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] kernel 3.2->3.5 upgrade unusable: keyboard borked Message-ID: <20121202152700.GZ23914@server> References: <1540977.IXnsEoOt74@dethkomp> <201212020806.55695.michaelkintzios@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201212020806.55695.michaelkintzios@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Provags-ID: V02:K0:JHM4yBM7/QKU313Qp4cQuQ2IhntCym6Y8KQ5D1MgIiZ 7up4FOg5i09m9Rtru+qjS8IcTXijs9TX0FC/FseFLlayu/ZyCd YfR8XQtlE4w7LQBX9JTPs86H1dpNao697I19ZX0NzMKGKciMwl QXVSxBC+VWewJYvVDuQ793IUzuSIjF45Lq37bPsi5LNVC4MgWq HbOc3m3WoOj6yV7K6r6VlSsobY4TOecSsbdgnzLMfRQH1OXkIB vlctE5yDVmnCwqB4/0YNQnjkcyKix25dqU2+vC32lKI1TlyuIc griSPnazjRB6P3fbeNug9GqZcseuCYEGqBP0cr/Vb5UyGKtJ/9 odIMDc9U2xIlqtc3GmAEjTVydBuUVJ42ThxibB5Xm X-Archives-Salt: 7ef3267a-bf3b-457f-8db2-4eb6d7590d8a X-Archives-Hash: 8b36ddda7d06f2e3ddccb3eb7b59a6fe On Sun, Dec 02, 2012 at 08:06:43AM +0000, Mick wrote: > > You can check if rc-update -s -v | grep numlock (or rc-status -s | grep > numlock) shows it being set, otherwise add it to see if this makes a > difference. > -- > Regards, > Mick Though there is no /etc/conf.d/numlock, Mick's post caused me to read /etc/init.d/numlock ... interesting. So if your "rc-update -s -v | grep numlock" shows numlock but no runlevel, you can determine from the aforementioned file how it got turned on. -- Happy Penguin Computers >') 126 Fenco Drive ( \ Tupelo, MS 38801 ^^ support@happypenguincomputers.com 662-269-2706 662-205-6424 http://happypenguincomputers.com/ Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting