Ninjastic
Search content
Sort by
Showing 20 of 168 results by lebuawu2
Post
Topic
Board Mining (Altcoins)
Re: [ANN] TeamRedMiner 0.6.0 - Ethash/Cryptonight/Chukwa Thread
by
lebuawu2
on 29/11/2019, 02:15:18 UTC
Quote from: keksik on November 28, 2019, 08:39:22 PM
im using Claymore 15 and mining eth. reported hash is 825.9 and average 6hours is only 727,6mhs.

going to try TRM 0.6.0, curious about results.

I also feel the same with you, I tried both Claymore and PM both of them showing pool side (ethermine) more lower than in the miner(after deducted fee from miner and pool side).

will wait for your review after you try TRM.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] TeamRedMiner 0.6.0 - Ethash/Cryptonight/Chukwa Thread
by
lebuawu2
on 29/11/2019, 02:10:14 UTC
Quote from: kerney666 on November 28, 2019, 08:10:23 AM
Quote from: dingdongtobias on November 28, 2019, 07:14:14 AM
advertizing own work by spit on other dev's work is not the way to win!!!!
understand you late in the eth game so want to make atenttion in dirty way
Well, you're always a bit of a troll and probably some alias account for someone else, posting obscene posts removed by moderators in this thread, I know that, but I agree with both you and joblo, this can REALLY look that way. It's all about if I'm correct or not, isn't it?

lol advertizing and pointing the fact (we need to check of course) in his own thread should be ok, dingdongtobias is just die hard SRB which don't like with your miner because someone advertise TRM miner in SRB thread.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] TeamRedMiner 0.6.0 - Ethash/Cryptonight/Chukwa Thread
by
lebuawu2
on 29/11/2019, 02:05:10 UTC
Quote from: kerney666 on November 25, 2019, 10:51:37 AM
Quote from: lebuawu2 on November 25, 2019, 09:29:12 AM
Hi,

can someone share hashrate and power consumption comparison for Polaris card (RX 580 8GB) between TRM, PM, Claymore with the same setting (Core Clock, Mem Clock, Other Tweak) ?

Thanks.

We will shortly release a Ethash miner testing tool, it's just a simple open source node.js project. You will be able to run controlled long-running tests on all miners. The reason this is important is that the displayed hashrates of Claymore and Phoenix are just bullshit. They both add +1.5% or more of fake hashrate. I don't ask anyone to buy these claims without being able to verify it themselves though, which is why we'll release the tool (which acts as a low diff fake pool with a static epoch and controlled job update mechanism) and everyone can see for themselves if they are willing to mine air for ~24h. To verify that we're not insane, we've also reverse engineered both miners, analysed their kernels, traced their OpenCL enqueue calls, and the evidence is clear.

Plenty of people have already pointed this out just by logging all shares over time, but it's really hard to prove anything. You need controlled runs of (preferably) 1 million shares, which is more or less impossible without controlling the environment properly. Another simple way is just to find a big farm from e.g. the frontpage of ethermine.org (found blocks) and check the difference between their reported and accepted hashrate.

Here is one example: https://ethermine.org/miners/6F714AaAAF72977267601cC1cADC49fb3966Ff89/dashboard

Reported: 3.206 TH/s, Accepted: 3.111 TH/s, difference -2.97%. I'm fairly certain this is Phoenix miner. Why do we have a diff of -3%? The dev fee is 0.65%, and there are 1% stale shares, and this is a HUGE sample set that should converge nicely. Contrary to what people seem to believe, the additional -1.35% just should _not_ disappear. For comparison, here is a run using our soon-to-be-released testing tool for 247k shares on Phoenix 4.7c:

Code:
Hashrates for 1 active connections:
    Global hashrate: 228.51 MH/s vs 235.43 MH/s avg reported [diff -2.94%] (A247366:S1575:R0 shares, 93582 secs)
    Global stats: 99.37% acc, 0.63% stale, 0% rej.
    [1] hashrate:  228.51 MH/s vs 235.43 MH/s avg reported [diff -2.94%] (A247366:S1575:R0 shares, 93582 secs)

Look at that, a diff of -2.94% between the reported and accepted hashrate, what a coincidence? To be fair though, 247k shares is only good for a +-0.5% estimate at 99% confidence, so we must treat the value accordingly. The point is that neither CM nor PM can never ever produce a poolside hashrate over time that matches their displayed hashrates.

Sorry for a long rant to your simple question, the bigger point I'm trying to make is this: unless miners start accepting that CM and PM are bullshitting their displayed hashrates, "comparing" CM/PM/TRM/Ethminer is pointless, you'll just be stating that CM and PM are much better than what they really are.


Hi Kerney,

I agree with you, hash rate displayed in the miner is just number, we need to verify in the pool side. I just want to get rough estimation base on hashrate in the miner, because it will be easy rather than wait 24h in pool side.

Thanks.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] TeamRedMiner 0.6.0 - Ethash/Cryptonight/Chukwa Thread
by
lebuawu2
on 25/11/2019, 09:29:12 UTC
Hi,

can someone share hashrate and power consumption comparison for Polaris card (RX 580 8GB) between TRM, PM, Claymore with the same setting (Core Clock, Mem Clock, Other Tweak) ?

Thanks.
Post
Topic
Board Mining (Altcoins)
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v14.7 (Windows/Linux)
by
lebuawu2
on 30/06/2019, 02:55:36 UTC
Quote from: Xavieras on June 29, 2019, 01:46:53 PM
I have almost same problem. My rig was worked fine about 1week. Later something went wrong... I started search why my pc don't see only 6gpu of 7. Started to check cables, and found that cable which goes from psu to riser burned one contactor of six. Ok I thought maybe it's because I using cable for more then one year. I plug it to other psu place and turned on with -starp 1. Again my rig started work well but only about one hour and again it started to restart and again one gpu lost. Again checked cable and again same problem. Then I tried again to change in psu cable place and turned on rig without -strap function and currently everything is ok. I am not sure but I think something not so good with that -strap function. My rig working on two psu  which is corsair RM850X. Have someone same issue?

Thank a lot!

I got the same issue, the problem because I connected 3 GPU riser to one cable sata from PSU.
maximum should be only 2 GPU.
Post
Topic
Board Mining (Altcoins)
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v14.7 (Windows/Linux)
by
lebuawu2
on 30/06/2019, 02:47:30 UTC
Quote from: ManDoneKTM on June 29, 2019, 09:05:18 PM
i found a bug in your miner ...  https://imgur.com/a/k5Nw9k3 and he still staying like this , i have to go to the rig and reset manually ...

if one of your GPU dead better you restart windows rather than restart only miner.

what is your setting for your 580 to get 34 mh/s? memory type, cclock, mclock ?
Post
Topic
Board Mining (Bahasa Indonesia)
Topic OP
Setting optimal Rig dengan linux Debian / Ubuntu?
by
lebuawu2
on 19/06/2019, 05:10:45 UTC
Hi agan2,

saya beberapa hari ini mencoba untuk setting rig menggunakan linux Debian 9.9.
tapi kalau di compare dengan Hive OS hashrate-nya masih jauh sekali untuk algoritma CN-Haven dan CNR.

konfigurasi yang saya lakukan di Debian 9.9 berdasarkan link berikut : https://www.amd.com/en/support/kb/release-notes/rn-radpro-lin-mining-beta
install AMDGPU-PRO Beta Mining Driver 17.40 dan Enabling Large Page (amdgpu.vm_fragment_size=9).

mohon pencerahan suhu2 disini kira2 harus di setting apa lagi ya supaya bisa mendekati hashrate Hive OS?

sebagai komparasi untuk hashrate GPU RX 580 8GB Hynix dengan cclock 1250 mclock 2100 menggunakan miner TeamRedMiner 0.5.2 dengan config 16+14:AAA.

Hive OS CN-Haven 1220 h/s, CNR 930 h/s.
Debian CN-Haven 940 h/s, CNR 860 h/s.

Thanks.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] TeamRedMiner 0.5.2 - Cryptonight Thread - High hashrate, Low Power
by
lebuawu2
on 17/06/2019, 11:47:09 UTC
Hi,

I new to linux, currently I tried Debian 9.9 and installed opencl-amdgpu-pro.
GPU RX 580 8GB algo CN-Haven with cclock 1250 mclock 2100 only got 464 h/s. VDDC also keep showing 0.0 mV.
Windows with the same cclock and mclock I got more than 1200 h/s.

Please help how I can achieve more than 1200 h/s in linux.



Thanks.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] TeamRedMiner 0.5.1 - Cryptonight Thread - High hashrate, Low Power
by
lebuawu2
on 14/06/2019, 00:31:13 UTC
Quote from: kerney666 on June 13, 2019, 04:06:15 PM

Well, it should really only happen when we restart our servers, which isn't often at all. So, there's something else cutting the connection for you. In some cases there are home routers that cut connections, in other cases many countries/jurisdictions don't like neither SSL traffic nor mining traffic. May I ask where you're located? You can PM me if you want to. Also, I'd love to know what version of TRM you're running? We have noticed a higher degree of short-lived inbound connections lately, but can't explain why.


Hi Kerney,

I already PM you, please check your message.

Thanks.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] TeamRedMiner 0.5.1 - Cryptonight Thread - High hashrate, Low Power
by
lebuawu2
on 13/06/2019, 13:41:48 UTC
Hi Dev,

Why I often got this message :
Quote
Dev pool connection was closed due to an error.
Mining will proceed at reduced rate while not connected to dev pool.

