Show Posts
|
Pages: [1] 2 3 »
|
i tried it but my hash went down to 26mh/s, ref above 20 doesn't make any change and 2200mhz gets 28mh/s as long as the ref is 20, i'm using the latest amd driver 21.2.3 could that be the cause of low hash?
Hi, did you flash a mod bios already? Or is it still an original bios?
|
|
|
i am using rx 580 samsung mem, my ref is 20 in amd memory tweaker and mem freq 2200mhz but i only get 28 mh/s, in the gpu pcie section in trm it shows 1:00.0 but in gpu-z it's pcie 2 is this normal?
Samsung memory usually can only be 2000mhz max, sometime can be 2050mhz. More than that, you will find a lot of error using hwinfo. Try this, set core clock to 1150, mem 2000, ref 30. And you will get 30+ mhs.
|
|
|
Wowww... That's pretty amazing. How could it be with RX580 8GB? rx 580 to 40Mh/s x7=280Mh/s 625wats Phoenix Miner 5.5c Windows/msvc - Release build ----------------------------------------------- OpenCL driver version: 21.1.1 Available GPUs for mining: GPU1: Radeon RX 580 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 36 CUs GPU2: Radeon RX 580 Series (pcie , OpenCL 2.0, 8 GB VRAM, 36 CUs GPU3: Radeon RX 580 Series (pcie 10), OpenCL 2.0, 8 GB VRAM, 36 CUs GPU4: Radeon RX 580 Series (pcie 12), OpenCL 2.0, 8 GB VRAM, 36 CUs GPU5: Radeon RX 580 Series (pcie 13), OpenCL 2.0, 8 GB VRAM, 36 CUs GPU6: Radeon RX 580 Series (pcie 14), OpenCL 2.0, 8 GB VRAM, 36 CUs GPU7: Radeon RX 580 Series (pcie 15), OpenCL 2.0, 8 GB VRAM, 36 CUs *** 0:03 *** 1/27 22:20 ************************************** Eth: Mining ETH on ssl://eu1.ethermine.org:5555 for 0:03 Eth: Accepted shares 14 (0 stales), rejected shares 0 (0 stales) Eth: Incorrect shares 4 (22.22%), est. stales percentage 0.00% Eth: Maximum difficulty of found share: 20.6 GH (!) Eth: Average speed (5 min): 279.670 MH/s Eth: Effective speed: 307.69 MH/s; at pool: 307.69 MH/s Eth: Estimated income: 20.68 USD/day Eth: New job #4a6bd6e9 from ssl://eu1.ethermine.org:5555; diff: 4000MH Eth speed: 279.704 MH/s, shares: 14/0/4, time: 0:03 GPUs: 1: 39.851 MH/s (3) 2: 39.920 MH/s (3) 3: 39.872 MH/s (1) 4: 39.992 MH/s (1/2) 5: 40.043 MH/s (2) 6: 39.991 MH/s (2/2) 7: 40.035 MH/s (2) Eth: New job #cd4c8264 from ssl://eu1.ethermine.org:5555; diff: 4000MH Eth speed: 279.744 MH/s, shares: 14/0/4, time: 0:03 GPUs: 1: 39.877 MH/s (3) 2: 39.939 MH/s (3) 3: 39.903 MH/s (1) 4: 39.957 MH/s (1/2) 5: 40.064 MH/s (2) 6: 39.984 MH/s (2/2) 7: 40.021 MH/s (2) Eth: New job #9d925a19 from ssl://eu1.ethermine.org:5555; diff: 4000MH
|
|
|
No, it doesn't. Good day does the miner support strap applies to cards? I dont want to bios mod them
|
|
|
how much have you set virtual mem? It is 65k.
|
|
|
Here comes 0.32g GPUSmaller release package (~4MB) Netcode fixes CN-Heavy/Tube/HVX optimization Automated last four greeks (now deprecated and lo longer logged) New warm-up phase
During the warmup (about 5min) the hashrate can be crazy, your vega can display 50 or 5000 h/s, that's normal (as least, expected). That's because all timings are tweaked during this time, so two hashes can be mined in a row, leading to a crazy number. That's cosmetical, during this time you mine normally and can find shares. If a bad share is found, that's a bug or GPU problem, the warum phase is not expected to produce bad shares. I tested it on my RX560 and after 5mn of crazy hashrates, i get my stable 527 h/s i got on 0.31, same for all my rigs. Hi, waited for 30 minutes, but still hasn't got the peak yet on my rx 580 8gb. https://ibb.co/kAODoz
|
|
|
dok. why miner after 4 min go on dev fee
V1.6.3 - Reorganised devfee mining, first mining is in the first 15 minutes, so to maintain the 0.85% fee, decreased devfee time from 1 minute to 55 seconds every 2 hours If you just want to test you can use the benchmarking in 1.6.5 this is 4 minut not 15 min. And i on-off 30-50 time on day. u use dev fee alwys start miner? i start miner 5 time in 1 hour and u use dev fee 4* in 1 hour? and i dont wont test in imaginar mininig. i test in real mining. Aha... finally somebody raised this problem. I got the same issue, somehow, devfee appear in 4 or 5 minutes after the miner started. So, if you quite often to switch to other coin, I really understand your frustration about this logic. I think doctor needs to check it... somehow, logic doesn't work as expected.
|
|
|
I already took a look and gave up. it's not just a fork of cn-v7, they completely changed the network protocol too. the changes are far more important than for Nicehash. it would be too complicated to handle both, and even themselves just made a webchain-only miner from xmrig but not one that handle all CN variations. i cannot afford time to handle two separate netcodes.
any feedback about cn-heavy hashrates of 0.32f ?
I tried on bittube it slightly increase hashrate about 5-10 h/s per card and no rejected shared which is good. Edit : the things need to take note is like Sx5000 said on some card it really difficult to reach peak hashrate, I need to fire GPU-Z over and over. Same as me about hard to reach the hashrate peak, should run gpu-z more than once. Very small increase on hashrate, it is about up to 5 h/s only on mine. Currently back to 0.32a.
|
|
|
No more, online is the 0.32ethat's the exact same as 0.32d, plus GPU fan/temp in JSON, and bad shares colored in red if > 0 seven releases in one day, two days to track the bug and two hours to add GPU fan/temp. Woow. Thanks all for all the tests you did Tested on my 570 4GB. Great release!!! Great temp and fan!!! No rejected share. Got same hashrate as 0.32a for bittube. Will roll out to 580 8GB rigs. Thanks JCE.
|
|
|
It looked Strange, JCE perf on Saber are close to Heavy (and to Haven) I re-uploaded a 3rd t version with some code of 0.32c back. New test on Ellesmere would be welcome again Seems that this 3rd version is same as first version. Still no good I think. Still with RX 570 4GB, Bittube, win 1709, driver 18.6.1, single thread, multi hash 928. 19:32:27 | Hashrate GPU Thread 4: 812.61 h/s - Total GPU 4: 812.61 h/s 19:32:27 | Hashrate GPU Thread 5: 809.39 h/s - Total GPU 5: 809.39 h/s 19:32:27 | Total: 4849.48 h/s - Max: 4849.48 h/s 19:32:39 | GPU 2 Thread 2 Lane 567 has found an invalid Share. 19:32:51 | GPU 0 Thread 0 Lane 646 has found an invalid Share. 19:33:29 | GPU 2 Thread 2 Lane 306 finds a Share, value 160003 19:33:29 | Accepted by the pool. 19:33:29 | GPU 5 Thread 5 Lane 408 finds a Share, value 160003 19:33:29 | Accepted by the pool. 19:34:07 | GPU 4 Thread 4 Lane 855 has found an invalid Share. 19:34:09 | Pool sends a new Job. 19:34:35 | GPU 2 Thread 2 Lane 372 finds a Share, value 160003 19:34:42 | Accepted by the pool. 19:34:42 | Pool sends a new Job. 19:35:01 | Pool sends a new Job. 19:35:07 | GPU 3 Thread 3 Lane 23 finds a Share, value 160003 19:35:07 | Accepted by the pool. 19:35:29 | Pool sends a new Job. 19:35:37 | GPU 4 Thread 4 Lane 788 has found an invalid Share. 19:35:48 | GPU 0 Thread 0 Lane 522 has found an invalid Share.
|
|
|
Using this latest test version on RX570 4GB, bittube, win 1709, driver 18.6.1, single thread, multi hash 944, now I got exactly same result/hashrate as 0.32a. No more issue with rejected shares. Haven't tried yet for heavy/cn-v7.
|
|
|
0.32t on Rx 570 4gb, bittube, using 18.5.1, winver 1709, lots of rejected shares, and my miner got banned by miner.rocks.
Backed to 0.32a and all is good.
Continue testing: The above testing was using multi hash 944. Tried to decrease multi hash to 864, still got rejected shares some times. Tried again to decrease multi hash to 832, still got rejected shares as well. Backed to 0.32a with multi hash 944 and all is good, no reject shares. 17:19:21 | Pool sg.bittube.miner.rocks:5555 17:19:21 | Currency Cryptonote 17:19:21 | Current pool Difficulty 160003 17:19:21 | Valid Shares found 3 17:19:21 | Total hashes 480009 17:19:21 | Miner uptime 0:02:40 17:19:21 | Effective net hashrate 3000.06 h/s 17:19:23 | Hashrate GPU Thread 0: 714.35 h/s - Total GPU 0: 714.35 h/s 17:19:23 | Hashrate GPU Thread 1: 719.15 h/s - Total GPU 1: 719.15 h/s 17:19:23 | Hashrate GPU Thread 2: 714.35 h/s - Total GPU 2: 714.35 h/s 17:19:23 | Hashrate GPU Thread 3: 719.15 h/s - Total GPU 3: 719.15 h/s 17:19:23 | Hashrate GPU Thread 4: 720.69 h/s - Total GPU 4: 720.69 h/s 17:19:23 | Hashrate GPU Thread 5: 719.15 h/s - Total GPU 5: 719.15 h/s 17:19:23 | Total: 4306.81 h/s - Max: 4308.57 h/s 17:19:30 | GPU 5 Thread 5 Lane 819 finds a Share, value 160003 17:19:30 | Rejected by the pool. 17:19:30 | Message from the pool: Low difficulty share 17:20:46 | GPU 2 Thread 2 Lane 794 finds a Share, value 160003 17:20:46 | Rejected by the pool. 17:20:46 | Message from the pool: Low difficulty share 17:21:03 | Pool sends a new Job. 17:21:12 | Pool sends a new Job. 17:21:30 | GPU 0 Thread 0 Lane 507 finds a Share, value 160003 17:21:31 | Accepted by the pool. 17:22:08 | GPU 4 Thread 4 Lane 351 finds a Share, value 160003 17:22:08 | Accepted by the pool.
|
|
|
0.32t on Rx 570 4gb, bittube, using 18.5.1, winver 1709, lots of rejected shares, and my miner got banned by miner.rocks.
Backed to 0.32a and all is good.
|
|
|
Thanks for reminder. Windows 10 1709 AMD Driver 18.3.4 GPU-Z v2.9.0
what settings did you run the test on? config for srb and jce. That can indicate performance diff too. With JCE, I use auto config for GPU, disabled CPU. And with SRB, I set intensity to 53 (default is 51 for 580 8gb).
|
|
|
hi all,
--no-cpu to disable cpu mining (manual or auto) and its reciprocal --no-gpu (but better use the cpu-only version in such case). thanks Unclwish for the reply.
ok i note the requests about gpu fan/temp, right, but i will add read-only features. it may be damaging to set voltage too high or fan too slow. that's a job for afterburner or overdriventool. but temp/fan read is useful and needed for watchdog.
jce is detected as trojan like every miner, but it contains no malicious code, really.
Nice! Yes, it's just read-only features. For me, I use overdriventool to do overclock and undervolt, it's ok. Thanks for your support. Also, just to inform if no one knows yet. Just like SRB, running GPU-Z after running JCE-Miner can trigger the hashrate higher. Here is the steps: 1. Run the miner until you see the miner receives first job from pool. 2. Wait until the console of GPU-Z appear, and then close it. 3. Now, press h to see your hashrate. Other thing, below the screen shot of the comparison between SRB and JCE Miner, using same pool, same Overdriventool setting. It is 8x HIS 580 8GB Hynix. Algo: bittube v2 JCE Miner is higher about 10-20 h/s /card. https://imgur.com/NfqsMj3You forgot to point Windows version, drivers version and GPU-Z version to work all of it... Thanks for reminder. Windows 10 1709 AMD Driver 18.3.4 GPU-Z v2.9.0
|
|
|
hi all,
--no-cpu to disable cpu mining (manual or auto) and its reciprocal --no-gpu (but better use the cpu-only version in such case). thanks Unclwish for the reply.
ok i note the requests about gpu fan/temp, right, but i will add read-only features. it may be damaging to set voltage too high or fan too slow. that's a job for afterburner or overdriventool. but temp/fan read is useful and needed for watchdog.
jce is detected as trojan like every miner, but it contains no malicious code, really.
Nice! Yes, it's just read-only features. For me, I use overdriventool to do overclock and undervolt, it's ok. Thanks for your support. Also, just to inform if no one knows yet. Just like SRB, running GPU-Z after running JCE-Miner can trigger the hashrate higher. Here is the steps: 1. Run the miner until you see the miner receives first job from pool. 2. Wait until the console of GPU-Z appear, and then close it. 3. Now, press h to see your hashrate. Other thing, below the screen shot of the comparison between SRB and JCE Miner, using same pool, same Overdriventool setting. It is 8x HIS 580 8GB Hynix. Algo: bittube v2 JCE Miner is higher about 10-20 h/s /card. https://imgur.com/NfqsMj3
|
|
|
Hi JCE-Miner,
Please help to add temp and fan speed for each GPU, that information really useful to make sure my GPU not too hot.
Thanks.
Agreed. It really helps us to monitor the GPU temperature and do next action. So far, I am very happy with JCE miner during trial on one of my rig. Will see for next 24 hours. If everything is good (hashrate, temperature, undervolt, overclock), I will switch my other 8 rigs to JCE miner. Just expect temp and fan speed information on the next release please.
|
|
|
V1.6.3 - More speed on Vega56 cards on every algo (probably on Vega64 and VegaFE too, i don't have them to test) - Added parameter --enableduplicategpuid (used in start.bat), that enables to use the same gpu id in gpu_conf multiple times - Removed useless kernels 3 and 4 - Removed useless CPU opencl support ... Don't copy new version of miner over old one, or if you do make sure you delete .srb files before running it!
Great update, dok. I am mining bittube. Vega56 increased minimum 30 h/s, some got 40 and 50 h/s. RX580 increased about 5-10 h/s. Need to monitor it within few hours to get it stable hashrate.
|
|
|
I used SBR 1.6.1
need help connect pools: tube.ingest.cryptoknight.cc:5632
I used algo ipbc messger Pool rejected result 0x00005CEB (wrong algo, use monero7 miner)
] use 1.6.2 "cryptonight_type" : "BitTubeV2", { "cryptonight_type" : "BitTubeV2", "intensity" : 62, "double_threads" : true, /* THERE ARE A LOT OF OPTIONS/PARAMETERS YOU CAN USE HERE */ /* YOU CAN FIND THEM IN THE README FILE */ } { "pools" : [ {"pool_use_tls" : true, "pool" : " tube.ingest.cryptoknight.cc:5632", "wallet" : "bxcEgao1WQ6GoMnU8CS89xSGasBnMxU77M7EgZkXMr8wgEpHU1woiLXAPJ7ja2pVbXWJ4M5ijchoJXc CgzSzAmLC1B7q2hgQz", "password" : "w=02", "location" : "europe"}, ] } [2018-07-05 10:47:12] ADL initialised successfully! [2018-07-05 10:47:12] Main pool: tube.ingest.cryptoknight.cc:5632 [2018-07-05 10:47:13] ERROR : Socket closed [2018-07-05 10:47:13] Connection to pool lost. Reconnecting in 10 seconds. [2018-07-05 10:47:23] ERROR : Socket closed [2018-07-05 10:47:23] Connection to pool lost. Reconnecting in 10 seconds. [2018-07-05 10:47:33] ERROR : Socket closed [2018-07-05 10:47:33] Connection to pool lost. Reconnecting in 10 seconds. [2018-07-05 10:47:43] ERROR : Socket closed [2018-07-05 10:47:43] Connection to pool lost. Reconnecting in 10 seconds. hi, set pool_use_tls = false
|
|
|
V1.6.2 - Added support for Italocoin new algo (from block 55.000) - Auto intensity for Vega cards improved, also managed to increase hashing speed on Vega cards for about ~1-1.5% (mainly on heavy algos) - If user uses non existing GPU id in gpu_conf, it will be ignored, no error will be thrown - Fixed miner crash when using a non AES capable CPU on some algos - Added Windows version and build in log - Added video driver version in log - Added info about CPU AES support in log - Statistics now shows number of stale shares that were accepted by pool - Added parameter 'min_rig_speed_duration' that can set period for 'min_rig_speed' parameter (minimum is 30 sec), default is 5 min
+ I finally bought a Vega 56 card, so in the next releases i will try to improve the performance for Vegas. For now a little speedup of about 1-1.5% is achieved, mainly on Heavy based algos (Heavy, Haven, Bittube, Italo)
+ If you use a non existant id in gpu_conf, it will now be ignored, only id's that exist in your system will be used
+ There was a bug in soft AES that caused miner crash on Stellite and Haven algos, this is now fixed
+ Added accepted stale shares number in statistics. It can't know the number of real accepted stale shares on pool side, but the logic is simple, if a new job is received, but the miner sends a result in the mean time that is for the previous job, and this share gets accepted by the pool, miner will treat this like an accepted stale share.
+ min_rig_speed_duration can set the time you want to check the average hashrate for 'min_rig_speed' parameter. Default is 5 min.
Nice job, dok. For heavy algo, I don't need to run twice with intensity 60 first, and then 56. It is good now since intensity 56.
|
|
|
|