lolMiner 1.64: Fastest Kaspa miner in market

[Velmerk]

i hive Vega 56 and Hive os (latest version)
lolminer 0.9.2 grin31
i get the inscription:
"All devices deselected or failed compatiblity check. Closing lolMiner"
what should be done?

update your drivers... 19.10+ i think...

[Lolliedieb]

i hive Vega 56 and Hive os (latest version)
lolminer 0.9.2 grin31
i get the inscription:
"All devices deselected or failed compatiblity check. Closing lolMiner"
what should be done?

As already pointed out by @Velmerk the problem is likely the driver. Use the current hive beta images, they have 19.30 and should work like a charm with 0.9.x versions

[jasta more]

Random x algo soon?

[Velmerk]

Random x algo soon?

RandomX not for GPU, its for CPU botnet.

[kaiokenx10]

Hello, i am having some problems with lolminer 0.9.2.

Vega 56 flashed to 64, win 10 1703, adrenalin 19.2.1

+---------------------------------------------------------+
|    _       _ __  __ _                    ___   ___      |
|   | | ___ | |  \/  (_)_ __   ___ _ __   / _ \ / _ \     |
|   | |/ _ \| | |\/| | | '_ \ / _ \ '__| | | | | (_) |    |
|   | | (_) | | |  | | | | | |  __/ |    | |_| |\__, |    |
|   |_|\___/|_|_|  |_|_|_| |_|\___|_|     \___(_) /_/(2)  |
|                                                         |
|              This software is for mining                |
|              Equihash  96/5, 144/5, 210/9               |
|              BeamHash II (EquihashR 150/5/3)            |
|              ZelHash     (EquihashR 125/4/0)            |
|              CuckarooD 29                               |
|              Cuckatoo  31                               |
|                                                         |
|                                                         |
|          Made by Lolliedieb, November 2019              |
+---------------------------------------------------------+
Warning: No user profile defined in command line (--profile <profileName> missing)
Using only DEFAULT section and command line input
Reading pool data from command line
lolMiner is configured to mine Grin(GRIN-AT31), Cuckatoo-31

Setup Miner...
 Device 0:
    Name:    Radeon RX Vega
    Address: 3:0
    Vendor:  Advanced Micro Devices (AMD)
    Memory:  8176 MByte (8112 MByte free)
    Active:  false (OpenCL init failure: Build program failure)
 Device 1:
    Name:    Radeon RX Vega
    Address: 7:0
    Vendor:  Advanced Micro Devices (AMD)
    Memory:  8176 MByte (8112 MByte free)
    Active:  false (OpenCL init failure: Build program failure)
 Device 2:
    Name:    Radeon RX Vega
    Address: 10:0
    Vendor:  Advanced Micro Devices (AMD)
    Memory:  8176 MByte (8112 MByte free)
    Active:  false (OpenCL init failure: Build program failure)
 Device 3:
    Name:    Radeon RX Vega
    Address: 15:0
    Vendor:  Advanced Micro Devices (AMD)
    Memory:  8176 MByte (8112 MByte free)
    Active:  false (OpenCL init failure: Build program failure)

Connecting to pool...
Connected to grin-eu.sparkpool.com:6667 (TLS disabled)
Authorized worker: a*****@hotmail.com
New job received: 1575721135886 Difficulty: 1
Start Mining...
All devices deselected or failed compatiblity check. Closing lolMiner

EDIT: Just updated to 19.12.1 Adrenalin, works like a charm

[LilouCha]

impossible with 5700 xt sapphire pulse on aion.
I have newjob but 0 shares.

I have the latest amd drivers for windows and I use the latest version lolminer ... I see even a hasrate that goes from 0.2s to 0.8s, 0.5, 0.4 without sharing

[ctsbitcoin]

I'm using Windows and Vega 56/64 rigs with the latest drivers running lolminer 0.9.2 however on either of my rigs I will randomly get a GPU that says "Stuck device detected, invoking emergency script."  

Then the next line down says:
'.' is not recognized as an internal or external command, operable program or batch file.

I did find a reboot.bat file and I tried adding a line:
shutdown.exe /r /t 10

