[mythtv] RE: mythuitest screen corruption

[Robert S. Kerr]

Kristian,

It appears to me that the current mythuitest is really inefficient with respect to video RAM utilization.  I had the same problem and what worked for me on two separate machines was to increase the VideoRAM setting in my xorg.conf to over 128M.  Even then, the frame rate was fairly slow on an Athlon 2400XP.  I get ~500FPS using glxgears, and probably 5 FPS with mythuitest.  I'm chalking that up to video card and memory issues.

Rob

Kristian Kalweit wrote: 
>Hi,
>
>yesterday I tested mythuitest. I have an epia M10000 system, 2.6.7 
>Kernel, DRM 2.4.3 and Unichrome driver. Myth .17 is running fine. My 
>first test with libmythui was with software opengl (original xorg 
>R8.6.2). The test application was running like expected, but very, very, 
>very slow (I expected this also, of course).  So I installed the opengl 
>driver of the unichrome project. Glxinfo said yes to direct rendering, 
>also glxgears is working with 495 FPS. If I start mythuitest now I get 
>only a white screen with an orange box at the bottom of the screen. The 
>orange box is fading, so I think this is originally the "Press any key" 
>message. I use GANT, so the color of the orange box is like the focus 
>color of GANT.
>
>Do I need some special GL extensions? Or what could cause this?
>
>Output of mythuitest:
>pvr mythuitest # ./mythuitest
>2005-02-23 07:35:51.355 Switching to square mode (G.A.N.T.)
>Could not find theme: Standard
>libGL: XF86DRIGetClientDriverName: 4.1.30 unichrome (screen 0)
>libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/unichrome_dri.so
>drmOpenByBusid: Searching for BusID PCI:1:0:0
>drmOpenDevice: node name is /dev/dri/card0
>drmOpenDevice: open result is 9, (OK)
>drmOpenByBusid: drmOpenMinor returns 9
>drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
>__driCreateNewScreen - succeeded
>libGL error:
>Can't open configuration file /etc/drirc: No such file or directory.
>libGL error:
>Can't open configuration file /root/.drirc: No such file or directory.
>
>The libGL errors are not a problem. Only shown because I enabled debug 
>mode with LIBGL_DEBUG="verbose".
>
>Some other OpenGL apps seemed to work, e.g. Racer from racer.nl is 
>running fine.
>
>Kristian.