AMD Radeon Pro v540 Research Thread

[Beatyoubeach]

the blue connectors have the same amount as my firepro w8100 sink connector i also bought the v540 and verified it, its even in same order

the blue connectors have the same amount as my firepro w8100 sink connector i also bought the v540 and verified it, its even in same order

also i have a intel 12th gen system with PCI GEN 5 that I can switch to 4 I would like to help the stuff out.

 

[itanium_nostalgia]

I'd love to see some progress on this so I want to add some additional information to my last message.

Attached you can find a .zip bundle of all the vbios I dumped off my card. It's fairly self explanatory - they're cataloged by the side of the board they were dumped from and then distance from the MDP port (there are _2 of each dump for verification). Screenshots too.

On my card, you can see on the GPU side:

• the vbios nearest to the MDP port is legacy bios name /number D3020100.012 - it does NOT have EFI GOP.
• the vbios farthest from the MDP port is legacy bios name / number D3020100.09G - it does have EFI GOP.

Equally, on the backside:

• the vbios nearest to the MDP port is legacy bios name /number D3020100.09G - it does have EFI GOP.
• the vbios farthest from the MDP port is legacy bios name /number D3020100.012 - it does NOT have EFI GOP.

 

[LabRat 891]

I'd love to see some progress on this so I want to add some additional information to my last message.

Attached you can find a .zip bundle of all the vbios I dumped off my card. It's fairly self explanatory - they're cataloged by the side of the board they were dumped from and then distance from the MDP port (there are _2 of each dump for verification). Screenshots too.

On my card, you can see on the GPU side:

• the vbios nearest to the MDP port is legacy bios name /number D3020100.012 - it does NOT have EFI GOP.
• the vbios farthest from the MDP port is legacy bios name / number D3020100.09G - it does have EFI GOP.

View attachment 299707

Equally, on the backside:

• the vbios nearest to the MDP port is legacy bios name /number D3020100.09G - it does have EFI GOP.
• the vbios farthest from the MDP port is legacy bios name /number D3020100.012 - it does NOT have EFI GOP.

View attachment 299708

Progress! Several people have been asking for vBIOS info/dumps. Thank you

