|
From: Davicillo U. <dav...@ya...> - 2009-05-15 06:27:27
|
Dear Mike Smith 41 I think I have solved this problem, although I don't really know what I'm doing. It seems that the DRM developers have recently changed the code of the mach64_irq.c and that change is what is causing us so many problems. I have been trying to reach a solution since January until now. I have downloaded the latest git and afterwards modified the mach64_irq.c, this way: 1.-as root, download with "git clone git://anongit.freedesktop.org/mesa/drm" 2.-"cd drm/linux-core" 3.-Edit the mach64_irq.c 4.-Inside the function "int mach64_driver_irq_postinstall(struct drm_device * dev)" there is only one line "return 0;" 5.-Replace the "return 0;" by "return drm_vblank_init(dev,1);" 6.-Save the file and exit 7.-Make with "make DRM_MODULES=mach64" and "make install" 8.-Unload any previously loaded drm.ko and mach64.ko with "modprobe -rv mach64" 9.-(optional) load the new modules with "modprobe -v mach64" 10.-Start X the way you like better. In my case no longer hangs X and my glxgears is about 250fps. Hooray! I hope it solves the problem for good, but I'm also a little worried about why the DRM developers changed this. Anyway, it's worse for me that DRI hang my PC, so I will take the risk. Best regards. Davicillo Uno. -- View this message in context: http://www.nabble.com/mach64-kernel-modules-for-2.6.26-kernel-tp22668419p23549757.html Sent from the mesa3d-users mailing list archive at Nabble.com. |