Ubuntu
fglrx-installer package

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

Bug #755756 reported by Balazs Oveges on 2011-04-09

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

I just installed kernel 2.6.38 from Ubuntu PPA to get my USB dvb-T tuner working.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-30.59-generic 2.6.32.29+drm33.13
Uname: Linux 2.6.32-30-generic i686
NonfreeKernelModules: fglrx
Architecture: i386
Date: Sat Apr 9 21:27:23 2011
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-7253
PackageVersion: 2:8.723.1-0ubuntu5
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-30-generic root=UUID=67669130-9924-41cc-ad15-95a400beba5e ro quiet splash
SourcePackage: fglrx-installer
Title: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build
dmi.bios.date: 09/01/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: MS-7253
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.board.version: 1.00
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/01/2006:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7253:pvr1.00:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7253:rvr1.00:cvn:ct3:cvr:
dmi.product.name: MS-7253
dmi.product.version: 1.00
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-30-generic

Tags:

Revision history for this message

Balazs Oveges (ovegesb) wrote on 2011-04-09:

BootDmesg.txt Edit (39.5 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (3.3 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (476 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (4.5 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (414 bytes, text/plain; charset="utf-8")
GdmLog.txt Edit (19.4 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (18.9 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (18.9 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (24.8 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (467 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.8 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.8 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (108.8 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (220.8 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (188 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (24.4 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (23.8 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (7.9 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (18.3 KiB, text/plain; charset="utf-8")
make.log.txt Edit (476 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (329 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (21.3 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (64.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Robert Roth (evfool) wrote on 2011-04-22:

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 #751177, 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.