but after sometime it will connect to dev pool :
Quote
Dev pool connected and ready.

is there any solution for this message?



Thanks.
Post
Topic
Board Mining (Altcoins)
Re: PhoenixMiner 4.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
by
lebuawu2
on 31/05/2019, 11:04:01 UTC
Quote from: laik2 on May 30, 2019, 05:07:20 PM
Quote from: justoiurii on May 30, 2019, 04:45:49 PM
After Claymore last ver. 14.6 you are not the fastest eth miner. I've got 32,3 mh/sec vs 31,5 with phoenix (RX480, bc drivers ). Your next pace, dev)
Phoenix linux:
Quote
GPU2:  PCI 0000:03:00, Radeon RX 580 8 GB - BIOS: 113-BE366EU-Z46, MEMINFO: SK Hynix H5GQ8H24MJR
GFXCLK: 1239Mhz, DPM: 3, MEMCLK: 2250Mhz, PWR:84W, VLT: 0.86v, FAN: 40%, GPU TEMP: 53C, ASIC TEMP: 56C
Quote
GPUs: 1: 31.264 MH/s (174) 2: 31.489 MH/s (153) 3: 33.678 MH/s (181) 4: 31.826 MH/s (197)
Claymore linux:
Quote
GPU2:  PCI 0000:03:00, Radeon RX 580 8 GB - BIOS: 113-BE366EU-Z46, MEMINFO: SK Hynix H5GQ8H24MJR
GFXCLK: 1239Mhz, DPM: 3, MEMCLK: 2250Mhz, PWR:85W, VLT: 0.86v, FAN: 40%, GPU TEMP: 54C, ASIC TEMP: 57C
Quote
ETH: GPU0 30.479 Mh/s, GPU1 30.595 Mh/s, GPU2 33.614 Mh/s, GPU3 31.638 Mh/s
Are you still sure Claymore is faster?


did you use RX Boost in Phoenix and Claymore?
Post
Topic
Board Mining (Altcoins)
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v14.6 (Windows/Linux)
by
lebuawu2
on 28/05/2019, 21:47:15 UTC
Quote from: darkCryptoMiner on May 28, 2019, 07:52:43 PM
On my asrock h110, win10 home, 8x rx580 nitro+ 8gb I am running the following config for 14.6

cclock 1150, mclock 2200, cvddc 850 mvddc 875 rxboost 1

The above works correctly and go from 30.5mh to 31.5mh

Trying the straps 0,1...7 @2200 just crashes the rig

They are all hynix except 1 is micron

Any suggestions on what to try to stop the crashing?

I.tried just strap 1,with the same crashing

if you said without strap you already got 31.5mh then I believe you already flashed your bios.
in order to use strap you need to restore to original bios.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] TeamRedMiner 0.3.8 - CNv8 - Vega 64 2200+h/s Rx470 1025+h/s Low Power Draw
by
lebuawu2
on 23/01/2019, 09:52:29 UTC
Hi TRM,

any plan to support MTP algorithm?

Thanks.
Post
Topic
Board Mining (Altcoins)
Re: [JCE]Fast & stable CN/v8/Heavy/Tube/XHV miner, CPU+GPU, Vega56 1800+ RX580 1200+
by
lebuawu2
on 05/01/2019, 16:29:40 UTC
Hi JCE,

most likely ETH will switch to ProgPow, so are you planning to support ProgPow in your miner?

Thanks.
Post
Topic
Board Mining (Altcoins)
Re: [JCE] Fast & stable CN-Heavy/Tube/XHV miner, low power, Vega56 1750+h/s
by
lebuawu2
on 05/12/2018, 09:00:39 UTC
Quote from: GrayCatt on December 05, 2018, 07:53:15 AM
Quote from: JCE-Miner on December 04, 2018, 11:04:15 PM
I'm wondering if that idea to enable Intel by default was a good one... it caused a lot of troubles, and despite it's explained in the doc, nobody read it.

May be, just add a BIG RED WARNING at the start of the miner if any Intel is detected?


just want to give another solution by adding another parameter like --ignore-igpu then it will work with old config.
Post
Topic
Board Mining (Altcoins)
Re: [JCE] Fast & stable CN-Heavy/Tube/XHV miner, low power, Vega56 1750+h/s
by
lebuawu2
on 05/12/2018, 08:59:07 UTC
Quote from: HardKano on December 05, 2018, 02:12:23 AM
WOW JCE !

From 032q to 033b7 here is the diff in the hashrate stats :

RIG1 (6x RX580 8gb gigabyte) : 6400 to 6900 !!!
RIG2 (6x RX580 8gb sapphire) : 6700 to 7300 !!!

I use 2 thread with 880 multi hash each thread.


