package fglrx 2:8.771-0ubuntu1 failed to install/upgrade: fglrx kernel module failed to build

[Scott]

Failed driver installation

ProblemType: Package
DistroRelease: Ubuntu 10.10
Package: fglrx 2:8.771-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
DRM.card0.HDMI_Type_A.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1366x768 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480
 edid-base64: AP///////wAw5AHPAAAAAAASAQOAIhN4Cqu1n1lUliYWUFQAAAABAQEBAQEBAQEBAQEBAQEBPhxWoFAAFjAwIDUAWMIQAAAZAAAAAAAAAAAAAAAAAAAAAAAAAAAA/gBMRyBEaXNwbGF5CiAgAAAA/ABMUDE1NldIMi1UTEUxANw=
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
Date: Fri Oct 8 07:52:55 2010
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
MachineType: Gateway NV53
PackageVersion: N/A
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=0ae9779c-cd33-4e9c-aa94-0075eed1c3dc ro quiet splash
SourcePackage: fglrx-installer
Title: package fglrx 2:8.771-0ubuntu1 failed to install/upgrade: fglrx kernel module failed to build
dmi.bios.date: 10/22/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.04
dmi.board.name: SJV50TR
dmi.board.vendor: Gateway
dmi.board.version: Rev
dmi.chassis.type: 10
dmi.chassis.vendor: Gateway
dmi.chassis.version: None
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.04:bd10/22/2009:svnGateway:pnNV53:pvr0100:rvnGateway:rnSJV50TR:rvrRev:cvnGateway:ct10:cvrNone:
dmi.product.name: NV53
dmi.product.version: 0100
dmi.sys.vendor: Gateway
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-22-generic

[Brian Murray (brian-murray)]

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 671868, 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.