Re: fonts corruption with 3dfx drm module

From: Christian Burger (christian.burger@edb.ericsson.se)
Date: Fri May 10 2002 - 01:28:42 EST


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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Tue May 14 2002 - 12:00:13 EST