From: safemode <safemode@voicenet.com>
To: Adrian Cox <apc@agelectronics.co.uk>
Cc: Dylan Griffiths <Dylan_G@bigfoot.com>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: More on the VIA KT133 chipset misbehaving in Linux
Date: Mon, 29 Jan 2001 06:30:55 -0500 [thread overview]
Message-ID: <3A75546F.DAC87368@voicenet.com> (raw)
In-Reply-To: <3A75278F.B41B492B@bigfoot.com> <3A75507A.9386AFE2@agelectronics.co.uk>
Adrian Cox wrote:
> Dylan Griffiths wrote:
> > The VIA KT133 chipset exhibits the following bugs under Linux 2.2.17 and
> > 2.4.0:
> > 1) PS/2 mouse cursor randomly jumps to upper right hand corner of screen and
> > locks for a bit
>
> This happens to me about once a month on a BX chipset PII machine here,
> and on a KT133 chipset machine I have. I have to hit ctrl-alt-backspace
> to regain control of the console. I always assumed it was a bug in X,
> but it never caused me enough trouble to actually make me pursue it.
>
> - Adrian
>
turn off gpm.. fixes the mouse problem immediately. as in killall -9 gpm
before starting X.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-29 11:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 8:19 More on the VIA KT133 chipset misbehaving in Linux Dylan Griffiths
2001-01-29 11:14 ` Adrian Cox
2001-01-29 11:30 ` safemode [this message]
2001-01-29 11:40 ` Adrian Cox
2001-01-29 11:48 ` Lars Gaarden
2001-01-30 1:02 ` Matthew Fredrickson
2001-01-29 16:01 ` Benson Chow
2001-02-02 14:55 ` Rogerio Brito
-- strict thread matches above, loose matches on Subject: below --
2001-01-29 9:20 Quim K Holland
2001-01-29 10:20 ` David Raufeisen
2001-01-29 14:14 ` Mark Hahn
[not found] <Pine.LNX.4.10.10101290853030.26212-100000@coffee.psychology.mcmaster.ca>
2001-01-29 18:36 ` Dylan Griffiths
2001-02-02 16:30 Dunlap, Randy
2001-02-05 3:00 ` Rogerio Brito
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=3A75546F.DAC87368@voicenet.com \
--to=safemode@voicenet.com \
--cc=Dylan_G@bigfoot.com \
--cc=apc@agelectronics.co.uk \
--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