Return to BSD News archive
Path: euryale.cc.adfa.oz.au!como.dpie.gov.au!news.gan.net.au!act.news.telstra.net!news.telstra.net!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!news-peer.sprintlink.net!news.sprintlink.net!Sprint!howland.erols.net!newsfeed.internetmci.com!in1.uu.net!202.232.2.100!np1.iij.ad.jp!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: PS/2 mouse not available Date: 18 May 1997 03:02:16 GMT Organization: Utsunomiya University, Utsunomiya, Japan Lines: 60 Message-ID: <5llrfo$2v2$1@nikko.utsunomiya-u.ac.jp> References: <337B7C0B.36B3@arscorp.com> NNTP-Posting-Host: zodiac.mech.utsunomiya-u.ac.jp X-Newsreader: mnews [version 1.19PL2] 1996-01/26(Fri) Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:41149 In article <337B7C0B.36B3@arscorp.com> for comp.unix.bsd.freebsd.misc Joseph Mack wrote: mack>>I've newly arrived from the Linux world and am mack>>trying to get my mouse (and XF86) running. mack>> mack>>I'm running FreeBSD 2.2.1 on a 90MHz Pentium with a PS/2 2 button mack>>Microsoft Mouse (Mouse Port compatible). I've activated the PS/2 mack>>mouse in UserConfig and it is detected on boot up (IRQ12 I think) So far, so good. mack>>startx returns "None of the configured devices where detected" How the Pointer section of your XF86Config look like? a) If you are NOT using `moused' and you want to use the PS/2 mouse, you need to have the following lines there. Protocol "PS/2" Device "/dev/psm0" b) If you ARE using `moused', the lines should be: Protocol "mousesystems" Device "/dev/sysmouse" and your `/etc/sysconfig' should contain mousedtype=ps/2 mousedport=/dev/psm0 mack>>I assume the mouse (at least) is not being seen. mack>>To see if the mouse is connected to the kernel I've done mack>> mack>>cat /dev/psm0 mack>> mack>>which gives "Resource temporarily unavailable" This is normal. /dev/psm0 is a non-blocking device node and returns that error code, if no data is available when read. If you want to test your PS/2 mouse, do the following: 1. Make sure `moused' is not running. Kill it if it does. 2. `su' to root and type `moused -f -d -t ps/2 -p /dev/psm0'. 3. This will run `moused' in the debug mode and print data bytes when you move your mouse. 4. See if `button', `dx', and `dy' status changes properly when you move/click the mouse. 5. ^C to quit. 6. Run `moused' again. This time in the daemon mode by typing `moused -t ps/2 -p /dev/psm0'. 7. Type `vidcontrol -m -on'. 8. This will activate mouse cut/paste in your current screen. See your mouse pointer moves, and marks text if you drag the pointer with the left button down. Kazu