7970m flashing to R9 M290X ?

Hi guys, who do that? i find a lot of guid how flash 7970m to 8970m, but still cant find how flash 7970m to R9 M290X, any one has experince?

 

You'd do the exact same procedure as you mentioned except use a m290x vbios instead of a 8970m vbios.
Having said that, I don't know if it wouldn't result in bricking though.

 

. All of those are different hardware...

Enviado do meu SM-N9005 através de Tapatalk

 

7970M and 8970M are the same hardware. Not 100% sure about the M290X, performance wise they are the same.

 

They are all rebrands of 7970m. But I don't know if this means a slam dunk for flashing a 7970m with a m290x vbios.

 

You know, as unreliable as GCN video cards have been, especially 7970M, I'd be worried about trying that. It might end in a bad way. They're just too fragile to experiment with like that. And, on top the chance for problems there is really no point in it. It's like flashing a 580M to a 675M. The only reason I can think of that anyone would feel compelled to do that is to pass off an older NVIDIA GPU as being a newer one, and that's certainly not kosher. There's no performance advantage to be realized by spoofing the GPU name through firmware.

If it's something you want as an ego boost and just want to pretend you have R9 M290X, you can probably just mod the INF to make the driver lie to Device Manager without doing a firmware mod. (I am assuming you can do this with AMD drivers... I know you can with NVIDIA drivers.)

 

Hmm. If you look at the notebook check graphics card line up they so the r290 above 680m sli and it's gaming bench marks are higher. I'm not sure it's exactly the same.as the 7970

Sent from my SM-N900T using Tapatalk

 

It's an overclocked 7970m so thats about right under those conditions.

 

Another reason I could think of would be when AMD discontinues official driver support for the 7900M series, which going by the way AMD has worked before, is bound to happen sooner rather than later. Then of course one could always just modify the 8970M/M290x driver/.inf file, which is much safer and should work fine. I definitely wouldn't risk a flash to go bad on these cards (especially since the clocks are higher and the 7970Ms tend to fizzle out when overclocked), although I'm quite interested if it works if anybody is silly enough to try.

 

Why not just OC the thing using a vbios flash. Easy to do and easily reversible when you don't need the horsepower.

Are they that fragile? I have been running a QS for exactly 2 years now although it is mainly left at stock clocks and undervolted for lower temps. This could attribute to it's good health. I hope it will last out the year until 20nm GPU's come along to replace it.

 

OK, so let's stop and think about that for a minute. (1) Notebookcheck is doing it, so it's of limited value; and, (2) they're using a stock NVIDIA vBIOS, which means that the results are truly irrelevant to real-world application. Never take a check from them to the bank or you'll end up overdrawn. Not saying they are worthless because they are a valuable source for some information, just limited value where their in-house testing in concerned. What they post as far as benchmarks can be very far off from what these GPUs are capable of doing. If you have any kind of ability to tweak and tune, then what R9 M290X versus 680M looks like out of the box from Notebookcheck truly does not matter. The closer together their results are the less relevant and less accurate they become.

But, I suppose it does matter if you're a good boy that would never dream of doing anything really naughty like overclocking and you plan to live and die by whatever comes your way from the bowels of AMD and/or NVIDIA.

If Notebookcheck did not test the GPUs on the same day, using the exact same laptop, same exact OS condition, same Windows Updates (or lack thereof), etc. then their results are "ball park" values. Unless the difference between the two video cards is too huge to account for these differences, you cannot rely on their results as adequate guidance on which GPU is more powerful.

 

This seems a little more secure than flashing it to the R9.

 

Plus I hear currently driver isn't gr8 for the the r9 yet. Perhaps worse than the 7970m!


Sent from my iPod touch using Tapatalk

 

You know, when you look at how pathetic AMD products have become it is kind of scary and very sad. This leaves the door wide open for NVIDIA and Intel to suck at what they do as well.

Example... Compare: Desktop with FX-9590 Octacore CPU @ 4.7GHz with R9 290X 2x CrossFire (P16479) versus Mr. Fox's M18xR2 with 3920XM @ 4.7GHz with 780M SLI (P17197)

I don't know whether to be proud of my achievement, or angry and extremely disappointed with such a showing of mediocrity for AMD. The example chosen above was a #2 record for AMD with dual-GPU and the #1 spot with the same CPU @ 5.3GHz and 3x R9 290X ( P19069) is equally unimpressive. The graphics scores seem low all things considered, especially for that 3x CrossFire combo and the Physics (CPU) score. It is hard for me to understand how some people are actually excited about these components.

 

