https://bugs.freedesktop.org/show_bug.cgi?id=76490
Alex Deucher changed:
What|Removed |Added
Status|REOPENED|RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #122 from Franc[e]sco ---
I also edited this piece of code (still in si_dpm.c) to let my memory clock hit
1400 MHz which is stock speed for this card, and I'm still running rock solid:
/* limit all SI
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #121 from Franc[e]sco ---
I removed the quirks for my r9 270x and I have no stability issues whatsoever,
it's a really nice performance boost.
this is the line I commented out for my card:
{ PCI_VENDOR_ID_ATI,
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #120 from Elia Argentieri ---
Yes! My graphics card can finally unleash all its potential! Following your
suggestion, I downloaded linux 4.10 master, removed this from quirks (R7 370):
{
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #119 from Daniel Exner ---
Good news!
With kernel 4.10.0-rc5-00071-ga4685d2f58e2 that includes:
drm/radeon/si: load special ucode for certain MC configs
from drm-fixes-4.10 branch and the
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #118 from Alex Deucher ---
(In reply to Daniel Exner from comment #117)
> (In reply to Alex Deucher from comment #116)
> > Created attachment 126814 [details] [review] [review]
> > possible fix
> >
> > Does this patch help?
>
> I
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #117 from Daniel Exner ---
(In reply to Alex Deucher from comment #116)
> Created attachment 126814 [details] [review]
> possible fix
>
> Does this patch help?
I applied the patch on Kernel
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #116 from Alex Deucher ---
Created attachment 126814
--> https://bugs.freedesktop.org/attachment.cgi?id=126814=edit
possible fix
Does this patch help?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=76490
AmarildoJr changed:
What|Removed |Added
CC||amarildosjr at riseup.net
--- Comment #115
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #114 from Daniel Exner ---
(In reply to Alex Deucher from comment #113)
> That tree is using the same code power management as radeon, just ported to
> amdgpu.
Ok, thx for the clarification. Then
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #113 from Alex Deucher ---
(In reply to Daniel Exner from comment #112)
> If I read that correct R9 270X is a GCN 1.0 card and thus should be
> supported by experimental drm-next-4.8-wip-si branch.
>
> Is it worth trying? AMDGPU is
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #112 from Daniel Exner ---
If I read that correct R9 270X is a GCN 1.0 card and thus should be supported
by experimental drm-next-4.8-wip-si branch.
Is it worth trying? AMDGPU is using a yet
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #111 from Alex Deucher ---
(In reply to thirdloop from comment #110)
> Created attachment 123371 [details]
> sapphire nitro r7 370 4gb lspci -vnn output
>
> I'm on ubuntu 16.04 (can't use the fglrx driver anymore) and I have been
>
https://bugs.freedesktop.org/show_bug.cgi?id=76490
thirdloop at teknik.io changed:
What|Removed |Added
CC||thirdloop at teknik.io
---
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #109 from Gustavo Lopes ---
Not to mention that even with the quirk I would get (last time I tried) a hang
every 1-2 days. Catalyst has been quite stable for me.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=76490
Benjamin Bellec changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=76490
Michael Rosile changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #106 from samdenies at zhentarim.net ---
(In reply to Alex Deucher from comment #105)
> Does this attached patch help?
I was not able to apply the patch itself as it didn't match the source for
4.5.1 that I downloaded. However,
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #105 from Alex Deucher ---
Created attachment 122946
--> https://bugs.freedesktop.org/attachment.cgi?id=122946=edit
possible fix
(In reply to samdenies from comment #102)
> I want to add another data point for a card not yet
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #104 from samdenies at zhentarim.net ---
Created attachment 122942
--> https://bugs.freedesktop.org/attachment.cgi?id=122942=edit
XFX R9 270X lspci -xnn results
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #103 from Alex Deucher ---
(In reply to samdenies from comment #102)
> I want to add another data point for a card not yet mentioned in this bug.
> I have had this issue for quite some time, awaiting a fix. I run a
> fully-updated
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #102 from samdenies at zhentarim.net ---
I want to add another data point for a card not yet mentioned in this bug. I
have had this issue for quite some time, awaiting a fix. I run a fully-updated
Debian testing, and my card is
https://bugs.freedesktop.org/show_bug.cgi?id=76490
Nicholas Vaughan changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #101 from Maxim Sheviakov ---
(In reply to Daniel Exner from comment #100)
> If that worked for you you are lucky, but at least I won't flash a different
> BIOS just to _downgrade_ my card, possibly breaking it completely. Alas the
>
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #100 from Daniel Exner ---
(In reply to Maxim Sheviakov from comment #99)
> Interesting, but it got flashed 0_0
> Also, the problem is not in VBios or IDs. It's all about memory clock -
> setting a
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
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #98 from Alex Deucher ---
(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
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #97 from Maxim Sheviakov ---
He-hey! Succeeded in booting and making the card work with 1050Mhz core clocks!
So, I added the firmware, applied the pathes from Alex, modified quirk's values
so that it's 1020MHz core + 1200MHz mem,
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #96 from Maxim Sheviakov ---
1) Thanks.
2) Nope. There's a tool - "ATIFlash" - from TechPowerUp. It allows you to
A) Save your current VBios
B) Flash another VBios
I think we have to modify vendor/model IDs, or fix clocks to their
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #95 from Tobias Droste ---
$ cat /sys/kernel/debug/dri/0/radeon_pm_info
If you have debugfs mounted on /sys/kernel/debug
Are you suggesting that Microsoft Windows 10 is delivering a different VBIOS
for your card then what was
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #94 from Maxim Sheviakov ---
How can I acquire GPU and MEM clocks being used? Just tried flashing R7 370
Gaming 2G VBIOS from EvilOS-10 and it boots and even works on my Archlinux
installation. Is there a way to get the values?
--
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #93 from Maxim Sheviakov ---
Can anyone give me values from si_dpm.c for MSI R7 370 2GB Gaming 2G (Red)? I
think I have an idea on how to implement higher/normal clocks on Armor 2X.
Also, a copy of fresh VBios would be welcome.
--
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #92 from Maxim Sheviakov ---
So, got my PSU yesterday. Compiled 4.3.3-zen with -Ofast + those patches, quirk
removed and firmware added to initrd. Modesetting works, I'm able to see
Plymouth finishing its animation. However, at X
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #91 from Maxim Sheviakov ---
(In reply to Tobias Droste from comment #90)
> Yes I did.
>
> And right now it's only working for Stefan (R7 370).
>
> It's not working for me (R9 270X) and Daniel (R9 270X).
Hmm... Seems like the code
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #90 from Tobias Droste ---
Yes I did.
And right now it's only working for Stefan (R7 370).
It's not working for me (R9 270X) and Daniel (R9 270X).
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #89 from Maxim Sheviakov ---
(In reply to Tobias Droste from comment #88)
> Doesn't fix it for me, it still locks up at boot with dpm enabled and the
> quirk removed.
>
> [drm] initializing kernel modesetting (PITCAIRN 0x1002:0x6810
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #88 from Tobias Droste ---
Doesn't fix it for me, it still locks up at boot with dpm enabled and the quirk
removed.
[drm] initializing kernel modesetting (PITCAIRN 0x1002:0x6810 0x174B:0xE271
0x00)
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #87 from Stefan Ott ---
Nice, this seems to fix the issue on my ASUS card.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #86 from Daniel Exner ---
Tried kernel 4.4.0-rc4 with
"drm/radeon: load different smc firmware on some SI variants"
and
"drm/radeon: print pci revision id as well as pci ids"
applied.
The
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #85 from Maxim Sheviakov ---
(In reply to Alex Deucher from comment #84)
> (In reply to Maxim Sheviakov from comment #82)
> > So, those workaround lines in si_dpm.c have to be removed in order to use
> > thise new patches?
>
> You
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #84 from Alex Deucher ---
(In reply to Maxim Sheviakov from comment #82)
> So, those workaround lines in si_dpm.c have to be removed in order to use
> thise new patches?
You can try the patches either way. You need to remove the
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #83 from Maxim Sheviakov ---
These*
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #82 from Maxim Sheviakov ---
(In reply to Alex Deucher from comment #81)
> (In reply to Daniel Exner from comment #80)
> > Is this a revision of the previous override? Read: should this previous
> > patch be reverted before testing?
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #81 from Alex Deucher ---
(In reply to Daniel Exner from comment #80)
> Is this a revision of the previous override? Read: should this previous
> patch be reverted before testing?
If you have a quirk in place for your board, remove
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #80 from Daniel Exner ---
Is this a revision of the previous override? Read: should this previous patch
be reverted before testing?
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #79 from Maxim Sheviakov ---
Oh, thanks. When I get my new PSU (maybe tomorrow) I'll rebuild my 4.3-zen and
build 4.4 from git, both with these changes and normal GPU (higher than present
in 4.3/4.4) clocks - will report.
--
You
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #78 from Alex Deucher ---
(In reply to Maxim Sheviakov from comment #77)
> How do I do it? For the first link:
> Is it enough to copy
> http://cgit.freedesktop.org/~agd5f/linux/tree/drivers/gpu/drm/
> radeon?h=new_smc to 4.3 source
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #77 from Maxim Sheviakov ---
(In reply to Alex Deucher from comment #76)
> Can you try the code in this branch:
> http://cgit.freedesktop.org/~agd5f/linux/log/?h=new_smc
> and the new ucode from here:
>
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #76 from Alex Deucher ---
Can you try the code in this branch:
http://cgit.freedesktop.org/~agd5f/linux/log/?h=new_smc
and the new ucode from here:
http://people.freedesktop.org/~agd5f/radeon_ucode/k/
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #75 from Maxim Sheviakov ---
(In reply to Maxim Sheviakov from comment #74)
> (In reply to Maxim Sheviakov from comment #73)
> > (In reply to Alex Deucher from comment #72)
> > > (In reply to Maxim Sheviakov from comment #71)
> > > >
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #74 from Maxim Sheviakov ---
(In reply to Maxim Sheviakov from comment #73)
> (In reply to Alex Deucher from comment #72)
> > (In reply to Maxim Sheviakov from comment #71)
> > > Hmm, nice point. By the way, is the MCLK kinda divided
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #73 from Maxim Sheviakov ---
(In reply to Alex Deucher from comment #72)
> (In reply to Maxim Sheviakov from comment #71)
> > Hmm, nice point. By the way, is the MCLK kinda divided by four? So, if
> > Memory Clock is 5600MHz, I'll
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #72 from Alex Deucher ---
(In reply to Maxim Sheviakov from comment #71)
> Hmm, nice point. By the way, is the MCLK kinda divided by four? So, if
> Memory Clock is 5600MHz, I'll have to do 5600/4*1 to get the correct
> value?
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #71 from Maxim Sheviakov ---
(In reply to Tobias Droste from comment #70)
> (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 ?
>
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,
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #69 from Maxim Sheviakov ---
I can't see no logic. Nothing sensible. Remember: NOTHING does XXX
automatically,it first has to be implemented. And, hell, tbe kernel actually
reads the vbios and looks for the same IDs, but it's not
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #68 from Benjamin Bellec ---
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 "12". I
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #67 from Maxim Sheviakov ---
(In reply to Benjamin Bellec from comment #65)
> I just bought a Gigabyte "GV-R737WF2OC-2GD" (R7 370).
> Same problem: unable to boot Linux (Fedora 23 GNOME Workstation)
> Same fix: radeon.dpm=0
>
> It
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #66 from Benjamin Bellec ---
Created attachment 120154
--> https://bugs.freedesktop.org/attachment.cgi?id=120154=edit
Gigabyte GV-R737WF2OC-2GD BIOS (F3 version)
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=76490
Benjamin Bellec changed:
What|Removed |Added
CC||b.bellec at gmail.com
--- Comment #65
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #64 from Maxim Sheviakov ---
So what does it mean? It boots with high (not low) clocks without dpm?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #63 from Stefan Ott ---
I appear to have the same issue on an ASUS STRIX R7 370. It's also a
factory-overclocked card and radeon.dpm=0 seems to work.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=76490
almos changed:
What|Removed |Added
CC||aaalmosss at gmail.com
--- Comment #62 from
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #61 from Maxim Sheviakov ---
Heh, got a pretty same issue. Although I've got my patch for MSI R7 370 Armor
2X proposed and present in 4.3, I've got some weird issues with dpm, like
complete system hang + black screen after some time
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #60 from m.gabrielboehme at googlemail.com ---
Created attachment 119434
--> https://bugs.freedesktop.org/attachment.cgi?id=119434=edit
PowerColor R7 370 PCS+ VBIOS
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #59 from m.gabrielboehme at googlemail.com ---
I switched to a PowerColor R7 370 PCS+ and have the same problems as reported
already. Starting with radeon.dpm=0 or nomodeset helps to boot up. I'm on
Fedora 23 at the moment with a 4.2
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #58 from Kevin McCormack ---
Alex, have you had a chance to look at the vbios files? I think that Michael
Larabel of Phoronix is also having difficulties with his R9 270X card.
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #57 from Alex Deucher ---
I don't think this has anything to do with the vbios. I suspect the same pci
ids are just used in multiple board configurations (e.g., different clocks or
vram chip vendors or voltage configurations) so the
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #56 from Kevin McCormack ---
Hey guys, I am just wondering if there is any news about this? I noticed a new
commit for an MSI R7 370 here
https://github.com/torvalds/linux/commit/e78654799135a788a941bacad3452fbd7083e518
that makes my
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #55 from Tobias Droste ---
What I can see:
Your bios:
AMD VER015.0400.001
My bios:
AMD VER015.0400.032
Your bios:
12/09/13 00:31
My bios:
12/25/14 22:33
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #54 from Tobias Droste ---
Ok they _are_ different. Alex can you have a look at this and tell us what's
different between the bioses?
Compare VBIOS Sapphire Radeon R9 270X 2GB (windows) with Sapphire Dual-X R9
270X 2GB OC Edition
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #53 from Kevin McCormack ---
Created attachment 118292
--> https://bugs.freedesktop.org/attachment.cgi?id=118292=edit
Sapphire Dual-X R9 270X 2GB OC Edition vbios
OK, Tobias, I did as you guided me.
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #52 from Tobias Droste ---
>From comment #26:
(as root)
(use lspci to get the bus id)
cd /sys/bus/pci/devices/
echo 1 > rom
cat rom > /tmp/vbios.rom
echo 0 > rom
then upload /tmp/vbios.rom
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #51 from Kevin McCormack ---
Tobias, I don't know how to do that. If you can explain or point me in the
right direction I'd be happy to upload the bios.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #50 from Tobias Droste ---
Hm nice... Could you upload your bios? Would be interesting if it's different
to my bios. I can't event boot without this workaround.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #49 from Kevin ---
I think I our issues are related if not the same. I bisected and that brought
me to this bug report. It seems like a "fix" for this bug caused my issues.
https://bugzilla.kernel.org/show_bug.cgi?id=103271
--
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #48 from Tobias Droste ---
There is only one way to find out the values:
Trial and error.
Start with what works with other cards:
{ PCI_VENDOR_ID_ATI, , ,
, 0, 12 },
Last value is mclk (memory) and the other is sclk (gpu).
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #47 from christoffer.appe at gmail.com ---
Created attachment 118004
--> https://bugs.freedesktop.org/attachment.cgi?id=118004=edit
MSI R9 390 MB bios
Recently got an MSI R9 390, it also suffers problem with DPM enabled.
Would
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #46 from Daniel Exner ---
I was lucky as someone had exactly the same card (S/N prefix identical) and
requested a new Bios in the MSI forums.
The old bios uploaded there was identical to mine.
--
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #45 from Tobias Droste ---
Where did you get a new bios from? MSI?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #44 from Daniel Exner ---
Just to rule this out I did a bios upgrade and tried reverting the blacklisting
of my card: on X start black screen so of no use.
Should I attach the new bios?
--
You
https://bugs.freedesktop.org/show_bug.cgi?id=76490
Tobias Droste changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #43 from Tobias Droste ---
I don't think the voltage is a problem as the voltage used by the linux driver
seems to be the same as by the windows driver.
For my card it's 1238mV for high(er) clocks in windows and linux. I even tried
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #42 from Daniel Exner ---
My best guess is that clocks are propably ok, but voltage is too low, perhaps
confused by the fact that all of those cards are "factory overclocked".
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #41 from Alex Deucher ---
(In reply to Tobias Droste from comment #40)
>
> Do you think it's a problem with the kernel code or with the firmware? Does
> windows use the same firmware for DPM?
I think it's probably a driver bug.
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #40 from Tobias Droste ---
Ah sorry the difference in the bios versions was me. I fiddled with it to try
to get it to boot in linux without the workaround in the kernel.
You are correct in linux and windows they are the same but
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #39 from Alex Deucher ---
(In reply to Tobias Droste from comment #35)
> 3) This card works fine with any sclk/mclk combination with the same vddc
> (1238mV) in windows and I can overclock there!
There is apparently some aspect of
https://bugs.freedesktop.org/show_bug.cgi?id=76490
Tobias Droste changed:
What|Removed |Added
Attachment #116922|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #37 from Tobias Droste ---
Created attachment 116922
--> https://bugs.freedesktop.org/attachment.cgi?id=116922=edit
VBIOS Sapphire Radeon R9 270X 2GB (linux)
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=76490
Tobias Droste changed:
What|Removed |Added
CC||tdroste at gmx.de
--- Comment #36 from
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #35 from Tobias Droste ---
I have to do this:
{ PCI_VENDOR_ID_ATI, 0x6810, 0x174b, 0xe271, 85000, 9 },
This is with a Sapphire Radeon R9 270X 2GB GDDR5.
A higher value for either sclk or mclk results in an instant freeze as
https://bugs.freedesktop.org/show_bug.cgi?id=76490
Fabrice Bellet changed:
What|Removed |Added
CC||fabrice at bellet.info
--- Comment #34
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #33 from Gustavo Lopes ---
It doesn't help.
I patched 4.0 rc2 to set the maximum to 1100 Mhz (down from 1200). The computer
still hanged after roughly one day running xscreensaver. Another time X seems
to have crashed first because
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #32 from Alex Deucher ---
(In reply to Gustavo Lopes from comment #31)
> I'm using 4.0-rc1 and the radeon module now works, but it hangs once or
> twice a day, something I did not experience with catalyst. It seems to be
> more
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #31 from Gustavo Lopes ---
I'm using 4.0-rc1 and the radeon module now works, but it hangs once or twice a
day, something I did not experience with catalyst. It seems to be more frequent
under load.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #30 from Alex Deucher ---
(In reply to dex+fdobugzilla from comment #29)
> I can confirm the patch works.
>
> Will this be part of 3.19?
yes and stable kernels.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #29 from dex+fdobugzilla at dragonslave.de ---
I can confirm the patch works.
Will this be part of 3.19?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #28 from Alex Deucher ---
Created attachment 112144
--> https://bugs.freedesktop.org/attachment.cgi?id=112144=edit
temporary workaround
The attached patch adds a temporary workaround until I sort out what's wrong
with the higher
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #27 from dex+fdobugzilla at dragonslave.de ---
Created attachment 112051
--> https://bugs.freedesktop.org/attachment.cgi?id=112051=edit
Video BIOS MSI R270X 4G Gaming
Here you are. Hope you can disassemble it
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- Comment #26 from Alex Deucher ---
(In reply to dex+fdobugzilla from comment #25)
>
> Could this have something todo with the card having 4Gb of VRAM?
Doubtful. More likely the card requires special some voltage tweaks for the
higher
1 - 100 of 113 matches
Mail list logo