(Sadly, IIRC vBIOS modding post-Polaris is just about impossible. I'd be more than happy to be wrong)

 

[Beatyoubeach]

the blue connectors have the same amount as my firepro w8100 sink connector i also bought the v540 and verified it, its even in same order


also i have a intel 12th gen system with PCI GEN 5 that I can switch to 4 I would like to help the stuff out.

 

[Veseleil]

Nothing better than a natural light?

"Hey man, how was your day, anything special? - Nah, I just took my V540 for a walk and took some shots while at it. Then we sat on a pavement, talked about love, death and robots, time flew... Ended up watching the sunset together. "

 

[eidairaman1]

I'd love to see some progress on this so I want to add some additional information to my last message.

Attached you can find a .zip bundle of all the vbios I dumped off my card. It's fairly self explanatory - they're cataloged by the side of the board they were dumped from and then distance from the MDP port (there are _2 of each dump for verification). Screenshots too.

On my card, you can see on the GPU side:

• the vbios nearest to the MDP port is legacy bios name /number D3020100.012 - it does NOT have EFI GOP.
• the vbios farthest from the MDP port is legacy bios name / number D3020100.09G - it does have EFI GOP.

View attachment 299707

Equally, on the backside:

• the vbios nearest to the MDP port is legacy bios name /number D3020100.09G - it does have EFI GOP.
• the vbios farthest from the MDP port is legacy bios name /number D3020100.012 - it does NOT have EFI GOP.

View attachment 299708

Open gpu-z and upload the bios to the VGA Bios Collection so its not in the thread and can be found there please,

 

[itanium_nostalgia]

I am not able to currently. Those vbios dumps are from a hardware programmer.

 

[eidairaman1]

I am not able to currently. Those vbios dumps are from a hardware programmer.

I was going to say have the card in another slot and a bootable card or igp and do it that way...

 

[itanium_nostalgia]

I was going to say have the card in another slot and a bootable card or igp and do it that way...

No, sorry, I should clarify. I would if I could.

My daily driver is a NUC 11 Extreme which won’t fit the card, and I’ve a quirky Cavium ThunderX system which is useless for this purpose.

Anything else that could fit/run the card is in storage.

 

[Beatyoubeach]

Nothing better than a natural light?

"Hey man, how was your day, anything special? - Nah, I just took my V540 for a walk and took some shots while at it. Then we sat on a pavement, talked about love, death and robots, time flew... Ended up watching the sunset together. "

i will if it works in like 12-15 hours

I was going to say have the card in another slot and a bootable card or igp and do it that way...

i use a gtx 1080 as my main and w8100 as a cpu helper in a word so i can dump that bios

 

[Beatyoubeach]

i will if it works in like 12-15 hours


i use a gtx 1080 as my main and w8100 as a cpu helper in a word so i can dump that bios

I failed the mxgpu works in my system a little bit but it does not show up in GPUz both of the rear blue lights work including the white ones and my ram goes down so dose my gtx 1080 GPU usage

 

[Catch2223]

Sure, I hope I recall the steps correctly. Its important to note that we have to use linux aws drivers amdgpu-pro-20.20-1184451-ubuntu-18.04 . I could not manage to get any other package to work so far.

For OS we need Ubuntu Server 18.04.5, boot and install HWE kernel. We should be on 5.4. Once system is up:

sudo dpkg --add-architecture i386
sudo apt-get update -y && sudo apt upgrade -y

Installing drivers

sudo -i
tar xf amdgpu-pro-20.20-1184451-ubuntu-18.04.tar.xz
cd amdgpu-pro-20.20-1184451-ubuntu-18.04
./amdgpu-pro-install --opencl=pal --headless

Reboot after installing driver.

Some additional software

sudo apt install build-essential cmake opencl-headers ocl-icd-opencl-dev clinfo

Verify that OpenCL platform works

clinfo

Two platforms should be available

Get binary build of xmrig

wget https://github.com/xmrig/xmrig/releases/download/v6.19.2/xmrig-6.19.2-linux-x64.tar.gz
tar -xf xmrig-6.19.2-linux-x64.tar.gz
cd xmrig-6.19.2-linux-x64
./xmrig --opencl --no-cpu

Again, Im doing this from memory, and don't have OpenCL installed on my current test bench. Let us know how it works.

I'm trying to reproduce your success but am not having much luck. Here's what I have tried following the guide:

1. Installing Ubuntu Server 18.04.5 on bare metal
2. Updating the kernel to HWE 5.4
3. Installing AWS driver version mentioned above
4. Restart
5. Install additional tools mentioned above
6. Run "clinfo" but the GPUs do not appear.

Dmesg log is attached with the error though this seems to be a pretty non-descript error.

I did try adding kernel parameters for experimental hardware and for the feature mask but that made no difference. I've also tried on 18.04.6 again with no difference. If you have any idea what might be missing to get this thing talking I would greatly appreciate the input.

 

[mczkrt]

I don't think I ever saw fatal gpu error while tinkering. But you need to have message:

Initialized amdgpu

after installing drivers and rebooting, before any further steps.

I followed this guide:

AMD drivers for your EC2 instance - Amazon Elastic Compute Cloud

AMD driver information and install instructions for EC2 instances.

docs.aws.amazon.com

Few things I have setup in BIOS:
Above 4G decoding - enable
Resizable BAR - disable (if present)
IOMMU - disable

I'm not using any kernel parameters except for virtual display, but drivers also worked fine without any outputs.

 

[Beatyoubeach]

I don't think I ever saw fatal gpu error while tinkering. But you need to have message:

Initialized amdgpu

after installing drivers and rebooting, before any further steps.

I followed this guide:

AMD drivers for your EC2 instance - Amazon Elastic Compute Cloud

AMD driver information and install instructions for EC2 instances.

docs.aws.amazon.com

Few things I have setup in BIOS:
Above 4G decoding - enable
Resizable BAR - disable (if present)
IOMMU - disable

I'm not using any kernel parameters except for virtual display, but drivers also worked fine without any outputs.

so if sizable bar is enabled it won't show up since I enabled mine and I didn't get the mxgpu to show up

 

[PixelButts]

so if sizable bar is enabled it won't show up since I enabled mine and I didn't get the mxgpu to show up

Fascinating behavior that's for sure

 

[LabRat 891]

Any updates on Windows compatibility? I saw some new drivers posted in the LTT thread.

I'm considering getting another MI25 (for crossfire Vega 16GB), but would rather spend a little more on a single BC-160/v520 or V540, if working.

 

[PixelButts]

Any updates on Windows compatibility? I saw some new drivers posted in the LTT thread.

I'm considering getting another MI25 (for crossfire Vega 16GB), but would rather spend a little more on a single BC-160/v520 or V540, if working.

Got a link to that thread? I'll save those drivers

 

[LabRat 891]

Got a link to that thread? I'll save those drivers

Windows driver for AMD Radeon Pro V540

I bought an interesting video card but i need drivers for tesing. There is no information or driver on the AMD site. I know this is an ES card but the one GPU version is a released card (V520) This is navi12 dual gpu, like a navi10 5700XT but with HBM2. Power connector is server grade EPS (max 33...

linustechtips.com

 

[PixelButts]

Windows driver for AMD Radeon Pro V540

I bought an interesting video card but i need drivers for tesing. There is no information or driver on the AMD site. I know this is an ES card but the one GPU version is a released card (V520) This is navi12 dual gpu, like a navi10 5700XT but with HBM2. Power connector is server grade EPS (max 33...

linustechtips.com

This definitely isn't the original zip, but it does provide a nice instructional document for installation at least.
I still need a proper machine for this (and man, my purchases have been kinda wack) but I will amass a pile of any drives found for this in the mean time.

 

[masterdeejay]

This card is not working when REBAR is enabled (not booting, black screen). Very sad because i modded my workstation for the Intel A380 card as primary video card.
But what happens if i connect it hot? (hotswap in pcie slot)

 

[mczkrt]

Here is a sidenote, but I think it is still relevant:

I managed to test V520 on AWS using drivers posted on LTT and I can confirm they work. I'm attaching some screenshots with an overview of performance.

Some observations:
- Boost clock around 1600MHz compared to 1450MHz on V540
- Power draw much closer to 130W PPT
- OpenCL is not available
- GravityMark D3D12 test could not start

 

[mczkrt]

I had a look at BIOS files posted by @itanium_nostalgia and there are notable differences between them.

compare

That perhaps explains high initial power draw. Maybe second BIOS is being initialized once drivers are installed.

I would like to ask resident AMD experts on viability of crossflashing V520 BIOS. I see this as most reasonable way forward, now that we have confirmed working drivers for V520.

amd radeon v520 pro VBIOS

8 GB HBM2, 1150 MHz GPU, 334 MHz Memory

www.techpowerup.com

EDIT Card seems to respond well to amdvbflash. ROMs can also be read.

 

[eidairaman1]

I had a look at BIOS files posted by @itanium_nostalgia and there are notable differences between them.
View attachment 304936View attachment 304937
compare
View attachment 304938View attachment 304939
That perhaps explains high initial power draw. Maybe second BIOS is being initialized once drivers are installed.

I would like to ask resident AMD experts on viability of crossflashing V520 BIOS. I see this as most reasonable way forward, now that we have confirmed working drivers for V520.

amd radeon v520 pro VBIOS

8 GB HBM2, 1150 MHz GPU, 334 MHz Memory

www.techpowerup.com

EDIT Card seems to respond well to amdvbflash. ROMs can also be read.
View attachment 304950

V520 is it a mxm part?

TechPowerUp

Extensive repository of graphics card BIOS image files. Our database covers submissions categorized by GPU vendor, type, and board partner variant.

www.techpowerup.com

Oh on here it states never released...

AMD Radeon Pro V540 Specs

AMD Navi 12 x2, 1600 MHz, 2304 Cores, 144 TMUs, 64 ROPs, 8192 MB HBM2, 1000 MHz, 2048 bit

www.techpowerup.com

 

[mczkrt]

Here is another ROM, dumped from V520, still different from the rest.

AMDVBFLASH version 4.71, Copyright (c) 2020 Advanced Micro Devices, Inc.

    Product Name is :    NAVI12 A0 XT D30501 8GB EVAL 1150e/334m HYN/SAM
    Device ID is    :    7360
    Bios Version    :    017.003.000.007.014041
    Bios P/N is     :    113-D3050100-101
    Bios SSID       :    0A34
    Bios SVID       :    1002
    Bios Date is    :    07/08/20 15:08

From TPU

AMDVBFLASH version 4.71, Copyright (c) 2020 Advanced Micro Devices, Inc.

    Product Name is :    NAVI12 A0 GLXLB D30503 8GB BC160 1150e/334m HYN/SAM
    Device ID is    :    7360
    Bios Version    :    017.003.000.008.017114
    Bios P/N is     :    113-D3050301-X00
    Bios SSID       :    0A34
    Bios SVID       :    1002
    Bios Date is    :    07/27/21 08:30

Which seems to be from BC-160 in fact.

Anyway I don't think this file is complete, its only 256KB, and other ROMs seem to have valid data after 3FFFF offset - starting at 43100

 

[mczkrt]

Despite no forthcoming opinions, I went on flashing adventure anyway. It turns out that card can be made to work in Windows, however daily use is out of question (at present). Have CH341A with add-on clip on hand.

How to get there:
- Have some way to flash a vbios from software. I used my working Linux setup, but booting from USB with some most recent kernels (6.2 tested) should also initialize GPU properly. DOS/UEFI I have not tested and none of the available Windows amdvbflash allowed me to program vbios. AMDVBFlash 4.71 confirmed as working.
- Flash this vbios

amd radeon v520 pro VBIOS

8 GB HBM2, 1150 MHz GPU, 334 MHz Memory

www.techpowerup.com

to device 1 (second GPU, away from the bracket, reason will be made clear later).

sudo ./amdvbflash -p 1 258445.rom -f

- Reboot straight into Windows, DO NOT power cycle or hard reset.
- Manually install drivers posted on LTT to the flashed Video Controller. Check properties - select one with higher bus ID.

Radeon Pro V520 Win10x64.zip

drive.google.com

- I was connected through RDP, so V520 was automatically used for rendering. If you are using secondary GPU, find a way to select primary rendering device.
- One GPU should be ready to play around.
- Now the best part. Once you get bored, shutdown the machine. Oh wait, "I have to check something else" - too bad, computer will no longer POST with this card connected. Switch off/on AC power - first POST will always fail, second after hard reset will pass, but flashed GPU will no longer be detected in OS. (That was my experience, YMMV)
- Now it is time to restore vbios with CH341A, luckily SPI chip of the second GPU we were flashing is on the backside of the card.
- Good luck, if You dare.

My quest for the weekend - flash both ROMs and see what happens.