[Hardy Alpha-4] xserver-xorg can't start with ATI Radeon X1200

I have the same problem but not exactly the same ATI

I also had problems with xorg on a Radeon. Mine is a Radeon Mobility 7000 IGP.

What would happen is that upon loading GDM, the screen would go black, with some garbled output at the top of the screen. I did get a cursor and I could move it.
If I tried to kill the X server by Ctrl-Alt-Backspace, or I tried to switch to a terminal, the screen would hang, although I could still reboot using Ctrl-Alt-Del. Is this the same behaviour as you are seeing?

My problem was solved by installing new ati drivers from this page:
https://wiki.ubuntu.com/XorgOnTheEdge
Maybe this i worth a try for you too?

Regards,
Jeroen

I have a different problem. I couldn't get gdm to load. There wasn't garbled output.

It will use USplash in the beginning. The screen will go black and switch the boot up messages (in text not USplash) and back for while, then it stopped to that boot up messages.

It stops and is shows this on the screen.
* Starting defined execution scheduler atd [OK]
* Starting periodic command scheduler crond [OK]
* Checking battery state... [OK]
* Running local boot scripts (/etc/rc.local) [OK]

I can confirm this.
I have a brand-new Asus G1 with the following specs:

# Screen: 15.4" WSXGA+ (1680x1050) ColorShine
# Graphics: NVIDIA GeForceGo 7700 GPU 512 MB

Tried installing Hardy Studio Alpha 4 -- nothing.

Oddly, running
dpkg-reconfigure xserver-xorg
does not bring up screens so that I can change any of the monitor attributes.
The file xorg.conf contains only a bit of generic information.

Ubuntu Hardy i386 2.6.24-7.12-generic

lspci -nn | grep VGA
01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RS485 [Radeon Xpress 1100 IGP] [1002:5975]

I can confirm this on a Dell 1501. Enable ATI driver with from "Hardware Drivers" and reboot. Usplash appears as expected. After usplash finishes screen goes blank and is unresponsive to everything but a hard reboot. Reboot with failsafe and fix X works, but you're back with the Mesa driver then. This is a major regression. No problems of this sort in Gutsy.

If there is any thing else that I can supply please ask.

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 #174434, 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.

I don't really think that this is a duplicate. Bug #174434 describes no generation of xorg.conf.failsafe. That is not my issue. That file is generated. I can boot up fine if I use the Mesa driver. The problem is when trying to enable the restricted ATI driver. Attached is my xorg.conf.failsafe

Andrew, since this bug has been reported by Pratik, and his issue looks like just the same as the ones report in Bug #174434 (and other duplicates), I believe this is a duplicate too. Maybe you would like to report a different bug for your problem?

This isn't a duplicate of Bug #174434

Pratik, what makes you think it isn't a duplicate? The symptoms are the same, and you all have a X1xxx series radeon.

I thought I had to have this screen pop up http://launchpadlibrarian.net/11128838/DSC_0001.JPG to have that problem, but all the other symptoms happened. I also thought, It shouldn't have created the xorg.conf.failsafe file, if it was the same problem.

Ah, well there was another problem earlier in hardy which resulted in that dialog, but the underlying problem is the same.