I have just gone through a java install.
Don't know it that is the cause or just someother freeky thing.
My mouse is in total run-away mode.
Just touch it and it goes all over the place. Things start dropping and draging. The system bar is on the top now and the action bar on the side.
If I manage to get a terminal window open and leave the mouse alone, I can type.
Also <alt-cnlt-F1> gets me to display 1.
If I go back to display 0, everything is still hosed.
Any pointers? Some mouse file out of align and too sensitive? How I fix this and reset things?
HELPPPPPPP
On Tue, 2006-02-21 at 12:54 -0500, Robert Moskowitz wrote:
I have just gone through a java install.
Don't know it that is the cause or just someother freeky thing.
My mouse is in total run-away mode.
Just touch it and it goes all over the place. Things start dropping and draging. The system bar is on the top now and the action bar on the side.
If I manage to get a terminal window open and leave the mouse alone, I can type.
Also <alt-cnlt-F1> gets me to display 1.
If I go back to display 0, everything is still hosed.
Any pointers? Some mouse file out of align and too sensitive? How I fix this and reset things?
HELPPPPPPP
What type of KVM switch are you using?
At 01:24 PM 2/21/2006, Scot L. Harris wrote:
On Tue, 2006-02-21 at 12:54 -0500, Robert Moskowitz wrote:
I have just gone through a java install.
Don't know it that is the cause or just someother freeky thing.
My mouse is in total run-away mode.
Just touch it and it goes all over the place. Things start dropping and draging. The system bar is on the top now and the action
bar on the side.
If I manage to get a terminal window open and leave the mouse alone, I can type.
Also <alt-cnlt-F1> gets me to display 1.
If I go back to display 0, everything is still hosed.
Any pointers? Some mouse file out of align and too sensitive? How I fix this and reset things?
HELPPPPPPP
What type of KVM switch are you using?
They are some old Master views.
Use to have an old wheel mouse that did not work.
That is what was present when I build all of these systems.
Now I have a nice Logitech wireless kyb/mouse plugged into the KVM. The use wheel is working on my Win32 systems and on 2 other Centos builds.
Now in my /etc/X11/xorg.conf the Input Device protocol is "IMPS/2"
A friend had me try "PS/2" and things SEEMed a little bit better. Then "auto" and now it seems to be the same as before.
But wait. When the system booked, I was switched to another system. When I boot and leave that system as the 'active' one, I get a similar action as to when it was "PS/2".
I did an Alt-D while it was starting so I could see the startup messages and I see that that mouse console services started 'OK'.
Thing is it was fine before, and now not. And the other systems are fine...
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Tue, 2006-02-21 at 13:55 -0500, Robert Moskowitz wrote:
Just touch it and it goes all over the place. Things start dropping and draging. The system bar is on the top now and the action
bar on the side.
If I manage to get a terminal window open and leave the mouse alone, I can type.
Also <alt-cnlt-F1> gets me to display 1.
If I go back to display 0, everything is still hosed.
Any pointers? Some mouse file out of align and too sensitive? How I fix this and reset things?
I haven't followed this thread closely, so sorry if this has already been suggested. On my KVM at work, if I switch over to a windows computer and then back to my linux box my mouse goes crazy (I don't know why, but its common to our Belkin KVM's). If I unplug and replug my mouse, everything works fine after then. Does this work for you?
--Bill
On Tue, 2006-02-21 at 14:29 -0500, William (Bill) E. T. wrote:
On Tue, 2006-02-21 at 13:55 -0500, Robert Moskowitz wrote:
Just touch it and it goes all over the place. Things start dropping and draging. The system bar is on the top now and the action
bar on the side.
If I manage to get a terminal window open and leave the mouse alone, I can type.
Also <alt-cnlt-F1> gets me to display 1.
If I go back to display 0, everything is still hosed.
Any pointers? Some mouse file out of align and too sensitive? How I fix this and reset things?
I haven't followed this thread closely, so sorry if this has already been suggested. On my KVM at work, if I switch over to a windows computer and then back to my linux box my mouse goes crazy (I don't know why, but its common to our Belkin KVM's). If I unplug and replug my mouse, everything works fine after then. Does this work for you?
---- the well known belkin kvm switch fix...
psmouse.proto=bare
tack that onto the end of your 'kernel' line in /boot/grub/grub.conf
--- you will lose the 'mouse wheel' on the top but it won't go crazy
Craig
At 02:40 PM 2/21/2006, Craig White wrote:
On Tue, 2006-02-21 at 14:29 -0500, William (Bill) E. T. wrote:
On Tue, 2006-02-21 at 13:55 -0500, Robert Moskowitz wrote:
Just touch it and it goes all over the place. Things start dropping and draging. The system bar is on the top now and the action
bar on the side.
If I manage to get a terminal window open and leave the mouse alone, I can type.
Also <alt-cnlt-F1> gets me to display 1.
If I go back to display 0, everything is still hosed.
Any pointers? Some mouse file out of align and too sensitive? How I fix this and reset things?
I haven't followed this thread closely, so sorry if this has already been suggested. On my KVM at work, if I switch over to a windows computer and then back to my linux box my mouse goes crazy (I don't know why, but its common to our Belkin KVM's). If I unplug and replug my mouse, everything works fine after then. Does this work for you?
the well known belkin kvm switch fix...
psmouse.proto=bare
tack that onto the end of your 'kernel' line in /boot/grub/grub.conf
--- you will lose the 'mouse wheel' on the top but it won't go crazy
To the end of /boot/grub/grub.conf I added the line:
psmouse.proto=imps
then I tried bare
neither made a difference.
I am running at init 3 now, the after logging in, typing init 5 to bring up X
To the end of /boot/grub/grub.conf I added the line:
psmouse.proto=imps
Well the psmouse.proto=imps needs to be added to one of the kernel command lines in grub.conf, not on a line by itself.
I use a msi wireless keyboard and mouse on a kvm and the only time I see erratic mouse behaviour is when the batteries have gotten low and I put in a full charged set.
John
-- Registered Linux User 263680, get counted at http://counter.li.org
At 02:40 PM 2/21/2006, Craig White wrote:
On Tue, 2006-02-21 at 14:29 -0500, William (Bill) E. T. wrote:
On Tue, 2006-02-21 at 13:55 -0500, Robert Moskowitz wrote:
Just touch it and it goes all over the place. Things start dropping and draging. The system bar is on the top now and the action
bar on the side.
If I manage to get a terminal window open and leave the mouse alone, I can type.
Also <alt-cnlt-F1> gets me to display 1.
If I go back to display 0, everything is still hosed.
Any pointers? Some mouse file out of align and too sensitive? How I fix this and reset things?
I haven't followed this thread closely, so sorry if this has already been suggested. On my KVM at work, if I switch over to a windows computer and then back to my linux box my mouse goes crazy (I don't know why, but its common to our Belkin KVM's). If I unplug and replug my mouse, everything works fine after then. Does this work for you?
the well known belkin kvm switch fix...
psmouse.proto=bare
tack that onto the end of your 'kernel' line in /boot/grub/grub.conf
--- you will lose the 'mouse wheel' on the top but it won't go crazy
As I said, I am running Init 3.
It seems that this comes in at Display 1 ( alt-cntl-F1 ) and when I do an Init 5, that goes to display 0 ( alt-cntl-F7) I see this as I switch between the two,.
The reason I point this out is that if I move the mouse now while I am in Display 1 I get the error to the console:
psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
Or it might be 2 or 1 byte.
Does this help at all????
On 2/21/06, Robert Moskowitz rgm@htt-consult.com wrote:
Now I have a nice Logitech wireless kyb/mouse plugged into the KVM. The use wheel is working on my Win32 systems and on 2 other Centos builds.
Now in my /etc/X11/xorg.conf the Input Device protocol is "IMPS/2"
I think this is an Xorg bug. I have a similar problem with the mouse with a Ubuntu install that I was experimenting with. The same hardware works fine with an older linux dist that has XFree86.
I suspect that the problem is that Xorg has abandoned support for some older hardware, but the system isn't *that* old (originally purchased around 2001, I think).
On Tue, 2006-02-21 at 13:55 -0500, Robert Moskowitz wrote:
They are some old Master views.
Use to have an old wheel mouse that did not work.
That is what was present when I build all of these systems.
Now I have a nice Logitech wireless kyb/mouse plugged into the KVM. The use wheel is working on my Win32 systems and on 2 other Centos builds.
Now in my /etc/X11/xorg.conf the Input Device protocol is "IMPS/2"
A friend had me try "PS/2" and things SEEMed a little bit better. Then "auto" and now it seems to be the same as before.
But wait. When the system booked, I was switched to another system. When I boot and leave that system as the 'active' one, I get a similar action as to when it was "PS/2".
I did an Alt-D while it was starting so I could see the startup messages and I see that that mouse console services started 'OK'.
Thing is it was fine before, and now not. And the other systems are fine...
Well most of the time when this problem is reported it is a Belkin ominview KVM switch.
You might try variations of psmouse.proto=imps or =bare on the kernel command line. That has helped many people in the past with similar problems on the Belkin KVM switches.
I switched to using IOGear KVM switches which have been working just fine with FC and Centos systems.
What versions of Linux are you running?
At 02:39 PM 2/21/2006, Scot L. Harris wrote:
On Tue, 2006-02-21 at 13:55 -0500, Robert Moskowitz wrote:
They are some old Master views.
Use to have an old wheel mouse that did not work.
That is what was present when I build all of these systems.
Now I have a nice Logitech wireless kyb/mouse plugged into the KVM. The use wheel is working on my Win32 systems and on 2 other Centos builds.
Now in my /etc/X11/xorg.conf the Input Device protocol is "IMPS/2"
A friend had me try "PS/2" and things SEEMed a little bit better. Then "auto" and now it seems to be the same as before.
But wait. When the system booked, I was switched to another system. When I boot and leave that system as the 'active' one, I get a similar action as to when it was "PS/2".
I did an Alt-D while it was starting so I could see the startup messages and I see that that mouse console services started 'OK'.
Thing is it was fine before, and now not. And the other systems
are fine...
Well most of the time when this problem is reported it is a Belkin ominview KVM switch.
You might try variations of psmouse.proto=imps or =bare on the kernel command line. That has helped many people in the past with similar problems on the Belkin KVM switches.
I switched to using IOGear KVM switches which have been working just fine with FC and Centos systems.
Well actually these are ATEN switches which is IOGear is. But it is an old device.
What versions of Linux are you running?
Centos 4.2
All the systems are on Centos 4.2.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
Bart Schaefer -
Craig White -
John Pierce -
Robert Moskowitz -
Scot L. Harris -
William (Bill) E. T.