Re: mouse unresponsive after FC3 upgrade to laptop [solved!]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Bob Marcum wrote:
>
> > Gentlemen:
> >
> > As best I can tell the mouse and the touchpad drivers are receiving
> > input from the same interrupts.  When I get to a command prompt via
> > alt-F2 then move the mouse, I see repeated messages that the touchpad
> > has lost sync as the mouse is moved.  How can I re-configure this, or
> > how can I further diagnose this problem?
> >
> > I have just joined this mail list and it looks like the right place to
> > get counsel on this kind of problem.  Perhaps this problem has already
> > been encountered and resolved.  If anybody knows elsewhere I should
> > check, I will be grateful for the guidance.
> >
> > Thnaks.
> >
> > I upgraded FC3 over Redhat 7.1.
> >
>

Dmitry Torokhov wrote:

> Is that a Dell?

No, Dmitry, this is an HP Omnibook 6000.

>
>
> 1. Try booting with psmouse.proto=exps
> 2. Invest in an USB mouse
>
> --
> Dmitry

and
John Summerfield wrote:

I have seen people mention this kind of problem on Ubuntu Linux - also
kernel
2.6.

Apprently on 2.6 both PS/2 and USB mice appear at /dev/input/mice. I myself

has used two USB mice with no problems.

No, I don't know what the resolution is, but some googling may help.

=================================================

Based on these clues I did checkout the 2.6 kernel forum archives and found
this is a known problem.  The culprit seems to be the synaptics touchpad.
Its driver doesn't pay nice with code that is in kernel 2.6.

I was able to solve the problem by appending the kernel option,
"psmouse.proto=imps".  Seems to work fine now.

I found I could check out this option by catching the system at boot time.
Press any key before the delay time expires.  That allows a choice of
several options, one of which is 'a' (as in "append") which then allows me
to specify that kernel boot option just for this boot instance.  Once I was
able to sort out that solved my problem, I edited /etc/grub.conf and added
the option to the kernel boot line ... to make that option effective for
every boot.

By the way, the Synaptics touchpad does still work okay.

Thank you, gentlemen - one and all - for your good counsel!


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux