From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: disable syanptics pad
Date: Sat, 23 May 2009 09:55:10 +0100 [thread overview]
Message-ID: <200905230955.21185.michaelkintzios@gmail.com> (raw)
In-Reply-To: <loom.20090522T144633-332@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1837 bytes --]
On Friday 22 May 2009, james wrote:
> Paul Hartman <paul.hartman+gentoo <at> gmail.com> writes:
> > I think you need to set corepointer=0 in the FDI file or something
> > similar to that. Or if you're using xorg.conf point it to a specific
> > mouse instead of /dev/mice or whatever the catch-all mouse device is.
> > May be able to get rid of it "even more" with udev rules or something
> > to just make it go away. Sorry I don't have specific examples, I'm on
> > a windows machine right now.
>
> I'm sure your information is good. But, I need specifics....
This is from my /etc/hal/fdi/policy/10-xinput-configuration.fdi:
=================================================
<!-- touchpad -->
<device>
<match key="info.capabilities" contains="input.touchpad">
<match key="info.product" contains="SynPS/2">
<merge key="input.x11_driver" type="string">synaptics</merge>
<merge key="input.x11_options.SHMConfig" type="string">true</merge>
<merge key="input.x11_options.VertEdgeScroll"
type="string">true</merge>
<merge key="input.x11_options.HorizEdgeScroll"
type="string">true</merge>
<merge key="input.x11_options.TapButton1" type="string">1</merge>
<merge key="input.x11_options.ClickButton1" type="string">1</merge>
</match>
</match>
</device>
=================================================
Try modifying the above with something like:
<merge key="input.x11_options.corepointer" type="string">0</merge>
You may want to try my fdi as is first. It may just work without problems in
your setup and the touchpad will become useful again.
Note: This is on a system which does not use xorg.conf anymore. I am not sure
how things get parsed by xorg when both an fdi and a xorg.conf are present.
HTH.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-05-23 8:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 18:00 [gentoo-user] disable syanptics pad James
2009-05-21 18:39 ` Paul Hartman
2009-05-22 14:47 ` [gentoo-user] " james
2009-05-23 8:55 ` Mick [this message]
2009-06-04 13:33 ` James
2009-05-21 19:13 ` [gentoo-user] " Uwe
2009-05-22 14:49 ` [gentoo-user] " James
2009-05-22 4:57 ` [gentoo-user] " Saphirus Sage
2009-05-22 15:06 ` [gentoo-user] " James
2009-05-22 18:22 ` James Ausmus
2009-06-04 13:29 ` James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200905230955.21185.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox