From: Chris Howells <chrish@gmx.co.uk>
To: ajoshi@shell.unixbox.com, faith@valinux.com
Cc: linux-fbdev-devel@lists.sourceforge.net, dri-devel@lists.sourceforge.net
Subject: Possible bug: nasty interaction between framebuffer and DRI/DRM
Date: Fri, 31 May 2002 12:54:39 +0100 [thread overview]
Message-ID: <200205311254.50400.chrish@gmx.co.uk> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I seem to have discovered a nasty interaction between framebuffer and DRI/DRM
in OpenGL applications. I can reproduce this problem in at least Return to
Castle Wolfenstein (version 1.1b) and Tux Racer.
I am using a 32 MB ATI Rage Pro 128 on Debian woody (XFree86 4.1). If I run
Tuxracer or RTCW, and wait for the game to load, everything is alright.
However if I switch to a spare virtual terminal, and switch back to X, the
fonts become illegible -- they just appear as coloured boxes with no
outlines, making things unplayable.
The problem does not occur when using software based OpenGL rendering which is
why I believe DRI/DRM is involved. This problem only occurs when framebuffer
is enabled in the kernel, if framebuffer is disabled the problem disappears,
so I believe framebuffer is also at fault.
Greatful for any help...
Chris Howells
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE892SKF8Iu1zN5WiwRAgMbAJ0V5bWa85Lfsgu4FFtKeIj4c/YX8gCcCrn6
YU1lq0HuQpefLVGsDvFzN4E=
=qzHZ
-----END PGP SIGNATURE-----
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
next reply other threads:[~2002-05-31 11:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-31 11:54 Chris Howells [this message]
2002-05-31 12:01 ` Possible bug: nasty interaction between framebuffer and DRI/DRM Chris Howells
2002-05-31 12:08 ` Geert Uytterhoeven
2002-05-31 18:39 ` Chris Howells
2002-05-31 20:10 ` Geert Uytterhoeven
2002-05-31 12:09 ` [Dri-devel] " Keith Whitwell
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=200205311254.50400.chrish@gmx.co.uk \
--to=chrish@gmx.co.uk \
--cc=ajoshi@shell.unixbox.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=faith@valinux.com \
--cc=linux-fbdev-devel@lists.sourceforge.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 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.