fglrx (not installed): fglrx kernel module failed to build

[Vaibhav Malawade]

ATI properitary driver fglrx-13.300

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: fglrx 2:13.300-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDmesg:

DKMSKernelVersion: 3.13.0-32-generic
Date: Thu Aug 7 11:18:21 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 blackmagic, 10.1.1a26, 3.13.0-32-generic, x86_64: installed
 blackmagic-io, 10.1.1a26, 3.13.0-32-generic, x86_64: installed
 fglrx, 13.300: added
 v4l2loopback, 0.8.0, 3.13.0-32-generic, x86_64: installed
DuplicateSignature: dkms:fglrx:(not installed):/var/lib/dkms/fglrx/13.300/build/2.6.x/kcl_acpi.c:796:59: error: ‘struct acpi_dev_node’ has no member named ‘handle’
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 200 Series] [1002:130f] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:85cb]
InstallationDate: Installed on 2014-07-23 (15 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
LightdmGreeterLog: ** (lightdm-gtk-greeter:1750): WARNING **: Failed to load user image: Failed to open file '/home/vaibhav/.face': No such file or directory
LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1769): WARNING **: Failed to load user image: Failed to open file '/home/vaibhav/.face': No such file or directory
MachineType: System manufacturer System Product Name
PackageVersion: (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=95d3dc87-9965-437b-ab9d-89f7011e5f9d ro quiet splash vt.handoff=7
SourcePackage: fglrx-installer
Title: fglrx (not installed): fglrx kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/30/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0703
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A88X-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd12/30/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88X-PRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56+git20140801.5d835797-0ubuntu0sarvatt~trusty
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0~git20140805.fc2b2d33-0ubuntu0sarvatt2~trusty
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0~git20140805.fc2b2d33-0ubuntu0sarvatt2~trusty
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914+git20140806.105d478c-0ubuntu0sarvatt~trusty
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10+git20140806.edd1608c-0ubuntu0sarvatt~trusty
xserver.bootTime: Thu Aug 7 11:08:08 2014
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2
xserver.video_driver: radeon

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1254424, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.