2004.09.26 ~01 Radeon 64DDR, X.Org 6.7, GATOS CVS, linux 2.6.8.1 Finally I got both 3D and vidcap simultaneously again, after I don't know how long. Prior to today, I had two sets of X installed, one that works with DRI but no vidcapping, and the other with vidcapping but no accelerated 3D. To make matters worse, I couldn't straighten out the modules mess, so using the other X install meant having to reboot into the other kernel as well (linux 2.4.26 with vidcap, linux 2.6.7 with 3D). I compiled stock X.Org 6.7. The radeon (radeon.ko) module was from the X.Org tree under programs/Xserver/hw/xfree86/os-support/linux/drm/kernel (I cd'd to there so many times I have the path memorized by heart now). The KMultimedia modules were from GATOS CVS as of 2004.09.26; these are km_api_drv.ko and km_drv.ko. I used the ati.4.4.0 drivers from GATOS cvs as well; had these installed into the XOrg tree with "make install". Upon running avview (also from GATOS cvs), the kernel module (km_drv, I think) kept complaining about the Radeon memory controller being misconfigured. Searching the GATOS mailing list, I came across a post from Jan 2003 -- http://sourceforge.net/mailarchive/forum.php?forum_id=5014&style=flat&viewday=14&viewmonth=200301 -- indicating that I may skip the check causing this error messsage if I were certain the memory controller was indeed configured properly. I assumed it was, since other posts implied that ati.4.4.0 properly configures the Radeon memory controller for linux 2.6.x. So I edited km/radeon.c so that it always returned 1. Testing avview... well, avview from CVS doesn't seem to vidcap properly, so I reverted to the older version (which has always worked before), which was from GATOS CVS 2003.03.22. Testing the recorded MPEG with xine, I was satisfied that recording actually worked. I tested 3D first with glxinfo (said Yes for Direct Rendering), then glxgears (got 1300fps, 200 if software rendered), then Blender, then finally Quake 3. Everything worked as expected. I had checked out DRI, but those drivers seem to conflict in existence with GATOS's ati.4.4.0. So no Mesa cvs either. As circumstances have it, XOrg 6.8 is already released, but someone else has tried GATOS on XOrg 6.8, without success. In summary, linux 2.6.8.1, XOrg 6.7, GATOS cvs for km and ati.4.4.0, old GATOS avview; radeon.ko from XOrg 6.7, km_api_drv.ko and km_drv.ko from GATOS km (with one-line change). On another note, km_drv.ko cannot coexist happily with fbcon. Best as I can tell, the fbcon calls dibs on the Radeon device before km_drv can get to it, so the kernel never gives km_drv a chance to probe devices. I wonder if there's a way for them to coexist.