Date: Wed, 13 Oct 2010 05:59:06 +0200 From: Polytropon <freebsd@edvax.de> To: Gary Kline <kline@thought.org> Cc: Mailing List <freebsd-stable@freebsd.org>, FreeBSD Mailing List <freebsd-questions@freebsd.org>, FreeBSD Subject: Re: mouse problems.... Message-ID: <20101013055906.bdc5f644.freebsd@edvax.de> In-Reply-To: <20101013032018.GA3163@thought.org> References: <20101011032642.GA3354@thought.org> <20101011164152.GA4652@thought.org> <20101011193153.758efde5.freebsd@edvax.de> <4CB411AF.5050109@qeng-ho.org> <20101012221020.1a8dcd90.freebsd@edvax.de> <20101012233002.GA4957@thought.org> <20101013014326.6630e3b5.freebsd@edvax.de> <20101013032018.GA3163@thought.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 12 Oct 2010 20:20:18 -0700, Gary Kline <kline@thought.org> wrote: > I just looked at the handbook "2.10.10 Mouse Settings" I am > running 7.2 on the server, not that old, but the text does not > match what I see on my sysinstall screen. > > // cut and paste > > > This option will allow you to cut and paste text in the console and > user programs with a 3-button mouse. If using a 2-button mouse, > refer to manual page, moused(8), after installation for details on > emulating the 3-button style. This example depicts a non-USB mouse > configuration (such as a PS/2 or COM port mouse): > > User Confirmation Requested > Does this system have a PS/2, serial, or bus mouse? > > [ Yes ] No > > Select [ Yes ] for a PS/2, serial or bus mouse, or [ No ] for a USB > mouse and press Enter. > > Figure 2-42. Select Mouse Protocol Type > > [[ GRAPHIC ]] > > I mouse down to the Post-install section of the sysinstall menu. > I do not see anything like the > > "User Confirmation Requested, [[etc]]" > > that lets me select Yes or No. *This may be what has been > causing the trouble. What I _do_ see is just the graph that > begins, "You can cut and paste text... ." etc. Nowhere do I > see an option to select the USB protocol; it is only the PS/2 > stuff. ..... USB mice get autodetected and autoactivated (by the USB subsystem), so there is no need to configure them. Currently I have no such setting in /etc/rc.conf, and mouse works. I think you should look at "Configuring X" rather than the system's mouse setting, as X seems to work independently. There's a section about that in the handbook. http://www.freebsd.org/doc/handbook/x-config.html > > > The kernel is set for PS/2 mice and evidently sticks them on > > > /dev/sysmouse. > > > > Yes - if one is present. At least X can be set to use sysmouse as > > pointer device, but it is not a symlink to either a USB or PS/2 > > mouse. Currently, I'm using a Sun USB mouse, and there is > > > > crw------- 1 root wheel 0, 10 Oct 13 01:31 /dev/sysmouse > > > > as well as > > > > crw-r--r-- 1 root operator 0, 122 Oct 13 01:31 /dev/ums0 > > > > If this does survive a KVM switch-over, all is fine. > > > Yup:: > > p0 19:51 Server <ethic> [5002] ll sysmouse > 0 crw------- 1 root wheel 0, 11 Oct 12 17:12 sysmouse > > and, > > 0 crw-r--r-- 1 root operator 0, 44 Oct 12 17:12 ums0 > > > So, both devices are there. Just that when I set the mouse to > the latter, /dev/ums0, the kernel sees it always as busy. A > poster to our -stable lists thought it might be hald bug, so I > commented out that in /etc/rc.conf. BZZZT. It's back:) Correct. If you disable HAL, and your X is configured to run *WITH* HAL, it won't run anymore. Edit /etc/X11/xorg.conf (and if not present, create it) to make X work *WITHOUT* HAL. How it is to be done is described here: http://www.wonkity.com/~wblock/docs/html/aei.html You can only have ONE of the following settings, as far as I understood the current state of X: a) X with HAL and DBUS, no xorg.conf b) X with HAL and DBUS, with xorg.conf c) X without HAL and DBUS, with xorg.conf So your way would be now to (1st) disable HAL and DBUS from the system and then (2nd) configure X not to require them. Another (maybe 3rd) option is to recompile X without HAL and DBUS require- ments. > Will you please check out this posting: > > http://osdir.com/ml/freebsd.bugs/2002-03/msg00032.html > > The way that the mose config worked as to turn off the > moused_enable, to moused_enable="NO". Didn't seem to do > anything... Yes, sounds familiar... It is to be interpreted as follows: If you use a USB mouse, set moused_enable="NO", as the USB subsystem will call moused with the correct settings automatically. If you use a PS/2 or serial mouse, set moused_enable="YES" and also set the needed options like _port and _type, and maybe _flags, so moused can take care of the mouse. The USB system is not involved here. I really think you should concentrate on configuring X's mouse handling, as the system's seems to work in a correct manner. Suggested TODO: 1. Disable HAL and DBUS per rc.conf 2. Create xorg.conf # X -configure # cp /root/xorg.conf.new /etc/X11/xorg.conf 3. Enter AutoAddDevices setting to xorg.conf as described http://www.wonkity.com/~wblock/docs/html/aei.html 4. ??? 5. Profit! :-) Oh, and don't forget to reboot. Medieval times... :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101013055906.bdc5f644.freebsd>