there are hundreds of postings on the web about this problematic type
of mouse; many conclude that it only works in a USB port; others
insist you can't have gpm and xconfig both controlling the mouse at
the same time;

i recently unplugged mine from a USB port [WHERE IT WORKED FINE] and
stuck it into a KVM switch [PS/2]; i got it to work, on the console
and in X, but not until i had followed several futile recipes; would
it be instructive, for all us newbies, if some of you seasoned hackers
commented on problems lurking here?

FINAL /etc/conf.d/gpm

#MOUSE=ps2
MOUSE=imps2
MOUSEDEV=/dev/psaux
#MOUSEDEV=/dev/input/mice
#RESPONSIVENESS=
REPEAT_TYPE=raw
#APPEND="-g 1 -A 60"
----------------------------------------------

FINAL /etc/X11/XF86Config

Section "InputDevice"
        Identifier      "ExplorerMouse"
        Driver          "mouse"
        Option          "Protocol"      "imps/2"
        Option          "Device"        "/dev/psaux"
        Option          "ZAxisMapping"  "4 5"
        Option          "Buttons"       "5"
EndSection
-----------------snip-----------------
Section "ServerLayout"
        Identifier      "Simple Layout"
        Screen          "Screen 1"
        InputDevice     "ExplorerMouse" "CorePointer"
        InputDevice     "Keyboard1"     "CoreKeyboard"
EndSection
------------------------------------------

HISTORY: attempts to adjust /etc/X11/XF86Config [i.e. reset "Device"
and "Protocol"]

[starting with gpm set to: /dev/psaux, ps/2]:

1. /dev/psaux and Auto: LOADS X, BUT MOUSE POINTER IMMOBILE; SO,
DRIVER OK? ID WRONG?

2. /dev/psaux and MouseManPlusPS/2: MOUSE ALIVE IN X, BUT NO WHEEL;

3. /dev/psaux and imps/2: ALL SET FOR X [WHEEL O.K.], BUT CONSOLE A
MESS; [i.e. X and gpm "fighting for control?"]

4. /dev/psaux and ps/2: LOADS X, BUT MOUSE A MESS both IN X and IN
CONSOLE; SO revert to /dev/psaux and MouseManPlusPS/2, then REBOOT
[WHICH RESTORES GPM'S CONTROL IN CONSOLE],

5. /dev/mouse and imps/2 
[NB /etc/conf.d/gpm HAS /dev/psaux]: 
ALL OK FOR X, CONSOLE A MESS; SO IMPS/2 IS GREAT FOR X BUT BAD FOR
CONSOLE?

6. SO, GO BACK TO /dev/psaux and MouseManPlusPS/2; 
NB gpm was stopped and restarted but mouse still f*'d in terminal; SO
REBOOT AND TRY:
gpm -t /dev/psaux -m imps/2 
["uses gpm on console and leaves x to use its own driver
("mousemanplus") I HAD TO RECONFIG GPM MANUALLY]; 
and then psaux and mm+ for xconfig: 
RESULT: NO WHEEL IN WINDOWS, CONSOLE OK; JUST LIKE psaux ps/2 in gpm,
and psaux and mm+ in xconf;

7. GPM: psaux, imps/2, raw; XCONF: imps/2, /dev/gpmdata 
("don't let gpm and X fight over /dev/psaux -- that will be erratic,
let gpm get the raw device and then feed it to X via a "fifo" (aka
"named pipe" or "unix domain socket"): 
RESULT: CONSOLE OK; X WON'T LOAD: (EE) xf86OpenSerial: Cannot open
device /dev/gpmdata No such file or directory.  (EE) ExplorerMouse:
cannot open input device (EE) PreInit failed for input device
"ExplorerMouse" No core pointer

8. gpm: psaux, imps2, raw; xconf: psaux, imps2: AND ALL'S WELL

[ALSO suggested:
options "BaudRate" "9600", "SampleRate" "150", "Resolution" "800"


--
[EMAIL PROTECTED] mailing list

Reply via email to