Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.Hawaii.Edu!news.uoregon.edu!hunter.premier.net!news-peer.gsl.net!news.gsl.net!news.mathworks.com!uunet!in3.uu.net!news.iij.ad.jp!nr1.scn.co.jp!sinfony-news!wnoc-tyo-news!news.nc.u-tokyo.ac.jp!train.ad.jp!iroha.utsunomiya-u.ac.jp!nikko.utsunomiya-u.ac.jp!yokota From: yokota@zodiac.mech.utsunomiya-u.ac.jp. (Kazutaka YOKOTA) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: How to tst my mouse ? Date: 17 Oct 1996 05:48:05 GMT Organization: Utsunomiya University, Utsunomiya, Japan Lines: 43 Message-ID: <544hal$otj@nikko.utsunomiya-u.ac.jp> References: <stanbDzC874.J5B@netcom.com> NNTP-Posting-Host: zodiac.mech.utsunomiya-u.ac.jp X-Newsreader: mnews [version 1.18] 1994-05/16(Mon) stanb@netcom.com wrote: stanb>> Well as the sating goes I have good news, and I have bad news. stanb>> stanb>> Firt the good news. Through the auspices of a very kind person, stanb>>I have managed to make my HP Vectra runig FreeBSD star X without stanb>>crashing the machine. It turns out that Vectras use a PS/2 mouse. stanb>> stanb>> Now the bad news. Now that I have X running, I still can't get stanb>>the mouse to do anything. I have recompiled the kernel with psm0 support stanb>>Correclty (I think). I have run MAKEDVE psm0, and still no go. stanb>> stanb>> Can anyone sugest a way to check the hardwre and software (kernel stanb>>build etc) without haveing to load windoze on this machine ? Assuming you are using version 2.1.X-RELEASE and XFree86, I think there two possibilities: The first possibility is that when you configured your X server, you somehow failed to specify "PS/2 mouse" for the pointing device. Check /usr/X11R6/lib/X11/XF86Config, and make sure the following lines appear in the "Pointer" section: Protocol "PS/2" Device "/dev/psm0" You may add the above lines by hand, or you may run `xf86config'. The second possibility is that the `psm0' device driver does not successfully detect your PS/2 mouse. It it known that the probe routine of the `psm' device driver is not very reliable and has caused many troubles to many people. Check messages during system boot up process; if the device driver detects a mouse, you will see something like "psm0 at 0x60-0x63 irq 12 on motherboard". (You can also use the `dmesg' command to print the messages after the system has booted.) If the device driver fails to recognize your mouse, well, you need an improved or hacked driver. I myself had to fight with the driver to recognize my PS/2 mouse recently, and modified the source code of the `psm' driver so that the probe routine will find a mouse in more reliable and robust manner. If the cause of your trouble is the `psm' device driver and you are interested in my hacked driver, contact me, and I will send you my code.