It might be useful to install xserver "dbg" packages (search for dpkg in synaptic and install X related dbg packages), then use gdb as instructed on http://www.x.org/wiki/Development/Documentation/ServerDebugging from another machine and get a backtrace. This is of course only if you think you know how to follow those instructions.
Please note that again traces etc. when using fglrx driver are next to useless, since those bugs can only be fixed by AMD.
I'm also fairly sure that various people reporting in this bug have different kind of bugs with their specific ATI models / hardware combinations. As for the open source ati driver, I myself am running them without any problems on a Mobility Radeon 9000 (a laptop) and a Radeon X800 GTO PCI-E card (a desktop computer).
It might be useful to install xserver "dbg" packages (search for dpkg in synaptic and install X related dbg packages), then use gdb as instructed on http:// www.x.org/ wiki/Developmen t/Documentation /ServerDebuggin g from another machine and get a backtrace. This is of course only if you think you know how to follow those instructions.
Please note that again traces etc. when using fglrx driver are next to useless, since those bugs can only be fixed by AMD.
I'm also fairly sure that various people reporting in this bug have different kind of bugs with their specific ATI models / hardware combinations. As for the open source ati driver, I myself am running them without any problems on a Mobility Radeon 9000 (a laptop) and a Radeon X800 GTO PCI-E card (a desktop computer).