Hmm, it's good to see the progress. But apparently you need really recent code. On the SuSE installation (just got to openSuSE 13.1) I am supervising there are still problems with the free driver stack and an A6 5400K. Glitches and graphic deformations, garbage from time to time on the screen. And the SW components aren't that old. (Kernel 3.11.something, Mesa 9.2.2 and so on). (I should have installed Gentoo on it anyway, but then installation takes much longer and I can't come over to that box so often for regular syncing and updating.) Fglrx worked "fine" besides giving me a black screen on any real console (ctrl-alt-Fx). It is a bit sad since I had hoped for 8 months since the last SuSE that I could use the free driver stack now. But no, it is still haunted by bugs.
Just in case you didn't know, there's an open bug for a year now, only on Black Editions, and only on China-assembled ones:
It's diffused in Germany and ass. in Malaysia but the bug looks interesting. These desktop artifacts are quite a nuisance.
Thanks for the link.
I would have prefered no overclocking.
Why? Overclocking is pretty trivial these days if you don't have crippled Dell/HP/Acer/Lenovo etc. hardware.
Originally Posted by stqn
The top end GPUs are now overclocking themselves based on thermals. The cooler you can keep the GPU the higher it'll push itself.
- As you said, it may not be possible on all hardware.
Originally Posted by Kivada
- Itís not representative of the out-of-the-box performance of the hardware that most users will experiment.
- It may require a different cooling solution than the one provided by AMD in order to keep the noise down (though arguably the same can be said of my non-overclocked i3Ö)
- Different processors will (AFAIK) have different overclocking possibilities, so itís not certain that everyone will be able to overclock this processor to 4.7*GHz.
- Overclocking will cause the processor to consume more power and the fan to spin faster which I donít like; I prefer to undervolt my processors and keep them at their normal frequency.
Now if GPUs are overclocking themselves out of the box, then maybe itís what should be benchmarkedÖ But the results will change according to the case ventilation and ambiant temperature and length of the testÖ fun.
Both current CPUs and GPUs do it (the "turbo" mode). You're also correct that it affects benchmarking results, and many sites wondered what to do with that.
Originally Posted by stqn
Some planned to only benchmark with that disabled; but that has two problems 1) not all cards let you disable it 2) then it's not what most users will see.