[Techtalk] Spastic Mouse After Using Virtual Console

Dom Incollingo dom_incollingo at linuxmail.org
Sat Jan 25 02:28:50 EST 2003


Hello,

I am using a PS/2 scroll mouse with SuSE 8.1.  The mouse works perfectly, except when I open a virtual console (ctrl-alt-F1, for example) and then return to my graphical session (ctrl-alt-F7). Upon return to my graphical session, the cursor does not work. Any cursor movement seems to be interpreted as clicks rather than pointer movement. Even if I don't try to move the mouse at all, programs start launching automatically, as if the mouse were clicking spastically on various icons.

If I toggle back through two or three virtual consoles (ctrl-alt-F1, ctrl-alt-F2, for example) and then return to the graphical session (ctrl-alt-F7), the mouse works normally again.

Here's what I've tried so far to resolve this problem:

- Checked /var/log/XFree86.0.log to verify that XWindows is using /etc/X11/XF86Config (shown at the end of this note)

- Verified that XF86Config contains the ServerFlag "AllowMouseOpenFail".

- Modified the mouse section of XF86Config to use device "/dev/mouse" rather than "/dev/psaux". No improvement.

- Added /usr/sbin/sysp -s mouse > /dev/null to /etc/init.d/boot.local. No improvement.

- Disabled 3D acceleration. No improvement.

- Checked /var/log/warn and /var/log/faillog to see if the problem was reported. Did not find any pertinent messages.

- Verified that gpm is not running by executing 'ps axw | grep gpm' in the shell. This command did not return any output.

- Tried starting gpm. No improvement. (Didn't think this would help, but thought it was worth a try.)

- Made the following change to /boot/grub/menu.lst as per the SuSE Support help:
  Changed the line:

   kernel (hd0,1)/boot/vmlinuz root=/dev/hda2  hdc=ide-scsi  vga=791

  to:

   kernel (hd0,1)/boot/vmlinuz root=/dev/hda2 acpi=off hdc=ide-scsi vga=791

    This did not help.

- Added the following line to /etc/X11/XF86Config as per the SuSE Support help:

     Option        "SW_cursor"

   below VendorName "NVidia" of the Section "Device".
    
   This change prevented the mouse from working at all, so I had to remove it.

- Searched newsgroups in google. This problem was reported before, but I did not find any solution.

Has anyone had this problem and found a way to resolve it?  Thanks very much for your help!

Dom


PS/2 scroll mouse (Mitsumi Model-ECM-S5002)

XF86Config excerpts:

 Section "ServerFlags"
   Option       "AllowMouseOpenFail"
 EndSection

 Section "InputDevice"
   Driver       "mouse"
   Identifier   "Mouse[1]"
   Option       "ButtonNumber" "3"
   Option       "Device" "/dev/mouse"
   Option       "Name" "Autodetection"
   Option       "Protocol" "imps/2"
   Option       "Vendor" "Sysp"
   Option       "ZAxisMapping" "4 5"
 EndSection

Section "Device"
  BoardName    "GeForce4 MX 420"
  BusID        "1:0:0"
  Driver       "nvidia"
  Identifier   "Device[0]"
  Screen       0
  Option       "Rotate" "off"
  VendorName   "NVidia"
EndSection

Section "ServerLayout"
  Identifier   "Layout[all]"
  InputDevice  "Keyboard[0]" "CoreKeyboard"
  InputDevice  "Mouse[1]" "CorePointer"
  Option       "Clone" "off"
  Option       "Xinerama" "off"
  Screen       "Screen[0]"
EndSection


Permissions:
  lrwxrwxrwx 1 root root 10 2003-01-12 06:56 /dev/mouse -> /dev/psaux
  crw-rw----    1 root   root   10,   1 2003-01-12 06:57 /dev/psaux


-- 
______________________________________________
http://www.linuxmail.org/
Now with e-mail forwarding for only US$5.95/yr

Powered by Outblaze



More information about the Techtalk mailing list