Peter Clifton wrote: > Jamie, do you consistently get the above error about non-contiguous GTT > entries? This code doesn't actually look to have changed since 2.1.1, > althoguh lots of other stuff dealing with memory allocation has.
No. Since the previous report, I have rebooted and used the same driver a few times, and none of those times reported non-contiguous GTT. Yet, it was quite consistent when I first installed it and restarted X a few times. What seems most likely, then, is that running that driver a _second_ time (after it's run once, or after another driver) produces that non-contiguous GTT and doesn't fix it. I've now switched back to Gutsy's own driver, because I did have problems with the driver that removes the screen artifact. (Suspend was completely unreliable, tending to crash with the too-familiar "text mode garbage blocks of colour and stuck system", and also the DVI output was unstable: Occasionally there was a glitch in the picture, and after 30-60 minutes, the picture would disappear completely. Gutsy's driver seems 95% stable with suspend, and no DVI glitch). Following your ideas in another comment, I looked closer at the screen artifact, which is the subject of my next comment. -- screen artifacts after resume, part row of pixels in error (945GM) https://bugs.launchpad.net/bugs/91966 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
