Mouse disappears after kvm switch

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in recently. We were wondering if this is still an issue for you? Thanks in advance.

Yes it does still happen although I have found a slightly nicer workaround. I am now running Gutsy here and if it helps here are some syslog extracts:

Reloading the kernel module with:

#modprobe -r psmouse
#modprobe psmouse

Gives the following:

Dec 11 09:19:47 len NetworkManager: <debug> [1197364787.754732] nm_hal_device_removed(): Device removed (hal udi is /org/freedesktop/Hal/devices/platform_i8042_i8042_AUX_port_logicaldev_input').
Dec 11 09:19:48 len kernel: [68553.988000] input: PS/2 Generic Mouse as /class/input/input9
Dec 11 09:19:48 len NetworkManager: <debug> [1197364788.064945] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX_port_logicaldev_input').

and I still have no mouse cursor, but pressing reset on the kvm switch (better than unplugging but still awkward) gives:

Dec 11 09:21:06 len NetworkManager: <debug> [1197364866.597000] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX_port_logicaldev_input').
Dec 11 09:21:07 len NetworkManager: <debug> [1197364867.304938] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX_port_logicaldev_input').
Dec 11 09:21:07 len kernel: [68633.108000] input: ImPS/2 Generic Wheel Mouse as /class/input/input10

and I do get the mouse back.

If any other info would help then please ask and I'll do my best to be rather quicker responding this time.

The Hardy Heron kernel was recently uploaded for testing. We'd really appreciate it if you could try testing with this newer kernel and verify if this issue still exists. Unfortunately, the Hardy Heron Alpha1 LiveCD was released with the older 2.6.22 kernel. You'll have to manually install the newer Hardy Heron kernel in order to test. This should not be the case for Alpha2. However, here are the instructions to install (if you choose to do so):

1) edit the file /etc/apt/sources.list and add the following line:

deb http://archive.ubuntu.com/ubuntu hardy main restricted

2) sudo apt-get update
3) sudo apt-get install linux-image-2.6.24-1-generic
4) reboot and select the new kernel from the grub menu

After you've tested, please feel free to revert back - ie boot into the old kernel, sudo apt-get remove linux-image-2.6.24-1-generic, and remove the line from /etc/apt/sources.list . Please update this report with your results. Thanks in advance!

OK, I tried this as requested but there is no change.

X41 still needs me to reset the kvm switch, another box will still bring the mouse back by reloading the psmouse module.

I haven't completely reverted the X41 in case there are any other tests you'd like to see on the newer kernel. I would feel happier getting back to just Gutsy though as this is an important box for me. Please let me know if there is any need to keep the newer kernel.

Another thought, in case you're not familiar with the X41, the mouse is connected to the docking station - there is no PS/2 port on the laptop itself. I don't know what difference this could make but just in case...

Thanks for looking into this.

Thanks George.

Feel free to go back to using the Gutsy kernel. The Hardy Heron Alpha2 LiveCD will be coming out within days and will contain the newer 2.6.24 kernel. Any further testing can be done via the LiveCD. If you can, once the Alpha2 LiveCD is available, care to run it and capturing the following files:

* uname -a > uname-a.log
* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

Please be sure to attach each file as a separate attachment. For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . I'll be sure to update this report when Alpha2 is available. Thanks again and we appreciate your help and feedback.

We've opened a new task ('linux') against the actively developed kernel. However, I'm closing the report against linux-source-2.6.22 as it does not meet the criteria for a stable release update. You can learn more about the stable release update process at https://wiki.ubuntu.com/StableReleaseUpdates . Thanks!

Here are the attached logs from an alpha2 livecd. I went through my "normal" test:

Booted
Switched the KVM to another box
Switched back - no mouse
Unloaded and reload module psmouse - still no mouse
Pressed reset on the KVM switch - mouse comes back

No argument from me about ignoring this for a stable upgrade but it would be good to solve for a new release.

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

I have tested using the Alpha5 LiveCD. The problem remains. There is a little more to say though...

I have changed to a newer KVM switch (to use a higher display resolution - nothing to do with this problem). The problem has become intermittent now but otherwise I can't spot any difference. There's no obvious difference between Hardy and Intrepid.

One suspicion which I'll mention just in case it helps, is that removing power from the docking station when the laptop is off /might/ make the loss of mouse less frequent. I haven't been able to spot any pattern so I can't support this with any evidence at all - not even relative frequency.

Let me know if you'd like any detail attaching but it didn't seem to add anything.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Have you tried with a different mouse?

This bug was reported a while ago but there hasn't been any recent comments or updates. Is this still an issue with the latest pre-release of Jaunty 9.04? Refer to http://www.ubuntu.com/testing/jaunty/beta . Please let us know.

Hi
I have Linux Mint Felicia (AMD 64 with 32 bit) on one box and Hardy (AMD 64) on another. Hardy seems to behave really well but both Intrepid and Felicia have started kernel panics which affect my KVM (Edimax EK-UAK44). I bought the new KVM as it sends constant signals to each PC whether in use or not - sorry - forgot the term)

When I switch the PCs on in the "wrong" order, I get a kernel panic on both PCs and the KVM cannot be reset. The problem seems to always start with Mint 6 and before that, with Intrepid.

I am going to try jaunty soon so I am hoping that this can be fixed

Many thanks

Should have posted this a while ago sorry, but ...

I started having more serious mouse problems so I bought a usb-PS2 adapter. Since then I have seen no more problems. I deuce from this that the problem is either hardware or software related around the PS2 port. Given that no-one else seems to see this, I'd guess hardware.

I don't think this issue is worth any more of your or my time so, unless anyone else disagrees, Isuggest that this can be closed.

Thanks for your efforts.

George - closing based on your feedback.