Bug 473670

Summary: intel driver needs tweak to produce acceptable FPS on Aspire One A110 netbook
Product: [openSUSE] openSUSE 11.1 Reporter: Forgotten User l5QCzUHucG <forgotten_l5QCzUHucG>
Component: X.OrgAssignee: E-mail List <xorg-maintainer-bugs>
Status: RESOLVED WONTFIX QA Contact: E-mail List <xorg-maintainer-bugs>
Severity: Normal    
Priority: P5 - None CC: markgray+to-suse, sndirsch
Version: Final   
Target Milestone: ---   
Hardware: i686   
OS: openSUSE 11.1   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: dmesg for A110
lspci -v
x.org

Description Forgotten User l5QCzUHucG 2009-02-07 17:39:02 UTC 
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-1.1 Firefox/3.0.5

I installed Opensuse 11.1 (KDE 3.5) on my Aspire One A110 (8GB) netbook.
I also installed extreme-tuxracer on it and it ran very slowly with the default configuration.
glxgears also showed 250FPS.
In order to improve the speed, I had to apply various fixes:
1) add the following to my boot.local script
echo "disable=4" > /proc/mtrr
echo "base=0x1f800000 size=0x800000 type=write-back" > /proc/mtrr
2) add the following to my etc/profile.local
export INTEL_BATCH=1

with these two changes, etracer runs at acceptable speed and glxgears reports about 450 FPS.

Reproducible: Always

Steps to Reproduce:
1.start glxgears
2.
3.
Actual Results:  
shows a frame rate of about 250

Expected Results:  
much higher than that
Comment 1 Forgotten User l5QCzUHucG 2009-02-07 17:42:09 UTC 
Created attachment 271032 [details]
dmesg for A110

dmesg output if required
Comment 2 Forgotten User l5QCzUHucG 2009-02-07 17:43:26 UTC 
Created attachment 271033 [details]
lspci -v

lspci -v output if required
Comment 3 Forgotten User l5QCzUHucG 2009-02-07 17:44:57 UTC 
Created attachment 271034 [details]
x.org

x.org if required
Comment 4 Stefan Dirsch 2009-02-10 09:16:18 UTC 
This sounds very much machine and not graphics chip specific. I'm afraid we don't have a framework to apply such workarounds depending on the machine. WONTFIX.