Christopher, On Mon, Dec 01, 2003 at 12:46:55AM -0500, Christopher Gleba wrote: > > Hello, > > I had been using the mach64-0-0-5-branch in > linux for a while but recently I upgraded my > install and thus gave a shot at the > mach64-0-0-6-branch and encountered a problem.
> This report is broken into sections: > > 1 - Problem description > 2 - System information > 3 - XF86Config-4 > > ----------------------------------- > 1) Problem Description: > > I first tried the mach64-20031128-linux.i386.tar.bz2 > daily snapshot with XFree86-4.3-23mdk. Kernel modules > built fine and insmod'ed. DRI was not working; the > relevant section on XFree86.0.log reads: > > (II) ATI(0): [drm] created "mach64" driver at busid "PCI:1:0:0" > (II) ATI(0): [drm] added 8192 byte SAREA at 0xd0ba0000 > (II) ATI(0): [drm] mapped SAREA 0xd0ba0000 to 0x40016000 > (II) ATI(0): [drm] framebuffer handle = 0xf5000000 > (II) ATI(0): [drm] added 1 reserved context for kernel > (II) ATI(0): [drm] Will request asynchronous DMA mode > (WW) ATI(0): [agp] AGP not available > (WW) ATI(0): [agp] AGP failed to initialize -- falling back to PCI mode. > (WW) ATI(0): [agp] Make sure you have the agpgart kernel module loaded. Do you have a PCI card? If not make sure the agpgart kernel module is loaded before the mach64 module, by adding pre-install mach64 modprobe -k agpgart to your /etc/modules.conf > (II) ATI(0): [drm] register handle = 0xf4100000 > (II) ATI(0): [dri] Visual configs initialized > (II) ATI(0): [dri] Block 0 base at 0xf4100400 > (WW) ATI(0): Not enough memory for local textures, disabling DRI And you should decrease the screen depth (16bpp is a must if you care for 3D performance). > (II) ATI(0): [drm] removed 1 reserved context for kernel > (II) ATI(0): [drm] unmapping 8192 bytes of SAREA 0xd0ba0000 at 0x40016000 > > Did a lsmod, agpgart and mach64 are loaded. Looked at > kernel logs and found: > > kernel: [drm:mach64_dma_init] *ERROR* mach64_dma_init called without lock held > kernel: [drm:mach64_unlock] *ERROR* Process 1836 using kernel context 0 > kernel: [drm:mach64_dma_init] *ERROR* mach64_dma_init called without lock held > kernel: [drm:mach64_unlock] *ERROR* Process 2427 using kernel context 0 > kernel: [drm:mach64_dma_init] *ERROR* mach64_dma_init called without lock held > kernel: [drm:mach64_unlock] *ERROR* Process 2733 using kernel context 0 > kernel: [drm:mach64_dma_init] *ERROR* mach64_dma_init called without lock held > kernel: [drm:mach64_unlock] *ERROR* Process 4150 using kernel context 0 Well, this is suerly a consequence of above, but these calls shouldn't be happening consedering DRM was disabled.... > So I figured that a patch that Mandrake put on X may > have been causing the problem -- so I downloaded the > mach64-0-0-6-branch from CVS yesterday and re-built > a clean XFree86 -- same problem. > I hope that this bug report helps and thank the dri development > people for their hard work. See if the above tips help. Let us know otherwise. Jose Fonseca ------------------------------------------------------- This SF.net email is sponsored by OSDN's Audience Survey. Help shape OSDN's sites and tell us what you think. Take this five minute survey and you could win a $250 Gift Certificate. http://www.wrgsurveys.com/2003/osdntech03.php?site=8 _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
