Re: The quest for rodent power
Vineet Kumar <firstname.lastname@example.org> writes:
> * Harry Putnam (email@example.com) [020305 00:29]:
>> /etc/gpm.conf is set to /dev/psaux. So the X mouse cannot be
>> .. right?
> Right. Also, as I've said before, adding a symlink in the mix can only
> confuse things further. Forget about a /dev/mouse symlink. Tell gpm to
> use /dev/psaux and tell X to use /dev/gpmdata. See the links below.
Not sure I see what confusion it causes but it does seem extraneous.
Are suggesting it is the problem here?
>> Here is the current situation in /dev
>> ls -l /dev |grep 'mouse\|psaux\|gpm'
>> prw-r--r-- 1 root root 0 Mar 4 23:56 gpmdata
>> lrwxrwxrwx 1 root root 7 Feb 28 21:41 mouse -> gpmdata
>> crw------- 1 root root 10, 1 Mar 4 23:45 psaux
>> crw-rw---- 1 root root 10, 32 Nov 4 14:52 usbmouse
>> How should it look by your technique?
> I explained this in an email a few weeks back with subject line "mouse
> freezes" back on Feb 13; check the archives. Actually, with a little
> googling, it seems I've explained this more than once already =)
> See these, please:
> (20020213210941.GC903@doorstop.net seems to be missing from
> groups.google.com, but it's quoted (albeit rather rudely) here:)
After reading thru those, it seems the setup I posted conforms to
You say "(Start by reading Joost's message regarding mouse hardware.)"
Joost says if the hardware connector is small and round it is PS/2.
Thats what I've used. Everyone seems to agree if it is ps2 /dev/psaux
should be the device:
My current (non-working) gpm.conf:
My current XF86Config (in part)
Option "Device" "/dev/gpmdata"
Option "Protocol" "PS/2"
Option "Emulate3Buttons" "true"
# Option "ZAxisMapping" "4 5" (This is now commented)
Two possible places where they might diverge.
1) I didn't rm /dev/mouse (The symlink)
But I don't think you are suggesting that is the main problem.
2) More important probably. You talk about both configs (gpm.conf and
XF86Config-4) Referencing the same mouse protocol but never really
say what that is. For example: The gpm.conf I posted says `raw'
for the repeat option and as you note in those posts is
alright. But you never say what the X config should say... only
that it should be the same. But don't think you mean `raw' in
the X config.
>From your post:Message-ID: <20010627135905.A10128@doorstop.net>
> Alternatively, you can specify any protocol you
> like in your gpm repeater config, as long as you tell X to use the
> same protocol. As someone else suggested, you can tell gpm to repeat
> as type 'raw' in which case you should configure X to use the actual
> protocol that your mouse is speaking.
By `actual protocol' you mean PS/2 .. right?
Can you say point blank what you see as wrong with the above? It
seems to conform to your outline. But, I've been staring at it too
long and probably missing some important difference.
The final piece of the puzzle:
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "gpm-mouse" "CorePointer"
# InputDevice "Generic Mouse"
Note Generic Mouse is commented out along with that entire section
from further up in the config. Like this:
## Section "InputDevice"
## Identifier "Generic Mouse"
## Driver "mouse"
## Option "SendCoreEvents" "true"
## Option "Device" "/dev/input/mice"
## Option "Protocol" "ImPS/2"
## Option "Emulate3Buttons" "true"
## Option "ZAxisMapping" "4 5"
With that setup, and in console mode running this command:
# /etc/init.d/gpm force-reload
Stopping mouse interface server: gpm.
Starting mouse interface server: gpm.
# ps wuax|grep gpm
Appears as if gpm is started but nothing shows in ps output and mouse
Mouse doesn't work in X with these settings either.
>> >> What does the ZAxisMapping thing mean?
> ZAxisMapping is used to tell X which buttons you want to use for your
Thanks, Note above its commented out now.