From owner-freebsd-stable@FreeBSD.ORG Wed Oct 8 15:56:34 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0BA116A4BF for ; Wed, 8 Oct 2003 15:56:34 -0700 (PDT) Received: from 100m.mpr200-1.esr.lvcm.net (100m.mpr200-1.esr.lvcm.net [24.234.0.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AAAB43FCB for ; Wed, 8 Oct 2003 15:56:33 -0700 (PDT) (envelope-from sevn@dangpow.com) Received: from dangpow.com (ip68-104-88-107.lv.lv.cox.net [68.104.88.107]) by 100m.mpr200-1.esr.lvcm.net (Mirapoint Messaging Server MOS 2.9.3.5) with ESMTP id BFL22686; Wed, 8 Oct 2003 15:56:30 -0700 (PDT) Message-ID: <3F84961E.1080607@dangpow.com> Date: Wed, 08 Oct 2003 15:56:30 -0700 From: 7 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030903 Thunderbird/0.2 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Keyboard Controller woes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Oct 2003 22:56:34 -0000 Hello There, Happy Wednesday Yall. I had a business partner ask me a question about something that seriously rang a bell, but I could not find the reference after much searching. It's a problem I think I used to have on a LX based intel board a while ago, but I can't remember. If he cold boots a certain machine without a keyboard (ps/2) plugged in, then tries to plug one in after it's up and running, it won't work. However if he already has a keyboard plugged in when he boots, then unplugs it and leaves it that way for days, then plugs the keyboard in it works fine. The whole point is he'd rather not have to be there to plug a keyboard into each of 50 1U rackmounts when they need rebooted to be sure they will work later. He's running the latest redhat on the exact same 1U's and they don't display the same behavior. I was *sure* this was something simple I read in LINT or on the mailing list at some point, but I'm not sure. Damn time and age and all that. Anyone remember what I'm talking about? It was something to do with a kernel config parameter if I'm not mistaken that fixed this issue with the keyboard controller. If I'm not mistaken, he's using 4.8 release updated with RELENG_4_8. If someone could just point me in the right direction, I'd be much appreciative. After searching all day I'm burnt. THANKS IN ADVANCE!