public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Burger <christian.burger@edb.ericsson.se>
To: Jussi Laako <jussi.laako@kolumbus.fi>, linux-kernel@vger.kernel.org
Subject: Re: fonts corruption with 3dfx drm module
Date: Fri, 10 May 2002 09:28:42 +0300	[thread overview]
Message-ID: <3CDB689A.F43BD31@edb.ericsson.se> (raw)
In-Reply-To: <3CDA61CA.498991DF@edb.ericsson.se> <3CDADD92.908001AB@kolumbus.fi>

Does anyone know how to trace this problem to check if it's related to tdfx?
I think there are two modules for tdfx, one created for the DRI tree of X and
one created from the kernel.
I don't know which we are supposed to use.
Besides this, I believe glide3.so.xxx library interacts with this part of the
code, so it might also be a reason for the problem.
Anyone knows how to investigate this further? Does this make any sense?
Thanks, 

	Christian Burger
  

Jussi Laako wrote:
> 
> Christian Burger wrote:
> >
> > I've seen a much more serious problem which seems to be related to this:
> > I have AMD Athlon K7 650MHz, Via chipset, Voodoo5 5500AGP, MTTR enabled.
> > What is happening here is that when switching back from init 5 to init 3
> > for instance, the system hangs completely and a blinking character
> > appears in a black screen. There's no other way other than to power cycle
> > the system. It seems to be a kernel panic.
> > Kernel version is 2.4.18, and it happens with or without DRM support,
> > with and without FB support. There's no way I can have this version of
> > the kernel to work here.
> 
> Same problem here, with AMD K6 and Voodoo3 2000 PCI. All kernels and all
> XFree86 4.x.x versions. Although it doesn't hang the machine. Usually just
> fonts in vc1 are messed up.
> 
> So, it's not MTRR nor AGP problem. It must be something in XFree86 tdfx
> driver. Accelerated-X doesn't show this problem.
> 
>         - Jussi Laako
> 
> --
> PGP key fingerprint: 161D 6FED 6A92 39E2 EB5B  39DD A4DE 63EB C216 1E4B
> Available at PGP keyservers

  reply	other threads:[~2002-05-10 12:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-09 11:47 fonts corruption with 3dfx drm module Christian Burger
2002-05-09 20:35 ` Jussi Laako
2002-05-10  6:28   ` Christian Burger [this message]
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
     [not found] <20020128182427.11F20FB8D@netfinity.realnet.co.sz>
2002-01-29  6:45 ` Zwane Mwaikambo
2002-01-29 14:32   ` Dieter Nützel
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=3CDB689A.F43BD31@edb.ericsson.se \
    --to=christian.burger@edb.ericsson.se \
    --cc=jussi.laako@kolumbus.fi \
    --cc=linux-kernel@vger.kernel.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