X does not start after 8/22 fglrx update

This is the old xorg.conf that works.

This is the new xorg.conf that causes the xserver crash. System>Administration>Screens and Graphics creates this xorg.conf so it maybe not be the update script that did it.

I too experience this bug. I have an ATI Radeon xpress 200 (RS480), and when I enable fglrx through the restricted drivers manager, and restart X, the screen will flicker for several moments and then dump me into failsafe mode. I copied my xorg.conf file over from my working Feisty install, and it works as expected.

I have the same problem here with Radeon 9550. I fixed it by booting with Live CD, chroot to my root partition and aticonfig -f --initial --overlay-type=Xv.

The annoying thing is that sometimes KDE loses its screen resolution settings, jumps to highest possible (i.e. unusable) resolution and when I change back in System Settings, a broken xorg.conf is generated again.

I attach kdm.log, the broken xorg.conf and working xorg.conf.

Oops, the linux-restricted-modules package is already at version 2.6.22-14. Anyway, the bug is more likely in the program that generates xorg.conf.

Is this symptom still reproducible in 8.10 beta or later?

[This is an automated message]

As of Intrepid (8.10), we have a dedicated package 'fglrx-installer' for fglrx bugs, which now includes a process for upstreaming bugs to AMD.

  http://bugs.launchpad.net/ubuntu/+source/fglrx-installer

To transition your bug into the new fglrx-package, we need your help. Please do the following:

 a. Verify the bug occurs in Intrepid.
     (Intrepid ISOs: http://cdimage.ubuntu.com)
 b. If you haven't already, please include in the bug:
     * Your /var/log/Xorg.0.log
     * The output of `lspci -vvnn`
     * Steps to reproduce the issue
 c. Click 'Also affects distribution'
 d. Set 'Source Package Name' to 'fglrx-installer'
 e. Click Continue

Thank you. This will assist us in reviewing and upstreaming your fglrx bug, as appropriate.

[We'll expire the fglrx bugs in l-r-m-* in a month or so.]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!