fglrx (not installed): fglrx kernel module failed to build
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fglrx-installer (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
ser@ser-M51Vr ~/catalyst12.8 % sudo dpkg -i fglrx*.deb
(Lecture de la base de données... 311323 fichiers et répertoires déjà installés.)
Dépaquetage de fglrx (à partir de fglrx_8.
Sélection du paquet fglrx-amdcccle précédemment désélectionné.
Dépaquetage de fglrx-amdcccle (à partir de fglrx-amdcccle_
Sélection du paquet fglrx-dev précédemment désélectionné.
Dépaquetage de fglrx-dev (à partir de fglrx-dev_
Paramétrage de fglrx (2:8.982-0ubuntu1) ...
update-
update-
update-
update-
update-
update-initramfs: deferring update (trigger activated)
Loading new fglrx-8.982 DKMS files...
First Installation: checking all kernels...
Building only for 3.5.0-15-generic
Building for architecture i686
Building initial module for 3.5.0-15-generic
Error! Bad return status for module build on kernel: 3.5.0-15-generic (i686)
Consult /var/lib/
update-initramfs: deferring update (trigger activated)
Traitement des actions différées (« triggers ») pour « ureadahead »...
ureadahead will be reprofiled on next reboot
Traitement des actions différées (« triggers ») pour « bamfdaemon »...
Rebuilding /usr/share/
Paramétrage de fglrx-amdcccle (2:8.982-0ubuntu1) ...
Paramétrage de fglrx-dev (2:8.982-0ubuntu1) ...
Traitement des actions différées (« triggers ») pour « initramfs-tools »...
update-initramfs: Generating /boot/initrd.
Traitement des actions différées (« triggers ») pour « libc-bin »...
ldconfig deferred processing now taking place
ser@ser-M51Vr ~/catalyst12.8 %
ser@ser-M51Vr ~ % sudo aticonfig --initial -f
[sudo] password for ser:
aticonfig: No supported adapters detected
ser@ser-M51Vr ~ % fglrxinfo
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual!
Linux ser-M51Vr 3.5.0-15-generic #23-Ubuntu SMP Mon Sep 24 20:37:59 UTC 2012 i686 i686 i686 GNU/Linux
04:42:40 up 10 min, 3 users, load average: 0,71, 0,81, 0,52
ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: fglrx (not installed)
ProcVersionSign
Uname: Linux 3.5.0-15-generic i686
ApportVersion: 2.5.2-0ubuntu4
Architecture: i386
CompizPlugins: No value set for `/apps/
CompositorRunning: None
DKMSKernelVersion: 3.5.0-15-generic
Date: Tue Sep 25 04:41:10 2012
DistUpgraded: 2012-09-25 02:24:55,224 DEBUG enabling apt cron job
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus:
fglrx, 8.982: added
vboxhost, 4.1.20, 3.2.0-30-
vboxhost, 4.1.20, 3.2.0-31-
vboxhost, 4.1.20, 3.5.0-15-generic, i686: installed
GraphicsCard:
Advanced Micro Devices [AMD] nee ATI RV620 [Mobility Radeon HD 3400 Series] [1002:95c4] (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:1875]
InstallationMedia: Ubuntu 12.04 "Precise" - Build i386 LIVE Binary 20120426-12:41
MachineType: ASUSTeK Computer Inc. M51Vr
PackageVersion: (not installed)
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: fglrx-installer
Title: fglrx (not installed): fglrx kernel module failed to build
UnitySupportTest: Error: command ['/usr/
UpgradeStatus: Upgraded to quantal on 2012-09-25 (0 days ago)
dmi.bios.date: 11/17/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 211
dmi.board.
dmi.board.name: M51Vr
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: M51Vr
dmi.product.
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.8.
version.libdrm2: libdrm2 2.4.39-0ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
tags: | removed: need-duplicate-check |
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 1025488, 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.