Re: quick question (shot in the dark)
On Thu, Jan 17, 2002 at 06:43:42AM -0500, John Magrini wrote: > when i switch back to my debian box, my mouse movements are all scrambled, > the mouse driver basically eats it. the fix is to switch to a console and > then back again, i suppose this resets the driver. Now, can KDE reset the > driver at all, or is this compleatly X and kde has no power to do this. > this is just a frustrating problem, not vital but if someone has an answer it > would be greatly appreciated. The only thing I can think of is are you using a PS/2 or a USB interface for your mouse? PS/2 is not designed to hot-plug (which I think is how KVM switches work), so maybe it just gets confused. Have you tried using it as a USB mouse? I have the same mouse, and it works fine, with both GPM and X (using raw-repeating). As an aside, I think I blew my PS/2 mouse port from hot-plugging my mouse one to many times...fortunately, this was just after working USB [mouse] support entered the 2.2 kernels (I think...), so I just dropped the USB->PS/2 converter dongle. Anyhow, I hope you figure it out. -rob pgpACTeI8w0tr.pgp Description: PGP signature
Re: quick question (shot in the dark)
John Magrini <[EMAIL PROTECTED]> wrote: im not sure if kde can do anything about this, but it doesnt hurt to ask. i have already asked on the Xfree mailing lists and the advice they gave me was that the driver needs to be coded better. situation: im using a KVM to switch between debian and windows, im running sid with the latest kde 2.X. my mouse is the micro$oft intellimouse explorer, X is setup fine using the correct /dev/ device and the right protocal. buttons are setup fine. problem: when i switch back to my debian box, my mouse movements are all scrambled, the mouse driver basically eats it. the fix is to switch to a console and then back again, i suppose this resets the driver. Now, can KDE reset the driver at all, or is this compleatly X and kde has no power to do this. this is just a frustrating problem, not vital but if someone has an answer it would be greatly appreciated. as a sidenote, when i switch to my win2k box, i get a sharp: 10-15 lines scrolldown, then everything is fine. i suppose it resets itself after that. just a shot in the dark to see if kde can control this, thanks John I don't think this is a "specific" KDE problem, nor does it have a solution. However, here are some ideas for you to consider. 1. Are you using GPM for the mouse driver in X? Your symptoms sound suspiciously like the message I get whenever the GPM program is re-started during an upgrade. If you are NOT, then try using it. If you are using it, try going directly to the device (psaux, ttyS0, etc). I am using GPM with a Microsoft Wheelmouse (Intellimouse) w/ "Intellieye" thorugh a USB port at the moment. 2. Are the computers networked? If so, you can use the VNC programs to connect your Linux box to the Winders box. You would need to install a VNC "server" on the Windows box and the vncviewer on your Linux box. I have done this here and it is like having a remote X terminal. You login and the Windows screen comes up on your Linux box and you can run all the Windows programs remotely. This would avoid having to use the KVM switch. You can read more about VNC at: http://www.uk.research.att.com/vnc/ Cheers, -Don Spoon-
Re: quick question (shot in the dark)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is strictly X, sorry. On Thursday 17 January 2002 04:43 am, John Magrini wrote: > im not sure if kde can do anything about this, but it doesnt hurt to ask. > i have already asked on the Xfree mailing lists and the advice they gave me > was that the driver needs to be coded better. - -- D.A.Bishop -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8SDmiEHLN/FXAbC0RAitgAKCDbLj6Kp9qG6CRoKcixeYKY6dxHwCeK/MT cBvniibeLFQyBtwiI3ghkO0= =vbWh -END PGP SIGNATURE-
quick question (shot in the dark)
im not sure if kde can do anything about this, but it doesnt hurt to ask. i have already asked on the Xfree mailing lists and the advice they gave me was that the driver needs to be coded better. situation: im using a KVM to switch between debian and windows, im running sid with the latest kde 2.X. my mouse is the micro$oft intellimouse explorer, X is setup fine using the correct /dev/ device and the right protocal. buttons are setup fine. problem: when i switch back to my debian box, my mouse movements are all scrambled, the mouse driver basically eats it. the fix is to switch to a console and then back again, i suppose this resets the driver. Now, can KDE reset the driver at all, or is this compleatly X and kde has no power to do this. this is just a frustrating problem, not vital but if someone has an answer it would be greatly appreciated. as a sidenote, when i switch to my win2k box, i get a sharp: 10-15 lines scrolldown, then everything is fine. i suppose it resets itself after that. just a shot in the dark to see if kde can control this, thanks John