Same response as above.  Is there somewhere that I need to enable this rather handy watchdog feature, or is there certain syntax that needs to be used?

As for the error, I'm wondering if my P3/P7 are off.  I'm having a heck of a time with adjusting as these cards can absorb electricity at stock, wow.  I did quite well with tweaking for XMR but G31 appears to be different.  

V56 x8 (onsite)
P7 = 1350 / 890
P3 = 950 / 800
Power Target = -50%
Result: 0.7g/s per GPU

V64 x4 (offsite)
P7 = 1408 / 925
P3 = 945 / 1000
Power Target = 10%
Result: 1g/s per GPU

Any assistance and knowledge would be appreciated, thank you.

[GKumaran]

I'm using Windows and Vega 56/64 rigs with the latest drivers running lolminer 0.9.2 however on either of my rigs I will randomly get a GPU that says "Stuck device detected, invoking emergency script."  

Then the next line down says:
'.' is not recognized as an internal or external command, operable program or batch file.

I did find a reboot.bat file and I tried adding a line:
shutdown.exe /r /t 10

Same response as above.  Is there somewhere that I need to enable this rather handy watchdog feature, or is there certain syntax that needs to be used?

As for the error, I'm wondering if my P3/P7 are off.  I'm having a heck of a time with adjusting as these cards can absorb electricity at stock, wow.  I did quite well with tweaking for XMR but G31 appears to be different.  

V56 x8 (onsite)
P7 = 1350 / 890
P3 = 950 / 800
Power Target = -50%
Result: 0.7g/s per GPU

V64 x4 (offsite)
P7 = 1408 / 925
P3 = 945 / 1000
Power Target = 10%
Result: 1g/s per GPU

Any assistance and knowledge would be appreciated, thank you.

Hey for the Vega 64s my suggestion :

P6 - ODT : 1305/850 ; Hwinfo : 1237/820
P3 - ODT : 1028/850 ; Hwinfo(mem clock and soc clock) : 1028
Power Target - 0% ( Stock) Driver : 19.10.1

Results : 1.07 g/s for 190 watts at the wall

[kaiokenx10]

I'm using Windows and Vega 56/64 rigs with the latest drivers running lolminer 0.9.2 however on either of my rigs I will randomly get a GPU that says "Stuck device detected, invoking emergency script."  

Then the next line down says:
'.' is not recognized as an internal or external command, operable program or batch file.

I did find a reboot.bat file and I tried adding a line:
shutdown.exe /r /t 10

Same response as above.  Is there somewhere that I need to enable this rather handy watchdog feature, or is there certain syntax that needs to be used?

As for the error, I'm wondering if my P3/P7 are off.  I'm having a heck of a time with adjusting as these cards can absorb electricity at stock, wow.  I did quite well with tweaking for XMR but G31 appears to be different.  

V56 x8 (onsite)
P7 = 1350 / 890
P3 = 950 / 800
Power Target = -50%
Result: 0.7g/s per GPU

V64 x4 (offsite)
P7 = 1408 / 925
P3 = 945 / 1000
Power Target = 10%
Result: 1g/s per GPU

Any assistance and knowledge would be appreciated, thank you.

i tried every setting possible and it keeps saying the same stuff on both of my vega 56 and 64 rigs.. i think the problem lies in something else, not the clocks and voltage

[ctsbitcoin]

i tried every setting possible and it keeps saying the same stuff on both of my vega 56 and 64 rigs.. i think the problem lies in something else, not the clocks and voltage

I switched my V64s back to stock 1630/1200/945/1100 and so far so good this morning.  It appears the P3 is more important than the P7.  

I tried GKumaran's and my V64s immediately crashed.  Just wondering if anyone else had any numbers that may help in avoiding the reinvention of the wheel.

However with lolminer, that Watchdog reboot.bat file is a really good idea and I'd like to know what I'm doing wrong in getting that to work as explained above.  

UPDATE:
Well it appears even the stock values have had issues as I again received this error:

"Stuck device detected, invoking emergency script." 

Then the next line down says:
'.' is not recognized as an internal or external command, operable program or batch file.

I can live with it if there is a way lolminer can auto restart the affected GPU or even simply restarts the rig. 

