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

tale01

newbie

Activity: 121

Merit: 0

lolMiner 0.9.1 - Fiji cannot mine GRIN31. Adrenalin 19.11.3 & 19.10.1 is the same result
Old version can mine.

+---------------------------------------------------------+
| _ _ __ __ _ ___ ___ |
| | | ___ | | \/ (_)_ __ ___ _ __ / _ \ / _ \ |
| | |/ _ \| | |\/| | | '_ \ / _ \ '__| | | | | (_) | |
| | | (_) | | | | | | | | | __/ | | |_| |\__, | |
| |_|\___/|_|_| |_|_|_| |_|\___|_| \___(_) /_/(1) |
| |
| 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 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: AMD Radeon (TM) R9 Fury Series
   Address: 1:0
   Vendor: Advanced Micro Devices (AMD)
   Memory: 4096 MByte (4042 MByte free)
   Active: false ()

Connecting to pool...
Connected to eu.stratum.grin-pool.org:3416 (TLS disabled)
Authorized worker: Lolliedieb
New job received: 8 Difficulty: 4
Start Mining...
All devices deselected or failed compatiblity check. Closing lolMiner

cikusa

jr. member

Activity: 39

Merit: 2

Reporting 1.2gps on 5700xt using stock settings.

VasilyS

member

Activity: 618

Merit: 21

0,43 G/s on R9 290 while mining on Ubuntu algo Grin31. Ethereum mining is more profitable on R9 290 at the moment with 29 mh/s.

Lolliedieb

member

Activity: 433

Merit: 48

Always welcome Guys Wink

I pushed a new version (0.9.1) today adding support for 4G and 16G cards and experimental one for Navi

Also users of 0.9 should update, because in some situations it was possible that 0.9 gave lower pool hash for Grin-31 then it should give - this was fixed with 0.9.1

Have fun mining

fredeq

legendary

Activity: 1537

Merit: 1005

Updating to 19.10.1 helped, thanks for fast support!

laik2

sr. member

Activity: 652

Merit: 266

Quote from: fredeq on November 22, 2019, 06:50:44 AM

Quote from: Lolliedieb on November 22, 2019, 03:06:15 AM

We had that problem with qweb1 (there its solved by the way): You will need Adrenalin 19.10.1 WHQL or newer for the new 8G Kernels - on older drivers loading the Kernels will fail and thus the miner jumps to the next best option on same Algorithm (which is the old 4G solver).

Will try this, though sounds a bit strange as in the same rig 480 8g is able to load 8g kernel.
The difference may come from the fact that 480 is reported to have 8138 free memory while vegas report 8112.

Newer driver was used to compile the support for Vega and Radeon VII, thats the reason, older code was probably not suitable with current optimizations. As dev advised, please update your drivers to latest.

fredeq

legendary

Activity: 1537

Merit: 1005

Quote from: Lolliedieb on November 22, 2019, 03:06:15 AM

We had that problem with qweb1 (there its solved by the way): You will need Adrenalin 19.10.1 WHQL or newer for the new 8G Kernels - on older drivers loading the Kernels will fail and thus the miner jumps to the next best option on same Algorithm (which is the old 4G solver).

Will try this, though sounds a bit strange as in the same rig 480 8g is able to load 8g kernel.
The difference may come from the fact that 480 is reported to have 8138 free memory while vegas report 8112.

qwep1

hero member

Activity: 610

Merit: 500

my problem is sloved nead updaite driver thanks

Lolliedieb

member

Activity: 433

Merit: 48

We had that problem with qweb1 (there its solved by the way): You will need Adrenalin 19.10.1 WHQL or newer for the new 8G Kernels - on older drivers loading the Kernels will fail and thus the miner jumps to the next best option on same Algorithm (which is the old 4G solver).

fredeq

legendary

Activity: 1537

Merit: 1005

Using 0.9 and it selects 4gb solver for both 56 and 64 vegas. Currently on win10.

The thing is that I had the exact same config files on 0.8.7 and it was selecting 8gb solver (still works btw)
Possible to force 8gb somehow? Wink

Lolliedieb

member

Activity: 433

Merit: 48

Quote from: UselessGuru on November 21, 2019, 12:16:14 PM

Falling back to 0:

This indeed can happen with Nvidias on this Algo - thus I never announced Nvidia support for this one Wink

Also its loading the old 4G sources kernel and not the ones that are new in 0.9, because I did not create new Nvidia kernels.
I suggest you test with --devices 3 to pick the 580 Wink

For the Nvidias I would run bminer / nbminer along with lolMiner.

By the way: --workbatch is deprecated since ... 0.8 - it just has no effect any more Wink

UselessGuru

jr. member

Activity: 200

Merit: 3

lolminer.exe --coin GRIN-AT31 --workbatch HIGH --shortstats 5 --digits 3 --pool grincuckatoo31.eu.nicehash.com --port 3372 --user *********************.**** --pass x --apiport 4001 --tls 0 --devices 1

Falling back to 0:

Code:

