Date: Thu, 29 Oct 1998 08:11:38 -0500 From: Stephen A Derdau <sderdau@ne.mediaone.net> To: Christopher Raven <c.raven@ukonline.co.uk> Cc: Robert Nesius <nesius@europa.com>, freebsd-questions@FreeBSD.ORG Subject: Re: Mouse Message-ID: <3638698A.66F4A9D5@ne.mediaone.net> References: <v03110701b25dc4ea8bea@[204.202.55.93]> <36385D2F.F9AF9F07@ukonline.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Could there be a i/o irq conflict ? Christopher Raven wrote: > > Robert Nesius wrote: > > > > Greetings, > > I've spent several hours over the past few days trying to get my > > mouse recognized by the xserver on my freebsd box. Alas, my > > efforts to this point have been unsuccessful and I must avail > > myself of the resources this list has to offer. My thanks > > in advance. :) > > > > Details: > > P133 with DB9 serial port interface for mouse. > > The mouse: Logitech 3-button mouse with ps/2 bus connector attached > > to the DB9 port using an adapter. > > The OS: FreeBSD 2.2.6. > > > > Problem - mouse not recognized by X server. Can't get cursor to move > > during XF86Setup. > > > > What I've tried: > > I would like to use moused. I've configured moused to point at > > /dev/cuaa0, and have linked /dev/mouse to /dev/sysmouse. I've > > specified the moused_protocol in rc.conf to be many things, > > including ps/2, logitech, busmouse, mouseman, etc... With > > ps/2 as the protocol, moused complains about a "-t" option. > > I have specified NO options in the rc.conf file in the moused > > options area. I /have/ insured that ps2 driver support has been > > built into the kernel. With 'logitech' specified as the protocol, > > moused seems to come up cleanly, although I really don't know how > > to confirm if moused has attached to a device and recognized it > > as a mouse. > > > > In XF86Setup, I have tried to specify the protocol as just about > > every possibility available, with the device either being /dev/cuaa0 > > (probably not the right thing to do with moused running), or as > > /dev/mouse. Also, I've tried several combinations of options without > > moused. For some reason, I just can't get the cursor to move > > after hitting the "Apply" button. > > > > At this point I'm wondering if: > > a) Anyone else has tried to get a logitech mouse with a DB9 adapter running > > under this version of 2.2.6. > > b) If anyone knows if the adapter is forcing the logitech mouse to look like > > an ordinary serial mouse, or a real ps/2 mouse, or logitech mouse, or > > what? > > c) How can I confirm that moused really found a device to talk to? > > d) How can I confirm that cuaa0 is really the device to point moused at? > > > > I searched the FAQs and mailing lists. I feel that I have an intuitive > > understanding of what's happening, but I just can't get things to go. > > > > Thanks again for your assistance. :) > > > > -Rob > > > > Not really an answer to your questions, but have you tried using > another serial port? I found that one of my motherboard types > (Micronics Twister AT) doesn't seem to let the mouse run on port 1 > (com 1) (? I think) under FreeBSD but fine under Win '95. Swapping > over allowed FreeBSD to see it. > > -- > Christopher Raven > E-mail: c.raven@ukonline.co.uk & ICQ: 2254369 > http://www.FreeBSD.org/ "The Power To Serve" > http://www.unmetered.org.uk/ "A PC is for life, not just for Xmas" > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3638698A.66F4A9D5>