From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 09:06:40 2004 Return-Path: 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 8350416A4CE for ; Tue, 9 Mar 2004 09:06:40 -0800 (PST) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1A0243D31 for ; Tue, 9 Mar 2004 09:06:39 -0800 (PST) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) i29H6NrQ038499 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Tue, 9 Mar 2004 18:06:26 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [IPv6:3ffe:400:8d0:301::12]) by cicely5.cicely.de (8.12.10/8.12.10) with ESMTP id i29H6AQn044094 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Mar 2004 18:06:10 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.12.10/8.12.10) with ESMTP id i29H69c5092749; Tue, 9 Mar 2004 18:06:09 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.12.10/8.12.10/Submit) id i29H68GM092748; Tue, 9 Mar 2004 18:06:08 +0100 (CET) (envelope-from ticso) Date: Tue, 9 Mar 2004 18:06:08 +0100 From: Bernd Walter To: Mike Crosland Message-ID: <20040309170608.GH95533@cicely12.cicely.de> References: <20040308232730.GA1323@cnd.mcgill.ca> <20040309015423.GV95533@cicely12.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely12.cicely.de 5.2-CURRENT alpha User-Agent: Mutt/1.5.6i X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.61 X-Spam-Report: * -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on cicely5.cicely.de cc: freebsd-current@freebsd.org cc: ticso@cicely.de cc: Mathew Kanner Subject: Re: FreeBSD 5.2.1 usb problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Mar 2004 17:06:40 -0000 On Tue, Mar 09, 2004 at 05:48:32PM +0100, Mike Crosland wrote: > On Tue, 9 Mar 2004 02:54:24 +0100, Bernd Walter > wrote: > > >On Mon, Mar 08, 2004 at 06:27:30PM -0500, Mathew Kanner wrote: > >>On Mar 08, Mike Crosland wrote: > >>> I have a problem with getting my usb mouse/keyboard combination > >>running in > >>> FreeBSD. It's a Logitech diNovo, and although both keyboard and mouse > >>both > >>> work fine under Linux I can only get the keyboard working under > >>FreeBSD. > >>> The mouse is correctly recognised when booting, but is given the same > >>usb > >>> device address as the keyboard. Using 'cat /dev/usm0' gives no > >>output, and > >>> attempts to use /dev/usm0 reports that the device is busy. Is it > >>possible > >>> to manually assign usb device addresses in order to try and work round > >>> this? > >> > >> Hello Mike, > >> ISTR that we have problem with mice/keyboards using different > >>interfaces on the same device (my usb memory is extremly hazy). > > > >This shouldn't happen (tm). > >Both ums(4) and ukbd(4) are interface level driver and shouldn't have > >problems with other drivers on different interfaces of the same device. > > > > It seems a similar problem has already been submitted. A search on freebsd > bugs shows this problem has already been reported. > http://news.gw.com/freebsd.bugs/28887 > My excuses for the duplication. Correct me if I'm wrong, but this report is about ums problem with a mice and not with ukbd/ums in a single device. I think that this is a single device hasn't anything to do with the problem itself, but I will recheck if the source takes the correct pipes for each interface. We have had similar sounding problems with mice only devices. When connected to PS/2 the protocol changes so inkompatibilities are specific to that. -- B.Walter BWCT http://www.bwct.de ticso@bwct.de info@bwct.de