Date: Wed, 24 Jun 1998 22:38:49 +0100 (BST) From: Duncan Barclay <dmlb@ragnet.demon.co.uk> To: Greg Lehey <grog@lemis.com> Cc: freebsd-hardware@FreeBSD.ORG, Chris Dillon <cdillon@wolves.k12.mo.us> Subject: Re: PS/2 Mouse resolution. Message-ID: <XFMail.980624223849.dmlb@computer.my.domain> In-Reply-To: <19980624173514.L5023@freebie.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24-Jun-98 Greg Lehey wrote: > On Thu, 18 June 1998 at 18:30:46 -0500, Greg Lehey wrote: >> On Thu, 18 June 1998 at 0:03:50 -0500, Chris Dillon wrote: >>> On Fri, 12 Jun 1998, Greg Lehey wrote: >>> >>>> On Thu, 11 June 1998 at 18:34:38 -0500, Chris Dillon wrote: >>>>> On Thu, 11 Jun 1998, Duncan Barclay wrote: >>>>> >>>>>> Just upgraded my motherboard to one with a PS/2 port on it (FIC PT-2007, >>>>>> 430TX). >>>>>> >>>>>> I moved my mouse (Logicitech MouseMan) from sio0 to the PS/2 port and it >>>>>> is now >>>>>> "slower" and a pain to use under X. I guess the resolution has >>>>>> increased, can >>>>>> moused be used to fake it back top where it was before? >>>>>> >>>>>> I've tried upping the X acceleration but don't really like it, feels >>>>>> wrong. >>>>>> >>>>>> I don't want to go back the serial port, I want it for the console of >>>>>> my (new) crash box. >>>>> >>>>> I noticed something similar when I bought this new trackball, which sits >>>>> on the PS/2 port. The cursor zips across the screen fast enough, but >>>>> selecting text in an xterm is a whole different story. It used to be >>>>> that >>>>> when I clicked/dragged to select text the "reverse" selection followed >>>>> the >>>>> cursor perfectly. Now it lags behind the cursor and updates in bursts. >>>>> Weird, eh? Anyone know why this happens? >>>> >>>> Interesting. The "updates in bursts" looks like an interrupt problem. >>>> I've had similar problems, but I hadn't associated them with the >>>> change from serial to PS/2. I'm currently using a MouseMan on a >>>> serial port on my laptop, and it works fine, but I've been having real >>>> problems on my "real" machine with a PS/2 port. I thought it was the >>>> screen resolution (1600x1200) which was causing the problems, but now >>>> I'll investigate more carefully. >>> >>> If it were an interrupt problem, wouldn't the cursor itself move jumpily >>> and not just the inverse selection? >> >> Yes. That's what comes of not reading the message carefully. Of >> course, it could still be a conflict with disk access. >> >>> It moves even more fluidly than with my serial mouse (of course, it >>> was a cheap low-res mouse). >> >> My impression is that the same mouse (convertible) is smoother on a >> serial connection than on the PS/2 connector. As I said, I'll try >> this out when I get home. > > I'm home now, and I've tried it out. It turns out my recollection was > defective: the mouse was already connected as a serial mouse. I tried > it on PS/2, and as Duncan Barclay observes, the mouse slowed down. > 'xset m' doesn't help much either--if I really speed it up, it jumps > in increments of up to 10 pixels. Some of this may be due to the old > version of Xinside I'm using, of course. Did you try $ moused -r high ? Works for me, I found it in psm(4). > Greg > -- > See complete headers for address and phone numbers > finger grog@lemis.com for PGP public key --- ________________________________________________________________________ Duncan Barclay | God smiles upon the little children, dmlb@ragnet.demon.co.uk | the alcoholics, and the permanently stoned. ________________________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.980624223849.dmlb>