On Tue, Mar 09, 2004 at 05:48:32PM +0100, Mike Crosland wrote: > On Tue, 9 Mar 2004 02:54:24 +0100, Bernd Walter <ticso_at_cicely12.cicely.de> > 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_at_bwct.de info_at_bwct.deReceived on Tue Mar 09 2004 - 08:06:40 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:46 UTC