PC Graphics

[cgavaller2]

Hey all! I’m tinkering with a Radeon Pro V340l (dual Vega 10 GPUs, 8GB Hynix HBM each) that I snagged off eBay. Trying to crossflash it to a Vega 56 vBIOS so it plays nice with Windows 10. Since AMD’s official Vega 56 BIOS only works with Samsung memory (and this card uses Hynix), I flashed both GPUs with an ASUS Strix Vega 56 BIOS instead (Using ATIFlash 2.93 as well as a CH341a hardware flasher).

Current Status:

• GPU #1 works perfectly after flashing.

• GPU #2 shows Code 43 in Device Manager. If I disable/re-enable it, Windows claims it’s "working," but it’s clearly not functional.

What I’ve Tried:

• Latest Adrenalin + Enterprise drivers: Both fail immediately.

• Using modded Radeon ID (R.ID) drivers: Only fully supports GPU #1.

This feels like a driver/software hiccup. I’ve dealt with similar weirdness before (like flashing a Firepro S9300x2 to Fury X BIOS), but this one’s got me stumped. I’ll drop some pics below for context. Anyone run into this before? Open to ideas! I also want to note that I am using my motherboard's integrated graphics for display out and am just planning on using the GPU's for compute or passing through to VM's for 3D rendering. My motherboard is an Asrock Rack EP2C612WS with dual Xeon E5-2699v3's. It could be a PCIe config issue but I don't know what other settings to mess with. Thanks!

(Note: The cards only display as a V64 due to the driver. They are flashed with This Bios, not a Vega 64 one.)

Chipset BIOS SettingsDevice ManagerCode 43 on Second GPUGPU-Z on each GPUHWInfo SHows all data for one GPU, but not other?Task Manager only showing one GPU

[Kwell42]

https://www.techpowerup.com/vgabios/198618/xfx-rxvega56-8192-171119

This is xfx Vega 56 with 150w tdp, it's a middle ground between the 110w stock and 210w normal.

[ShadowSword]

Sorry If I'm misinterpreting this or sounding stupid (I'm kinda a newbie), but you were able to turn a 50 dollar GPU you can find on eBay, into 2 Vega 64s (That are limited by power) without even flashing it! Even if you're not able to get SR-IOV working that is very impressive. Couldn't you use this as just a dual GPU setup for AI or something? or do 3d work/games with one of the GPUs?

[hastock3]

its not 2 vega 64's because they only have 56 CUs. its more like 2 vega 56's which are limited to 110w. they just show up as vega 64's because of the modded drivers. we're just trying to get them to work properly in windows as a more proper vega 56.

AI is exactly what im using these for. i have 3 of them set up in linux running ollama.  They are natively supported in linux so none of that is relevant to this conversation.

[cgavaller2]

Yes, like @hastock3 stated they are effectively dual Vega 56's. They work without vBIOS flashing using R.ID drivers, and 3D rendering (DirectX, Vulkan, etc.) is supported. Although take it with a grain of salt, as this is 100% not officially supported in any way, so don't get your hopes up in case it won't work in your use case for any number of reasons regarding compatibility. I just wish the crossflashed vBIOS would work for both GPUs.

[Hoji]

I also recently purchased a 340 and have been trying to get it to recognize in Windows. At first, I tried to flash the bios as cgavaller2 stated worked for them. But when using Atiflash 293 it gives the error "Adapter not found".

After not getting much success from Atiflash I tried using the R.ID drivers. I have tried using PVN 24.3.1 and PVN 23.40, which then would make the cards appear in the device manager as either Vega 64 cards or MI25 depending on if I used the Consumer kernels or Enterprise. However, the issue with R.ID is that the cards have an error stating "This device cannot find enough free resources that it can use. (Code 12)

If you want to use this device, you will need to disable one of the other devices on this system."

If anyone is able to get it working with R.ID please let me know what Kernel version and other settings you used.

[cgavaller2]

I was able to use R.ID drivers on the default vBIOS. Try that and let me know how it goes.

[Hoji]

