Hi > Whoops. The oops is my fault, it's a bug in _cleanup_dma. It's fixed in > CVS now. Just update and rebuild and install the kernel module. This is > not related to your original problem though, I'm not sure what would be > causing a lockup on vt switches if no GL contexts are running. I really don't know but... Well, it works now (snapshot 0502). No OOPS detected. In my syslog I see:
May 2 20:31:23 localhost kernel: [drm] Creating pci pool May 2 20:31:23 localhost kernel: [drm] Allocating descriptor table memory May 2 20:31:23 localhost kernel: [drm] descriptor table: cpu addr: 0xc08a4000, bus addr: 0x008a4000 May 2 20:31:23 localhost kernel: [drm] Starting DMA test... May 2 20:31:23 localhost kernel: [drm] starting DMA transfer... May 2 20:31:23 localhost kernel: [drm] waiting for idle... May 2 20:31:23 localhost kernel: [drm] waiting for idle...done May 2 20:31:23 localhost kernel: [drm] DMA test succeeded, using synchronous DMA mode Does it mean DMA works for me? AFAIK it does. BTW, does "synchronous" mean there will be "asynchronous" somewhere?:) About FPS - they are still lower than in good old user-mode MMIO... (241 vs 286 in 0-0-3). But DMA is already enabled - does this mean I will never get anything better? Well, glxgears works OK. So does Counter-Strike. As usual, in texture-intensive apps (celestia) we are waiting for GART... Anyway, thanks for fast fix. Cheers, Sergey _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel