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 [EMAIL PROTECTED]
wrote:I think Hans's idea
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 [EMAIL PROTECTED] wrote:
Following up: The solution proposed by Hans was somewhat
successful. The
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 /
Hi,
On Fri, 18 Nov 2005 00:56:18 +1000
Alan E. Davis [EMAIL PROTECTED] wrote:
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.
That won't help. I'm
On Fri, Nov 18, 2005 at 11:57:12PM -0600, kashani wrote
The Mystique has 4mb of RAM upgradeable to 8mb IIRC. It was likely
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
On Fri, Nov 18, 2005 at 12:56:18AM +1000, Alan E. Davis wrote
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.
There are two set of constraints...
Walter Dnes wrote:
2) You mentioned it was an ancient card. How much RAM does it have?
Under X, here are the RAM requirements...
8 bit colour (256 colours) = 1 byte per pixel
16 bit colour (65536 colours) = 2 bytes per pixel
24 bit colour (16777216 colours) = 4 (yes, *FOUR*) bytes per
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 Fri, 18 Nov 2005 00:56:18 +1000
Alan E. Davis [EMAIL PROTECTED] wrote:
How would you recommend to go about trying vesa. That may be what Ubuntu is
doing. Turn on vesa framebuffer?
Yes. Under - Device Driver -- Graphics support -- Select VESA VGA graphics
support
The further
On 11/18/05, Bob Sanders [EMAIL PROTECTED] wrote:
Also, it mught be useful to download the mga.o from Matrox andfollow the instructions to replace the one in /usr/X11R6/lib/modules (if I recallthe path correctly).
I did download this driver, and when I installed, a message was
generated that the
On Fri, 18 Nov 2005 13:11:58 +1000
Alan E. Davis [EMAIL PROTECTED] wrote:
I did download this driver, and when I installed, a message was generated
that the version was wrong. Maybe I'll try again, and just install it
anyway.
I wonder if the HAL use flag needs to be set to use the driver?
I'm in over my head---bigtime. Trying to install a good gentoo
setup, to configure xorg where I have been forced to use the last
working video card in my parts box: a matrox mystique. The system
is ok, with A7V600 MB, 512 MB RAM, and an Athlon XP 2600+. Video
is corrupted using Gentoo, no matter
On Wed, 16 Nov 2005 20:50:14 +1000
Alan E. Davis [EMAIL PROTECTED] wrote:
I gather that there was a bug in the mga drivers some time ago, and it
appears that the xorg drivers have incorporated the patches I have seen
during my google searches.
I had one running on Gentoo last year, before
13 matches
Mail list logo
