lolMiner 1.53: Dual mining Eth+Kaspa and more efficient AMD kernels

[un4given]

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

[1660921762]

1660921762

[1660921762]

1660921762

[1660921762]

1660921762

[1660921762]

1660921762

[kbs1]

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

[cluburlauber]

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

[jasta more]

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]

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

[Lolliedieb]

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

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    

[Bathmat]

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)

[Vooxaa]

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

[artful]

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)

[laik2]

Now reread the logfile a bit more recursive
Hint: They are displayed - not selected.

[WhyMe]

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

[Lolliedieb]

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

[Lolliedieb]

C31 very profitable at the moment - because the grin network needed to adjust diff down due to the C29 fork.
Miner where are you?


Ps: good progress on 4G C29M code

[WhyMe]

No profit to do on C31 with RX

[Lolliedieb]

Well no I would say ... When you put in the actual values its 2nd best algo after ethash - but well that still leading the pack. Well on Vegas its different (just wtm using totally unreasonable clock settings ^^)

[ayiphelmy]

fury not working with new grin algo... any clue for this gpu?

[Lolliedieb]

Problem is that my solver at the moment needs 8G to work. So 390 does work, but Fury only got 4G ... I am thinking about a 4G solver but its more complicated then anticipated.

[ayiphelmy]

Problem is that my solver at the moment needs 8G to work. So 390 does work, but Fury only got 4G ... I am thinking about a 4G solver but its more complicated then anticipated.

ah i see... but fury is still strong on etc can get 33 mhs

[joeykolb]

this version of lolminer v09.5 doesnt like vega's.. it gives me 0.00 hashes

[Lolliedieb]

this version of lolminer v09.5 doesnt like vega's.. it gives me 0.00 hashes

Can you share operation system.and driver version? Would like to debug, but need more info