All of lore.kernel.org
 help / color / mirror / Atom feed
From: tabris <tabris@tabris.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: console/gpm mouse breakage 2.6.3-rc1-mm1
Date: Tue, 10 Feb 2004 23:50:54 -0500	[thread overview]
Message-ID: <200402110024.00792.tabris@tabris.net> (raw)
In-Reply-To: <20040210201102.GB261@ucw.cz>

[-- Attachment #1: clearsigned data --]
[-- Type: Text/Plain, Size: 1734 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 10 February 2004 3:11 pm, Vojtech Pavlik wrote:
> On Tue, Feb 10, 2004 at 06:05:19AM -0500, tabris wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > 	just went to 2.6.3 this morning due to frustrations with my PDC20265
> > causing lockups... hoping that 2.6 solves this problem...
> >
> > 	and now i'm having trouble where gpm doesn't work right... cilcks don't
> > register as a click event. Yes, it works fine in X (using GPM in repeater
> > mode, -R raw. the old hack I used to allow X to use both mice, as well as
> > eliminating the gpm crashes every couple times I switched btwn X and
> > console mode.)
> >
> > instead I get characters echoed to my terminal
> > left click: Q
> > right click: W
> > middle click: E (plus some control character... i haven't tried a capture
> > and hexdump yet)
> >
> > 	also, my PS/2 mouse (MS IMPS/2) no longer works. from any /dev node I've
> > tried.
>
> This is very interesting. Can you post your /proc/bus/input/devices and
> dmesg?

ok. updated... i rebuilt it, and made psmouse a module. mouse now is working 
with gpm. (tracking feels funny tho)

also, it does NOT have the issue with the odd console echo. but my 
USB/wireless mouse still has that problem.

- -- 
Sharks are as tough as those football fans who take their shirts off
during games in Chicago in January, only more intelligent.
		-- Dave Barry, "Sex and the Single Amoeba: What Every
		   Teen Should Know"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAKbS31U5ZaPMbKQcRAh/4AJ4thxf+ccp60OsGcwtJq0NomoNvKgCeM0Wv
rg9bl/9F71NnIYqvX09tkJk=
=HQHn
-----END PGP SIGNATURE-----

[-- Attachment #2: devices --]
[-- Type: application/x-zerosize, Size: 964 bytes --]

  parent reply	other threads:[~2004-02-11  5:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-10 11:05 console/gpm mouse breakage 2.6.3-rc1-mm1 tabris
2004-02-10 11:06 ` tabris
2004-02-10 20:11 ` Vojtech Pavlik
2004-02-10 21:36   ` tabris
2004-02-11  4:50   ` tabris [this message]
2004-02-11  7:53     ` tabris

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=200402110024.00792.tabris@tabris.net \
    --to=tabris@tabris.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.