Re: fonts corruption with 3dfx drm module

Re: fonts corruption with 3dfx drm module

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

	Christian Burger


On Mon, Jan 28, 2002 at 04:12:34PM +0200, Zwane Mwaikambo wrote:

> On Mon, 28 Jan 2002, Zwane Mwaikambo wrote:
> 
> > 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
-- 
Dieter Nützel
Graduate Student, Computer Science

University of Hamburg
Department of Computer Science
@home: Dieter.Nuetzel@hamburg.de
-
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/

Re: fonts corruption with 3dfx drm module

[Jussi Laako]

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

Re: fonts corruption with 3dfx drm module

[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
  

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

Re: fonts corruption with 3dfx drm module

[Diego Calleja]

On Thu, 09 May 2002 14:47:22 +0300
Christian Burger <christian.burger@edb.ericsson.se> escribió:

> 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 <DiegoCG@teleline.es>

fonts corruption with 3dfx drm module

[Marek Kassur]

Zwane Mwaikambo ask me to post to kernel list directly, so here it is.

I have Voodoo 3 3000 PCI on dual pentium 200MHz (MMX) so no MTRR here
and I see occasionally font corruption with every Xfree 4.x (excluding
4.2, because don't have it yet). I use only text console. Typically one
or sometimes more characters are corrupted and look like upper/lower
fragment is eaten. Always switch to X and back correct it.

Best regards,
Marek Kassur.

PS. Please CC me as I'm not subscribed.

Re: fonts corruption with 3dfx drm module

[Jurriaan on Alpha]

On Wed, Jan 30, 2002 at 08:10:42PM +0100, Marek Kassur wrote:
> Zwane Mwaikambo ask me to post to kernel list directly, so here it is.
> 
> I have Voodoo 3 3000 PCI on dual pentium 200MHz (MMX) so no MTRR here
> and I see occasionally font corruption with every Xfree 4.x (excluding
> 4.2, because don't have it yet). I use only text console. Typically one
> or sometimes more characters are corrupted and look like upper/lower
> fragment is eaten. Always switch to X and back correct it.
> 
In that case, let me pitch in and say I never saw any corruption.

Voodoo 4500 pci
X 4.1.x
framebuffer 1600x1200-16@86
Alpha 21164 computer.
mtrr? none on Alpha :-)

Jurriaan
-- 
5) "My competition did it!"  Tactics for showing how the spam that
points to your site (and got you 12 orders) was actually an attempt by
your competition to malign you.
	'Top ten seminars at an upcoming DMA conference' as seen in nanae
GNU/Linux 2.4.18p7-rmap12a on Debian/Alpha 988 bogomips load:0.04 0.03 0.00

Re: fonts corruption with 3dfx drm module

[Zwane Mwaikambo]

On 28 xxx -1, Diego Calleja wrote:

> On 28 ene 2002, 16:12:34, Zwane Mwaikambo wrote:
> > 
> > On Mon, 28 Jan 2002, Zwane Mwaikambo wrote:
> > 
> > > Do you guys have CONFIG_MTRR and/or CONFIG_FB_VESA enabled? Also which 
> > > motherboard chipset?
> I have CONFIG_MTRR enabled. CONFIG_FB_VESA is disabled.
> Moterhboard: MS-5571
> Chipset: SIS 5571 Trinity, Video card voodoo 3 3000 PCI
> > 
> > Forgot to mention, which XFree86 version?
> 
> X 4.1.0 (debian woody release)
> 

Can you try reproduce the font corruption with CONFIG_MTRR disabled, just 
for my amusement. I would greatly appreciate it.

Cheers,
	Zwane Mwaikambo

Re: fonts corruption with 3dfx drm module

[Diego Calleja]

> Can you try reproduce the font corruption with CONFIG_MTRR disabled, just 
> for my amusement. I would greatly appreciate it.
> 
> Cheers,
> 	Zwane Mwaikambo
I can reproduce it whith CONFIG_MTRR disabled. It happens again.

Re: fonts corruption with 3dfx drm module

[Zwane Mwaikambo]

On Tue, 29 Jan 2002, Dieter [iso-8859-15] Nützel wrote:

> > (mostly because with 3.3.6 i never setup the MTRRs myself)
> 
> We 3.3.6 you have to do it some times.

Yep mine never got enabled per default, if i enabled it i would experience 
the same segfaults and font corruption so i got 3.3.6 to "behave" like 
4.1 default and reproduced the problem.

> This could be all the VIA/mobo/BIOS problems widely discussed.
> Maybe the latest AGP GART issue.

This was about a year ago, and i wasn't aware of an issue.

> Have you ever looked at XFree and/or DRI devel?
> I think this could and should be solved. Without notice nobody cares...

I think i'll do that.

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

Thanks for reply, i'm going to resurrect that board ;)

Cheers,
	Zwane Mwaikambo

Re: fonts corruption with 3dfx drm module

[Zwane Mwaikambo]

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 (mostly 
because with 3.3.6 i never setup the MTRRs myself) and a friend of mine was
seeing corruption plus the occasional lockup with his KT133. Disabling MTRRs
solved both our lockup problems, mind you i soon switched back to my older
440BX setup and my problems went away. 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.

Regards,
	Zwane Mwaikambo

Re: fonts corruption with 3dfx drm module

[Dieter Nützel]

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

Re: fonts corruption with 3dfx drm module

[Dieter Nützel]

On Mon, Jan 28, 2002 at 04:12:34PM +0200, Zwane Mwaikambo wrote:

> On Mon, 28 Jan 2002, Zwane Mwaikambo wrote:
> 
> > 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
-- 
Dieter Nützel
Graduate Student, Computer Science

University of Hamburg
Department of Computer Science
@home: Dieter.Nuetzel@hamburg.de

Re: fonts corruption with 3dfx drm module

[Zwane Mwaikambo]

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

Regards,
	Zwane Mwaikambo

Re: fonts corruption with 3dfx drm module

[Zwane Mwaikambo]

On Mon, 28 Jan 2002, Zwane Mwaikambo wrote:

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

Forgot to mention, which XFree86 version?

Cheers,
	Zwane Mwaikambo

Re: fonts corruption with 3dfx drm module

[Mark Zealey]

On Mon, Jan 28, 2002 at 04:12:34PM +0200, Zwane Mwaikambo wrote:

> On Mon, 28 Jan 2002, Zwane Mwaikambo wrote:
> 
> > Do you guys have CONFIG_MTRR and/or CONFIG_FB_VESA enabled? Also which 
> > motherboard chipset?

MTTR, yes, FB, no, chipset is a via apollo MVP3, using X 4.1.0

-- 

Mark Zealey
mark@zealos.org
mark@itsolve.co.uk

UL++++>$ G!>(GCM/GCS/GS/GM) dpu? s:-@ a16! C++++>$ P++++>+++++$ L+++>+++++$
!E---? W+++>$ N- !o? !w--- O? !M? !V? !PS !PE--@ PGP+? r++ !t---?@ !X---?
!R- b+ !tv b+ DI+ D+? G+++ e>+++++ !h++* r!-- y--

(www.geekcode.com)

Re: fonts corruption with 3dfx drm module

[Diego Calleja]

On 28 ene 2002, 16:12:34, Zwane Mwaikambo wrote:
> 
> On Mon, 28 Jan 2002, Zwane Mwaikambo wrote:
> 
> > Do you guys have CONFIG_MTRR and/or CONFIG_FB_VESA enabled? Also which 
> > motherboard chipset?
I have CONFIG_MTRR enabled. CONFIG_FB_VESA is disabled.
Moterhboard: MS-5571
Chipset: SIS 5571 Trinity, Video card voodoo 3 3000 PCI
> 
> Forgot to mention, which XFree86 version?

X 4.1.0 (debian woody release)

Diego Calleja.

> 
> Cheers,
> 	Zwane Mwaikambo
> 
> -
> 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/

Re: fonts corruption with 3dfx drm module

[Chris Meadors]

On 28 xxx -1, Diego Calleja wrote:

> X 4.1.0 (debian woody release)

I was going to pipe up and say that I think 4.2.0 fixed the problem.  But
today running a 2.4.17 kernel, and X 4.2.0, I flopped out of X and to look
at e-mail on a normal text console (132x60) to find the bottom of my '7's
eaten away.

This font corruption has seemed to have gotten better over time (orginally
I saw thins like yellow blinking question marks on red background
scattered about my screen a year ago), 2.4.17 and 4.2.0 seem to have the
problem at an all time low.

-Chris
-- 
Two penguins were walking on an iceberg.  The first penguin said to the
second, "you look like you are wearing a tuxedo."  The second penguin
said, "I might be..."                         --David Lynch, Twin Peaks

fonts corruption with 3dfx drm module

[Diego Calleja]

I can see fonts corruption when switching from X to console. I use last
stable kernel, but it's been hapenning from earlier versions. I use
iso-8959-15 fonts in console, with tdfx drm module for X, my video card is voodoo 3 3000 PCI.
I hope this can help.




Diego.

Re: fonts corruption with 3dfx drm module

[Mark Zealey]

On Sun, Jan 27, 2002 at 12:15:01PM +0000, Diego Calleja wrote:

> I can see fonts corruption when switching from X to console. I use last
> stable kernel, but it's been hapenning from earlier versions. I use
> iso-8959-15 fonts in console, with tdfx drm module for X, my video card is voodoo 3 3000 PCI.
> I hope this can help.

Yes, I've been seeing this too, it's happened in 2.2.19, 2.2.20 and 2.4.17 (for
me). Voodoo banshee PCI card.. it can be annoying, but another switch usially
fixes it...

-- 

Mark Zealey
mark@zealos.org
mark@itsolve.co.uk

UL++++>$ G!>(GCM/GCS/GS/GM) dpu? s:-@ a16! C++++>$ P++++>+++++$ L+++>+++++$
!E---? W+++>$ N- !o? !w--- O? !M? !V? !PS !PE--@ PGP+? r++ !t---?@ !X---?
!R- b+ !tv b+ DI+ D+? G+++ e>+++++ !h++* r!-- y--

(www.geekcode.com)

RE: fonts corruption with 3dfx drm module

[Daniel J Blueman]

Do you have a graphical console or text? I believe there are fixes in
2.4.18-preX to decrease the 3dfx banshee/v3 pixel clock or something to
alleviate this issue. That'll be in the 3dfx framebuffer driver.

Or, of course, it could be something entirely different....
____________________
Daniel J Blueman 

> On Sun, Jan 27, 2002 at 12:15:01PM +0000, Diego Calleja wrote:
> > I can see fonts corruption when switching from X to console. I use 
> > last stable kernel, but it's been hapenning from earlier 
> versions. I 
> > use iso-8959-15 fonts in console, with tdfx drm module for 
> X, my video 
> > card is voodoo 3 3000 PCI. I hope this can help.
> 
> Yes, I've been seeing this too, it's happened in 2.2.19, 
> 2.2.20 and 2.4.17 (for me). Voodoo banshee PCI card.. it can 
> be annoying, but another switch usially fixes it...

Re: fonts corruption with 3dfx drm module

[Mark Zealey]

On Sun, Jan 27, 2002 at 01:00:57PM -0000, Daniel J Blueman wrote:

> Do you have a graphical console or text? I believe there are fixes in
> 2.4.18-preX to decrease the 3dfx banshee/v3 pixel clock or something to
> alleviate this issue. That'll be in the 3dfx framebuffer driver.
> 
> Or, of course, it could be something entirely different....

Text at something like 32x80 and graphics in X at 640x480. This seems to be a
character map corruption problem, like an > will only have the / bit showing on
it, or an ! will be half-sized etc. Also happens with other chars, but a flip
back into X and then console again usially fixes it

-- 

Mark Zealey
mark@zealos.org
mark@itsolve.co.uk

UL++++>$ G!>(GCM/GCS/GS/GM) dpu? s:-@ a16! C++++>$ P++++>+++++$ L+++>+++++$
!E---? W+++>$ N- !o? !w--- O? !M? !V? !PS !PE--@ PGP+? r++ !t---?@ !X---?
!R- b+ !tv b+ DI+ D+? G+++ e>+++++ !h++* r!-- y--

(www.geekcode.com)

Re: fonts corruption with 3dfx drm module

[thunder7]

On Sun, Jan 27, 2002 at 01:33:48PM +0000, Mark Zealey wrote:
> On Sun, Jan 27, 2002 at 01:00:57PM -0000, Daniel J Blueman wrote:
> 
> > Do you have a graphical console or text? I believe there are fixes in
> > 2.4.18-preX to decrease the 3dfx banshee/v3 pixel clock or something to
> > alleviate this issue. That'll be in the 3dfx framebuffer driver.
> > 
That fix only becomes active when the pixelclock is over half the maximum
value for the DAC on your card.
> > Or, of course, it could be something entirely different....
> 
> Text at something like 32x80 and graphics in X at 640x480. This seems to be a
> character map corruption problem, like an > will only have the / bit showing on
> it, or an ! will be half-sized etc. Also happens with other chars, but a flip
> back into X and then console again usially fixes it
> 
> -- 
That means it would be difficult to hit with the console at 80x32 and X at
640x480, unless you run at a ridiculous vertical frequency.
Anyway, it's simple to test if this fix caused it by replacing txfxfb.c 
with a version from before 2.4.18-pre6.

Since I proposed this fix, I'd be intertested to know if this fix caused it.

Let me know,
Jurriaan
> 
> Mark Zealey
> mark@zealos.org
> mark@itsolve.co.uk
> 
> UL++++>$ G!>(GCM/GCS/GS/GM) dpu? s:-@ a16! C++++>$ P++++>+++++$ L+++>+++++$
> !E---? W+++>$ N- !o? !w--- O? !M? !V? !PS !PE--@ PGP+? r++ !t---?@ !X---?
> !R- b+ !tv b+ DI+ D+? G+++ e>+++++ !h++* r!-- y--
> 
> (www.geekcode.com)
> -
> 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/
> 

RE: fonts corruption with 3dfx drm module

[Diego Calleja]

On 27 ene 2002, 13:00:57, Daniel J Blueman wrote:
> 
> Do you have a graphical console or text? I believe there are fixes in
> 2.4.18-preX to decrease the 3dfx banshee/v3 pixel clock or something to
> alleviate this issue. That'll be in the 3dfx framebuffer driver.
> 
> Or, of course, it could be something entirely different....
I use 2.4.18-pre7 now




> ____________________
> Daniel J Blueman