lolMiner 1.64: Fastest Kaspa miner in market

[jgonzi]

testing lolminer over phoenix.  must say, impressive power reduction on NAVI...im running 10x5700(non XT) on MSOS(linux)good hashrate and temps. 

Are you measuring power at the wall with a killawatt/power meter?  Or is this just in software reporting?

In software is less than in Wall always... why? because of the quality of the PSU... unless the GPU is in the Sweet post with PhoenixMiner... much load normaly is less efficiency, and with Phoenixminer you will have more load because he hasn't got a Navi Optimisation for Watts.

[digital$]

aside from the wattage optimization..pool side hash reflecting better numbers as well.  am i correct in understanding...miner doesn't disconnect and reconnect for devfee like phoenix?   

[jgonzi]

aside from the wattage optimization..pool side hash reflecting better numbers as well.  am i correct in understanding...miner doesn't disconnect and reconnect for devfee like phoenix?   

You are complete right... that was one of the works the developer did to reduce time lost on the fee.

[EthosRIG]

Hi guys, I do have a rig with 6 cards, 3 with 8GB memory and 3 with 4GB memory. Now that ETH is ways more profitable compared to other coins I was thinking about dual mine.

ETH with the 8GB cards and BEAM or other ethash coins with the 4GB cards. Can lolminer do it? I can't find anything about.

Now I am mining ETH with all cards but the 4GB ones are in zombie mode because of the DAG size and they loose around 2mhs every epoch change...

Thanks in advance for the help.

You should run 2 instances, with the --devices parameter

My understanding is that that parameter understands --devices AMD and --devices NVIDIA. I have AMD only. I need to mine ETH with 3 8GB cards and BEAM with the remaining 4GB cards.

In addition to the above if I run twice lolminer with two different strings how can it work? I mean how is the JSON and config file going to be?

 

[jgonzi]

Hi guys, I do have a rig with 6 cards, 3 with 8GB memory and 3 with 4GB memory. Now that ETH is ways more profitable compared to other coins I was thinking about dual mine.

ETH with the 8GB cards and BEAM or other ethash coins with the 4GB cards. Can lolminer do it? I can't find anything about.

Now I am mining ETH with all cards but the 4GB ones are in zombie mode because of the DAG size and they loose around 2mhs every epoch change...

Thanks in advance for the help.

You should run 2 instances, with the --devices parameter

My understanding is that that parameter understands --devices AMD and --devices NVIDIA. I have AMD only. I need to mine ETH with 3 8GB cards and BEAM with the remaining 4GB cards.

In addition to the above if I run twice lolminer with two different strings how can it work? I mean how is the JSON and config file going to be?

 

It is not possible... you should add it as a custom miner and launch 2 miners... or launch one with the normal launch and other manual or semiautomatic  in a shell...

[Lolliedieb]

My understanding is that that parameter understands --devices AMD and --devices NVIDIA. I have AMD only. I need to mine ETH with 3 8GB cards and BEAM with the remaining 4GB cards.

In addition to the above if I run twice lolminer with two different strings how can it work? I mean how is the JSON and config file going to be?

It understand --devices AMD and --devices Nvidia or alternatively you can use --devices 0,1,2,4 to skip e.g. 4th card (index 3) in the system.
So you can indeed open two miner windows where one is pointed to Ethash and one to Beam, both using just different devices strings.

In json the configuration is 100% same
"DEVICES" : "0,1,2",
will select first 3 cards,
"DEVICES" : "3,4,5",
will select the 2nd set.

[EthosRIG]

Thanks guys, very very good. I will try.

Now let's say I don't want to change EthOS because I don't have time (even if I am aware I should change it with a normal lightweight linux distro....). Can I let EthOS start lolminer at the startup with his own lolminer? And after it is mining to launch another lolminer for the 4GB cards?
Or do I need to disallow the miner launch from Ethos and launch the two miners indipendently?

Also I noticed the last lolminer available in Ethos repo is the 1.16. Is it an issue to let him run the 1.16, download the 1.17 and run a string from that folder?

[jgonzi]

Thanks guys, very very good. I will try.

