Any word on amd vega hash rates? - page 27.

oskar_n8

newbie

Activity: 37

Merit: 0

Quote from: Pickle-Rick on January 20, 2018, 03:44:23 AM

Quote from: dlezama on January 20, 2018, 03:28:50 AM

Quote from: Pickle-Rick on January 20, 2018, 03:24:05 AM

So it seems aftermarket cards use Hynix memory and do not seem to overclock so well? Few I have seen struggle to maintain 950.

We’re all reference cards Samsung memory?

Mine are Samsung (Vega 56) One card can't go stable beyond 900. Some of them start failing around 930. One I tested worked at 980 but I don't know which one now and it takes forever to try one by one. So currently my rig has 1 card at 900 and 5 cards at 925. Maybe Samsung mem is overrated?

Yeah maybe. I thought it was common to get them to run 1100mhz.

As far as I know, if you have a V56 with Samsung, it should be able run around 1100Mhz, but you have to flash a V64 BIOS on it.
For my V56 with Samsung it works.

Pickle-Rick

member

Activity: 143

Merit: 10

Quote from: dlezama on January 20, 2018, 03:28:50 AM

Quote from: Pickle-Rick on January 20, 2018, 03:24:05 AM

So it seems aftermarket cards use Hynix memory and do not seem to overclock so well? Few I have seen struggle to maintain 950.

We’re all reference cards Samsung memory?

Mine are Samsung (Vega 56) One card can't go stable beyond 900. Some of them start failing around 930. One I tested worked at 980 but I don't know which one now and it takes forever to try one by one. So currently my rig has 1 card at 900 and 5 cards at 925. Maybe Samsung mem is overrated?

Yeah maybe. I thought it was common to get them to run 1100mhz.

dlezama

member

Activity: 140

Merit: 17

Quote from: Pickle-Rick on January 20, 2018, 03:24:05 AM

So it seems aftermarket cards use Hynix memory and do not seem to overclock so well? Few I have seen struggle to maintain 950.

We’re all reference cards Samsung memory?

Mine are Samsung (Vega 56) One card can't go stable beyond 900. Some of them start failing around 930. One I tested worked at 980 but I don't know which one now and it takes forever to try one by one. So currently my rig has 1 card at 900 and 5 cards at 925. Maybe Samsung mem is overrated?

Pickle-Rick

member

Activity: 143

Merit: 10

So it seems aftermarket cards use Hynix memory and do not seem to overclock so well? Few I have seen struggle to maintain 950.

We’re all reference cards Samsung memory?

ntshb

newbie

Activity: 95

Merit: 0

anyone knows why I can't seem to get shares recorded in nanopool (xmr) when I am using xmr stak?