multi_hash 944 should be better result.
Post
Topic
Board Mining (Altcoins)
Re: [JCE] Ultrafast CN-Heavy/Tube/XHV miner, low power, Vega56 1750+h/s
by
lebuawu2
on 04/12/2018, 09:38:55 UTC
Quote from: UnclWish on December 04, 2018, 09:28:30 AM
Quote from: lebuawu2 on December 04, 2018, 09:19:57 AM
Quote from: UnclWish on December 04, 2018, 08:00:33 AM
Quote from: lebuawu2 on December 04, 2018, 06:09:25 AM
Hi UnclWish,

I already explain even without warm up my rig with 8 GPU RX 580 8GB on first print hash rate it already reach max on all GPU.

Windows 10 Build 1709
AMD Driver 18.6.1
2 thread multi_hash 944

Maybe in your case because you have latest Windows 10 and latest AMD Driver.
Maybe you're right. I have 1803 Windows 10 and 18.11.2 drivers... Still playing with GPU voltages to check...

Or maybe your cards have good samsung memory... Or maybe your memory straps better than my...
What memory type and clocks/voltages you use? What memory straps?

JCE, can drivers affect that way?

2 samsung memory (GPU 1 & GPU 7) CC 1250/890 MC 2000/890 and 6 hynix memory (the rest), GPU 4 is really bad can only set CC 1250/890 MC 2020/890 GPU 2,3,5,6 CC 1250/890 MC 2100/890 GPU 8 CC 1250/890 MC 2080/890.

samsung memory strap from PBE 1.6.7.
hynix memory strap from doktor83.
Thanks for info. You use high memory voltage - 890 mV... I use 825-850 mV for clocks near 2000MHz...
Can you share your hynix memory strap from doctor83?

you can get from doktor83 thread here :
https://bitcointalk.org/index.php?topic=3167363.msg35676403#msg35676403
Post
Topic
Board Mining (Altcoins)
Re: [JCE] Ultrafast CN-Heavy/Tube/XHV miner, low power, Vega56 1750+h/s
by
lebuawu2
on 04/12/2018, 09:19:57 UTC
Quote from: UnclWish on December 04, 2018, 08:00:33 AM
Quote from: lebuawu2 on December 04, 2018, 06:09:25 AM
Hi UnclWish,

I already explain even without warm up my rig with 8 GPU RX 580 8GB on first print hash rate it already reach max on all GPU.

Windows 10 Build 1709
AMD Driver 18.6.1
2 thread multi_hash 944

Maybe in your case because you have latest Windows 10 and latest AMD Driver.
Maybe you're right. I have 1803 Windows 10 and 18.11.2 drivers... Still playing with GPU voltages to check...

Or maybe your cards have good samsung memory... Or maybe your memory straps better than my...
What memory type and clocks/voltages you use? What memory straps?

JCE, can drivers affect that way?

2 samsung memory (GPU 1 & GPU 7) CC 1250/890 MC 2000/890 and 6 hynix memory (the rest), GPU 4 is really bad can only set CC 1250/890 MC 2020/890 GPU 2,3,5,6 CC 1250/890 MC 2100/890 GPU 8 CC 1250/890 MC 2080/890.

samsung memory strap from PBE 1.6.7.
hynix memory strap from doktor83.
Post
Topic
Board Mining (Altcoins)
Re: [JCE] Ultrafast CN-Heavy/Tube/XHV miner, low power, Vega56 1750+h/s
by
lebuawu2
on 04/12/2018, 06:09:25 UTC
Quote from: UnclWish on December 04, 2018, 04:53:21 AM
Quote from: JCE-Miner on December 03, 2018, 10:10:30 PM
@Unclwish: did at least the -sync solved your problem of stuck thread?

Quote
JCE, b5+ to sync versions requires more power than b4 version
yes, measured +20% speed and +6% power on RX. Still a good deal Wink

Strange question from myself: i just plugged back my HD6950 that hasn't mined (except for quick tests) since the golden age of Claymore 9.7 and so far i cannot use multi_hash over 256 (=512Mb), while i got report from GitHub support tickets the value 864 was good. Did somebody managed to allocate >512M on those cards? I'm still using the drivers 15.11 on win8.1 i used with the card it replaced (a 7900), not tried yet to use the recommended 14.4
Yes, thread stuck bug is gone. Now trying to undestand why my RX 580 cards didn't have stable speed long time...

On old cards. Maybe my 270X 4Gb with availible only 3,5Gb for OpenCL can use all 4Gb somehow?

Who allready have good tests of sync version - please say what time need to recieve max speed on RX 580 8Gb. I want to spend some tests, but I need to know how much to wait every time...

1st try - rise a bit voltage on GPU cores - 12 minutes - no result - speed not max...
Hi UnclWish,

I already explain even without warm up my rig with 8 GPU RX 580 8GB on first print hash rate it already reach max on all GPU.

Windows 10 Build 1709
AMD Driver 18.6.1
2 thread multi_hash 944

Maybe in your case because you have latest Windows 10 and latest AMD Driver.

Code:
              +-----------------------------------------------+
              | JC Expert Cryptonote CPU+GPU Miner 0.33b-sync |
              +-----------------------------------------------+


For Windows 64-bits
Detecting OpenCL-capable GPUs...
Found GPU 0, with:
  Vendor:                       Intel
  Processor: Intel(R) HD Graphics 510
  Device:                       ff:ff
  Compute-Units:                   12
  Cache Memory:                256 KB
  Local Memory:                 64 KB
  Global Memory:              3139 MB
  Addressing:                 64-bits
Found GPU 1, with:
  Vendor:                         AMD
  Processor:                Ellesmere
  Device:                       01:00
  Compute-Units:                   36
  Cache Memory:                 16 KB
  Local Memory:                 32 KB
  Global Memory:              8192 MB
  Addressing:                 64-bits
Found GPU 2, with:
  Vendor:                         AMD
  Processor:                Ellesmere
  Device:                       02:00
  Compute-Units:                   36
  Cache Memory:                 16 KB
  Local Memory:                 32 KB
  Global Memory:              8192 MB
  Addressing:                 64-bits
Found GPU 3, with:
  Vendor:                         AMD
  Processor:                Ellesmere
  Device:                       03:00
  Compute-Units:                   36
  Cache Memory:                 16 KB
  Local Memory:                 32 KB
  Global Memory:              8192 MB
  Addressing:                 64-bits
Found GPU 4, with:
  Vendor:                         AMD
  Processor:                Ellesmere
  Device:                       04:00
  Compute-Units:                   36
  Cache Memory:                 16 KB
  Local Memory:                 32 KB
  Global Memory:              8192 MB
  Addressing:                 64-bits
Found GPU 5, with:
  Vendor:                         AMD
  Processor:                Ellesmere
  Device:                       05:00
  Compute-Units:                   36
  Cache Memory:                 16 KB
  Local Memory:                 32 KB
  Global Memory:              8192 MB
  Addressing:                 64-bits
Found GPU 6, with:
  Vendor:                         AMD
  Processor:                Ellesmere
  Device:                       06:00
  Compute-Units:                   36
  Cache Memory:                 16 KB
  Local Memory:                 32 KB
  Global Memory:              8192 MB
  Addressing:                 64-bits
Found GPU 7, with:
  Vendor:                         AMD
  Processor:                Ellesmere
  Device:                       09:00
  Compute-Units:                   36
  Cache Memory:                 16 KB
  Local Memory:                 32 KB
  Global Memory:              8192 MB
  Addressing:                 64-bits
Found GPU 8, with:
  Vendor:                         AMD
  Processor:                Ellesmere
  Device:                       0b:00
  Compute-Units:                   36
  Cache Memory:                 16 KB
  Local Memory:                 32 KB
  Global Memory:              8192 MB
  Addressing:                 64-bits

Preparing 16 Mining Threads...

+-- Thread 0 config ------------------------+
| Run on GPU:                     1         |
| Multi-hash:                   944         |
| Worksize:                       8         |
| Factor Alpha                   64         |
| Factor Beta                    16         |
+-------------------------------------------+

+-- Thread 1 config ------------------------+
| Run on GPU:                     1         |
| Multi-hash:                   944         |
| Worksize:                       8         |
| Factor Alpha                   64         |
| Factor Beta                    16         |
+-------------------------------------------+

+-- Thread 2 config ------------------------+
| Run on GPU:                     2         |
| Multi-hash:                   944         |
| Worksize:                       8         |
| Factor Alpha                   64         |
| Factor Beta                    16         |
+-------------------------------------------+

+-- Thread 3 config ------------------------+
| Run on GPU:                     2         |
| Multi-hash:                   944         |
| Worksize:                       8         |
| Factor Alpha                   64         |
| Factor Beta                    16         |
+-------------------------------------------+

+-- Thread 4 config ------------------------+
| Run on GPU:                     3         |
| Multi-hash:                   944         |
| Worksize:                       8         |
| Factor Alpha                   64         |
| Factor Beta                    16         |
+-------------------------------------------+

+-- Thread 5 config ------------------------+
| Run on GPU:                     3         |
| Multi-hash:                   944         |
| Worksize:                       8         |
| Factor Alpha                   64         |
| Factor Beta                    16         |
+-------------------------------------------+

+-- Thread 6 config ------------------------+
| Run on GPU:                     4         |
| Multi-hash:                   944         |
| Worksize:                       8         |
| Factor Alpha                   64         |
| Factor Beta                    16         |
+-------------------------------------------+

+-- Thread 7 config ------------------------+
| Run on GPU:                     4         |
| Multi-hash:                   944         |
| Worksize:                       8         |
| Factor Alpha                   64         |
| Factor Beta                    16         |
+-------------------------------------------+

