I did try it alone, got stuck in reboot loop with black screenDont think so, you can try it allone , it should work with uga framebuffer support at least for a basic gui on one display.
I did try it alone, got stuck in reboot loop with black screenDont think so, you can try it allone , it should work with uga framebuffer support at least for a basic gui on one display.
So maybe it gone south, as a last step test it with a supported system. But this is getting off topic, nowI did try it alone, got stuck in reboot loop with black screen
May be just poor connection. Take it out, use eraser to clean the PCIe cnonector. Also, give a good blow to the PCIe slot. Then make sure you fully insert the card into the slot.It booted once with the 580, but then no more. Did I brick it?
I tested a few times with the dumper. It is very safe indeed. All the required safety precautions have done automatically, highly recommended.The dumper can also flash the Mac Pro firmware. It does a verification, a 2nd readout and a full bitwise check of the flash file against the 2nd readout. Also you dont't need to read the SPI flash type as it probes what setting is compatible.
Also it stores the full verbose log of flashrom.
I want to know if this is safe as the original firmware? thanks!
I think this is a good idea. I will try resetting it first, thanks!If your better BootROM image dump is bad as the screenshot, you are in trouble.
Try to deep reset the NVRAM (reset the NVRAM continuously until you hear the fifth chime) - if you can't get a cleaner/better dump, you gonna need a BootROM clean-up and reconstruction.
Cross-flashed early-2009 Mac Pros are mess even when the NVRAM is perfectly clean, your Mac Pro currently is in a fast track to a brick.
Try to deep reset the NVRAM (reset the NVRAM continuously until you hear the fifth chime) - if you can't get a cleaner/better dump, you gonna need a BootROM clean-up and reconstruction.
This is on a "vanilla" High Sierra installation.
No OpenCore or anything else.
Maybe I should try flashing a different BIOS to the RX580?
I know not an exact comparison scenario but I was able to boot a live Linux usb efi mode boot on my Xserve 3,1 (which is essentially a 4,1 Mac Pro) and used it to flash the vbios of the AMD WX 4150 MXM GPU (which is essentially RX 560) several times. I’d like to think you could do the same using the mac pro to flash the RX 480.I forgot to specify that it has the dual bios, on one position I left the original RX480 bios and I've put the RX580 on the other, and I have already tried both to no avail.
I kept the "gaming" bios (the other was marked as "silent", probably lower frequencies and less aggressive fan curve) of the RX480 and flashed the RX580 on the other slot.
My issue is that I don't have a Windows PC anymore and I've read a user suggesting not to flash the card on a Mac Pro on Bootcamp, so I'm afraid I'm kind of stuck.
I forgot to specify that it has the dual bios, on one position I left the original RX480 bios and I've put the RX580 on the other, and I have already tried both to no avail.
I kept the "gaming" bios (the other was marked as "silent", probably lower frequencies and less aggressive fan curve) of the RX480 and flashed the RX580 on the other slot.
My issue is that I don't have a Windows PC anymore and I've read a user suggesting not to flash the card on a Mac Pro on Bootcamp, so I'm afraid I'm kind of stuck.
That's great, thank you so much! I wasn't aware of this option, I'll probably go this route since you've reported success doing this.With OpenCore, you can run the Open UEFI shell for the boot picker which will give you a command shell.
From this shell, you can use amdvbflash.efi command line tool to flash the AMD GPU without of having to use Linux or Windows. I did that a while back to add UEFI to a legacy VBIOS.
See my earlier post here where I posted the amdvbflash.efi command.
If you run the command on it's own, it will give you the Usage. It's quite easy to use.
Yes the syntax is similar to DOS & Linux.I guess the syntax is similar to the DOS tool? Where does it look for/save the vBIOS?
I have zero experience with EFI shell, I guess that there are the usual suspects such as mount command for USB drives and such?
map -b
command and it will stop the scrolling after one screenful. FSXX
and select it. E.g. in my case it was FS13
:ls
to list the contents of the Tools folder.amdvbflash -i
command to find out the AMD adapter number you have (should only be one listed if you only have card). E.g:Since I don't remember what the hell I flashed onto this card I'll probably first make a backup of both the vBIOS, load them up on a Linux/Windows VM and see what's in there and then choose and flash another vBIOS to see if I can get the bootscreen.
amdvbflash -s 0 my-dump.rom
as shown above.amdvbflash -p 0 my-new.rom
That's generally not a good idea as I do not know what VRAM my Nitro+ RX580 uses and it could brick your card.EDIT: also, if you don't mind, can you share a vBIOS dump of your card since it is a known working card for getting the bootscreen?
So I don't have to go to techpowerup and try 20 different vBIOS.
If your vBIOS has support for the same memory my RX580 has I think we're set.
Thank you so much for the detailed guide!
I'll tackle this tomorrow.
Polaris Bios Editor can show all the information of a vBIOS (and make modifications, if one wants), that's why I asked you for the dump of your card: I'll compare it in Polaris Bios Editor to mine and see if they have the support for the same VRAM and other parameters to see if they are compatible.
If they are, you have saved me lots of time and effort, otherwise I'll just have to start trying out compatible vBIOS until I get the bootscreen.
God bless linux, it worked and luckily the vBIOS MacNB2 kindly provided had the support for the same VRAM as mine.
I have discovered a big issue though: if you alter the vBios in any way, then bootscreen won't work.
This is a disaster because the stock RX580 ROM has clocks too high for the RX480, so I have to somehow edit it or it will crash when I try to run something intensive.
I've tried with the lowest clocked RX580 I could find and it still crashed when I benchmarked Unigine Valley.
I'm afraid I'll have to look for alternate vBIOS with lower clocks speeds that will give me a bootscreen...
EDIT: found it!! This Gigabyte one is very very similar to my Sapphire and gives me bootscreen, very nice clock speeds and it's perfectly stable, I've been running Unigine Valley for one hour and it never crashed.
Phew, thanks everyone, I finally have bootscreen support!
Shoutouts to @Ludacrisvp for the hint of using Linux! ;D
I just disconnected every drive and booted only with Fedora (which is my main Linux distro) Live on a usb pen drive.Glad you solved your problem.
How were you able to boot Linux without boot screen ?