i have a rig with 12 GPUS (rx580 4GB) and there is a problem with remote status report and management it takes long time (>40s) to report status even in localhost(127.0.0.1). and because of the delay EthMan can not get result in time.  Is anyone else having this problem? I have the same problem, but it only happens with the first rig listed in EthMan, rig_0. The other two miners listed below it in the same EthMan instance are reporting fine. The timeout for the first rig was also present on v10.2 with the Crimson Relive 17.11.4 drivers. It makes no difference if EthMan is running on that rig or another rig. It seems the connection is dropped intermittently on the first rig. I noticed in the Opitions.ini, the [rig_0] password will remove the quotation marks before and after the password, even if I put them back. I don't know if it's related to that since I also tried running it without a password and the same thing happens. All the rigs are running the same v3.7 of EthMan. |
|
|
|
In 1-3 days I will release new version with Adrenalin drivers support (fan/temperature/clocks management) and some other improvements.
Good news... I guess. What's the benefit of using latest adrenalin drivers? Are there any improvements? Well, for one the Adrenalin drivers are WHQL certified, so they should be more stable than the non-WHQL Crimson Relive 17.11.x drivers. |
|
|
|
Already using a Samsung 850 EVO Pro 256 GB SSD with 64GB virtual memory and disk usage is very low.  |
|
|
|
Neo,
Why Kabby Lake i5 7400T? Celeron is enough.
When using Asrock H110 BTC+ with 7 x 1070 + 6 x 570 my G3930 Celeron runs at 70-80% CPU when using some miners. With the combination of this AMD miner + that NVIDIA miner it uses high CPU. I profit switch with Awesome miner on Win 10 so any combination of miners is possible. I have ran linux and have seen similar results, just a little bit lower and returned to windows for ease of use. When administering the machine remotely or performing and maintenance work it is simply unusable and hashrates suffer. Remember that the CPU has to handle bus interrupts for data flow... more cards = more interrupts. When my setup is working hard the process interrupts account for 40-50% CPU. Those of you who are not mining on 13+ GPU's rigs shouldn't lecture us who do with your Celeron is OK bullshit. IMHO a I3 series and 8GB memory are a bare min for these types of setups. The OP has taken necessary steps to prevent a CPU bottleneck and personally don't care if he shoved a I7 in it... It is his prerogative and money. Most miners overlook the details like CPU and power requirements and wonder why their shit melts down. There is more to mining than ROI and cheap parts. Well said. I agree the minimum for a 13 card motherboard should be an i3 with 8GB of DDR4. On my ASRock H110 Pro BTC+ Windows 10 v1709 build 13 card RX 580 build with an i3 6100 and 8GB RAM, about ~35% CPU and 4GB RAM is in use when dual mining. Boot times, updates and driver installation also go MUCH faster with a better processor. It's amazing people have no problem droping $4K+ on overpriced GPU's for a build, but are too cheap to spend an extra $120 to buy an adequate CPU and RAM for a 13 GPU build that will make their life easier. LOL.  |
|
|
|
Mate, again, if you are mining Ubiq, use "-allcoins exp". It will mine Ubiq for devfee, same pool, same dag. I have tested myself in 3 different ubiq pools and the devfee works in all of them (dont use -allpools).
I can confirm this works. DevFee stays on the same UBQ pool. Thank you! |
|
|
|
|
Except the number of coins you receive is not just dependent on your hash rate. It also depends on the difficulty and the luck of pool, both of which can vary greatly over any given 24 hour period. It my experience, Bminer is ~3% faster compared to DSTM's miner. This is going by the reported hash rate and the average 24 hour hash rate graph reported on Flypool, which shows the effective hash rate is somewhat higher when using Bminer compared to using DSTM in the same 24 hour period.
|
|
|
|
|
What is the error code in Device Manager? You can mix cards with the blockchain drivers. I have a Biostar TB85 mixed 7 card rig on Windows 10 v1703 with 5 RX 570's, a RX 580 and a HD 7850. Check the PCI-E settings in the Bios and try changing the slots to GEN 1 or 2. Also make sure the onboard video is disabled.
|
|
|
|
|
Can't help you there, though I imagine almost any one would work. You shouln't mine on WiFi. It increses your latency and dropped packets. It's always better to run a Cat 6 patch cable or use a powerline network adapter.
|
|
|
|
|
Memory errors are the main cause of incorrect shares and instability. It means you are overclocking the card beyond it's capacity and basically making it work harder than it needs to, which causes extra power and heat. I always reduce the memory overclock by 50 MHz until there are no memory errors or at most just a couple. You will see the card invalid shares will drop and it will run cooler after doing that.
|
|
|
|
|
No, the only people mining BTC in 2009 and 2010 were computer programmers and hard core geeks. You could solo mine full blocks with a laptop back then and still CPU solo mine in 2011. Since currently GPU rigs and ASIC are the standard for POW mining, it's no longer possible for CPU's to compete effectively. So it's much harder and much more expensive to mine now compared to when BTC began.
|
|
|
|
|
I have the original Add2PSU, the copy and the ATX spliiter cable. I like the ATX splitter cables the best. Basically all you are doing is connecting the ground and +12v power on signal of the PSU's so they turn on and off together. The ATX splitter cable does it in the simplest and most direct way. The Add2PSU is just a Reed relay that joins the connections when the relay gets power from the Sata/molex connector. From my experience, in some cases the ATX splitter cables work to turn the PSU's on/off together when the Add2PSU won't.
|
|
|
|
|
Even with the stock Bios you still need to adjust the core and memory frequency. I use Windows v1703 with the blockchain drivers with Afterburner to set the core/memory and power limit. If you are using Claymore to set the power limit -powlim -5 decreses the TDP by 5% and -powlim 5 increases it by 5%. With RX 580's dual mining I set the power limit to -15% with a -150 mV core undervolt in Afterburner. Some cards like some of my RX 570's I need to increase the power limit to -5% for the cards to be stable.
|
|
|
|
|
Show Posts
