From owner-freebsd-current@FreeBSD.ORG Fri Oct 15 13:30:14 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4162316A4CE for ; Fri, 15 Oct 2004 13:30:14 +0000 (GMT) Received: from out002.verizon.net (out002pub.verizon.net [206.46.170.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBC6B43D41 for ; Fri, 15 Oct 2004 13:30:13 +0000 (GMT) (envelope-from Alex.Kovalenko@verizon.net) Received: from [10.0.3.231] ([138.89.97.54]) by out002.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20041015133013.DUGM22336.out002.verizon.net@[10.0.3.231]>; Fri, 15 Oct 2004 08:30:13 -0500 From: "Alexandre \"Sunny\" Kovalenko" To: Jose M Rodriguez In-Reply-To: <200410121359.33918.josemi@freebsd.jazztel.es> References: <69b7b6901d.6901d69b7b@osu.edu><416BBED8.7020307@gmx.de> <200410121359.33918.josemi@freebsd.jazztel.es> Content-Type: text/plain; charset=ISO-8859-1 Message-Id: <1097847001.843.3.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 15 Oct 2004 09:30:02 -0400 Content-Transfer-Encoding: 8bit X-Authentication-Info: Submitted using SMTP AUTH at out002.verizon.net from [138.89.97.54] at Fri, 15 Oct 2004 08:30:11 -0500 cc: Jochen Gensch cc: freebsd-current@freebsd.org Subject: Re: ACPI Suspend -> /dev/ums0 dead X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Oct 2004 13:30:14 -0000 On Tue, 2004-10-12 at 07:59, Jose M Rodriguez wrote: > El Martes, 12 de Octubre de 2004 13:24, Jochen Gensch escribió: > > Jose M Rodriguez wrote: > > > There isn't mouse 'mux' support in FreeBSD's moused. You can use > > > only one. > > > > Sure that is true? I am using both at this moment on the console, so > > no X is runnig. Both with moused. I can activate usb mouse by moused > > -p /dev/ums0 and trackpoint by moused -p /dev/psm0. Usbd is running, > > too by the way. > > > > I think so. > > There's only one /dev/sysmouse that must be gerenated by just one moused > process. > > If you have in /etc/rc.conf: > moused_enable="YES" > usbd_enable="YES" > > You will have two moused processes and all sort of extrange behavior. > But it may works. > > Maybe your BIOS can make the usb and the trackpad 'mux'. In that case, > you must edit your /etc/usbd.conf and comment out the device 'mouse' > > You may also try and specific resume in /etc/rc.resume: > /usr/bin/killall moused > [ -c /dev/psm0 ] && /usr/sbin/moused -p /dev/psm0 \ > -I /var/run/moused.pid > [ -c /dev/ums0 ] && /usr/sbin/moused -p /dev/ums0 \ > -I /var/run/moused.ums0.pid > /usr/sbin/vidcontrol -m on > > See also the comments in /etc/rc.suspend, /etc/rc.resume about uhci. > You may need a kernel without usb to make this work. Also, load your > required usb modules from /etc/loader.conf > > > > > I figured out, that ums0 isn't the problem here, it just takes 2-3 > > seconds and it is there after resuming. I didn't know what device is > > carrying what mouse. So the problem is /dev/psm0. The trackpoint is > > dead after resuming, even though I entered a moused -p /dev/psm0 in > > /etc/rc.resume. This doesn't seem to be executed. Is that the correct > > place to set commands after resume? > > > > Jochen > > > > -- > josemi > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Just for the record -- in current you *can* run multiple moused processes on multiple hardware mice and they will happily coexist and provide source of events for /dev/sysmouse. For more information, please, read "Multiple Mice" section of `man moused`. --- Alexandre "Sunny" Kovalenko.