lolMiner 1.64: Fastest Kaspa miner in market - page 89.

Lolliedieb

member

Activity: 433

Merit: 48

Quote from: artful on January 15, 2020, 04:26:14 PM

Bug in lolminer on nvidia card

....
why lolminer launch in all videocards (55-100Mb using in all videocard)

I will check - seems some of the cleanup does not work for unselected cards. That lolMine is displayed at all comes from.OpenCL context that is created...

By the way we had C29M blocks now, but the diff balancibg in grin takes a while to adjust to the new scheme. Give it 3-4 hrs then every thing should be normal

WhyMe

sr. member

Activity: 661

Merit: 250

Are we facing a fail ? No more C29 block since the fork Sad

laik2

sr. member

Activity: 652

Merit: 266

Now reread the logfile a bit more recursive

Hint: They are displayed - not selected.

artful

newbie

Activity: 59

Merit: 0

Bug in lolminer on nvidia card

I run lolminer string:

Code:

./lolMiner --coin GRIN-AD29 --pool grincuckarood29.eu.nicehash.com --port 3377 --user --user wallet.worker --devices 12

me see log:
Setup Miner...
 Device 0:
    Name:    GeForce GTX 1650
    Address: 1:0
    Vendor:  NVIDIA Corporation
    Memory:  3910 MByte
    Active:  false (not selected)
 Device 1:
    Name:    GeForce GTX 1070
    Address: 2:0
    Vendor:  NVIDIA Corporation
    Memory:  8119 MByte
    Active:  false (not selected)
 Device 2:
    Name:    GeForce GTX 1070
    Address: 3:0
    Vendor:  NVIDIA Corporation
    Memory:  8119 MByte
    Active:  false (not selected)
 Device 3:
    Name:    GeForce GTX 1060 3GB
    Address: 7:0
    Vendor:  NVIDIA Corporation
    Memory:  3019 MByte
    Active:  false (not selected)
 Device 4:
    Name:    GeForce GTX 1070 Ti
    Address: 8:0
    Vendor:  NVIDIA Corporation
    Memory:  8119 MByte
    Active:  false (not selected)
 Device 5:
    Name:    P104-100
    Address: 9:0
    Vendor:  NVIDIA Corporation
    Memory:  8121 MByte
    Active:  false (not selected)
 Device 6:
    Name:    GeForce RTX 2070
    Address: 11:0
    Vendor:  NVIDIA Corporation
    Memory:  7982 MByte
    Active:  false (not selected)
 Device 7:
    Name:    GeForce GTX 1050 Ti
    Address: 13:0
    Vendor:  NVIDIA Corporation
    Memory:  4040 MByte
    Active:  false (not selected)
 Device 8:
    Name:    GeForce GTX 1060 3GB
    Address: 15:0
    Vendor:  NVIDIA Corporation
    Memory:  3019 MByte
    Active:  false (not selected)
 Device 9:
    Name:    GeForce GTX 1060 6GB
    Address: 16:0
    Vendor:  NVIDIA Corporation
    Memory:  6078 MByte
    Active:  false (not selected)
 Device 10:
    Name:    P104-100
    Address: 17:0
    Vendor:  NVIDIA Corporation
    Memory:  4042 MByte
    Active:  false (not selected)
 Device 11:
    Name:    P104-100
    Address: 18:0
    Vendor:  NVIDIA Corporation
    Memory:  8121 MByte
    Active:  false (not selected)
 Device 12:
    Name:    GeForce GTX 1060 6GB
    Address: 19:0
    Vendor:  NVIDIA Corporation
    Memory:  6078 MByte
    Active:  true (Selected Algorithm: Cuckarood 29-6G)

after run miner - me check working - nvidia-smi

