Topic: lolMiner 1.64: Fastest Kaspa miner in market - page 22. (Read 155326 times)
Nice... I have updated to HiveOS today and RaveOS. So ready to use it
Now getting 55.3mhs and 53mhs from my 2 rtx 3070ti's.
Small improement with latest update.
Thanks for the hard work
Small improement with latest update.
Thanks for the hard work
Really good values, what OC are you having?.
For me the easy now is the same flighsheet for all rigs with the new 1.33, that's perfect for modifications and changes. I don't need to change flightsheet if I take a GPU or add a new one.
+2000 memory
1200 locked core
170w power limit
Now getting 55.3mhs and 53mhs from my 2 rtx 3070ti's.
Small improement with latest update.
Thanks for the hard work
Small improement with latest update.
Thanks for the hard work
Really good values, what OC are you having?.
For me the easy now is the same flighsheet for all rigs with the new 1.33, that's perfect for modifications and changes. I don't need to change flightsheet if I take a GPU or add a new one.
Now getting 55.3mhs and 53mhs from my 2 rtx 3070ti's.
Small improement with latest update.
Thanks for the hard work
Small improement with latest update.
Thanks for the hard work
Trying different option for a 3060 RIG v2.
100Mhs at 80W
110Mhs at 100W
The efficiency in the 100Mhs is really good...
Core 1185
Memory 1750
PL 110
It is really a nice sweetpost
Trying different option for a 3060 RIG v2.
100Mhs at 80W
110Mhs at 100W
The efficiency in the 100Mhs is really good...
System: Amd rx 470-480 8GB GPU's
Algo : Ethash - ETH
Tested drivers : AMd 18.20 - 20.30 - 20.40
Operation system : Linux (Simplemining)
Q:
Why Lolminer no tolerance about OC ?
All my GPU's mine with same OC value with other miners (no stale - no reject or reboot ) but when i use Lolminer too many GPU's start error and reboot.
Because of this i need to lower my OC settings drastically with Lolminer
Is anyone else experiencing this?
Algo : Ethash - ETH
Tested drivers : AMd 18.20 - 20.30 - 20.40
Operation system : Linux (Simplemining)
Q:
Why Lolminer no tolerance about OC ?
All my GPU's mine with same OC value with other miners (no stale - no reject or reboot ) but when i use Lolminer too many GPU's start error and reboot.
Because of this i need to lower my OC settings drastically with Lolminer
Is anyone else experiencing this?
Have you been able to share your OC to try to help?
System: Amd rx 470-480 8GB GPU's
Algo : Ethash - ETH
Tested drivers : AMd 18.20 - 20.30 - 20.40
Operation system : Linux (Simplemining)
Q:
Why Lolminer no tolerance about OC ?
All my GPU's mine with same OC value with other miners (no stale - no reject or reboot ) but when i use Lolminer too many GPU's start error and reboot.
Because of this i need to lower my OC settings drastically with Lolminer
Is anyone else experiencing this?
Algo : Ethash - ETH
Tested drivers : AMd 18.20 - 20.30 - 20.40
Operation system : Linux (Simplemining)
Q:
Why Lolminer no tolerance about OC ?
All my GPU's mine with same OC value with other miners (no stale - no reject or reboot ) but when i use Lolminer too many GPU's start error and reboot.
Because of this i need to lower my OC settings drastically with Lolminer
Is anyone else experiencing this?
phoenix miner is the best so far for rx series. it has a lot parameter to tweak
System: Amd rx 470-480 8GB GPU's
Algo : Ethash - ETH
Tested drivers : AMd 18.20 - 20.30 - 20.40
Operation system : Linux (Simplemining)
Q:
Why Lolminer no tolerance about OC ?
All my GPU's mine with same OC value with other miners (no stale - no reject or reboot ) but when i use Lolminer too many GPU's start error and reboot.
Because of this i need to lower my OC settings drastically with Lolminer
Is anyone else experiencing this?
Algo : Ethash - ETH
Tested drivers : AMd 18.20 - 20.30 - 20.40
Operation system : Linux (Simplemining)
Q:
Why Lolminer no tolerance about OC ?
All my GPU's mine with same OC value with other miners (no stale - no reject or reboot ) but when i use Lolminer too many GPU's start error and reboot.
Because of this i need to lower my OC settings drastically with Lolminer
Is anyone else experiencing this?
Could you share your OC to have an idea? that will help. About stale or reject, other miners don't check it you have them at the pool not in the rig.
System: Amd rx 470-480 8GB GPU's
Algo : Ethash - ETH
Tested drivers : AMd 18.20 - 20.30 - 20.40
Operation system : Linux (Simplemining)
Q:
Why Lolminer no tolerance about OC ?
All my GPU's mine with same OC value with other miners (no stale - no reject or reboot ) but when i use Lolminer too many GPU's start error and reboot.
Because of this i need to lower my OC settings drastically with Lolminer
Is anyone else experiencing this?
Algo : Ethash - ETH
Tested drivers : AMd 18.20 - 20.30 - 20.40
Operation system : Linux (Simplemining)
Q:
Why Lolminer no tolerance about OC ?
All my GPU's mine with same OC value with other miners (no stale - no reject or reboot ) but when i use Lolminer too many GPU's start error and reboot.
Because of this i need to lower my OC settings drastically with Lolminer
Is anyone else experiencing this?
please someone help me out a whole gigabyte of vram is missing on ubuntu
command : dmesg | grep VRAM (shows nothing unusual)
command : dmesg | grep VRAM (shows nothing unusual)
use VGA integred on motherboard don't use card !
please someone help me out a whole gigabyte of vram is missing on ubuntu
command : dmesg | grep VRAM (shows nothing unusual)
command : dmesg | grep VRAM (shows nothing unusual)
Hello, i just try the new lolminer 1.32.
I use a 3070ti MSI Gaming X with HiveOS
Algo : AUTOLYKOS2
core clock fix to 1545 (i try with 1500 and same problem) and memory oc at 2700
My driver is up to date : 470.63.01
i try the parameter : --mode LHR2 but there is no difference in hashrate than 1.31
i also try with --lhrtune parameter with -20 the -15 ... no difference too
semi unlock only work on ethash ? or should it work with Autolykos2 too ?
Thanks a lot
EDIT : exactly the same issue with other RIG with 3060ti lhr v2
I use a 3070ti MSI Gaming X with HiveOS
Algo : AUTOLYKOS2
core clock fix to 1545 (i try with 1500 and same problem) and memory oc at 2700
My driver is up to date : 470.63.01
i try the parameter : --mode LHR2 but there is no difference in hashrate than 1.31
i also try with --lhrtune parameter with -20 the -15 ... no difference too
semi unlock only work on ethash ? or should it work with Autolykos2 too ?
Thanks a lot
EDIT : exactly the same issue with other RIG with 3060ti lhr v2
For 3060ti
Core 750
Memory 1750
PL 130
Will give you stable 113Mhs without problem
3070ti is more complicated:
I have seen:
Core 1590
Memory 350
PL 230
Try
Core -600
Memory 1900
PL 200
Hello, i just try the new lolminer 1.32.
I use a 3070ti MSI Gaming X with HiveOS
Algo : AUTOLYKOS2
core clock fix to 1545 (i try with 1500 and same problem) and memory oc at 2700
My driver is up to date : 470.63.01
i try the parameter : --mode LHR2 but there is no difference in hashrate than 1.31
i also try with --lhrtune parameter with -20 the -15 ... no difference too
semi unlock only work on ethash ? or should it work with Autolykos2 too ?
Thanks a lot
EDIT : exactly the same issue with other RIG with 3060ti lhr v2
I use a 3070ti MSI Gaming X with HiveOS
Algo : AUTOLYKOS2
core clock fix to 1545 (i try with 1500 and same problem) and memory oc at 2700
My driver is up to date : 470.63.01
i try the parameter : --mode LHR2 but there is no difference in hashrate than 1.31
i also try with --lhrtune parameter with -20 the -15 ... no difference too
semi unlock only work on ethash ? or should it work with Autolykos2 too ?
Thanks a lot
EDIT : exactly the same issue with other RIG with 3060ti lhr v2
https://gyazo.com/9f2c4268bc98edf004120674b935f7df
https://gyazo.com/86d084b5544c0de4776f6549d8318ff4
Why its getting error?
((
https://gyazo.com/86d084b5544c0de4776f6549d8318ff4
Why its getting error?
((The error comes because it has been done the bat file to have a failsafe pool. Some pools have failsafe other not...
You have two solution... fast an easy, add this line after POOL2, same POOL has 1 in your case
set "POOL2=eth.2miners.com:2020"
The 2nd solution is delete the --pool !POOL2! --user !WALLET! from the file
https://gyazo.com/9f2c4268bc98edf004120674b935f7df
https://gyazo.com/86d084b5544c0de4776f6549d8318ff4
Why its getting error?((
https://gyazo.com/86d084b5544c0de4776f6549d8318ff4
Why its getting error?
(( 
Dang ergo taking off to fast, almost 3x times in a month, the difficulty to fast to handle in small network, now the profit is sinking almost par with eth, hope some farm switch to eth, and ergo can breathe again for small miner
It has also reduce the diff in ERGO, so now is a new state of mix... also other coins have come to the new situation. It will be interesting how goes the next months.
The problem is the difficulty of the network of Ethash algorithms,the two most well known Ethereum and Ethereum Classic difficulties keep increasing,in fact the Ethereum difficulty is almost 9 P which is a new all time high now.This means a lot of people have switched to Ethereum as of lately because of the Ethereum price and this maybe has decreased the difficulty in Ergo for small miners and it looks like difficulty has decreased in about some more than 0.42 P for Ergo.
Dang ergo taking off to fast, almost 3x times in a month, the difficulty to fast to handle in small network, now the profit is sinking almost par with eth, hope some farm switch to eth, and ergo can breathe again for small miner
It has also reduce the diff in ERGO, so now is a new state of mix... also other coins have come to the new situation. It will be interesting how goes the next months.
Dang ergo taking off to fast, almost 3x times in a month, the difficulty to fast to handle in small network, now the profit is sinking almost par with eth, hope some farm switch to eth, and ergo can breathe again for small miner
I have been trying a new 6600XT... and the Watts consume is amazing:
32Mhs - 47W.
I have checked at the wall and this value is not like the old Polaris, that values are real.
32Mhs - 47W.
I have checked at the wall and this value is not like the old Polaris, that values are real.
Jump to: