public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Rankin <rankincj@yahoo.com>
To: VANDROVE@vc.cvut.cz
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Screen corruption in 2.4.18
Date: Tue, 02 Apr 2002 22:43:03 +0100	[thread overview]
Message-ID: <3CAA25E7.2060405@yahoo.com> (raw)

Hi,

I have an i840 motherboard with dual 733 MHz PIIIs and a Matrox G400 
MAX, and I am also seeing console corruption with 2.4.18. The difference 
with me is that I *only* see it when I am using xine (CVS) and the 
SyncFB video plugin, possibly the Xv video plugin sometimes too. When I 
kill xine, the regular multicoloured rectangle disappears from the console.

Obviously, this isn't something that I would normally notice - I 
wouldn't have noticed at all if the CVS xine hadn't locked up on me in 
full-screen mode, forcing me to turn to a console to kill it.

A few other things:
- since I have about 1.25 GB of RAM, I have enabled a 256 MB AGP aperture.
- I am using XFree86 4.2, but with the mga.o module that is native to 
Linux 2.4.18. I have not installed the Matrox HAL X module.

Whatever is causing this console corruption, it doesn't seem to be a VIA 
bug (in my case, anyway).

Chris


             reply	other threads:[~2002-04-02 21:43 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-02 21:43 Chris Rankin [this message]
2002-04-02 22:33 ` Screen corruption in 2.4.18 Richard B. Johnson
2002-04-02 22:40   ` Chris Rankin
2002-04-03 14:00     ` Richard B. Johnson
2002-04-03 20:34       ` Chris Rankin
2002-04-02 23:38 ` Erik Ljungström
  -- strict thread matches above, loose matches on Subject: below --
2002-04-02 22:50 Petr Vandrovec
2002-04-02 22:09 ` Chris Rankin
2002-03-29 12:26 Petr Vandrovec
2002-03-28 22:46 Bill Hammock
2002-03-29  0:14 ` Danijel Schiavuzzi
2002-03-29  2:05   ` Andre Pang
2002-03-25 17:59 Petr Vandrovec
2002-03-19 21:12 Danijel Schiavuzzi
2002-03-20  0:03 ` Steven Walter
     [not found] ` <200203201506.QAA13795@jagor.srce.hr>
     [not found]   ` <20020320172516.GA14024@hapablap.dyn.dhs.org>
     [not found]     ` <200203211209.NAA11121@jagor.srce.hr>
2002-03-21 17:22       ` Steven Walter
     [not found]         ` <200203222204.XAA01121@jagor.srce.hr>
2002-03-22 23:23           ` Steven Walter
     [not found]             ` <200203231526.QAA09302@jagor.srce.hr>
2002-03-23 16:06               ` Steven Walter
2002-03-24  7:05                 ` Andre Pang
2002-03-24 15:07                   ` Danijel Schiavuzzi
2002-03-24 16:51                     ` Alan Cox
2002-03-24 17:13                       ` Danijel Schiavuzzi
2002-03-25  1:43                     ` Andre Pang
2002-03-25  2:40                       ` Steven Walter
2002-03-25  3:00                         ` Andre Pang
2002-03-25  8:50                       ` Marc Wilson
2002-03-25 17:07                         ` Daniel Gryniewicz
2002-03-25 21:02                         ` Steven Walter
2002-03-25 21:19                           ` Marc Wilson
2002-03-29  2:06                         ` Andre Pang
2002-03-29  3:16                           ` Marc Wilson
2002-03-25  1:55                     ` Andre Pang
2002-03-25 19:52                       ` Danijel Schiavuzzi

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=3CAA25E7.2060405@yahoo.com \
    --to=rankincj@yahoo.com \
    --cc=VANDROVE@vc.cvut.cz \
    --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