Been through this before...
upgraded from FC-1 to FC-3 - using a Belkin KVM
things worked ok on FC-1
when switching back to FC-3, mouse is erratic and unusable. Doesn't help to switch to text console (Control-Alt-F2) and back to X. Doesn't help to add psmouse.proto=imps to grub boot.
Anyone else seeing this on FC-32.6.9-1.681_FC3 ?
Craig
when switching back to FC-3, mouse is erratic and unusable. Doesn't help to switch to text console (Control-Alt-F2) and back to X. Doesn't help
Drives me crazy and I actually had 2 mouses on my desk not plugged into the KVM but a friend said hitting the ESC key worked for him and I tried it, it works for me too. I have no idea why the ESC key would fix it but it does for my friend and I. By the way it started on FC2 for me.
On Sunday 05 December 2004 01:47 am, Craig White wrote:
Been through this before...
upgraded from FC-1 to FC-3 - using a Belkin KVM
things worked ok on FC-1
when switching back to FC-3, mouse is erratic and unusable. Doesn't help to switch to text console (Control-Alt-F2) and back to X. Doesn't help to add psmouse.proto=imps to grub boot.
Anyone else seeing this on FC-32.6.9-1.681_FC3 ?
Yes! I've got a Belkin Omniview SE 4-port switch. Back in RH9 it worked fine. Now it doesn't work and I *have* to use VNC to have a useable system. If you figure out what the problem is, let me know. I thought maybe it was my mouse settings since I'm not using a "name-brand" mouse!
On Sun, 2004-12-05 at 15:01, John Aldrich wrote:
On Sunday 05 December 2004 01:47 am, Craig White wrote:
Been through this before...
upgraded from FC-1 to FC-3 - using a Belkin KVM
things worked ok on FC-1
when switching back to FC-3, mouse is erratic and unusable. Doesn't help to switch to text console (Control-Alt-F2) and back to X. Doesn't help to add psmouse.proto=imps to grub boot.
Anyone else seeing this on FC-32.6.9-1.681_FC3 ?
Yes! I've got a Belkin Omniview SE 4-port switch. Back in RH9 it worked fine. Now it doesn't work and I *have* to use VNC to have a useable system. If you figure out what the problem is, let me know. I thought maybe it was my mouse settings since I'm not using a "name-brand" mouse!
If you look at the archives there are many posts on this topic. The root problem seems to be that the Belkin KVM does not do keep-alive so the mouse/keyboard is effectively detached from the computer unless it is the selected option on the KVM. Interestingly enough, I have found this with FC1 too, but not RH7.3 or 7.2.
I have psmouse.proto=bare in the kernel line in grub.conf and I don't have any problem. Does this work in your case?
Regards
Chris
On Sunday 05 December 2004 01:57 pm, Chris Hewitt wrote:
If you look at the archives there are many posts on this topic. The root problem seems to be that the Belkin KVM does not do keep-alive so the mouse/keyboard is effectively detached from the computer unless it is the selected option on the KVM. Interestingly enough, I have found this with FC1 too, but not RH7.3 or 7.2.
I have psmouse.proto=bare in the kernel line in grub.conf and I don't have any problem. Does this work in your case?
No, but I'm wondering what changed between RH9 and FC3 that it doesn't work now...
Also, what is the *exact* option one uses? Finally, last time I tried to edit my grub.conf, I ended up screwing things up so badly I couldn't boot off the hdd and had to boot off floppy. Obviously that's not going to work this time. I'd appreciate some help getting this fixed...
Thanks.
On Mon, 2004-12-06 at 11:44, John Aldrich wrote:
On Sunday 05 December 2004 01:57 pm, Chris Hewitt wrote:
If you look at the archives there are many posts on this topic. The root problem seems to be that the Belkin KVM does not do keep-alive so the mouse/keyboard is effectively detached from the computer unless it is the selected option on the KVM. Interestingly enough, I have found this with FC1 too, but not RH7.3 or 7.2.
I have psmouse.proto=bare in the kernel line in grub.conf and I don't have any problem. Does this work in your case?
No, but I'm wondering what changed between RH9 and FC3 that it doesn't work now...
My guess, the kernel.
Also, what is the *exact* option one uses? Finally, last time I tried to edit my grub.conf, I ended up screwing things up so badly I couldn't boot off the hdd and had to boot off floppy. Obviously that's not going to work this time. I'd appreciate some help getting this fixed...
My kernel line in grub.conf for FC3 is "kernel /vmlinuz-2.6.9-1.667 psmouse.proto=bare ro root=/dev/hdb7 rhgb quiet". This is for the original kernel and my root partition so yours may differ.
If you are worried about messing up grub.conf and not being able to boot, you could copy the whole 4 lines and give it a different title then edit that. This way you get an extra bootup option in the grub list and if you have messed up the edited one you can boot from the original.
Hope this helps.
Chris
On Sun, 2004-12-05 at 18:57 +0000, Chris Hewitt wrote:
On Sun, 2004-12-05 at 15:01, John Aldrich wrote:
On Sunday 05 December 2004 01:47 am, Craig White wrote:
Been through this before...
upgraded from FC-1 to FC-3 - using a Belkin KVM
things worked ok on FC-1
when switching back to FC-3, mouse is erratic and unusable. Doesn't help to switch to text console (Control-Alt-F2) and back to X. Doesn't help to add psmouse.proto=imps to grub boot.
Anyone else seeing this on FC-32.6.9-1.681_FC3 ?
Yes! I've got a Belkin Omniview SE 4-port switch. Back in RH9 it worked fine. Now it doesn't work and I *have* to use VNC to have a useable system. If you figure out what the problem is, let me know. I thought maybe it was my mouse settings since I'm not using a "name-brand" mouse!
If you look at the archives there are many posts on this topic. The root problem seems to be that the Belkin KVM does not do keep-alive so the mouse/keyboard is effectively detached from the computer unless it is the selected option on the KVM. Interestingly enough, I have found this with FC1 too, but not RH7.3 or 7.2.
I have psmouse.proto=bare in the kernel line in grub.conf and I don't have any problem. Does this work in your case?
---- indeed, appending psmouse.proto=bare worked where as psmouse.proto=imps didn't work.
Thanks to all - just wanted to post up a resolution
Craig
-
Chris Hewitt -
Craig White -
John Aldrich -
Mike Rambour