mouse problems....

Polytropon freebsd at edvax.de
Tue Oct 12 20:10:23 UTC 2010


On Tue, 12 Oct 2010 08:43:43 +0100, Arthur Chance <freebsd at qeng-ho.org> wrote:
> On 10/11/10 18:31, Polytropon wrote:
> [snip]
> > The psm device can be configured per /etc/rc.conf using moused.
> > While USB mice get configured by the USB subsystem automatically,
> > PS/2 and serial mice do not.
> >
> > Here's an example entry:
> >
> > 	moused_enable="YES"
> > 	moused_port="/dev/psm0"
> > 	moused_flags="-z 4"
> > 	moused_type="auto"
> 
> I'm not sure that bit about PS/2 mice not being configured automatically 
> is true.

PS/2 mice usually GET configured automatically, so type=auto is
sufficient in MOST cases. In my case (where I took those lines
from) I had to specify additional flags to make sure some specific
functionality of THAT mouse runs properly.



> I run 8.1-RELEASE-p1 on amd64 with a PS/2 mouse and my 
> /etc/rc.conf contains
> 
> moused_enable="NO"
> moused_nondefault_enable="NO"
> moused_type="NO"
> 
> and X has no problem seeing the mouse. OK, I don't have a mouse in 
> console mode, but that's a personal foible of mine.

As I mentioned in another message, X should pick up the mouse
INDEPENDENTLY from the system (moused), and if my memory serves
me, this works both in combination with HAL + DBUS, but should
work also without them.

The idea of trying to get a mouse pointer in console mode is a
means of diagnostics, where "choose lowest level to check" is
often the best idea. The fewer components are involved, and
the better you can CONTROL those components, the easier it is
to check if something works.




-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...


More information about the freebsd-questions mailing list