Today there is a new release of lolMiner that will allow you to keep going on! Hello! Is there a way to speed up zombie mode? RAM/CPU overclocking, dual channel, nvme swap file etc. what else it depends on?
|
|
|
You will be able to run 4gb cards on eth using linux approx to the end of this year, but we are waiting for the prognpow right? So there will be some changes regarding those news And the 4gb cards at the end of the mining era on eth will be able to mine some other algo, so, I’m not worried at all I wish Mr @Claymore make best ProgPow miner )
|
|
|
@Claymore, something is happening with DevFee since DwarfPool is closed. How can you still mine with 4gb cards? I thought that dag was at least 3.51gb now? Unless you're using an OS other than Windows. I ran tests with different epoch numbers using -benchmark #epoch option. ETH on Windows 10 with 4 Gb card will die ~ in july
|
|
|
For C31: Anyone managed to get more than 1.2+ on Vega64? If yes, what clocks and timings? Thanks! could anyone please share settings for Vega64 on C31? Cannot get more than 1.05 (
|
|
|
dejvid98, no, I hate MSI AB  it's Claymore's config remember that Claymore will not affect this setting if AB is installed (even if not run)
|
|
|
Does anyone use gtx1660? How much mhs you can get? 26.5 -mclock +670 -powlim -35 -strap 1 (notice: powlim is negative)
|
|
|
there are many websites saying it's official, in fact they have epools.txt with lines filled. this one, for example: claymore-dual.github.io
|
|
|
The achieved values are currently between: 2300 - 2350 H/s per card @tweak-profile "10"
Total power consumption at: ~ 2410 watts (/ 12 = 200.83 watts per card) wow! this is really great! Thanks for settings. I had 17200 for 8 liquid cards, these settings give 18 650 and a little bit lower power consumption. Did anybody manage to get good hashes on Micron memory? I have ~1800 on MSI Air Vega 56 with SRB. TRM gives more, but it often stucks with no reaction.
|
|
|
That is rather odd and should definitely not be happening. I've read log files in detail and found relation: after one or more GPUs stops giving shares, "total table" stops appearing further. In below example GPU3 and GPU4 are lost, so the blue table is not shown anymore, but rig continues hashing without two GPUs until manual restart. I'm sure you can catch totals disappearing in code and react as GPU watchdog shoud. I could write external tool for log monitoring, but it's a hack. [2019-08-27 23:10:00] Pool xmr-eu1.nanopool.org share accepted. (GPU4) (a:47526 r:853) (139 ms) [2019-08-27 23:10:03] Pool xmr-eu1.nanopool.org share accepted. (GPU7) (a:47527 r:853) (133 ms) [2019-08-27 23:10:09] Pool xmr-eu1.nanopool.org share accepted. (GPU7) (a:47528 r:853) (151 ms) [2019-08-27 23:10:10] Stats Uptime: 4 days, 05:59:51 [2019-08-27 23:10:10] GPU 0 [59C, fan 13%] cnr: 2.036kh/s, avg 2.034kh/s, pool 1.940kh/s a:5937 r:116 hw:0 [2019-08-27 23:10:10] GPU 1 [60C, fan 15%] cnr: 2.038kh/s, avg 2.036kh/s, pool 1.949kh/s a:5964 r:98 hw:0 [2019-08-27 23:10:10] GPU 2 [59C, fan 13%] cnr: 2.040kh/s, avg 2.039kh/s, pool 1.945kh/s a:5950 r:95 hw:0 [2019-08-27 23:10:10] GPU 3 [59C, fan 14%] cnr: 2.022kh/s, avg 2.037kh/s, pool 1.940kh/s a:5937 r:123 hw:0 [2019-08-27 23:10:10] GPU 4 [58C, fan 13%] cnr: 2.039kh/s, avg 2.037kh/s, pool 1.954kh/s a:5980 r:99 hw:0 [2019-08-27 23:10:10] GPU 5 [60C, fan 16%] cnr: 2.019kh/s, avg 2.033kh/s, pool 1.953kh/s a:5975 r:114 hw:0 [2019-08-27 23:10:10] GPU 6 [58C, fan 13%] cnr: 2.016kh/s, avg 2.035kh/s, pool 1.899kh/s a:5810 r:109 hw:0 [2019-08-27 23:10:10] GPU 7 [59C, fan 13%] cnr: 2.036kh/s, avg 2.034kh/s, pool 1.953kh/s a:5975 r:99 hw:0 [2019-08-27 23:10:10] Total cnr: 16.25kh/s, avg 16.29kh/s, pool 15.53kh/s a:47528 r:853 hw:0 [2019-08-27 23:10:14] Pool xmr-eu1.nanopool.org share accepted. (GPU0) (a:47529 r:853) (265 ms) [2019-08-27 23:10:19] Pool xmr-eu1.nanopool.org share accepted. (GPU2) (a:47530 r:853) (201 ms) [2019-08-27 23:10:26] Pool xmr-eu1.nanopool.org share accepted. (GPU3) (a:47531 r:853) (219 ms) [2019-08-27 23:10:26] Pool xmr-eu1.nanopool.org share accepted. (GPU3) (a:47532 r:853) (127 ms) [2019-08-27 23:10:29] Pool xmr-eu1.nanopool.org share accepted. (GPU7) (a:47533 r:853) (131 ms) [2019-08-27 23:10:40] Stats Uptime: 4 days, 06:00:21 [2019-08-27 23:10:40] GPU 0 [59C, fan 14%] cnr: 2.036kh/s, avg 2.034kh/s, pool 1.940kh/s a:5938 r:116 hw:0 [2019-08-27 23:10:40] GPU 1 [60C, fan 15%] cnr: 2.039kh/s, avg 2.036kh/s, pool 1.949kh/s a:5964 r:98 hw:0 [2019-08-27 23:10:40] GPU 2 [60C, fan 14%] cnr: 2.040kh/s, avg 2.039kh/s, pool 1.945kh/s a:5951 r:95 hw:0 [2019-08-27 23:10:40] GPU 3 [59C, fan 13%] cnr: 2.026kh/s, avg 2.037kh/s, pool 1.941kh/s a:5939 r:123 hw:0 [2019-08-27 23:10:40] GPU 4 [60C, fan 12%] cnr: 2.039kh/s, avg 2.037kh/s, pool 1.954kh/s a:5980 r:99 hw:0 [2019-08-27 23:10:40] GPU 5 [59C, fan 16%] cnr: 2.020kh/s, avg 2.033kh/s, pool 1.953kh/s a:5975 r:114 hw:0 [2019-08-27 23:10:40] GPU 6 [61C, fan 13%] cnr: 2.015kh/s, avg 2.035kh/s, pool 1.899kh/s a:5810 r:109 hw:0 [2019-08-27 23:10:40] GPU 7 [59C, fan 14%] cnr: 2.036kh/s, avg 2.034kh/s, pool 1.953kh/s a:5976 r:99 hw:0 [2019-08-27 23:10:40] Total cnr: 16.25kh/s, avg 16.29kh/s, pool 15.53kh/s a:47533 r:853 hw:0 [2019-08-27 23:10:52] Pool xmr-eu1.nanopool.org share accepted. (GPU5) (a:47534 r:853) (134 ms) [2019-08-27 23:10:57] Pool xmr-eu1.nanopool.org received new job. (job_id: 9111) [2019-08-27 23:11:10] Stats Uptime: 4 days, 06:00:51 [2019-08-27 23:11:10] GPU 0 [59C, fan 13%] cnr: 2.036kh/s, avg 2.034kh/s, pool 1.940kh/s a:5938 r:116 hw:0 [2019-08-27 23:11:10] GPU 1 [57C, fan 15%] cnr: 2.038kh/s, avg 2.036kh/s, pool 1.949kh/s a:5964 r:98 hw:0 [2019-08-27 23:11:10] GPU 2 [59C, fan 14%] cnr: 2.040kh/s, avg 2.039kh/s, pool 1.945kh/s a:5951 r:95 hw:0 [2019-08-27 23:11:10] GPU 3 [59C, fan 14%] cnr: 2.024kh/s, avg 2.037kh/s, pool 1.941kh/s a:5939 r:123 hw:0 [2019-08-27 23:11:10] GPU 4 [60C, fan 13%] cnr: 2.039kh/s, avg 2.037kh/s, pool 1.954kh/s a:5980 r:99 hw:0 [2019-08-27 23:11:10] GPU 5 [59C, fan 16%] cnr: 2.021kh/s, avg 2.033kh/s, pool 1.953kh/s a:5976 r:114 hw:0 [2019-08-27 23:11:10] GPU 6 [61C, fan 14%] cnr: 2.016kh/s, avg 2.035kh/s, pool 1.899kh/s a:5810 r:109 hw:0 [2019-08-27 23:11:10] GPU 7 [59C, fan 15%] cnr: 2.036kh/s, avg 2.034kh/s, pool 1.953kh/s a:5976 r:99 hw:0 [2019-08-27 23:11:10] Total cnr: 16.25kh/s, avg 16.29kh/s, pool 15.53kh/s a:47534 r:853 hw:0 [2019-08-27 23:11:13] Pool xmr-eu1.nanopool.org share accepted. (GPU5) (a:47535 r:853) (178 ms) [2019-08-27 23:11:14] Pool xmr-eu1.nanopool.org share accepted. (GPU2) (a:47536 r:853) (194 ms) [2019-08-27 23:11:16] Pool xmr-eu1.nanopool.org share accepted. (GPU2) (a:47537 r:853) (139 ms) [2019-08-27 23:11:19] Pool xmr-eu1.nanopool.org share accepted. (GPU5) (a:47538 r:853) (127 ms) [2019-08-27 23:11:40] Stats Uptime: 4 days, 06:01:21 [2019-08-27 23:11:41] Pool xmr-eu1.nanopool.org share accepted. (GPU7) (a:47539 r:853) (132 ms) [2019-08-27 23:11:44] Pool xmr-eu1.nanopool.org share accepted. (GPU7) (a:47540 r:853) (214 ms) [2019-08-27 23:11:44] Pool xmr-eu1.nanopool.org share accepted. (GPU6) (a:47541 r:853) (174 ms) [2019-08-27 23:11:49] Pool xmr-eu1.nanopool.org share accepted. (GPU0) (a:47542 r:853) (155 ms) [2019-08-27 23:11:57] Pool xmr-eu1.nanopool.org received new job. (job_id: 9112) [2019-08-27 23:12:03] Pool xmr-eu1.nanopool.org share accepted. (GPU2) (a:47543 r:853) (168 ms) [2019-08-27 23:12:11] Pool xmr-eu1.nanopool.org share accepted. (GPU7) (a:47544 r:853) (203 ms) [2019-08-27 23:12:19] Pool xmr-eu1.nanopool.org share accepted. (GPU2) (a:47545 r:853) (150 ms) [2019-08-27 23:12:25] Pool xmr-eu1.nanopool.org share accepted. (GPU7) (a:47546 r:853) (179 ms) [2019-08-27 23:12:25] Pool xmr-eu1.nanopool.org share accepted. (GPU0) (a:47547 r:853) (222 ms) [2019-08-27 23:12:56] Pool xmr-eu1.nanopool.org share accepted. (GPU1) (a:47548 r:853) (167 ms) [2019-08-27 23:12:57] Pool xmr-eu1.nanopool.org received new job. (job_id: 9113) [2019-08-27 23:13:26] Pool xmr-eu1.nanopool.org share accepted. (GPU6) (a:47549 r:853) (149 ms) [2019-08-27 23:13:38] Pool xmr-eu1.nanopool.org share accepted. (GPU0) (a:47550 r:853) (180 ms) [2019-08-27 23:13:45] Pool xmr-eu1.nanopool.org share accepted. (GPU6) (a:47551 r:853) (136 ms) [2019-08-27 23:13:57] Pool xmr-eu1.nanopool.org received new job. (job_id: 9114) [2019-08-27 23:14:01] Pool xmr-eu1.nanopool.org share accepted. (GPU0) (a:47552 r:853) (169 ms) [2019-08-27 23:14:02] Pool xmr-eu1.nanopool.org share accepted. (GPU1) (a:47553 r:853) (129 ms) [2019-08-27 23:14:06] Pool xmr-eu1.nanopool.org share accepted. (GPU7) (a:47554 r:853) (127 ms) [2019-08-27 23:14:12] Pool xmr-eu1.nanopool.org share accepted. (GPU1) (a:47555 r:853) (180 ms) [2019-08-27 23:14:19] Pool xmr-eu1.nanopool.org share accepted. (GPU1) (a:47556 r:853) (128 ms) [2019-08-27 23:14:20] Pool xmr-eu1.nanopool.org share accepted. (GPU2) (a:47557 r:853) (168 ms) [2019-08-27 23:14:25] Pool xmr-eu1.nanopool.org share accepted. (GPU1) (a:47558 r:853) (146 ms) [2019-08-27 23:14:29] Pool xmr-eu1.nanopool.org share accepted. (GPU5) (a:47559 r:853) (151 ms) [2019-08-27 23:14:32] Pool xmr-eu1.nanopool.org share accepted. (GPU6) (a:47560 r:853) (155 ms) [2019-08-27 23:14:49] Pool xmr-eu1.nanopool.org share accepted. (GPU1) (a:47561 r:853) (128 ms) [2019-08-27 23:14:53] Pool xmr-eu1.nanopool.org share accepted. (GPU0) (a:47562 r:853) (188 ms) [2019-08-27 23:14:56] Pool xmr-eu1.nanopool.org share accepted. (GPU2) (a:47563 r:853) (142 ms) [2019-08-27 23:14:58] Pool xmr-eu1.nanopool.org received new job. (job_id: 9115) [2019-08-27 23:15:11] Pool xmr-eu1.nanopool.org share accepted. (GPU6) (a:47564 r:853) (158 ms) [2019-08-27 23:15:23] Pool xmr-eu1.nanopool.org received new job. (job_id: 9116) [2019-08-27 23:15:46] Pool xmr-eu1.nanopool.org share accepted. (GPU6) (a:47565 r:853) (135 ms) [2019-08-27 23:15:47] Pool xmr-eu1.nanopool.org share accepted. (GPU0) (a:47566 r:853) (159 ms)
|
|
|
That is rather odd and should definitely not be happening. Can you tell us a bit more about your setup? Which OS version are you using? What version drivers are you running? Which version of the miner are you running? Do the stats still display when you press 's' ? How do you know if it's just one GPU that crashes? 8 x Vega56 MSI Air (original bios, no software timing mods) Win10 LTSB, 18.6.1 drivers, latest 0.5.7 miner 's' shows only one string as in attached image. one gpu is just a guess. first it began rebooting with "GPU 6: detected DEAD" in log for the last two days. than began hanging like screened. if I reboot in manually, it works for serveral minutes, after that same behaviour again. rig power drops to ~370W. I realize that code is multi-thread, but it seems like it waits for something before giving them next jobs. txt log shows the same thing, nothing special. upd now I've disabled gpu6 using "-d" key - same result some time later  upd2 now another rig shows almost same picture. it has 8 Vega64 liquid. same OS, drivers and miner, same pool. maybe there's something connected to difficulty growth? 
|
|
|
Hello, @todxx ! If one card crashes, miner stops finding shares on all gpus, but continues getting jobs. is there a way to avoid this? 
|
|
|
Please add DAG epoch number in API responce. Yes. Please!!! And add best intensities found in auto tuning mode. @Claymore, if you really want to add all that, please add a choice of what to show in web interface - there's too much data already (
|
|
|
What could be the reason for this message?
"opencl error -4 cannot write buffer DAG" after that miner freezes and I have to restart the rig.
I have virtual memory set to 20+ gigs on 8 GPU rig
each card requires DAG size of memory (3+ Gb for ETH now) + some memory for Windows. you need up to 30 Gb swap
|
|
|
Hello! Is there a way to connect to pools via external proxy/socks?
|
|
|
@Claymore, -logfile logs\ -logsmaxsize 100 combination is not working still in 14.6. Miner doesn't clean logs folder different from root
|
|
|
I'm still dualmining ETH+ZIL, it should work in a different way. Once per 2-3 hours ETH miner stops and ZIL miner digs for Ziliqa blockchain during several minutes. Link above cannot show ZIL miners on ETH blockhain.
|
|
|
can i combine the new -rxboost Option with the included Straps like: -rxboost 1 -straps 1 yes, it works for me Is anyone getting lots of hashrate bounces? I got bouncing with new kernels on version 10, so I'm still using -oldkernels since that, hashrate seems to be much more stable using it
|
|
|
wow, really 5% increased...
didn't get how to use -install key. rigs with old blockchain drivers ignore -install, -strap and -rxboost options. it works only after manual driver update.
|
|
|
|