Recommended driver for AMD Mullins [1002:9853] is very slow

[Yung Shen]

The recommended driver[1] for [Radeon APU E2-4000 with R2 Graphics] in "Additional Driver" tells user that "X.Org X server -- AMD/ATI display driver wrapper", xserver-xorg-video-ati, is in used, however it is very slow, almost unusable, the issue had been reported here, bug 1323967.

However, the command "sudo ubuntu-drivers autoinstall" returns the message:
"No dirvers found for automatic installation."

I've tried to use fglrx driver which works good on this system, ubuntu-drivers should be able to provide autoinstall the "Video driver for the AMD graphics accelerators", fglrx, to the user.

[1]: If you use dash->additional driver GUI, there will be a string "tested"

-------------------------------------------------------------------------

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-drivers-common 1:0.2.91.4
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: wl fglrx
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Wed May 28 03:04:33 2014
InstallationDate: Installed on 2014-05-28 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: ubuntu-drivers-common
UpgradeStatus: No upgrade log present (probably fresh install)

[Alberto Milone (albertomilone)]

We cannot autoinstall the fglrx driver on a per device base. Either we install it for all the supported AMD cards, or we don't. The latter is our current policy. The open radeon driver usually works well enough (hence we use it by default).

LP: #1323967 simply shows that the system is using software rendering. This means that probably the open 3D driver that we ship doesn't support that GPU.

Please attach /var/log/Xorg.0.log and the output of dmesg in that bug report and let's try to fix that bug instead.

I'm marking this as "won't fix".

[Taihsiang Ho (tai271828)]

Please refer to LP: #1401864
I think there is no such issue and it is worthy to verify this bug again.