public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: tabris <tabris@tabris.net>
To: linux-kernel@vger.kernel.org
Subject: console/gpm mouse breakage 2.6.3-rc1-mm1
Date: Tue, 10 Feb 2004 06:05:19 -0500	[thread overview]
Message-ID: <200402100605.25115.tabris@tabris.net> (raw)

-----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.

	I do most of my work in console mode, and having no console mouse for pastes 
and such is a pain.

	This is probably some old issue hashed and rehashed, but after reading the 
LKML pretty much all the time for the last couple years, I don't remember 
this problem being mentioned.

	as another problem, tho I believe this is also well known, sensors don't 
work, as i2c-proc doesn't exist anymore and there are no /proc/ entries for 
sensors.

- --
tabris
- -
In 1869 the waffle iron was invented for people who had wrinkled waffles.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAKLry1U5ZaPMbKQcRAhg3AJ9QWqwWEaBVXBlbdOqrEg3Kd31OhwCdFFey
pS/v2GtN2n/g5aQbjyOKN/4=
=iz7k
-----END PGP SIGNATURE-----


             reply	other threads:[~2004-02-10 11:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-10 11:05 tabris [this message]
2004-02-10 11:06 ` console/gpm mouse breakage 2.6.3-rc1-mm1 tabris
2004-02-10 20:11 ` Vojtech Pavlik
2004-02-10 21:36   ` tabris
2004-02-11  4:50   ` tabris
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=200402100605.25115.tabris@tabris.net \
    --to=tabris@tabris.net \
    --cc=linux-kernel@vger.kernel.org \
    /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