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

How and where can we use this command ?

cast_xmr --help

Once miner is running, how can I see stats such as active pool, averages, ...

Also I have a correct global hashrate but most of the lines are empty... Is this normal ??

[14:05:45] GPU3 | 63°C | Fan 2085 RPM | 0.0 H/s
[14:05:45] GPU4 | 64°C | Fan 2188 RPM | 0.0 H/s
[14:05:45] GPU5 | 62°C | Fan 1886 RPM | 0.0 H/s
[14:05:45] GPU0 | 63°C | Fan 1922 RPM | 835.8 H/s
[14:05:45] GPU1 | 63°C | Fan 1979 RPM | 0.0 H/s
[14:05:45] GPU2 | 64°C | Fan 2013 RPM | 0.0 H/s
[14:05:45] GPU3 | 63°C | Fan 2083 RPM | 0.0 H/s
[14:05:45] GPU4 | 63°C | Fan 2187 RPM | 0.0 H/s
[14:05:45] GPU5 | 62°C | Fan 1886 RPM | 0.0 H/s
[14:05:46] GPU0 | 63°C | Fan 1923 RPM | 0.0 H/s
[14:05:46] GPU1 | 64°C | Fan 1976 RPM | 0.0 H/s
[14:05:46] GPU2 | 64°C | Fan 2014 RPM | 0.0 H/s
[14:05:46] GPU3 | 63°C | Fan 2080 RPM | 0.0 H/s
[14:05:46] GPU4 | 64°C | Fan 2188 RPM | 0.0 H/s
[14:05:46] GPU5 | 62°C | Fan 1885 RPM | 843.5 H/s
[14:05:46] GPU0 | 62°C | Fan 1923 RPM | 0.0 H/s
[14:05:46] GPU1 | 63°C | Fan 1976 RPM | 0.0 H/s
[14:05:46] GPU2 | 63°C | Fan 2015 RPM | 0.0 H/s
[14:05:46] GPU3 | 63°C | Fan 2081 RPM | 0.0 H/s
[14:05:46] GPU4 | 63°C | Fan 2190 RPM | 862.8 H/s
[14:05:46] GPU5 | 61°C | Fan 1886 RPM | 0.0 H/s
[14:05:46] GPU0 | 62°C | Fan 1923 RPM | 0.0 H/s
[14:05:46] GPU1 | 63°C | Fan 1975 RPM | 0.0 H/s
[14:05:46] GPU2 | 63°C | Fan 2016 RPM | 0.0 H/s
[14:05:46] GPU3 | 63°C | Fan 2081 RPM | 831.6 H/s
[14:05:46] GPU4 | 63°C | Fan 2190 RPM | 0.0 H/s
[14:05:46] GPU5 | 61°C | Fan 1885 RPM | 0.0 H/s
[14:05:48] GPU0 | 62°C | Fan 1921 RPM | 0.0 H/s
[14:05:48] GPU1 | 64°C | Fan 1958 RPM | 763.0 H/s
[14:05:48] GPU2 | 64°C | Fan 2032 RPM | 0.0 H/s
[14:05:48] GPU3 | 63°C | Fan 2081 RPM | 0.0 H/s
[14:05:48] GPU4 | 64°C | Fan 2193 RPM | 0.0 H/s
[14:05:48] GPU5 | 61°C | Fan 1884 RPM | 0.0 H/s
[14:05:50] GPU0 | 62°C | Fan 1919 RPM | 0.0 H/s
[14:05:50] GPU1 | 63°C | Fan 1965 RPM | 0.0 H/s
[14:05:50] GPU2 | 63°C | Fan 2030 RPM | 834.8 H/s
[14:05:50] GPU3 | 63°C | Fan 2086 RPM | 0.0 H/s
[14:05:50] GPU4 | 63°C | Fan 2179 RPM | 0.0 H/s
[14:05:50] GPU5 | 62°C | Fan 1880 RPM | 0.0 H/s
[14:05:50] GPU0 | 62°C | Fan 1920 RPM | 836.4 H/s
[14:05:50] GPU1 | 63°C | Fan 1967 RPM | 0.0 H/s
[14:05:50] GPU2 | 64°C | Fan 2029 RPM | 0.0 H/s
[14:05:50] GPU3 | 63°C | Fan 2086 RPM | 0.0 H/s
[14:05:50] GPU4 | 63°C | Fan 2179 RPM | 0.0 H/s
[14:05:50] GPU5 | 62°C | Fan 1880 RPM | 0.0 H/s
[14:05:50] GPU0 | 62°C | Fan 1921 RPM | 0.0 H/s
[14:05:50] GPU1 | 63°C | Fan 1970 RPM | 0.0 H/s
[14:05:50] GPU2 | 63°C | Fan 2027 RPM | 0.0 H/s
[14:05:50] GPU3 | 63°C | Fan 2086 RPM | 0.0 H/s
[14:05:50] GPU4 | 63°C | Fan 2179 RPM | 0.0 H/s
[14:05:50] GPU5 | 61°C | Fan 1880 RPM | 834.5 H/s
[14:05:50] GPU0 | 62°C | Fan 1924 RPM | 0.0 H/s
[14:05:50] GPU1 | 63°C | Fan 1969 RPM | 0.0 H/s
[14:05:50] GPU2 | 63°C | Fan 2026 RPM | 0.0 H/s
[14:05:50] GPU3 | 63°C | Fan 2086 RPM | 0.0 H/s
[14:05:50] GPU4 | 63°C | Fan 2181 RPM | 847.7 H/s
[14:05:50] GPU5 | 61°C | Fan 1879 RPM | 0.0 H/s
[14:05:50] GPU0 | 63°C | Fan 1922 RPM | 0.0 H/s
[14:05:50] GPU1 | 62°C | Fan 1964 RPM | 0.0 H/s
[14:05:50] GPU2 | 63°C | Fan 2026 RPM | 0.0 H/s
[14:05:50] GPU3 | 64°C | Fan 2087 RPM | 728.5 H/s
[14:05:51] GPU4 | 64°C | Fan 2180 RPM | 0.0 H/s
[14:05:51] GPU5 | 61°C | Fan 1879 RPM | 0.0 H/s

