[fglrx] X1650 black screen, system freeze and crash

[Julius Vitkauskas]

Xorg with fglrx crashes with X1650. Screen goes
black. Keyboard becomes unresponsive. System
is thoroughly hung and requires hard reset to recover. Works with vesa driver only. I am using DVI connection.

I've discussed this problem in mandriva:
http://forum.mandriva.com/viewtopic.php?p=430804

Other bug reports in unofficial ati bugtracker:
http://ati.cchtml.com/show_bug.cgi?id=1015
http://ati.cchtml.com/show_bug.cgi?id=910

[Julius Vitkauskas (julius-vitkauskas)]

I've also submited bug report to ati linux driver feedback (ati doesn't provide online support and says their driver is developed "as-is").

I would like to know if somebody knows any workaround.

[David Mills (d-mills)]

Hello and thank you for your feedback.

In order to help us diagnose your problem, could you please attach your /var/log/dmesg and /var/log/Xorg.0.log files from right after a crash?

Thank you

[Julius Vitkauskas (julius-vitkauskas)]

/var/log/dmesg right after a crash attached.
It appears that no /var/log/Xorg.0.log is created after the crash (I've deleted /var/log/Xorg.0.log before booting, booted got black screen and freeze, then did hard reset) :(

[Timo Aaltonen (tjaalton)]

Please don't add random tags, there are too many anyway for them to be useful.

[Timo Aaltonen (tjaalton)]

Make sure you have "DefaultDepth 24" in the Screen section.

[Julius Vitkauskas (julius-vitkauskas)]

Yes i have. I have attached my current xorg.conf

[Julius Vitkauskas (julius-vitkauskas)]

Sorry about 7z format attachment, here's gzip'ed xorg.conf

[Bryce Harrington (bryce)]

Please attach files without compressing them; it makes it harder to review them.

[Bryce Harrington (bryce)]

Also, you still need to attach a /var/log/Xorg.0.log (or Xorg.0.log.old) from right after a crash.

Can you ssh into the box when it is locked up, attach gdb, and get a full backtrace? For directions, see https://wiki.ubuntu.com/DebuggingXorg.

Obviously, we won't get any useful backtrace info from fglrx since it's closed source, but if it's an X issue rather than fglrx it would be useful, and if not then the surrounding X calls should give us some clues.

[Bryce Harrington (bryce)]

Heya zolookas,

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.