Ubuntu
fglrx-installer package

Unable to enable fglrx driver since updated to 2.6.38-8

Bug #780144 reported by Qazjap11 on 2011-05-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 have updated to kernel 2.6.38-8 using ubuntu ppa, and since I have done it, my graphic driver fglrx for my 4870 radeon refused to work or reinstall.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-8.42~lucid1-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Mon May 9 23:53:38 2011
DkmsStatus: fglrx, 8.723.1: added
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: Gigabyte Technology Co., Ltd. EP35-DS3L
PackageVersion: 2:8.723.1-0ubuntu5
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-8-generic root=UUID=48918cca-afec-4a70-9bbf-174d8cd1f0c0 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: 04/02/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F4
dmi.board.name: EP35-DS3L
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd04/02/2008:svnGigabyteTechnologyCo.,Ltd.:pnEP35-DS3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP35-DS3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: EP35-DS3L
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 2.6.38-8-generic

Tags:

Revision history for this message

Qazjap11 (qazjap11) wrote on 2011-05-09:

BootDmesg.txt Edit (56.7 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (9.0 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (459 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (4.5 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (15.6 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (17.7 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (17.7 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (27.4 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (710 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.0 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.3 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.0 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (133.7 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (262.3 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (188 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (18.9 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (22.4 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (8.0 KiB, text/plain; charset="utf-8")
make.log.txt Edit (459 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (267 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (4.2 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (63.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Felix Kuehling (felix-kuehling) wrote on 2011-05-09:

You need Catalyst 11.4 or newer (fglrx 8.84 or newer) to support kernel version 2.6.38.

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2011-07-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 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.