Version 0.3.4b.
EWBF's Zcash cuda miner. Expected speeds 444 sols/s gtx1070. Stock settings.
How? Stock Asus 1070 Strix OC i'm getting 400.. :/
|
|
|
Hi,
Can us Nvidia peeps please get some type of update? Using 12 x 1070's, on the ASUS 13 slot motherboard, nvidia-settings and nvidia-smi randomly using 100% of the CPU (i7 monster i might add) is not normal!
Regards, Cami
|
|
|
Pretty please could we have an API for the SimpleMining.net site? At the very least even a plain text or json return of the current "rigs list" and their relative stats.
|
|
|
thanks for the settings, what hashrate you have with those ?
~22.5 MH/s per GPU.
|
|
|
@tytanik - i experience the same issue issue like most of users with NV and more cards. H110+ 13 x P106 setup, found everything from the start, have the following problems: 1. Overclocking works pretty strange, to clock the memory of the P106 from 4000 to 4900 i needed to put 1600 as parameter. Steps that increase the MHz are really not relevant. Putting 900 clock to 4400 something. 2. Finally stabilized the machine to 325MH and runs well but it reboots without reason 14 times for 10 hours. Temperatures are under 65C, target is 76C.
So how to fix those nonsense reboots ?
Not all the cards will overclock as well as others, so 1 badly working card can cause a reboot. That being said, SMOS has some weird behavior with NVIDIA cards. Until they are fixed, you're better off mining ETH with (H110+ 13 x P106) with the following overclock settings: GPU Core: -200 Memory MHz: 500 Power Limit (watt): 70 Target Temperature ℃: 75 Minimum Fan speed %: 20 I have about 12 rigs, all of them with those settings.. no reboots, less noise and less heat.
|
|
|
So basicaly one of my rigs downloaded a new config and after that was giving me a Magic Cookie error and now the rig is hashing at 1mh per gpu... anyone got same problem?
Now after 3 new flashed pens i still cant get the rig online... Everytime the OS starts to boot it turns off the ethernet connection... Anyone can help? # dmesg Might show something useful
|
|
|
Could we get an update for Claymore's CryptoNote GPU Miner v9.7
Also When I mine with Claymore 9.7-10.0 eth/sia everything is good no gpu errors when I try to mine with claymore CryptoNote 9.1 overclocked or not I get constant errors "gpu fault detected" what could this be since it does that overclocked and not overclocked?
What GPU are you using?
|
|
|
Hello, is there a reason you don't support powerlimit as low as 50% for Nvidia?
Because a lot of Nvidia cards run ok with 50% powerlimit, dualmining. For me that's a big drawback becuse all my cards are under 80% powerlimit. All the Nvidia cards that i installed until now required a max powerlimit of 75.
My 13x1060's work just fine with a powerlimit of 55% using sMOS.
|
|
|
Hi everyone, i have 2 problems running this OS with nvidia GPUs (1060 6GB).
Problem 1 - no GUI I download fresh image for NV GPU, and when i start it got only text terminal. How start GUI? Running version for AMD GPUs GUI start by default.
Problem 2 - overclocking How to downclock core? While mining ETH theres no need to GPU core run on full speed. Under Windows I set core for -400MHz and hashrate are the same like on default clock. Negative value are not allowed. And second thing. Is there a way to turn of P2 State. To OC memory clock for 500MHz , from 4000 to 4500MHz, I need to set offest at 1400, so GPU definitly go in to P2 State and drop the clock.
I heard that under linux you can not reduce the power limit of the 1060's (changing it on the UI does nothing for its actual power usage).
|
|
|
I have strong evidence that Poloniex is going to support BCC VERY soon.
|
|
|
So I take it we hold onto our SJCX and there will be an easy way to get that onto the new platform? Does it need to be kept in the wallet or will keeping it on the exchange (like Poloniex) handle that?
|
|
|
~snip
coming out today release Can we see the feature list for the new release?
|
|
|
Store is nearly complete, just one or two days more Bitpay is working. Europe shipping rates are configured. Whats left to complete in store: - description + more photos - USA/Asia shippment rates. Shipping Rates for Cape Town, South Africa?
|
|
|
There was holidays and new year. We are getting back to work If there is a power outage, and the power comes back, can the SimpleminingResetter start the Rig? Or it must be definitely done manually? Thanks Most BIOS these days can change the state to power on automatically in the event of a power outage. (it's configurable in the BIOS, i've done it on mine)
|
|
|
Hi lbr! My hardware: 6x RX470 8G Gigabyte z170 gaming k3 8G RAM G4400 CPU
AMD drivers 16.11.5
In windows 7 x64 two GPUs have code 43 error. After i use your program and patch registry only 5 GPUs work fine and one - code 43 error. In Windows 10 work all 6 GPUs, but win10 unstabe, and telemetry, and updates... Can you wrote new program, which can run all 6 GPUs on Win7? I'll donate you, if you can.
This program works very well with 6 gpu, win 7 64bit, Crimson 16.10.2 Driver. With 6 x RX480's? I tried that, no go.
|
|
|
Like I said in an earlier post - I worry about the upgrading of this miner because of all the possible RX cards it will potentially add to the XMR network - making the difficulty skyrocket just like it did when they all appeared on the ETH network, but I guess it's inevitable and Claymore wants/needs his dev fees - he doesn't have to worry about difficulty, he just wants as many miners using his software as possible.
You can already mine XMR with the miner just fine. I have ZERO issues with 5 x RX480 cards. Also you're forgetting you can also use Wolf's XMR GPU miner, and also SG-miner (windows and linux). You're worried about nothing really. Does XMR respond to memory over/underclocking much? It doesn't seem to matter if I have my 290s at 1125, 1250 or 1375. Or my 380s at 1425 or 1500.
XMR responds to GPU clock speed. Bumping it up increases hash rate but uses more wattage.
|
|
|
What does "GPU1 hangs in OpenCL call" mean?
Possibly faulty PCI riser, Try replacing GPU1's riser and it might go away. Check your overclocking. Does it happen on stock rom?
|
|
|
Please allow workernames as username, not only wallet addresses
bumping this once more Ok I will release new version in 2-4 days, I will update many things. Thank you!
|
|
|
@Claymore
I am getting constant devfee DAG creation errors and constant crashes of the miner. ! The moement devfee DAG creation starts from dwarfpool; it crashes immediately with this error 18:09:21:751 87c DevFee: ETH: Stratum - connecting to 'eth-eu.dwarfpool.com' <87.98.182.61> port 8008 18:09:21:888 87c send: {"worker": "eth1.0", "jsonrpc": "2.0", "params": ["0xe19fFB70E148A76d26698036A9fFD22057967D1b", "x"], "id": 2, "method": "eth_submitLogin"} 18:09:21:889 87c DevFee: ETH: Stratum - Connected (eth-eu.dwarfpool.com:8008) 18:09:22:024 87c got 39 bytes 18:09:22:024 87c buf: {"id":2,"jsonrpc":"2.0","result":true} 18:09:22:024 87c parse packet: 38 18:09:22:024 87c ETH: Authorized 18:09:22:024 87c send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"} 18:09:22:024 87c new buf size: 0 18:09:22:163 87c got 244 bytes 18:09:22:163 87c buf: {"result":["0xd91c11bf6e42ba9dda8d6c80488bd3ce943989494b3ffbc59c634ee7645ba0d8","0xb0a52850ea22f7b03f44593e27552c6d850e40a9f6b92fbf1d15586b6affbccb","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}
18:09:22:163 87c parse packet: 242 18:09:22:163 87c ETH: job changed 18:09:22:163 87c new buf size: 0 18:09:22:164 87c DevFee: start mining 18:09:22:346 344 Setting DAG epoch #96... 18:09:23:987 344 Setting DAG epoch #96 for GPU #0 18:09:23:987 924 Setting DAG epoch #96 for GPU #3 18:09:23:987 8e0 Setting DAG epoch #96 for GPU #2 18:09:23:993 a78 Setting DAG epoch #96 for GPU #1 18:09:24:256 d7c recv: 51 18:09:24:256 d7c srv pck: 50 18:09:24:281 d7c srv bs: 0 18:09:24:281 d7c sent: 203 18:09:29:019 87c got 244 bytes 18:09:29:019 87c buf: {"result":["0xfbd42bf89ae4b0bdffdafa7c9ac7842b0cb13b4745f4cd3ea6c81e62c1617595","0xb0a52850ea22f7b03f44593e27552c6d850e40a9f6b92fbf1d15586b6affbccb","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":0}
18:09:29:019 87c parse packet: 242 18:09:29:019 87c ETH: job changed 18:09:29:019 87c new buf size: 0 18:09:29:020 87c DevFee: ETH: 12/30/16-18:09:29 - New job from eth-eu.dwarfpool.com:8008 18:09:29:020 87c target: 0x0000000225c17d04 18:09:29:266 804 recv: 51 18:09:29:266 804 srv pck: 50 18:09:29:292 804 srv bs: 0 18:09:29:292 804 sent: 182 18:09:29:557 13a8 GPU0 t=62C fan=35%, GPU1 t=60C fan=34%, GPU2 t=75C fan=34%, GPU3 t=70C fan=35% 18:09:29:558 13a8 em hbt: 0, fm hbt: 0, 18:09:29:558 13a8 watchdog - thread 0, hb time 7391 18:09:29:558 13a8 watchdog - thread 1, hb time 7219 18:09:29:558 13a8 watchdog - thread 2, hb time 7344 18:09:29:558 13a8 watchdog - thread 3, hb time 7172 18:09:29:558 13a8 watchdog - thread 4, hb time 7219 18:09:29:558 13a8 watchdog - thread 5, hb time 7375 18:09:29:558 13a8 watchdog - thread 6, hb time 7172 18:09:29:558 13a8 watchdog - thread 7, hb time 7375 18:09:31:596 8e0 GPU 2 DAG creation time - 7566 ms 18:09:31:596 8e0 Setting DAG epoch #96 for GPU #2 done 18:09:31:596 8e0 DevFee: restart timer because of updating DAG 18:09:31:607 924 GPU 3 DAG creation time - 7564 ms 18:09:31:608 924 Setting DAG epoch #96 for GPU #3 done 18:09:31:609 924 DevFee: restart timer because of updating DAG 18:09:31:643 a78 GPU 1 DAG creation time - 7609 ms 18:09:31:643 a78 Setting DAG epoch #96 for GPU #1 done 18:09:31:644 a78 DevFee: restart timer because of updating DAG 18:09:31:782 344 GPU 0 DAG creation time - 7634 ms 18:09:31:782 344 Setting DAG epoch #96 for GPU #0 done 18:09:31:783 344 DevFee: restart timer because of updating DAG 18:09:32:166 87c DevFee: ETH: checking pool connection... 18:09:32:166 87c send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
18:09:32:301 87c got 244 bytes 18:09:32:301 87c buf: {"result":["0xfbd42bf89ae4b0bdffdafa7c9ac7842b0cb13b4745f4cd3ea6c81e62c1617595","0xb0a52850ea22f7b03f44593e27552c6d850e40a9f6b92fbf1d15586b6affbccb","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}
18:09:32:301 87c parse packet: 242 18:09:32:301 87c ETH: job is the same 18:09:32:301 87c new buf size: 0 This is a new error. Gotta mine buddy!! 2 Gig video card?
|
|
|
I had my first power delivery failure today: Four risers off of one molex drop is too much. The modular connector at the PSU burnt up.
Four?! That's crazy town I won't put more than two risers on one molex ever.
|
|
|
|