public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Danijel Schiavuzzi <dschiavu@public.srce.hr>
To: linux-kernel@vger.kernel.org
Cc: Steven Walter <srwalter@yahoo.com>, Andre Pang <ozone@algorithm.com.au>
Subject: Re: Screen corruption in 2.4.18
Date: Sun, 24 Mar 2002 16:07:31 +0100	[thread overview]
Message-ID: <200203241507.g2OF7WN26069@ls401.hinet.hr> (raw)
In-Reply-To: <200203192112.WAA09721@jagor.srce.hr> <20020323160647.GA22958@hapablap.dyn.dhs.org> <1016953516.189201.5912.nullmailer@bozar.algorithm.com.au>

On Sunday 24 March 2002 08:05, you wrote:
> On Sat, Mar 23, 2002 at 10:06:47AM -0600, Steven Walter wrote:
> > > Don't get it wrong. I *do have* an VT8365. VT8365 (ProSavage KM133) is
> > > somewhat the same as VT8363 (KT133), except that 8365 has an integrated
> > > Savage graphics card (which *I use*).
> >
> > Aha... I see.  And in thinking about it, I realize that my motherboard
> > also has this integrated graphics card.  Perhaps this is the difference?
> > Unfortunately, it seems they both report the same PCI id, so I don't
> > really know of a way to differentiate them.
>
> I can verify Danijel's report -- I have the same setup
> (VT8363+VT8353, a.k.a. ProSavage KM133), and I experience the

Actually the *northbridge is VT8365* (ProSavage KM133), while it can be 
combined with other southbridges like VIA VT86c686A or VT86c686B (I'm using 
the B one.) VT8363 (KT133) is a similar chipset to KM133, and the only 
difference should be the integrated Savage graphics card in KM133.

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

> the problem; clearing bits 5 and 6 causes the video to go all
> borky.  There's been another thread about it on lkml over the
> last week or so.
>
> > I looked at that datasheet, and the datasheet for the 8363.  Both said
> > not to program offset 55, and both said the bits we are clearing are
> > "reserved."  Perhaps we should contact VIA directly, tell them the
> > problem we're having with their current fix, tell them our theory, and
> > ask if we're right.
>
> Heh, a VIA contact who knows what the hell that register does
> would be nice :).
>
> In the meantime, I'd probably suggest a patch which looks for
> clears only bit 7 of Rx55 if an 8363 and an 8365 is found.  I'll
> whip one up later today.

Yes, should implement some autodetection to detect VT8365 and clear only bit 
7 and include it in the kernel *as soon as possible* (I don't have any kernel 
programming experience, so don't ask me to do so, although it should be 
something trivial ;))

BTW, find KM133 and KT133 datasheets here ;)
	* VT8363: http://www.fae.com.tw/datasheet/8363kt/DS8363040.pdf
	* VT8365: http://www.fae.com.tw/datasheet/8365/DS8365030.pdf

Regards,

Danijel

  parent reply	other threads:[~2002-03-24 15:08 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-19 21:12 Screen corruption in 2.4.18 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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=200203241507.g2OF7WN26069@ls401.hinet.hr \
    --to=dschiavu@public.srce.hr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ozone@algorithm.com.au \
    --cc=srwalter@yahoo.com \
    /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