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, 18 Nov 2005 00:56:18 +1000	[thread overview]
Message-ID: <7bef1f890511170656x6977f2d3wd61ecd63d757abb3@mail.gmail.com> (raw)
In-Reply-To: <20051116175214.06a925c4@chi.speakeasy.net>

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

Bob:

Your comments are extremely useful. However much I would like to get a newer
graphics card, I am stuck with this one for a few weeks at least. It works
well on an Ubuntu system on a different partition.

How would you recommend to go about trying vesa. That may be what Ubuntu is
doing. Turn on vesa framebuffer?

I backed down to 1024xsomething: vertical lines were scalloped/wavy. Someone
mentioned this would be a timing issue, but I don't know what I'd do to
microadjust timing? xvidtune? I'll try it.

Thanks again.

Alan

On 11/17/05, Bob Sanders <rmsand@concentric.net> wrote:
>
>
> Have you tried just using - vesa? Or vga? It should work. Turning on
> everything
> is always a sure way to break a kernel.
>
> >
> > Description: when scrolling the buffer, some lines are doubled, some are
> > lost, and using Firefox at least, when I type Ctrl-L, the frame displays
> > properly until it is scrolled again. I have found descriptions of
> similar
> > issues on the Inet, but nothing that has helped get my system to work
> > properly. Does this symptom ring a bell with anyone?
> >
>
> Generally, it's because the gfx card can't refresh from it's internal
> memory fast enough.
> As I recall, the Mystique had an optional memory module, which I have on
> mine. Perhaps
> its just that your trying to use too high a resolution and hitting the
> cards performance
> limits?
>
> With due respect, save up your pennies and get a current Gfx card. Should
> be around
> US$42. Sure, that's a months wages in some parts of the world. But still -
> throwing a massively
> powerful processor in a system with a dead-end Gfx card is kind of
> wasteful, unless you're making
> this thing into a server.
>
> Bob
> -
> --
> gentoo-user@gentoo.org mailing list
>
>

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

  reply	other threads:[~2005-11-17 15:02 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 [this message]
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
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=7bef1f890511170656x6977f2d3wd61ecd63d757abb3@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