Your message dated Wed, 28 Nov 2007 01:54:03 +0100
with message-id <[EMAIL PROTECTED]>
and subject line PS/2 mouse not properly recognized on MSI KT4V mainboard
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: kernel-image
version: 2.6.8-2-k7
1) congratulations on the 3.1 release! I've been running Sarge on a
number of machines and I love it!
2) This issue is one I should have reported some time ago. Sorry. It
seems to affect the 2.6.7 and 2.6.8 kernels but not the earlier or later
ones. I'm running a system with an MSI KT4V mainboard using an IOgear
MiniView KVM switch. The KT4V seems to have a problem with the MiniView
in that it will produce a keyboard error when I boot (except sometimes
from a cold start) if I have that system selected - but not if I am
watching a different system (go figure). This is generic to the KT4V
because I have another KT4V-based system with the same problem, but
other systems with different mainboards don't have this problem. This
information is provided as background - I know there are issues with
this KVM / Mainboard combination.
The problem I'm having with the 2.6.8 kernel however is that when I boot
the system with the KVM attached to the PS/2 mouse port, the mouse does
not respond properly once X starts. It reacts to mouse movements in a
random fashion. However, if I boot with a mouse attached directly to the
PS/2 port, then switch to the KVM afterwards, the mouse behaves properly.
I had also tried a number of workarounds including changing mouse
parameters in X and adding a mouse parameter in Grub. The latter worked
with the 2.6.7 kernel but not the 2.6.8 one. In the end, I had to go to
Sid to get a newer kernel.
This problem disappeared in the 2.6.9 kernel and is still absent in the
2.6.11 one which I am currently using (my only deviation from Sarge).
--- End Message ---
--- Begin Message ---
Version: 2.6.9-1
> This problem disappeared in the 2.6.9 kernel and is still absent in the
> 2.6.11 one which I am currently using (my only deviation from Sarge).
so assuming that current stable 2.6.18 works fine too,
thus closing.
hope you have fun with the Debian improvements.
all the best
--
maks
--- End Message ---
