From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 76490] Hang during boot when DPM is on (R9 270X) Date: Mon, 30 Nov 2015 08:11:24 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1764239062==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 494F36E539 for ; Mon, 30 Nov 2015 00:11:24 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1764239062== Content-Type: multipart/alternative; boundary="1448871084.BFAd04.4504"; charset="UTF-8" --1448871084.BFAd04.4504 Date: Mon, 30 Nov 2015 08:11:24 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=76490 --- Comment #70 from Tobias Droste --- (In reply to Benjamin Bellec from comment #68) > If I have to read the VBIOS and add I quirk in the kernel, why the kernel > can't do this by himself ? > > Moreover, I saw the previous quirk in the kernel, the max memory clock is > often set to "120000". I guess it stands for 1.2GHz QDR which is equivalent > to 4.8GHz. My card, like all the R7 370 are supposed to work at 5.6GHz so > this is a serious lost of performance. > > At the moment I will just return my card. For the record: This stuff *can't* be read from the VBIOS and has to be found by trial and error. You also don't have to google the steps, they are described in comment #48. But otherwise you are right, It will limit your card and replacing it with another one seems like the only option you have right now. At least that's what I did too, because I don't see this bug fixed in the near future. -- You are receiving this mail because: You are the assignee for the bug. --1448871084.BFAd04.4504 Date: Mon, 30 Nov 2015 08:11:24 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 70 on bug 76490 from 
(In reply to Benjamin Bellec from comment #68)
> If I have to read the VBIOS and add I quirk in the kernel, why the kernel
> can't do this by himself ?
> 
> Moreover, I saw the previous quirk in the kernel, the max memory clock is
> often set to "120000". I guess it stands for 1.2GHz QDR which is equivalent
> to 4.8GHz. My card, like all the R7 370 are supposed to work at 5.6GHz so
> this is a serious lost of performance.
> 
> At the moment I will just return my card.

For the record:

This stuff *can't* be read from the VBIOS and has to be found by trial and
error.
You also don't have to google the steps, they are described in comment #48.

But otherwise you are right, It will limit your card and replacing it with
another one seems like the only option you have right now. At least that's what
I did too, because I don't see this bug fixed in the near future.

You are receiving this mail because:
  • You are the assignee for the bug.
--1448871084.BFAd04.4504-- --===============1764239062== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1764239062==--