Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 17 Mar 2013 15:24:42 -0700 (PDT)
From:      Don Lewis <truckman@FreeBSD.org>
To:        andrnils@gmail.com
Cc:        darius@dons.net.au, freebsd-stable@FreeBSD.org, fullermd@over-yonder.net
Subject:   =?iso-2022-jp?Q?Re:_What_is_the_Right_Way(=1B$(D"o=1B(B)_to_run?= X?
Message-ID:  <201303172224.r2HMOg25013615@gw.catspoiler.org>
In-Reply-To: <CAPS9%2BSsjwy%2B8CojdAY0dLfkFpLv%2Bbyz9d0YYT-GWKHhWP-u=fA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 17 Mar, Andreas Nilsson wrote:
> On Sun, Mar 17, 2013 at 1:58 PM, Daniel O'Connor <darius@dons.net.au> wrote:
> 
>>
>> On 17/03/2013, at 23:08, "Matthew D. Fuller" <fullermd@over-yonder.net>
>> wrote:
>> > However, some time back, X _did_ start being all stupid about finding
>> > the mouse for me.  Un/re-plugging it (USB) after starting X made it
>> > show up working, but that's annoying and stupid (and not an option on
>> > other systems with e.g. PS/2 meece).  I wound up sticking the "other
>> > half" of that oft-cargo-culted incantation:
>> >
>> > Section "ServerFlags"
>> >    Option "AutoAddDevices" "off"
>> > EndSection
>> >
>> > in my config, and it's worked OK since.  's probably worth a try...
>>
>>
>> Yeah, that does work too. It's just annoying it's necessary :)
>>
> 
> Sure is. One thing that also comes to mind is moused. Do you have it
> running? I seem to remember having weird troubles when moused wasn't
> running.

I ran into this problem a while back.  The problem turned out to be that
moused was exclusively opening /dev/psm0 before hald so that hald was
unable open it.  This happened first on my laptop, and I just disabled
moused and everything seemed to work except that the trackpad no longer
worked in console mode.  I tried the same thing later when my primary
desktop broke and it sort of worked.  The problem that I ran into was
that Xorg would occasionally wedge and spam its log with messages about
problems with detecting the mouse protocol.  Even worse, I found that my
KVM switch would very reliably trigger this problem.  After much hair
pulling, I eventually re-enabled moused and added this to xorg.conf:
	Option          "AllowEmptyInput" "Off"
so that it would obey this mouse configuration section:
Section "InputDevice"
        Identifier  "Mouse0"
        Driver      "mouse"
        Option      "Protocol" "auto"
        Option      "Device" "/dev/sysmouse"
        Option      "ZAxisMapping" "4 5 6 7"
EndSection

I don't recall if I disabled hald and changed xorg.conf to point to
/dev/psm0 before I re-enabled moused.  I do know that hald is currently
disabled and nothing obvious seems to be broken in Gnome.

I haven't had any issues with AllowEmptyInput so I never bothered to
switch over to the preferred AutoAddDevices.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201303172224.r2HMOg25013615>