Tried using 24.3.1 RID, which shows the cards in Device Manager as Vega 64s'. But other than that no other changes.

I have sr-iov, resizable bar, and above 4GB decoding enabled. Every time I try to open up GPU-Z with 24.3.1 installed both with the latest PVN RID driver in either Consumer (Vega 64) or Enterprise (MI25) it crashes the system.

I will try to mess around in the BIOS with sr-iov.

[hastock3]

Oh i just noticed something in your screenshots. were you still using the R.ID drivers after flashing the bios'? i tried using the default amd drivers and could never get more than 1 gpu working.

[cgavaller2]

Yes, The default AMD drivers never worked for me so I was using the R.ID ones for the default vBIOS as well as after flashing. I still am getting the error of one GPU per card showing a code 43 with any vBIOS other than the default. Will try to look into it more when I have some time to mess with them more. If I could just unlock the power limit on the stock BIOS, this wouldn't be a problem, but the stock vBIOS doesn't allow power limit modification with software, and it's not as easy as just modifying the vBIOS as they're all signed and won't boot if edited (theoretically). I've tried software like OverdriveNTool and MorePowerTool but haven't gotten either to work unfortunately.

[hastock3]

pretty sure this error is an sr-iov issue. if you have sr-iov (or i think sometimes for intel its called VT-d) you need that enabled. Otherwise you'll have to use Linux. i messed with these a lot in linux before i tried windows and if you dont have sr-iov then linux will work (dont ask me how, this is just what i observed).

[hastock3]

Hey so i decided to flash 1 of my cards to a compatible bios i found. i now have a problem where only 1 card works. its not an virtualization problem as i have both cpu virtualization and sr-iov turned on. is it possible i just had a bad flash and now it doesn't work? i used a ch341a (the version with built in voltage control so i did 3.3v in case you were curious). or is there some other problem?

[cgavaller2]

I'm having the same issues when running Vega 56 vBIOS's as well. I also tried a Radeon Pro WX8200 I believe it was called? maybe the V340 vBIOS has some element of it that lets both GPUs work but I really want to solve this issue.

[hastock3]

okay well im glad to hear that its not just me. i had mine running in my gaming pc along with my 6900xt and i could only ever get 1 gpu to work. honestly im thinking of just flashing this one back to stock and set up my 3 cards in linux instead. linux just works which might be all it takes for me to give up.

i never tried the R.ID drivers properly because i found out later that my test rig doesnt have sr-iov exposed in the bios and so there was no way to get both gpus to show up as working correctly in windows. @cgavaller2 just to clarify you used the R.ID drivers and didnt have any trouble right? it was just plug and play? did you use the latest driver pack 24.3.1?

[cgavaller2]

Yes, R.ID drivers worked out of the box I believe. Not sure of the version but whatever was the newest as of a week ago is what I used.

[Kwell42]

Hey I was just wondering, did you try to pass through any cards to windows and using r.id drivers with linux?  I'm still waiting for some parts but I have my cards. I'm still thinking that someway somehow I can get my gaming server working.

[hastock3]

also @cgavaller2 i was just looking back at some of your original posts and what happened with the Asus bios? you said it worked perfectly but does it not now?

[cgavaller2]

When I first enabled SR-IOV both GPUs showed up and worked for a whole day of testing on the v56 vBIOS. After that, I started getting the code 43 error again.

[ghrdz]

what i did to fix the issue was flashed the second gpu on the card with asrock vega 56 bios and left the other one as it is (v340).  installed normally the asrock 56 while i installed the v340 using the inf file from the amd folder. i have tested it with times spy and furmark and played with it with different versions of tomb raider. seems to be working well. im using windows 11 and make my settings on the graphics settings  by gpu passthrough since im unable to make the mini display to work. ill test it later with aster multi seat hoe this post will solve some of our issuess..  🙂

[Kwell42]

Thanks for the update

[hastock3]

@ghrdz hey just came back to check on this forum. what you described sounds like it could work well. can you give step by step instruction for what you did? the wording here is a bit confusing.

[ghrdz]

