Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!nntp.coast.net!news.kei.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: XFree86-3.2 & Microsoft Mouse Date: 30 Nov 1996 17:06:18 GMT Organization: Private BSD site, Dresden Lines: 27 Message-ID: <57ppia$2ae@uriah.heep.sax.de> References: <23933722.u8t20e.34e60@slip106.termserv.siu.edu> 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 jimd@slip106.termserv.siu.edu (Jim Dutton) wrote: > I have installed V3.2 of XFree86 on a Gateway-2000 using a "true" Microsoft > mouse, and FreeBSD 2.2-SNAP. > > In the kernel configuration, /dev/psm0 is commented out and its I/O address > conflicts with that for scd0 (sc0 ?) - the SCSI disk (controller). Basically, yes. Except no, it's not a disk controller, it's the keyboard controller. And no, it doesn't _really_ conflict with it, it's only that config(8) needs to know that both share some resources. Hence the keyword ``conflicts''. And no, psm0 is not what you are looking for if you've got a Mickeysoft mouse; those mice are serial mice, hence you need to specify /dev/ttyd0 or /dev/ttyd1 as the mouse device. You should _really_ have used XF86Setup to accomplish all of this. You can navigate through the mouse setup screen there using your keyboard, and empirically ``probe'' for your mouse. -- 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. ;-)