package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: fglrx kernel module failed to build

[Ste4lth]

Trying to do a routine update. Errors like crazy were thrown at me, this one including.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Tue Jun 22 12:02:04 2010
DkmsStatus:
 vboxnetadp, 3.2.0, 2.6.32-22-generic, x86_64: installed
 vboxdrv, 3.2.0, 2.6.32-22-generic, x86_64: installed
 fglrx, 8.723.1: added
 vboxnetflt, 3.2.0, 2.6.32-22-generic, x86_64: installed
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: Hewlett-Packard HP G61 Notebook PC
PackageVersion: 2:8.723.1-0ubuntu4
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=381e7e16-3cd0-4a91-b2f2-5c781bdc3bda ro quiet splash
SourcePackage: fglrx-installer
Title: package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: fglrx kernel module failed to build
dmi.bios.date: 09/18/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.04
dmi.board.name: 363F
dmi.board.vendor: Quanta
dmi.board.version: 42.13
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.04:bd09/18/2009:svnHewlett-Packard:pnHPG61NotebookPC:pvr0393100000210C10000020000:rvnQuanta:rn363F:rvr42.13:cvnQuanta:ct10:cvrN/A:
dmi.product.name: HP G61 Notebook PC
dmi.product.version: 0393100000210C10000020000
dmi.sys.vendor: Hewlett-Packard
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-22-generic

[Jean-Baptiste Lallement (jibel)]

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 596805, 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. Please continue to report any other bugs you may find.