Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!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 and keybd conflict ... Date: 19 Jul 1996 10:37:47 GMT Organization: Private BSD site, Dresden Lines: 23 Message-ID: <4snohr$46c@uriah.heep.sax.de> References: <4slepf$r3l@crl.crl.com> <4sm93t$7p2@uriah.heep.sax.de> <4sn3q4$dg6@crl.crl.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 medrecjm@crl.com (John Mosser) wrote: > Thanks J"org, I'll give that a try, however I've been advised by one of the > FreeBSD development team that this problem is fixed with 2.1.5. 2.1.5? I don't remember what might have been changed there. In -current (and all 2.2-SNAPs therefore), psm0 is in the kernel by default, since the configuration file knows about a keyword `disable' there. This allows to configure an offending driver like psm, but keep it disabled initially. People who really have a PS/2 mouse can enable it via UserConfig then. (The driver is `offending' since it tends to jam the keyboard controller when there's no PS/2 mouse present. This is likely a bug, but there are 23000 different keyboard controllers around, and it's often very hard to get it right for all of them.) -- 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. ;-)