Hi,
On Sun, 24 Jul 2005 13:23:14 +0200
smoke3 <[EMAIL PROTECTED]> wrote:
> It's OK: I had winzoz installed from the seller i bought it from and
> the mouse did function as well!
Hm, OK, it definately _is_ a driver issue then...
> > * the right PS/2 plug (not that keyboard one...)
> nice joke, but... no!
Well, seen it before, and I thought to mention it doesn't harm... :-)
> "dmesg | grep PS/2" -->
> "PNP: PS/2 Controller... irq 1,12
> mice: PS/2 mouse device common for all mice
> input ImExPS/2 Generic Explorer Mouse on isa0060/serio1"
Hm, OK. So it _is_ recognized then... Maybe the kernel choses a level
that's too high. From kernel docs (kernel-parameters.txt):
----snip----
psmouse.proto= [HW,MOUSE] Highest PS2 mouse protocol extension to
probe for (bare|imps|exps).
psmouse.rate= [HW,MOUSE] Set desired mouse report rate, in reports
per second.
psmouse.resetafter=
[HW,MOUSE] Try to reset the device after so many bad
packets
(0 = never).
----snip----
So I'd try to begin with the proto setting. Note that this only applies
if the driver actually is compiled into the kernel instead of being a
module. In the latter case, you'd need to edit the module parameters.
On the grub kernel line (or LILO's parameter line, respectively),
append something like:
psmouse.proto=imps
And see what happens. Try with the other values (exps, bare), too. Of
course, this will need a reboot after modifiing the kernel command line.
As a side note, my dmesg reads:
Jul 2 12:59:52 sub00421 input: ImPS/2 Generic Wheel Mouse on isa0060/serio1
Last question: Does this mouse work for any (other) linux box? What
does the dmesg read there?
-hwh
--
[email protected] mailing list
