Pages:
Author

Topic: [Cast XMR] high speed XMR/CryptoNight miner for RX Vega GPUs (2 KHash/s) - page 78. (Read 206388 times)

full member
Activity: 1123
Merit: 136
I wonder what I am doing wrong. Optimized version of stak-amd is getting around 5670 hashes (3 vega 64s @ around 215 watts per card).
CAST_XMR ist at around 5680 hashes [Hash Rate Avg: 5685.2 H/s]. That makes a difference of about 10 hashes on avg.

Any settings you can recommend so I can get more out of my vega 64s?


Did you read through this thread?

Also - standard response -

I encourage you to read through the following threads/guides:
Vega thread  https://bitcointalksearch.org/topic/any-word-on-amd-vega-hash-rates-2002025
Cast thread   https://bitcointalk.org/index.php?topic=2256917.0
vega.miningguides.com

Sure...because everybody has the time to read all these posts again!
Thanks for nothing anyway.


Thanks for nothing?  He gave you all the information you need you ungrateful piece of crap. Do some reading and figure it out.
newbie
Activity: 296
Merit: 0
Will xmr miner have support to amd 560 cards?   Cool
member
Activity: 75
Merit: 10

Did you read through this thread?

Also - standard response -

I encourage you to read through the following threads/guides:
Vega thread  https://bitcointalk.org/index.php?topic=2002025.0
Cast thread   https://bitcointalksearch.org/topic/cast-xmr-high-speed-xmrcryptonight-miner-for-rx-vega-gpus-2-khashs-2256917
vega.miningguides.com

Sure...because everybody has the time to read all these posts again!
Thanks for nothing anyway.

Yes, you absolutely should be reading the thread to find if other people have had your issue before making a separate, redundant comment. That goes for all forums on all topics. Shnikes even gave you other resources you could use, so I don't know why you would say 'thanks for nothing'.
newbie
Activity: 43
Merit: 0
I wonder what I am doing wrong. Optimized version of stak-amd is getting around 5670 hashes (3 vega 64s @ around 215 watts per card).
CAST_XMR ist at around 5680 hashes [Hash Rate Avg: 5685.2 H/s]. That makes a difference of about 10 hashes on avg.

Any settings you can recommend so I can get more out of my vega 64s?


Did you read through this thread?

Also - standard response -

I encourage you to read through the following threads/guides:
Vega thread  https://bitcointalksearch.org/topic/any-word-on-amd-vega-hash-rates-2002025
Cast thread   https://bitcointalk.org/index.php?topic=2256917.0
vega.miningguides.com

Sure...because everybody has the time to read all these posts again!
Thanks for nothing anyway.
member
Activity: 118
Merit: 10
As in the link i posted, don't open radeon settings. btw only install driver and nothing other from the install package.
Deactivate crossfire, and ulps via regedit as in the how to i posted.
full member
Activity: 798
Merit: 116
if i want set a list of server? so when a servers will be down the miner change to other server?
member
Activity: 101
Merit: 10
Miner / Engineer
Pool difficulties is not going to impact your card performance, shoot me a message on skype @ , I will try to trouble shoot this with you.

Will do later in the day.  Need to get some work done.  Smiley


So something happened between the multiple reboots and power offs this morning.  Seriously, only setting that changed was me enabling/disabling HBCC (all GPUs are Enabled at the moment).

Now I get has rates at 1900/2000+ with the correct memory!


...Except, 1 GPU.  When I "Disable/Enable" it in Device Manager, it no longer comes back and always errors with a Code 43.

I've tried moving it to another slot, swapping out cables, pcie risers, etc.  Doesn't matter, same GPU always fails to be "re-enabled."

But the other four are happy now.


Close...
newbie
Activity: 39
Merit: 0
Let's examine everything I am doing...  Let's take a look at the mining settings.

Code:
cast_xmr-vega -G 1 --fastjobswitch -S pool.supportxmr.com:7777 -p  -u 

Testing it on the true Vega64 first to dial it in, before I start tackling the Vega56s.

I've tried this pool, and a few other coins. 

I've tried with and without --fastjobswitch.


That port, 7777, is for "highend hardware" starting at 25,000 difficulty. 

I have tried lower difficulty, of 5,000.  I have tried setting the difficulty flat in 50,000 increments from 50,000 to 350,000 to no effect.



Pool difficulties is not going to impact your card performance, shoot me a message on skype @ mo.jin.ee, I will try to trouble shoot this with you.
member
Activity: 101
Merit: 10
Miner / Engineer
Let's examine everything I am doing...  Let's take a look at the mining settings.

Code:
cast_xmr-vega -G 1 --fastjobswitch -S pool.supportxmr.com:7777 -p  -u 

Testing it on the true Vega64 first to dial it in, before I start tackling the Vega56s.

I've tried this pool, and a few other coins. 

I've tried with and without --fastjobswitch.


That port, 7777, is for "highend hardware" starting at 25,000 difficulty. 

