BTW, now I'm just realized that my /proc/mtrr already contains a line for the video memory, but with "uncachable" option.
reg00: base=0x000000000 ( 0MB), size=32768MB, count=1: write-back
reg01: base=0x0e0000000 ( 3584MB), size= 512MB, count=1: uncachable
reg02: base=0x0ddc00000 ( 3548MB), size= 4MB, count=1: uncachable
reg03: base=0x0de000000 ( 3552MB), size= 32MB, count=1: uncachable
Maybe I need to somehow erase that line before running fixmtrr.sh??
Also, there are strange messages from logs:
/var/log/syslog.0:May 7 01:33:07 rg-work kernel: [ 14.320969] mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining
/var/log/syslog.0:May 7 01:33:07 rg-work kernel: [ 14.320971] [drm] MTRR allocation failed. Graphics performance may suffer.
Last edited by relgames; May 7th, 2009 at 11:20 PM.
Has anyone that has done this with RC4 found that it doesn't have the power management issues that can cause the overheating? I'd love to do this but that would be a stopper for me.
Last edited by NJC; May 8th, 2009 at 07:36 PM. Reason: Misleading information
G31 works well with uxa enabled using the default Jaunty xorg. The one from ppa, even the stable one crashes it.
If you're gettting the 404 errors during download you've got to change those files to -2 from -1.
Code:wget -c http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.30-rc2/linux-headers-2.6.30-020630rc2-generic_2.6.30-020630rc2_i386.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.30-rc2/linux-headers-2.6.30-020630rc2_2.6.30-020630rc2_all.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.30-rc2/linux-image-2.6.30-020630rc2-generic_2.6.30-020630rc2_i386.deb http://ftp.us.debian.org/debian/pool/main/libd/libdrm/libdrm2_2.4.9-2_i386.deb http://ftp.us.debian.org/debian/pool/main/libd/libdrm/libdrm-intel1_2.4.9-2_i386.deb http://http.us.debian.org/debian/pool/main/x/xserver-xorg-video-intel/xserver-xorg-video-intel_2.7.0-1_i386.deb sudo dpkg -i linux-headers-2.6.30-020630rc2_2.6.30-020630rc2_all.deb linux-headers-2.6.30-020630rc2-generic_2.6.30-020630rc2_i386.deb linux-image-2.6.30-020630rc2-generic_2.6.30-020630rc2_i386.deb libdrm2_2.4.9-2_i386.deb libdrm-intel1_2.4.9-2_i386.deb xserver-xorg-video-intel_2.7.0-1_i386.deb
A towel is about the most massively useful thing for fixing computers. Use it to muffle your screams when you mess up, or to dry your tears if it's broken beyond repair. When all else fails, use it to cover up the useless machine, then walk away.
The difference between "EXA" and "UXA" acceleration methods are major, because if you enable UXA, the new DRI2 rendering framework is used. Although glxgears seems "slower", real 3D applications should be faster (if UXA & DRI2 work correctly on your chipset at this time).
You do realize that compiz will cause increased CPU usage with Adobe Flash? Although Flash can support hardware rendering, it's explicitly disabled when any composite manager (e.g. compiz) is detected. If your MTRR ranges aren't fixed properly (with or without the newer drivers/configuration), you're always going to experience slowdowns and stuttering in video-intensive applications.
Last edited by psyke83; May 8th, 2009 at 06:02 AM.