[Linux-fbdev-devel] Possible bug: nasty interaction between framebuffer and DRI/DRM

[Chris H. <ch...@gm...>]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I seem to have discovered a nasty interaction between framebuffer and DRI/D=
RM=20
in OpenGL applications. I can reproduce this problem in at least Return to=
=20
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=
=20
Tuxracer or RTCW, and wait for the game to load, everything is alright.=20
However if I switch to a spare virtual terminal, and switch back to X, the=
=20
fonts become illegible -- they just appear as coloured boxes with no=20
outlines, making things unplayable.

The problem does not occur when using software based OpenGL rendering which=
 is=20
why I believe DRI/DRM is involved. This problem only occurs when framebuffe=
r=20
is enabled in the kernel, if framebuffer is disabled the problem disappears=
,=20
so I believe framebuffer is also at fault.

Greatful for any help...

Chris Howells
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE892SKF8Iu1zN5WiwRAgMbAJ0V5bWa85Lfsgu4FFtKeIj4c/YX8gCcCrn6
YU1lq0HuQpefLVGsDvFzN4E=3D
=3DqzHZ
=2D----END PGP SIGNATURE-----