 Show Posts
|
|
Pages: [1] 2 3 »
|
|
3
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux)
|
on: December 13, 2019, 02:40:20 PM
|
|
Hi guys can someone please explain to me in detail how the achieve the best settings for etherium on Vega 64. I have been mining recently Monero, right before the fork and i cant have the same settings for Etherium. I have 2 rigs of 13 Vega 64 cards each. One is using one of the latest drivers 590MH and 2kw energy for the whole rig. Settings applied min stage 4 max stage 5 CPU clock on 900mv and memory 1090MHz on 890mv the other rig is hashing with power play tables with 18.5.2 driver with 490MH and 1.2kw energy for the whole rig. Can someone please share some information with me how to get the most out of my rigs, what drivers, settings, tools and miner configuration do i have to do. Thank you in advance
|
|
|
|
|
4
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux)
|
on: December 01, 2019, 02:45:18 AM
|
Have we to specify the -wd parameter to enable wacthdog in config file or are enable by default? I´m asking this because miner gets stucked on: 20:48:27:096 2374 ETH - Total Speed: 341.362 Mh/s, Total Shares: 208, Rejected: 0, Time: 00:35 20:48:27:098 2374 ETH: GPU0 47.980 Mh/s, GPU1 48.846 Mh/s, GPU2 0.000 Mh/s, GPU3 48.985 Mh/s, GPU4 48.786 Mh/s, GPU5 48.992 Mh/s, GPU6 48.784 Mh/s, GPU7 48.989 Mh/s 20:48:30:010 20ec em hbt: 0, fm hbt: 0, 20:48:30:010 20ec watchdog - thread 0 (gpu0), hb time 422 20:48:30:011 20ec watchdog - thread 1 (gpu0), hb time 47 20:48:30:011 20ec watchdog - thread 2 (gpu1), hb time 469 20:48:30:011 20ec watchdog - thread 3 (gpu1), hb time 109 20:48:30:012 20ec watchdog - thread 4 (gpu2), hb time 82547 20:48:30:015 20ec WATCHDOG: GPU 2 hangs in OpenCL call, exit 20:48:30:015 20ec watchdog - thread 5 (gpu2), hb time 82922 20:48:30:018 20ec WATCHDOG: GPU 2 hangs in OpenCL call, exit20:48:30:019 20ec watchdog - thread 6 (gpu3), hb time 485 20:48:30:020 20ec watchdog - thread 7 (gpu3), hb time 141 20:48:30:021 20ec watchdog - thread 8 (gpu4), hb time 125 20:48:30:021 20ec watchdog - thread 9 (gpu4), hb time 469 20:48:30:022 20ec watchdog - thread 10 (gpu5), hb time 141 20:48:30:023 20ec watchdog - thread 11 (gpu5), hb time 485 20:48:30:024 20ec watchdog - thread 12 (gpu6), hb time 125 20:48:30:024 20ec watchdog - thread 13 (gpu6), hb time 469 20:48:30:025 20ec watchdog - thread 14 (gpu7), hb time 485 20:48:30:025 20ec watchdog - thread 15 (gpu7), hb time 141 And doesn´t have restarted..  I had a simillar stalling with one of my GPUs it turned out that the stalling GPU wasn't able to keep up with the low voltage that i put. Can I ask you if those cards are VEGAS and what are your settings both in the miner and the AMD panel and drivers please. Thank you in advance. |
|
|
|
|
6
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux)
|
on: November 30, 2019, 01:50:33 PM
|
Who has the best settings for Vega64 OverdriveNTool???
You can find your own best settings as each and every card is different and it won't overclock the same. As there is no way to increase memory voltage. Increase memory speed by increments of 25 MHz until it is unstable. After this reduce core clock and core voltage in a similar fashion until it starts affecting the hashrate. Use HWInfo for any memory errors and display monitor to detect if there are any artefacts visible on the screen. My Vega 56 flash 64 air bios. Mem - 1095MHz; Core - 1246MHz; Cove(v) - 1025mV; fan - 66% What is your mining speed if i may ask with these settings? |
|
|
|
|
7
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux)
|
on: November 30, 2019, 01:48:03 PM
|
|
Hi there I am recently switching from Mining Moreno and I am new to Ehterium mining. On my main PC I have VEGA 64 with the latest drivers clocked to 1450 and memory to 1125 with 49MH speed and on my 13GPU VEGA 64 RIG I have 18.5.2 drivers Overdrive Ntool settings with 870mm memory to 1100 and clock to 1400 with 44MH speed. Can someone give me some info if there is a way to squeeze some extra hashes with some tweaks and settings, I have the default mining settings. Thank you
|
|
|
|
|
8
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Who ordered the AMD Radeon VII? Lets make a list of Miners / Hashrates / Coins
|
on: September 10, 2019, 04:37:38 AM
|
Did anyone managed to get over 3050 hashes for Monero under 200 Watts?
I get 3060-3070 at 170-171 watts (software, probably about 190 watts at the wall). This is a personal desktop tucked back in a corner, so I can't put a killawat on it to get the exact power draw. I was hoping we would have seen hashes over 4000 for under 200 watts, considering that it has been 8 months now since the release date, but still there is no change in the hashrate, this is sad |
|
|
|
|
13
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.9.2 - native algo switching
|
on: July 15, 2019, 07:24:38 PM
|
V1.9.2
- Added parameter '--disablerestartonrejectedshares' to disable auto restart of miner on too many rejected shares
- Added parameter '--maxrejectedshares' to set the number of allowed rejected shares on a pool connection ( min 1, max 100, def. 15)
- Optimisations in OpenCL code, so tiny hashrate increase could be seen on Vegas and Ellesmere cards.
- Minor bug fixes
+ Previous version added a feature that restarts miner when there are too many rejected shares. This version adds a new parameter to disable this feature, '--disablerestartonrejectedshares'
+ Also previous version had a hardcoded number of 5 for the max allowed rejected shares, this is now changed to 15, or you can set your own value with '--maxrejectedshares' value
+ Vegas and Ellesmere cards can see some small hashrate increase on major algorithms
Abut the rejected shares parameter, where do we write this code, in the config file or in the start.bat? Every parameter that starts with -- is a cmd parameter and goes to start.bat: SRBMiner-CN.exe --config Config\config-normalv4.txt --pools pools.txt --maxrejectedshares 20 Тhank you Doc, for the update and you response. On another note perhaps an idea about the following update. Won't it be cool if let's say to automatically restart the miner every 2-3 days so at least the miner can insure a 24/7 undisturbed operation. For example if the GPUs are mining more than a week straight they start to become buggy at some point. Like, you won't able to close the miner whiteout a hard rig restart or power off, or one of the gpus will die and the miner wont be able to start it back again. So i was thinking if the miner automatically restarts every 2-3 days, of course optional input from the user, would simply amazing. Thaks ones again! |
|
|
|
|
14
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.9.2 - native algo switching
|
on: July 15, 2019, 05:02:03 PM
|
V1.9.2
- Added parameter '--disablerestartonrejectedshares' to disable auto restart of miner on too many rejected shares
- Added parameter '--maxrejectedshares' to set the number of allowed rejected shares on a pool connection ( min 1, max 100, def. 15)
- Optimisations in OpenCL code, so tiny hashrate increase could be seen on Vegas and Ellesmere cards.
- Minor bug fixes
+ Previous version added a feature that restarts miner when there are too many rejected shares. This version adds a new parameter to disable this feature, '--disablerestartonrejectedshares'
+ Also previous version had a hardcoded number of 5 for the max allowed rejected shares, this is now changed to 15, or you can set your own value with '--maxrejectedshares' value
+ Vegas and Ellesmere cards can see some small hashrate increase on major algorithms
Abut the rejected shares parameter, where do we write this code, in the config file or in the start.bat? |
|
|
|
|
15
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.9.1 - native algo switching
|
on: July 12, 2019, 02:56:45 PM
|
Hi Doc, I find out that my Vegas 64 are all stable at memory tweak profile 8. How to apply it so it is already at 8 when restarting the miner, instead of manually pressing the + sign. Thank you
Try adding "tweak_profile" : 8 in config.txt, for example : {
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"off_temperature" : 80,
"tweak_profile" : 8
} Thanks Doc, for your fast response, it did work like a charm. But I will have to ask one more question though. Maybe i was thinking to do a fine tuning and isolate the weaker cards and put them one profile 8 and the rest on 9 or 10. How to do that? And last thing after updating to the latest SRB miner 1.9.1 I found out that it restarts the miner after 5 bad shares. One of my Vega VII apparently inst from the silicone lottery. I have memory at 1075 and clock at 1700 to avoid too many bad shares. I still get one bad share from time to time but its not a big deal, because I still get about 99.5%, but my question is how to disable the new option of restarting the miner after 5 bad shares or maybe to increase it to 20, in order down time due to restarts. I think I have 3-9 bad shares per 24 hours from that GPU. Thank you so much! For per card configuration use gpu_conf array, here is an example : {
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"gpu_conf" :
[
{
"id" : 0,
"intensity" : 112,
"worksize" : 16,
"threads" : 2,
"tweak_profile" : 8
},
{
"id" : 1,
"intensity" : 112,
"worksize" : 16,
"threads" : 2,
"tweak_profile" : 10
}
]
} You get the idea. Also on the first page or in the readme.txt you have more info. Regarding the restart on 5 bad shares, well yes, i don't know myself why i didn't make that one optional  I will add a parameter that disables this in the next version in a few days. God Bless, you are amazing! |
|
|
|
|
16
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.9.1 - native algo switching
|
on: July 12, 2019, 11:54:49 AM
|
Hi Doc, I find out that my Vegas 64 are all stable at memory tweak profile 8. How to apply it so it is already at 8 when restarting the miner, instead of manually pressing the + sign. Thank you
Try adding "tweak_profile" : 8 in config.txt, for example : {
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"off_temperature" : 80,
"tweak_profile" : 8
} Thanks Doc, for your fast response, it did work like a charm. But I will have to ask one more question though. Maybe i was thinking to do a fine tuning and isolate the weaker cards and put them one profile 8 and the rest on 9 or 10. How to do that? And last thing after updating to the latest SRB miner 1.9.1 I found out that it restarts the miner after 5 bad shares. One of my Vega VII apparently inst from the silicone lottery. I have memory at 1075 and clock at 1700 to avoid too many bad shares. I still get one bad share from time to time but its not a big deal, because I still get about 99.5%, but my question is how to disable the new option of restarting the miner after 5 bad shares or maybe to increase it to 20, in order down time due to restarts. I think I have 3-9 bad shares per 24 hours from that GPU. Thank you so much! |
|
|
|
|
20
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Who ordered the AMD Radeon VII? Lets make a list of Miners / Hashrates / Coins
|
on: June 10, 2019, 11:13:00 PM
|
POWER SUPPLIES (PSU) RUN BEST AT 50-70% LOAD--
Running a power supply at max load will wear it out prematurely. And, a cheap PSU at max load can fail with a fire hazard because they may be improperly rated. A 2000W cheap PSU on a 110V (USA) circuit would likely overload the 110V circuit and could possibly cause a house fire, not just an explodong PSU.
A cheap PSU will explode when run at max load. --scryptr
Thats what I wrote often before. NEVER buy cheap. You only have one life. Saving a few bucks with cheapest hardware is just stupid. I second this. Most US household plugs are rated for 15 amps. That's 110V * 15A = 1650W. My extension cords get scary warm at already 1250W even without tripping the fuses... So please take care, measure your consumption if you don't know it, and stay safe. A continuous load (e.g. a 24/7 mining rig) should generally be held to 80% of a circuits nominal rating. That 15a rating is for transient / short-term loads. For instance, I have a ‘20a’ PDU which is already derated to 16a to enforce this ‘rule’. Also, not all extension cords are equal. You should look for high amp/power cords - ‘heavy duty’, prob 12g or 10g wiring, and no longer than necessary (typically used for large outdoor/construction equipment like saws.) Also, the longer the extension cord, the more the voltage drop and higher amps needed for same wattage (which doesn't charge if you're mining with same setup). Hi there, can someone tell me how to configure SRB miner or XMR stack for Vega VII. Mine arrived today. For SRB miner on do you want to use double threads I put yes but I dont see double threds i am mining with 1400 hashes, please help me |
|
|
|
|
