 Show Posts
|
|
Pages: [1] 2 »
|
|
So, how do I send more than 10 IRD at a time. Wallet 5.0 can't send more than 10. Kinda makes sending 300K a bit tedious...
|
|
|
|
|
Is it possible to enable or disable a card in the MinerbabeOS or using kbminer? I have a card that locks up on occasion. I'll just remove it but was wondering some miners allow to specify which cards to mine on.
|
|
|
|
Anyone?
How much you get with 280x?
I have 3 R9 280x running 1180/1500 +20 powertune and get 390h/s on two and 440h/s on the other on CN Heavy. JCE 33b5 didn't increase by much - maybe 5%. But wow my RX cards are nearly 30% faster than 33b. And JCE was already the fasted CN miner by far. Some are pretty close in miner-reported hashrate, but at the pool JCE is 10-20% better than all others. I'm using BETA blockchain drivers. Still the fasted for me. |
|
|
|
Great miner. Love the management functionality. Tried it for BitTube but sounds like needs to be updated to support tube's new Cryptonight-Heavy variant named Saber. IPBC results in rejected shares. Any chance to add Saber in a future release?  |
|
|
|
Try with kernel 2 it will work
next version will set it automatically
That worked. Thanks! |
|
|
|
Anyone have download for 1.6.4? I missed it. 1.6.5 won't initialize cards on half my rigs. Some issue due to compiling everything into the .exe maybe.
Nope, thats not the problem probably. But you can download older versions from Mega, link on the first page. Here's the log on one of my rigs where 1.6.5 just exists. 1.6.3 works fine. Could I be missing dependancy or doesn't like the AMD Blockchain BETA driver? [2018-08-07 12:23:01] Miner version: 1.6.5
[2018-08-07 12:23:01] Windows version: 10.0 build 16299
[2018-08-07 12:23:02] Video driver version: 22.19.659.0
[2018-08-07 12:23:02] AMD Platform ID: 0
[2018-08-07 12:23:02] AMD platform FOUND
[2018-08-07 12:23:02] Found 3 AMD devices
[2018-08-07 12:23:02] CPU AES-NI: FALSE
[2018-08-07 12:23:02] GPU0: AMD Radeon R9 200 Series [Tahiti] [3072 MB][Intensity 27.0][W: 8][T: 1][K: 1][BUS: 3]
[2018-08-07 12:23:02] GPU1: AMD Radeon R9 200 Series [Tahiti] [3072 MB][Intensity 26.5][W: 8][T: 1][K: 1][BUS: 3]
[2018-08-07 12:23:02] GPU2: AMD Radeon (TM) R9 390 Series [Hawaii] [8192 MB][Intensity 38.0][W: 4][T: 1][K: 1][BUS: 4]
[2018-08-07 12:23:02] GPU3: AMD Radeon (TM) R9 390 Series [Hawaii] [8192 MB][Intensity 37.5][W: 4][T: 1][K: 1][BUS: 4]
[2018-08-07 12:23:02] GPU4: AMD Radeon (TM) R9 390 Series [Hawaii] [8192 MB][Intensity 38.0][W: 4][T: 1][K: 1][BUS: 4]
[2018-08-07 12:23:02] GPU5: AMD Radeon (TM) R9 390 Series [Hawaii] [8192 MB][Intensity 37.5][W: 4][T: 1][K: 1][BUS: 4]
[2018-08-07 12:23:02] GPU6: AMD Radeon (TM) R9 390 Series [Hawaii] [8192 MB][Intensity 39.0][W: 4][T: 1][K: 1][BUS: 1]
[2018-08-07 12:23:02] GPU7: AMD Radeon (TM) R9 390 Series [Hawaii] [8192 MB][Intensity 38.5][W: 4][T: 1][K: 1][BUS: 1]
[2018-08-07 12:23:02] GPU8: AMD Radeon (TM) R9 390 Series [Hawaii] [8192 MB][Intensity 39.0][W: 4][T: 1][K: 1][BUS: 1]
[2018-08-07 12:23:02] GPU9: AMD Radeon (TM) R9 390 Series [Hawaii] [8192 MB][Intensity 38.5][W: 4][T: 1][K: 1][BUS: 1]
[2018-08-07 12:23:02] ADL is enabled
[2018-08-07 12:23:02] CryptonightV7 mode enabled
[2018-08-07 12:23:02] DevFee pool SET
[2018-08-07 12:23:02] DevFee address SET
[2018-08-07 12:23:02] Starting init of mining threads
[2018-08-07 12:23:02] Compiling kernel for DEVICE BUS ID 3 ...
[2018-08-07 12:23:03] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram for DeviceID 0 (Thread 0)
[2018-08-07 12:23:03] Error initing GPU's. Stopping miner process
[2018-08-07 12:23:03] Stopping miner process |
|
|
|
|
Anyone have download for 1.6.4? I missed it. 1.6.5 won't initialize cards on half my rigs. Some issue due to compiling everything into the .exe maybe.
|
|
|
|
can someone share the "start.bat" file, I cant atart the miner   Here's mine. Monitors for crash and restarts if no longer in memory. setx GPU_FORCE_64BIT_PTR 1
setx GPU_MAX_HEAP_SIZE 100
setx GPU_MAX_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_MAX_SINGLE_ALLOC_PERCENT 100
@echo off
cd %~dp0
cls
SETLOCAL EnableExtensions
set EXE=bxb-miner.exe
:START
FOR /F %%x IN ('tasklist /NH /FI "IMAGENAME eq %EXE%"') DO IF %%x == %EXE% goto RUNNING
%EXE% -c config_lite_v7.json
TIMEOUT /T 15 /NOBREAK
goto START
:RUNNING
echo "%EXE% is already running"
pause |
|
|
|
Hi,
Please give a config.txt file for AMD RX280X!
Thanks
I have four R9 280x cards that do between 475 to 550h/s depending on the ram type. Here's my config: "gpu_conf" :
[
{ "id" : 0, "intensity" : 27, "worksize" : 8, "threads" : 2, "adl_type" : 2}, You can try intensity 29 or 31. Double the intensity if you drop to worksize 4. But I find worksize 8 gives best hashrate. |
|
|
|
And after seen all this you still think it's miner related ? Absolutely... you've missed this: At the same time xmr-stak or xmrig works fine
Something strange exactly in bunch srbminer with electroneum.hashvault or electroneum.miningpoolhub. With etn.nanopool works fine. I've had the same thing happen a few times over the last few weeks. Prefer SRBMiner so switched to Nanopool and no more issues. And Nanopool just reduced their fixed diff from 240000 to 120000 so now getting more shares on lower hash rigs and and more consistent shares. Weird. |
|
|
|
+ I would like to politely ask everyone if they appreciate my work, to switch their miners to this new version.
All of my miners have been updated to 1.5.8. Great work - keep it up |
|
|
|
V1.5.5 (read more)- No need for all that stuff in start.bat anymore, because watchdog can now restart the whole miner process without it - Fixed kernels 3 & 4 for heavy algo - Fixed OCL binary caching for Vega cards - Added last job received info in stats and API - Added 'job_timeout' parameter to pools config, it reconnects to pool if no job received for 'job_timeout' time (in seconds), default is 5 min - Pool reload now checks if current pool is first in reloaded pools list, if not, it switches to first pool Found a bug. Watchdog was unable to restart the miner when GPU hung up. Error returned was could not find file - was clear it couldn't handle a space in a folder name in the path to SRBMiner-CN.exe May want to either encapsulate the path or use the 8.3 folder name. I moved it into folder with no spaces, but means won't restart if put it in Program Files or anywhere else with a space. |
|
|
|
Yay ! So far - so good. Just installed it on my testrig and it acts up a bit. CN Heavy: Miner restarts as soon as a 2nd 8GB card wants to start with two threads. Nothing in the logs - just a miner restart. Will dig a bit deeper l8r on when i have a bit more time. More details when i had time to fidel a bit with the miner  Crap. I have the same issue. 2 R9 390x. First one starts up, but when second one starts when goes from 1.2GB memory to 2.4, application crashes  |
|
|
|
Hi found a problem. Grabbed 1.3.3 alpha. Mining Stellite. After coming off DEVFEE, version of Cryptonight doesn't switch back so after DEVFEE finishes, no shares are submitted, at all. Here's snippet of log. You can see it switches from Monero version 3 to Monero version 7 for DEVFEE, but never switches back. I have to restart it before I get any new shares: 2018-04-15 10:43:11.8818 [1] Gateless Gate Sharp 1.3.3 alpha started.
2018-04-15 10:43:12.6787 [1] Number of Devices: 6
2018-04-15 10:43:12.7256 [1] Successfully initialized AMD Display Library.
2018-04-15 10:43:12.7256 [1] Number of ADL Adapters: 46
2018-04-15 10:43:12.7725 [1] ADL_Adapter_AdapterInfo_Get() returned error code 0
2018-04-15 10:43:12.7725 [1] Failed to initialize NVIDIA Management Library.
2018-04-15 10:43:21.7113 [1] Loaded PhyMem.
2018-04-15 10:43:27.5847 [1] Loaded DeviceSettings\AMD Radeon RX 470 4.0GB.xml for Device #0.
2018-04-15 10:43:37.4451 [1] Loaded DeviceSettings\AMD Radeon RX 470 4.0GB.xml for Device #2.
2018-04-15 10:43:46.8876 [1] Loaded DeviceSettings\AMD Radeon RX 470 4.0GB.xml for Device #3.
2018-04-15 10:43:56.1855 [1] Loaded DeviceSettings\AMD Radeon RX 470 4.0GB.xml for Device #4.
2018-04-15 10:43:57.0450 [1] Unloaded PhyMem.
2018-04-15 10:43:57.0606 [1] Invalid argument: C:\Users\James Simmons\Downloads\Gateless Gate Sharp\GatelessGateSharp.exe
2018-04-15 10:44:01.2017 [13] Running garbage collection...
2018-04-15 10:44:01.2017 [13] Memory used before collection: 138MB
2018-04-15 10:44:01.2798 [13] Memory used before collection: 25MB
2018-04-15 10:44:03.2019 [15] API Listener started.
2018-04-15 10:46:29.9988 [1] Saving settings to C:\Users\James Simmons\AppData\Roaming\GatelessGateSharp\GatelessGateSharp.sqlite...
2018-04-15 10:46:30.2332 [1] Saved settings.
2018-04-15 10:46:30.2645 [1] Launching miner(s) for Custom Pool 0...
2018-04-15 10:46:30.5927 [16] Miner thread for Device #0 started.
2018-04-15 10:46:30.5927 [16] NiceHash mode is off.
2018-04-15 10:46:30.6084 [16] Loaded Kernels\cryptonight.cl for Device #0.
2018-04-15 10:46:31.4209 [17] Miner thread for Device #0 started.
2018-04-15 10:46:31.4209 [17] NiceHash mode is off.
2018-04-15 10:46:31.4209 [17] Loaded Kernels\cryptonight.cl for Device #0.
2018-04-15 10:46:32.2960 [18] Miner thread for Device #1 started.
2018-04-15 10:46:32.2960 [18] NiceHash mode is off.
2018-04-15 10:46:32.2960 [18] Loaded Kernels\cryptonight.cl for Device #1.
2018-04-15 10:46:33.1086 [19] Miner thread for Device #1 started.
2018-04-15 10:46:33.1086 [19] NiceHash mode is off.
2018-04-15 10:46:33.1242 [19] Loaded Kernels\cryptonight.cl for Device #1.
2018-04-15 10:46:35.1869 [20] Miner thread for Device #2 started.
2018-04-15 10:46:35.1869 [20] NiceHash mode is off.
2018-04-15 10:46:35.1869 [16] Built cryptonight program for Device #0.
2018-04-15 10:46:35.1869 [16] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:46:35.2025 [20] Loaded Kernels\cryptonight.cl for Device #2.
[color=yellow]2018-04-15 10:46:35.2025 [16] Switching to Monero Version 3[/color]
2018-04-15 10:46:36.0307 [21] Miner thread for Device #2 started.
2018-04-15 10:46:36.0307 [21] NiceHash mode is off.
2018-04-15 10:46:36.0307 [21] Loaded Kernels\cryptonight.cl for Device #2.
2018-04-15 10:46:38.1502 [22] Miner thread for Device #3 started.
2018-04-15 10:46:38.1502 [22] NiceHash mode is off.
2018-04-15 10:46:38.1502 [19] Built cryptonight program for Device #1.
2018-04-15 10:46:38.1502 [19] Build options: -O5 -legacy -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:46:38.1502 [19] Switching to Monero Version 3
2018-04-15 10:46:38.1658 [22] Loaded Kernels\cryptonight.cl for Device #3.
2018-04-15 10:46:38.9784 [23] Miner thread for Device #3 started.
2018-04-15 10:46:38.9784 [23] NiceHash mode is off.
2018-04-15 10:46:38.9784 [23] Loaded Kernels\cryptonight.cl for Device #3.
2018-04-15 10:46:42.7913 [24] Miner thread for Device #4 started.
2018-04-15 10:46:42.7913 [24] NiceHash mode is off.
2018-04-15 10:46:42.7913 [21] Built cryptonight program for Device #2.
2018-04-15 10:46:42.7913 [21] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:46:42.7913 [21] Switching to Monero Version 3
2018-04-15 10:46:42.7913 [24] Loaded Kernels\cryptonight.cl for Device #4.
2018-04-15 10:46:43.6039 [25] Miner thread for Device #4 started.
2018-04-15 10:46:43.6039 [25] NiceHash mode is off.
2018-04-15 10:46:43.6039 [25] Loaded Kernels\cryptonight.cl for Device #4.
2018-04-15 10:46:44.9478 [16] Device #0 submitted Share #0 to communitypool.stellite.cash as Se2xy7zgW....
2018-04-15 10:46:44.9478 [16] Device #0 submitted a share to communitypool.stellite.cash as Se2xy7zgW....
2018-04-15 10:46:45.1666 [9] Share #0 accepted.
2018-04-15 10:46:45.2291 [26] Miner thread for Device #5 started.
2018-04-15 10:46:45.2291 [26] NiceHash mode is off.
2018-04-15 10:46:45.2447 [26] Loaded Kernels\cryptonight.cl for Device #5.
2018-04-15 10:46:46.0573 [27] Miner thread for Device #5 started.
2018-04-15 10:46:46.0573 [27] NiceHash mode is off.
2018-04-15 10:46:46.0573 [27] Loaded Kernels\cryptonight.cl for Device #5.
2018-04-15 10:46:46.5417 [16] Device #0 (CryptoNight): 558.70 h/s
2018-04-15 10:46:47.2606 [23] Built cryptonight program for Device #3.
2018-04-15 10:46:47.2606 [23] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:46:47.2606 [23] Switching to Monero Version 3
2018-04-15 10:46:49.3389 [19] Device #1 (CryptoNight): 360.80 h/s
2018-04-15 10:46:49.9171 [27] Built cryptonight program for Device #5.
2018-04-15 10:46:49.9171 [27] Build options: -O5 -legacy -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:46:49.9171 [27] Switching to Monero Version 3
2018-04-15 10:46:50.8391 [9] Received new job: h81JaI/iTTSABw1vZOjh1+ORJg5w
2018-04-15 10:46:52.5893 [26] Built cryptonight program for Device #5.
2018-04-15 10:46:52.5893 [26] Build options: -O5 -legacy -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:46:52.5893 [26] Switching to Monero Version 3
2018-04-15 10:46:54.2145 [21] Device #2 (CryptoNight): 555.02 h/s
2018-04-15 10:46:56.9492 [25] Built cryptonight program for Device #4.
2018-04-15 10:46:56.9492 [25] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:46:56.9492 [25] Switching to Monero Version 3
2018-04-15 10:46:57.7773 [16] Device #0 (CryptoNight): 558.65 h/s
2018-04-15 10:46:58.6681 [23] Device #3 (CryptoNight): 554.60 h/s
2018-04-15 10:47:00.4964 [19] Device #1 (CryptoNight): 362.37 h/s
2018-04-15 10:47:01.5278 [27] Device #5 (CryptoNight): 226.17 h/s
2018-04-15 10:47:01.8559 [24] Built cryptonight program for Device #4.
2018-04-15 10:47:01.8559 [24] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:47:01.8559 [24] Switching to Monero Version 3
2018-04-15 10:47:03.4498 [26] Device #5 (CryptoNight): 226.17 h/s
2018-04-15 10:47:05.5125 [21] Device #2 (CryptoNight): 554.71 h/s
2018-04-15 10:47:06.7002 [22] Built cryptonight program for Device #3.
2018-04-15 10:47:06.7002 [22] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:47:06.7002 [22] Switching to Monero Version 3
2018-04-15 10:47:07.6378 [25] Device #4 (CryptoNight): 316.43 h/s
2018-04-15 10:47:09.0129 [16] Device #0 (CryptoNight): 558.26 h/s
2018-04-15 10:47:09.6536 [23] Device #3 (CryptoNight): 308.67 h/s
2018-04-15 10:47:11.6539 [19] Device #1 (CryptoNight): 361.56 h/s
2018-04-15 10:47:11.9195 [20] Built cryptonight program for Device #2.
2018-04-15 10:47:11.9195 [20] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:47:11.9195 [20] Switching to Monero Version 3
2018-04-15 10:47:13.4196 [27] Device #5 (CryptoNight): 226.20 h/s
2018-04-15 10:47:13.6697 [24] Device #4 (CryptoNight): 308.10 h/s
2018-04-15 10:47:14.5604 [18] Built cryptonight program for Device #1.
2018-04-15 10:47:14.5604 [18] Build options: -O5 -legacy -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:47:14.5604 [18] Switching to Monero Version 3
2018-04-15 10:47:15.3417 [26] Device #5 (CryptoNight): 225.79 h/s
2018-04-15 10:47:17.7170 [21] Device #2 (CryptoNight): 316.14 h/s
2018-04-15 10:47:18.4827 [22] Device #3 (CryptoNight): 308.10 h/s
2018-04-15 10:47:18.9046 [25] Device #4 (CryptoNight): 317.28 h/s
2018-04-15 10:47:18.9358 [17] Built cryptonight program for Device #0.
2018-04-15 10:47:18.9358 [17] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:47:18.9358 [17] Switching to Monero Version 3
2018-04-15 10:47:20.2797 [16] Device #0 (CryptoNight): 543.69 h/s
2018-04-15 10:47:20.9518 [23] Device #3 (CryptoNight): 318.14 h/s
2018-04-15 10:47:21.9675 [19] Device #1 (CryptoNight): 204.98 h/s
2018-04-15 10:47:23.7333 [20] Device #2 (CryptoNight): 308.10 h/s
2018-04-15 10:47:25.2646 [24] Device #4 (CryptoNight): 309.70 h/s
2018-04-15 10:47:25.3115 [27] Device #5 (CryptoNight): 226.80 h/s
2018-04-15 10:47:26.2805 [18] Device #1 (CryptoNight): 204.75 h/s
2018-04-15 10:47:27.2337 [26] Device #5 (CryptoNight): 225.98 h/s
2018-04-15 10:47:28.9682 [21] Device #2 (CryptoNight): 318.25 h/s
2018-04-15 10:47:30.0777 [22] Device #3 (CryptoNight): 309.59 h/s
2018-04-15 10:47:30.2184 [25] Device #4 (CryptoNight): 316.19 h/s
2018-04-15 10:47:31.5935 [17] Device #0 (CryptoNight): 320.18 h/s
2018-04-15 10:47:31.9998 [16] Device #0 (CryptoNight): 309.16 h/s
2018-04-15 10:47:32.2655 [23] Device #3 (CryptoNight): 316.83 h/s
2018-04-15 10:47:32.8905 [19] Device #1 (CryptoNight): 204.90 h/s
2018-04-15 10:47:35.3438 [20] Device #2 (CryptoNight): 308.95 h/s
2018-04-15 10:47:36.8128 [24] Device #4 (CryptoNight): 310.67 h/s
2018-04-15 10:47:37.1878 [27] Device #5 (CryptoNight): 226.20 h/s
2018-04-15 10:47:37.2347 [18] Device #1 (CryptoNight): 204.23 h/s
2018-04-15 10:47:37.7817 [16] Device #0 submitted Share #1 to communitypool.stellite.cash as Se2xy7zgW....
2018-04-15 10:47:37.7817 [16] Device #0 submitted a share to communitypool.stellite.cash as Se2xy7zgW....
2018-04-15 10:47:37.9692 [9] Share #1 accepted.
2018-04-15 10:47:39.1256 [26] Device #5 (CryptoNight): 225.91 h/s
2018-04-15 10:47:40.2663 [21] Device #2 (CryptoNight): 316.64 h/s
2018-04-15 10:47:41.5790 [25] Device #4 (CryptoNight): 315.25 h/s
2018-04-15 12:05:27.6441 [1] Switching to the DEVFEE mode...
2018-04-15 12:05:27.6753 [27] Restarting miner thread...
2018-04-15 12:05:27.7222 [13] Device #0 (CryptoNight): 314.37 h/s
2018-04-15 12:05:27.7222 [13] Restarting miner thread...
[color=yellow]2018-04-15 12:05:27.9567 [13] Switching to Monero Version 7[/color]
2018-04-15 12:05:28.0192 [27] Switching to Monero Version 7
2018-04-15 12:05:28.1598 [23] Switching to Monero Version 7
2018-04-15 12:05:28.2223 [30] Device #5 (CryptoNight): 233.19 h/s
2018-04-15 12:05:28.2223 [30] Switching to Monero Version 7
2018-04-15 12:05:28.3630 [29] Switching to Monero Version 7
2018-04-15 12:05:28.4723 [26] Switching to Monero Version 7
2018-04-15 12:05:28.5974 [18] Switching to Monero Version 7
2018-04-15 12:05:28.6442 [20] Device #1 (CryptoNight): 202.53 h/s
2018-04-15 12:05:28.6442 [20] Switching to Monero Version 7
2018-04-15 12:05:28.8474 [28] Device #4 (CryptoNight): 347.24 h/s
2018-04-15 12:05:28.8474 [28] Switching to Monero Version 7
2018-04-15 12:05:28.9724 [15] Switching to Monero Version 7
2018-04-15 12:05:29.6287 [24] Device #2 (CryptoNight): 312.96 h/s
2018-04-15 12:05:29.6287 [24] Switching to Monero Version 7
2018-04-15 12:05:29.8631 [25] Device #3 (CryptoNight): 312.94 h/s
2018-04-15 12:05:29.8631 [25] Switching to Monero Version 7
2018-04-15 12:05:31.3320 [26] Device #3 submitted a share to xmr-us-east1.nanopool.org as a DEVFEE.
2018-04-15 12:05:31.3320 [26] Device #3 submitted a share to xmr-us-east1.nanopool.org as a DEVFEE.
2018-04-15 12:05:31.3320 [26] Device #3 (CryptoNight): 312.98 h/s
2018-04-15 12:05:31.5508 [32] Share accepted.
2018-04-15 12:05:32.2071 [29] Device #5 (CryptoNight): 233.18 h/s
2018-04-15 12:05:32.9885 [18] Device #1 (CryptoNight): 204.64 h/s
2018-04-15 12:05:33.8947 [23] Device #2 (CryptoNight): 312.95 h/s
2018-04-15 12:05:34.7074 [15] Device #0 (CryptoNight): 312.45 h/s
2018-04-15 12:05:39.3016 [13] Device #0 (CryptoNight): 315.69 h/s
2018-04-15 12:05:39.3797 [27] Device #4 (CryptoNight): 314.90 h/s
2018-04-15 12:05:39.5985 [20] Device #1 (CryptoNight): 204.57 h/s
2018-04-15 12:05:39.7392 [30] Device #5 (CryptoNight): 233.14 h/s
2018-04-15 12:05:40.3955 [28] Device #4 (CryptoNight): 310.74 h/s
2018-04-15 12:05:41.0831 [24] Device #2 (CryptoNight): 312.92 h/s
2018-04-15 12:05:41.3175 [25] Device #3 (CryptoNight): 312.95 h/s
2018-04-15 12:05:42.7864 [26] Device #3 (CryptoNight): 312.92 h/s
2018-04-15 12:05:43.7240 [29] Device #5 (CryptoNight): 232.93 h/s
2018-04-15 12:05:43.9428 [18] Device #1 (CryptoNight): 204.74 h/s
2018-04-15 12:05:45.3492 [23] Device #2 (CryptoNight): 312.94 h/s
2018-04-15 12:05:46.1617 [15] Device #0 (CryptoNight): 312.27 h/s
2018-04-15 12:05:50.5372 [20] Device #1 (CryptoNight): 205.35 h/s
2018-04-15 12:05:50.6622 [13] Device #0 (CryptoNight): 315.37 h/s
2018-04-15 12:05:50.7715 [27] Device #4 (CryptoNight): 314.48 h/s
2018-04-15 12:05:50.9591 [32] Received new job: 4817
2018-04-15 12:05:51.2717 [30] Device #5 (CryptoNight): 233.19 h/s
2018-04-15 12:05:51.9124 [28] Device #4 (CryptoNight): 311.40 h/s
2018-04-15 12:05:52.5217 [24] Device #2 (CryptoNight): 312.94 h/s
2018-04-15 12:05:52.7562 [25] Device #3 (CryptoNight): 313.05 h/s
2018-04-15 12:05:54.2407 [26] Device #3 (CryptoNight): 312.76 h/s
2018-04-15 12:05:54.8971 [18] Device #1 (CryptoNight): 204.52 h/s
2018-04-15 12:05:55.2565 [29] Device #5 (CryptoNight): 233.16 h/s
2018-04-15 12:05:56.4753 [27] Device #4 submitted a share to xmr-us-east1.nanopool.org as a DEVFEE.
2018-04-15 12:05:56.4753 [27] Device #4 submitted a share to xmr-us-east1.nanopool.org as a DEVFEE.
2018-04-15 12:05:56.6628 [32] Share accepted.
[color=orange]2018-04-15 12:06:27.6506 [1] Switching back from the DEVFEE mode...[/color]
2018-04-15 12:06:27.7443 [18] Device #1 (CryptoNight): 203.13 h/s
2018-04-15 12:06:28.5882 [26] Device #3 (CryptoNight): 312.82 h/s
2018-04-15 12:06:29.8382 [29] Device #5 (CryptoNight): 233.18 h/s
2018-04-15 12:06:30.5728 [12] Received new job: 6kwKoZg81V4326woKS+swufMYJ8m
2018-04-15 12:06:31.1509 [23] Device #2 (CryptoNight): 313.06 h/s
2018-04-15 12:06:31.8541 [15] Device #0 (CryptoNight): 313.84 h/s
2018-04-15 12:06:34.3544 [20] Device #1 (CryptoNight): 205.14 h/s
2018-04-15 12:06:36.2140 [13] Device #0 (CryptoNight): 314.48 h/s
2018-04-15 12:06:36.4796 [27] Device #4 (CryptoNight): 313.06 h/s
2018-04-15 12:06:37.3704 [30] Device #5 (CryptoNight): 233.30 h/s
2018-04-15 12:06:37.8392 [28] Device #4 (CryptoNight): 312.62 h/s
2018-04-15 12:06:38.3392 [24] Device #2 (CryptoNight): 313.02 h/s
2018-04-15 12:06:38.5580 [25] Device #3 (CryptoNight): 312.94 h/s
2018-04-15 12:06:38.7143 [18] Device #1 (CryptoNight): 203.98 h/s
2018-04-15 12:06:39.2612 [12] Received new job: TjuVcz7aiXSYG7mFJVc+Ayh3mtfK
2018-04-15 12:06:40.0425 [26] Device #3 (CryptoNight): 312.81 h/s
2018-04-15 12:06:41.3552 [29] Device #5 (CryptoNight): 233.16 h/s
2018-04-15 12:06:42.6053 [23] Device #2 (CryptoNight): 313.04 h/s
2018-04-15 12:06:43.2616 [15] Device #0 (CryptoNight): 314.93 h/s
2018-04-15 12:06:45.3087 [20] Device #1 (CryptoNight): 204.91 h/s
2018-04-15 12:06:47.6215 [13] Device #0 (CryptoNight): 314.81 h/s
2018-04-15 12:06:47.9184 [27] Device #4 (CryptoNight): 313.50 h/s
2018-04-15 12:06:48.9028 [30] Device #5 (CryptoNight): 233.34 h/s
2018-04-15 12:06:49.2935 [28] Device #4 (CryptoNight): 312.66 h/s
2018-04-15 12:06:49.6529 [18] Device #1 (CryptoNight): 204.17 h/s
2018-04-15 12:06:49.7936 [24] Device #2 (CryptoNight): 312.92 h/s
2018-04-15 12:06:50.0123 [25] Device #3 (CryptoNight): 312.94 h/s
2018-04-15 12:06:51.4968 [26] Device #3 (CryptoNight): 313.19 h/s
2018-04-15 12:06:52.8876 [29] Device #5 (CryptoNight): 232.97 h/s
2018-04-15 12:06:54.0597 [23] Device #2 (CryptoNight): 312.95 h/s
2018-04-15 12:06:54.6847 [15] Device #0 (CryptoNight): 313.86 h/s
2018-04-15 12:06:56.2630 [20] Device #1 (CryptoNight): 204.73 h/s
2018-04-15 12:06:59.0289 [13] Device #0 (CryptoNight): 314.26 h/s
2018-04-15 12:06:59.3571 [27] Device #4 (CryptoNight): 313.27 h/s
2018-04-15 12:07:00.4197 [30] Device #5 (CryptoNight): 233.13 h/s
2018-04-15 12:07:00.6072 [18] Device #1 (CryptoNight): 204.60 h/s
2018-04-15 12:07:00.7635 [28] Device #4 (CryptoNight): 312.66 h/s
2018-04-15 12:07:01.2479 [24] Device #2 (CryptoNight): 313.02 h/s
2018-04-15 12:07:01.4666 [25] Device #3 (CryptoNight): 312.91 h/s
2018-04-15 12:07:02.9356 [26] Device #3 (CryptoNight): 313.33 h/s
2018-04-15 12:07:04.4044 [29] Device #5 (CryptoNight): 233.15 h/s
2018-04-15 12:07:05.5140 [23] Device #2 (CryptoNight): 312.54 h/s
2018-04-15 12:07:06.0921 [15] Device #0 (CryptoNight): 313.39 h/s
2018-04-15 12:07:07.2173 [20] Device #1 (CryptoNight): 204.53 h/s
2018-04-15 12:07:10.4364 [13] Device #0 (CryptoNight): 313.49 h/s
2018-04-15 12:07:10.8115 [27] Device #4 (CryptoNight): 313.05 h/s
2018-04-15 12:07:11.5459 [18] Device #1 (CryptoNight): 204.63 h/s
2018-04-15 12:07:11.9522 [30] Device #5 (CryptoNight): 233.17 h/s
2018-04-15 12:07:12.2179 [28] Device #4 (CryptoNight): 312.91 h/s
2018-04-15 12:07:12.6867 [24] Device #2 (CryptoNight): 313.08 h/s
2018-04-15 12:07:12.9211 [25] Device #3 (CryptoNight): 313.06 h/s
2018-04-15 12:07:14.3900 [26] Device #3 (CryptoNight): 312.76 h/s
2018-04-15 12:07:15.9370 [29] Device #5 (CryptoNight): 233.14 h/s
2018-04-15 12:07:16.9683 [23] Device #2 (CryptoNight): 313.16 h/s
2018-04-15 12:07:17.4996 [15] Device #0 (CryptoNight): 313.66 h/s
2018-04-15 12:07:18.1716 [20] Device #1 (CryptoNight): 204.76 h/s
2018-04-15 12:07:21.8283 [13] Device #0 (CryptoNight): 313.94 h/s
2018-04-15 12:07:22.2501 [27] Device #4 (CryptoNight): 313.18 h/s
2018-04-15 12:07:22.5001 [18] Device #1 (CryptoNight): 204.57 h/s
2018-04-15 12:07:23.4846 [30] Device #5 (CryptoNight): 233.07 h/s
2018-04-15 12:07:23.6722 [28] Device #4 (CryptoNight): 312.86 h/s
2018-04-15 12:07:24.1410 [24] Device #2 (CryptoNight): 312.95 h/s
2018-04-15 12:07:24.3754 [25] Device #3 (CryptoNight): 312.83 h/s
2018-04-15 12:07:25.8442 [26] Device #3 (CryptoNight): 313.10 h/s
2018-04-15 12:07:27.4694 [29] Device #5 (CryptoNight): 232.93 h/s
2018-04-15 12:07:28.4070 [23] Device #2 (CryptoNight): 312.94 h/s
2018-04-15 12:07:28.9228 [15] Device #0 (CryptoNight): 313.92 h/s
2018-04-15 12:07:29.1103 [20] Device #1 (CryptoNight): 204.48 h/s
2018-04-15 12:07:30.6572 [12] Received new job: aWTFKKvnCsatry0LcqPyg21MgrmP
2018-04-15 12:07:33.2357 [13] Device #0 (CryptoNight): 314.49 h/s
2018-04-15 12:07:33.4545 [18] Device #1 (CryptoNight): 204.90 h/s
2018-04-15 12:07:33.7045 [27] Device #4 (CryptoNight): 312.84 h/s
2018-04-15 12:07:35.0015 [30] Device #5 (CryptoNight): 233.18 h/s
2018-04-15 12:07:35.1266 [28] Device #4 (CryptoNight): 312.91 h/s
2018-04-15 12:07:35.5954 [24] Device #2 (CryptoNight): 312.84 h/s
2018-04-15 12:07:35.8298 [25] Device #3 (CryptoNight): 313.05 h/s
2018-04-15 12:07:37.2986 [26] Device #3 (CryptoNight): 312.94 h/s
2018-04-15 12:07:38.9864 [29] Device #5 (CryptoNight): 233.11 h/s
2018-04-15 12:07:39.8614 [23] Device #2 (CryptoNight): 312.94 h/s
2018-04-15 12:07:40.0646 [20] Device #1 (CryptoNight): 204.83 h/s
2018-04-15 12:07:40.3459 [15] Device #0 (CryptoNight): 313.76 h/s
2018-04-15 12:07:44.3931 [18] Device #1 (CryptoNight): 205.19 h/s
2018-04-15 12:07:44.6276 [13] Device #0 (CryptoNight): 314.19 h/s
2018-04-15 12:07:45.1589 [27] Device #4 (CryptoNight): 312.83 h/s
2018-04-15 12:07:46.5340 [30] Device #5 (CryptoNight): 233.17 h/s
2018-04-15 12:07:46.5809 [28] Device #4 (CryptoNight): 312.89 h/s
2018-04-15 12:07:47.0497 [24] Device #2 (CryptoNight): 313.08 h/s
2018-04-15 12:07:47.2685 [25] Device #3 (CryptoNight): 313.21 h/s
2018-04-15 12:07:48.7530 [26] Device #3 (CryptoNight): 313.00 h/s
2018-04-15 12:07:50.5188 [29] Device #5 (CryptoNight): 233.10 h/s
2018-04-15 12:07:51.0189 [20] Device #1 (CryptoNight): 204.73 h/s
2018-04-15 12:07:51.3158 [23] Device #2 (CryptoNight): 313.06 h/s
2018-04-15 12:07:51.7533 [15] Device #0 (CryptoNight): 313.93 h/s
2018-04-15 12:07:55.3475 [18] Device #1 (CryptoNight): 205.15 h/s
2018-04-15 12:07:56.0351 [13] Device #0 (CryptoNight): 314.16 h/s
2018-04-15 12:07:56.6132 [27] Device #4 (CryptoNight): 312.95 h/s
2018-04-15 12:07:58.0353 [28] Device #4 (CryptoNight): 313.15 h/s
2018-04-15 12:07:58.0509 [30] Device #5 (CryptoNight): 233.27 h/s
2018-04-15 12:07:58.5040 [24] Device #2 (CryptoNight): 312.56 h/s
2018-04-15 12:07:58.7228 [25] Device #3 (CryptoNight): 313.16 h/s
2018-04-15 12:08:00.1917 [26] Device #3 (CryptoNight): 313.01 h/s
2018-04-15 12:08:01.9576 [20] Device #1 (CryptoNight): 204.93 h/s
2018-04-15 12:08:02.0357 [29] Device #5 (CryptoNight): 233.14 h/s
2018-04-15 12:08:02.7701 [23] Device #2 (CryptoNight): 313.05 h/s
2018-04-15 12:08:03.1608 [15] Device #0 (CryptoNight): 314.58 h/s
2018-04-15 12:08:06.3018 [18] Device #1 (CryptoNight): 204.98 h/s
2018-04-15 12:08:07.4425 [13] Device #0 (CryptoNight): 313.92 h/s
2018-04-15 12:08:08.0520 [27] Device #4 (CryptoNight): 313.27 h/s
2018-04-15 12:08:09.4896 [28] Device #4 (CryptoNight): 312.88 h/s
2018-04-15 12:08:09.5833 [30] Device #5 (CryptoNight): 233.13 h/s
2018-04-15 12:08:09.9584 [24] Device #2 (CryptoNight): 312.96 h/s
2018-04-15 12:08:10.1772 [25] Device #3 (CryptoNight): 313.05 h/s
2018-04-15 12:08:11.6461 [26] Device #3 (CryptoNight): 313.03 h/s
2018-04-15 12:08:12.9275 [20] Device #1 (CryptoNight): 203.38 h/s
2018-04-15 12:08:13.5681 [29] Device #5 (CryptoNight): 233.12 h/s
2018-04-15 12:08:14.2245 [23] Device #2 (CryptoNight): 312.84 h/s
2018-04-15 12:08:14.5839 [15] Device #0 (CryptoNight): 314.00 h/s
2018-04-15 12:08:17.2873 [18] Device #1 (CryptoNight): 205.16 h/s
2018-04-15 12:08:18.8344 [13] Device #0 (CryptoNight): 315.04 h/s
2018-04-15 12:08:19.5063 [27] Device #4 (CryptoNight): 313.17 h/s
2018-04-15 12:08:20.9440 [28] Device #4 (CryptoNight): 312.95 h/s
2018-04-15 12:08:21.1002 [30] Device #5 (CryptoNight): 233.17 h/s
2018-04-15 12:08:21.3971 [24] Device #2 (CryptoNight): 312.89 h/s
2018-04-15 12:08:21.6159 [25] Device #3 (CryptoNight): 313.16 h/s
2018-04-15 12:08:23.1005 [26] Device #3 (CryptoNight): 312.97 h/s
2018-04-15 12:08:23.8974 [20] Device #1 (CryptoNight): 205.00 h/s
2018-04-15 12:08:25.0850 [29] Device #5 (CryptoNight): 232.98 h/s
2018-04-15 12:08:25.6632 [23] Device #2 (CryptoNight): 312.95 h/s
2018-04-15 12:08:25.9914 [15] Device #0 (CryptoNight): 314.48 h/s
2018-04-15 12:08:28.2416 [18] Device #1 (CryptoNight): 205.36 h/s
2018-04-15 12:08:30.2419 [13] Device #0 (CryptoNight): 313.93 h/s
2018-04-15 12:08:30.7263 [12] Received new job: uYWWVY7ltnIsow52Hn/yeP4v+p1k
2018-04-15 12:08:30.9450 [27] Device #4 (CryptoNight): 312.83 h/s
2018-04-15 12:08:32.3982 [28] Device #4 (CryptoNight): 312.87 h/s
2018-04-15 12:08:32.6327 [30] Device #5 (CryptoNight): 233.17 h/s
2018-04-15 12:08:32.8515 [24] Device #2 (CryptoNight): 313.15 h/s
2018-04-15 12:08:33.0703 [25] Device #3 (CryptoNight): 313.05 h/s
2018-04-15 12:08:34.5392 [26] Device #3 (CryptoNight): 312.76 h/s
2018-04-15 12:08:34.8517 [20] Device #1 (CryptoNight): 204.03 h/s
2018-04-15 12:08:36.6175 [29] Device #5 (CryptoNight): 233.07 h/s
2018-04-15 12:08:37.1176 [23] Device #2 (CryptoNight): 312.95 h/s
2018-04-15 12:08:37.3832 [15] Device #0 (CryptoNight): 314.39 h/s
2018-04-15 12:08:39.1958 [18] Device #1 (CryptoNight): 204.69 h/s
2018-04-15 12:08:39.9929 [12] Received new job: jsmgDOPx8rfWIPsgJ38VnSjUWTLC
2018-04-15 12:08:41.6649 [13] Device #0 (CryptoNight): 313.93 h/s
2018-04-15 12:08:42.3993 [27] Device #4 (CryptoNight): 312.94 h/s
2018-04-15 12:08:43.8527 [28] Device #4 (CryptoNight): 312.89 h/s
2018-04-15 12:08:44.1652 [30] Device #5 (CryptoNight): 233.28 h/s
2018-04-15 12:08:44.3059 [24] Device #2 (CryptoNight): 313.11 h/s
2018-04-15 12:08:44.5245 [25] Device #3 (CryptoNight): 312.84 h/s
2018-04-15 12:08:45.8060 [20] Device #1 (CryptoNight): 203.61 h/s
2018-04-15 12:08:45.9935 [26] Device #3 (CryptoNight): 312.99 h/s
2018-04-15 12:08:48.1499 [29] Device #5 (CryptoNight): 233.15 h/s
2018-04-15 12:08:48.5719 [23] Device #2 (CryptoNight): 313.17 h/s
2018-04-15 12:08:48.7906 [15] Device #0 (CryptoNight): 314.39 h/s
2018-04-15 12:08:50.1971 [18] Device #1 (CryptoNight): 201.05 h/s
2018-04-15 12:08:53.0724 [13] Device #0 (CryptoNight): 314.13 h/s
2018-04-15 12:08:53.8538 [27] Device #4 (CryptoNight): 313.16 h/s
2018-04-15 12:08:55.3070 [28] Device #4 (CryptoNight): 312.56 h/s
2018-04-15 12:08:55.6820 [30] Device #5 (CryptoNight): 233.18 h/s
2018-04-15 12:08:55.7602 [24] Device #2 (CryptoNight): 313.05 h/s
2018-04-15 12:08:55.9790 [25] Device #3 (CryptoNight): 313.05 h/s
2018-04-15 12:08:56.8228 [20] Device #1 (CryptoNight): 204.13 h/s
2018-04-15 12:08:57.4478 [26] Device #3 (CryptoNight): 312.94 h/s
2018-04-15 12:08:59.3387 [12] Received new job: Hi8/9lxIV70LxkyOIzAEStfd5CJE
2018-04-15 12:08:59.6669 [29] Device #5 (CryptoNight): 233.20 h/s
2018-04-15 12:09:00.0263 [23] Device #2 (CryptoNight): 313.17 h/s
2018-04-15 12:09:00.1981 [15] Device #0 (CryptoNight): 314.19 h/s
2018-04-15 12:09:01.4014 [18] Device #1 (CryptoNight): 185.82 h/s
2018-04-15 12:09:04.4798 [13] Device #0 (CryptoNight): 314.01 h/s
2018-04-15 12:09:05.3080 [27] Device #4 (CryptoNight): 312.73 h/s
2018-04-15 12:09:06.7613 [28] Device #4 (CryptoNight): 312.97 h/s
2018-04-15 12:09:07.2146 [24] Device #2 (CryptoNight): 313.03 h/s
2018-04-15 12:09:07.2146 [30] Device #5 (CryptoNight): 233.37 h/s
2018-04-15 12:09:07.4177 [25] Device #3 (CryptoNight): 312.82 h/s
2018-04-15 12:09:08.0897 [20] Device #1 (CryptoNight): 203.76 h/s
2018-04-15 12:09:08.8866 [26] Device #3 (CryptoNight): 313.39 h/s
2018-04-15 12:09:11.1993 [29] Device #5 (CryptoNight): 233.09 h/s
2018-04-15 12:09:11.4806 [23] Device #2 (CryptoNight): 313.04 h/s
2018-04-15 12:09:11.5900 [15] Device #0 (CryptoNight): 314.68 h/s
2018-04-15 12:09:12.4494 [18] Device #1 (CryptoNight): 204.59 h/s
2018-04-15 12:09:15.9032 [13] Device #0 (CryptoNight): 314.03 h/s
2018-04-15 12:09:16.7624 [27] Device #4 (CryptoNight): 312.94 h/s
2018-04-15 12:09:18.2000 [28] Device #4 (CryptoNight): 313.06 h/s
2018-04-15 12:09:18.6688 [24] Device #2 (CryptoNight): 312.84 h/s
2018-04-15 12:09:18.7313 [30] Device #5 (CryptoNight): 233.20 h/s
2018-04-15 12:09:18.8721 [25] Device #3 (CryptoNight): 313.05 h/s
2018-04-15 12:09:19.0596 [20] Device #1 (CryptoNight): 204.34 h/s
2018-04-15 12:09:20.3410 [26] Device #3 (CryptoNight): 313.10 h/s
2018-04-15 12:09:22.7162 [29] Device #5 (CryptoNight): 233.04 h/s
2018-04-15 12:09:22.9194 [23] Device #2 (CryptoNight): 313.05 h/s
2018-04-15 12:09:22.9974 [15] Device #0 (CryptoNight): 314.22 h/s
2018-04-15 12:09:23.4037 [18] Device #1 (CryptoNight): 204.11 h/s
2018-04-15 12:09:27.3105 [13] Device #0 (CryptoNight): 313.87 h/s
2018-04-15 12:09:28.2168 [27] Device #4 (CryptoNight): 312.83 h/s
2018-04-15 12:09:29.6545 [28] Device #4 (CryptoNight): 312.84 h/s
2018-04-15 12:09:30.0295 [20] Device #1 (CryptoNight): 201.83 h/s
2018-04-15 12:09:30.1076 [24] Device #2 (CryptoNight): 313.12 h/s
2018-04-15 12:09:30.2638 [30] Device #5 (CryptoNight): 233.14 h/s
2018-04-15 12:09:30.3263 [25] Device #3 (CryptoNight): 313.07 h/s
2018-04-15 12:09:30.8576 [12] Received new job: ZSJ6cBIEgKNh1pJgzBdSFKM8ukj/
2018-04-15 12:09:31.7953 [26] Device #3 (CryptoNight): 312.99 h/s
2018-04-15 12:09:34.2487 [29] Device #5 (CryptoNight): 233.31 h/s
2018-04-15 12:09:34.3737 [23] Device #2 (CryptoNight): 312.94 h/s
2018-04-15 12:09:34.4049 [15] Device #0 (CryptoNight): 314.42 h/s
2018-04-15 12:09:34.4049 [18] Device #1 (CryptoNight): 204.42 h/s
2018-04-15 12:09:38.7179 [13] Device #0 (CryptoNight): 314.26 h/s
2018-04-15 12:09:39.6712 [27] Device #4 (CryptoNight): 312.94 h/s
2018-04-15 12:09:41.0150 [20] Device #1 (CryptoNight): 204.88 h/s
2018-04-15 12:09:41.1088 [28] Device #4 (CryptoNight): 312.91 h/s
2018-04-15 12:09:41.5620 [24] Device #2 (CryptoNight): 313.01 h/s
2018-04-15 12:09:41.7651 [25] Device #3 (CryptoNight): 313.05 h/s
2018-04-15 12:09:41.7964 [30] Device #5 (CryptoNight): 233.24 h/s
2018-04-15 12:09:43.2497 [26] Device #3 (CryptoNight): 312.94 h/s
2018-04-15 12:09:45.3604 [18] Device #1 (CryptoNight): 204.97 h/s
2018-04-15 12:09:45.7667 [29] Device #5 (CryptoNight): 233.07 h/s
2018-04-15 12:09:45.8136 [15] Device #0 (CryptoNight): 313.91 h/s
2018-04-15 12:09:45.8292 [23] Device #2 (CryptoNight): 313.05 h/s
2018-04-15 12:09:50.1265 [13] Device #0 (CryptoNight): 314.05 h/s
2018-04-15 12:09:51.1267 [27] Device #4 (CryptoNight): 313.17 h/s
2018-04-15 12:09:52.0174 [20] Device #1 (CryptoNight): 204.69 h/s
2018-04-15 12:09:52.5643 [28] Device #4 (CryptoNight): 312.84 h/s
2018-04-15 12:09:53.0175 [24] Device #2 (CryptoNight): 313.16 h/s
2018-04-15 12:09:53.2206 [25] Device #3 (CryptoNight): 312.94 h/s
2018-04-15 12:09:53.3144 [30] Device #5 (CryptoNight): 233.12 h/s
2018-04-15 12:09:54.6895 [26] Device #3 (CryptoNight): 312.98 h/s
2018-04-15 12:09:56.3616 [18] Device #1 (CryptoNight): 205.07 h/s
2018-04-15 12:09:57.2054 [15] Device #0 (CryptoNight): 314.06 h/s
2018-04-15 12:09:57.2836 [23] Device #2 (CryptoNight): 313.06 h/s
2018-04-15 12:09:57.3004 [29] Device #5 (CryptoNight): 233.15 h/s
2018-04-15 12:09:59.2056 [1] Stopping miners...
2018-04-15 12:10:01.2370 [1] Stopped miners.
/code] |
|
|
|
|
Never mind. Didn't factor in difficulty. duh!
|
|
|
|
|
I'd agree - sqlite can take a long time to update/load with many cards. json would be much faster, and data integrity isn't really a make or break so long as the user doesn't muck around in the json file.
|
|
|
|
|
Okay this is weird. Wondering if anyone else has experienced this. Have four rigs mining monero. Three have 2 card with ~1700 hashes each, get around 3500 shares every 30 minutes. The fourth rig has 6 rx470 at ~3600 hashes, but that one only shows ~1500 shares over 30 minutes. That's like 1/4 the of the shares the other three rigs do.
If run three instances of claymore with 2 cards each, my shares increase to nearly 5500 over 30 minutes for each of the three instances of two rx470 each - just ~1200 hashes a piece.
Why would running more cards produce fewer shares than running the fewer cards in more instances of claymore? I've been running these for a few months now - have no idea why...
|
|
|
|
How does one specify Cryptonight v7? I keep getting rejected shares as seems to be switching/selecting v3 and can't find documentation around designating version to use for a given pool: 2018-04-08 12:46:53.2386 [9] Built cryptonight program for Device #0.
2018-04-08 12:46:53.2386 [9] Build options: -O5 -IKernels -DWORKSIZE=8
2018-04-08 12:46:53.2386 [9] Switching to Monero Version 3
2018-04-08 12:46:54.8505 [19] Device #0 (CryptoNight): 420.74 h/s
2018-04-08 12:46:55.2617 [24] Device #1 (CryptoNight): 406.40 h/s
2018-04-08 12:46:55.3351 [23] Device #1 (CryptoNight): 406.35 h/s
2018-04-08 12:47:02.0377 [24] Device #1 submitted Share #0 to communitypool.stellite.cash as Se2xy7zgW....
2018-04-08 12:47:02.0377 [24] Device #1 submitted a share to communitypool.stellite.cash as Se2xy7zgW....
2018-04-08 12:47:02.2422 [20] Received new job: FkGgg0m47P7X598ydv/MJKX8iwYO
2018-04-08 12:47:02.4627 [20] Share #0 rejected: Low difficulty share Claymore's CryptoNote AMD GPU Miner v11.3 works via the -pow7 switch. |
|
|
|
|
You know what else would be great? Being able to adjust card overclocking while Gateless is running. Right now one must Pause mining, adjust and re-start. One feature I like about sgminer is the ability to define a range (auto-tune) for temp and fan speed. I'd like to see a range for gpu-engine and gpu-memory speeds, where if the card exceeds max temps when overclocked = true throttles the cards back to stock settings, thus lowering the gpu and memory speeds.
|
|
|
|
|