+-- Thread 8 config ------------------------+
| Run on GPU:                     5         |
| Multi-hash:                   944         |
| Worksize:                       8         |
| Factor Alpha                   64         |
| Factor Beta                    16         |
+-------------------------------------------+

+-- Thread 9 config ------------------------+
| Run on GPU:                     5         |
| Multi-hash:                   944         |
| Worksize:                       8         |
| Factor Alpha                   64         |
| Factor Beta                    16         |
+-------------------------------------------+

+-- Thread 10 config -----------------------+
| Run on GPU:                     6         |
| Multi-hash:                   944         |
| Worksize:                       8         |
| Factor Alpha                   64         |
| Factor Beta                    16         |
+-------------------------------------------+

+-- Thread 11 config -----------------------+
| Run on GPU:                     6         |
| Multi-hash:                   944         |
| Worksize:                       8         |
| Factor Alpha                   64         |
| Factor Beta                    16         |
+-------------------------------------------+

+-- Thread 12 config -----------------------+
| Run on GPU:                     7         |
| Multi-hash:                   944         |
| Worksize:                       8         |
| Factor Alpha                   64         |
| Factor Beta                    16         |
+-------------------------------------------+

+-- Thread 13 config -----------------------+
| Run on GPU:                     7         |
| Multi-hash:                   944         |
| Worksize:                       8         |
| Factor Alpha                   64         |
| Factor Beta                    16         |
+-------------------------------------------+

+-- Thread 14 config -----------------------+
| Run on GPU:                     8         |
| Multi-hash:                   944         |
| Worksize:                       8         |
| Factor Alpha                   64         |
| Factor Beta                    16         |
+-------------------------------------------+

+-- Thread 15 config -----------------------+
| Run on GPU:                     8         |
| Multi-hash:                   944         |
| Worksize:                       8         |
| Factor Alpha                   64         |
| Factor Beta                    16         |
+-------------------------------------------+

Cryptonight Variation: Cryptonight-Heavy


Starting GPU Thread 0, on GPU 1
Created OpenCL Context for GPU 1 at 0000023faf34c790
Created OpenCL Thread 0 Command-Queue for GPU 1 at 0000023faf34c8f0
Scratchpad Allocation success for OpenCL Thread 0
Allocating big 3776MB scratchpad for OpenCL Thread 0...
Compiling kernels of OpenCL Thread 0...
Kernels of OpenCL Thread 0 compiled.

Starting GPU Thread 1, on GPU 1
Created OpenCL Thread 1 Command-Queue for GPU 1 at 0000023faf4ea5f0
Scratchpad Allocation success for OpenCL Thread 1
Allocating big 3776MB scratchpad for OpenCL Thread 1...
Compiling kernels of OpenCL Thread 1...
Kernels of OpenCL Thread 1 compiled.

Starting GPU Thread 2, on GPU 2
Created OpenCL Context for GPU 2 at 0000023faf12cbc0
Created OpenCL Thread 2 Command-Queue for GPU 2 at 0000023fb404a6e0
Scratchpad Allocation success for OpenCL Thread 2
Allocating big 3776MB scratchpad for OpenCL Thread 2...
Compiling kernels of OpenCL Thread 2...
Kernels of OpenCL Thread 2 compiled.

Starting GPU Thread 3, on GPU 2
Created OpenCL Thread 3 Command-Queue for GPU 2 at 0000023fb404a980
Scratchpad Allocation success for OpenCL Thread 3
Allocating big 3776MB scratchpad for OpenCL Thread 3...
Compiling kernels of OpenCL Thread 3...
Kernels of OpenCL Thread 3 compiled.

Starting GPU Thread 4, on GPU 3
Created OpenCL Context for GPU 3 at 0000023fb3ff6820
Created OpenCL Thread 4 Command-Queue for GPU 3 at 0000023fb404ac20
Scratchpad Allocation success for OpenCL Thread 4
Allocating big 3776MB scratchpad for OpenCL Thread 4...
Compiling kernels of OpenCL Thread 4...
Kernels of OpenCL Thread 4 compiled.

Starting GPU Thread 5, on GPU 3
Created OpenCL Thread 5 Command-Queue for GPU 3 at 0000023fb404a590
Scratchpad Allocation success for OpenCL Thread 5
Allocating big 3776MB scratchpad for OpenCL Thread 5...
Compiling kernels of OpenCL Thread 5...
Kernels of OpenCL Thread 5 compiled.

Starting GPU Thread 6, on GPU 4
Created OpenCL Context for GPU 4 at 0000023fb3ff7060
Created OpenCL Thread 6 Command-Queue for GPU 4 at 0000023fbff90a20
Scratchpad Allocation success for OpenCL Thread 6
Allocating big 3776MB scratchpad for OpenCL Thread 6...
Compiling kernels of OpenCL Thread 6...
Kernels of OpenCL Thread 6 compiled.

