I use VGA splitters on Vega and no issues. But I also don't have any problem mixing power supplies on the same rig, so I am not sure what you are doing. So long as you are not drawing above 240w through each card, and you shouldn't if you use OverDriveNTool and Reg mods, I don't think it will present a problem.
The 6 pin VGA to dual 6+2 VGA cables are nice (the add-on adapters work fine as well), especially if you are using something like a HP server PSU (1500w common slot) and a breakout board.
thnx for the response, i needed to hear this as connecting 6 Vega with risers equals to 18 connections
with 8 to 6+2x2 adapters i can use one EVGA1600 to power all from its total 9 VGA out ports
i believe the only consideration is having the same or bigger calliber cabling on the adapter to not cause resistance thus heat
yea im using the 1100 reg file with Ntool runing at 218W/GPU incl mobo and screen
(tests with the 1200 reg file shot my Wattage to max on all cards over 320W/GPU, need more time for trial+error)
the PSU debate rages on lol, im just cautious to have the same PSU on the riser as card
i suppose exaclty the same PSUs used in synch can be mixed as they produce the same frequency voltage
thnx again
Yes, pay attention to the wire gauge, I agree. One setup that I have used on a number of rigs: HP PSU powering 5 or 6 video cards and risers; ATX power supply powering the motherboard and maybe 1-3 other video cards and their risers. Works very well for me even though completely different power supplies. Cheaper alternative. YMMV. |
|
|
|
Hi All, I have a couple of questions if anyone can help
Can anyone tell me what the P Values in Overdriventool change. I believe P7 is the memory frequecy of the card and P3 the cards Ram? but what are the others.
also, I always stop the miner before making any changes in Overdriventool. Is it ok to make changes while the miner is running?
Thanks
Yes, it is OKAY to make changes in OverDriveNTool while the miner is running. Let's say you have 4 Vega cards and one is the proverbial mutt. If you are using the Jericho Jones script, you might opt to have the script load a pretty conservative, lower hashing rate OverDriveNTool profile just so that Cast or XMR start mining smoothly. Then you can go into OverDriveNTool and apply a different profile for the three cards that work great, one by one, while the miner is running. You should see changed hash rates for those cards in under a minute. Or you could create two different profiles, and load the slower one for the mutt card, and the better one for the three good cards using the VideoTools option explained within the script and at the vegaminingblog. Changing settings in OverDriveNTool while the miner is running can help you determine which card(s) is or are the dog(s) (your miner will crash after you hit "apply" for that card, even if it did not crash for the other cards). You can fine tune your setup in this way. But be aware that OverDriveNTool numbers the cards differently than the miner program. So change one card's settings and see which card # in the miner window is affected. |
|
|
|
[Wattman discussion...] What would this achieve though, other than sucking even more power?
Currently I have basically tried variations of these two main options (short of a bios mod):
1. 1407@905mV core and 925@900mV hbm (1900h/s/card - 1385W @ the wall for the 6-card rig)
2. core -20% tdp, 925@900mV hbm (1800h/s/card - 1125W @ the wall)
For case 1, HBM temp is between 75 and 82C
For case 2, HBM temp is between 60 and 70C
In either case I cannot increase hbm speed or the rig will crash.
Is a bios mod the only way to get higher speed? I read from other people clocking their Vega 56 HBM at close to 1100!... How on earth do they do that?
Well, as mentioned, yes -- a bios mod. Also I think a psu that provides slightly higher voltage, for example a HP 1,500w common slot psu with a Parallelminer breakout board, helps with Vega speeds. |
|
|
|
<snip>
--------------------------------
i do have a question for those experienced in using power splitter adapter cables from a VGA 8 pin to 2x8 (so i can remove the EVGA1000 PSU)
various people on the net claim that they cause electrical noise and should not be used
are you using them on a VEGA? if so whats your take on the matter?
thnx
ps i bought 10 on/off switches for $4 to replace the bare wires im currently using in favour of a more modern look hahahaha
I use VGA splitters on Vega and no issues. But I also don't have any problem mixing power supplies on the same rig, so I am not sure what you are doing. So long as you are not drawing above 240w through each card, and you shouldn't if you use OverDriveNTool and Reg mods, I don't think it will present a problem. The 6 pin VGA to dual 6+2 VGA cables are nice (the add-on adapters work fine as well), especially if you are using something like a HP server PSU (1500w common slot) and a breakout board. |
|
|
|
I'm using SMOS for quite a bit time, and pretty happy about it.
Last 5 months I have not touched anything and today I have checked status and I see that one GPU is not listed, I can't see for how long it is offline at the pool or at SMOS.
There is probably something dead or needs to be checked, but since rig is far away from me I will do it later.
My question is: Will there be an option to send report by mail about offline rigs or changes in configurations?
Thanks!
would be nice to have a monitor - it's why i haven't switched over from windows yet. no monitoring. i do like that it was literally plug and play for the drivers, booted up and found all 6 GPU's right away. With windows it does take more time for the initial, have to download nvidia driver updates, then 90% of the time I have to plug in 1 card at a time, reboot till it reads all 6. BUT once you do that, there's tons of miner monitors and haven't had 1 single issue with win10 in the past year, so still on the fence migrating farm to smos. I completely agree with that assessment. However, from time to time, Windows blows up for no apparent reason, which is annoying and time wasting. SMOS is like the EverReady Bunny... I'm split between SMOS and Win10. |
|
|
|
Finally got around to configuring a script to restart cards, apply profiles and launch miner.
Curious, if anyone is copying/making a shortcut of this script into startup folder for reset purposes or are y'all just remoting in on restarts and running the script.
I guess I don't see a reason why I couldn't throw the script into the startup folder?
Windows TaskScheduler |
|
|
|
Hello , i think i tired everything... got a biostar tb250 + mobo (8gpu) and installed first 4 vegas. already made the crossfire reg mode, the devcon, pagefile,VM etc etc. when i'm on single vega i can run at 2060h/s when on 2+ pc crashes instantly. i have seen hellae guide on reddit and set clocks at -30% 930 auto -20% . now its stable at 1890 each. got free electricity so i don't care about it. using wattman. anyone has any idea ..?
I gave up on that motherboard yesterday. Moved to an Asus Z270-A. |
|
|
|
I'm having the "one card drops to 0 h/s" issue too. I get that error then the whole rig stops hashing with the GPUs even though XMR still shows activity. Eventually the system crashes when i try to quit the miner and I have to reboot. It happens after 45-60 mins of mining almost every time. I'm going to reinstall windows again but this issue is making me rethink my XMR mining. I might end up ditching this project and going with asics if I cant get it working. Has anyone solved it?
Sigh. Vegamining blog for a script that you can modify to monitor hash rate and restart. If the same card keeps dropping to "0" dial back the P7 and P3 settings using OverDriveNTool and apply that profile to just the weak card. |
|
|
|
That's an okay PSU, but why wouldn't you go with: DPS-2500BB with a breakout board from: http://www.price-technology.com/Better all the way around. * You do need either 240v outlet OR a step-up transformer. |
|
|
|
You definitely need to do the powerplay if you are concerned with powerdraw. Otherwise it mostly even does not matter what voltages you set manually.
You cant get much more than 1950 out of them. I havent seen a reliable way to up the SOC clock with out significantly increasing powerdraw.
You can get 2080h with 1400mhz core / 1199mhz SoC / 1199mhz HBM with a 30%/50w increase in powerdraw. With some mods the cards would crash instantly without core @ 950mv. On some it will work with <900mv settings but it still actually draws 950mv.
I found that the extra 130h @ 50w and much higher temps are not worth it for me.
I know RednoWs reg worked on some cards with high SoC and low voltage but on most cards it will not work and I cant figure out what makes it work on some and not others....
Maybe silicon lottery...
where can i find info on the power play mod please Start with YouTube: find Oldcomer's two part video, Cryptonight is covered in part 2. Reddit: find Hellae's "definitive Vega mining guide" which is a little out date, last I looked. Search for Vegamining blog authored by @Circusdad and read through that. It is the most up to date guide. |
|
|
|
Hello,
i got the following issue:
initially i got average around 1900h/s and after some time, it can be minutes or hours, i drops to 1500-1600h/s
Anyone having such issue and eventually a solution ?
I'm experiencing the same  . No ideea how to fix it Visit vegamining blog authored by @Circusdad. This issue is discussed and a script for XMR-STAK to monitor hash rate and restart is provided; a few posts back in this thread, user StellarX88 explained how to modify that script to work with Cast. Meaning, once you customize the script as laid out, and based on the number of cards that you have, the script will restart Cast if your hash rates drops below the hash limit that you define. Not foolproof, but it has been working fairly well. If your hash rate is dropping every few minutes, then your problem is with bad values for P7 and P3 (OverDriveNTool), or too aggressive settings in XMR-STAK config file. |
|
|
|
So I finally got my Onda D1800 working with six Vega56's plugged in and hashing happily.
Set clocks at 1407/935 (900mV on the mem).
Hashing at approx 1920H/s per card.
Any suggestions on how to get this higher? Have not flashed nor played with power table...
Find brnstead's PowerPlayTable, it was the most stable one for me. The PPSoftPowerPlay table just has to get past boot. After boot, you can refer to @Circusdad's vegamining blog to figure out how to script it so that your custom OverDriveNTool profiles are applied card by card. You also want to look into bumping up SOCC. Page 82 on the overclock.net Preliminary thoughts about Vega is helpful. You can go to 1950/1960 H/s by dropping P7 to 1376-1384 or so, 890mv and increasing P3 to 1100 or 1080, 870mv. I have Vega 56's, you can go higher if you have Vega 64. |
|
|
|
Hi Guys,
What is your bios configuration for Asus Z270-A Prime ?
I have an issue only 2 of my cards are showing. Need help for that.
Thx in advance
Dexx
4G encoding needs to be "enabled" on that motherboard. |
|
|
|
Hi i m getting 6200hs on my mixed rig, however i m getting alot 0.0hs lines in the miner...
Who can help me solve this?
does someones has the --help working?
thnx
If you are mixing RX 480 or RX 580 with RX Vega, the 0.0hs lines are weird, but check your total hash rate. The total rate may be fine on your end and pool side. |
|
|
|
In my case, I've stopped even LOOKING at Gigabyte cards except the Aorus - way too many "dead fan" issues on cards at or a bit less than a year old, and had 2 of the ITX cards die on me last month.
They really got cheap on their fans - you have to BREAK the things open to even fix them as they don't have "oil covers" in the back like MOST sleeve bearing designs do and they are held together by a "sonic welded" piece.
I suspect I just found new long-term homes for the left-overs of the big batch of 92mm NMB Boxer fans I got at a hamfest years ago - which happen to soak the same .35 amps of the cheap Gigabyte fans, but I only need *2* of the NMBs for good cooling vs. 2 or 3 on the Windforce cards I have....
BTW - I blame Voskcoin's video for NewEgg being out of the EVGA SC 1070 ti right now.
8-P
Gigabyte Aorus 1080 Ti Extreme edition - they've worked well me. They fit in 4U builds, hash rate is good, fans works well. And you get a LED light show at night... Only Gigabyte card I've ever used, but I like them. |
|
|
|
Where Can I find Devcon.exe? Where's the file location I mean. Please help.
1. Get your hands on the Windows Device Console (Devcon.exe). This will let you disable/enable devices from console.
Two things... 1) You can actually do what you are looking for with a windows script... no Devcon.exe is required: http://vega.miningguides.com/p/auto-run-miner-without-hashmonitor.html2) You can get Devcon.exe direct from Microsoft without an extensive installation by following the method here: (first time I posted this link bitcointalk said it was a suspicious link and took it out... not sure why but I have edited the post to break the link into two pieces... (Just remove the spaces): https://networchestration.wordpress.com/2016/07/11/ how-to-obtain-device-console-utility-devcon-exe-without-downloading-and-installing-the-entire-windows-driver-kit-100-working-method/ Hi CircusDad, just PM'd you over on Reddit. StellarX88 has modified the Jericho Jones hash monitoring/restart upon defined trigger setting script so that it works with Cast. His posting is over on the CastXMR miner thread. |
|
|
|
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__I0jzLWlBZMTVCMWZDZ3YwRDZiRkh6cldKWnc1WjlzSome 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. One other section that people might find confusing, though StellarX88 explained it: Drop trigger section is dependent on the number of Vegas that you have installed. When hash rate drops, if it drops for 1 card from 1950 down to 1600 the difference = 350. So if it drops for 5 cards, then 5 x 350 = 1750 BUT you need to add three "000" to match /json output of Cast 0.70. So my $hdiff = 1750000 Similarly, if my normal total hash rate is aroud 9.6KH/s, and if I want to restart if that total drops to 8KH/s, I have to express that value by adding three "000" onto the end. $global:vegaHash = 8KH/s = 8000000 ######################################################################### # Set drop trigger and startup timeout ######################################################################### $hdiff = 1750000 # This is the drop in total hash rate where we # trigger a restart (Starting HASHRATE-$hdiff) # $timeout = 60 # (STARTUP ONLY)How long to wait for CAST_XMR to # return a hashrate before we fail out and # restart. There is no limiter on the number of restarts. # Press CTRL-C to EXIT # $CAST_XMRstable = 20 # How long to wait for the hashrate to stabilize. # $global:vegaHash = 8000000 # Minimum vega hash rate before we also trigger # a restart ######################################################################### ###################### END USER DEFINED VARIABLES ####################### #################### MAKE NO CHANGES BELOW THIS LINE #################### ##### BEGIN FUNCTIONS ##### |
|
|
|
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__I0jzLWlBZMTVCMWZDZ3YwRDZiRkh6cldKWnc1WjlzSome 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. thanks! i'll get on this (probably next week) StellarX88, Thank you!!! It's working! Sweet! Okay, when running multiple Vega's, your start up lines for Cast might look like this: $global:CAST_XMRexe = "cast_xmr-vega.exe" # The miner. Expects to be in same folder as this script $global:CAST_XMRcmdline = "-S mine.xmrpool.net:7777 -u [Your_Wallet_Address].[Your_Rig_Name] -p x -O 1 -G 0,1,2,3,4 -I 8 -R" #"Cast_XMRcmdline = values you had put into your .bat file, with some reordering I moved the --opencl to the end (the "-O 1" is my opencl value) -O is the same thing as earlier "--opencl" The "-G" command I also moved to the end. "-R" works, is equivalent to, --remoteaccess but for some reason using "--remoteaccess" did not work. But "-R" does ! Vid tools is where you put your OverDriveNTool profiles to apply: #### Vid Tool 1 $vidTool += 'OverdriveNTool.exe -r0 -r1 -r2 -r3 -r5 -p0Vega -p1Vega -p2Vega -p3Vega -p5Vega' #-r4 is an Nvidia card, that is why "4" is skipped over here # Expects to be in same folder as this script # Delete or REMARK if you don't want use it #### Vid Tool 2 $vidTool += 'regedit.exe /S 000.reg' # Expects to be in same folder as this script #from Kekso on Reddit, if you want to try this, move a copy of RegEdit into your Cast folder. These are my SoftPowerPlay mods. # Delete or REMARK if you don't want use it #### Vid Tool 3 $vidTool += 'regedit.exe /S 001.reg' # Expects to be in same folder as this script # Delete or REMARK if you don't want use it #### Vid Tool 4 $vidTool += 'regedit.exe /S 002.reg' # Expects to be in same folder as this script # Delete or REMARK if you don't want use it #### Vid Tool 5 $vidTool += 'regedit.exe /S 003.reg' # Expects to be in same folder as this script # Delete or REMARK if you don't want use it #### Vid Tool 6 $vidTool += 'regedit.exe /S 004.reg' # Expects to be in same folder as this script # Delete or REMARK if you don't want use it #### Vid Tool 7 $vidTool += 'regedit.exe /S 005.reg' # Expects to be in same folder as this script # Delete or REMARK if you don't want use it #### Vid Tool 8 $vidTool += 'regedit.exe /S 006.reg' # Expects to be in same folder as this script # Delete or REMARK if you don't want use it ##### End VidTools $global:Url = "http://$CAST_XMRIP`:$CAST_XMRPort" # <-- DO NOT CHANGE THIS !! Nice! So happy to have auto-restart if Hash rate drops. |
|
|
|
Getting SOCKET ERROR - Job Error: invalid target: 00000000 Any ideas? Haven't set any parameters (apart from pool address, wallet and password)... EDIT: trying on a bone stock Vega56 You usually also need to set (as a parameter) "-O" for --opencl and then argument ("0" or "1" or "2"), so -O 1 for example. Put that after cast_xmr-vega in your .bat file Also, if you have more than one card, you need to set "-G" and put in cards, so if I have 4 Vegas, "-G 0,1,2,3" |
|
|
|
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__I0jzLWlBZMTVCMWZDZ3YwRDZiRkh6cldKWnc1WjlzSome 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. Stellar, Thanks for this. Will report on results soon. |
|
|
|
|
Show Posts
