lolMiner 1.64: Fastest Kaspa miner in market

[misterkit]

Might have a bug.  I'm running a mixed rig of vega 64s and 56's.   The first gpu progressively loses hashrate while the others fluctuate up or down.  Restarting the miner puts the first gpu back up to where id expect it and it starts all over again.  Im on win 10 amd driver 19.1.1

Small update...the first card seems to settle down and stop dropping after a little bit.  It starts out hashing arpund 18/19 sols and then eventually drops to 14/15. After restart its right back at 18 again.

Im on the latest alpha release mining beam.

[1695290024]

1695290024

[1695290024]

1695290024

[gaalx01]

488 - 10.5. Vega56 - 17-19, ok?

could you share your vega 56 clock set up?

18.5.1 driver. default.

[joeykolb]

the suprnova difficulty is 400m on BEAM, and the other  pool diff, is 256m, its a difference. just saying

[The Godfather]

I dont see in first post or answer to previous question about clock from command line from miner?
How do you clock amd cards on linux ?

[Lolliedieb]

Might have a bug.  I'm running a mixed rig of vega 64s and 56's.   The first gpu progressively loses hashrate while the others fluctuate up or down.  Restarting the miner puts the first gpu back up to where id expect it and it starts all over again.  Im on win 10 amd driver 19.1.1

Small update...the first card seems to settle down and stop dropping after a little bit.  It starts out hashing arpund 18/19 sols and then eventually drops to 14/15. After restart its right back at 18 again.

Im on the latest alpha release mining beam.

How long does it take for the card to loose speed?

Because I observe at my 580 that it starts rather quickly but then looses some hash when it gets to warm / reaches power limit - can you try reading a temperature curve aside of the run? Here adding one fan already helped, but what helped more (also good for energy bill) was to do some undervolting

--------

Hello,

The lolminer 0.6 miner random say this: The gpu 00 is stucked, and than miner quit.
I have to restart the miner to mine again.

What is the problem? 1 card is wrong? My cards are rx vega 64.

Thanks the help.

On which coin does this happen? I am currently integrating all the other coins to lolMiner 0.7 branch and would like to review codes to reduce potential lock ups

--------

so, this miner lolminer v07 alpha 5, si multiminer? what coin can mine beside the beam?

The 0.7 branch currently can only do beam, but I am right now working on bringing back the other algorithms as well ( Equihash 144/5, 192 / 7, 210/9 and 96/5)

--------

I am a bit desparate. I can not get my Vegas to work with this miner, while other miners work fine. It only hashes on 3-4 of 6 cards and the rest shows 0 sol/s.

Well BEAM (Equihash 150/5) has an extreme amount of host memory use (in Windows) when you want to start up your cards. For many users the solution is to add tons of virtual memory over the Windows page file.

[joeykolb]

u put like this ?after the x........ --pass x --tls 0   at the end?

{
   "DEFAULTS" : {
      "DEVICES" : "AUTO",    
      "APIPORT" : 0
                "TLS" : 0
   },
or like this

[hustleman]

Might have a bug.  I'm running a mixed rig of vega 64s and 56's.   The first gpu progressively loses hashrate while the others fluctuate up or down.  Restarting the miner puts the first gpu back up to where id expect it and it starts all over again.  Im on win 10 amd driver 19.1.1

Small update...the first card seems to settle down and stop dropping after a little bit.  It starts out hashing arpund 18/19 sols and then eventually drops to 14/15. After restart its right back at 18 again.

Im on the latest alpha release mining beam.

How long does it take for the card to loose speed?

Because I observe at my 580 that it starts rather quickly but then looses some hash when it gets to warm / reaches power limit - can you try reading a temperature curve aside of the run? Here adding one fan already helped, but what helped more (also good for energy bill) was to do some undervolting

--------

Hello,

The lolminer 0.6 miner random say this: The gpu 00 is stucked, and than miner quit.
I have to restart the miner to mine again.

What is the problem? 1 card is wrong? My cards are rx vega 64.

Thanks the help.

On which coin does this happen? I am currently integrating all the other coins to lolMiner 0.7 branch and would like to review codes to reduce potential lock ups

--------

so, this miner lolminer v07 alpha 5, si multiminer? what coin can mine beside the beam?

The 0.7 branch currently can only do beam, but I am right now working on bringing back the other algorithms as well ( Equihash 144/5, 192 / 7, 210/9 and 96/5)

--------

I am a bit desparate. I can not get my Vegas to work with this miner, while other miners work fine. It only hashes on 3-4 of 6 cards and the rest shows 0 sol/s.

Well BEAM (Equihash 150/5) has an extreme amount of host memory use (in Windows) when you want to start up your cards. For many users the solution is to add tons of virtual memory over the Windows page file.

Does Lolminer support OC and undervolting of core and memory in the command line?

[mehrdadb3]

hello guys
is therer any command for use in lolminer line for undervolt mem and gpu
like claymore command -cclock  -mclock  -cvddc

[sp_]

Tested beam on the R9 Fury Nano and r9 390's

15.2 sol on the nano.
12.5sol on the 390 gigabyte g1 gaming

Pretty good, bether than the 580's

[UnclWish]

Tested beam on the R9 Fury Nano and r9 390's

15.2 sol on the nano.
12.5sol on the 390 gigabyte g1 gaming

Pretty good, bether than the 580's

580 gives 12.5-13 for about 100-120Wt. Your cards take more power.

[4ward]

@Lolliedieb

Can you add a Gpu Platform parameter (either Index or AMD/NVIDIA) so it would be possible to specify devices in more predictable manner on a mixed rig?
something like "-platform AMD -devices 0,1,2" and "-platform NVIDIA -devices 0,1,2" or "-platform 0 -devices 0,1,2"

[misterkit]

Might have a bug.  I'm running a mixed rig of vega 64s and 56's.   The first gpu progressively loses hashrate while the others fluctuate up or down.  Restarting the miner puts the first gpu back up to where id expect it and it starts all over again.  Im on win 10 amd driver 19.1.1

Small update...the first card seems to settle down and stop dropping after a little bit.  It starts out hashing arpund 18/19 sols and then eventually drops to 14/15. After restart its right back at 18 again.

Im on the latest alpha release mining beam.

How long does it take for the card to loose speed?

I've DDU'd the drivers and reinstalled and it seems to be stable now however I think this may have something to do with the OverDrive settings.  

The rig has 9 cards in it, 4 of which are Vega 64's.  Before DDU & Reinstall it would happen on the first and last 64 almost immediately.  

For anyone that is seeing 22+ SOLs with a Vega 64 would you mind posting your P7 and P3 values?

My Vega 64s are doing the same #s as my 56's...even though the clocks are different.

[Divinity666]

Have just tried mining beam with my R9 Fury cards, got 16.5Sol@150Wt. Well, at least this miner does support Fiji ))

[Lolliedieb]

u put like this ?after the x........ --pass x --tls 0   at the end?

{
   "DEFAULTS" : {
      "DEVICES" : "AUTO",    
      "APIPORT" : 0
                "TLS" : 0
   },
or like this

Yes, to turn TLS off you need --tls 0 ... if you do failover pool do --tls 0,1,1,0 with one entry per pool.

For the config file the way you did it is almost right, but behind the "APIPORT" line a "," is missing to complete right json syntax.

---------

@Lolliedieb

Can you add a Gpu Platform parameter (either Index or AMD/NVIDIA) so it would be possible to specify devices in more predictable manner on a mixed rig?
something like "-platform AMD -devices 0,1,2" and "-platform NVIDIA -devices 0,1,2" or "-platform 0 -devices 0,1,2"

Well --devices already understands that. Doing --devices AMD will only select the AMD devices and will keep all Nvidias idle for other task. With --devices NVIDIA its exactly fliped.

---------

hello guys
is therer any command for use in lolminer line for undervolt mem and gpu
like claymore command -cclock  -mclock  -cvddc

No, atm not. It will come maybe some time, but till now I found no proper way doing this cross platform and for both AMD and Nvidia. Maybe I will do some research on this, but right now my priority is rather bringing back the other algorithms to lolMiner 0.7 and then improving the algorithms and of cause adding new. Pretty lot to do xD

[4ward]

---------

@Lolliedieb

Can you add a Gpu Platform parameter (either Index or AMD/NVIDIA) so it would be possible to specify devices in more predictable manner on a mixed rig?
something like "-platform AMD -devices 0,1,2" and "-platform NVIDIA -devices 0,1,2" or "-platform 0 -devices 0,1,2"

Well --devices already understands that. Doing --devices AMD will only select the AMD devices and will keep all Nvidias idle for other task. With --devices NVIDIA its exactly fliped.

I know, but this works if you want to use all AMD or NVIDIA devices, but not specific ones.

I will explain an exact use case:
I develop Forager (in my signature) and I allow creating DeviceGroups based on card types.
Different cards can have different optimal miner/algo
So if a rig has for example 2 different AMD cards and some NVIDIA (or the other way around), I don't have a way to predict which card gets which device index in lolMiner.

With most miners (almost all actually) I can either set platform (opencl platform id, example - sgminer) + device list or set nvidia/amd flag (example Claymore/Ethminer/BMiner) + devicelist

[zhihao4456]

I would like to mine Beam with this miner. May I know what are the overclock settings should I do for my RX580 8GB cards to get the most sols? Like how much core, memory, voltage and etc? Would like to know the efficient way to mine for this card for BEAM. THanks

[Andartis]

I am a bit desparate. I can not get my Vegas to work with this miner, while other miners work fine. It only hashes on 3-4 of 6 cards and the rest shows 0 sol/s.

Well BEAM (Equihash 150/5) has an extreme amount of host memory use (in Windows) when you want to start up your cards. For many users the solution is to add tons of virtual memory over the Windows page file.

I have 16GB of RAM and a pagefilesize of 128GB.

[misterkit]

No matter what settings I try in Overdrive I can not get the Vega 64's to perform (on average) higher than what my Vega 56's are doing.  I seem to get a consistent 18-20 SOLs.   I'm on Win 10, driver 19.1.1.  Pagefile is set to 120GB to use across 9 cards.

Does this have something to do with LoLminer?

For an upcoming release, would it be possible to add stats like fan speed, temp, and watts? 

[misterkit]

I put the vega 64 back to factory mem/speed settings. Sol rate dropped by quite a bit.  It would seem the rate gets better the slower and less voltage is applied.  No advantage that I can see for a 64 at this point.

[VoskCoin]

I created an updated video guide on mining beam

In the updated guide I walkthrough mining beam with AMD GPUs -- I am using the latest lolminer build and include my config for leafpool -- you can simply download it and swap my beam address with yours so you are mining to your own wallet in seconds. Hope it helps

https://www.youtube.com/watch?v=tqPEd_3tCDU