The mouse driver, re-developed for kernel 2.6, ever since the earliest 2.6 release lost the ability to reset a broken link with an IMPS2 mouse (this happens when disconnecting the mouse plug either physically or through a "non imps2" KVM switch). The result is that the mouse can no longer be controlled, with the only solution being a RE-BOOT!
This issue has been filed as bug 2082 (http://bugme.osdl.org/show_bug.cgi?id=2082) . A fix was posted for 2.6.8, but this patch never made its way into the kernel main stream. "Vojtech", author of the 2.6 mouse driver, keeps modifying his code version after version, therefore breaking compatibility with the posted patch. I adapted the patch for 2.6.9 and 2.6.10 (there are now three versions for 2.6.8, 2.6.9 and 2.6.10). Kernel 2.6.11(.6) was released recently, still with the same bug, and would require further adaptation of the posted patch. I was wondering if some business related priority could be set for this issue. Given that most Linux deployments are in server farms, where boxes share a console attached to a KVM that might good enough, but not properly supporting IMPS2, please, could we include this patch in the kernel main stream before adding support for any new mouse device that hardly anyone running a server would be interested in? Mauro - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