Code:

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0       778      G   /usr/lib/xorg/Xorg                             5MiB |
|    0       863      C   ./lolMiner                                    55MiB |
|    0      3904      C   .../calcprofit/miners/pm/4.2c/PhoenixMiner  3705MiB |
|    1       778      G   /usr/lib/xorg/Xorg                             5MiB |
|    1       863      C   ./lolMiner                                    85MiB |
|    1     11603      C   ...ing/calcprofit/miners/gminer/1.93/miner  7707MiB |
|    2       778      G   /usr/lib/xorg/Xorg                             5MiB |
|    2       863      C   ./lolMiner                                    85MiB |
|    2     11610      C   ...ing/calcprofit/miners/gminer/1.93/miner  7707MiB |
|    3       778      G   /usr/lib/xorg/Xorg                             5MiB |
|    3       863      C   ./lolMiner                                    61MiB |
|    3     31127      C   ...ing/calcprofit/miners/gminer/1.70/miner  1747MiB |
|    4       778      G   /usr/lib/xorg/Xorg                             5MiB |
|    4       863      C   ./lolMiner                                   103MiB |
|    4     11596      C   ...ing/calcprofit/miners/gminer/1.82/miner  7725MiB |
|    5       778      G   /usr/lib/xorg/Xorg                             5MiB |
|    5       863      C   ./lolMiner                                    85MiB |
|    5      5680      C   .../calcprofit/miners/pm/4.2c/PhoenixMiner  3737MiB |
|    6       778      G   /usr/lib/xorg/Xorg                             5MiB |
|    6       863      C   ./lolMiner                                    99MiB |
|    6     11614      C   ...ing/calcprofit/miners/gminer/1.93/miner  7725MiB |
|    7       778      G   /usr/lib/xorg/Xorg                             5MiB |
|    7       863      C   ./lolMiner                                    47MiB |
|    7     24771      C   .../calcprofit/miners/pm/4.2c/PhoenixMiner  3699MiB |
|    8       778      G   /usr/lib/xorg/Xorg                             5MiB |
|    8       863      C   ./lolMiner                                    61MiB |
|    8     31132      C   ...ing/calcprofit/miners/gminer/1.82/miner  1747MiB |
|    9       778      G   /usr/lib/xorg/Xorg                             5MiB |
|    9       863      C   ./lolMiner                                    65MiB |
|    9      3892      C   .../calcprofit/miners/pm/4.2c/PhoenixMiner  3717MiB |
|   10       778      G   /usr/lib/xorg/Xorg                             5MiB |
|   10       863      C   ./lolMiner                                    85MiB |
|   10     27853      C   .../calcprofit/miners/pm/4.2c/PhoenixMiner  3737MiB |
|   11       778      G   /usr/lib/xorg/Xorg                             5MiB |
|   11       863      C   ./lolMiner                                    85MiB |
|   11     27853      C   .../calcprofit/miners/pm/4.2c/PhoenixMiner  3737MiB |
|   12       778      G   /usr/lib/xorg/Xorg                             5MiB |
|   12       863      C   ./lolMiner                                  5261MiB |
+-----------------------------------------------------------------------------+

why lolminer launch in all videocards (55-100Mb using in all videocard)

Vooxaa

newbie

Activity: 15

Merit: 0

please support Cuckarood29V pow for mining MoneroV
reference miner: https://github.com/xmvdev/MoneroVMiner/releases

Bathmat

jr. member

Activity: 78

Merit: 3

Just tested the new version: nice improvement for Navi on Windows. Also, I'm using 19.9.2 without any issues so far.

GPU settings: 1500/875/825mV (~100W gpu only power draw), averaging ~1.05 gps per Navi (up from around 0.93 gps)

Lolliedieb

member

Activity: 433

Merit: 48

Hey Friends,

just pushed the update to lolMiner 0.9.5.

For all that just need the link: Here it is

This one will finally bring support for the C29M upgrade on Thursday Cheesy

Here is the full change log:

Version 0.9.5

Added support for Grin CuckarooM-29 (hard fork on Jan 16th) on 8G AMD GPUs, use --coin GRIN-C29M to mine with it.

Hint: The miner will pause until the fork height is reached not to waste energy. Use --coin FLOO-C29M to test the miner in floonet testnet before if you like.

Improved C31 performance on 8G cards by ~5% (Windows: relatively to 0.9.3, Linux: relatively to 0.9.4)
Navi on Windows now runs same kernels as in Linux
Slightly lowered energy use of C31 / C32 solver
Added aliases GRIN-C31 and GRIN-C32 for the Cuckatoo solvers (the old names still exist and continue to work)
Changed driver requirement for all GRIN codes: 18.50 for all pre-Navi cards, 19.30 for Navi (Linux); Adrenaline 18.12 for all pre-Navi, Adrenaline 19.10 for Navi

Expected performances:

GRIN-C29M (stock clocks, tested using amdgpu-pro 19.30)
Note: Windows speeds may differ slightly (max 3-4%)

Radeon VII: 6.1 g/s
Vega 64: 4.4 g/s
Vega 56: 3.7 g/s
RX 5700: 4.0 g/s
RX 570: 2.2 g/s

Any feedback appreciated

cluburlauber

newbie

Activity: 57

Merit: 0

Quote from: jasta more on January 11, 2020, 03:17:50 AM

Quote from: cluburlauber on January 10, 2020, 07:31:33 PM

Hi Lollidieb
Have you an old miner for x16r for amd?
Your miner for other algos is one of the best
I use very old graphic cards (r9 290) and no miner i try will work (very low hashrate <0,6 mhs with standard clocks)
Best wishes
Cluburlauber

X16r is Asics territory now, you would just lose money mining it

X16r is asic - really?
I want to mine the death coin gravium. Maybee in the future it will be reactivated.
Because there is only one miner.
But i didnt find a miner who works with r9 290. So i ask here lollidieb

Greetings

jasta more

member

Activity: 224

Merit: 18

Quote from: cluburlauber on January 10, 2020, 07:31:33 PM