Little confused. Does is it lock up on the 64 bios or stock 56? Or both?

Try mining with just the Stock 56 bios. If you've already tried that, flip the bios switch and try it with the other stock bios that is on the card.
I've had a few cards that just don't liked to be flashed to 64 AIOs

I got it working all my cards now the struggle with computation  and outdated fails ?  how to get lower it ? i get around 20% away from those

overdriventool can be called via command line to set clocks, volts, fans, etc, but can't query information.

Little confused. Does is it lock up on the 64 bios or stock 56? Or both?

Try mining with just the Stock 56 bios. If you've already tried that, flip the bios switch and try it with the other stock bios that is on the card.
I've had a few cards that just don't liked to be flashed to 64 AIOs

Hi All,
I am running a 6 x Gigabyte Vega 56 rig on following setup:
   - motherboard = Asrock H97 Anniversary
   - CPU = Intel G3258
   - Ram = 8gb
   - Windows10 Pro, Blockchain 23 aug drivers
   - stock bios, oc and uv with OverdriveNTool

Here is a picture of my settings:
http://i66.tinypic.com/semucz.png

I use Cast to mine ETN and I cannot manage to run all 6 cards.
I works like a charm with 5 cards, at avg. of 1950 h/s, and when I enable the 6th everything goes crazy - artifacts and freeze/restart.

I am running out of ideas, any thoughts how to make the 6th card work?
I was thinking of incompatibility issues between vega and my mobo, could that be the case?

Thanks in advance
Pericle.
  

Hello once again i trying to get my new rig workin with 3x vega 56 flashed to 64,   two of them without problems mining together , but last card even tho it was flashed right and reflashed black to retail and back to 64bios  everytime i start mining with it even if i dont use other 2x cards  teh screen start tearin and pc restarts eventually , the card works normaly on everything else than miming .. tryed it solo on another pc had the same problém just with mining could it be bricked ? it loads normally and all...

P.S. Is there any analog of nvidia-smi for AMD?

I posted this on another thread and also helping some redditor, but you can try this:

I have modified the script slightly to work with 1 of my Vega card. You can modified it accordingly to fit your rig.

