From: Andre Pang <ozone@algorithm.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: Screen corruption in 2.4.18
Date: Fri, 29 Mar 2002 13:05:04 +1100 [thread overview]
Message-ID: <1017367504.319988.13334.nullmailer@bozar.algorithm.com.au> (raw)
In-Reply-To: <Pine.LNX.4.33.0203281443500.17304-100000@whisper.jaggnet.org> <200203282315.AAA02844@jagor.srce.hr>
On Fri, Mar 29, 2002 at 01:14:47AM +0100, Danijel Schiavuzzi wrote:
> > 00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev
> > 81) 00:01.0
>
> It's interesting that everyone who is experiencing these problems has the
> *revision 81* of the VT8365 chipset! This should be the key...
You know, we might be barking down the wrong tree. (Arf.)
So far, everybody who has reported video corruption seems to have
a Savage or ProSavage video card. Maybe it'd be a better idea to
look at the ProSavage data sheets and see if we should be
tweaking something there? That would be much safer than playing
around with the northbridges.
--
#ozone/algorithm <ozone@algorithm.com.au> - trust.in.love.to.save
next prev parent reply other threads:[~2002-03-29 2:06 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-28 22:46 Screen corruption in 2.4.18 Bill Hammock
2002-03-29 0:14 ` Danijel Schiavuzzi
2002-03-29 2:05 ` Andre Pang [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-02 22:50 Petr Vandrovec
2002-04-02 22:09 ` Chris Rankin
2002-04-02 21:43 Chris Rankin
2002-04-02 22:33 ` 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
2002-03-29 12:26 Petr Vandrovec
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=1017367504.319988.13334.nullmailer@bozar.algorithm.com.au \
--to=ozone@algorithm.com.au \
--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