Hi Lollidieb
Have you an old miner for x16r for amd?
Your miner for other algos is one of the best
I use very old graphic cards (r9 290) and no miner i try will work (very low hashrate <0,6 mhs with standard clocks)
Best wishes
Cluburlauber

X16r is Asics territory now, you would just lose money mining it

cluburlauber

newbie

Activity: 57

Merit: 0

Hi Lollidieb
Have you an old miner for x16r for amd?
Your miner for other algos is one of the best
I use very old graphic cards (r9 290) and no miner i try will work (very low hashrate <0,6 mhs with standard clocks)
Best wishes
Cluburlauber

kbs1

jr. member

Activity: 107

Merit: 1

Lolliedieb, will cuckaroom29 on RX 580 8GB on Win 10 be supported?

un4given

full member

Activity: 192

Merit: 100

Hi!

when i try mining BEAM V2 on my 5700 XT i see jobs received but speed is 0 and miner is not showing in pool? any idea what is wrong? the configuration s correct and miner connects to the pool

pbfarmer

member

Activity: 340

Merit: 29

HNY!

Just wanted to post some c31 settings (for vega64) which may be more interesting to people w/ prices so low these days. In general, it seems that 1150cclk/800mclk @ 800mv is pretty safe - for about 1.03-1.05gps. Only one of my 8 Nitros needed a tiny bump down on cclk (to 1140MHz) to be stable. Some can go up quite a bit while still maintaining 800mv - the last two in this screenshot are running w/ a setting of 1250+ cclk for ~1.1gps (I haven't tuned the others yet.) I'm seeing an avg of about 150-153w/GPU ATW on a 1600 plat PSU @ 120v, which should be significantly more efficient than any of the settings provided in the ann.

Lolliedieb

member

Activity: 433

Merit: 48

Happy new Year you all Cheesy

Quote from: xMindx163 on December 30, 2019, 05:21:20 AM

Quote from: tale01 on December 29, 2019, 10:00:36 PM

Can you support MoneroV (XMV) Algorithm: Cuckarood29v

?
Official Miner https://github.com/xmvdev/MoneroVMiner/releases

I need to support 4G Grin

As soon as there is support with manners, the coin will be rolled into the bottom. So you don't need anything. Be happy with what you have.

Just hearing of MoneroV the first time. Wonder what this is about. Well it seems there are only changes in the cycle length and some small stuff in the stratum (Hell, why people always fail to document that stuff when they fork a coin)... but seriously: There is not even 1k g/s using my C29D code although its the only 4G implementation for AMDs ... how much can I expect from this - the network not even is 1/100 the size of grin. That likely won't roi the time for me changing the code Sad

xMindx163

newbie

Activity: 37

Merit: 0

Quote from: tale01 on December 29, 2019, 10:00:36 PM

Can you support MoneroV (XMV) Algorithm: Cuckarood29v

?
Official Miner https://github.com/xmvdev/MoneroVMiner/releases

I need to support 4G Grin

As soon as there is support with manners, the coin will be rolled into the bottom. So you don't need anything. Be happy with what you have.

tale01

newbie

Activity: 121

Merit: 0

Can you support MoneroV (XMV) Algorithm: Cuckarood29v

?
Official Miner https://github.com/xmvdev/MoneroVMiner/releases

I need to support 4G Grin

Lolliedieb

member

Activity: 433

Merit: 48

Good and bad news from AMD (Link if anyone wants to read themselves why)

It seems I will be able to port 0.9.4 speedup for Navi on Windows, but not for Vega 56/64 and VII. "Stupid" driver limitation imao - well at least they are aware of the issue now. Will need to figure out if I see a way to speed it up without using the extra memory (in that case also 470/480/570 and 580 would profit ... I will try...)

Lolliedieb

member

Activity: 433

Merit: 48

Quote from: tromp on December 16, 2019, 05:10:42 PM

Until the C31 phaseout starts around Jan 15, C31 will certainly be more profitable.
It depends on your hardware when C32 becomes more profitable, but likely not until April...

Well I would guess a little earlier - lets assume a Vega64 does 1.3 g/s C31 and 0.4 g/s C32. So 30.7% of the speed. Considering the higher scale of C32 the profitability is right now 63% of C31. So at current speeds it will take until end of March until the profitability flips. But C32 is barely optimized yet Wink

Ps: currently on travel, sry for the silence. Also still waiting for reply from AMD about the Windows issue :/

tromp

legendary

Activity: 990

Merit: 1108

Quote from: kaiokenx10 on December 16, 2019, 01:13:27 PM

So is it more profitable to mine c32 or c31 now ?

Until the C31 phaseout starts around Jan 15, C31 will certainly be more profitable.
It depends on your hardware when C32 becomes more profitable, but likely not until April...

WhyMe

sr. member

Activity: 661

Merit: 250

Any chance to have BFC variant ?

Topic: lolMiner 1.64: Fastest Kaspa miner in market - page 89. (Read 155842 times)