From: bert hubert <ahu@ds9a.nl>
To: petero2@telia.com
Cc: linux-kernel@vger.kernel.org
Subject: Synaptics trouble in 2.5.73
Date: Wed, 2 Jul 2003 20:54:12 +0200 [thread overview]
Message-ID: <20030702185412.GA24350@outpost.ds9a.nl> (raw)
Petero, List,
Up to 2.5.68 my laptop had no problems with its touchpad but since upgrading
to 2.5.73, neither gpm nor X see my mouse anymore.
>From dmesg:
Jul 2 20:17:38 snapcount kernel: mice: PS/2 mouse device common for all mice
Jul 2 20:17:38 snapcount kernel: inport.c: Didn't find InPort mouse at 0x23c
Jul 2 20:17:38 snapcount kernel: logibm.c: Didn't find Logitech busmouse at 0x23c
Jul 2 20:17:38 snapcount kernel: pc110pad: I/O area 0x15e0-0x15e4 in use.
Jul 2 20:17:38 snapcount kernel: input: PC Speaker
Jul 2 20:17:38 snapcount kernel: i8042.c: Detected active multiplexing controller, rev 1.0.
Jul 2 20:17:38 snapcount kernel: serio: i8042 AUX0 port at 0x60,0x64 irq 12
Jul 2 20:17:38 snapcount kernel: Synaptics Touchpad, model: 1
Jul 2 20:17:38 snapcount kernel: Firware: 4.1
Jul 2 20:17:38 snapcount kernel: Sensor: 8
Jul 2 20:17:38 snapcount kernel: new absolute packet format
Jul 2 20:17:38 snapcount kernel: input: Synaptics Synaptics TouchPad on isa0060/serio2
Later on, I get this:
Synaptics driver lost sync at 1st byte
Synaptics driver lost sync at 4th byte
Synaptics driver resynced.
But the mouse still does not work. This is a 'Gericom' laptop, which
contains mostly SiS parts. Anything I can do to help debug this, just let me
know.
I saw mention of special X drivers for this, but the kernel messages appear
to indicate that the kernel itself is not succeeding in communicating with
the touchpad.
Thanks!
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next reply other threads:[~2003-07-02 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 18:54 bert hubert [this message]
2003-07-03 10:42 ` Peter Osterlund
2003-07-03 15:09 ` Niels den Otter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030702185412.GA24350@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®