From owner-freebsd-questions@FreeBSD.ORG Sat Jul 21 02:40:06 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D868216A417 for ; Sat, 21 Jul 2007 02:40:06 +0000 (UTC) (envelope-from zhangweiwu@realss.com) Received: from bossdog.realss.com (bossdog.realss.com [211.157.108.128]) by mx1.freebsd.org (Postfix) with ESMTP id 2C68E13C457 for ; Sat, 21 Jul 2007 02:40:06 +0000 (UTC) (envelope-from zhangweiwu@realss.com) Received: from localhost (unknown [127.0.0.1]) by bossdog.realss.com (Postfix) with ESMTP id ABA321C000B; Sat, 21 Jul 2007 10:40:17 +0800 (CST) Received: from bossdog.realss.com ([127.0.0.1]) by localhost (bossdog.realss.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20726-02; Sat, 21 Jul 2007 10:40:16 +0800 (CST) Received: from [218.193.55.195] (50.19.61.59.board.xm.fj.dynamic.163data.com.cn [59.61.19.50]) by bossdog.realss.com (Postfix) with ESMTP id 9A7B31C000A; Sat, 21 Jul 2007 10:40:15 +0800 (CST) From: Zhang Weiwu To: Nikola Lecic In-Reply-To: <200707202346.l6KNkdTY019727@smtpclu-5.eunet.yu> References: <1184965369.6013.21.camel@joe.realss.com> <200707202346.l6KNkdTY019727@smtpclu-5.eunet.yu> Content-Type: text/plain Organization: Real Softservice Date: Sat, 21 Jul 2007 10:33:47 +0800 Message-Id: <1184985227.7989.24.camel@joe.realss.com> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at bossdog.realss.com Cc: freebsd-questions@freebsd.org Subject: Re: mouse wheel doesn't work X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jul 2007 02:40:07 -0000 On Sat, 2007-07-21 at 01:42 +0200, Nikola Lecic wrote: > Yes, this is more likely -- the trackpoint and external ps/2 mouse > collide. Thank you for the information! Now I have made it work. 0) edit /etc/rc.d/moused, remove '-t {$mytype}' from moused parameter list: #/usr/sbin/moused ${myflags} -p ${myport} -t ${mytype} ${_pidarg} /usr/sbin/moused ${myflags} -p ${myport} ${_pidarg} 1) enter DOS mode with a Windows 98 rescue disk 2) use the PS2.EXE form Lenovo, run 'ps2.exe tpoint autodisable'; 3) reboot, enter FreeBSD, mouse wheel is working now. It's important to do step 0 because moused can only forward wheel scroll to X if it's invoked without "-t" parameter. I think there are two bugs: Bug A: As manual of moused says: For the PS/2 mouse: ps/2 This is the only protocol type available for the PS/2 mouse and should be specified for any PS/2 mice, regardless of the brand. In fact, it is wrong! If I invoke moused with -t ps/2, mouse wheel doesn't work. This doesn't work (according to manual it should): "moused -p /dev/psm0 -t ps/2" In fact, only this works: "moused -p /dev/psm0", no "-t" parameter. This must be a bug. 100% of all users who read the manual should directly conclude they should get equal or better result with -t ps/2 than with no "-t" parameter for their ps/2 mouse, this is wrong, they get better result without "-t" parameter. Bug B: As said in the manual, -t is an optional parameter. /etc/rc.d/moused should respect this. If user didn't specify -t, then it should not assume to use "-t microsoft", it should launch moused without "-t" parameter. Even if there is a good reason to assume the device is microsoft type, this assume logic should be placed in moused source code. Moused should be the one knowing how to handle different situation automatically and fall-back sanely. The rc.d script tries to do too much and think it's smarter then device driver on deciding device type without even communicating to device at all. This is a user's point of view and welcome developer with background knowledge to correct me. Thanks again Nikola for helping me out! Best Regards Zhang Weiwu