Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!news.kei.com!sol.ctr.columbia.edu!startide.ctr.columbia.edu!wpaul From: wpaul@ctr.columbia.edu (Bill Paul) Newsgroups: comp.os.386bsd.questions Subject: Re: [FreeBSD/XFree86] Mouse woes Date: 2 Nov 1994 15:21:32 GMT Organization: The M00se Illuminati (bl00p!) Lines: 80 Message-ID: <398aps$pjl@sol.ctr.columbia.edu> References: <397ag6$nr1@dcsun4.us.oracle.com> NNTP-Posting-Host: startide.ctr.columbia.edu X-Newsreader: TIN [version 1.2 PL2] Daring to challenge the will of the almighty Leviam00se, Bruce Caruthers (bcaruthe@us.oracle.com) had the courage to say: : First of all, thanks to the people who have sent me help with getting : my serial ports configured. Well it must not have been enough because... : 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: COM1 at 0x3f8 IRQ 3 COM2 at 0x2f8 IRQ 4 COM3 at 0x3e8 IRQ 5 COM4 at 0x2e8 IRQ 9 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. : 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. : - At 1200, they jump to the bottom left corner and sit there : forever at the slightest touch. : - At 4800 [...] : - At 9600 [...] : Does anyone have any suggestions? I'd really like to get X working : properly on my system. 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: 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 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. 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: # # Mouse definition and related parameters # MouseSystems "/dev/cua01" <-- use your real mouse port here # BaudRate 9600 # SampleRate 150 # Emulate3Buttons Note that I have the special settings turned off. The defaults seem to work well for me. Your mileage may vary. : Thanks, : -bkc -- -Bill Paul wpaul@ctr.columbia.edu