<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:RalfPeter.Rohbeck@quantum.com" title="Ralf-Peter Rohbeck <RalfPeter.Rohbeck@quantum.com>"> <span class="fn">Ralf-Peter Rohbeck</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - radeonsi & glamor: No acceleration"
href="https://bugs.freedesktop.org/show_bug.cgi?id=59703">bug 59703</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>INVALID
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - radeonsi & glamor: No acceleration"
href="https://bugs.freedesktop.org/show_bug.cgi?id=59703#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - radeonsi & glamor: No acceleration"
href="https://bugs.freedesktop.org/show_bug.cgi?id=59703">bug 59703</a>
from <span class="vcard"><a class="email" href="mailto:RalfPeter.Rohbeck@quantum.com" title="Ralf-Peter Rohbeck <RalfPeter.Rohbeck@quantum.com>"> <span class="fn">Ralf-Peter Rohbeck</span></a>
</span></b>
<pre>OK one crash and one hang with fglrx 13.1 today gave me a lot of incentive to
work some more on this.
I got it to work! It seems that the root cause was that the old X server didn't
pick up the config files from /opt/xorg/share/X11/xorg.conf.d correctly. Once I
cat'd them all to /etc/X11/xorg.conf and got rid of the -configdir argument for
X things became much better. Thanks all! You got me on the right track.
Observations:
The whole thing hung hard immediately with Dave Airlie's 3.8rc4 drm-next kernel
but with 3.7 it works mostly.
DRM/KMS with 2560x1440 monitors on DP->DVI adapters doesn't work correctly. The
monitors were detected with the wrong resolution (1024x768) even after I
hardwired them on the kernel command line with video=DP-1:2560x1440-24@60e
video=DP-2:2560x1440-24@60e.
The only thing that worked was to hardwire the modeline in xorg.conf but xrandr
-q still thinks they can do other modes than 2560x1440 (they don't):
DisplayPort-0 connected 1440x2560+3360+0 right (normal left inverted right x
axis y axis) 0mm x 0mm
2560x1440 60.0*+
1024x768 60.0
800x600 60.3 56.2
848x480 60.0
640x480 59.9
However the monitor detection/mode switching code in the Atom BIOS is broken in
general for DP outputs. Not even the BIOS switches modes correctly when these
monitors are connected. I had a long and fruitless exchange with AMD tech
support about this. Now the monitors are still not detected reliably but
switching to a text console and back gets them all up after a couple of tries.
KDE decorations don't look quite right (default theme, XRender or OpenGL.) I'll
attach a screenshot.
Every now and then the display freezes for a moment. During that time the
migration process is very busy, often with over 200% CPU and several threads.
This can be triggered by switching KDE desktop effects on/off (Shift-Alt-F12.)
Doing that also leaves some garbage on the screen.
Other than that, I have messed around for a while and haven't seen a crash yet.
So far so good :)</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>