Hey everyone...this is my first posting here, and I may not be going about
this the right way so please forgive me if I am not. I had a question
regarding the status of the code for the ImExPS/2 style mice.
I currently have a Nexxtech NXX200 PS/2 Optical Wheel Mouse, running kernel
2.6.13.4. I noticed that prior to the 2.6.x.x series (whilst in the 2.4.x.x
series (I was stubborn)), that my mouse was working fine.
Now, however,if I plug my mouse in, the optical light comes on for perhaps
half a second, and the mouse goes dark. The second thing that happens is if
you click either button, or move/click the scrollwheel, the cursor will go to
the upper right hand corner of the screen to where you only see a small
fraction of it. This happens in both console mode and in graphical.
I have included the results from what dmesg displayed when I connected the
mouse to the computer, as well as some of the output from /var/log/messages:
input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1
Oct 18 06:47:25 scooby gpm[18741]: Started gpm successfully. Entered daemon
mode.
Oct 18 06:48:46 scooby kernel: psmouse.c: bad data from KBC - timeout
Oct 18 06:48:47 scooby hal.hotplug[22794]: DEVPATH is not set
Oct 18 06:48:47 scooby hal.hotplug[22836]: DEVPATH is not set
Oct 18 06:48:47 scooby kernel: input: PS/2 Generic Mouse on isa0060/serio1
Oct 18 06:52:54 scooby hal.hotplug[2047]: DEVPATH is not set
Oct 18 06:52:55 scooby hal.hotplug[2133]: DEVPATH is not set
Oct 18 06:52:55 scooby kernel: input: ImExPS/2 Generic Explorer Mouse on
isa0060/serio1
Oct 18 06:54:28 scooby hal.hotplug[5846]: DEVPATH is not set
Oct 18 06:54:28 scooby hal.hotplug[5884]: DEVPATH is not set
Oct 18 06:54:29 scooby kernel: input: PS/2 Generic Mouse on isa0060/serio1
Is this something that is being addressed in the 2.6.14 kernel? Or is there
perhaps currently a patch available so that I can use my mouse? I would
really not have to go by another one if I can help it.
Thanks in advance,
James
James E. Jennison wrote:
> Hey everyone...this is my first posting here, and I may not be going about
> this the right way so please forgive me if I am not. I had a question
> regarding the status of the code for the ImExPS/2 style mice.
>
> I currently have a Nexxtech NXX200 PS/2 Optical Wheel Mouse, running kernel
> 2.6.13.4. I noticed that prior to the 2.6.x.x series (whilst in the 2.4.x.x
> series (I was stubborn)), that my mouse was working fine.
>
> Now, however,if I plug my mouse in, the optical light comes on for perhaps
> half a second, and the mouse goes dark. The second thing that happens is if
> you click either button, or move/click the scrollwheel, the cursor will go to
> the upper right hand corner of the screen to where you only see a small
> fraction of it. This happens in both console mode and in graphical.
Does this also happen if the mouse is plugged in when powering up the
machine? PS/2 devices are not really designed to be hot-plugged.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/
Robert:
Yes, it does. I have also tried manually specifying the mouse protocol to
use, and that does not seem to help either. Let me know if I can give you
any other information.
-James
On Tuesday 18 October 2005 20:52, you wrote:
> James E. Jennison wrote:
> > Hey everyone...this is my first posting here, and I may not be going
> > about this the right way so please forgive me if I am not. I had a
> > question regarding the status of the code for the ImExPS/2 style mice.
> >
> > I currently have a Nexxtech NXX200 PS/2 Optical Wheel Mouse, running
> > kernel 2.6.13.4. I noticed that prior to the 2.6.x.x series (whilst in
> > the 2.4.x.x series (I was stubborn)), that my mouse was working fine.
> >
> > Now, however,if I plug my mouse in, the optical light comes on for
> > perhaps half a second, and the mouse goes dark. The second thing that
> > happens is if you click either button, or move/click the scrollwheel, the
> > cursor will go to the upper right hand corner of the screen to where you
> > only see a small fraction of it. This happens in both console mode and
> > in graphical.
>
> Does this also happen if the mouse is plugged in when powering up the
> machine? PS/2 devices are not really designed to be hot-plugged.
On Tuesday 18 October 2005 19:11, James E. Jennison wrote:
> Hey everyone...this is my first posting here, and I may not be going about
> this the right way so please forgive me if I am not. I had a question
> regarding the status of the code for the ImExPS/2 style mice.
>
> I currently have a Nexxtech NXX200 PS/2 Optical Wheel Mouse, running kernel
> 2.6.13.4. I noticed that prior to the 2.6.x.x series (whilst in the 2.4.x.x
> series (I was stubborn)), that my mouse was working fine.
>
> Now, however,if I plug my mouse in, the optical light comes on for perhaps
> half a second, and the mouse goes dark. The second thing that happens is if
> you click either button, or move/click the scrollwheel, the cursor will go to
> the upper right hand corner of the screen to where you only see a small
> fraction of it. This happens in both console mode and in graphical.
>
> I have included the results from what dmesg displayed when I connected the
> mouse to the computer, as well as some of the output from /var/log/messages:
>
> input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1
>
> Oct 18 06:47:25 scooby gpm[18741]: Started gpm successfully. Entered daemon
> mode.
> Oct 18 06:48:46 scooby kernel: psmouse.c: bad data from KBC - timeout
> Oct 18 06:48:47 scooby hal.hotplug[22794]: DEVPATH is not set
> Oct 18 06:48:47 scooby hal.hotplug[22836]: DEVPATH is not set
> Oct 18 06:48:47 scooby kernel: input: PS/2 Generic Mouse on isa0060/serio1
So you start without a mouse plugged in and still it detects a mouse?
> Oct 18 06:52:54 scooby hal.hotplug[2047]: DEVPATH is not set
> Oct 18 06:52:55 scooby hal.hotplug[2133]: DEVPATH is not set
> Oct 18 06:52:55 scooby kernel: input: ImExPS/2 Generic Explorer Mouse on
> isa0060/serio1
And here you plug the mouse, right?
> Oct 18 06:54:28 scooby hal.hotplug[5846]: DEVPATH is not set
> Oct 18 06:54:28 scooby hal.hotplug[5884]: DEVPATH is not set
> Oct 18 06:54:29 scooby kernel: input: PS/2 Generic Mouse on isa0060/serio1
>
--
Dmitry
On Tuesday 18 October 2005 22:30, you wrote:
<Cut to save space and not be so long>
...
...
...
> > I have included the results from what dmesg displayed when I connected
> > the mouse to the computer, as well as some of the output from
> > /var/log/messages:
> >
> > input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1
> >
> > Oct 18 06:47:25 scooby gpm[18741]: Started gpm successfully. Entered
> > daemon mode.
> > Oct 18 06:48:46 scooby kernel: psmouse.c: bad data from KBC - timeout
> > Oct 18 06:48:47 scooby hal.hotplug[22794]: DEVPATH is not set
> > Oct 18 06:48:47 scooby hal.hotplug[22836]: DEVPATH is not set
> > Oct 18 06:48:47 scooby kernel: input: PS/2 Generic Mouse on
> > isa0060/serio1
>
> So you start without a mouse plugged in and still it detects a mouse?
No, in both instances, the mouse was already plugged in.
> > Oct 18 06:52:54 scooby hal.hotplug[2047]: DEVPATH is not set
> > Oct 18 06:52:55 scooby hal.hotplug[2133]: DEVPATH is not set
> > Oct 18 06:52:55 scooby kernel: input: ImExPS/2 Generic Explorer Mouse on
> > isa0060/serio1
>
> And here you plug the mouse, right?
>
> > Oct 18 06:54:28 scooby hal.hotplug[5846]: DEVPATH is not set
> > Oct 18 06:54:28 scooby hal.hotplug[5884]: DEVPATH is not set
> > Oct 18 06:54:29 scooby kernel: input: PS/2 Generic Mouse on
> > isa0060/serio1