Topic: lolMiner 1.64: Fastest Kaspa miner in market - page 88. (Read 155532 times)
Any plans to support --coin GRIN-AUTO on Nicehash?
Hey, just pushed 0.9.7 
Changes
If you got any questions about the automatic algorithm selector let me know (but please read that page first
)
Preview of what is does:
Its 1% since 0.7.0 - and will stay there
The beam algorithm at the moment needs a big rework on Navi - a lot of things not working there. I will try to fix that with 0.9.8 (but honestly: wait for BeamHash III and mine something else and buy Beam from the mining return... currently thats the more profitable way to get Beams...)
0.9.6.1 needs a bit more memory - maybe that is the issue here. Does one of the card run the screen or is the rig headless? Also can you check how large your Windows pagefile (virtual memory) is? Please set it to at least 8G * number of cards (stupid Adrenaline Windows requirement that the virtual CPU memory needs to be as big as the used actual GPU memory... )
Changes
- Windows: Increased GRIN-C32 performance on Navi cards by 15-18%
- Linux: Increased GRIN-C32 performance on Vega, VII & Navi cards by 15-18%
- Added a Grin Auto profit switcher (use: --coin GRIN-AUTO + further options). Please read https://github.com/Lolliedieb/lolMiner-releases/wiki/Grin-Automatic-Profit-Switching carefully how to use it and which pools are supported.
If you got any questions about the automatic algorithm selector let me know (but please read that page first
)Preview of what is does:
what is the mining dev fee for BEAM?
Its 1% since 0.7.0 - and will stay there
Trying to mine beam with my 5700's but they don't seem to be working... Miner reads average speed of 0.00 Sol/s. I'm receiving jobs, just not mining. Thoughts on how to resolve?
Mining solo (or trying) on win 10 pro 64 bit w/19.10.02 drivers. Win defender disabled and wallets online.
Any help is appreciated...
Mining solo (or trying) on win 10 pro 64 bit w/19.10.02 drivers. Win defender disabled and wallets online.
Any help is appreciated...
The beam algorithm at the moment needs a big rework on Navi - a lot of things not working there. I will try to fix that with 0.9.8 (but honestly: wait for BeamHash III and mine something else and buy Beam from the mining return... currently thats the more profitable way to get Beams...)
Version 0.9.6.1 doesn't want to start up for me - it just hangs after initialising the first GPU. When I skip the second RX580 8GB, it hangs on the third. Tried rebooting, nothing. Cmd line is default for C29M, I only fiddled with --devices. Clocks and power limits are default (no overclocking or anything). Drivers are adrenalin 20.1.1 / W10 pro. In afterburner I see the gpu clock on currently stuck initialsing GPU at max, but it never proceeds.
0.9.6.1 needs a bit more memory - maybe that is the issue here. Does one of the card run the screen or is the rig headless? Also can you check how large your Windows pagefile (virtual memory) is? Please set it to at least 8G * number of cards (stupid Adrenaline Windows requirement that the virtual CPU memory needs to be as big as the used actual GPU memory... )
what is the mining dev fee for BEAM?
Trying to mine beam with my 5700's but they don't seem to be working... Miner reads average speed of 0.00 Sol/s. I'm receiving jobs, just not mining. Thoughts on how to resolve?
Mining solo (or trying) on win 10 pro 64 bit w/19.10.02 drivers. Win defender disabled and wallets online.
Any help is appreciated...
Mining solo (or trying) on win 10 pro 64 bit w/19.10.02 drivers. Win defender disabled and wallets online.
Any help is appreciated...
Version 0.9.6.1 doesn't want to start up for me - it just hangs after initialising the first GPU. When I skip the second RX580 8GB, it hangs on the third. Tried rebooting, nothing. Cmd line is default for C29M, I only fiddled with --devices. Clocks and power limits are default (no overclocking or anything). Drivers are adrenalin 20.1.1 / W10 pro. In afterburner I see the gpu clock on currently stuck initialsing GPU at max, but it never proceeds.
Before that, 0.9.5.1 fired up just fine, althrough it did take like 90 seconds to "initialise" all cards. Now it just looks like this with --devices 0,2,3,4,5 (I have 6 RX580 8GB total)
Setup Miner...
Device 0:
Name: Radeon RX 580 Series
Address: 1:0
Vendor: Advanced Micro Devices (AMD)
Memory: 8192 MByte (8142 MByte free)
Active: true (Selected Algorithm: CuckarooM 29-8G)
Device 1:
Name: Radeon RX 580 Series
Address: 2:0
Vendor: Advanced Micro Devices (AMD)
Memory: 8192 MByte (8142 MByte free)
Active: false (not selected)
Device 2:
Name: Radeon RX 580 Series
Address: 3:0
Vendor: Advanced Micro Devices (AMD)
Memory: 8192 MByte (8142 MByte free)
.... hangs there ....
Before that, 0.9.5.1 fired up just fine, althrough it did take like 90 seconds to "initialise" all cards. Now it just looks like this with --devices 0,2,3,4,5 (I have 6 RX580 8GB total)
Setup Miner...
Device 0:
Name: Radeon RX 580 Series
Address: 1:0
Vendor: Advanced Micro Devices (AMD)
Memory: 8192 MByte (8142 MByte free)
Active: true (Selected Algorithm: CuckarooM 29-8G)
Device 1:
Name: Radeon RX 580 Series
Address: 2:0
Vendor: Advanced Micro Devices (AMD)
Memory: 8192 MByte (8142 MByte free)
Active: false (not selected)
Device 2:
Name: Radeon RX 580 Series
Address: 3:0
Vendor: Advanced Micro Devices (AMD)
Memory: 8192 MByte (8142 MByte free)
.... hangs there ....
Were able to resolve the issue in Telegram
For some reason the 18.50 driver in Hive did not work for him, while 19.10 did (what is strange since I compiled with 18.50...)
Any ways: it worked then
For Windows users: updated version to 0.9.6.1 - fixing a bug with 8G cards on Win 10 using 4G solver on C31. Download location is same as before, Linux is not affected afaik.
For some reason the 18.50 driver in Hive did not work for him, while 19.10 did (what is strange since I compiled with 18.50...)
Any ways: it worked then
For Windows users: updated version to 0.9.6.1 - fixing a bug with 8G cards on Win 10 using 4G solver on C31. Download location is same as before, Linux is not affected afaik.
Having problems getting miner to show up pool side (C31). Can't connect at all on 0.9.6 and on 0.9.5.1 miner is reporting that it is connected and showing accepted speeds but 0 h/s on nicehash. Radeon VII, 18.50 drivers on linux (hiveos).
16:03:39 Average speed (60s): 2.98 g/s | 2.97 g/s | 3.00 g/s | 2.98 g/s Total: 11.93 g/s
16:03:39 Fidelity (14 cycles): 0.00 | 0.00 | 0.00 | 0.00 Total: 0.00
16:03:39 Fidelity (42 cycles): 0.00 | 0.00 | 0.00 | 0.00 Total: 0.00
This doesn't look as Radeon VII C31 speed, are you sure you've set it up properly?16:03:39 Average speed (60s): 2.98 g/s | 2.97 g/s | 3.00 g/s | 2.98 g/s Total: 11.93 g/s
16:03:39 Fidelity (14 cycles): 0.00 | 0.00 | 0.00 | 0.00 Total: 0.00
16:03:39 Fidelity (42 cycles): 0.00 | 0.00 | 0.00 | 0.00 Total: 0.00
./lolMiner --coin GRIN-AT31 --pool grincuckatoo31.eu.nicehash.com --port 3372 --user ${BTC_WALLET}.${RIG_NAME} --pass x --devices AMD
Having problems getting miner to show up pool side (C31). Can't connect at all on 0.9.6 and on 0.9.5.1 miner is reporting that it is connected and showing accepted speeds but 0 h/s on nicehash. Radeon VII, 18.50 drivers on linux (hiveos).
16:03:39 Average speed (60s): 2.98 g/s | 2.97 g/s | 3.00 g/s | 2.98 g/s Total: 11.93 g/s
16:03:39 Fidelity (14 cycles): 0.00 | 0.00 | 0.00 | 0.00 Total: 0.00
16:03:39 Fidelity (42 cycles): 0.00 | 0.00 | 0.00 | 0.00 Total: 0.00
16:03:39 Average speed (60s): 2.98 g/s | 2.97 g/s | 3.00 g/s | 2.98 g/s Total: 11.93 g/s
16:03:39 Fidelity (14 cycles): 0.00 | 0.00 | 0.00 | 0.00 Total: 0.00
16:03:39 Fidelity (42 cycles): 0.00 | 0.00 | 0.00 | 0.00 Total: 0.00
Just updated the version to 0.9.6
Overall should give a nice speed bump for all GRIN algorithms including the new C29M.
Expected Performance
Test Platform: Ubuntu 18.40, amdgpu-pro 19.30, stock cards
* On Windows sadly 5-7% slower due to a driver issue AMD Adrenaline has on Vegas
Overall should give a nice speed bump for all GRIN algorithms including the new C29M.
Expected Performance
Test Platform: Ubuntu 18.40, amdgpu-pro 19.30, stock cards
| Algorithm | RX 570 8G | Vega 56 | Vega 64 | RX 5700 | Radeon VII |
| Cuckaroom-29 | 2.4 g/s | 4.1 g/s | 4.6 g/s | 4.4 g/s | 6.4 g/s |
| Cuckatoo-31 | 0.67 g/s | 1.15 g/s* | 1.37 g/s* | 1.12 g/s | 2.05 g/s* |
| Cuckatoo-32 | 0.18 g/s | 0.36 g/s | 0.42 g/s | 0.34 g/s | 0.65 g/s |
* On Windows sadly 5-7% slower due to a driver issue AMD Adrenaline has on Vegas
its allright now, it was the ip from zel labs
Problem is that my solver at the moment needs 8G to work. So 390 does work, but Fury only got 4G ... I am thinking about a 4G solver but its more complicated then anticipated.
Hey! We waiting your 4G version! Good luck!
Just downloaded win64 version. Manual pdf doesn't even list GRIN. BEAM only. 
Github shows grin... but not for windows I guess? Anyone know?
Github shows grin... but not for windows I guess? Anyone know? this version of lolminer v09.5 doesnt like vega's.. it gives me 0.00 hashes
Can you share operation system.and driver version? Would like to debug, but need more info
this version of lolminer v09.5 doesnt like vega's.. it gives me 0.00 hashes
Problem is that my solver at the moment needs 8G to work. So 390 does work, but Fury only got 4G ... I am thinking about a 4G solver but its more complicated then anticipated.
ah i see... but fury is still strong on etc can get 33 mhs
Problem is that my solver at the moment needs 8G to work. So 390 does work, but Fury only got 4G ... I am thinking about a 4G solver but its more complicated then anticipated.
fury not working with new grin algo... any clue for this gpu?
Well no I would say ... When you put in the actual values its 2nd best algo after ethash - but well that still leading the pack. Well on Vegas its different (just wtm using totally unreasonable clock settings ^^)
No profit to do on C31 with RX 
C31 very profitable at the moment - because the grin network needed to adjust diff down due to the C29 fork.
Miner where are you?
Ps: good progress on 4G C29M code
Miner where are you?
Ps: good progress on 4G C29M code
Jump to: