From: Witukind <witukind@nsbm.kicks-ass.org>
To: "Zephaniah E. Hull" <warp@babylon.d2dc.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Voodoo3 2000 is eating my chars!
Date: Fri, 2 Jul 2004 06:56:45 +0200 [thread overview]
Message-ID: <20040702065645.27e93ac3.witukind@nsbm.kicks-ass.org> (raw)
In-Reply-To: <20040702073636.GA25592@babylon.d2dc.net>
On Fri, 2 Jul 2004 03:36:36 -0400
"Zephaniah E. Hull" <warp@babylon.d2dc.net> wrote:
> On Thu, Jul 01, 2004 at 08:55:27PM +0200, DervishD wrote:
> > Hi all :)
> >
> > I recently put a Voodoo3 2000 (AGP) card to my home linux box,
> > and now I have a problem in the console. When switching from X to
> > the console, some chars dissappear, or appear cut, etc. I've googled
> > for this, but with no success. Is this a known bug? Maybe an X bug?
>
> This is actually an X bug, which I thought I had fixed a long time ago
> when I was still doing 3Dfx stuff.
>
> On console switch not all the state is being restored properly,
> specificly the font is getting screwed up, simply reloading the font
> should work fine though.
>
> I no longer have either an X tree to easily play in, nor a 3Dfx card
> in a box to test with, so I'm afraid that you're going to have to bug
> the X people.
Same behavior here with Voodoo 3 2000 PCI. I just quickly switch back to X and back to the
console to get the font right, it'll mess up a character or two only quite rarely though, at most 10% of the times
when I switch. I'm not even sure it happened yet since I upgraded to XFree86 4.4.0, but I'm not 100% positive on
this.
next prev parent reply other threads:[~2004-07-02 13:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 18:55 DervishD
2004-07-02 7:36 ` Zephaniah E. Hull
2004-07-02 4:56 ` Witukind [this message]
2004-07-04 16:42 ` DervishD
2004-07-02 8:21 ` DervishD
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=20040702065645.27e93ac3.witukind@nsbm.kicks-ass.org \
--to=witukind@nsbm.kicks-ass.org \
--cc=linux-kernel@vger.kernel.org \
--cc=warp@babylon.d2dc.net \
/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®