From: thunder7 <thunder7@xs4all.nl>
To: Mark Zealey <mark@zealos.org>
Cc: "'lkml'" <linux-kernel@vger.kernel.org>
Subject: Re: fonts corruption with 3dfx drm module
Date: Sun, 27 Jan 2002 15:35:28 +0100 [thread overview]
Message-ID: <20020127153528.A3222@xs4all.nl> (raw)
In-Reply-To: <20020127122501.GA23825@itsolve.co.uk> <000301c1a732$a989fa80$132f23d9@stratus> <20020127133348.GB23825@itsolve.co.uk>
In-Reply-To: <20020127133348.GB23825@itsolve.co.uk>; from mark@zealos.org on Sun, Jan 27, 2002 at 01:33:48PM +0000
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/
>
next prev parent reply other threads:[~2002-01-27 14:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2002-01-27 17:35 ` Diego Calleja
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-28 16:39 Dieter Nützel
[not found] <20020128182427.11F20FB8D@netfinity.realnet.co.sz>
2002-01-29 6:45 ` Zwane Mwaikambo
2002-01-29 14:32 ` Dieter Nützel
[not found] <20020129143209.2AE68FB85@netfinity.realnet.co.sz>
2002-01-29 14:40 ` Zwane Mwaikambo
[not found] <20020128203706.24AC0FB8D@netfinity.realnet.co.sz>
2002-01-30 10:14 ` Zwane Mwaikambo
2002-01-31 21:03 ` Diego Calleja
2002-01-30 19:10 Marek Kassur
2002-01-30 19:56 ` Jurriaan on Alpha
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
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=20020127153528.A3222@xs4all.nl \
--to=thunder7@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@zealos.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
all inboxes | Powered by JetHome®