Date: Mon, 11 Oct 2010 13:56:10 -0700 From: Gary Kline <kline@thought.org> To: Polytropon <freebsd@edvax.de> Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: mouse problems.... Message-ID: <20101011205610.GA3261@thought.org> In-Reply-To: <20101011221609.b2cff60e.freebsd@edvax.de> References: <20101011032642.GA3354@thought.org> <20101011164152.GA4652@thought.org> <20101011193153.758efde5.freebsd@edvax.de> <20101011181438.GA5076@thought.org> <20101011202741.9e107460.freebsd@edvax.de> <20101011191443.GA5223@thought.org> <20101011213216.0d19ed70.freebsd@edvax.de> <20101011194907.GB5223@thought.org> <20101011221609.b2cff60e.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 11, 2010 at 10:16:09PM +0200, Polytropon wrote: > On Mon, 11 Oct 2010 12:49:07 -0700, Gary Kline <kline@thought.org> wrote: > > I got a reply from grepping ums and a truckload from usbdev -s. > > Copied to my `posit' notes or whatever: > > > > > > ethic# dmesg | grep ums > > ums0: <rand Combo Free KVM, class 0/0, rev 1.10/0.00, addr 3> on uhub4 > > ums0: 5 buttons and Z dir. > > ethic# > > The mouse is detected. Good. > > A problem that now comes to my mind is that switching from / to > the "ethic" machine might confuse the USB subsystem, as a device > disappears and later appears. Although USB is capable of hot plug, > the USB subsystem might not be able to pick up the mouse correctly. > > You could try: > > # moused -d -f -p /dev/ums0 -t auto > > Then debugging messages should appear on the console, and a moving > mouse cursor should be visible. > i tried this remove on _this_ console; then buttoned over to `ethic' [server], killed the moused that was running. Indeed it was /dev/ums0! But the mouse was frozen, and afer I killed it, gone. Then I tried your line and got the data stream. But there was no mouse. ... > > > > I was able to balanced anf get forward enough to see what my > > friend did. The keyboard *is* a PS/2; it is plugged into a new > > adaptor that plugs into the USM slot. The (`Logitech') mouse is > > already a USB and plugs nto the second USB slot/jack on the KVM. > > So it's a "pure USB" solution for the mouse - should be no problem. > > > > > As noted, things are happy on my linux desktop, but not on my > > FBSD boxen. Any ideas how to rebuild things to the new USB > > protocol? > > Which "new" protocol? USB 3.0 for the three buttons? :-) There are two buttons and the mouse "wheel"; I have no clue what's next. Clearly, my 7.2.X sees the mouse. But when I typed simply # startx the windows are there; the mouse cursor hangs, dead-center. > > No, honestly: I think the problem is somewhere in the interaction > of the KVM switch and the FreeBSD USB subsystem which has influence > on how moused handles the mouse. > > Can you check "forcing the mouse on" as described above? If it is > present in dmesg (from boot time on, and NOT switched away and on > again), and also listed in the current state per usbdevs command, > it should be picked up. > > As far as I understood in regards of X, there is > > a) X using the mouse provided through moused, or > > b) X detecting it "itself" by HAL and DBUS. > > Do you use HAL and DBUS with X? > Dunno; I do have hal and dbus there; that's about all I can say. Do I check with ps -ax | egrep "hal|dbus"? gary > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... -- Gary Kline kline@thought.org http://www.thought.org Public Service Unix The 7.90a release of Jottings: http://jottings.thought.org/index.php http://journey.thought.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101011205610.GA3261>