mouse problems....
Gary Kline
kline at thought.org
Mon Oct 11 21:57:43 UTC 2010
On Mon, Oct 11, 2010 at 11:13:20PM +0200, Polytropon wrote:
> On Mon, 11 Oct 2010 13:56:10 -0700, Gary Kline <kline at thought.org> wrote:
> > i tried this remove on _this_ console; then buttoned over to
> > `ethic' [server], killed the moused that was running. Indeed it
> > was /dev/ums0! But the mouse was frozen, and afer I killed it,
> > gone.
>
> It seems that disconnect / reconnect (performed by the KVM switch)
> causes some problems.
>
>
>
> > Then I tried your line and got the data stream. But
> > there was no mouse. ...
>
> But if you moved the mouse, status messages appeared? Remove the
> -d option and try
>
> # moused -f -p /dev/ums0 -t auto
>
> Now a mouse cursor should be present in text mode.
>
>
>
> > There are two buttons and the mouse "wheel"; I have no clue what's
> > next.
>
> I'm using such mice (with wheel) since FreeBSD 5.0, so there should
> be sufficient support if the mouse it not "broken by design".
>
>
>
> > Clearly, my 7.2.X sees the mouse. But when I typed simply
> >
> > # startx
> >
> > the windows are there; the mouse cursor hangs, dead-center.
>
> If you've tried the moused example above - and it WORKS, remove
> the -f option.
>
> # moused -p /dev/ums0 -t auto
>
> It should then become a daemon. Right after that, run
>
> # startx
>
> and X should use the mouse access provided by moused - unless, of
> course, there's HAL and DBUS trouble ahead.
>
>
>
> > Dunno; I do have hal and dbus there; that's about all I
> > can say. Do I check with ps -ax | egrep "hal|dbus"?
>
> If it was THAT obvious... :-)
>
> Check
>
> # grep "hal" /etc/rc.conf
> # grep "dbus" /etc/rc.conf
>
> to see if they are enabled. You should also have hal-x.y.z and
> dbus-x.y.z packages installed. If you installed X from package or used
> the port with default options, it relies on their presence. That's
> nothing bad per se, especially if you're using KDE, Gnome or Xfce,
> those seem to run better with HAL and DBUS, especially all the
> autodetection and automount stuff. If you intendedly do NOT want
> to use that, you can code AAD in your xorg.conf (you need to have
> one for that).
>
> There's a section in the handbook covering that topic:
>
> 5.4 X11 Configuration
> http://www.freebsd.org/doc/handbook/x-config.html
>
> Especially see 5.4.2. Also don't miss
>
> http://www.wonkity.com/~wblock/docs/html/aei.html
>
> And maybe
>
> http://www.kite.ping.de/xorg-hal-migration.html
>
> This should give sufficient information to find out what is the best
> solution for your setting.
>
I thank you sincerely. I will try one last thing before I
abandon my post: namely, to try a hard reset of the KVM switch.
If nothing, then it is over my head. I'll vheck the site
mentioned, who knows?
gary
PS: to the list: if this has happened to anyone else onlist, i
would like to hear about it. I bought a Belkin circa '05 and
it worked flalessly gor years ... until something burned out!
>
>
> --
> Polytropon
> Magdeburg, Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe, Mousa, ...
--
Gary Kline kline at thought.org http://www.thought.org Public Service Unix
The 7.90a release of Jottings: http://jottings.thought.org/index.php
http://journey.thought.org
More information about the freebsd-questions
mailing list