On Mon, Mar 04, 2002 at 07:03:14AM -0800, Harry Putnam wrote: > Running woody (testing) > > I've been ignoring this issue and working on other things but I really > miss having my little rodent in text mode. > > Its a logitec 3 button ps2, critter that works in X just fine. > > I can't remember how to tell with no doubt where the mouse is > connected. At which device. I remember saying /dev/psaux during install > but that was just a guess. > > Boot messages indicate gpm services are being started. But I have no > functioning mouse in text mode. > > A grep of ps waux shows" > ps waux|grep 'gpm' turns up nothing
Odd. Perhaps there is a bug (gasp!) in gpm?
To get more diagnostic info, try these after *stopping* your X server
(switching to a text-mode VT ain't enough):
# /etc/init.d/gpm stop
# /etc/init.d/gpm start
and keep an eye on what gets added /var/log/syslog.
Posting /etc/gpm.conf will probably help too.
But since the mouse works in X, I assume that that X reads from
/dev/psaux.
Since only one process can read from /dev/psaux at a time (unless you
patch the kernel), this implies that if you get gpm running, then the
mouse won't work in X (with your current config).
> The devices directory itself shows
> ls -l /dev/ |grep 'mouse\|psaux\|gpm'
>
> prw-r--r-- 1 root root 0 Mar 1 15:26 gpmdata
> lrwxrwxrwx 1 root root 7 Feb 28 21:41 mouse -> gpmdata
> crw------- 1 root root 10, 1 Nov 4 14:52 psaux
> crw-rw---- 1 root root 10, 32 Nov 4 14:52 usbmouse
Looks OK.
> >From posts here, I got the idea that the XF86Config mouse section is
> related to text mode mouse settings in some way.
Sort of. -ish. XF86Config is the configuration for the X server, and
doesn't care about text mode at all. It simply doesn't know.
gpm doesn't know about X, but knows all about text mode. It does
allow "repeating" the mouse movements onto /dev/gpmdata, thus allowing
other applications use /dev/gpmdata as the mouse.
> That section of mine [kj: XF86Config] looks like this:
>
> Section "InputDevice"
> Identifier "Configured Mouse"
> Driver "mouse"
> Option "CorePointer"
> Option "Device" "/dev/psaux"
> Option "Protocol" "PS/2"
> Option "Emulate3Buttons" "true"
> Option "ZAxisMapping" "4 5"
> EndSection
>
> 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"
> EndSection
>
> How can I tell beyond doubt which device the mouse is on. And get this
> thing configured and working.
Which one of the input devices above gets used is specified by the
"ServerLayout" section (probably further down the file). It may actually
use both. The /dev/psaux mouse is a PS/2 connection, whereas
/dev/input/mice is the USB mouse(/mice).
A "good" config (i.e. one that worked for me, YMMV) would be (only
relevant fragments shown):
/etc/gpm.conf:
device=/dev/psaux
repeat_type=raw
/etc/X11/XF86Config-4
Section "InputDevice"
Identifier "gpm-mouse" # human-readable ID
Driver "mouse"
Option "Device" "/dev/gpmdata"
Option "Protocol" "PS/2"
# Add other options according to personal taste...
EndSection
Section "ServerLayout"
...
InputDevice "gpm-mouse" "CorePointer"
...
EndSection
I.e. stop X from reading from /dev/psaux, and tell it to read from
/dev/gpmdata instead (use the same protocol & options as those that work
for you now, no need to change them).
Since you had a 3-button mouse, you may want to tell gpm (and X about
it) to make the middle mouse button work. Hopefully somebody else can
help with that.
HTH
--
Karl E. Jørgensen
[EMAIL PROTECTED]
www.karl.jorgensen.com
==== Today's fortune:
For God's sake, stop researching for a while and begin to think!
pgpBdi3TOZSJl.pgp
Description: PGP signature
