package fglrx 2:8.723.1-0ubuntu5 [modified: usr/lib/fglrx/bin/atiodcli usr/lib/fglrx/bin/fglrx_xgamma usr/lib/fglrx/libfglrx_gamma.so.1.0 usr/lib/fglrx/libGL.so.1.2 usr/lib/fglrx/libatiuki.so.1.0] failed to install/upgrade: fglrx kernel module failed to build
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fglrx-installer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
how to solve it
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5 [modified: usr/lib/
ProcVersionSign
Uname: Linux 2.6.32-
Architecture: i386
CurrentDmesg:
[ 20.376471] ppdev: user-space parallel port driver
[ 27.181789] eth0: no IPv6 routers present
Date: Sat Jan 8 10:23:36 2011
DkmsStatus: fglrx, 8.723.1, 2.6.32-
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
Lsusb:
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: PCCHIPS P25G
PackageVersion: 2:8.723.1-0ubuntu5
ProcCmdLine: BOOT_IMAGE=
SourcePackage: fglrx-installer
Title: package fglrx 2:8.723.1-0ubuntu5 [modified: usr/lib/
dmi.bios.date: 06/17/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: P4M800-8237
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: P25G
dmi.sys.vendor: PCCHIPS
glxinfo: Error: command ['glxinfo'] failed with exit code -11:
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-
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 555957, 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.