From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 83461] hdmi screen flicker/unusable
Date: Sun, 30 Nov 2014 20:51:34 +0000 [thread overview]
Message-ID: <bug-83461-2300-v5yKbcRpRB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-83461-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #26 from kb@spatium.org ---
(In reply to Christian König from comment #25)
> You could try to artificially limit ref_div_max or fb_div_max until you get
> a stable signal once more. Maybe this will yield some more light on the root
> cause of the issue.
Can you give me some details - how to do this?
> > Do you think change of graphics card would resolve the issue?
>
> Well, most likely yes.
>
> But the new kernel seems to work better for some people, but has regressed
> for you. So I would really like to create a solution that works for
> everybody.
Right now I switched to catalyst which seems to work and allows me to use new
kernel. But since apparently my card is "legacy" I had to downgrade to xorg
server 1.12 :-|
--
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:[~2014-11-30 20:51 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 18:49 [Bug 83461] New: hdmi screen flicker/unusable bugzilla-daemon
2014-09-08 4:22 ` [Bug 83461] " bugzilla-daemon
2014-09-15 17:03 ` bugzilla-daemon
2014-09-15 18:57 ` bugzilla-daemon
2014-09-16 16:00 ` bugzilla-daemon
2014-09-17 1:10 ` bugzilla-daemon
2014-09-17 14:35 ` bugzilla-daemon
2014-10-19 19:35 ` bugzilla-daemon
2014-10-19 19:37 ` bugzilla-daemon
2014-10-20 16:20 ` bugzilla-daemon
2014-10-23 17:55 ` bugzilla-daemon
2014-10-23 18:05 ` bugzilla-daemon
2014-10-23 18:06 ` bugzilla-daemon
2014-10-24 18:00 ` bugzilla-daemon
2014-10-28 15:49 ` bugzilla-daemon
2014-11-01 19:40 ` bugzilla-daemon
2014-11-01 19:45 ` bugzilla-daemon
2014-11-01 20:01 ` bugzilla-daemon
2014-11-01 20:01 ` bugzilla-daemon
2014-11-02 11:58 ` bugzilla-daemon
2014-11-07 19:19 ` bugzilla-daemon
2014-11-17 11:44 ` bugzilla-daemon
2014-11-18 15:50 ` bugzilla-daemon
2014-11-18 15:50 ` bugzilla-daemon
2014-11-28 21:20 ` bugzilla-daemon
2014-11-29 16:30 ` bugzilla-daemon
2014-11-30 20:51 ` bugzilla-daemon [this message]
2014-12-01 11:47 ` bugzilla-daemon
2014-12-28 8:24 ` bugzilla-daemon
2014-12-28 22:11 ` bugzilla-daemon
2014-12-30 16:24 ` bugzilla-daemon
2015-01-17 8:54 ` bugzilla-daemon
2015-01-20 11:23 ` bugzilla-daemon
2015-02-09 16:09 ` bugzilla-daemon
2015-02-09 16:29 ` bugzilla-daemon
2015-02-19 20:36 ` bugzilla-daemon
2015-02-19 20:39 ` bugzilla-daemon
2015-02-19 20:49 ` bugzilla-daemon
2016-05-02 22:31 ` 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-83461-2300-v5yKbcRpRB@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.