lolMiner 1.64: Fastest Kaspa miner in market

[Lolliedieb]

Another question:
RX 580-8 rig. On 1st card of rig when monitor connected and trying to look video on youtube or play any videofile (even in bad quality f.e. 320p) video playback goes with freezes. On all other miners (Claymore, TR, PM) video plays without problems during eth mining.

It might be, because my miner has no pauses between kernel calls ... it has two threads to keep the card busy ... Will need to think about this.

I've got no positive results on RX 470 4GB rig even I tried all different miners including the new lol miner 1.16.
I haven't change the old blockchain driver and the result is still poor, max 10 Mh/s for the whole rig.
Now I'm waiting for ETC Thanos fork at the end of November.

Can you share more info e.g. driver and operation system? I am running my 580 4G with still 15 mh/s on ETC epoch 388 in Linux with 20.40 drivers.



Wrt this 6800 stuff: it is indeed strange using the same card 2x. Why this works and if we can replicate this to get the speedup on other systems: not yet sure. Still awaiting an own 6800 for tests, the card to test the miner was a remote one where a friend allowed me to check it out - and there it was only shown as one card.

[jgonzi]

Is there any new about the 6800 x 2 GPU?...

With the limit of bandwith that numbers doesn't seem normal... let's see

[preda]

i am not able to mine etc+zil wit lolminer someone can helps? thanks

[abarth23]

Which are the best drivers to use with lolminer 1.16 for rx570 4gb?

[jgonzi]

Which are the best drivers to use with lolminer 1.16 for rx570 4gb?

One of the best drivers now is 20.30, the 20.40 is having some problems on som Linux versions.

For mining in Windows, one of the best is 20.4.2.

[abarth23]

thank you so much for your help

[Lolliedieb]

i am not able to mine etc+zil wit lolminer someone can helps? thanks

Can you give some details about the problem? e.g. cards, driver, error messages - the more details we have the quicker we get it going

[biblioteczny]

What could be the reason for this message?
"GPU 1: Allocation of DAG failed with error: Memory object allocation failure GPU 1: will be stopped."

I tried to use lolMiner 1.15 and 1.16 - same error.
GPU 1 is a RX 5700 XT 8GB from PowerColor.

[Lolliedieb]

What could be the reason for this message?
"GPU 1: Allocation of DAG failed with error: Memory object allocation failure GPU 1: will be stopped."

I tried to use lolMiner 1.15 and 1.16 - same error.
GPU 1 is a RX 5700 XT 8GB from PowerColor.

That is an interesting one. Usually should not happen... unless... is this Linux and if yes: which kernel version do you use please (you can find out with "uname -r")

[biblioteczny]

What could be the reason for this message?
"GPU 1: Allocation of DAG failed with error: Memory object allocation failure GPU 1: will be stopped."

I tried to use lolMiner 1.15 and 1.16 - same error.
GPU 1 is a RX 5700 XT 8GB from PowerColor.

That is an interesting one. Usually should not happen... unless... is this Linux and if yes: which kernel version do you use please (you can find out with "uname -r")

It is Windows 10, not Linux.

[jgonzi]

What could be the reason for this message?
"GPU 1: Allocation of DAG failed with error: Memory object allocation failure GPU 1: will be stopped."

I tried to use lolMiner 1.15 and 1.16 - same error.
GPU 1 is a RX 5700 XT 8GB from PowerColor.

That is an interesting one. Usually should not happen... unless... is this Linux and if yes: which kernel version do you use please (you can find out with "uname -r")

It is Windows 10, not Linux.

Can you put a screenshot or the GPUZ Information to see if that could help to find the problem

[Pe_Da]

Its time to say hello to lolMiner 1.16.

You can load it here: https://github.com/Lolliedieb/lolMiner-releases/releases/tag/1.16

Here is the - again not so short - change log