[kaiokenx10]

i tried every setting possible and it keeps saying the same stuff on both of my vega 56 and 64 rigs.. i think the problem lies in something else, not the clocks and voltage

I switched my V64s back to stock 1630/1200/945/1100 and so far so good this morning.  It appears the P3 is more important than the P7. 

I tried GKumaran's and my V64s immediately crashed.  Just wondering if anyone else had any numbers that may help in avoiding the reinvention of the wheel.

However with lolminer, that Watchdog reboot.bat file is a really good idea and I'd like to know what I'm doing wrong in getting that to work as explained above. 

it is unreal that c31 is more memory intensive than i.e. ETH, i find that really hard to believe, it is something with the miner, the dev should look into it

[ctsbitcoin]

Version 0.9.2

• Significant performance improvement of GRIN-AT31 on 8 / 16G cards (+5% on Polaris & Vega, +10 on Navi)
• Experimental support for GRIN-AT31 and Polaris, Vega and VII using AMD ROCm drivers
• Added range checks to GRIN-AT31 code (improves better stability)
• Added function to call external watchdog scripts in case a GPU fails during mining (see release notes)

Usage of Watchdog Script

In case the miner detects no action of a GPU for at least a minute it will call the included scripts "reboot.sh" (Linux) or "reboot.bat" (Windows) and display a warning message in red. Afterwards the counters are reset. The scripts can be used to trigger a reboot of the rig or to call any other watchdog actions. The miner itself will take no further action and continue operation on the remaining cards.

I read the "lolMiner_manual.pdf" included in the zip but I'm not seeing any details on the Watchdog Script.  I presume this is just a simple bat command file?  I'd prefer to simply restart ODT + lolminer if a GPU fails or if needed the entire rig.  Thank you!

[Lolliedieb]

impossible with 5700 xt sapphire pulse on aion.
I have newjob but 0 shares.

I have the latest amd drivers for windows and I use the latest version lolminer ... I see even a hasrate that goes from 0.2s to 0.8s, 0.5, 0.4 without sharing

Well 0.x sol/s is very low - I would not expect to see a share very soon. Normally this Navi should do up to 200 sol/s on Aion, but well - its not officially supported yet and it seems I need to redo a lot of code to support it. Support will come, but do not know when, yet.

I read the "lolMiner_manual.pdf" included in the zip but I'm not seeing any details on the Watchdog Script.  I presume this is just a simple bat command file?  I'd prefer to simply restart ODT + lolminer if a GPU fails or if needed the entire rig.  Thank you!

Well there is not much to tell - the script will be called once a GPU got stuck and thats it - it can do anything you write in that. I guess mostly mining operation systems will use it to trigger their watchdogs.

Then the next line down says:
'.' is not recognized as an internal or external command, operable program or batch file.

You got hit by two bugs of 0.9.2 - the one is a small instability that can happen the card to crash even at stocks - rare but can happen, the other is that I made a mistake with the reboot call in Windows. Both will hopefully be fixed with 0.9.3 that will be out likely tomorrow Working hard on that one right now / testing it for stability. Also new version will allow to run with older drivers and will give better "miner displayed hash" <--> "pool hash" ratio Stay tuned

[ctsbitcoin]

You got hit by two bugs of 0.9.2 - the one is a small instability that can happen the card to crash even at stocks - rare but can happen, the other is that I made a mistake with the reboot call in Windows. Both will hopefully be fixed with 0.9.3 that will be out likely tomorrow Working hard on that one right now / testing it for stability. Also new version will allow to run with older drivers and will give better "miner displayed hash" <--> "pool hash" ratio Stay tuned

Woot, woot!  Talk customer service!  Looking forward my friend!

[Lolliedieb]

Just pushed the new release of lolMiner 0.9.3.

Was plenty of work ironing out all problems found so far - user experience on this one should be much better. Also pool hash (read the example below)

Hope you like it

Changes to 0.9.2