[ghrdz]

First - Flash the first V340 to WX8200 using AtiFlash 2.93 or leave it as it is.

Second- Flash the second V340 with a Vega 56 BIOS intended for ASRock/Asus Vega 56 cards with hynix bios

NOT TO DO - Flashing both GPUs with the Vega 56 BIOS, only one of the GPUs will work.

Third- Install drivers normally. 

pls see pictures for more info.

[hastock3]

@ghrdz  Which gpu is "first"? is it the one closest to the power connectors or is it the one closest to the minidp?

[ghrdz]

do amdvbflash -i

the one on the top I think is the one closer to the dp.

[hastock3]

i use a ch341 manual programmer. do you know for certain which one it is? ive not used amdvbflash successfully with this card before.

[ghrdz]

i haven't opened my card yet too lazy to do it after i taped the fan. just use AtiFlash 2.93 and do the flashing in windows 10.  use amdcleanuputility before flashing. the command i used should just be this

"amdvbflash.exe -f -p (card number) (name of rom file)"

[hastock3]

hey do you mind posting the exact bios files you used? or a link to a google driver or smt? i just want to make sure i didnt grab a bad file.

[ghrdz]

just get the asrock or asus from the  techpowerup as well as the wx8200 it just works

[Hoji]

Gave up trying to get the card working in Windows 10. I did try Windows 11, which gave the same result. I have been testing today with Proxmox, which thankfully detects the cards correctly, however, still having issues with passthrough. I have tried following The Ultimate Beginner's Guide to GPU Passthrough (Proxmox, Windows 10) on reddit. But keep having is...

Those of you working on Linux with these cards, how does that look? Are you just installing a distro and then running RID drivers?

[cgavaller2]

Funnily enough I just booted up my server again after about a week and had all 6 GPU's across 3 cards recognized, so weird. They're flashed to a WX8200 vBIOS currently. The power limit is still locked, but it's 170w vs 110w at least so that's a bonus! Knowing my luck, it'll probably either crash or GPU's will disappear out of nowhere lol.

[TreverRhoads]

New to the forum, but I figured I could chime in as I just picked up one of these cards and put it in my "new" server... I tried Windows Server 2019 as that is what my processors are listed as supported in (2X Xeon Gold 6130) and when I booted into Windows the cards were recognized, but no drivers would actually work (no bios mods done) and the card would just sit there and suck power and get hot to the point of causing my server to lock up. When I loaded up Proxmox I used that to pass through the card (only 1 GPU of the two on the card) to a VM and the card is behaving nicely in a Debian VM. 

Here is the output from sudo lspci -v -s 06:10.0
06:10.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 [Radeon Pro V340/Instinct MI25x2] (rev 05)
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 [Radeon Pro V340/Instinct MI25x2]
Physical Slot: 16-2
Flags: bus master, fast devsel, latency 0, IRQ 21
Memory at 383800000000 (64-bit, prefetchable) [size=8G]
Memory at 383a00000000 (64-bit, prefetchable) [size=2M]
Memory at 88600000 (32-bit, non-prefetchable) [size=512K]
Expansion ROM at 886a0000 [disabled] [size=128K]
Capabilities: [48] Vendor Specific Information: Len=08 <?>
Capabilities: [50] Power Management version 3
Capabilities: [a0] MSI: Enable- Count=1/4 Maskable+ 64bit+
Capabilities: [c0] MSI-X: Enable+ Count=3 Masked-
Kernel driver in use: amdgpu
Kernel modules: amdgpu

I think I just enabled none-free firmwares, but I honestly cannot remember. I don't see r.id drivers in my downloads directory, so unless I downloaded them to a USB drive I am likely just using default AMD drivers. 

Now I just need to figure out how I am going to cool this thing, and then if I can squeeze another one in!

[Kwell42]

I got my system working with proxmox, passing through cards with the stock v340 bios to windows 10 and 11 and using r-id drivers got me nowhere. They just come in broken, in gpuz I get no clocks or anything, can't get them to render, etc. So I will be flashing them and reply again hopefully soon.