•     Added support of Ethash and Beam Hash III for RX 6000 generation of GPUs
•     All supported algorithms now show the share difficulty and have best share statistics.
•     New feature: use --rebuild-defect n to trigger a rebuild of DAG if a GPU produced n defect shares on the current one. Default is 3, use 0 to deactivate this feature.
•     New feature: Use --workmulti n to modify the amount of Ethash work a GPU does per batch. Higher values will cause less CPU load but more stale shares, lower values will give less stale shares but higher CPU load. Performance may vary for different values. Default is 128. 
•     New feature: if Ethash pool disconnects within 2 seconds from connection attempt (immediate reconnect), then the other stratum mode is tested to login.
•     New feature: AMD Vega and newer cards now display memory temperature in statistics & api (only visible if there is at least one such GPU in the rig).
•     Default ethstratum changed from ETHV1 to ETHPROXY for better pool compatibility.
•     Stratum pool addresses now understand "stratum+tcp://", "stratum+ssl://" and "ssl://" prefixes (turning on or of ssl / tls automatically) for better compatibility with existing configurations.   
•     Slightly reduced CPU load when mining Ethash
•     New coloring scheme with more friendly colors. For terminals that do not have rgb colors (e.g. shellinabox) use --basecolor to restrict to a simpler set. Use --nocolor to deactivate coloring completely.
•     Fixed bug: Cards may crash when switching from ZIL cache back to normal mining.
•     Fixed bug: Wavy hashrate - especially for rigs with many AMD Navi GPUs.
•     Fixed bug: (Linux:) Watchdog not called when a GPU is stuck & extremely high CPU load on crashed GPU. (1)
•     Fixed bug: Hashrate reporting not working on some pools (e.g. sparkpool)
•     Fixed bug: Miner can crash after trying to reconnect to same pool over 5 minutes.
•     Fixed bug: Miner crashes when mixing TLS and non-TLS pools for fail-over.

So pretty lot of new stuff - new cards added (I must say: 6800 is slower then most have hoped, but energy efficiency is damn impressive) - new colors (hope you like it) and a ton of fixes

-----------------------------

I will do an update after changing the all farm.

Sadly no watts reduction this time - only some CPU stuff / speed stability fixes
But next I will likely put hands to code again to see what we can do

Can you implement an option for minimal rig speed and restart if that speed is lower?
I am using lolminer through SMOS and several times now I found it to be working with 0 H/s.

Problem is: if an amd card drops to 0, then usually the full card is stuck and can not recover unless you reboot the rig. In fact if you try to touch it again often the rig will completely lock up, so system reboot does not work via terminal - you then often need to power cycle it by hand. To cover this the new version finally should be able to trigger restart scripts gracefully. Also smos should be able to detect the 0 hr and reboot - or isn't it.
By the way if a card is most of the time stable but then does suddenly fall to 0 its often its voltage is one small bit to low for current settings. Increase it by 5 or 10mV and see if card stable then again.

Is there a chance of a speed up of the RX6000 Series Cards because the new "Infinity Cache" or "Smart Access Memory"?

[Lolliedieb]

It is Windows 10, not Linux.

Which driver version you are on and have you checked other values for --keepfree and --4G-alloc-size like described in the 4G_Windows_Readme.txt?

Is there a chance of a speed up of the RX6000 Series Cards because the new "Infinity Cache" or "Smart Access Memory"?

Well wrt SAM I am not sure yet what effects that has. On ethash you see the impact of the cache when building the DAG (way faster then on RX 5700 although bandwidth did not grow that much) and when mining ZIl, cause that uses a 1G dag that fits to over 12% into the cache - there the card is about 10% faster then for the 4G dag. For other algos I still try to understand how to use it ideally. Generally the card already is the fastest Equihash card among all AMDs (reaching 90+ sol/s on BTG) and its 2nd fastest on Beam. I got good hope to profit from the cache in Beam and Grin C32.

[Pe_Da]

It is Windows 10, not Linux.

Which driver version you are on and have you checked other values for --keepfree and --4G-alloc-size like described in the 4G_Windows_Readme.txt?

Is there a chance of a speed up of the RX6000 Series Cards because the new "Infinity Cache" or "Smart Access Memory"?

Well wrt SAM I am not sure yet what effects that has. On ethash you see the impact of the cache when building the DAG (way faster then on RX 5700 although bandwidth did not grow that much) and when mining ZIl, cause that uses a 1G dag that fits to over 12% into the cache - there the card is about 10% faster then for the 4G dag. For other algos I still try to understand how to use it ideally. Generally the card already is the fastest Equihash card among all AMDs (reaching 90+ sol/s on BTG) and its 2nd fastest on Beam. I got good hope to profit from the cache in Beam and Grin C32.

Thank you for the quick answer, sounds promising!

And another question, the new Octopus algo is promising at nVidia, is there a plan to implement these in your miner for AMD?

[Lolliedieb]

Quick info for upcoming ETC hardfork (in few hours):

lolMiner 1.16 (and the versions before) is ready to support the fork that will happen on block 11 700 000.
To automatically switch over to the new scheme use --algo ETCHASH when you run the miner manually.

If you are using a mining OS like HiveOS, please select ETC or ETCHASH as parameter in your flight sheet.
In case you can not change it or are uncertain you alternatively can add --enable-ecip1099 to your extra user configuration parameters.

