X11 does not start with glx enabled (ATI Radeon HD 4670)

[Jan-Niklas Meier]

Binary package hint: xorg

When i boot Ubuntu without an /etc/X11/xorg.conf the screen gets black before the GDM login screen. The graphics card doesn't provide any output and i am not able to switch to a console. I think the driver brings the card into a bad state so output is deactivated.
If i create a xorg.conf with a deactivated glx extension in can start normal and of course i don't have 3D acceleration. Is the fglrx driver not working yet? At least i was able to install it and i think this should not bring up this situation.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: fglrx 2:8.723.1-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic x86_64
Architecture: amd64
Date: Sat Sep 11 15:39:49 2010
DkmsStatus:
 fglrx, 8.723.1, 2.6.32-24-generic, x86_64: installed
 virtualbox-ose, 3.2.8, 2.6.35-20-generic, x86_64: installed
GdmLog1:

InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
MachineType: Gigabyte Technology Co., Ltd. GA-MA785GMT-UD2H
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-20-generic root=UUID=b227180f-836e-4fc5-b31e-49bb6378fae4 ro single pci=noacpi
ProcEnviron:
 LANG=de_DE.utf8
 SHELL=/bin/bash
SourcePackage: fglrx-installer
XorgLogOld:

dmi.bios.date: 09/16/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F3
dmi.board.name: GA-MA785GMT-UD2H
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.:bvrF3:bd09/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA785GMT-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA785GMT-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA785GMT-UD2H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
glxinfo:
 Error: command ['glxinfo'] failed with exit code -11: Xlib: extension "GLX" missing on display ":0.0".
 Xlib: extension "GLX" missing on display ":0.0".
 Xlib: extension "GLX" missing on display ":0.0".
 Xlib: extension "GLX" missing on display ":0.0".
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-20-generic

[Jan-Niklas Meier (dschanoeh)]

I just found out that this was caused by the fglrx packets leftover from the Lucid installation. After the upgrade they were still present and caused this bug. Removing all of them and deleting the xorg.conf solves the problem for me. Is this still an issue (for people who want to upgrade) or may i close the bug?

[bugbot (bugbot)]

Hey Jan-Niklas,

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.