dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71051] Cannot suspend with radeon drivers.
Date: Sat, 20 Sep 2014 05:04:06 +0000	[thread overview]
Message-ID: <bug-71051-2300-9pLscPiE20@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-71051-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=71051

--- Comment #13 from Hin-Tak Leung <htl10@users.sourceforge.net> ---
(In reply to Michel Dänzer from comment #12)
> (In reply to Hin-Tak Leung from comment #11)
> > photo of the double-pointer corruption
> 
> Looks like you're using an old version of xf86-video-modesetting, or another
> generic driver which doesn't correctly handle 128x128 hardware cursors.
> Please use the radeon driver from a current version of xf86-video-ati; with
> glamor enabled, that also provides X-Video support.

Thanks for the hints! Bringing drv-ati,drv-modesetting,glamor up gives me the
correct cursor, and I get X-Video after bring mesa (and llvm) up - from
up-to-date fedora 20 to the not-yet-alpha fedora 21-ish.

The mouse cursor totally disappeared after GUI login in the first reboot (and I
had to use vt2 to reboot the system again) and video playback showed very
strange colors - almost B/W-ish - after the first X restart, but both wierdness
seems to be gone in later reboots, so far.

So as far as I am concerned, I just need attachment 150801 going upstream, and
possibly the hibernate cik_ring_test/radeon_dp_link_train_cr error issue looked
at. FWIW, I tested attachment 150801 against 3.16.2 (or rather, adapted
fedora's 3.16.2-200 to include the patch).

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2014-09-20  5:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-71051-2300@https.bugzilla.kernel.org/>
2014-02-24 12:22 ` [Bug 71051] Cannot suspend with radeon drivers bugzilla-daemon
2014-02-24 14:28 ` bugzilla-daemon
2014-02-24 15:33 ` bugzilla-daemon
2014-02-24 15:34 ` bugzilla-daemon
2014-02-24 15:46 ` bugzilla-daemon
2014-02-24 15:47 ` bugzilla-daemon
2014-09-18  8:32 ` bugzilla-daemon
2014-09-18 15:46 ` bugzilla-daemon
2014-09-18 15:47 ` bugzilla-daemon
2014-09-19  5:27 ` bugzilla-daemon
2014-09-19  5:30 ` bugzilla-daemon
2014-09-19  5:36 ` bugzilla-daemon
2014-09-19  8:50 ` bugzilla-daemon
2014-09-20  5:04 ` bugzilla-daemon [this message]
2014-10-07 21:32 ` bugzilla-daemon
2014-10-10 22:40 ` bugzilla-daemon
2015-01-23 21:05 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-71051-2300-9pLscPiE20@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).