+---------------------------------------------------------+
| _ _ __ __ _ ___ ___ |
| | | ___ | | \/ (_)_ __ ___ _ __ / _ \ / _ \ |
| | |/ _ \| | |\/| | | '_ \ / _ \ '__| | | | | (_) | |
| | | (_) | | | | | | | | | __/ | | |_| |\__, | |
| |_|\___/|_|_| |_|_|_| |_|\___|_| \___(_) /_/ |
| |
| 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 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: GeForce GTX 1080 Ti
   Address: 1:0
   Vendor: NVIDIA Corporation
   Memory: 11264 MByte
   Active: true (Selected Algorithm: Cuckatoo 31-4G)
Device 1:
   Name: GeForce GTX 1060 6GB
   Address: 4:0
   Vendor: NVIDIA Corporation
   Memory: 6144 MByte
   Active: false (not selected)
Device 2:
   Name: AMD Radeon (TM) RX 560
   Address: 5:0
   Vendor: Advanced Micro Devices (AMD)
   Memory: 2048 MByte (1994 MByte free)
   Active: false (not selected)
Device 3:
   Name: Radeon RX 580 Series
   Address: 8:0
   Vendor: Advanced Micro Devices (AMD)
   Memory: 8192 MByte (8138 MByte free)
   Active: false (not selected)

Connecting to pool...
Connected to grincuckatoo31.eu.nicehash.com:3372 (TLS disabled)
Authorized worker: ************************************.********
New job received: 938691245 Difficulty: 16
Start Mining...
Average speed (5s): 0.317 g/s
Average speed (5s): 0.000 g/s
New job received: 938692617 Difficulty: 16
Average speed (5s): 0.000 g/s
Average speed (5s): 0.000 g/s

Lolliedieb

member

Activity: 433

Merit: 48

Quote from: qwep1 on November 20, 2019, 03:07:49 PM

vega 56 0.47 (((

Hmm ... can you check if it really loaded the new kernel and not the old 4G one? Because here on test system (Linux, 19.30 driver & Windows 10, Adrenalin 19.30) the V56 is at ~1.04 g/s. What I could imagine is that if you run an older driver or ROCm then the load of the binary kernal fails and it falls back to the backup 4G solver.

Here what the testsys (2x 56, 1x 64 in the middle, optimized clocks for performance/watts) just produced:

Code:

Average speed (60s): 1.03 g/s | 1.13 g/s | 1.03 g/s Total: 3.20 g/s

Edit:
In case its ROCm: will provide ROCm builds in next version

qwep1

hero member

Activity: 610

Merit: 500

vega 56 0.47 (((

Lolliedieb

member

Activity: 433

Merit: 48

Yes, 5700 (XT) is currently a problem. Background is that one function compiles wrong and thus produces a low fidelity on the new code. I will try to find a way around that (else expected would be 0.9 g/s approx)

Other values from testing (0.9 Cuckatoo-31):
RX 580, 8G: 0.55 g/s
Vega 64: 1.15 g/s
Radeon VII: 1.53 g/s

Next days we will get a new 16G code (should push the VII over 1.75 g/s) and a new 4G as well (expected 0.4 g/s on RX 580 4G).

cikusa

jr. member

Activity: 39

Merit: 2

Can confirm there is no fix for 5700 series yet, only one that works is c31 and it is slow around 0.73gps

logicalray77

jr. member

Activity: 66

Merit: 4

Quote from: alucard20724 on October 23, 2019, 12:04:33 PM

Quote from: Lolminer001 on October 21, 2019, 02:23:37 PM

Will lol miner be getting an update to mine with amd rx5700xt

0.8.8 already works for 5700, for cuckatoo31, cuckarood29, equihash192, and equihash144. Doesn't hash from equihash125.

Any hashrate results?

Lolliedieb

member

Activity: 433

Merit: 48

Yes indeed it could be OC settings. The problem when you run settings that are good for ETH is that those are pushing memory a lot and same time give very low voltage to the compute core. But both Equihash and also the Grin algorithms are much more compute intense (and the algorithms are more sensitive for memory or cache bits flipping), so I rather would suggest to start with stock settings, then reduce core clock a bit (e.g. 10%) and then start to up mem clock and undervolt the core as long as it remains stable.

Alternatively some mining OSed (e.g. MMP OS) have already OC / UV profiles adjusted for the combination of mining software and card. That helps maxing out performance / watts rather easily

MATHReX

sr. member

Activity: 861

Merit: 281

Quote from: raptorman on October 28, 2019, 06:52:33 PM

Only one vega 64 card in a 8cards rig after 5-10 minutes go to 0 s/s hash. The others works fine. I tried increase the virtual memory but same problem. Do you have any idea what can I do? Other software with other algorithm works fine.

Just revet any OC that you have on that particular card and try again.
If it doesn't work, try replacing the riser. They are one of the major points of failure.

Quote from: zeef on November 10, 2019, 09:37:08 AM

Hi guys,

Its normal for an vega64 on beam do 26,5 sol? Cool

Increase memory and core clocks with voltages. It'll increase the hash rate but also power consumption. So, try to find a sweet spot for it.

ayiphelmy

copper member

Activity: 416

Merit: 105

Hai i got rejected share mining ZCl on 2miners is there something i must put in commandline? i already put --coin AUTO192_7 but still not working.... maybe someone can tell me??

Thanks

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