From owner-freebsd-questions@FreeBSD.ORG Thu Mar 27 19:38:02 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C834737B401 for ; Thu, 27 Mar 2003 19:38:01 -0800 (PST) Received: from mail.airnet.com.au (mail.airnet.com.au [202.174.32.5]) by mx1.FreeBSD.org (Postfix) with SMTP id EC15743FCB for ; Thu, 27 Mar 2003 19:37:59 -0800 (PST) (envelope-from ws@senet.com.au) Received: (qmail 16424 invoked from network); 28 Mar 2003 03:37:58 -0000 Received: from dsl2-81.gw1.adl1.airnet.com.au (HELO predatorii) (202.174.37.81) by mail.airnet.com.au with SMTP; 28 Mar 2003 03:37:58 -0000 Message-ID: <01c401c2f4dc$3c0a84e0$0264a8c0@regional.net.au> From: "W. Sierke" To: "Greg 'groggy' Lehey" References: <019301c2f458$38276340$0264a8c0@regional.net.au> <20030328002850.GG47524@wantadilla.lemis.com> Date: Fri, 28 Mar 2003 14:13:45 +1030 Organization: OVirt Technologies MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Status: No, hits=-6.6 required=5.0 tests=AWL,EMAIL_ATTRIBUTION,REFERENCES autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) cc: freebsd-questions@FreeBSD.org Subject: Re: Mitsubishi Diamond Touch keyboard problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Mar 2003 03:38:05 -0000 Greg 'groggy' Lehy wrote: >This is probably a timing problem with the keyboard. I had a couple >I'd suggest you try 4.8 or 5.0 and see if the problem persists. You Thanks for that, Greg. In fact I had originally attempted an install of 5.0 and when I sought assistance with that same problem it was suggested that I drop back to 4.7. So the problem does still appear to be present. Who could I speak to in order to determine whether any assistance can be offered in debugging any outstanding issues with this keyboard? Thanks, Wayne