From: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
To: Zwane Mwaikambo <zwane@linux.realnet.co.sz>
Cc: Mark Zealey <mark@zealos.org>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: fonts corruption with 3dfx drm module
Date: Tue, 29 Jan 2002 15:32:09 +0100 [thread overview]
Message-ID: <20020129143609Z289385-13996+13878@vger.kernel.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0201290838560.20095-100000@netfinity.realnet.co.sz>
In-Reply-To: <Pine.LNX.4.44.0201290838560.20095-100000@netfinity.realnet.co.sz>
On Tuesday, 29. January 2002 07:45, Zwane Mwaikambo wrote:
> On Mon, 28 Jan 2002, Dieter [iso-8859-15] Nützel wrote:
> > MTRR, of course (do you like 2D and even 3D hardware accelerated without
> > MTRR?), FB, no, chipset is a AMD 750 (Irongate C4), using X 4.1.99.1 DRI
> > CVS.
>
> The reason why i ask is because i was experiencing font corruption with
> MTRRs enabled and X segfaulting with 4.x and a VIA Apollo pro
That make sense.
> (mostly because with 3.3.6 i never setup the MTRRs myself)
We 3.3.6 you have to do it some times.
> and a friend of mine was seeing corruption plus the occasional lockup with
> his KT133. Disabling MTRRs solved both our lockup problems,
This could be all the VIA/mobo/BIOS problems widely discussed.
Maybe the latest AGP GART issue.
> mind you i soon switched back to my older 440BX setup and my problems went
> away.
Some point at Intel 'cause they "designed" the AGP port with UP only in mind
and AMD's Athlon/Duron is designed for SMP from the ground.
> I also asked about FB because my particular card (ATI Rage IIC) never gets
> MTRRs working in X4.1 unless i have it FB enabled.
Have you ever looked at XFree and/or DRI devel?
I think this could and should be solved. Without notice nobody cares...
You should definitely go with XFree86 4.2.0. It is out and most distros have
packages available. Then look deeper into the MTRR problem.
Good luck.
Dieter
--
Dieter Nützel
Graduate Student, Computer Science
University of Hamburg
Department of Computer Science
@home: Dieter.Nuetzel@hamburg.de
next prev parent reply other threads:[~2002-01-29 14:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020128182427.11F20FB8D@netfinity.realnet.co.sz>
2002-01-29 6:45 ` Zwane Mwaikambo
2002-01-29 14:32 ` Dieter Nützel [this message]
2002-05-09 11:47 Christian Burger
2002-05-09 20:35 ` Jussi Laako
2002-05-10 6:28 ` Christian Burger
2002-05-09 21:07 ` Diego Calleja
-- strict thread matches above, loose matches on Subject: below --
2002-01-30 19:10 Marek Kassur
2002-01-30 19:56 ` Jurriaan on Alpha
[not found] <20020128203706.24AC0FB8D@netfinity.realnet.co.sz>
2002-01-30 10:14 ` Zwane Mwaikambo
2002-01-31 21:03 ` Diego Calleja
[not found] <20020129143209.2AE68FB85@netfinity.realnet.co.sz>
2002-01-29 14:40 ` Zwane Mwaikambo
2002-01-28 16:39 Dieter Nützel
2002-01-28 14:11 Zwane Mwaikambo
2002-01-28 14:12 ` Zwane Mwaikambo
2002-01-28 15:56 ` Mark Zealey
2002-01-28 20:41 ` Diego Calleja
2002-01-28 21:31 ` Chris Meadors
2002-01-27 11:36 Diego Calleja
2002-01-27 12:25 ` Mark Zealey
2002-01-27 13:00 ` Daniel J Blueman
2002-01-27 13:33 ` Mark Zealey
2002-01-27 14:35 ` thunder7
2002-01-27 17:35 ` Diego Calleja
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=20020129143609Z289385-13996+13878@vger.kernel.org \
--to=dieter.nuetzel@hamburg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@zealos.org \
--cc=zwane@linux.realnet.co.sz \
/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®