[HD5450] Cannot load module fglrxdrm after xorg-driver-fglrx 2:8.723.1-0ubuntu3 update

Bug #569475 reported by Manuel Sanchez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fglrx-installer (Ubuntu)
New
Undecided
Unassigned

Bug Description

After updating xorg-driver-fglrx to 2:8.723.1-0ubuntu3, the machine previously exhibiting the behaviour described in bug #560570 (running 10.04 beta) now fails to load libfglrxdrm.so and reverts to vesa. I presume this is an update error unrelated to the problem defined in the other bug (driver hang), thus I'm submitting it as a new one.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xorg-driver-fglrx 2:8.723.1-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
NonfreeKernelModules: fglrx
Architecture: i386
CheckboxSubmission: 33a6ff8ffd30f8bd1df95c0b208fcb87
CheckboxSystem: 6ce041aeed0a2c17b3343b66d157175d
Date: Sat Apr 24 17:31:37 2010
DkmsStatus: fglrx, 8.723.1, 2.6.32-21-generic, i686: installed
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
MachineType: HP-Pavilion RR498AA-ABU s7720.uk
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=31fcdf37-c8d7-4b82-be95-905814e9201d ro quiet splash
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: fglrx-installer
dmi.bios.date: 12/18/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.03
dmi.board.name: Hematite
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 1.00
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: 1111
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.03:bd12/18/2006:svnHP-Pavilion:pnRR498AA-ABUs7720.uk:pvr:rvnASUSTekComputerINC.:rnHematite:rvr1.00:cvnHewlett-Packard:ct3:cvr1111:
dmi.product.name: RR498AA-ABU s7720.uk
dmi.sys.vendor: HP-Pavilion
glxinfo: Error: command ['glxinfo'] failed with exit code -11:
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-21-generic

Revision history for this message
Manuel Sanchez (manuel-antonio-sanchez) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.