• Extended GRIN-AT31 compatibility to older drivers (18.x +)
• Improved GRIN-AT31 performance on ROCm (RX 470/480/570/580/Vega/VII)
• Introduced early job cancellation for GRIN-AT31+ (improves hash on pool side, see further release notes)
• Deeply reworked kernel scheduler
• Fixed GRIN-AT31 kernel bugs (improving stability and fidelity)
• Fixed Bug: Vega FE loading 8G instead of 16G GRIN-AT31 solver in Windows
• Fixed Bug: Watchdog did not call right file in Windows
• Added --disablewatchdog 1 parameter to disable the 0 sol/s / 0 g/s detection

About Early Job Cancellation for GRIN

The GRIN proof of work is a compute intense and rather slow algorithm. Especially C31 often needs (at 1 g/s) about one second for each graph processed. In case a new job (for a new chain height) arrives, the current calculation effort is worthless, because the block that was mined on already got found.
lolMiner 0.9.3 now introduces an early cancellation for long lasting works: if a new work arrives that invalidates the current run calculations, they get canceled to start quicker on the fresh work. To demonstrate the effect see the example describing the 0.9.2 and 0.9.3 difference:
Assume you have a card running 1 g/s on GRIN-AT31. Then in 2 minutes (120 seconds) it will be able to process 120 graphs. On average - Grin has a 1 minute block time - two of these graphs are already obsolete when they got finished.
lolMiner 0.9.2 will display the 1 g/s, because of 120 processed graphs per 120 seconds. But two of the graphs are then filtered out in the stratum module, thus the pool can see at most 118 / 120 = 0.983 g/s (minus about 1 graph fee).
lolMiner 0.9.3 will cancel the running work before it gets completed. On average you will be able to process one more graph then 0.9.2 assuming both are canceled about half way through. Thus lolMiner 0.9.3 starts 121 graphs and completes 119 of them. The displayed hash rate is now 119 graphs /120 seconds = 0.991 g/s. This equals what the pool could see (minus one for fee), because the 119 completed are the ones that got not canceled early.

Conclusion: lolMiner 0.9.3 DISPLAYED hash rate may be a little lower then 0.9.2, but what arrives at pool is better. The slower the cards are, the more drastic is this effect, e.g. a 580 8G running at 0.65 g/s will benefit almost 2% on pool side, a VII with 1.75 g/s only half a percent.
Combined with the mostly on GPU cycle finder lolMiner achieves a stale share rate of less then 0.7% and thus gives you best displayed to pool hash rate ratio available for Grin Cuckatoo-31.

[Velmerk]

Just pushed the new release of lolMiner 0.9.3.

Thank you for job!
HiveOS w/19.30 ~same hashrate (1.0-1.3) as 0.9.2, its good.
I installed ROCm 2.10 drivers, and hashrate only 0.69 now. What do you think?
6*Vega56

P.S. after testing with only 1 device, hashrate up to 1.04h.... may be high CPU usage... (only with ROCm)

[Vladegg]

Warning:
For AMD Navi support on Grin-32 you need Adrenalin 19.10.1 WHQL or newer (Windows) or amdgpu-pro 19.30 (Linux)

Grin-32? 

[Lolliedieb]

Just pushed the new release of lolMiner 0.9.3.

Thank you for job!
HiveOS w/19.30 ~same hashrate (1.0-1.3) as 0.9.2, its good.
I installed ROCm 2.10 drivers, and hashrate only 0.69 now. What do you think?
6*Vega56

P.S. after testing with only 1 device, hashrate up to 1.04h.... may be high CPU usage... (only with ROCm)

Thats good to know. Grin is indeed a bit cpu demanding, I do not know why its that much - mostly the scheduler turning wild there. Will see if I can do something on that...

Grin-32? 

Spelling mistake ... but ... well a lot of Grin-32 code in in the miner already

[Shaddyr]

can't  mine beamv2 at nice. Command line is

Code:

lolMiner.exe  --coin Beam --pool beamv2.eu.nicehash.com --port 3378 --user addr.wrkr --pass x --tls 0

It says

Connected to beamv2.eu.nicehash.com:3378 (TLS disabled)
Lost connection to stratum server beamv2.eu.nicehash.com:3378 or server not reachable

Anybody else?

[kidus]

Just pushed the new release of lolMiner 0.9.3.

How can I see the temperature of the videocards, the speed of the fans?
Did you test VEGA64?