Skip to contentSkip to conversation

fonts corruption with 3dfx drm module

DISCUSSION Christian Burger 3 participants 4 messages May 9, 2002 – May 10, 2002

lore
Share & tools
lore
#0 lore raw

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.
Thanks,

Christian Burger

Quoted 4 lines · Zwane Mwaikambo
Quoted 2 lines · Zwane Mwaikambo

Do you guys have CONFIG_MTRR and/or CONFIG_FB_VESA enabled? Also which motherboard chipset?

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.

I am with the DRI devel team and saw it occasionally with XFree86 DRI CVS trunk and the latest mesa-4-0-branch. At that time I had FB enabled as I remember right.

The current DRI stuff is "only" missing the latest XFree86 4.2.0 release 2D code. Update is under way.

I can _NOT_ see it without FB and currently running 2.4.18-pre7-J6-VM-23-preempt-lock.

/home/nuetzel> cat /proc/mtrr
reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1
reg01: base=0x20000000 ( 512MB), size= 128MB: write-back, count=1
reg02: base=0xec103000 (3777MB), size= 4KB: write-combining, count=1
reg03: base=0xe0000000 (3584MB), size= 64MB: write-combining, count=2

Voodoo5 5500 AGP.

Regards,
Dieter

Signature · 11 lines
Dieter Nützel
Graduate Student, Computer Science

University of Hamburg
Department of Computer Science
@home: [email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
#1 lore raw
Quoted 10 lines · Christian Burger

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

Signature · 2 lines
PGP key fingerprint: 161D 6FED 6A92 39E2 EB5B  39DD A4DE 63EB C216 1E4B
Available at PGP keyservers
#2 lore raw
In reply to Christian Burger
Quoted 6 lines · On Thu, 09 May 2002 14:47:22 +0300 Christian Burger…

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.

I've seen a blinking character (green, if i can remember) with my voodoo 3 3000 PCI, but I could change the VT.

The only issue with my graphics card is the corruption of some characters, when switching X to/from vt. The most affected character is: ! .

Diego Calleja <[email protected]>

#3 lore raw
In reply to Christian Burger

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

Quoted 25 lines · Jussi Laako
Quoted 10 lines · Christian Burger

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