Return to BSD News archive
From: Keith Walker <kew@phobos.walker.org> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Problems with moused 2.2 BETA Date: 03 Feb 1997 07:15:19 -0800 Organization: Keith's House Lines: 38 Message-ID: <87enexyl87.fsf@phobos.walker.org> References: <stanbE4ztu0.DHx@netcom.com> NNTP-Posting-Host: natca.spk.wa.us X-Newsreader: Gnus v5.2.25/XEmacs 19.14 Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!news.enteract.com!news.maxwell.syr.edu!news.mathworks.com!uunet!in2.uu.net!206.96.83.98!news.dsource.com!cnn.isc-br.com!phobos.walker.org!usenet Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:34989 stanb@netcom.com (Stan Brown) writes: > > I have a ps/2 mouse which works fine while runing X. However, I have > been unableto get moused to work. I have tried thisas root, so I'm > pretty sure it's not a permissions problem. > > When I run moused -f -d -t ps/2 -p /dev/psm0, I get the error message > "Read returned -1 : Resource temprarily unavailable" > > I do not have X runing when I try this. I no longer have /etc/sysconfig > set up to start moused. > > What could I be doing wrong here? > The ps/2 device uses a non-blocking interface and the moused program isn't equipped to handle this (unlike X). The quickest fix is to create another device file that has a blocking interface like the other drivers: # cd /dev # mknod # ll psm0 crw------- 1 root wheel 21, 1 Feb 3 06:50 psm0 # mknod psm1 c 21 0 # ll psm? crw------- 1 root wheel 21, 1 Feb 3 06:50 psm0 crw-rw-r-- 1 root wheel 21, 0 Feb 3 07:08 psm1 Now use the "/dev/psm1" device with moused and all will be well. The best way to fix the problem is to fix moused, but this works just as well. -- keith.