failed to load module fglrx on ATI Radeon RS880

Bug #573311 reported by Murz on 2010-05-01
This bug affects 3 people
Affects Status Importance Assigned to Milestone
fglrx-installer (Ubuntu)

Bug Description

After upgrade from Karmic to Lucid I can't use fglrx driver.
Graphics card: ATI Technologies Inc RS880 [Radeon HD 4200]

I have successfully install fglrx and other related packages.
If I boot xorg without xorg.conf, it loads the ati driver without compositing support.
If I try to create xorg.conf with driver=fglrx, I see the error on startx:
(EE) Failed to load module "fglrx" (module does not exist, 0)
(EE) No drivers available.

but I see the fglrx module loaded:
$ lsmod | grep fglrx
fglrx 2353422 0

I try to purge and reinstall all fglrx-related packages, but this isn't help.

If I use "Hardware Drivers" utility, I see the "ATI Fire GL" as activated, deactivating and activating again didn't help.

What I can try more for solve this bug?
I can give you any additional info about my configuration, if needed.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Sun May 2 01:54:45 2010
GdmLog1: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory
GdmLog2: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=c4598b85-895e-4b22-8a01-0a9e73822e1c ro quiet splash elevator=deadline
SourcePackage: fglrx-installer 08/31/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0501
dmi.board.asset.tag: To Be Filled By O.E.M. M4A785T-M
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd08/31/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785T-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-21-generic

Murz (murznn) wrote :
Murz (murznn) wrote :
Murz (murznn) wrote :
Murz (murznn) wrote :

I have attached a 'startx' output and xorg.conf that was active at this moment.

Murz (murznn) wrote :

I have created an additions bug report #573322 from console after trying to load fglrx and got the error for give you an additional info.
And mark it as duplicate of this.

starslights (starslights) wrote :


I run a fresh install of kubuntu Lucid 10.04 on x86 64 and i have the same bug with Nvidia Driver.

I make the update and right after booting, i wasn't able to restart anymore.

Failed to load module Nvidia.

After that the only was to reformat, So i am waiting before install any graphic drivers , since it look a serious bugs.

Any idea for a workaround welcome in case i have same problem again.

Linux xxxxx 2.6.32-21-generic #32-Ubuntu SMP Fri Apr 16 08:09:38 UTC 2010 x86_64 GNU/Linux .

The bug wasn't appear with this Kernel, because i wait to update again .

Best regards

Montblanc (montblanc) wrote :

This bug is affecting me too, on Natty, with the same hardware (on a HP P3135 AX250). The only thing I thought could be the problem might be the way the BIOS is sharing video memory. It is reported to work with UMA or UMA + Sideport, but I think it's using Sideport only and I can't change these options in the BIOS, I can't even see them as options. Moreover, there is no BIOS update, and there won't be any.

Changed in fglrx-installer (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers