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.
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.hackerspac e.lu/wiki/ Tracking_ intel_performan ce_regression