fixmtrr.sh should be called just before starting x, even a logout operation resets the MTRR ranges (when using GDM)
I've found that the MTRR fix does not affect performance in the least when run on a system using a display manager for starting X. It seems that the X server is only unable to set the MTRR range itself if it is called by a normal user (eg. using startx), in that case, the MTRR fix has a slight effect on performance on my i915 and g35. Here are my test results using the 2.6 driver and the 2.4 backport on different configurations on i915 and G35: https://www.hackerspace.lu/wiki/Tracking_intel_performance_regression -- [i945] (Needs UXA) Kubuntu Jaunty Intel 945 GM - Poor sluggish graphics performance in Kate text, etc. https://bugs.launchpad.net/bugs/342923 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
