Date: Sun, 17 Mar 2013 07:38:08 -0500 From: "Matthew D. Fuller" <fullermd@over-yonder.net> To: Daniel O'Connor <darius@dons.net.au> Cc: "freebsd-stable@freebsd.org stable" <freebsd-stable@freebsd.org> Subject: Re: What is the Right =?utf-8?Q?Way=28?= =?utf-8?B?4oSiKQ==?= to run X? Message-ID: <20130317123808.GH53758@over-yonder.net> In-Reply-To: <82EEB5DC-DD57-4EC3-936A-2F28C4BAF0B4@dons.net.au> References: <82EEB5DC-DD57-4EC3-936A-2F28C4BAF0B4@dons.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Mar 17, 2013 at 10:37:08PM +1030 I heard the voice of
Daniel O'Connor, and lo! it spake thus:
> Hi,
> I recently updated my 9.1-PRE system's ports and my previous X
> config now results in no mouse (but the keyboard does work).
>
> I found that I needed to add the following..
> Section "ServerFlags"
> Option "AllowEmptyInput" "False"
> EndSection
I think general wisdom is that AEI is a Bad Idea for various reasons
that I don't remember, but seemed reasonable when I read them.
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...
--
Matthew Fuller (MF4839) | fullermd@over-yonder.net
Systems/Network Administrator | http://www.over-yonder.net/~fullermd/
On the Internet, nobody can hear you scream.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130317123808.GH53758>