Received & installed 8.2 Pro - very, very happy. Only 2 issues - one is 'optical mouse goes insane in KDE'. (Other will be posted separately) I use the combination of KVM & optical mouse. This is a Logitech 2x Optical USB Wheel Mouse connected to the Belkin KVM using a USB to PS2 connector. When I flip away from the box & return, the mouse frequently goes insane. The symptoms are as described in SuSE's document "X Server Configuration with SaX", section "Mouse Problems". It seems as long as I keep the KVM pointing to the SuSE box, I have no problem. When I switch away and return, the symptoms show up. If I'm lucky enough to have YaST2 Control or a Konsole up, then I can restabilize the mouse through selecting & Test (YaST) or sax. Any ideas for work around appreciated - although I like the mouse, I'm close to giving it up because I like SuSE 8.2 better /Hans (I admit, I haven't RTFM for this yet - a few other crisis going on. TIA to anyone who answers, especially who points to the proper place in the manual.)
This is, definetely, KVM problem :-)
----- Original Message -----
From: "Hans Forbrich"
Received & installed 8.2 Pro - very, very happy. Only 2 issues - one is 'optical mouse goes insane in KDE'. (Other will be posted separately)
I use the combination of KVM & optical mouse. This is a Logitech 2x Optical USB Wheel Mouse connected to the Belkin KVM using a USB to PS2 connector.
When I flip away from the box & return, the mouse frequently goes insane.
Dmitry Melekhov wrote:
This is, definetely, KVM problem :-)
How so? Yes, the KVM is causing the mouse to be disconnected/reconnected. But does this mean the kernel/mouse-handler needs to lose knowledge of the mouse? A possible workaround might be something I can invoke, or maybe click in lower left corner - seems to be mouse's home, to run the sax command again. Right now, without digging too deep, I'd think some sort of keep-alive-timeout setting for the mouse might be the answer. Also, I think the problem is the Optical Wheel Mouse, not the KVM, especially since the symptoms are known for USB Wheel Mice. The thing that concerns me - Linux is going mainstream enterprise, where we'll see more and more KVMs. Is this going to be an issue? /Hans
* Hans Forbrich (forbrich@telusplanet.net) [030417 09:12]: -> ->Yes, the KVM is causing the mouse to be disconnected/reconnected. But does ->this mean the kernel/mouse-handler needs to lose knowledge of the mouse? -> ->A possible workaround might be something I can invoke, or maybe click in lower ->left corner - seems to be mouse's home, to run the sax command again. Right ->now, without digging too deep, I'd think some sort of keep-alive-timeout ->setting for the mouse might be the answer. Also, I think the problem is the ->Optical Wheel Mouse, not the KVM, especially since the symptoms are known for ->USB Wheel Mice. -> ->The thing that concerns me - Linux is going mainstream enterprise, where we'll ->see more and more KVMs. Is this going to be an issue? It is a problem between " powered " KVM switches, X and Wheel mice. A co-worker was having issues with an older Belkin KVM that he was using. I gave him a Linksys switch that didn't require power and the problem went away. I believe newer Belkin's do not suffer from this. It's not a Linux kernel issue. It's an XFree86 issue because I had the same problem with two FreeBSD boxes in my lab at work. I'm not sure if there is a fix yet since I moved these machines to a Linksys KVM and they work fine. You might want to see if there is a fix in Xfree86 4.3.0 for this.. I've not checked it out recently. -- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org Tell me what you believe.. I'll tell you what you should see.
----- Original Message -----
From: "Hans Forbrich"
Dmitry Melekhov wrote:
This is, definetely, KVM problem :-)
How so?
Yes, the KVM is causing the mouse to be disconnected/reconnected. But does this mean the kernel/mouse-handler needs to lose knowledge of the mouse?
OK, I forgot to add IMHO.
The thing that concerns me - Linux is going mainstream enterprise, where we'll see more and more KVMs. Is this going to be an issue?
No. First, I never had such problem with our HP switches. Certanly, I only _tested_ this, but don't use in production. Second, and more important, - I don't need X and even framebuffer on server, so I don't need mouse on server. I even don't need more than serial console, unfortunately it is impossible to run most if x86 servers in headless mode :-(
----- Original Message -----
From: "Hans Forbrich"
Dmitry Melekhov wrote:
This is, definetely, KVM problem :-)
How so?
Yes, the KVM is causing the mouse to be disconnected/reconnected. But does this mean the kernel/mouse-handler needs to lose knowledge of the mouse?
Oh, sorry! When I talked about switch, I talked about so called electronics switch, i.e. mouse and keyboard are _not_ disconnected! => switch problem :-)
Dmitry Melekhov wrote:
This is, definetely, KVM problem :-)
How so? Yes, the KVM is causing the mouse to be disconnected/reconnected. But does this mean the kernel/mouse-handler needs to lose knowledge of the mouse? A possible workaround might be something I can invoke, or maybe click in lower left corner - seems to be mouse's home, to run the sax command again. Right now, without digging too deep, I'd think some sort of keep-alive-timeout setting for the mouse might be the answer. Also, I think the problem is the Optical Wheel Mouse, not the KVM, especially since the symptoms are known for USB Wheel Mice. The thing that concerns me - Linux is going mainstream enterprise, where we'll see more and more KVMs. Is this going to be an issue? /Hans
Dmitry Melekhov wrote:
OK, I forgot to add IMHO.
Sorry if I sound grumpy - brand new KVM, brand new mouse and new release of my favorite OS. It does appear to be the KVM - see bottom.
No. First, I never had such problem with our HP switches. Certanly, I only _tested_ this, but don't use in production. Second, and more important, - I don't need X and even framebuffer on server, so I don't need mouse on server. I even don't need more than serial console, unfortunately it is impossible to run most if x86 servers in headless mode :-(
AND Ben Rosenberg wrote:
It is a problem between " powered " KVM switches, X and Wheel mice. A co-worker was having issues with an older Belkin KVM that he was using. I gave him a Linksys switch that didn't require power and the problem went away. I believe newer Belkin's do not suffer from this. It's not a Linux kernel issue. It's an XFree86 issue because I had the same problem with two FreeBSD boxes in my lab at work. I'm not sure if there is a fix yet since I moved these machines to a Linksys KVM and they work fine. You might want to see if there is a fix in Xfree86 4.3.0 for this.. I've not checked it out recently.
OK ... The original KVM was a Belkin Omniview SOHO 4-port (model F1DS104P). This is a unit with >optional< power, which I do not have installed, so it (apparently) get's it's power from the PS2 keyboard connections. I switched to a non-optical wheel mouse - same problem. I then switched to a Belkin OmniView SE 4-port (model F1D104). This is a powered unit. Mouse works fine. So I get a different result than Ben???? Next tests - switch back & add power to the SOHO. Then switch to a non-wheel mouse (if I can find one <g>) Thanks to both of you ofr the ideas, suggestions, etc. /Hans
Hello, I have a F1D094 Belkin OMNI-Cube 4 port powered KVM switch. Here is what happens here: If it is switched to a system that is running OK and I switch it to another sys all is OK. If it is switched to a sys that hung, or otherwise lost its Op Sys then it may or may not switch to another sys by keyboard key combo. If I switch it to another working sys by pushing the Belkin's switch, it is likely that there will be no mouse avail to the newly selected system. NOTE: this means that when a system 'messes-up' it can affect how the other systems work. If I leave the KVM switched to the hung system and reset adn reboot the sys, and the reboot works, then I can switch to other systems w/o problems. My (Semi-perment) solution? I plug seperate mice into each system HTH .............. PeterB On Thursday 17 April 2003 12:37 pm, Hans Forbrich wrote:
Dmitry Melekhov wrote:
OK, I forgot to add IMHO.
Sorry if I sound grumpy - brand new KVM, brand new mouse and new release of my favorite OS.
It does appear to be the KVM - see bottom.
No. First, I never had such problem with our HP switches. Certanly, I only _tested_ this, but don't use in production. Second, and more important, - I don't need X and even framebuffer on server, so I don't need mouse on server. I even don't need more than serial console, unfortunately it is impossible to run most if x86 servers in headless mode :-(
AND
Ben Rosenberg wrote:
It is a problem between " powered " KVM switches, X and Wheel mice. A co-worker was having issues with an older Belkin KVM that he was using. I gave him a Linksys switch that didn't require power and the problem went away. I believe newer Belkin's do not suffer from this. It's not a Linux kernel issue. It's an XFree86 issue because I had the same problem with two FreeBSD boxes in my lab at work. I'm not sure if there is a fix yet since I moved these machines to a Linksys KVM and they work fine. You might want to see if there is a fix in Xfree86 4.3.0 for this.. I've not checked it out recently.
OK ...
The original KVM was a Belkin Omniview SOHO 4-port (model F1DS104P). This is a unit with >optional< power, which I do not have installed, so it (apparently) get's it's power from the PS2 keyboard connections.
I switched to a non-optical wheel mouse - same problem.
I then switched to a Belkin OmniView SE 4-port (model F1D104). This is a powered unit. Mouse works fine. So I get a different result than Ben????
Next tests - switch back & add power to the SOHO. Then switch to a non-wheel mouse (if I can find one <g>)
Thanks to both of you ofr the ideas, suggestions, etc. /Hans
-- -- Proud to be a SuSE Linux User since 5.2 --
On Thursday 17 April 2003 20:21, Peter B Van Campen wrote:
Hello,
I have a F1D094 Belkin OMNI-Cube 4 port powered KVM switch.
Here is what happens here:
If it is switched to a system that is running OK and I switch it to another sys all is OK.
If it is switched to a sys that hung, or otherwise lost its Op Sys then it may or may not switch to another sys by keyboard key combo. If I switch it to another working sys by pushing the Belkin's switch, it is likely that there will be no mouse avail to the newly selected system. NOTE: this means that when a system 'messes-up' it can affect how the other systems work.
If I leave the KVM switched to the hung system and reset adn reboot the sys, and the reboot works, then I can switch to other systems w/o problems.
My (Semi-perment) solution? I plug seperate mice into each system
<snip> My brother uses a kvm switch for a linux and windows pc. The mice have been plugged into each machine separately as otherwise the switching does not go smoothly.
Anyone here using a Sony Vaio notebook with Suse? I would like to know what problems you've had, if any, with the combination. Thanks Jerome
Hi, On Friday 18 April 2003 07:03, Jerome Lyles wrote:
Anyone here using a Sony Vaio notebook with Suse? I would like to know what problems you've had, if any, with the combination.
I'm using an FX605 with 8.1, had some problems with the DVD/RW combo but got it sorted out using the various docs available on the 'net. It's a very good distro IMHO, been using it for years. But... today I'm going to pick up the new 8.2 and judging by the reports on the SuSE mailing list it's even better than 8.1! Martijn
A good resource for all kinds of notebooks is at: http://www.linux-on-laptops.com/ It is a link page to peoples personal page and how they got Linux to work or not on their notebooks. pben
Hi, On Friday 18 April 2003 07:03, Jerome Lyles wrote:
Anyone here using a Sony Vaio notebook with Suse? I would like to know what problems you've had, if any, with the combination.
Did you know there is a mailing list dedicated to Linux on Sony laptops? Check out http://returntonature.com/mailman/listinfo/linux-sony and http://returntonature.com/linux/phpwiki. <cross-posted to linux-sony> I picked up the latest SuSE last week (6 CDs, one DVD) and installed it over the weekend. Here is a small account. For the record: the install took place on a Vaio FX-605. I chose a full install, since I experienced some quircks with upgrading an existing installation before. So I made a backup of my $HOME, popped in the DVD and rebooted. I heard before that getting the initial screen resolution right is important in order to save yourself hassles later on, so in the installation boot screen I chose the 1024x768 resolution. The rest of the installation was really a piece of cake. I kept a note of my previous partitioning scheme and simply used that for the new installation (ReiserFS), taking care not to format /home. Practically all my hardware was correctly autodetected: Athlon kernel got installed, PCMCIA, USB mouse, keypad, screen, sound (via686), DVD/RW/CD combo, videocard, ethernet card (rtl8139too). The exception being the HSF modem, but after installing the HSF software and running hsf-config that was fixed too, and my bubblejet printer: it turned out that selecting BJ-200 in stead of BJ-200ex solved that one. Choosing the locale, time zone, etc. is simple enough. As is the selection of packages. As the packages were being installed I went shopping, when I returned only a few questioned had to be answered (forgot what they were) and I was up and running! To get ACPI to work properly I had to add the ac, battery, fan, button, etc. modules to the list of modules to be loaded at boot time, this I did with the sysconfig editor in YaST2. I also found out that, in order to run VMware, apic must be enabled with the 'apic' boot option. Since that causes a hangup at shutdown (the laptop is not actually powering off) I only use it if I know I'm going to use VMware. In all, I'm very impressed with this release of SuSE and can recommended it to anyone! Regards, Martijn
* Hans Forbrich
Dmitry Melekhov wrote:
OK, I forgot to add IMHO.
Sorry if I sound grumpy - brand new KVM, brand new mouse and new release of my favorite OS.
It does appear to be the KVM - see bottom.
My experience with KVM switchs and wheel mice suggest that the combo -> KVM && Wheel mice <- is a root of problems. Unless you have a KVM switch that explicitly supports wheel mice (and states so in the docs) you are more than likely SOL. My setup Mouse -> KVM -> -> Linux box -> SGI O2 -> Sun box with PS/2 converter -> ?? (spare, either a laptop, second linux box, second O2 or whatever I have to fiddle with) All machines work just fine with a wheel mouse attached directly (well, except for the sun PS/2 cponverter box and some wheel mice) If I plug the KVM in between -> Sun box refuses to reconginise the middle mouse -> O2 refuses to see the middle mouse button [and I've tested this with only the specifix machine to the KVM] I had an older box (P166) as 4th machine, and it would see the wheel mouse, but when I've switched back and back again it would indeed go all haywire It looked as if the KVM switch no longer was sending imps/2 but normal ps/2 Switching back to the primary linux box never had any problems. In the end I ended up sticking a regular mouse (an old logitech 3 button one) hooking that up to the KVM swicth, and a nice optical wheel USB mouse which is connected to the USB port of the primary linux box (and an XF86Config that excepts input from both mice). Yes, I now have 2 mice next to the keyboard , 1 left [1] and 1 to the right, but it gets the job done just fine [1] if you are right handed, try mousing with your left hand .. it actually does a lot of good to prevent RSI ;)
Ben Rosenberg wrote:
It is a problem between " powered " KVM switches, X and Wheel mice. A True
The original KVM was a Belkin Omniview SOHO 4-port (model F1DS104P). This is a unit with >optional< power, which I do not have installed, so it (apparently) get's it's power from the PS2 keyboard connections.
But that is a powered unit as well, even though it only gets it's power from the PS/2 port. If you can find a mechanical KVM switch (though I've never seen a mechanical PS/2 one) the problem will not occur
I switched to a non-optical wheel mouse - same problem.
I then switched to a Belkin OmniView SE 4-port (model F1D104). This is a powered unit. Mouse works fine. So I get a different result than Ben????
It probably has better logic
Next tests - switch back & add power to the SOHO. Then switch to a non-wheel mouse (if I can find one <g>)
I know that feeling .. I found mine in the spare parts drawer, somewehre in the back next to 2 serial mice ;) Currently listening to: CD Audio Track 5 Gerhard, [faliquid@xs4all.nl] == The Acoustic Motorbiker == -- __O and I dreamed I wandered wayward as a restless wave =`\<, spanning from here to yonder most spectacularly saved (=)/(=) Dream and life entwine The old day cracks and crumbles and it's fine to be in your company funny to be in your day Never in a Life of Sundays would I have seen me here.
Thanks to all who replied, and esp. for all the ideas and suggestions. It appears that the Belkin OmniView SOHO 4-port PS/2 KVM (model F1DS104P) is not compatible with SuSE 8.2 / XFree86 in both powered and unpowered mode. For that cluster, I will need separate mice (for now) However, after 2.5 hours testing, the powered Belkin OmniView SE 4-port (model F1D104) does appear to be compatible with the Logitech Optical Wheel Mouse. That goes on the lab cluster. /Hans Hans Forbrich wrote:
Received & installed 8.2 Pro - very, very happy. Only 2 issues - one is 'optical mouse goes insane in KDE'. (Other will be posted separately)
I use the combination of KVM & optical mouse. This is a Logitech 2x Optical USB Wheel Mouse connected to the Belkin KVM using a USB to PS2 connector.
When I flip away from the box & return, the mouse frequently goes insane. The symptoms are as described in SuSE's document "X Server Configuration with SaX", section "Mouse Problems". It seems as long as I keep the KVM pointing to the SuSE box, I have no problem. When I switch away and return, the symptoms show up. If I'm lucky enough to have YaST2 Control or a Konsole up, then I can restabilize the mouse through selecting & Test (YaST) or sax.
Any ideas for work around appreciated - although I like the mouse, I'm close to giving it up because I like SuSE 8.2 better
/Hans (I admit, I haven't RTFM for this yet - a few other crisis going on. TIA to anyone who answers, especially who points to the proper place in the manual.)
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Friday 18 April 2003 09:02, Hans Forbrich wrote:
Thanks to all who replied, and esp. for all the ideas and suggestions.
It appears that the Belkin OmniView SOHO 4-port PS/2 KVM (model F1DS104P) is not compatible with SuSE 8.2 / XFree86 in both powered and unpowered mode. For that cluster, I will need separate mice (for now)
I've got a F1DS104P and a Logitech wheel mouse. Same problem. I heard that using a genuine MS Intellimouse Explorer fixes the problem, but that didn't work for me. You have 3 options: 1) Use a non-wheel mouse. The ps/2 protocol works, the imps/2 is the one with the problem. 2) Use 2 mouses. 3) When you switch back to Linux using the KVM, hit Ctrl-Alt-F1 then Ctrl-Alt-F7. Leaving and re-entering the X Server causes it to reinitialise the mouse port, which fixes the problem. I use option 3. You just need to get into the habit. :o) -- "...our desktop is falling behind stability-wise and feature wise to KDE ...when I went to Mexico in December to the facility where we launched gnome, they had all switched to KDE3." - Miguel de Icaza, March 2003
Derek Fountain wrote:
On Friday 18 April 2003 09:02, Hans Forbrich wrote:
Thanks to all who replied, and esp. for all the ideas and suggestions.
It appears that the Belkin OmniView SOHO 4-port PS/2 KVM (model F1DS104P) is not compatible with SuSE 8.2 / XFree86 in both powered and unpowered mode. For that cluster, I will need separate mice (for now)
I've got a F1DS104P and a Logitech wheel mouse. Same problem. I heard that using a genuine MS Intellimouse Explorer fixes the problem, but that didn't work for me.
Won't work for me either. I refuse to hand over any single $ more to the empire than I absolutely have to .... "give unto caesar that which is caesar's, make sure he doesn't know about the rest."
You have 3 options:
1) Use a non-wheel mouse. The ps/2 protocol works, the imps/2 is the one with the problem.
So I've read. For me, the optical part is the important part, not the wheel. (Wife's been having problems with her dustcatching mouse. I wonder ...)
2) Use 2 mouses.
Definitely - but only as an interim solution. Since I lack the full set of cables (rest arriving Tuesday) I currently have 4 rodents at my primary workstation. Gets too crowded and confusing.
3) When you switch back to Linux using the KVM, hit Ctrl-Alt-F1 then Ctrl-Alt-F7. Leaving and re-entering the X Server causes it to reinitialise the mouse port, which fixes the problem.
I knew there was a way to do this. I do believe you've just saved me a major set of headaches.
I use option 3. You just need to get into the habit. :o)
Nothing that a black felt marker, a piece of paper and some sticky tape can't fix. (Noticing the .uk in your address) should you ever happen towards western Canada, drop me a line - I owe you a pint. /Hans
Not just a headach this tip just sold me on KVM though not the more
expensive versions. It would seem workable for all types of KVM. As I
remember in switching from X to console and back causes linux to switch
the prioritys, if i got that name right, of the hardware from the
different screen modes.
If I have the termonology wrong please correct me as I spend lots of time
on google.com/linux studying.
CWSIV
On Thu, 17 Apr 2003 22:15:02 -0600 Hans Forbrich
Derek Fountain wrote: You have 3 options:
1) Use a non-wheel mouse. The ps/2 protocol works, the imps/2 is the one with the problem.
So I've read. For me, the optical part is the important part, not the wheel. (Wife's been having problems with her dustcatching mouse. I wonder ...)
3) When you switch back to Linux using the KVM, hit Ctrl-Alt-F1 then Ctrl-Alt-F7. Leaving and re-entering the X Server causes it to reinitialise the mouse port, which fixes the problem.
I knew there was a way to do this. I do believe you've just saved me a major set of headaches. ________________________________________________________________ The best thing to hit the internet in years - Juno SpeedBand! Surf the web up to FIVE TIMES FASTER! Only $14.95/ month - visit www.juno.com to sign up today!
participants (11)
-
Ben Rosenberg -
Carl William Spitzer IV -
Derek Fountain -
Dmitry Melekhov -
Gerhard den Hollander -
Hans Forbrich -
Jerome Lyles -
LinuxWorld999 -
Martijn van den Burg -
Paul Benjamin -
Peter B Van Campen