I have tried lower difficulty, of 5,000.  I have tried setting the difficulty flat in 50,000 increments from 50,000 to 350,000 to no effect.

member
Activity: 101
Merit: 10
Miner / Engineer
Crossfire disabled? Ensure that you do a vega driver reset after reboot once at least, it should push your vega to the expected range at 1050 to 1100 mem for vega64 BIOS.
I don't have any options to enable/disable crossfire.  That area is blank in my Radeon settings.

I didn't before, but now I am Disabling/Enabling each card after a reboot just in case.  It has not helped.

I also have tried the trick of enabling/disabling HBCC memory segment - and it doesn't have any effect either on hashrates.

Only tweaking the memory to 1050 or 1100 increases it to 1200 or 1300 depending on the card.  And lowering the GPU voltage to 900mV greatly reduces power consumption without affecting the the hashrate at all.  If I leave the GPU vcore at stock voltage, the hashrates are the same. 

Maybe Windows has updated your driver, first time i also had this problem  Smiley
If hbm2 is not to hot, i think deactivate/activate should help you. No automated scripts, made this automatically.
Also dont open any tools like gpuz etc.
I installed Windows without network connected, disabled Windows Update and that little known driver update portion as well - before I connected to the internet.

Remember, I am using the IGPU from the Intel CPU connected to my display, so I didn't need any drivers to use the machine upon setup.

Then I connected the internet and went online to download the blockchain drivers. 

But yeah, I guess somehow Windows snuck in a driver even with everything disabled.


I used to open MSI Afterburner just to keep tabs on the cards as I am most fimilar with that app over the last 10 years with its logging and INI settings.

However, I no longer load it - and just try to start mining.

Again, it doesn't make a difference.


I'm missing something there...  I'm sure it's something easy.
member
Activity: 118
Merit: 10
Maybe Windows has updated your driver, first time i also had this problem  Smiley
If hbm2 is not to hot, i think deactivate/activate should help you. No automated scripts, made this automatically.
Also dont open any tools like gpuz etc.
newbie
Activity: 39
Merit: 0
Well, the good news is after a full pave and reinstall of the drivers - I no longer get that warning message of not using the blockchain drivers.

I am also now able to use the same tweaked settings in the guides, and getting around 1300 H/s.  So yes, that's a little better.

But still a far cry from 1900 or 2000 H/s as advertised.

Guess I'll sleep on it.  Let me know if y'all have another ideas.

Crossfire disabled? Ensure that you do a vega driver reset after reboot once at least, it should push your vega to the expected range at 1050 to 1100 mem for vega64 BIOS.
member
Activity: 101
Merit: 10
Miner / Engineer
Well, the good news is after a full pave and reinstall of the drivers - I no longer get that warning message of not using the blockchain drivers.

I am also now able to use the same tweaked settings in the guides, and getting around 1300 H/s.  So yes, that's a little better.

But still a far cry from 1900 or 2000 H/s as advertised.

Guess I'll sleep on it.  Let me know if y'all have another ideas.
member
Activity: 101
Merit: 10
Miner / Engineer
Have you disable and enabled gpu in device manager before you start the miner. After reboot also if miner crash. Yet better?
If not go this how to http://vega.miningguides.com/

Don't thought 900mhz gpu is enough for 1900+h/s  Huh

I saw that disable/reenable in a few guides. But the newer ones don't have that step.  I'll try it now though; however, I do reboot often and power-cycle without any differences.

Back... Nope, made no difference at all.  Even powered off, booted, disable/enabled in device manager.

Oh and not 900mhz core - 900 millivolt.  Smiley  It greatly lowers power consumption.  Even at the full stock millivolts, it makes no difference in mining.

What bugs me is that it continues to say:

 "[22:35:41] [Suspicious link removed]pute Driver NOT detected."

The AMD installer explicitly says 17.30.1029.  However, once installed it shows 17.30.1091.  Yes, I ran DDU as well to clean.  Still only 1091 gets installed?


EDIT: If it matters, I do have IGPU enabled in bios and am using the onboard video.

http://support.amd.com/en-us/kb-articles/Pages/Radeon-Software-Crimson-ReLive-Edition-Beta-for-[Suspicious link removed]pute-Release-Notes.aspx

Ensure crossfire is off just in case. If you installed the correct driver, Cast-XMR won't throw the warning.

Yep, that's the exact driver I installed. The installer shows 17.30.1029 however the info page shows 17.30.1091.

At this point, I've just paved the entire PC and I am installing again.
newbie
Activity: 39
Merit: 0
Have you disable and enabled gpu in device manager before you start the miner. After reboot also if miner crash. Yet better?
If not go this how to http://vega.miningguides.com/

Don't thought 900mhz gpu is enough for 1900+h/s  Huh

I saw that disable/reenable in a few guides. But the newer ones don't have that step.  I'll try it now though; however, I do reboot often and power-cycle without any differences.

Back... Nope, made no difference at all.  Even powered off, booted, disable/enabled in device manager.

