2013-12-06, 22:05
(2013-12-06, 21:48)locomot1f Wrote: starting to wonder if it's the Richland APUs. I may be wrong. but it seems people with Trinity APUs haven't had the problem.
i'm running a6-6400 Richland APU.
i am tempted to trying the debian disto -- hehehe
No, while I myself have a Richland in the bug report there are a number of Trinity APU's having the issue.
However, a larger than not number of us are using Black Edition APU's. Not everyone in the bug report has specified, I don't think, whether they are all using a BE or not.. I also have no idea why a BE would matter if it's the same chip/GPU combination.
The OP in the Report had sets of the same APU, one set non-BE and the other BE, and the Non-BE APU's worked fine.
There is also another post that talks about someone testing several variations of APU's and discovering that a significant number of "GB" labeled APU's are experiencing the problem. But I haven't taken my system apart to check the country code on mine.
In any case.. it's definitely not just Richland. I also would be extremely strongly suspicious that is not Distro specific either. There a few different distro's in the Bug Report with the issue, and while I am using the Arch AUR, I have examined the PKGBUILD's and I am, in effect, doing exactly what gradinaruvasile did - which is compile everything directly from GIT. The biggest difference would be kernel - even from git, depending on what make config options you select and what, if any, distro-specific patches you apply.