Could you attach here .roms that you created and original ones?
I don't know what you did but Gigabyte HD7950 already had factory UEFI rom, so copy/paste worked flawlessly.
Cant be sure without looking at the rom what the problem is.
Ok, I managed to get it to work today, night helped me see clearer.
So what I did with the first card, the Rev1 is this:
- I went back to the original ROM I had extracted
- I downloaded the ROM on the first page of this thread, not the one by MVC but the one from the first poster.
- I copied the second half of his ROM, from 65536 (and not 65535 as I was doing yesterday)
- I pasted it in a copy of the original ROM, from the same point, making sure it was overwriting
- I used fixrom.py in Terminal to bless it or whatever term is correct (I didn't do that yesterday, that might be the difference.
I was able to flash the card that way, and got a boot screen and proper name in About this Mac.
Second card was bricked - thank god for the dual-bios switch. So I had to get my old GT120 to boot. It's a Rev2.
- I did exactly as above, and nothing worked. The strange thing -see attached files- is that the ROM extracted from the card doesn't have something clean starting at 65536. This offset contains lots of stuff.
- Having bricked/unbricked several times, I went to Gigabyte to see what other bios were available. I downloaded F13 from their website - it's attached, weirdly it's shorter so I had to convert it to ROM with ATIWinFlash. I took the resulting ROM to the Mac, and I compared to the original Rev1 ROM and it was strictly identical. So in the end I decided to flash my modded ROMrev1 onto the Rev2 card and it rebooted with Apple logo and so on.
Looking back at it now, it seems that the EFI part in the Rev2 starts earlier in the file. Which would explain why copy/pasting in the middle of a busy part was a recipe for disaster.
The other thing I understood was that the other method, using MAC7970.ROM was not going to work because the scripts I downloaded are working from EFI, not full ROM, which explains why the resulting files were bigger than 128K.