OS wrote: > I've asked about the RENDER and the xinerama extension myself. After posting > to the Xpert mailing list I don't believe that the xinerama extension is > supported by my chipset driver (ati). I just assumed that RENDER is not > supported on the ati driver as well (after all, hardly anything is !!! They > had 3D acceleration in 3.3.6, but not in 4 - go figure !). After searching around I found that the RENDER extension is sth. build into X that loads itself on startup without any entry in XF86Config. In my /var/log/XFree.0.log I see that this extension is attempted to be loaded but although no error follows I don't see it afterwards in the 'xdpyinfo' output. So it could be that it decides it can't be loaded if it realizes you use the ati module. Yes I too have an ati (expert@play). I think though XFree does some kind of acceleration. I hoped that 4.0.2 would even be better than 4.0.1 ... But let me tell you that with my XFree-4.0.1 I was able to use the latest kwintv albeit without the libqt-mt multithreading option compiled in kwintv. All my efforts to upgrade were just to enable this multi-threading in kwintv (question of being complete). I also start to suspect that the Xlib error I see is just a warning and that kwintv crashes for some other reason. I'll try to get help from the kwintv side. Guy. > > > Owen > > On Thursday 15 February 2001 3:40 am, you wrote: > > Hi all, > > > > In order to use the latest kwintv with use of qt multi-threading I went > > to the trouble of upgrading to glibc-2.2.1, qt-2.2.3, xfree-4.0.2, > > freetype2 etc... > > I compiled qt but got binary rpms for the rest. My original system was > > a Mdk 7.2. > > > > After re-compiling kwintv ok I get this bleeding error at launchtime: > > > > $ kwintv > > Xl$ kwintv > > Xlib: extension "RENDER" missing on display ":0.0". > > KCrash: crashing.... crashRecursionCounter = 2 > > KCrash: Application Name = kwintv path = <unknown> > > Xlib: extension "RENDER" missing on display ":0.0". > > > > Does this mean that the xfree-4.0.2 I got from the cooker didn't have > > the RENDER extension compiled in? I searched my system and found > > /usr/X11R6/lib/libXrender.so.1.0 present. > > If this is it how do you load it (tried 'load render' in vain)? An > > xdpyinfo right now shows no RENDER extension indeed. > > > > I find the extension loading quite ambiguous cause you have modules, > > built-in extension and others. > > > > Can anyone please shed some light on this by checking with xdpyinfo and > > the contents of his XF86Config-4 file e.g.. > > Thanks for any help. > > > > Guy.
