Re: trackpad not working after dist-upgrade to sarge unstable
Sorry for the dups. I am having trouble with gmail.
My sincere thanks to Florian and jlbelmonte . I did what both of you
suggested. I did add the modules and change the path in XF86Config to
/dev/input/mice after testing the device with hd as Florian suggested.
Now it works and I am a happy camper. Thanks again.
Just a side note. I am amazed how well Sarge unstable runs on this
machine which was made in 1997 and has a PentiumII with 384MB of RAM.
It still boots relatively fast and and for most development work
(emacs, ruby, rails) it is fast enough.
-bakki
PS: From gmail the std reply button does not send the reply to the
list! I had to copy it in manually. I have not had this happen in
other lists. Does this list not have a reply to set to the list?
On 3/31/06, Florian Kulzer <florian@molphys.leidenuniv.nl> wrote:
> Bakki Kudva wrote:
> > Hi,
> >
> > I have a Gateway Solo 9150 which I have used for Debian since 1997 and
> > had no dist-upgrade problems till now.
> >
> > IT appears that unstable with 2.4 and 2.6 kernels are both not setting
> > up the trackpad correctly to /dev/psaux. So X does not load.
> >
> > dmesg shows that it is detected and is called something like
> > serio: i8042 AUX port at 0x60,0x64 irq 12
> > serio: i8042 KBD port at 0x60,0x64 irq 1
> > input: Logitech Mouse on isa0060/serio1
> >
> > If I change /dev/psaux in XF86Config to /dev/ttyS1, X loads fine but
> > the mouse is still inoperative. I don't see a /dev/mouse
>
> It might be in the /dev/input directory, for example /dev/input/mice. A
> quick way to try it is to become root and run
>
> cat /dev/input/mice | hd
>
> or
>
> cat /dev/input/mouse0 | hd
>
> etc.
>
> If you find the right device you should see output scrolling by as soon
> as you do something with the trackpad. (CTRL-C to quit this.)
>
> Regards,
> Florian
>
>
> --
> To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
Reply to: