Topic: lolMiner 1.64: Fastest Kaspa miner in market - page 90. (Read 155532 times)
So is it more profitable to mine c32 or c31 now ?
I have two VEGA-64 cards that can 't work on such high settings.
Settings of these cards:
GPU 1032 Mhz 905 mV. Memory: 1020 Mhz, 905 mV.
Consumes 170W GPU power.
0,97 g/s
Settings of these cards:
GPU 1032 Mhz 905 mV. Memory: 1020 Mhz, 905 mV.
Consumes 170W GPU power.
0,97 g/s
With 1032 mhz core you can go much lower in voltage. This way its inbalanced because
-The very low core loweres performance
- The voltage needs to be high because mem clock is high
- The high voltage causes too high consumption
Rather go to 1200 / 920 / 835mV ... that should be (0.9.4) slightly over 1.1g/s at much lower consumption.
In mmpos chanel I saw one guy running 6x V64 on 1120 / 920 / 760mv (! Not all cards will alloe that). He had 6.3 g/s on all cards and 920W at wall (6card + cpu + mobo + ram...)
Thanks for answer,
Cant u do in next releases the background windows function ?
Thanks
Can try, sure
But before need to solve the miracle how to port the 0.9.4 speed improvement to Windows :/
hehe thanks
u cant implement the x16v2 for lolminer?
this is the announcement thread for lolMiner 0.9.4 a multi algorithm Equihash / Beam & Grin miner with focus on AMD GPUs (OpenCL based).
Note it will run on most Nvidia GPUs, too but the speed and stability may vary.
Note it will run on most Nvidia GPUs, too but the speed and stability may vary.
Just wanted to say that 0.9.3 for Windows has been awesome! Ever since I upgraded I have not had to babysit the rigs for crashing GPUs. Really looking forward to the hashing increases of 0.9.4!
I have two VEGA-64 cards that can 't work on such high settings.
Settings of these cards:
GPU 1032 Mhz 905 mV. Memory: 1020 Mhz, 905 mV.
Consumes 170W GPU power.
0,97 g/s
Settings of these cards:
GPU 1032 Mhz 905 mV. Memory: 1020 Mhz, 905 mV.
Consumes 170W GPU power.
0,97 g/s
With 1032 mhz core you can go much lower in voltage. This way its inbalanced because
-The very low core loweres performance
- The voltage needs to be high because mem clock is high
- The high voltage causes too high consumption
Rather go to 1200 / 920 / 835mV ... that should be (0.9.4) slightly over 1.1g/s at much lower consumption.
In mmpos chanel I saw one guy running 6x V64 on 1120 / 920 / 760mv (! Not all cards will alloe that). He had 6.3 g/s on all cards and 920W at wall (6card + cpu + mobo + ram...)
Thanks for answer,
Cant u do in next releases the background windows function ?
Thanks
Can try, sure
But before need to solve the miracle how to port the 0.9.4 speed improvement to Windows :/
hi its possible to run in background lolminer with some parameter in json file?
Not yet - well on Linux you can just append & on the cmd to run it completely in background.
Memory: Frequency - 1100Mhz, 905 mV.
GPU: P5 1212 Mhz, 1100mV. P6 1307Mhz, 905 mV. P7 1472 Mhz, 925 mV.
Radeon 19.12.1.
CPU Intel i3-4170
teamredminer-v0.6.1 - work.
lolMiner-0.9.3 don't work.
"Stuck device detected, invoking emergency script."
GPU: P5 1212 Mhz, 1100mV. P6 1307Mhz, 905 mV. P7 1472 Mhz, 925 mV.
Radeon 19.12.1.
CPU Intel i3-4170
teamredminer-v0.6.1 - work.
lolMiner-0.9.3 don't work.
"Stuck device detected, invoking emergency script."
Lifting my virtual hat then for trm (I like the guys anyways - they are great and made a great product!). I must admit I did not try that high memclk - afaik only Samsung mem allows to clock that high and also that often requite quite high core voltage.
I tested - and optimized - the miner more for more watts saving clocks like 1280 / 1000 which runs often with voltages low as 825mV (some cards may need 850 or 862 ...). At least on Linux, 19.30 the 0.9.4 miner then still mines at ~1.15 g/s (rocm 1.2 when you got no risers) but also power draw is <160W then (chip reported even <125, but always need to add some for board and memory).
With P7 at 1470 / 1100 I am sure you can not end up below 230? (more a guess ^^)
Thanks for answer,
Cant u do in next releases the background windows function ?
Thanks
I have two VEGA-64 cards that can 't work on such high settings.
Settings of these cards:
GPU 1032 Mhz 905 mV. Memory: 1020 Mhz, 905 mV.
Consumes 170W GPU power.
0,97 g/s
Settings of these cards:
GPU 1032 Mhz 905 mV. Memory: 1020 Mhz, 905 mV.
Consumes 170W GPU power.
0,97 g/s
Use AMD Mem Tweaker to apply weak settings on Vega Cards.
That should provide a bit boost to the hash rate.
Also, undervolt the core more as undervolting memory doesn't do anything.
I have two VEGA-64 cards that can 't work on such high settings.
Settings of these cards:
GPU 1032 Mhz 905 mV. Memory: 1020 Mhz, 905 mV.
Consumes 170W GPU power.
0,97 g/s
Settings of these cards:
GPU 1032 Mhz 905 mV. Memory: 1020 Mhz, 905 mV.
Consumes 170W GPU power.
0,97 g/s
Use AMD Mem Tweaker to apply weak settings on Vega Cards.
That should provide a bit boost to the hash rate.
Also, undervolt the core more as undervolting memory doesn't do anything.
I have two VEGA-64 cards that can 't work on such high settings.
Settings of these cards:
GPU 1032 Mhz 905 mV. Memory: 1020 Mhz, 905 mV.
Consumes 170W GPU power.
0,97 g/s
Settings of these cards:
GPU 1032 Mhz 905 mV. Memory: 1020 Mhz, 905 mV.
Consumes 170W GPU power.
0,97 g/s
Looks like healthy settings - but remember that the 190W displayed are chip power only - need to add memory and board for AMDs (else I could claim my miner would do 1.15 g/s at 100W - which is chip power only, but obviously cheating ^^)
With P7 at 1470 / 1100 I am sure you can not end up below 230? (more a guess ^^)
I started with low frequency and voltage. Then lifted above.
https://yadi.sk/i/pj9PGJFXOafMEg
https://yadi.sk/i/Wg0OH_zF9MU4ag
https://yadi.sk/i/UBrqhdqPqM-2xA
https://yadi.sk/i/3y8nXCxyEjgTxQ
https://yadi.sk/i/GXRQu7x2onCWmA
hi its possible to run in background lolminer with some parameter in json file?
Not yet - well on Linux you can just append & on the cmd to run it completely in background.
Memory: Frequency - 1100Mhz, 905 mV.
GPU: P5 1212 Mhz, 1100mV. P6 1307Mhz, 905 mV. P7 1472 Mhz, 925 mV.
Radeon 19.12.1.
CPU Intel i3-4170
teamredminer-v0.6.1 - work.
lolMiner-0.9.3 don't work.
"Stuck device detected, invoking emergency script."
GPU: P5 1212 Mhz, 1100mV. P6 1307Mhz, 905 mV. P7 1472 Mhz, 925 mV.
Radeon 19.12.1.
CPU Intel i3-4170
teamredminer-v0.6.1 - work.
lolMiner-0.9.3 don't work.
"Stuck device detected, invoking emergency script."
Lifting my virtual hat then for trm (I like the guys anyways - they are great and made a great product!). I must admit I did not try that high memclk - afaik only Samsung mem allows to clock that high and also that often requite quite high core voltage.
I tested - and optimized - the miner more for more watts saving clocks like 1280 / 1000 which runs often with voltages low as 825mV (some cards may need 850 or 862 ...). At least on Linux, 19.30 the 0.9.4 miner then still mines at ~1.15 g/s (rocm 1.2 when you got no risers) but also power draw is <160W then (chip reported even <125, but always need to add some for board and memory).
With P7 at 1470 / 1100 I am sure you can not end up below 230? (more a guess ^^)
Windows 10. Only 1,01 g/s VEGA-64. teamredminer-v0.6.1 - 1,23 g/s, 175 W.
Thats strange... which version exactly? Can you give more data (settings)? I have to admit I did test more with V56 but for a V64 thats far too low even without the improvements of 0.9.4.
Only data I got of a direct comparison with trm on Win was by a user using 0.9.2. There indeed trm was faster but also used more energy.
With 0.9.4 on Linux I am pretty sure that flipped
Edit: slept over that msg and now wonder if you can tell me what driver version and CPU you use. All my Win tests refer to Adrenalin 19.10.1 and its one card on a rather strong CPU. Saw on Linux that the driver may make a difference here, e.g. two cards, Xeon server GPU: 19.30 driver is slower then ROCm 2.10, 6 card rig Celeron: 19.30 is quicker then ROCm 2.10.
So maybe driver and or CPU may be the issue on Windows, too.
Memory: Frequency - 1100Mhz, 905 mV.
GPU: P5 1212 Mhz, 1100mV. P6 1307Mhz, 905 mV. P7 1472 Mhz, 925 mV.
Radeon 19.12.1.
CPU Intel i3-4170
teamredminer-v0.6.1 - work.
lolMiner-0.9.3 don't work.
"Stuck device detected, invoking emergency script."
hi its possible to run in background lolminer with some parameter in json file?
Lollie, do you mind explaining why you removed the 16G solver? Just curious why 8G would be faster. I've got some Vega FEs and a Radeon Pro Duo I wanted to throw at this, remember you had the 16G solver back on version 0.8.3.
It was only removed for 0.9 but brought back for 0.9.1 - the reason was that the 8G 0.9 solver was quicker then 16G 0.8.8 (and earlier). 0.9.2 has a bug that may cause to load wrong kernel (8G instead of 16G) in Windows on FE - will be fixed with 0.9.3
Is there possible to implement Cuckaroo29 BFC algorithm?
I am redoing my C29 codes atm. Hope to have it flexible enough to add Cuckarood-29 (Current Grin-29), Cuckaroom-29 (next gen Grin from January), Cuckaroo-29 (BFC, Swap) and Cuckaroo-30 (Cortex) one by one... not yet sure about the order though ^^
Windows 10. Only 1,01 g/s VEGA-64. teamredminer-v0.6.1 - 1,23 g/s, 175 W.
Thats strange... which version exactly? Can you give more data (settings)? I have to admit I did test more with V56 but for a V64 thats far too low even without the improvements of 0.9.4.
Only data I got of a direct comparison with trm on Win was by a user using 0.9.2. There indeed trm was faster but also used more energy.
With 0.9.4 on Linux I am pretty sure that flipped
Edit: slept over that msg and now wonder if you can tell me what driver version and CPU you use. All my Win tests refer to Adrenalin 19.10.1 and its one card on a rather strong CPU. Saw on Linux that the driver may make a difference here, e.g. two cards, Xeon server GPU: 19.30 driver is slower then ROCm 2.10, 6 card rig Celeron: 19.30 is quicker then ROCm 2.10.
So maybe driver and or CPU may be the issue on Windows, too.
Windows 10. Only 1,01 g/s VEGA-64. teamredminer-v0.6.1 - 1,23 g/s, 175 W.
So, only two days went by, but now already pushed 0.9.4 
Its a big jump again in C31 hash rate and as special sauce I also added support (very experimental) for grin - cuckatoo 32. Sadly running into some limitations of the Windows Adrenalin driver, thats why the improvements are Linux only. But did send a support request to AMD staff already - hopefully we can sort this out soon.
Its a big jump again in C31 hash rate and as special sauce I also added support (very experimental) for grin - cuckatoo 32. Sadly running into some limitations of the Windows Adrenalin driver, thats why the improvements are Linux only. But did send a support request to AMD staff already - hopefully we can sort this out soon.
can't mine beamv2 at nice. Command line is
It says
Code:
lolMiner.exe --coin Beam --pool beamv2.eu.nicehash.com --port 3378 --user addr.wrkr --pass x --tls 0
Quote
Connected to beamv2.eu.nicehash.com:3378 (TLS disabled)
Lost connection to stratum server beamv2.eu.nicehash.com:3378 or server not reachable
Anybody else?Lost connection to stratum server beamv2.eu.nicehash.com:3378 or server not reachable
I just tested and yes, also had a problem connecting to the EU server. Strangely beamv2.usa.nicehash.com works without problems - so maybe a problem with their eu stratum?
How can I see the temperature of the videocards, the speed of the fans?
Did you test VEGA64?
Did you test VEGA64?
Yes, we did test V64 as well. Stock should be about 1.25 g/s+ , but with energy saving settings (Clock down to 1220 or so, voltage to 0.835) you will get about 1.07 - but at much better energy consumption.
Currently the miner does not read out this data. I recommend using a mining OS like mmpOS or PiMP or Hive or ethos or ... (there are many). Those will give you usually very good watchdogs for the miner, tested out drivers and often also good OC or UV profiles for good mining speed / energy use ratio. The miner itself does not get this values yet (because its a pain in the ass reading it for AMD and NV and for Lin as well as Win) ... and since most serious farms run one of these OS just mentioned its wasted effort for me - rather concentrating on making the miner itself better
How can I see the temperature of the videocards, the speed of the fans?
Did you test VEGA64?
Jump to: