All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Kassur <cmarco@astercity.net>
To: linux-kernel@vger.kernel.org
Subject: fonts corruption with 3dfx drm module
Date: Wed, 30 Jan 2002 20:10:42 +0100	[thread overview]
Message-ID: <3C584532.3B64FBC@astercity.net> (raw)

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.



             reply	other threads:[~2002-01-30 19:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30 19:10 Marek Kassur [this message]
2002-01-30 19:56 ` fonts corruption with 3dfx drm module Jurriaan on Alpha
  -- strict thread matches above, loose matches on Subject: below --
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
     [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=3C584532.3B64FBC@astercity.net \
    --to=cmarco@astercity.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.