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: Sat, 26 Dec 2015 18:07:10 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1154794037==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 7B1C089E05 for ; Sat, 26 Dec 2015 10:07:10 -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 --===============1154794037== Content-Type: multipart/alternative; boundary="1451153230.CB2b24.1544"; charset="UTF-8" --1451153230.CB2b24.1544 Date: Sat, 26 Dec 2015 18:07:10 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=76490 --- Comment #99 from Maxim Sheviakov --- (In reply to Alex Deucher from comment #98) > (In reply to Tobias Droste from comment #95) > > Are you suggesting that Microsoft Windows 10 is delivering a different VBIOS > > for your card then what was originally installed on the graphics card? > > > > If so, who installs this? Windows itself? As far as I know is the driver > > only loading some binaries inside the VBIOS, but not replacing it. Or is > > this a new feature of the windows driver? > > Neither Windows nor the Windows driver flashes a new vbios. Flashing an > arbitrary vbios is not recommended, may render your card useless, and may > void your warranty. Interesting, but it got flashed 0_0 Also, the problem is not in VBios or IDs. It's all about memory clock - setting a value higher than 1.2GHz (in a quirk) makes the system hang after Plymouth/before display server start. So, to my mind we have to do something with DPM/PowerPlay code or make some userspace overclock support, as there's no other way right now. By the way, is there such a tool that allows to overclock memory of the card? And yep, with its standard VBios card works with 1050MHz/1.2GHz (core/memory) clocks. I'm using those SMC patches + new firmware. Maybe they should be sent upstream, even to add that new firmware files and code to use them? -- You are receiving this mail because: You are the assignee for the bug. --1451153230.CB2b24.1544 Date: Sat, 26 Dec 2015 18:07:10 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 99 on bug 76490 from 
(In reply to Alex Deucher from comment #98)
> (In reply to Tobias Droste from comment #95)
> > Are you suggesting that Microsoft Windows 10 is delivering a different VBIOS
> > for your card then what was originally installed on the graphics card?
> > 
> > If so, who installs this? Windows itself? As far as I know is the driver
> > only loading some binaries inside the VBIOS, but not replacing it. Or is
> > this a new feature of the windows driver?
> 
> Neither Windows nor the Windows driver flashes a new vbios.  Flashing an
> arbitrary vbios is not recommended, may render your card useless, and may
> void your warranty.

Interesting, but it got flashed 0_0
Also, the problem is not in VBios or IDs. It's all about memory clock - setting
a value higher than 1.2GHz (in a quirk) makes the system hang after
Plymouth/before display server start. So, to my mind we have to do something
with DPM/PowerPlay code or make some userspace overclock support, as there's no
other way right now. By the way, is there such a tool that allows to overclock
memory of the card?

And yep, with its standard VBios card works with 1050MHz/1.2GHz (core/memory)
clocks. I'm using those SMC patches + new firmware. Maybe they should be sent
upstream, even to add that new firmware files and code to use them?

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