package fglrx 2:8.723.1-0ubuntu6 failed to install/upgrade: fglrx kernel module failed to build
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fglrx-installer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
dkms_autoinstaller for fglrx failed with status = 10.
un 13 18:14:39 alages dkms_autoinstaller: fglrx (8.723.1): Installing module on kernel 2.6.38-
Jun 13 18:14:48 alages dkms_autoinstaller: (bad exit status: 10)
Jun 13 18:14:48 alages dkms_autoinstaller: Build failed. Installation skipped.
Jun 13 18:14:49 alages dkms_autoinstaller: fglrx (8.723.1): Installing module on kernel 2.6.38-
Jun 13 18:14:58 alages dkms_autoinstaller: (bad exit status: 10)
Jun 13 18:14:58 alages dkms_autoinstaller: Build failed. Installation skipped.
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu6
ProcVersionSign
Uname: Linux 2.6.32-
NonfreeKernelMo
Architecture: i386
Date: Wed Jun 13 18:14:55 2012
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release i386 (20110211.3)
MachineType: LENOVO 8810AA5
PackageVersion: 2:8.723.1-0ubuntu6
ProcCmdLine: BOOT_IMAGE=
SourcePackage: fglrx-installer
Title: package fglrx 2:8.723.1-0ubuntu6 failed to install/upgrade: fglrx kernel module failed to build
dmi.bios.date: 12/12/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 2JKT49ABR
dmi.board.name: LENOVO
dmi.board.vendor: LENOVO
dmi.board.version: NONE
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 8810AA5
dmi.product.
dmi.sys.vendor: LENOVO
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-
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 601447, 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.