mouse crazy in ubuntu 7.04

[danrevella]

both using live version or installing via alternate disk, my mouse "Microsoft mouse ps/2" does not work: it is too much fast and become crazy at all.....
I have try using the slide to slow down it, but even at minimum it move too much fast.
In this situation I'm totally unable even in editing some configuration files....
Under ubuntu 6.10 all was ok
Mouse is a Logitech trackman whell, but even connecting other mouse on ps/2 port the problem is always the same....
Under windowz all mouse work good....
My computer is Intel xeon 3.00 ghz 2 gb ram
Thanks!!!

[Diogo Matsubara (matsubara)]

Thank you for the report, but this is not a launchpad bug, re-assigning to Ubuntu.
We're interested in why you accidentally recorded this bug as occurring in malone instead of Ubuntu. If you can explain what happened, please let us know in bug 88818.

[Brian Murray (brian-murray)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

[danrevella (darthmaurizio)]

Hi!!
I understand english only about 15%..... :-(
I had the problem i described as bug, I believe that malone was the right
way to signal the bug, please excuse me.....
BTW, where have I to go to signal the bug, please may you be so kind in tell
me exactelly where have I to go and signal.
Please excuse for my ignorance and for not be able in understanding enough
english.

Many thanks.

Maurizio from Italy
----- Original Message -----
From: "Diogo Matsubara" <email address hidden>
To: <email address hidden>
Sent: Monday, April 23, 2007 6:50 PM
Subject: [Bug 109326] Re: mouse crazy in ubuntu 7.04

Thank you for the report, but this is not a launchpad bug, re-assigning to
Ubuntu.
We're interested in why you accidentally recorded this bug as occurring in
malone instead of Ubuntu. If you can explain what happened, please let us
know in bug 88818.

** Changed in: malone (upstream)
       Status: Unconfirmed => Rejected

** Also affects: Ubuntu
   Importance: Undecided
       Status: Unconfirmed

--
mouse crazy in ubuntu 7.04
https://bugs.launchpad.net/bugs/109326
You received this bug notification because you are a direct subscriber
of the bug.

[danrevella (darthmaurizio)]

Here I enclosed the info you requested...
----- Original Message -----
From: "Brian Murray" <email address hidden>
To: <email address hidden>
Sent: Tuesday, April 24, 2007 12:30 AM
Subject: [Bug 109326] Re: mouse crazy in ubuntu 7.04

Thanks for taking the time to report this bug and helping to make Ubuntu
better. Unfortunately we can't fix it, because your description doesn't yet
have enough information.
Please include the following additional information, if you have not already
done so (please pay attention to lspci's additional options), as required by
the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next
response. It should be one, long line of text which includes the exact
kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file
'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the
resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related
bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies .
Thanks in advance!

** Changed in: linux-source-2.6.20 (Ubuntu)
Sourcepackagename: None => linux-source-2.6.20
     Assignee: (unassigned) => Brian Murray
       Status: Unconfirmed => Needs Info

--
mouse crazy in ubuntu 7.04
https://bugs.launchpad.net/bugs/109326
You received this bug notification because you are a direct subscriber
of the bug.

[danrevella (darthmaurizio)]

here is my attachment files as you requested....

[danrevella (darthmaurizio)]

it seems to be that even an old serial mouse does NOT works!!!
I have sent the report you have ask me for.....

[Brian Murray (brian-murray)]

From dmesg:

psmouse.c: Failed to reset mouse on isa0060/serio1

[Ai1dRo0kNotBot (last-fr)]

The same thing on IBM ThinkPad R31 when using TrackPoint.

The issue: on any continious mouse move, or rapidly repeated mouse button press mouse jumps to rnadom screen edge, and makes random clicks.

Dmesg report on error:
[ 3014.824000] psmouse.c: TrackPoint at isa0060/serio4/input0 lost synchronization, throwing 2 bytes away.
[ 3022.808000] psmouse.c: TrackPoint at isa0060/serio4/input0 lost synchronization, throwing 2 bytes away.
[ 3158.128000] psmouse.c: TrackPoint at isa0060/serio4/input0 lost synchronization, throwing 2 bytes away.
One line each time the mouse goes crzay.

Notice: The mouse works fine till the desktop gets loaded i.e. it never jumps at logon screen, but does so on Gnome, XFCE, and fvwm-crystal window managers.

USB mouse (A4Tech WOP-35PU) works fine.

Add-on: Here are some dmesg complaints that may somehow affect mouse (or not).
[ 13.927370] Local APIC disabled by BIOS -- you can enable it with "lapic"
...
[ 14.626880] ACPI: Looking for DSDT in initramfs... file /DSDT.aml not found, using machine DSDT.
...
[ 14.647873] PCI: Transparent bridge - 0000:00:1e.0
[ 14.647947] PCI: Bus #02 (-#05) is hidden behind transparent bridge #01 (-#01) (try 'pci=assign-busses')
[ 14.647953] Please report the result to linux-kernel to fix this permanently
[ 14.647980] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 14.654530] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
...
[ 14.715722] PnPBIOS: Disabled by ACPI PNP
[ 14.715836] PCI: Using ACPI for IRQ routing
[ 14.715843] PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
...
[ 16.321903] mice: PS/2 mouse device common for all mice
...
[ 16.323615] input: Macintosh mouse button emulation as /class/input/input0
... (!!!)
[ 16.324024] PNP: PS/2 Controller [PNP0f13:PS2M] at 0x0,0x0 irq 12
[ 16.324031] PNP: PS/2 controller has invalid data port 0x0; using default 0x60
[ 16.324036] PNP: PS/2 controller has invalid command port 0x0; using default 0x64
[ 16.324041] PNP: PS/2 controller doesn't have KBD irq; using default 1
... (!!!)
[ 27.472000] IBM TrackPoint firmware: 0x0e, buttons: 3/3
[ 27.492000] input: TPPS/2 IBM TrackPoint as /class/input/input3

[Andres Mujica (andres.mujica)]

marked as duplicate of bug #119194 for lost synchronization error

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Launchpad Janitor (janitor)]

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.