All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 42373] Radeon HD 6450 (NI CAICOS) screen corruption on boot
Date: Thu, 28 Mar 2013 23:40:54 +0000	[thread overview]
Message-ID: <bug-42373-502-SjHBv0KSS4@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-42373-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1009 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=42373

--- Comment #44 from Alexandre Demers <alexandre.f.demers@gmail.com> ---
(In reply to comment #43)
> I do not know if this is relevant, but I recently purchased a radeon 6450
> and had similar issues - corruption when KMS is started and lockups when X
> starts. I did not get these issues in fglrx or the windows drivers.
> 
> I then happened to notice that the memory clock settings for the 'boot'
> power profile were incorrect, and were significantly higher than the card
> should support. The high & low power states appeared to be correct. Changing
> the boot values using the Radeon Bios editor
> (http://www.techpowerup.com/rbe/) fixed these problems for me.

While this is not related to the proposed attachment, it is quite interesting
to know you were able to fix your problem by tweaking your card's bios. Maybe
Kunal could tell us more about some similar observations.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1967 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2013-03-28 23:40 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-29 16:03 [Bug 42373] New: Radeon HD 6450 (NI CAICOS) screen corruption on boot bugzilla-daemon
2011-10-29 16:05 ` [Bug 42373] " bugzilla-daemon
2011-10-29 16:05 ` bugzilla-daemon
2011-10-30 12:13 ` bugzilla-daemon
2011-11-06  9:59 ` bugzilla-daemon
2011-11-06 10:00 ` bugzilla-daemon
2011-11-07  4:28 ` bugzilla-daemon
2011-11-07  4:29 ` bugzilla-daemon
2011-11-07 10:06 ` bugzilla-daemon
2011-11-07 15:29 ` bugzilla-daemon
2011-11-07 18:09 ` bugzilla-daemon
2011-11-07 18:10 ` bugzilla-daemon
2011-11-07 18:53 ` bugzilla-daemon
2011-11-10 17:38 ` bugzilla-daemon
2011-11-12  0:13 ` bugzilla-daemon
2012-06-16 21:28 ` bugzilla-daemon
2012-07-27  6:26 ` bugzilla-daemon
2012-08-04 13:26 ` bugzilla-daemon
2012-08-04 13:52 ` bugzilla-daemon
2012-08-04 17:47 ` bugzilla-daemon
2012-08-08 18:04 ` bugzilla-daemon
2012-08-15 15:41 ` bugzilla-daemon
2012-08-15 15:43 ` bugzilla-daemon
2012-08-15 15:44 ` bugzilla-daemon
2012-08-15 21:13 ` bugzilla-daemon
2012-08-16 21:44 ` bugzilla-daemon
2012-08-16 21:59 ` bugzilla-daemon
2012-08-17 13:54 ` bugzilla-daemon
2012-08-17 14:21 ` bugzilla-daemon
2012-08-17 18:10 ` bugzilla-daemon
2012-08-17 18:11 ` bugzilla-daemon
2012-08-17 18:11 ` bugzilla-daemon
2012-08-20  3:01 ` bugzilla-daemon
2012-08-20 14:03 ` bugzilla-daemon
2012-08-23  4:58 ` bugzilla-daemon
2012-09-17  4:29 ` bugzilla-daemon
2012-10-18 13:51 ` bugzilla-daemon
2012-10-18 14:48 ` bugzilla-daemon
2012-10-19 14:30 ` bugzilla-daemon
2012-11-12  6:37 ` bugzilla-daemon
2012-11-12  6:38 ` bugzilla-daemon
2012-11-12  6:39 ` bugzilla-daemon
2012-11-12  7:05 ` bugzilla-daemon
2012-12-08  6:53 ` bugzilla-daemon
2013-03-28  2:45 ` bugzilla-daemon
2013-03-28 19:14 ` bugzilla-daemon
2013-03-28 23:40 ` bugzilla-daemon [this message]
2019-11-19  8:20 ` bugzilla-daemon
2019-11-19  8:22 ` 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-42373-502-SjHBv0KSS4@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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.