Ask Your Question

WoW 5.0 10-15 fps

asked 2012-09-17 20:32:13 -0500

this post is marked as community wiki

This post is a wiki. Anyone with karma >750 is welcome to improve it.

Hey guys, ill start off by saying that im a complete fedora noob and today is really my first time using it, iv always managed to break it once and had to re-install it so yeah ... go easy :P

Here's my problem, when running windows WoW runs at about 25-30 fps (pretty standard), but in fedora (and ubuntu and basically any linux i can find) my fps runs at about 10-15fps this is with SET gxApi "OpenGL" added to my config file. Without SET gxApi "OpenGL" added to my config file my fps is between 5-10. Im running WoW on all low settings (as i did in windows cos my gfx card is horrible :P) and i'v tried many different things to get it working .. nothing works

List of things i'v tried:

Adding SET gxApi "OpenGL"

Setting maxfps to 30 (Did nothing)

Turned all WoW settings to low

My system specs:


CPU TYPE: AMD V160 Processor



VIDEO CARD MODEL: ATI Mobility Radeon HD 4200


VIDEO CARD DRIVER: atiumdag.dll


Any helps or tips to getting my fps up to 25-30 in fedora would be much appreciated, i really dont want to have to dual boot windows!

p.s. i havent touched gfx card drivers this time, every time i do i break an operating system (i broke ubuntu in the same way)

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2012-10-08 13:51:09 -0500

dmalcolm gravatar image

This may be too advanced, but you could try using oprofile to analyze your system as the program is running. It can give you a report on where the time goes, which perhaps may give ideas on how to tweak things, or, at least, create a better bug report for the driver maintainers...

Install oprofile using:

# yum install oprofile

As root, start a profiling session using:

# opcontrol --start

Then launch your program as normal (not as root!).

After a while of the activity you're trying to analyze, stop the profiling session (as root) using:

# opcontrol --stop

You should then be able to generate a report using:

# opreport --symbols |less

which will show every process that was running, how much time each one took.

Some time will be spent by the program you're running, some by the X server. You can zero in on the program in question by passing the path to it e.g.:

# opreport --symbols /usr/bin/wine |less

to see what a specific process was spending its time on. You'll want the debuginfo packages installed for wine and for the X server. See for some examples of the kind of output you'll see.

This may give clues as to whether the issue is in terms of the number of polygons being drawn, or the number of pixels, or the complexity of the shaders, or some other unexpected issue, and whether or not it's actually managing to use the GPU, or whether the CPU is having to do the work instead. However, to figure all of this out will likely require knowledge of 3D programming. It should at least make for a better bug report...

Hope this is helpful

edit flag offensive delete link more

Question Tools

1 follower


Asked: 2012-09-17 20:32:13 -0500

Seen: 538 times

Last updated: Oct 08 '12