Note that ETCHASH = ETHASH + ECIP 1099, so the result will be the same and you can safely add  --enable-ecip1099 to any working configuration without damaging it.


All of this also applies when you mine ETC+ZIL! In this case just configure for ETC mining - the miner will recognize the ZIL mining and switch to ETHASH for that time and switch back to ETCHASH once Zil mining is over.
Have fun with the fork.



--------------

And another question, the new Octopus algo is promising at nVidia, is there a plan to implement these in your miner for AMD?

I answered about this one few pages earlier. Octupus is extremely compute heavy, in particular multiplication of two 32 bit numbers to a 64 bit one. While Turing and Ampere can do this operation using only one clock cycle, the AMDs need 4 (professional cards & Vii) to 8 clock cycles. Also Turning and Ampere can do easier operations in parallel. Therefore the expected performance on AMD is rather ... horrible. I did some tests but was way away from the two modern Nvidia numbers here. It might be that big navi can do better, but the full instruction set for this architecture is not yet released. Waiting for that if this allows some quicker approach.

[KGSGRP.ITA]

Driver Requirement:
Nvidia:
Cuda 10 or 11
AMD:
- Big Navi: amdgpu-pro 20.40 (Linux) / Adrenaline 20.11.2 (Windows) and newer.
- Navi: amdgpu-pro 19.30 (Linux) /  Adrenaline 19.10.02 (Windows) and newer.
- Vega: amdgpu-pro 18.50 (Linux) /  Adrenaline 18.10 (Windows) and newer.
- older cards: Blockchain drivers and newer

My operating system:
Win 10 x64
GPUS: AMD Rx 480 GPU
What video driver should I install? Which version?
Which version of lolMiner is recommended?

I have another operating system:
Win 7 x64
GPUS: AMD RX480
What video driver should I install? Which version?
Which version of lolMiner is recommended?

Sorry for not good english

[miner29]

Driver Requirement:
Nvidia:
Cuda 10 or 11
AMD:
- Big Navi: amdgpu-pro 20.40 (Linux) / Adrenaline 20.11.2 (Windows) and newer.
- Navi: amdgpu-pro 19.30 (Linux) /  Adrenaline 19.10.02 (Windows) and newer.
- Vega: amdgpu-pro 18.50 (Linux) /  Adrenaline 18.10 (Windows) and newer.
- older cards: Blockchain drivers and newer

My operating system:
Win 10 x64
GPUS: AMD Rx 480 GPU
What video driver should I install? Which version?
Which version of lolMiner is recommended?

I have another operating system:
Win 7 x64
GPUS: AMD RX480
What video driver should I install? Which version?
Which version of lolMiner is recommended?

Sorry for not good english

Well the instructions you quoted say Blockchain and Newer drivers.  Win 7 probably want to go to win 10.  Current version lolminer 1.16.

[KGSGRP.ITA]

Well the instructions you quoted say Blockchain and Newer drivers.  Win 7 probably want to go to win 10.  Current version lolminer 1.16.

[/b]

Which ones are they? I don't understand which ones it refers to. Do you have a link to download?

[miner29]

Well the instructions you quoted say Blockchain and Newer drivers.  Win 7 probably want to go to win 10.  Current version lolminer 1.16.

[/b]

Which ones are they? I don't understand which ones it refers to. Do you have a link to download?

You quoted the instructions for lol....in your message.....

So go to AMD site and download newest driver for Polaris cards (your RX 480 are polaris cards)

https://www.amd.com/en/support

The scroll up through thread and see link from lol for 1.16....
It is literally 5 posts before this one....

https://github.com/Lolliedieb/lolMiner-releases/releases/tag/1.16

[jgonzi]

Well the instructions you quoted say Blockchain and Newer drivers.  Win 7 probably want to go to win 10.  Current version lolminer 1.16.

[/b]

Which ones are they? I don't understand which ones it refers to. Do you have a link to download?

You quoted the instructions for lol....in your message.....

So go to AMD site and download newest driver for Polaris cards (your RX 480 are polaris cards)

https://www.amd.com/en/support

The scroll up through thread and see link from lol for 1.16....
It is literally 5 posts before this one....

https://github.com/Lolliedieb/lolMiner-releases/releases/tag/1.16

You are right... one of the best drivers is 20.4.2, why I say this version, because it is also the last one that works perfectly with MSI Afterburner and also with OverDriveNTool... that is really helps to configure voltage of the memory cards.

Let's enjoy in 20min the autofork to ETCHASH