Now let's say I don't want to change EthOS because I don't have time (even if I am aware I should change it with a normal lightweight linux distro....). Can I let EthOS start lolminer at the startup with his own lolminer? And after it is mining to launch another lolminer for the 4GB cards?
Or do I need to disallow the miner launch from Ethos and launch the two miners indipendently?

Also I noticed the last lolminer available in Ethos repo is the 1.16. Is it an issue to let him run the 1.16, download the 1.17 and run a string from that folder?

Yes you can download and overwrite your lolMiner versiob 1.16 file...

[Lolliedieb]

Just wanted to tell you I just pushed the Linux build of lolMiner 1.18 
(The Windows one will follow within 24 hrs)

Here is the repo link

This time especially some more candy for my beloved zombie mode users:

Feature Updates:

•     Improved linux zombie mode power draw & speed Polaris GPUs (R9 380, RX Fury, RX 4x0 and RX 5x0). Depending on configuration, the zombie mode now uses 0.5 to 1W less energy and is 0.2 to 0.4 mh/s faster.
•     Added --zombie-tune parameter for Polaris GPUs. This will increase the performance of zombie mode (further up on the general improvement) by an other 5-15%, depending on parameter and epoch (later epochs profit more). Default value is 0 (off), for most cards the value of 2 is optimal. If you see cards getting slower then before, set to 0 or 1. Note: you either can give one value for the whole rig or provide a comma separated list for each card individually. Cards not running zombie mode ignore the parameter.
•     The parameter --4g-alloc-size can now also be set for each card individually
•     Slight rework of Beam Hash III back end. Improves poolside hash rate by approx 0.2 to 0.3% - displayed hashrate and power consume kept equal.
•     Added a 4G_Ethash_Linux_Readme.txt file to the Linux release, giving guidance how to configure for ideal zombie mode performance.

Fixes:

•     Segmentation fault when the dns resolve of a pool fails
•     Miner does not restart after connection loss.
•     Applied potential fix for "address or port already in use" bug.

Please read the new 4G_Ethash_Linux_Readme.txt carefully to know how to configure the miner for ideal zombie mode performance.

[EthosRIG]

Thanks guys, very very good. I will try.

Now let's say I don't want to change EthOS because I don't have time (even if I am aware I should change it with a normal lightweight linux distro....). Can I let EthOS start lolminer at the startup with his own lolminer? And after it is mining to launch another lolminer for the 4GB cards?
Or do I need to disallow the miner launch from Ethos and launch the two miners indipendently?

Also I noticed the last lolminer available in Ethos repo is the 1.16. Is it an issue to let him run the 1.16, download the 1.17 and run a string from that folder?

Yes you can download and overwrite your lolMiner versiob 1.16 file...

Do you mean to overwrite the script only inside the folder that contains all the supported miners? Are the other files (if any) the same between 1.16 and 1.18? Please confirm
Because I would like to overwrite the 1.16 with the 1.18 one. Our best friend Lolliedieb is killing it  . I need to try the new parameters as soon as possible.

Thank you Lolliedieb for the hard work. With the ETH prices going crazy like this, every additional mhs and every additional hour we can mine ETH is a big gift ;-)

[miner29]

Thanks guys, very very good. I will try.

Now let's say I don't want to change EthOS because I don't have time (even if I am aware I should change it with a normal lightweight linux distro....). Can I let EthOS start lolminer at the startup with his own lolminer? And after it is mining to launch another lolminer for the 4GB cards?
Or do I need to disallow the miner launch from Ethos and launch the two miners indipendently?

Also I noticed the last lolminer available in Ethos repo is the 1.16. Is it an issue to let him run the 1.16, download the 1.17 and run a string from that folder?

Yes you can download and overwrite your lolMiner versiob 1.16 file...

Do you mean to overwrite the script only inside the folder that contains all the supported miners? Are the other files (if any) the same between 1.16 and 1.18? Please confirm
Because I would like to overwrite the 1.16 with the 1.18 one. Our best friend Lolliedieb is killing it  . I need to try the new parameters as soon as possible.

