package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build this problem exists since i updated the kernel few months ago
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fglrx-installer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
from update manager it calls exit code 10. and shows me the both packages fglrx and fglrx-amd.....
perhaps this has something to do with the issue i tried to reinstall the driver from ati-grafiks wich did not do its work propably. well now it seems that some old parts are remaining and block new stuff coming in.
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5
ProcVersionSign
Uname: Linux 2.6.32-32-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Wed Jul 27 19:35:40 2011
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: Hewlett-Packard HP 625
PackageVersion: 2:8.723.1-0ubuntu5
ProcCmdLine: BOOT_IMAGE=
SourcePackage: fglrx-installer
Title: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build
dmi.bios.date: 08/13/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68DVA Ver. F.03
dmi.board.
dmi.board.name: 1475
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 72.0E
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP 625
dmi.sys.vendor: Hewlett-Packard
glxinfo: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 2.6.32-32-generic
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.