Starting GPU Thread 7, on GPU 4
Created OpenCL Thread 7 Command-Queue for GPU 4 at 0000023fbff915f0
Scratchpad Allocation success for OpenCL Thread 7
Allocating big 3776MB scratchpad for OpenCL Thread 7...
Compiling kernels of OpenCL Thread 7...
Kernels of OpenCL Thread 7 compiled.

Starting GPU Thread 8, on GPU 5
Created OpenCL Context for GPU 5 at 0000023fb3ff6980
Created OpenCL Thread 8 Command-Queue for GPU 5 at 0000023fbff900f0
Scratchpad Allocation success for OpenCL Thread 8
Allocating big 3776MB scratchpad for OpenCL Thread 8...
Compiling kernels of OpenCL Thread 8...
Kernels of OpenCL Thread 8 compiled.

Starting GPU Thread 9, on GPU 5
Created OpenCL Thread 9 Command-Queue for GPU 5 at 0000023fbff90cc0
Scratchpad Allocation success for OpenCL Thread 9
Allocating big 3776MB scratchpad for OpenCL Thread 9...
Compiling kernels of OpenCL Thread 9...
Kernels of OpenCL Thread 9 compiled.

Starting GPU Thread 10, on GPU 6
Created OpenCL Context for GPU 6 at 0000023fcda784b0
Created OpenCL Thread 10 Command-Queue for GPU 6 at 0000023fbff90240
Scratchpad Allocation success for OpenCL Thread 10
Allocating big 3776MB scratchpad for OpenCL Thread 10...
Compiling kernels of OpenCL Thread 10...
Kernels of OpenCL Thread 10 compiled.

Starting GPU Thread 11, on GPU 6
Created OpenCL Thread 11 Command-Queue for GPU 6 at 0000023fbff90f60
Scratchpad Allocation success for OpenCL Thread 11
Allocating big 3776MB scratchpad for OpenCL Thread 11...
Compiling kernels of OpenCL Thread 11...
Kernels of OpenCL Thread 11 compiled.

Starting GPU Thread 12, on GPU 7
Created OpenCL Context for GPU 7 at 0000023fcda78b90
Created OpenCL Thread 12 Command-Queue for GPU 7 at 0000023fbff90b70
Scratchpad Allocation success for OpenCL Thread 12
Allocating big 3776MB scratchpad for OpenCL Thread 12...
Compiling kernels of OpenCL Thread 12...
Kernels of OpenCL Thread 12 compiled.

Starting GPU Thread 13, on GPU 7
Created OpenCL Thread 13 Command-Queue for GPU 7 at 0000023fbff91c80
Scratchpad Allocation success for OpenCL Thread 13
Allocating big 3776MB scratchpad for OpenCL Thread 13...
Compiling kernels of OpenCL Thread 13...
Kernels of OpenCL Thread 13 compiled.

Starting GPU Thread 14, on GPU 8
Created OpenCL Context for GPU 8 at 0000023fcda79110
Created OpenCL Thread 14 Command-Queue for GPU 8 at 0000023fce3cc750
Scratchpad Allocation success for OpenCL Thread 14
Allocating big 3776MB scratchpad for OpenCL Thread 14...
Compiling kernels of OpenCL Thread 14...
Kernels of OpenCL Thread 14 compiled.

Starting GPU Thread 15, on GPU 8
Created OpenCL Thread 15 Command-Queue for GPU 8 at 0000023fce3cc8a0
Scratchpad Allocation success for OpenCL Thread 15
Allocating big 3776MB scratchpad for OpenCL Thread 15...
Compiling kernels of OpenCL Thread 15...
Kernels of OpenCL Thread 15 compiled.
GPU Watchdog minimum hashrate: 100
GPU Warmup disabled
Devfee for GPU is 0.9%

23:08:31 | Loki (LOK) Mining session starts!

During mining time, press:
 h      display hashrate for each mining thread.
 r      display full report.
 p      pause all.
 u      pause CPUs.
 0-F    pause GPU 0-15.
 t      GPU temperature and fan speed.
 q      quit.

