If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

phoen1x, is that ticket #1700 you're talking about on ati.cchtml.com ? If so, that ticket was reported as debian-only and the debian ticket containing the info was subsequently closed because the debian devs felt it was a kernel issue (mucked up MTRRs).

Any chance you could confirm the problem also occurs on a supported distro (maybe try Ubuntu 9.10) and update the ticket ?

I can confirm that this is not debian only bug. It doesn't depend on distribution, tested on ubuntu 9.04/9.10, archlinux and gentoo. The problem now is i got only gentoo and yesterday i tried cat 10.6 and still blank screen as usual xorg.log shows nothing suspicious. I tested cat 9.4-10.6, all versions higher than 9.8 just dont work and kernel version really doesn't matter, i tried 2.6.28-2.6.33 (even 2.6.34rc). Should i fill bug report? Bug #1794 perfectly describes problem.

I have to say I was pleasantly surprised by this new driver! I'm using a supported OS (openSUSE 11.2) but I've installed some extra libraries that aren't standard in the distro, namely Kernel 2.6.33, libdrm 2.4.21 and a few others I can't remember right now, although I'm still using xorg-server 7.4. I just build a package from the list of distros (SuSE/SUSE 11.2), but I wasn't hoping for much due to the upgraded kernel and not being sure if SUSE was referring to openSUSE or the commercial variant. The package build fine and I installed it, again with no errors to my big surprise. I just assumed that it would probably break my system on reboot since so far it had been a pleasant process. But once again my expectations weren't met and the damn thing worked fine and booted nicely.

By this time I was thinking that something HAD to be wrong, since I haven't had such a trouble free graphics driver installation process since the days I had a geforce4. I tried a few 3D apps and desktop effects and all worked great. So I have to say this is the best catalyst release yet for me and it is working perfectly... almost! After I changed the screen mode in the CCC everything also worked fine, until the next time I booted the system. This time it was more like a real catalyst driver and X wouldn't start. Some complaint about a ModeLine that was expecting H"something". Turns out that in each ModeLine line the first number after the mode name ("1600x1200") was like this -> 217,0 and xorg was expecting only integers so I had to manually delete the ",0" from every line to be able to boot into X. Why did this happen? I did an aticonfig --initial as was stated and everything was working perfectly until this. Why?? I suppose that CCC added those unnecessary ",0" to each number, I just don't understand why...

Anyway, it's not news that there are problems installing the catalyst drivers, and this was an easy one to solve, but it's a shame this still isn't a flawless victory for the driver. Maybe next month

Just to add to the discussion, very similar setup (HD5770, Nforce 430, 64-bit Ubuntu, mobo: Asus M2NPV-VM, btw just upgraded to the last BIOS available, as per Bridgman suggestion) same negative experience (black screen / hanging). I'll append my mtrr too, who knows..

long story:
I installed 10.6 yesterday starting ati-driver-installer-10-6-x86.x86_64.run from a konsole with su. I use the same xorg.conf since many Catalyst versions, so I let the file untouched and rebooted the PC. Everything worked fine.

Then I connected a projector to the second DVI port of my HD3850. amdcccle told me to run it with su privileges to be able to change screen settings. (that will bring me to a second question, later)
I run amdcccle as su and could activate the clone mode for both screens. I also wanted to change the resolution to 1280x720 to fit the projector but amdcccle told me that I have to reboot for this change. So I let the resolution at 1280x1024 because I just wanted to watch a DVD and go to bed.
Today I switched on my PC and it booted to text mode instead of KDE login.
My xsession-errors are here: http://pastebin.org/342355
After changing all "," back to "." manually my X started.