Previously I was using xmr stak with supportxmr pool then some issues happened so i switched to cast xmr with nanopool. then I decided to give xmr stak with nanopool another go and it was hashing fine for a few mins until i added failover server addresses (bad idea, it doesn't seem to switch to other servers like claymore) so i undid those changes

but nanopool records it as offline but it regularly submits shares

https://i.imgur.com/XaSKqzM.jpg
https://i.imgur.com/vs5Hg7C.jpg

as you can see, the wallet address is correct and it is hashing fine.

un4given

full member

Activity: 192

Merit: 100

Quote from: fr4nkthetank on January 18, 2018, 07:40:28 PM

wow ddr6, well thats something. I wonder how much it will get for ethereum. Anyways we wont see this soon, and its going to be expensive and theres bound to be shortages. Miners will gobble up any amount of hardware available Sad

Until the price crashes that is. And who knows in how long thats going to be.

just in theory, GDDR6 should be doing like 60 MH on dagger hashimoto? specs say its double the speed of GDDR5

treanski

full member

Activity: 364

Merit: 106

ONe Social Network.

somebody now how to activate hbcc on a mixxed rx 580/vega rig with driver 17.10.2 or later?
cant use blockchain driver because its 12gpu rig(with blockchain driver it works)

disable+enable in devicemanager dont work, toggle the switch in settings dont work to
have windows fall update installed

i flashed vega 56 to 64.
on blockchain driver it gets recognized as vega 64 on 17.10.2 or later as 56(but i can do still registry mods)

Toughit

full member

Activity: 378

Merit: 197

Quote from: ?? on ??

Guys,

Thank you for many tips, however, I tried everything.

I have two VEga 56 with the same bios

I have two systems prepared as per instructions.

The one vega works as intended in the both systems.
The other one fails as soon as do enable/disable or toggle hbcc. Even when it's installed alone in the system. The max speed I can get with it is 1300 h/s while another one runs 1900+ h/s

F$#%$#% miracle, yeah

The only thing to add that the problematic one has trouble only with blockchain drivers. With normal ones it acts normally when enabling/disabling, however, with normal drivers I can get the same 1200-1300 h/s only

rgds
a.

Are both vegas in the same computer?

fr4nkthetank

legendary

Activity: 2294

Merit: 1182

Now the money is free, and so the people will be

wow ddr6, well thats something. I wonder how much it will get for ethereum. Anyways we wont see this soon, and its going to be expensive and theres bound to be shortages. Miners will gobble up any amount of hardware available Sad

Until the price crashes that is. And who knows in how long thats going to be.

commonorx

newbie

Activity: 99

Merit: 0

Quote from: STT on January 18, 2018, 12:07:47 PM

Quote from: commonorx on January 18, 2018, 10:57:11 AM

If only we could get a Vega 64 refresh with this

https://hothardware.com/news/samsung-begins-production-of-gddr6-high-speed-dram-for-graphics-at-a-blistering-18gbps

WOW!

well think about it. The next card logically is the vega version of the rx580 and if gddr6 is cheaper then hbm2 then yea its feasible I guess. Problem is new tech is usually not especially cheaper, Im not sure AMD is in on that design or not like they were involved with HBM (so I guess are getting it slightly cheaper)

I expect little vegas to come with the cheaper memory types. Someone know but I believe cheaper could also mean faster mining wise hence the perfect card

Just to stoke the fire of discussion on this.

https://www.tweaktown.com/news/60025/amds-next-gen-gpus-gddr6-hbm2/index.html

I am perplexed by how hard it is to get any Vegas from anywhere or vendor/3rd party manufacture.

STT

legendary

Activity: 4060

Merit: 1448

Quote from: commonorx on January 18, 2018, 10:57:11 AM

If only we could get a Vega 64 refresh with this

https://hothardware.com/news/samsung-begins-production-of-gddr6-high-speed-dram-for-graphics-at-a-blistering-18gbps

WOW!

well think about it. The next card logically is the vega version of the rx580 and if gddr6 is cheaper then hbm2 then yea its feasible I guess. Problem is new tech is usually not especially cheaper, Im not sure AMD is in on that design or not like they were involved with HBM (so I guess are getting it slightly cheaper)

I expect little vegas to come with the cheaper memory types. Someone know but I believe cheaper could also mean faster mining wise hence the perfect card

heavyarms1912

full member

Activity: 729

Merit: 114

Quote from: StellarX88 on January 18, 2018, 03:36:35 AM

Samsung is indeed still the king, I am more amazed with the intensity with you not flashing to 64 BIOS.

It is indeed flipped, p3 mem voltage has nothing to do with adjusting memory voltage, it's hardcoded to 1.25V in BIOS for 56, and 1.35V in BIOS for 64. The adjustment you make in p3_mem voltage is merely setting the bare floor voltage for GPU core, but p7_gpu voltage takes precedence; no voltage adjustment that you can perform in OverDriveNTool is going to impact mem voltage.

Yup looks like it was flipped. I was using HWInfo64 5.6.x version and updating it to 5.7 (which added Vega support shows the correct voltages now)
This is not the primary card plugged into the monitor so I guess that might explain the intensities?

EDIT: So undervolting works only through soft_pp reg mod?

commonorx

newbie

Activity: 99

Merit: 0

If only we could get a Vega 64 refresh with this

https://hothardware.com/news/samsung-begins-production-of-gddr6-high-speed-dram-for-graphics-at-a-blistering-18gbps

WOW!

StellarX88

newbie

Activity: 39

Merit: 0

Quote from: heavyarms1912 on January 18, 2018, 01:21:06 AM

Quote from: StellarX88 on January 18, 2018, 01:05:16 AM

Quote from: heavyarms1912 on January 18, 2018, 12:04:16 AM

So got a Vega 56 to play around finally.
Mining cryptonight @1926 H/s with xmr-stak at 1408 core and 925 HBM2 (900mV). Even though the overdriveNTool profile is set to run at 1408/915mV HWinfo64 says the CVDDC is at 1.25V. MVDDC changes get reflected but not the core. Any pointers?
I am already using soft pp table btw.

Core P6 is 1212, 910 mV and P7 is 1408, 915 mV
HBM2 P3 is 925, 900mV

Pretty impressive, is that a reference model with Samsung memory?
The readings on hwinfo could be flipped depending on version reading, 1.25V is actually the MVDDC, your core voltage should be sub 0.9 as for your p7 915mV.

May I know what's your xmr-stak config for this? Inn terms of intensity.

Reference with Samsung. 1932 intensity, 2 threads. I am not sure if it's flipped. Cause it reflects the changes I do in MVDDC in HWInfo.

Samsung is indeed still the king, I am more amazed with the intensity with you not flashing to 64 BIOS.

It is indeed flipped, p3 mem voltage has nothing to do with adjusting memory voltage, it's hardcoded to 1.25V in BIOS for 56, and 1.35V in BIOS for 64. The adjustment you make in p3_mem voltage is merely setting the bare floor voltage for GPU core, but p7_gpu voltage takes precedence; no voltage adjustment that you can perform in OverDriveNTool is going to impact mem voltage.

heavyarms1912

full member

Activity: 729

Merit: 114

Quote from: StellarX88 on January 18, 2018, 01:05:16 AM

Quote from: heavyarms1912 on January 18, 2018, 12:04:16 AM

So got a Vega 56 to play around finally.
Mining cryptonight @1926 H/s with xmr-stak at 1408 core and 925 HBM2 (900mV). Even though the overdriveNTool profile is set to run at 1408/915mV HWinfo64 says the CVDDC is at 1.25V. MVDDC changes get reflected but not the core. Any pointers?
I am already using soft pp table btw.

Core P6 is 1212, 910 mV and P7 is 1408, 915 mV
HBM2 P3 is 925, 900mV

Pretty impressive, is that a reference model with Samsung memory?
The readings on hwinfo could be flipped depending on version reading, 1.25V is actually the MVDDC, your core voltage should be sub 0.9 as for your p7 915mV.

May I know what's your xmr-stak config for this? Inn terms of intensity.

Reference with Samsung. 1932 intensity, 2 threads. I am not sure if it's flipped. Cause it reflects the changes I do in MVDDC in HWInfo.

StellarX88

newbie

Activity: 39

Merit: 0

Quote from: heavyarms1912 on January 18, 2018, 12:04:16 AM

So got a Vega 56 to play around finally.
Mining cryptonight @1926 H/s with xmr-stak at 1408 core and 925 HBM2 (900mV). Even though the overdriveNTool profile is set to run at 1408/915mV HWinfo64 says the CVDDC is at 1.25V. MVDDC changes get reflected but not the core. Any pointers?
I am already using soft pp table btw.

Core P6 is 1212, 910 mV and P7 is 1408, 915 mV
HBM2 P3 is 925, 900mV

Pretty impressive, is that a reference model with Samsung memory?
The readings on hwinfo could be flipped depending on version reading, 1.25V is actually the MVDDC, your core voltage should be sub 0.9 as for your p7 915mV.

May I know what's your xmr-stak config for this? Inn terms of intensity.

joemanabat05

member

Activity: 168

Merit: 13

I also read that sir it looks like that new version is coming, I use the latest core and it is very useful and quiet amazing.

heavyarms1912

full member

Activity: 729

Merit: 114

So got a Vega 56 to play around finally.
Mining cryptonight @1926 H/s with xmr-stak at 1408 core and 925 HBM2 (900mV). Even though the overdriveNTool profile is set to run at 1408/915mV HWinfo64 says the CVDDC is at 1.25V. MVDDC changes get reflected but not the core. Any pointers?
I am already using soft pp table btw.

Core P6 is 1212, 910 mV and P7 is 1408, 915 mV
HBM2 P3 is 925, 900mV

R0mi

full member

Activity: 305

Merit: 148

Theranos Coin - IoT + micro-blood arrays = Moon!

Quote from: ?? on ??

Hello guys,

First I set up one VEGA 56, Cast Xmr, blockchain driver, toggling hbcc on/off, and I get my 1900+ H/s.

Bought another VEGA 56, riser setup, everything identical. As soon as toggling hbcc on/off, artefacts kicks in and everything breaks. I tried 6+ hr every possible setup, reinstallation of drivers as well as windows, I even tried to put it on the separate machine. Nothing has worked. If I toggle HBCC on/of or do disable/enable, that f#$$#$ card just dissapears/stops working, see attached screen.

So at the moment I am running both of it, for one card hbcc on/off works and I get 1900+, for other I can't do anything, it works 1300 H/s

Anyone had any similar issues?

Appreciate any insights,
Alex

Screen
https://ibb.co/iqxpz6

I agree with Poop135: first, disable Crossfire and Ulps in the registry. Then make sure you are on Windows 10 Fall creator's update (build 1709, not 1507, not 1511, not 1603).

And do visit vegaminingblog by CircusDad if you haven't already. Also, try disabling the --fastjobswitch option and see if the card runs stable.

shYter90

newbie

Activity: 19

Merit: 0

Quote from: Smashingmanson on January 17, 2018, 06:32:25 AM

What clocks are you using?

Could be sillicon lotery, my 56 for example doesnt really like anything above 935Mhz on memory.

so what's hashrate you have on your vega 56 with 935Mhz on memory?
have you flashed also bios to 64?

Topic: Any word on amd vega hash rates? - page 27. (Read 202722 times)