Ubuntu
fglrx-installer package

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

Bug #906915 reported by patrick on 2011-12-20

This bug report is a duplicate of: Bug #601447: package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: fglrx kernel module failed to build [Error: kernel includes at ... do not match current kernel. they are versioned as "" instead of "2.6.32-23-generic". you might need to adjust your symlinks: ...]. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	fglrx-installer (Ubuntu)	New	Undecided	Unassigned

Bug Description

Crash report raised while installing "linux-image-generic-lts-backport-oneiric"and "linux-headers-generic-lts-backport-oneiric" in ubuntu 10.04.03.

Laptop Dell M101z, Ram 3 Gb, HD 250 Gb, Amd Athlon neo K325 (dual core)
Using proprietary drivers Broadcom STA (wireless) and ATI/AMD fglrx (graphics driver)

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-36.79-generic 2.6.32.46+drm33.20
Uname: Linux 2.6.32-36-generic i686
NonfreeKernelModules: fglrx wl
Architecture: i386
Date: Tue Dec 20 14:32:10 2011
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
MachineType: Dell Inc. Inspiron 1120
PackageVersion: 2:8.723.1-0ubuntu5
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-36-generic root=UUID=bafa7955-74f9-4ce5-9ba2-bc4d122e790f ro gfxpayload=keep quiet splash noapic
SourcePackage: fglrx-installer
Title: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build
dmi.bios.date: 06/18/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.asset.tag: 1234567890
dmi.board.name: 090DNY
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.asset.tag: 1234567890
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A02
dmi.modalias: dmi:bvnDellInc.:bvrA02:bd06/18/2010:svnDellInc.:pnInspiron1120:pvrA02:rvnDellInc.:rn090DNY:rvrA02:cvnDellInc.:ct8:cvrA02:
dmi.product.name: Inspiron 1120
dmi.product.version: A02
dmi.sys.vendor: Dell Inc.
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-36-generic

Tags:

Revision history for this message

patrick (p-rahari) wrote on 2011-12-20:

BootDmesg.txt Edit (41.7 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (7.2 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (457 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (4.6 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (20.3 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (424 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1016 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.4 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (115.2 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (256.7 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (290 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (23.5 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (24.2 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (3.2 KiB, text/plain; charset="utf-8")
make.log.txt Edit (753 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (21.4 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (57.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2011-12-21:

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.