Thank you Lolliedieb for the hard work. With the ETH prices going crazy like this, every additional mhs and every additional hour we can mine ETH is a big gift ;-)

If you are on Ethos you can go to /opt/miners/lolminer and change out for the newest version.  All files are in that folder only.  As long as you stick the new version in the right folder Ethos will see it and work with it.

[rigomortis]

Bravo Mr Developer!!  I just used your new zombie setting and getting over 2mh/s more on my 4gb cards. Hashing now at 22.9mh/s!!! 

[EthosRIG]

Just wanted to tell you I just pushed the Linux build of lolMiner 1.18 
(The Windows one will follow within 24 hrs)

Here is the repo link

This time especially some more candy for my beloved zombie mode users:

Feature Updates:

•     Improved linux zombie mode power draw & speed Polaris GPUs (R9 380, RX Fury, RX 4x0 and RX 5x0). Depending on configuration, the zombie mode now uses 0.5 to 1W less energy and is 0.2 to 0.4 mh/s faster.
•     Added --zombie-tune parameter for Polaris GPUs. This will increase the performance of zombie mode (further up on the general improvement) by an other 5-15%, depending on parameter and epoch (later epochs profit more). Default value is 0 (off), for most cards the value of 2 is optimal. If you see cards getting slower then before, set to 0 or 1. Note: you either can give one value for the whole rig or provide a comma separated list for each card individually. Cards not running zombie mode ignore the parameter.
•     The parameter --4g-alloc-size can now also be set for each card individually
•     Slight rework of Beam Hash III back end. Improves poolside hash rate by approx 0.2 to 0.3% - displayed hashrate and power consume kept equal.
•     Added a 4G_Ethash_Linux_Readme.txt file to the Linux release, giving guidance how to configure for ideal zombie mode performance.

Fixes:

•     Segmentation fault when the dns resolve of a pool fails
•     Miner does not restart after connection loss.
•     Applied potential fix for "address or port already in use" bug.

Please read the new 4G_Ethash_Linux_Readme.txt carefully to know how to configure the miner for ideal zombie mode performance.

For God's sake!!! You are the man!!!
I was getting 20mhs from my RX570 4GB and now they are pushing 23.6 mhs!!! Amazing!!!

On the other hand I was getting 30.3mhs from the 570s 8GB (same rig) and now they are pushing 29.8mhs
But it is OK!!! The grand total is around 13mhs higer than before. I guess the shares will follow ;-)

[EthosRIG]

ah...big thank you to miner29.

I did what you said and booooommmm Ethos running the 1.18 ;-)

[FloppyPurpleGherkin]

Top work dude 

[Ortadan]

In RaveOS the latest version does not work, when starting the miner the platform it restarts using version 1.18 and 1.18A (worker_rebooting_by_flag_auto) this happens in my two 4GB platforms, instead version 1.17 works perfectly in both.

Am I doing something wrong or is it a problem with the version included in RaveOs?

[rigomortis]

In RaveOS the latest version does not work, when starting the miner the platform it restarts using version 1.18 and 1.18A (worker_rebooting_by_flag_auto) this happens in my two 4GB platforms, instead version 1.17 works perfectly in both.

Am I doing something wrong or is it a problem with the version included in RaveOs?

check your overclocks.  might have to dial them down for the miner to start

[jgonzi]

In RaveOS the latest version does not work, when starting the miner the platform it restarts using version 1.18 and 1.18A (worker_rebooting_by_flag_auto) this happens in my two 4GB platforms, instead version 1.17 works perfectly in both.

Am I doing something wrong or is it a problem with the version included in RaveOs?

Can you put a screenshot of the log?

Or add in the configuration to test (only a fast test)

--4g-alloc-size 4066,4080,4080,...

Put 1st card with 4066 and the other with max speed...

Let's try to see if we find the problem

[RAKOT]

to @Developer.

Thank you very much for correcting access to api from outside.

Very appreciated.

Best Regards.

[Desash]

Hey!

Run the last version on Windows 10. MSI RX480 4Gb shows 11.5Mhs with ETH. Is it Ok? I counted on 20 Mhs.  
Thanks in advance!