Yes, intel-gpu-tools in both Natty and Oneiric doesn't work from the repository (you get the error - Couldn't map MMIO region: No such file or directory). Compiling intel-gpu-tools from source is one option, but I also found a PPA that works, and you can also just download the .deb without adding the PPA:
https://launchpad.net/~sarvatt/+archive/intel-gpu-tools For those people that are still experiencing some artifacts, I have been playing around with the "sudo intel_reg_write 0x9404 0x1800" fix most of the afternoon and have come to find that it matters when you run this command. This command must be run before any 3D happens, if you have already had the artifacts and then run the command it will not fix it, even if you restart your 3D application. It appears once the graphics card is in this "state" already, the fix won't work. You must run the command just after you started the computer, when there have been no artifacts or 3D yet. Because the command has to be run as root (and it doesn't seem to matter if you run it before X starts), I have found the perfect place to place this line is in the /etc/rc.local file, just before the "exit 0" line. Since /etc/rc.local is executed by root, you don't have to put sudo in front either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/829086 Title: Artifacts in 3D with Sandy Bridge To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/829086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
