Now we know who is driving the prices up for GPU dead iMacs....I'm so happy for failed GPUs 😊
View attachment 1785018
Now we know who is driving the prices up for GPU dead iMacs....I'm so happy for failed GPUs 😊
View attachment 1785018
yea, but the 6970's on ebay also (1) suffer the same problems as the one in his original machine so they likely will fail, (2) often aren't out of iMacs so need to be flashed and you need to read the VBIOS from the original non-working card and (3) are just as expensive (or in the case of the 2GB version more expensive) as a GPU that might be more work to install but will certainly not be as much work to do a second or third time.@Ausdauersportler has made an excellent suggestion considering your current needs (2 screens and keeping High Sierra). There is a ton of HD6970M available on Ebay. You can buy one and install it. Then when it dies, you can buy another one and install it, and so on.
I have shares in AliExpress 😉Now we know who is driving the prices up for GPU dead iMacs....
Have you tried BR3 rom linked in post #1?@The_Croupier @dosdude1 can you help me please on https://forums.macrumors.com/threads/error-flashing-nvidia-gtx780m-on-imac-27-2011.2298750/
Thanks.
Wow. What do you do with those iMacs after replacing gpus?I'm so happy for failed GPUs 😊
Sorry, can you help me with the link to download, I not try BR3 😃Have you tried BR3 rom linked in post #1?
Your card seems to be an MXM 780M, the output of nvflash suggests is has a BIOS loaded made for the (Kepler) GRID K2 card. This is a different one I doubt you will succeed trying other versions. The flash software will always complain about the different device ID (11BF vs 119F). 119F is the one of all 780M ROMs found here.Sorry, can you help me with the link to download, I not try BR3 😃
WARNING: None of the firmware image compatible PCI Device ID's match the PCI Device ID of the adapter.
Adapter PCI Device ID: 11BF
Firmware image PCI Device ID: 119F
I test BR3 Rom and nothingPost 1 / table of working NVIDIA cards / GTX 780M ++
I try 780M_BR3 firmware but not successYour card seems to be an MXM 780M, the output of nvflash suggests is has a BIOS loaded made for the (Kepler) GRID K2 card. This is a different one I doubt you will succeed trying other versions. The flash software will always complain about the different device ID (11BF vs 119F). 119F is the one of all 780M ROMs found here.
Code:WARNING: None of the firmware image compatible PCI Device ID's match the PCI Device ID of the adapter. Adapter PCI Device ID: 11BF Firmware image PCI Device ID: 119F
You may have success using a clip programmer in the rare case your card has a SOIP BIOS chip compatible with the clip.
How to force nvflash (if even possible) to flash an BIOS regardless which card it discovers is beyond the scope of this thread. You may search the net for a possible software solution. The root cause is your card and the existing BIOS on the chip, not the tools, nor the BIOS versions, nor software you found here.I test BR3 Rom and nothingthe console tell:
Command:
./nvflash_linux -6 780M_BR3.rom
NVIDIA Firmware Update Utility (Version 5.414.0)
Simplified Version For OEM Only
Checking for matches between display adapter(s) and image(s)...
Adapter: GRID K2 (10DE,11BF,1028,05AA) H:--:NRM S:00,B:01,D:00,F:00
WARNING: None of the firmware image compatible PCI Device ID's match the PCI Device ID of the adapter.
Adapter PCI Device ID: 11BF
Firmware image PCI Device ID: 119F
NOTE: Exception caught.
Nothing changed!
ERROR: GPU mismatch
This is my graphics cardHow to force nvflash (if even possible) to flash an BIOS regardless which card it discovers is beyond the scope of this thread. You may search the net for a possible software solution. The root cause is your card and the existing BIOS on the chip, not the tools, nor the BIOS versions, nor software you found here.
The only possible solution is using a CLIP programmer in case you have a SOIC ship or desoldering and changing the BIOS chip to make if usable with a clip.
Manufacturer: | Nvidia |
---|---|
Model: | Quadro 3000M |
Device Id: | 10DE 0E3A |
Subsystem Id: | 1028 04A4 |
Memory: | 2048 MB |
---|
Hi guys
Does anybody have bios file or can edit an original bios to work natively in an iMac (27 inch - mid 2011) to the following Graphic card?
I have tried this BIOS file by @nikey22 but didn't work.
https://forums.macrumors.com/thread....1596614/page-436?post=29239859#post-29239859
BIOS Ver: 70.04.42.00.05
BIOS Original
Manufacturer: Nvidia Model: Quadro 3000M Device Id: 10DE 0E3A Subsystem Id: 1028 04A4 View attachment 1785240View attachment 1785239
Memory: 2048 MB
Any of my attempts using chipsec to write to the mmio where failure, machine got freeze with 3 beeps scenario, like there is a memory problem. Mind to elaborate a bit how you did it? Maybe we can do something combined using chipsec to unlock/get pass the error 28 that we get with fpt? Or somebody figured out how we can unlock the rom the hard way then flash it back with programmer and after that point just use fpt for future hacks?... I did find a way to patch & write the bootrom through EFI shell using a tool called Chipsec, but it was complicated and ridiculously slow (about 3 hours to write the full bootrom!) so the much faster / safer option is just to use a hardware programmer instead. ...
Nick left the thread more than a year ago, you will not get an answer. May be some other tried this. Just a heads up...Any of my attempts using chipsec to write to the mmio where failure, machine got freeze with 3 beeps scenario, like there is a memory problem. Mind to elaborate a bit how you did it? Maybe we can do something combined using chipsec to unlock/get pass the error 28 that we get with fpt? Or somebody figured out how we can unlock the rom the hard way then flash it back with programmer and after that point just use fpt for future hacks?
It is very hard to test various hacks on graphics/video when you have take out the display and flash the bootrom, it is very slow and sooner or later the display cable and/or board connector will crack...
Nick is gone, you will not get an answer. May be some other tried this. Just a heads up...
No more contact and he has not been online here since May 23rd of 2020. And this happens to all other participants of PMs with him in the same way. We have to assume the worst. Although his eBay business is still running and I am still no sure who @Santa's Little Helper really is we got no answers trying on various channels since then.I was not aware that Nick is gone..
What happend here I am wondering.. ?
I did notice he did not post anything for a long while..
Sorry to hear that, hope for the good...Nick is gone, you will not get an answer. May be some other tried this. Just a heads up...
I have had that problem before (3 beeps). I just pulled the memory and put two bars at a time, boot and then put the last two bars. That seemed to make it happy again.Any of my attempts using chipsec to write to the mmio where failure, machine got freeze with 3 beeps scenario, like there is a memory problem. Mind to elaborate a bit how you did it? Maybe we can do something combined using chipsec to unlock/get pass the error 28 that we get with fpt? Or somebody figured out how we can unlock the rom the hard way then flash it back with programmer and after that point just use fpt for future hacks?
It is very hard to test various hacks on graphics/video when you have take out the display and flash the bootrom, it is very slow and sooner or later the display cable and/or board connector will crack...
Looks like you did not read carefully my message, there is no problem with the RAM, they works just fine, I got 3 beeps when I try to write to mmio=Memory Mapped IO from shell using chipsec python tool in my attempts to unlock the firmware for flashing, probably best would be to just write a efi driver that would(try to) do the MMIO writes, load it from shell and then flash the firmware.I have had that problem before (3 beeps). I just pulled the memory and put two bars at a time, boot and then put the last two bars. That seemed to make it happy again.
Looks like you did not read carefully my message, there is no problem with the RAM, they works just fine, I got 3 beeps when I try to write to mmio=Memory Mapped IO from shell using chipsec python tool in my attempts to unlock the firmware for flashing, probably best would be to just write a efi driver that would(try to) do the MMIO writes, load it from shell and then flash the firmware.