From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 54381] [drm:radeon_atom_pick_pll] *ERROR* unable to allocate a PPLL
Date: Wed, 17 Jul 2013 14:22:20 +0000 [thread overview]
Message-ID: <bug-54381-2300-ATw3rtHCRu@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-54381-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=54381
Andrew Stubbs <ams@codesourcery.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ams@codesourcery.com
--- Comment #8 from Andrew Stubbs <ams@codesourcery.com> ---
I seem to have the exact same problem. :(
I've been using 12.04, and earlier, in a 3 monitor setup for ages now, and I'm
really disappointed that it's stopped working with 13.04.
The clock description does ring true though because every now and again one of
my monitors would say "Signal out of range", and I would shrug my shoulders,
cycle it through the input settings, and it would work again.
Is there any way to hack the driver to get back the near-enough solution? It's
a bit dirty, but I'm not sure I want to shell out £250 to fix the problem the
clean way. Where would I look? Can you point me at the patch that "broke" it,
perhaps?
--
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
next prev parent reply other threads:[~2013-07-17 14:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-24 13:16 [Bug 54381] New: [drm:radeon_atom_pick_pll] *ERROR* unable to allocate a PPLL bugzilla-daemon
2013-02-24 16:27 ` [Bug 54381] " bugzilla-daemon
2013-02-24 16:57 ` bugzilla-daemon
2013-02-24 17:24 ` bugzilla-daemon
2013-02-24 23:14 ` bugzilla-daemon
2013-02-25 20:08 ` bugzilla-daemon
2013-02-25 20:16 ` bugzilla-daemon
2013-02-25 20:41 ` bugzilla-daemon
2013-02-25 20:58 ` bugzilla-daemon
2013-07-17 14:22 ` bugzilla-daemon [this message]
2013-07-17 14:54 ` bugzilla-daemon
2013-07-17 15:05 ` bugzilla-daemon
2013-07-17 15:25 ` bugzilla-daemon
2013-07-17 15:26 ` bugzilla-daemon
2013-08-05 8:40 ` bugzilla-daemon
2013-09-11 9:24 ` bugzilla-daemon
2013-09-20 9:15 ` bugzilla-daemon
2013-09-20 9:16 ` bugzilla-daemon
2014-06-30 12:58 ` bugzilla-daemon
-- strict thread matches above, loose matches on Subject: below --
2016-07-08 18:09 Lucia Franceschi
2017-03-21 7:55 Frank Gomez
2017-06-09 0:02 Ashley Mcnatt
2017-06-14 4:22 mcorcho52
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-54381-2300-ATw3rtHCRu@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).