From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] xorg-server mouse and keyboard woes
Date: Fri, 10 Jul 2009 11:02:01 -0500 [thread overview]
Message-ID: <4A5765F9.7060408@gmail.com> (raw)
In-Reply-To: <tkrat.0a109561fab2fb0e@igpm.rwth-aachen.de>
Helmut Jarausch wrote:
> On 10 Jul, Dale wrote:
>
>
>> Same thing here. I just tried again to get hal, evdev and all his
>> "drive me crazy" friends to work, it doesn't. It appears to me that hal
>> will be disabled in package.use for xorg-server FOREVER. I'm sick of
>> messing with evdev. I'm waiting on something better to come along. I
>> bet someone does come up with something better too. This has been a
>> PITA since it came out.
>>
>
> Yes, I did have some problems with xorg + hal. But now it's working even
> better with hal than without (e.g. I had problems with using my mouse
> and my Wacom tablet simultaneously).
>
> Now I'm running xorg-server-1.6.2
>
> The following steps seem to be essential:
>
> emerge everything X-related with hal (I've put it into /etc/make.conf)
>
> Let hald start at boot time (very important)
> i.e. rc-update add hald boot
>
> Make a minimal xorg.conf (no drivers for any input device)
> the first lines being
>
> Section "ServerLayout"
> Identifier "Default"
> Screen 0 "Screen 0" 0 0
> # Option "AllowEmptyInput" "false"
> Option "AIGLX" "on"
> EndSection
>
> Section "ServerFlags"
> # Option "DontZap" "true"
> Option "AutoAddDevices" "on"
> Option "AutoEnableDevices" "on"
> Option "AllowEmptyInput" "on"
> EndSection
>
> Section "Extensions"
> Option "Composite" "On"
> EndSection
> .......
>
> In /etc/make.conf (here)
> INPUT_DEVICES="keyboard mouse evdev wacom"
>
> add the file /etc/hal/fdi/policy/x11-input.fdi
>
> here:
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <deviceinfo version="0.2">
> <device>
> <match key="info.capabilities" contains="input.keyboard">
> <append key="info.callouts.add" type="strlist">hal-setup-keymap</append>
> <merge key="input.x11_options.XkbModel" type="string">microsoft</merge>
> <merge key="input.x11_options.XkbRules" type="string">xorg</merge>
> <merge key="input.x11_options.XkbLayout" type="string">en_US</merge>
> <merge key="input.xkb.layout" type="string">en_US</merge>
> <merge key="input.xkb.model" type="string">microsoft</merge>
> <merge key="input.xkb.rules" type="string">xorg</merge>
> </match>
>
> <match key="info.capabilities" contains="input.mouse">
> <merge key="input.x11_driver" type="string">evdev</merge>
> <merge key="input.x11_options.WHEELRelativeAxisButtons" type="string">7 6</merge>
> <merge key="input.x11_options.HWHEELRelativeAxisButtons" type="string">5 4</merge>
> <merge key="input.x11_options.Buttons" type="int">8</merge>
> <merge key="input.x11_options.ZAxisMapping" type="string">4 5</merge>
> <merge key="input.x11_options.Sensitivity" type="int">30</merge>
> <merge key="input.x11_options.CorePointer" type="string">true</merge>
> </match>
>
> </device>
> </deviceinfo>
>
> Very import when upgrading to 1.6.*
> re-emerge everything that is installed from x11-drivers/*
>
> Now, you should have the best X11 ever (note, I'm using the
> bleeding-edge stuff (unstable isn't the wright word)
> i.e. I have
> ACCEPT_KEYWORDS="~amd64" (or ~x86 on a 32 bits machine)
>
> Helmut.
>
>
>
>
I printed this but I'm not sure I want to even try this mess again. I'm
to the point that until what I have doesn't work anymore, I'm sticking
with what does. This has left a bad taste in my mouth. Tasted like a
skunk that died about 4 days ago, in the hot sun I might add. Yep, it
is ripe.
Dale
:-) :-)
next prev parent reply other threads:[~2009-07-10 16:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 3:03 [gentoo-user] xorg-server mouse and keyboard woes Kevin O'Gorman
2009-07-10 3:18 ` [gentoo-user] " James
2009-07-10 3:51 ` Dale
2009-07-10 4:52 ` Kevin O'Gorman
2009-07-10 5:02 ` Dale
2009-07-10 5:40 ` Kevin O'Gorman
2009-07-10 5:33 ` Kevin O'Gorman
2009-07-10 5:52 ` Dale
2009-07-10 7:34 ` Robin Atwood
2009-07-10 11:55 ` Philip Webb
2009-07-10 15:43 ` Kevin O'Gorman
2009-07-10 15:58 ` Dale
2009-07-10 17:46 ` Alan McKinnon
2009-07-10 18:47 ` Dale
2009-07-11 6:04 ` Keith Dart
2009-07-11 6:40 ` Dale
2009-07-10 8:18 ` [gentoo-user] " Keith Dart
2009-07-10 8:24 ` Keith Dart
2009-07-10 10:07 ` Kevin O'Gorman
2009-07-10 10:10 ` Kevin O'Gorman
2009-07-10 13:19 ` Dale
2009-07-10 14:22 ` Paul Hartman
2009-07-10 14:32 ` Helmut Jarausch
2009-07-10 16:02 ` Dale [this message]
2009-07-10 16:03 ` Kevin O'Gorman
2009-07-10 8:29 ` Helmut Jarausch
2009-07-10 18:50 ` [gentoo-user] " walt
2009-07-10 19:07 ` David
2009-07-11 3:53 ` Kevin O'Gorman
2009-07-11 5:46 ` Keith Dart
2009-07-12 5:03 ` Kevin O'Gorman
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=4A5765F9.7060408@gmail.com \
--to=rdalek1967@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