Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!sol.ctr.columbia.edu!news.kei.com!yeshua.marcam.com!charnel.ecst.csuchico.edu!olivea!sgigate.sgi.com!enews.sgi.com!decwrl!gatekeeper.us.oracle.com!dcsun4.us.oracle.com!bcaruthe From: bcaruthe@us.oracle.com (Bruce Caruthers) Newsgroups: comp.os.386bsd.questions Subject: Re: [FreeBSD/XFree86] Mouse woes Date: 4 Nov 1994 08:19:21 GMT Organization: Oracle Corporation, Redwood Shores, Calif. Lines: 141 Message-ID: <39cqq9$knv@dcsun4.us.oracle.com> References: <397ag6$nr1@dcsun4.us.oracle.com> <398aps$pjl@sol.ctr.columbia.edu> NNTP-Posting-Host: kate.us.oracle.com In article <398aps$pjl@sol.ctr.columbia.edu>, Bill Paul <wpaul@ctr.columbia.edu> wrote: >Daring to challenge the will of the almighty Leviam00se, Bruce Caruthers >(bcaruthe@us.oracle.com) had the courage to say: > [...] >: I still can't get the second serial port on the multi-card to be >: found by FreeBSD -- does the kernel only recongize it if there is >: something attached to it? > >...you apparently haven't got it right yet. No, there doesn't have to >be anything plugged into the port in order for FreeBSD to detect it. It >just has to be jumpered for the correct I/O address and IRQ. The kernel >looks for 4 standard serial ports: I have tried all of the above, and many other possible combinations, both from what the CMOS reports, what my DOS comm programs think, etc. I have tried both using the COMx defines, as well as setting the values explicitly. The asking about whether something needed to be attached was just a desperate hope. >If your second serial port isn't jumpered to one of these combinations, >the GENERIC?? kernel ain't gonna find it. Refer to your I/O card's >documentation for jumper setting instructions or learn how to build >a new kernel with custom settings. The CMOS and comm programs think it is COM4 at 0x3e8, irq 5. I tried that and many other combinations (as I mentioned above). See above. I have built many kernels (and not just for PC Unices). I *am* considering replacing the multi-card. (Although everything works fine for DOS/MSW/MSWinNT [except for 1280x1024 mode for the WinNT 3.5 S3 driver, where the mouse disappears, if that is an indicator of anything].) >: But, on to the more important question. I have a MouseSystems >: OmniMouse II and III, and cannot get either to work properly. It >: seems to be a baud-related problem. > >Bzzzt. I'm sorry, that's incorrect but thanks for playing. As a consolation >prize, I'll tell you what the real problem is. Ah, the gentle kindnesses of the net overwhelm me. >There's a disagreement between what your mouse thinks it is and what >X thinks it is: either the mouse is set to use Micro$oft mouse protocol >and the X server has been told (via the Xconfig file) to expect >MouseSystems, or vice-versa. This can be fixed in one of two ways: If it means anything, I can connect via cu to the port the mouse is one, and if I move the mouse, I get a hangup signal (actually, I am not sure I tried this at 1200 baud). So, the mouse *is* connected at least somewhat (as I mentioned, it does sort of move at certain settings). >1) A lot of MouseSystems compatible mice have a switch on their bottom > sides to allow you to choose between MouseSystems protocol and Micro$oft > mouse protocol. The switch is usually labeled 'PC' on one side and > 'MS' on the other. If your rodents have this switch, check that it's > set to the 'PC' position That would be the Mouse Systems White Mouse, according to my manual. I have the OmniMouse II. To quote from the manual: "Mouse Systems Mice come with either two or three buttons. The two button mice are plug-compatible with the Microsoft serial mouse. Your application software should be configured for a Microsoft serial mouse, and the buttons will act identically to the Microsoft mouse." I have the two button (beige) mouse. I will give Microsoft, 1200 another try. The three button optical mouse (MSC PC Mouse) is one I got that they were going to get rid of from work (not broken, the person just preferred the MO mouse). I do not have a manual specifically for it, although its model is at least partially covered in the other mouse's manual. > Similarly, some mouses (like the old one I used to use before it > broke) let you switch modes by pressing down on one of the buttons > when the computer is first switched on. My old mouse would come up > in Micro$oft mode by default, but when I held down the left button > at power-up it switched to MouseSystems. I did not know about this one, and will try it next time I reboot to FreeBSD. The manual for the mouse makes no reference to this. >2) You botched up your Xconfig file and you were too lazy to install > the man pages and read the instructions to figure out where you went > wrong. Check the mouse configuration section -- it should look like this: Thanks for being so quick to assume I ask for help without trying anything first. I have read the Xconfig scripts (since they died during the autoconfig run) and man pages, and have tried the various options for Microsoft and MouseSystems (dtrclear, rtsclear, etc.) mice. I have the manual for my mouse, as well, which claims that it is 1200-8-N-1, as per standard mice, according to the Xconfig man pages. ># ># Mouse definition and related parameters ># >MouseSystems "/dev/cua01" <-- use your real mouse port here /dev/tty0[01] (tried configuring for each address in various kernels -- no difference) ># BaudRate 9600 That's what I have been playing with. ># SampleRate 150 Logitech only, according to the Xconfig man pages. ># Emulate3Buttons Haven't gotten far enough to worry about this one. > Note that I have the special settings turned off. The defaults seem to > work well for me. Your mileage may vary. I tried the defaults. They didn't work (mileage = 0). That's why I posted for help. Although I think I tried nearly every combination of mouse configs, I will try them all again (unless one suddenly starts working). Maybe I didn't try one particular combination after changing some other variable. Perhaps someone can suggest a combination I might not think to try, working only from the man pages and the sample Xconfig files? Is anyone else using a MSC OmniMouse II? Thanks, -bkc -- Bruce Caruthers bcaruthe@Oracle.Com bkc@cs.Princeton.Edu "To get the attention of a large animal, be it an elephant or a bureaucracy, it helps to know what part of it feels pain. Be very sure, though, that you want its full attention." -- Kelvin Throop, "Analog" Dec 1984