Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!lynx.aba.net.au!munnari.OZ.AU!spool.mu.edu!howland.erols.net!newsfeed.internetmci.com!news.mathworks.com!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: ps/2 mouse problems Date: 31 Aug 1996 15:40:54 GMT Organization: Private BSD site, Dresden Lines: 23 Message-ID: <509me6$7uq@uriah.heep.sax.de> References: <501trq$l6v@cronkite.cisco.com> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E "Keith A. Tomkins" <ktomkins@cisco.com> wrote: > Everything seemed to go OK until I tried to fire up > Xwindows. I have the pointer set up as a ps2 mouse (psm0) but when I > try to crank up X, it complains that the mouse is not > configured. The device exists in /dev. I then The non-existance of the device node would have caused the message ``No such file or directory'' (ENOENT). The message ``Device not configured'' (ENXIO) means that the driver is not available, or the device does not respond. > looked at dmesg and it complained that the ps2 mouse was not probed due to a > conflict. Quote this message. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)