Well 720p is a little silly for those cards but AMD had a disaster of management the real test is now they are back on the track if their proper next gen cpu architectures are worth a damn, we will know in a year or two.

The GPUS are fine, hopefully they target mobile a little more and get some design wins as the 7870m is far better than the 660m but had limited deployment.

Also on the vbios front most people will run with the stock one so making a judgement on that is not invalid.

 

I think if they posted the score, judgment is valid. You take it on face value and don't make excuses. It is what it is, whether good or bad. Running a stock vBIOS is not a legitimate excuse for low scores. It might be a reason, but it doesn't change the score.

 

So long as the scores are a true representation of stock performance that's fine. I would not expect a reviewer to go flashing modified bios files as most consumers will not do that.

If the stock scores are lower than what the stock should be then there is an issue.

 

I agree with you. I look to the professional reviews for information on specs and things of that nature. But, I don't rely on performance testing from most reviewers for that very reason. If they did that, the manufacturers probably would not send them any review units in the future.

What I was getting as is the fact that it is not relevant to me which GPU is better when run stock. I know it is important to some people, but I don't care about which one is faster stock. I only care about what they can do when pushed to their functional limits, and reviewers don't really do that. The "most consumers" are merely casual performance enthusiasts that enjoy a machine that offers a nice experience when they press the power button without having to tweak or tune anything.

 

What I just posted here might be useful to you... http://forum.notebookreview.com/alienware/759762-amd-r9-m290x-vbios-4.html#post9762363

 

Thanks man, how you think that vbios campability with Alienware m18x machine ? i have R2

 

Mauby you know i already make it one post but still not receive good reply...

I have in my m18x r2 one 7970m Wimbldeon XT, after that i find second one 7970m but Wimbledon v2 G1.2, i install here like right (slave card) and connect with crossfire adaptor, reset cmos and start the system, when system boot i will see in bios two GFX adaptors (my heart start beat much faster, finally its work) after that im from dos flash right card with my primary card bios and reset it again. My system see both card in bios and when it boot in my Windows 8 device manager but but but, device manager tell me what right card is start not properly and mark it with yellow mark! So if bios see both card in bios that mean what they are working... And device manager show me two 7970m but fla Wimbledon G2 V1.2 from Clevo mark it with yellow mark. Please frend give advice, mauby you know somthing ? Also before install second card i delet all AMD driver with AMD remove tool, but i hear somewere what at windows 8 sometime its dosent help and you must reinstall all system, that could be try ?

 

Perhaps reinstalling Windows will fix it. It is certainly worth trying. There could be a problem with the secondary GPU. If reinstalling Windows does not fix it, try swapping the video cards into the opposite PCI-e slots and see if the problem follows the GPU or remains the same on the secondary PCI-e slot. There has been a high failure rate on 7970M cards, so let us hope for the best.

 

Hi, i think its problem with Clevo card compability, because my dell 7970 Wimbledon XT even different color, my card is dark blue but clevo card in light blue, i think some problem in architecture, i use your guide with HWinfo64 setup and cooling now work very well "my laptop now like ice cube "

I hope today get it normal 7970m for DELL , you do not have link were i can get it 8970m vbios fro dell ? i find on:

Video Bios Collection | techPowerUp

But here only for clevo or msi...

Why i ask, i want flash it my 7970m at 8970m, hope will work fine )))

 

Maybe ask svl7 at Tech|Inferno if you cannot find answers in the thread over there. There are also Dell 7970M vBIOS files in a package you can download. If it is not already posted somewhere in the thread, I suspect there is a good chance svl7 may know if the Dell vBIOS will work on a Clevo GPU. There very well could be a compatibility problem trying to pair them in CrossFire mode. AMD 7970m - modified VBIOS

The 7970M was popular for upgrading the M15x (single) and M17xR2 (CrossFire) so other members in this community may also know the answer to the compatibility question.

 

i exchange my clevo card at dell card, but today i have probelm, crossfire work good but when i install driver after 20 minets he is gone and start work not properly, i reboot pc and delete again, when i reainstall amd driver same story. I use windows 8, mauby some issues with crossfire in windows 8 and driver compability, today will try fixe that...

 

I flash my 7970m to 8970m and seem work well, but i can't chose crossfire mod in driver, why ???

 

Did you flash them both?

 

Yep, i fixed problem now, with 8970m vbios system after 10 minets give white screen or artifacts, but both card is 41 C, so its not overheating, i return original dell 7970m vbios and all work good now, hope in future also will be))))

So reflashed 7970m at 8970 cause some problem and issues with drivers. So dont do that when you have crossfire you could damage youre card's