Oh and not 900mhz core - 900 millivolt.  Smiley  It greatly lowers power consumption.  Even at the full stock millivolts, it makes no difference in mining.

What bugs me is that it continues to say:

 "[22:35:41] [Suspicious link removed]pute Driver NOT detected."

The AMD installer explicitly says 17.30.1029.  However, once installed it shows 17.30.1091.  Yes, I ran DDU as well to clean.  Still only 1091 gets installed?


EDIT: If it matters, I do have IGPU enabled in bios and am using the onboard video.

http://support.amd.com/en-us/kb-articles/Pages/Radeon-Software-Crimson-ReLive-Edition-Beta-for-[Suspicious link removed]pute-Release-Notes.aspx

Ensure crossfire is off just in case. If you installed the correct driver, Cast-XMR won't throw the warning.
member
Activity: 101
Merit: 10
Miner / Engineer
Have you disable and enabled gpu in device manager before you start the miner. After reboot also if miner crash. Yet better?
If not go this how to http://vega.miningguides.com/

Don't thought 900mhz gpu is enough for 1900+h/s  Huh

I saw that disable/reenable in a few guides. But the newer ones don't have that step.  I'll try it now though; however, I do reboot often and power-cycle without any differences.

Back... Nope, made no difference at all.  Even powered off, booted, disable/enabled in device manager.

Oh and not 900mhz core - 900 millivolt.  Smiley  It greatly lowers power consumption.  Even at the full stock millivolts, it makes no difference in mining.

What bugs me is that it continues to say:

 "[22:35:41] Blockchain Compute Driver NOT detected."

The AMD installer explicitly says 17.30.1029.  However, once installed it shows 17.30.1091.  Yes, I ran DDU as well to clean.  Still only 1091 gets installed?


EDIT: If it matters, I do have IGPU enabled in bios and am using the onboard video.
member
Activity: 118
Merit: 10
Have you disable and enabled gpu in device manager before you start the miner. After reboot also if miner crash. Yet better?
If not go this how to http://vega.miningguides.com/

Don't thought 900mhz gpu is enough for 1900+h/s  Huh
member
Activity: 101
Merit: 10
Miner / Engineer
Hello all.

I must be missing something simple as I am not getting the expected 1800-2000 H/s per Vega out of my setup using Cast XMR.

AMD Blockchain drivers Aug 23rd, 17.30.1029 as the Installer says.  However, the digging into the Software stuff shows "17.30.1091.1011-170922a-318486C"

^- note that this is dated Aug 23rd, where others are saying "17.30.1029".  

Also Cast XMR says that the Blockchain driver isn't detected!?!?

I only get the following:

Vega 64: ~1250 H/s @ 1630c/900mV, 1095m/1050mV (stock settings is ~930 H/s)
Vega 56: ~1150 H/s @ 1630c/900mV, 1095m/1050mV (stock settings is ~870 H/s)

I started off following this guide to the letter: https://steemit.com/mining/@briggsy/briggsy-s-exhaustive-vega-56-64-monero-mining-guide-part-1-flashing-vega-56-with-vega-64-bios

I've since moved onto about a dozen different guides and recommendations.  Been browsing this post for hours and trying all sorts of combinations.  Nada.

One thing I have noticed is that Cast XMR does not report the proper temp or fan speed for the given CPU.  At least, I see a vast difference between Afterburner and what Cast XMR says (not the different GPU numbers, but actual values).

1x Vega 64
1x Vega 56 (flashed to Vega 64)
2x Vega 56 MSI Air Boost OC (can' flash to Vega 64)
1x Vega 56 Sapphire Nitro paperweight

Windows 10 Creative Update fresh install.  I have disabled everything with the "Windows 10 Registry tweaks for mining.bat" batch file (saved me the trouble).

I'm trying to stick only to OverdriveNTool for tweaking the settings.  

I've over-volted and under-volted.
I've +50% Power Target and -30% Power Target.
I've overclocked core and mem (oops, crash).
I've tried various combinations of all of the above, and left some alone, and can never see more than 1250 on the Vega64.

I've tried one GPU at a time, all GPUs, various combinations, etc.

I have not done any registry edits, as it seems the more recent guides don't have those settings.

I have tried 5 different pools and 2 different coins - all with the same effect.

Any help would greatly be appreciated.  
newbie
Activity: 22
Merit: 0
Sounds limited with the crashes.
newbie
Activity: 99
Merit: 0
cannot run more than 2 rx 470 8gig cards without crashing  i get error cl_mem_object_allocation_failure calling c1enqueueNDRangeKernel for kernel 0

works fine with 2  cards as soon as i add more i get the above.

windows 10 with  august 23 blockchain drivers  xmr cast 0.81   using  -G  0,1  etc to enable cards

  any ideas   or help would be welcome

Oh wow. A problem no one has ever seen before in this thread.


ANSWER: http://bfy.tw/G4tl
Pages:
Jump to: