public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Alan E. Davis" <lngndvs@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Dinosaur Matrox Mystique: corruption
Date: Fri, 25 Nov 2005 10:32:46 +1000	[thread overview]
Message-ID: <7bef1f890511241632m656d5f23ubb2ff62f523db4ac@mail.gmail.com> (raw)
In-Reply-To: <7bef1f890511241629j562d4ccaw531df29938a4e884@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1998 bytes --]

More information: at a lower clock, even at 1024x768 the lines seem to be
less of a problem.  At 832x624, this artifact is not apparent.

Thank you for all the help.

Alan

On 11/25/05, Alan E. Davis <lngndvs@gmail.com> wrote:
>
> Following up:  The solution proposed by Hans was somewhat successful.  The
> buffer update problem has apparently been solved  at a higher  of 1024x768.
>
> Wavy vertical lines are still evident.  This I can ignore, however.   At
> 862
> On 11/21/05, Alan E. Davis <lngndvs@gmail.com > wrote:
> >
> > I think Hans's idea makes sense, since it was the file storm.c that was
> > patched in the first place by others.  I'll have to wait, because I've
> > started a new gentoo install due to problems detecting the /boot partition
> > in my machine.  I botched an attempt to move data from that partition to the
> > / partition.
> >
> > I have been able to do 1064x768 at 16 or 24 bits.  Even 1100something x
> > something worked, perhaps not as perfectly.
> >
> > Thank you for so many great answers, in great depth.  I will see what
> > comes about in a day or two.  It's tricky to do this on a dialup.
> >
> > Alan Davis
> >
> > On 11/20/05, Walter Dnes < waltdnes@waltdnes.org> wrote:
> > >
> > > On Fri, Nov 18, 2005 at 11:57:12PM -0600, kashani wrote
> > >
> > > > The Mystique has 4mb of RAM upgradeable to 8mb IIRC. It was likely0
> > > > new in '95-'96 as I scraped together $140 to by the slightly better
> > > > Matrox Millennium used off Ebay in '96. The Mystique did not do well
> > >
> > > > at higher resolutions, which is why I went with the Millennium. I'd
> > > > shoot for 800x600 and go from there.
> > >
> > >   1024x768 at 24bits (16 million colours) should be doable.
> > >
> > > --
> > > Walter Dnes < waltdnes@waltdnes.org> In linux /sbin/init is Job #1
> > > My musings on technology and security at http://tech_sec.blog.ca
> > > --
> > > gentoo-user@gentoo.org mailing list
> > >
> > >
> >
>

[-- Attachment #2: Type: text/html, Size: 3408 bytes --]

  reply	other threads:[~2005-11-25  0:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 10:50 [gentoo-user] Dinosaur Matrox Mystique: corruption Alan E. Davis
2005-11-17  1:52 ` Bob Sanders
2005-11-17 14:56   ` Alan E. Davis
2005-11-18  2:49     ` Bob Sanders
2005-11-18  3:11       ` Alan E. Davis
2005-11-18  4:54         ` Bob Sanders
2005-11-19  5:36     ` Walter Dnes
2005-11-19  5:57       ` kashani
2005-11-20  3:45         ` Walter Dnes
2005-11-20 14:02           ` Alan E. Davis
2005-11-25  0:29             ` Alan E. Davis
2005-11-25  0:32               ` Alan E. Davis [this message]
2005-11-19 15:46     ` Hans-Werner Hilse

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=7bef1f890511241632m656d5f23ubb2ff62f523db4ac@mail.gmail.com \
    --to=lngndvs@gmail.com \
    --cc=gentoo-user@lists.gentoo.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