I have a ps/2 scroll mouse and a kvm. If I switch to another session to do something, is screws up the mouse quite bad.
In Redhat 9 I would just bring up the redhat mouse configure app and it would reset the mouse. That does not work in Fedora any more.
What is the correct way to reset the mouse? I want to write an app that I can bind to a keypress in X.
Also, is there going to be a config app to change mouse cursors in Gnome?
Le jeu 15/01/2004 à 10:38, Alan a écrit :
I have a ps/2 scroll mouse and a kvm. If I switch to another session to do something, is screws up the mouse quite bad.
In Redhat 9 I would just bring up the redhat mouse configure app and it would reset the mouse. That does not work in Fedora any more.
In the console, restarting gpm usually does the trick. In X, switching to the console and back does it too.
I think there were changes in 2.6 kernels to take care of kvms (not sure)
Cheers,
On Thu, 2004-01-15 at 01:57, Nicolas Mailhot wrote:
Le jeu 15/01/2004 à 10:38, Alan a écrit :
I have a ps/2 scroll mouse and a kvm. If I switch to another session to do something, is screws up the mouse quite bad.
In Redhat 9 I would just bring up the redhat mouse configure app and it would reset the mouse. That does not work in Fedora any more.
In the console, restarting gpm usually does the trick.
Switching consoles also works. My problem is in X.
In X, switching to the console and back does it too.
I will try that.
I think there were changes in 2.6 kernels to take care of kvms (not sure)
Not for the mouse. I am using the 2.6.1 kernel. (Working fairly well so far. Just a few misc glitches. cdrdao does not work (yet). vmware-config.pl freezes trying to unload modules. (and I have installed the recommended patches.) ALSA is not yet configured correctly. Other than that, it works very well.)
On Thu, Jan 15, 2004 at 01:38:45AM -0800, Alan wrote:
In Redhat 9 I would just bring up the redhat mouse configure app and it would reset the mouse. That does not work in Fedora any more.
Switch to text mode and back probably does the right thing
Also, is there going to be a config app to change mouse cursors in Gnome?
The cursor size is settable (where hardware supports it) in Preferences->Mouse
Alan -- "Facts stand alone. They only need to be noted. Bullshit needs repeating." -- Richard Johnson
On Thu, 2004-01-15 at 09:47, Alan Cox wrote:
On Thu, Jan 15, 2004 at 01:38:45AM -0800, Alan wrote:
In Redhat 9 I would just bring up the redhat mouse configure app and it would reset the mouse. That does not work in Fedora any more.
Switch to text mode and back probably does the right thing
There does not seem to be a keybinding for that anymore. (Used to be something like Alt-F12.) I guess I get to hack one in.
Also, is there going to be a config app to change mouse cursors in Gnome?
The cursor size is settable (where hardware supports it) in Preferences->Mouse
I am talking about the cursor theme. Keith Packard had a way of changing cursors in 4.3.0. There was an initial "cursor theme" changer in Redhat 9, but no way to add new ones. It went away in Fedora.
It is not important, just kind of nice...
"Facts stand alone. They only need to be noted. Bullshit needs repeating." -- Richard Johnson
"Bullshit makes the flowers grow and that's beautiful!" - The Principia Discordia
On Thu, 2004-01-15 at 16:04, Alan wrote:
On Thu, 2004-01-15 at 09:47, Alan Cox wrote:
On Thu, Jan 15, 2004 at 01:38:45AM -0800, Alan wrote:
In Redhat 9 I would just bring up the redhat mouse configure app and it would reset the mouse. That does not work in Fedora any more.
Switch to text mode and back probably does the right thing
There does not seem to be a keybinding for that anymore. (Used to be something like Alt-F12.) I guess I get to hack one in.
Ctrl-Alt-F1 (through F6), and yeah, it's still there.
Also, is there going to be a config app to change mouse cursors in Gnome?
The cursor size is settable (where hardware supports it) in Preferences->Mouse
I am talking about the cursor theme. Keith Packard had a way of changing cursors in 4.3.0. There was an initial "cursor theme" changer in Redhat 9, but no way to add new ones. It went away in Fedora.
It is not important, just kind of nice...
"Facts stand alone. They only need to be noted. Bullshit needs repeating." -- Richard Johnson
"Bullshit makes the flowers grow and that's beautiful!" - The Principia Discordia
-- "Push that big, big granite sphere way up there from way down here! Gasp and sweat and pant and wheeze! Uh-oh! Feel momentum cease! Watch it tumble down and then roll the boulder up again!" - The story of Sisyphus by Dr. Zeus in Frazz 12/18/2003
On Thu, 2004-01-15 at 15:14, Tyler larson wrote:
On Thu, 2004-01-15 at 16:04, Alan wrote:
On Thu, 2004-01-15 at 09:47, Alan Cox wrote:
On Thu, Jan 15, 2004 at 01:38:45AM -0800, Alan wrote:
In Redhat 9 I would just bring up the redhat mouse configure app and it would reset the mouse. That does not work in Fedora any more.
Switch to text mode and back probably does the right thing
There does not seem to be a keybinding for that anymore. (Used to be something like Alt-F12.) I guess I get to hack one in.
Ctrl-Alt-F1 (through F6), and yeah, it's still there.
Kewl. Thanks!
One slight problem here... It does not fix the mouse.
Here is the situation:
I switch over to another system on my KVM switch and the mouse cursor becomes very jumpy and does all sorts of nasty random things.
I am using Fedora 1 with the 2.6.1-1.126 smp kernel.
Switching to a text console does not reset the mouse.
Restarting gpm does not reset the mouse.
The mouse has the same problem in the text console(s) as well.
In the syslog, I get the messages:
Jan 15 15:23:53 zontar kernel: psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. Jan 15 15:24:19 zontar last message repeated 3 times Jan 15 15:24:23 zontar kernel: psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away. Jan 15 15:24:52 zontar kernel: psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. Jan 15 15:25:57 zontar kernel: psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. Jan 15 15:25:59 zontar kernel: psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away. Jan 15 15:26:02 zontar kernel: psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away. Jan 15 15:27:05 zontar gpm: gpm shutdown succeeded Jan 15 15:27:06 zontar gpm: gpm startup succeeded Jan 15 15:27:08 zontar kernel: psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. Jan 15 15:27:16 zontar kernel: psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away.
The only way to get the mouse to go back to "sane operation" is to reboot the machine.
Is this a problem in the 2.6.x kernels or am I missing something?
Alan wrote:
On Thu, 2004-01-15 at 15:14, Tyler larson wrote:
On Thu, 2004-01-15 at 16:04, Alan wrote:
On Thu, 2004-01-15 at 09:47, Alan Cox wrote:
On Thu, Jan 15, 2004 at 01:38:45AM -0800, Alan wrote:
In Redhat 9 I would just bring up the redhat mouse configure app and it would reset the mouse. That does not work in Fedora any more.
Switch to text mode and back probably does the right thing
There does not seem to be a keybinding for that anymore. (Used to be something like Alt-F12.) I guess I get to hack one in.
Ctrl-Alt-F1 (through F6), and yeah, it's still there.
Kewl. Thanks!
One slight problem here... It does not fix the mouse.
Here is the situation:
I switch over to another system on my KVM switch and the mouse cursor becomes very jumpy and does all sorts of nasty random things.
I am using Fedora 1 with the 2.6.1-1.126 smp kernel.
Switching to a text console does not reset the mouse.
Restarting gpm does not reset the mouse.
The mouse has the same problem in the text console(s) as well.
In the syslog, I get the messages:
Jan 15 15:23:53 zontar kernel: psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. Jan 15 15:24:19 zontar last message repeated 3 times Jan 15 15:24:23 zontar kernel: psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away. Jan 15 15:24:52 zontar kernel: psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. Jan 15 15:25:57 zontar kernel: psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. Jan 15 15:25:59 zontar kernel: psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away. Jan 15 15:26:02 zontar kernel: psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away. Jan 15 15:27:05 zontar gpm: gpm shutdown succeeded Jan 15 15:27:06 zontar gpm: gpm startup succeeded Jan 15 15:27:08 zontar kernel: psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. Jan 15 15:27:16 zontar kernel: psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away.
The only way to get the mouse to go back to "sane operation" is to reboot the machine.
Is this a problem in the 2.6.x kernels or am I missing something?
Hi,,, I using FC2 Test1 kernel 2.6.1-1.65 I got problem too...
If AUX port is really absent please use the 'i8042.noaux' option. serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 atkbd.c: Unknown key pressed (raw set 0, code 0x0 on isa0060/serio0). atkbd.c: Use 'setkeycodes 00 <keycode>' to make it known. input: PS/2 Generic Mouse on isa0060/serio0 psmouse.c: Mouse at isa0060/serio0/input0 lost synchronization, throwing 2 bytes away. psmouse.c: Mouse at isa0060/serio0/input0 lost synchronization, throwing 1 bytes away. last message repeated 8 times
This messages show only when I used SMP Kernel. I can't use keyboard ,when I press some key mouse cursor jumping.
I used KVM too.
but I can used UP Kernel...
??
MrChoke
-
Alan -
Alan Cox -
Nicolas Mailhot -
Supphachoke Suntiwichaya -
Tyler Larson