From owner-freebsd-questions@FreeBSD.ORG Wed May 16 02:16:11 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7F99C16A403 for ; Wed, 16 May 2007 02:16:11 +0000 (UTC) (envelope-from mfitzgerald@pacific.net.au) Received: from pecan.exetel.com.au (pecan.exetel.com.au [220.233.0.17]) by mx1.freebsd.org (Postfix) with ESMTP id 4616713C44C for ; Wed, 16 May 2007 02:16:10 +0000 (UTC) (envelope-from mfitzgerald@pacific.net.au) Received: from 28.101.233.220.exetel.com.au ([220.233.101.28] helo=[192.168.1.4]) by pecan.exetel.com.au with esmtp (Exim 4.63) (envelope-from ) id 1Ho93h-00015B-Dn for freebsd-questions@freebsd.org; Wed, 16 May 2007 12:16:09 +1000 Mime-Version: 1.0 (Apple Message framework v624) In-Reply-To: <6e92b764a1758622d8ce613b9d17fa37@catholic.org> References: <01cb8c224a7358a4c6a49f5b4b4bc0f0@catholic.org> <46498FFA.8070902@tomjudge.com> <6e92b764a1758622d8ce613b9d17fa37@catholic.org> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Malcolm Fitzgerald Date: Wed, 16 May 2007 12:16:08 +1000 To: freebsd-questions@freebsd.org X-Mailer: Apple Mail (2.624) Subject: Re: Computer wakes, keyboard sleeps on X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 May 2007 02:16:11 -0000 On 15/05/2007, at 8:48 PM, Tom Judge wrote: > Never you mind wrote: >> The keyboard stays asleep after everything else has woken up. How do >> I begin troubleshooting this problem? >> I use a KVM switch to share the KVM between two machines. The other >> machine runs Windows, everything works as it should there. >> Malcolm > > Does the KVM you are using have keyboard and mouse emulation for when > the system is not active on the KVM. It works as it should after reconnecting the keyboard. I had checked the connections before posting because that seemed the most likely cause but it seems that I did the job properly this time. thanks