From: Danijel Schiavuzzi <dschiavu@public.srce.hr>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, srwalter@yahoo.com (Steven Walter),
ozone@algorithm.com.au (Andre Pang),
Tom Eastep <teastep@shorewall.net>, Tom Brehm <BrehmTomB@aol.com>
Subject: Re: Screen corruption in 2.4.18
Date: Sun, 24 Mar 2002 18:13:13 +0100 [thread overview]
Message-ID: <200203241713.SAA20705@jagor.srce.hr> (raw)
In-Reply-To: <E16pBDX-0006fl-00@the-village.bc.nu>
On Sunday 24 March 2002 17:51, you wrote:
> > > same screen corruption. Clearing only bit 7 of register 55 fixes
> >
> > Well, we're not the only ones with this problem. BTW, which motherboard
> > do you have? Maybe it's a mainboard failure (mine is a MSI MS-6340M V1).
> > I know one more Linux user with this problem on the same M/B.
>
> Does everyone who sees this problem have the 8363/5 combination with the
> onboard Pro-Savage
>
> Alan
Hi,
AFAIK, these people are having these problems and using VT8365 (KM133)
(ProSavage graphics is integrated in this northbridge):
me <dschiavu@jagor.srce.hr>
Tom Brehm <BrehmTomB@aol.com>
Andre Pang <ozone@algorithm.com.au>
Steven Walter <srwalter@yahoo.com>
Tom Eastep <teastep@shorewall.net>
Regards,
Danijel
next prev parent reply other threads:[~2002-03-24 17:13 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
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
[not found] ` <200203231741.SAA00071@jagor.srce.hr>
2002-03-23 18:26 ` VIA technical contact [was Screen corruption in 2.4.18] Steven Walter
2002-03-24 7:05 ` Screen corruption in 2.4.18 Andre Pang
2002-03-24 7:16 ` [PATCH] " Steven Walter
[not found] ` <200203241231.g2OCV5X18426@Port.imtp.ilyichevsk.odessa.ua>
2002-03-24 15:59 ` Steven Walter
2002-03-24 16:48 ` Alan Cox
2002-03-24 18:03 ` Steven Walter
2002-03-25 2:01 ` Andre Pang
2002-03-24 15:07 ` Danijel Schiavuzzi
2002-03-24 16:51 ` Alan Cox
2002-03-24 17:13 ` Danijel Schiavuzzi [this message]
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
2002-03-25 17:59 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-29 12:26 Petr Vandrovec
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-04-02 22:50 Petr Vandrovec
2002-04-02 22:09 ` Chris Rankin
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=200203241713.SAA20705@jagor.srce.hr \
--to=dschiavu@public.srce.hr \
--cc=BrehmTomB@aol.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=ozone@algorithm.com.au \
--cc=srwalter@yahoo.com \
--cc=teastep@shorewall.net \
/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
all inboxes | Powered by JetHome®