Download link below:
https://drive.google.com/open?id=0B2XFJ__I0jzLWlBZMTVCMWZDZ3YwRDZiRkh6cldKWnc1Wjlz

Some changes I made:

If you are executing the run_HashMonitor.cmd, make sure you change the file name in it accordingly to reflect CastXMR_HashMonitor_v2.6.ps1 (Or any name that you saved as).
Notable change I have made in this ps script includes:
Line 168 - 172 : I am using the script to call Cast-XMR directly, and Line 169 is the usual config including my wallet address, mining pool etc (the usual you put in a .bat) & also --remoteaccess in this case. Line 170 - 172 is to assign the localhost & port accordingly (7777)
Line 187: The main address for local/remote monitoring
Line 191 - 201: I didn't use $hdiff variable, but make a new variable for min Vega Hashrate before restart $global:vegahash @ line 201 (multiply by 1,000 since the reported value in the web is in actual hash rate)
Line 392 - 397 : Initial Vega hashrate for comparison (Not really needed since we have a reset trigger down below, but it's the same as the next)
Line 476 - 479 : Vega hashrate used for monitoring in order for restart.
Line 483 - 484 : Nothing major, just changing monitoring from 1 minute to every 30 secs
7: Line 486 : Most important part, condition to restart (Here to check my Vega hashrate against my preset target -> ~1.75kH/s @ Line 201)
This should set you up in the right direction to start with;
Do take note that I am running only 1 Vega to check against, hence I can use the total_hash_rate for comparison; if you are running multiple Vegas rig, you might need to divide it by number of GPU instances before you make the comparison. Alternatively is to loop through the "devices" in the hashrate report JSON to check if any of them drop, but I find total_hash_rate to be easier. You can also use total_hash_rate_avg in the report, as current total_hash_rate might be too sensitive for occasional dip.
And remember to change the CMDLine in Line 169, or else you would be mining to my wallet instead.
Let me know if you have any further question. I will try my best to help set up.

has anyone tried butchering jj's hashmonitor powershell script to monitor castxmr now that it has an API?

i would but my programming leaves a lot to be desired....

I posted this on another thread and also helping some redditor, but you can try this:

I have modified the script slightly to work with 1 of my Vega card. You can modified it accordingly to fit your rig.

Download link below:
https://drive.google.com/open?id=0B2XFJ__I0jzLWlBZMTVCMWZDZ3YwRDZiRkh6cldKWnc1Wjlz

Some changes I made:

If you are executing the run_HashMonitor.cmd, make sure you change the file name in it accordingly to reflect CastXMR_HashMonitor_v2.6.ps1 (Or any name that you saved as).
Notable change I have made in this ps script includes:
Line 168 - 172 : I am using the script to call Cast-XMR directly, and Line 169 is the usual config including my wallet address, mining pool etc (the usual you put in a .bat) & also --remoteaccess in this case. Line 170 - 172 is to assign the localhost & port accordingly (7777)
Line 187: The main address for local/remote monitoring
Line 191 - 201: I didn't use $hdiff variable, but make a new variable for min Vega Hashrate before restart $global:vegahash @ line 201 (multiply by 1,000 since the reported value in the web is in actual hash rate)
Line 392 - 397 : Initial Vega hashrate for comparison (Not really needed since we have a reset trigger down below, but it's the same as the next)
Line 476 - 479 : Vega hashrate used for monitoring in order for restart.
Line 483 - 484 : Nothing major, just changing monitoring from 1 minute to every 30 secs
7: Line 486 : Most important part, condition to restart (Here to check my Vega hashrate against my preset target -> ~1.75kH/s @ Line 201)
This should set you up in the right direction to start with;
Do take note that I am running only 1 Vega to check against, hence I can use the total_hash_rate for comparison; if you are running multiple Vegas rig, you might need to divide it by number of GPU instances before you make the comparison. Alternatively is to loop through the "devices" in the hashrate report JSON to check if any of them drop, but I find total_hash_rate to be easier. You can also use total_hash_rate_avg in the report, as current total_hash_rate might be too sensitive for occasional dip.
And remember to change the CMDLine in Line 169, or else you would be mining to my wallet instead.
Let me know if you have any further question. I will try my best to help set up.