23:08:31 | GPU Compute allocation starts at 80% and reaches 100% after ~1min,
23:08:31 | during this time, the hashrate may be unstable and inconsistent.
23:08:31 | Let the miner warm-up if you're tuning for performance.
23:08:32 | Connecting to mining pool sg.loki.miner.rocks:5555 ...
23:08:32 | Connected to pool. Now logging in...
23:08:32 | Successfuly logged as LK8CGQ17G9R3ys3Xf33wCeViD2B95jgdpjAhcRsjuheJ784dumXn7g3RPAzedWpFq364jJKYL9dkQ8mY66sZG9BiD26Xb3NXBMT3hTiNGd.80000
23:08:32 | Pool changes Difficulty to 80000.
23:08:37 | GPU 3 Thread 4 Lane 236 finds a Share, value 80000
23:08:37 | Accepted by the pool in 78 ms.
23:08:39 | GPU 4 Thread 6 Lane 914 finds a Share, value 80000
23:08:39 | Accepted by the pool in 81 ms.
23:08:54 | GPU 3 Thread 4 Lane 797 finds a Share, value 80000
23:08:55 | Accepted by the pool in 109 ms.
23:08:55 | GPU 3 Thread 5 Lane 227 finds a Share, value 80000
23:08:55 | Accepted by the pool in 47 ms.
23:09:01 | Pool sends a new Job.
23:09:02 | Hashrate GPU Thread 0: 624.01 h/s
23:09:02 | Hashrate GPU Thread 1: 623.43 h/s - Total GPU 1: 1247.43 h/s
23:09:02 | Hashrate GPU Thread 2: 589.42 h/s
23:09:02 | Hashrate GPU Thread 3: 585.70 h/s - Total GPU 2: 1175.12 h/s
23:09:02 | Hashrate GPU Thread 4: 585.70 h/s
23:09:02 | Hashrate GPU Thread 5: 589.54 h/s - Total GPU 3: 1175.24 h/s
23:09:02 | Hashrate GPU Thread 6: 555.69 h/s
23:09:02 | Hashrate GPU Thread 7: 553.98 h/s - Total GPU 4: 1109.66 h/s
23:09:02 | Hashrate GPU Thread 8: 585.70 h/s
23:09:02 | Hashrate GPU Thread 9: 591.36 h/s - Total GPU 5: 1177.06 h/s
23:09:02 | Hashrate GPU Thread 10: 588.01 h/s
23:09:02 | Hashrate GPU Thread 11: 585.70 h/s - Total GPU 6: 1173.70 h/s
23:09:02 | Hashrate GPU Thread 12: 623.43 h/s
23:09:02 | Hashrate GPU Thread 13: 624.01 h/s - Total GPU 7: 1247.43 h/s
23:09:02 | Hashrate GPU Thread 14: 578.27 h/s
23:09:02 | Hashrate GPU Thread 15: 578.39 h/s - Total GPU 8: 1156.66 h/s
23:09:02 | Total: 9462.27 h/s - Max: 9462.27 h/s
23:09:10 | GPU 5 Thread 9 Lane 521 finds a Share, value 80000
23:09:10 | Accepted by the pool in 63 ms.
23:09:10 | GPU 1: Temp: 58C - Fan:  0% -- Shares: Good: 0 Bad: 0
23:09:10 | GPU 2: Temp: 57C - Fan: 56% -- Shares: Good: 0 Bad: 0
23:09:10 | GPU 3: Temp: 57C - Fan: 57% -- Shares: Good: 3 Bad: 0
23:09:10 | GPU 4: Temp: 57C - Fan: 56% -- Shares: Good: 1 Bad: 0
23:09:10 | GPU 5: Temp: 52C - Fan: 55% -- Shares: Good: 1 Bad: 0
23:09:10 | GPU 6: Temp: 53C - Fan: 56% -- Shares: Good: 0 Bad: 0
23:09:10 | GPU 7: Temp: 59C - Fan: 44% -- Shares: Good: 0 Bad: 0
23:09:10 | GPU 8: Temp: 57C - Fan: 52% -- Shares: Good: 0 Bad: 0
23:09:23 | Pool sends a new Job.
23:09:32 | GPU 3 Thread 4 Lane 299 finds a Share, value 80000
23:09:32 | Accepted by the pool in 63 ms.
23:09:34 | Pause All
Post
Topic
Board Mining (Altcoins)
Re: [JCE] Ultrafast CN-Heavy/Tube/XHV miner, low power, Vega56 1750+h/s
by
lebuawu2
on 03/12/2018, 02:01:25 UTC
Quote from: _ap_ on December 02, 2018, 11:05:16 PM
Quote from: JCE-Miner on December 02, 2018, 01:18:11 PM
forget the b7 and try the new experimental (read: very untested) B-sync GPU
That's the lone .exe in the github page.

1. Stable and fast hashrate
2. new parameter --no-monitor to disable fan/temp monitoring (the purple report)
3. various optims for some cards and some algos, expect about +0.5%
4. Fees still 0.9%

so far it burns like fire on my rigs, i hope it really fixes all the hashrate and warmup problems.

with:
- cpu: working perfect
- integral gpu: working perfect
- 8gb rx 580: working perfect
- 4gb rx570: after pool login, the miner stopped and i got: "Press any key to continue..." message

my config: "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 3, "multi_hash":944 },

any idea?

*update: algo = bittube

thanks!

4gb GPU multi_hash should be lower for 2 thread about 464 or 480.