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

keeps removing my link, so just google "how to obtain devcon.exe" and click the first one, i used it 4 days ago...

https://support.microsoft.com/en-us/help/311272/the-devcon-command-line-utility-functions-as-an-alternative-to-device

seems devcon.exe not exists anymore, where I can download it?

There are no optimized miners or drivers for Vega. New update soon and my opinion Vega work 3x more hashrate from rx 580

Hello. 8 Vega64 will work with ssd 120 GB?
I read that you need at least 15GB swap file for 1 VEGA. So you need a ssd 200-240 GB for 8Vega?
Google translate

Any ideas?

https://github.com/nicehash/NiceHashMinerLegacy/releases

1.8.2.0 Pre-release 2
@DillonN DillonN released this 4 hours ago

This is a pre-release intended to test the new version before it is released. Please restrict feedback and discussion to issue #487. This version may be buggy and most users probably want to download 1.8.1.5 below.

Changes in this pre-release

Drop Xmr-Stak-CPU in favour of new Xmr-Stak miner
Cryptonight mining for CPU, AMD, and NVIDIA
As many are aware, gives boosts for Vega cards
Due to config system, works a bit differently than most miners for tweaking (Wiki page)
BETA Threaded benchmarking
Benchmark devices simultaneously
ClaymoreCryptonight_old and Prospector have some issues currently, recommended to benchmark them manually for now
Fixes from 1.8.1.5, and some from upcoming 1.8.1.6
Overall 1.8.2.0 Changes

BETA Auto-tuning of ClaymoreDual intensity values (-dcri)
Allows benchmarking of many values for -dcri and saves all of them, using the most profitable during mining
Window to show/edit speeds for different dcri values as well as which will be benchmarked, opened by right clicking on the algorithm in the benchmark window
Enabled for each algorithm by right click menu in benchmark window (disabled by default)
NOTE: can take a very long time to benchmark many dcri values. Fortunately the miner will mine to your wallet if a valid one is entered, so you will be paid for the benchmarks
Currently ignores existing -dcri extra launch parameters and will overwrite existing speeds once enabled (suggested to keep a backup of 1.8.1.4 configs for pre-release in case you want to roll back)
Selected dcri values to benchmark are completely customizable
Ability to copy tuning settings to identical GPUs (works like existing copy all settings feature, but just for tuning settings/speeds)
Detailed guide coming soon
Drop Xmr-Stak-CPU in favour of new Xmr-Stak miner
Cryptonight mining for CPU, AMD, and NVIDIA
As many are aware, gives boosts for Vega cards
Due to config system, works a bit differently than most miners for tweaking (wiki page soon)
BETA Threaded benchmarking
Benchmark devices simultaneously
ClaymoreCryptonight_old and Prospector have some issues currently, recommended to benchmark them manually for now
Benchmark window now resizable

If you are receiving the error on Nicehash pool try to switch to other location. Several people get rid of the error after switching from EU to US servers. Please share you system|driver|miner info, I am trying to figure what's on. It is the first time it is VEGA-connected. Up to now usually it was about old drivers for obsolete cards, Catalyst 15.7 in my case.

Thats what it pretty much is. It (SOC) seems to vary a lot, you might need to set as high as 950mV to make it work.

Since today I got rejected shares: "Share above target" error, for ALL my shares. Yesterday was all OK. What has such a problem, what is solution?

https://www.asus.com/us/Motherboards/PRIME-Z270-A/overview/

Hi Guys,

Which mobo do you recommend ? I have an MSI Z170 Gaming Pro Carbon, but have too many issues to get it working properly.

Thx in advance

Dexx

My Vega 64 with softpp 1100@905mV working perfectly at 1960 H/s, but when I change the SOC clock to 1199 (6C,B0,01 -> C0,D4,01) after 1 minute mining resets itself even with the same settings of 1100@905mV and not increasing the Memory P3 to 1150...
Any idea what other setting should I change to make it work? or is it silicon lottery?

I'm using HWInfo64 for monitoring temperatures. However, the GPU# in it does not link directly neither to the Driver Key, nor the OPenCL index nor the card number in overdriventool.

Is there a monitoring utility that can show which card is which, precisely (i.e. PCI number, Driver Key, OpenCL index etc) and perhaps link that to the GPU# in hwinof64 ?

There's a hard way, off course: using single card at a time and checking which temperatures rise in hwinfo64, but I was hoping for a faster method.

test each card separately, find the unstable one, downclock or replace it... blockchain drivers support 8 cards

Well I can get a hold of a vega frontier for 699 USD. Seeing how the 56 and 64s are both selling for 600+ it was something to consider since the frontier card will likely retain it's value better aswell. I figured there wouldn't be much of a difference but does anyone have an actual screenshot or video link for proof. I tried reading a few pages of this thread but can't seem to find any concrete stats.

yes right, so what to do ?   make 7 cards or how ?

one of the cards is not stable

If I have 8 Vega 64 cards how to proceed all 8 cards?  Looks like only 7 works.

Well its not worth it for sure, if you would buy it just for mining. You get 2-3 vega 56s for a price of 1 FE?

And it wont even mine any better than vega 56.

which driver did you use? blockchain driver?

Anyone got any solid numbers for vega frontier? I'm considering buying one to try it out but would rather have some solid numbers before pulling the trigger.