<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - ati driver: modesetting not supported"
href="https://bugs.freedesktop.org/show_bug.cgi?id=63617#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - ati driver: modesetting not supported"
href="https://bugs.freedesktop.org/show_bug.cgi?id=63617">bug 63617</a>
from <span class="vcard"><a class="email" href="mailto:russ@ashlandhome.net" title="Russ Whitaker <russ@ashlandhome.net>"> <span class="fn">Russ Whitaker</span></a>
</span></b>
<pre>On Wed, 17 Apr 2013, <a href="mailto:bugzilla-daemon@freedesktop.org">bugzilla-daemon@freedesktop.org</a> wrote:
<span class="quote">>
> <a href="show_bug.cgi?id=63617#c3">Comment # 3</a> on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - ati driver: modesetting not supported"
href="show_bug.cgi?id=63617">bug 63617</a> from Michel Dänzer
>
> Please attach the output of dmesg from after X failed to start.
> </span >
Attached.
This box boots to a command line. "startx," and after, did not add
anything to dmesg.
I have a hunch: modesetting is done someplace else and the results
passed to the ati driver. The new ati driver requires modesetting to
work, and work properly. Here, modesetting hasn't worked right in years.
For example, with the vesa driver I get one mode that works; the rest
looks like giant backslashes.
Incidently, slackware-current went back to xorg-server-1.13.4
Tried it: still same problem.
Russ</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>