Search content
Sort by
Showing 20 of 49 results by Hellae
I'll just leave this here...
Hey got some working drivers! Compute toggle finally working for Vega on Cnote?
Too bad there's no real performance gain?
No real need in pulling rigs down to update just yet. Although, it would be nice to switch between Cnote and Neoscrypt at will...
Working, yes. But still WIP.
Compute Toggle is only needed for Polaris. All compute instructions have always been available for vegas.
This driver has no gains, in fact for me is showing a decrease of 50 H/s per card, but no longer requires to disable / enable devices. Oh, and it is by far more stable, even in gaming.
All my tests ended up in 2016/2016 being the best value.
Tried 1 2 3 4 and even 6 threads. Tried combinations of those thread intensities with worksizes of 4 8 and 16. None has beaten dual 2016, but it matters little when after 1 minute you are mining bellow a V56.
But even with the min fan speed at the MAX (4500RPM) the memory quickly goes above 70º (in less than a minute) and the hash quickly drops from 2100 to 1700ish, sometimes to even lower values down to 1450...
The blower is either not as good as the RX counterparts or it's the 1600MHz without underclock that are contributing for the massive temperature increase in a matter of seconds.
All P-States are unlocked via overdriveNtool. Tried the same core/voltages as in the 64 and the result got worse in hash with the same thermal issues.
Bottom line seems to be: If you ordered it to mine, try to cancel/resell it and get a 56 or 64 instead.
Tried 1 2 3 4 and even 6 threads. Tried combinations of those thread intensities with worksizes of 4 8 and 16. None has beaten dual 2016, but it matters little when after 1 minute you are mining bellow a V56.
But even with the min fan speed at the MAX (4500RPM) the memory quickly goes above 70º (in less than a minute) and the hash quickly drops from 2100 to 1700ish, sometimes to even lower values down to 1450...
The blower is either not as good as the RX counterparts or it's the 1600MHz without underclock that are contributing for the massive temperature increase in a matter of seconds.
All P-States are unlocked via overdriveNtool. Tried the same core/voltages as in the 64 and the result got worse in hash with the same thermal issues.
Bottom line seems to be: If you ordered it to mine, try to cancel/resell it and get a 56 or 64 instead.
Can't keep my Frontier at 2100. In a minute it goes right down to 1700/1800 range.
Already tried with max min fan speed. Something is missing me.
For now all I'm doing is setting the memory to 1100, the memory voltage to 905mV and running 2 threads of 2016 intensity.
All the core values are still at default.
What am I missing?
Already tried with max min fan speed. Something is missing me.
For now all I'm doing is setting the memory to 1100, the memory voltage to 905mV and running 2 threads of 2016 intensity.
All the core values are still at default.
What am I missing?
I was wondering has anyone tried out the vega frontier edition yet. do the guides to get it running to around 1900 h/s work on the FE edition as well? I was going to build a rig for rendering animations as well, and I wanted to know if I should go with the Frontier or 56/64 way. I know about all of the guides and setups to make the 64 work to 1900 h/s and was wondering if these will work (including that blockchain driver) for the FE as well.
I have had 1 Vega Frontier running on a Z170 board, I have 2 others but disabling and re-enabling fails to re-enable the other 2 although I managed to get 2 running once both at max speed.
I have now had one VF running for 2 weeks solid with xmr-stak-amd, average 2106H/s peak 2500+ mining electroneum (2 threads 2016)
blockchain driver, when it was running 2 cards was following a clean install on a reinstalled windows (using windows repair feature)
Mind to share your full config for FE? Driver, Power play table if using any, and stak config? All my tests ended up in a max of 1400 H/s although I keep seeing reports od 2500 H/s
quite simple really, vega fe in x16 slot, nothing tweaked, disable then re-enable (also using mining settings for GB-z170-ud5 mobo bios)
afterburner core 1646 mem 1102 custom fan profile to kick in around 47, temp 65 ish power 50
xmr-stak-amd, two threads of 2016 , I would set it higher but not sure what values to use
windows manages virtual ram but I have 64GB fast ram
just checked my new high score is 2601h/s peak, average 2106h/s (these are reflected at hashparty pool)
with a clean windows repair install which deletes all drivers I managed to get 2 cards running at full speed but once I started fiddling I couldn't get the second card working
I don't mess with card settings on driver, could possibly go higher but I'm looking for stability while mining ETN
Thanks! But you're using the blockchain driver for Frontier, right? That one is a pro driver without wattman access.
I'll do some work based on your input. Will let you know if I find something else.
I was wondering has anyone tried out the vega frontier edition yet. do the guides to get it running to around 1900 h/s work on the FE edition as well? I was going to build a rig for rendering animations as well, and I wanted to know if I should go with the Frontier or 56/64 way. I know about all of the guides and setups to make the 64 work to 1900 h/s and was wondering if these will work (including that blockchain driver) for the FE as well.
I have had 1 Vega Frontier running on a Z170 board, I have 2 others but disabling and re-enabling fails to re-enable the other 2 although I managed to get 2 running once both at max speed.
I have now had one VF running for 2 weeks solid with xmr-stak-amd, average 2106H/s peak 2500+ mining electroneum (2 threads 2016)
blockchain driver, when it was running 2 cards was following a clean install on a reinstalled windows (using windows repair feature)
Mind to share your full config for FE? Driver, Power play table if using any, and stak config? All my tests ended up in a max of 1400 H/s although I keep seeing reports od 2500 H/s
So... HBCC isn't what causes the higher hashrate.
Any ideas of what could be being triggered with the disable/enable method?
I'm afraid that this can be somewhat of a bug on the Beta driver that will never be ported to the Gaming driver.
Disabling the card would clear the frame buffer, but beyond that Im not sure what else a re-initialization would do
Anyone up for a brainstorm?
Any ideas of what could be being triggered with the disable/enable method?
I'm afraid that this can be somewhat of a bug on the Beta driver that will never be ported to the Gaming driver.
Disabling the card would clear the frame buffer, but beyond that Im not sure what else a re-initialization would do
Anyone up for a brainstorm?
Hi all,
Out of curiosity... are you guys just focused in mining, or are gamers here as well? And if you're a gamer, do you mine with that rig too or only with dedicated mining rigs?
I used to mine ETH when my Fury Nitro on the gaming PC was in idle, but with the difficulty increase I stopped doing it...
All in all, I'm curious if there's people here not using the blockchain driver only to be able to game as well
Out of curiosity... are you guys just focused in mining, or are gamers here as well? And if you're a gamer, do you mine with that rig too or only with dedicated mining rigs?
I used to mine ETH when my Fury Nitro on the gaming PC was in idle, but with the difficulty increase I stopped doing it...
All in all, I'm curious if there's people here not using the blockchain driver only to be able to game as well
2 Hellae
No need to set memory 1100 or 1050mhz via reg mod. It can be done later with overdriveNtool. It is more safe
No need to set memory 1100 or 1050mhz via reg mod. It can be done later with overdriveNtool. It is more safe
Thanks. On V64 the memory voltage can also be set at 905, sicne it is just a minimum mV and not actual voltage?
Hi all,
I've just posted a guide on reddit to help others. It will get more visibility and traction there, I hope.
There's some info I don't know like the V64 power consumption at .875 VDDC, so you're all invited to jump in and add your input.
My .reg file is there to download. Added another one for 1050 MHz if your card doesn't support the 1100.
https://www.reddit.com/r/MoneroMining/comments/74hjqn/monero_and_vega_the_definitive_guide/
I've just posted a guide on reddit to help others. It will get more visibility and traction there, I hope.
There's some info I don't know like the V64 power consumption at .875 VDDC, so you're all invited to jump in and add your input.
My .reg file is there to download. Added another one for 1050 MHz if your card doesn't support the 1100.
https://www.reddit.com/r/MoneroMining/comments/74hjqn/monero_and_vega_the_definitive_guide/
How much mhs vega 56 with ETH and equihash algo ? Thanks .
ETH is dead for me, and it should be to any Vega mining.
I think the max you can get with V64 bios, regedit changes and blockchain drivers is 44MH/s. Even if Vega was able to do 70MH/s ETH, Monero is still more profitable.
Thanks , is possible update firmware vega 64 on vega 56 ? .
Yes. just download ATIFlash and V64 Air or Liquid .rom from techpowerup.com
Incredible... all vega 56 update at vega 64 ? .
Yes. 3 V56
Did a few tests from 1700 to 1800 with multiples of 8.
2016 / 1736 are the values that gave me more hash.
https://i.imgur.com/KA5DUaq.png
I'll leave it runing now to check its stability and more accurate over the time values.
2016 / 1736 are the values that gave me more hash.
https://i.imgur.com/KA5DUaq.png
I'll leave it runing now to check its stability and more accurate over the time values.
That's not bad at all. are these 56s with the 64 bios and power mods?
with 2 x 56s stock I get
Code:
[2017-10-05 10:21:17] : New block detected.
HASHRATE REPORT
| ID | 10s | 60s | 15m | ID | 10s | 60s | 15m |
| 0 | 925.5 | 968.4 | 977.6 | 1 | 755.4 | 804.8 | 815.1 |
| 2 | 1000.5 | 1007.9 | 1009.1 | 3 | 823.5 | 843.3 | 843.9 |
-----------------------------------------------------
Totals: 3504.9 3624.5 3645.7 H/s
Highest: 4577.3 H/s
HASHRATE REPORT
| ID | 10s | 60s | 15m | ID | 10s | 60s | 15m |
| 0 | 925.5 | 968.4 | 977.6 | 1 | 755.4 | 804.8 | 815.1 |
| 2 | 1000.5 | 1007.9 | 1009.1 | 3 | 823.5 | 843.3 | 843.9 |
-----------------------------------------------------
Totals: 3504.9 3624.5 3645.7 H/s
Highest: 4577.3 H/s
Keep us posted on the stability.
Yup. V56 flashed to V64 (Air). So far the hash rate has been floating between 5650 and 5750, which I assume is related among many other things, with the variable difficulty.
the 15min average is at 5701
How much mhs vega 56 with ETH and equihash algo ? Thanks .
ETH is dead for me, and it should be to any Vega mining.
I think the max you can get with V64 bios, regedit changes and blockchain drivers is 44MH/s. Even if Vega was able to do 70MH/s ETH, Monero is still more profitable.
Thanks , is possible update firmware vega 64 on vega 56 ? .
Yes. just download ATIFlash and V64 Air or Liquid .rom from techpowerup.com
How much mhs vega 56 with ETH and equihash algo ? Thanks .
ETH is dead for me, and it should be to any Vega mining.
I think the max you can get with V64 bios, regedit changes and blockchain drivers is 44MH/s. Even if Vega was able to do 70MH/s ETH, Monero is still more profitable.
But we need some boost to 50-60mhs for Vega to be good with ETH.
I think it is possible but we need some good coder to make 2-dag eth miner for vega.
I guess Wolf0 already has one and sold it to some big farmers.
Wasn't aware of that incoming fork "feature" but doesn't that sound like they are desperate trying to save the coin? Before Vega hash rates on Monero jumping sky high, it was reading and comparing Monero to Ethereum what made me stick to XMR.
Did a few tests from 1700 to 1800 with multiples of 8.
2016 / 1736 are the values that gave me more hash.
https://i.imgur.com/KA5DUaq.png
I'll leave it runing now to check its stability and more accurate over the time values.
2016 / 1736 are the values that gave me more hash.
https://i.imgur.com/KA5DUaq.png
I'll leave it runing now to check its stability and more accurate over the time values.
How much mhs vega 56 with ETH and equihash algo ? Thanks .
ETH is dead for me, and it should be to any Vega mining.
I think the max you can get with V64 bios, regedit changes and blockchain drivers is 44MH/s. Even if Vega was able to do 70MH/s ETH, Monero is still more profitable.
Yes, I'm talking about 0.875 reading in hwinfo (sensors only). You will get it if you set 900-905mV in patch.
I also had problems with hwinfo system hang but solved it with disabling I2C for gpu in settings as Mumak, hwinfo author, advised.
I'm with 905mV on all cards now.
https://imgur.com/a/3WXyz
0.875 VDDC
At the wall it dropped to 525W 
-35WI'm comfortable with this power count so I'll not try to stress the cards even more with 900.
Last I want to try is new intensity values. Atm I'm with 2016/1700. 1800 on the second one gave lower hash.
Did you control the resulted gpu voltage in hwinfo64 and wattage from the wall?
I think you should set "memory" voltage (it is not memory voltage in fact) to the same value as your gpu core voltage.
I think you should set "memory" voltage (it is not memory voltage in fact) to the same value as your gpu core voltage.
Nope. I didn't even knew Hwinfo64 has that feature. Last time I opened it it sent erroneus data to sensors (temperature at 500º) and the fans gone crazy. Had to reboot and didn't opened it again since. Maybe I need to update it.
Wattage on the wall, always. I'm at ~560W
https://i.imgur.com/u15eNWD.jpg
950mV is to much for monero 1408/1050.
My cards are 1408/1100(some cards need 1080mem) with 905mV in registry (and OverdriveNTool) and 875mV in Hwinfo64 ... seems stable ...
My cards are 1408/1100(some cards need 1080mem) with 905mV in registry (and OverdriveNTool) and 875mV in Hwinfo64 ... seems stable ...
Reducing from 910 to 905 will be my next tweak. The 875 in Hwinfo64 I really need to google that. Always used it to read sensors only. Thanks.
wait... or are you refering to the 0.875 VDDC reading on Hwinfo64? I'm confused now.
Now that I can easily build/rebuild the miner, decided to learn some basics of C++ today for my own profit:
Old Web Interface:
https://i.imgur.com/1F9pA6P.png
New Web Interface:
https://i.imgur.com/mh8IDsf.png
Now I can spend less time adding thread values.
I'll not share the miner because it's without devfee (and has all the devfee code removed aswell), but if you can build it and are interested on my code changes for this UI, those I can share.
---
I've finally decided to try the regedit thing.
The 3 vega 56 there are all at 1408@910mV (haven't tried 905 nor 900 yet. that's the next step) and 1100@1050mV (V64 OC with V56 voltage), with min fan speed at 3500 and 0% Power Limit.
System is stable, have been running 24h, and had to restart it to test the new miner changes I did.
The device 0 is always doing more hash that the others, many times at 1920H/s. I suspect it's because that's the card on the riser connected to the x16, since everything else is equal. Other than that, it can only be wattman's sketchy code...
Old Web Interface:
https://i.imgur.com/1F9pA6P.png
New Web Interface:
https://i.imgur.com/mh8IDsf.png
Now I can spend less time adding thread values.
I'll not share the miner because it's without devfee (and has all the devfee code removed aswell), but if you can build it and are interested on my code changes for this UI, those I can share.
---
I've finally decided to try the regedit thing.
The 3 vega 56 there are all at 1408@910mV (haven't tried 905 nor 900 yet. that's the next step) and 1100@1050mV (V64 OC with V56 voltage), with min fan speed at 3500 and 0% Power Limit.
System is stable, have been running 24h, and had to restart it to test the new miner changes I did.
The device 0 is always doing more hash that the others, many times at 1920H/s. I suspect it's because that's the card on the riser connected to the x16, since everything else is equal. Other than that, it can only be wattman's sketchy code...
On the .REG file...
50% Power Level:
00,48,00,00,00,80,A9,03,00,F0,49,02,00,32,00,08,00,00,00,00,00,00,00,00,00\
0% Power Level:
00,48,00,00,00,80,A9,03,00,F0,49,02,00,00,00,08,00,00,00,00,00,00,00,00,00\
But how to set a negative value?!
My take on a -50% would be:
00,48,00,00,00,80,A9,03,00,F0,49,02,08,32,00,08,00,00,00,00,00,00,00,00,00\
Does this make any sense?
50% Power Level:
00,48,00,00,00,80,A9,03,00,F0,49,02,00,32,00,08,00,00,00,00,00,00,00,00,00\
0% Power Level:
00,48,00,00,00,80,A9,03,00,F0,49,02,00,00,00,08,00,00,00,00,00,00,00,00,00\
But how to set a negative value?!
My take on a -50% would be:
00,48,00,00,00,80,A9,03,00,F0,49,02,08,32,00,08,00,00,00,00,00,00,00,00,00\
Does this make any sense?