Also when you install second 7970m in aw m18x r2 it could be issues with new driver (driver just wont work), you can fixed that when delet intel hd driver.

 

If someonelse need original vbios 8970m for dell/alienware chekt a link, i use that vbios in my system and it work good with one card but not when you reflash it both in crossfire (he stop be available and cards work not properly).

dell 8970m: http://www.techpowerup.com/forums/attachments/dell_8970m-zip.57468/

 

guys my cards 7970m in CF reach in the game until 90-95C ! its normall ?

 

That's way too high even with a hefty overclock. You need a re-paste I think.

 

My cards in CF R9 M290X in the most difficult games to a maximum of 80C.

 

Overclocking and good thermal paste is the fear escapes

 

Also check the pads are flat and the right height.

 

I now clean system and with msi afterburner I get in batman origins left card 65 and right70 (hope it's ok) strange why right card it more hot? She is slave

 

That's fine.. One card is usually hotter than the other.. Your temps are normal for 7970Ms too...

 

Glad to hear that, because I think 70 in batman on ultra settings is to much

 

70C is not high at all.. I hit 65-70C on stock clocks and depending on ambient temperature... Additionally, with OC of 925/1350 I hit about 70-75C... NVIDIA cards like 780M routinely at stock clocks run at 80C and above so we are more than fine

 

Totally agree with you.. except for the bold part... I don't know why you're under that impression. I don't even hit 77 even with hefty overclocks.

 

Yeah, that is not accurate. I cannot remember the last time I saw 80°C with my 780M SLI, even overclocked and overvolted. It rarely exceeds 70°C. Anyone seeing temps like that has a bad paste job or has it installed in a laptop with an inadequate cooling system, but this is not the GPU's fault.

 

Well you could get a complete dud or have a heatsink on the poor end of tolerance.

 

Yes, that is always a possibility with any system... But, the "NVIDIA cards like 780M routinely at stock clocks run at 80C and above" comment is not accurate.

 

Just to inform you. Like month ago I flashed my msi 7970m to R9 m290x with no issue (and it still works). I mean I did it to original R9 bios not just OCed one from 7970m.

 

A reason I can see for flashing it is to make them compatible with newer laptops (maybe). I have a pair of 7970m's that I'm going to throw in a Clevo p377 when it gets here in a few days. Officially, the p377 doesn't support the 7970m, but it does support the R9 m290x. I imagine, the 7970m's should be plug and play in the Clevo as they are the exact same hardware as the R9 m290x's but if the computer doesn't like them, I imagine flashing them to R9 m290x's might solve any unforseen compatibility issues.

 

Unless something changed, the drivers may not even know what to call some of the AMD GPUs because of a shared hardware ID. For example, a system that ships with R9 M290X might appear in Windows to be a 8970M unless you stick to drivers provided by the OEM because they use an identical hardware ID. During driver installation, the content of the INF file tells Windows what name to assign to the GPU. Using generic AMD drivers may result in the GPU being called something different than what you paid for. This is upsetting to some people, but it causes no harm in terms of functionality or performance. I'm not sure flashing the vBIOS is even necessary.

 

In my AW17 R1 (originally came with the R9 M290X), the card was identified as a 7970M I believe. Other software saw it as an 8970M.

 

You can mod the INF and tell Windows to call it whatever you want it to be called. This works for NVIDIA GPUs as well. You can name your GeForce mobile card a Titan Black, an "ACME Crapworks 4K Extreme Edition" or even an AMD Fury if you feel like doing so.

 

I can see myself having fun with such a modded inf file. Change it to make it look like a Titan Z in my Clevo P750ZM, along with a Xeon CPU, show that to a friend. See their bewildered looks.

 

I've actually done that by accident more than once modding desktop drivers. I once had my 980M cards identified as Titans for a day or two before I noticed the mistake. I simply forgot to change the name under the [Strings] section.

Those that have been mobile enthusiasts for a long time might still remember the confusion around identification of 6970M versus 6990M because AMD drivers told Windows to call both of them "Radeon HD 6900M Series" (or something like that) and you had to look at clock speeds and shader counts using GPU-Z to figure out what GPU hardware your system actually had in it.

 

You know, I tried this with my GTX 860m (calling it a GTX 960m), and it worked. Only for Windows and GPU-Z. Nvidia Inspector calls it a GTX 860m still.
The weird thing is that I didn't have to disable driver signature enforcement (using Win8.1). It installed without problems.
I'm guessing name modding isn't bad enough for disabling. If that's the case, then R9 m290x users wouldn't have to disable driver signature, right?