is there any help to run lol miner as a custom miner in hive os?
Topic: lolMiner 1.64: Fastest Kaspa miner in market - page 136. (Read 156206 times)
Any update on the 0.5 release?
Thank you. That worked!
However, it doesn't seem to be doing any hashing..
I can see that it connected to my pool (on my local pool server) but it doesn't do anything past the output above. It sits there at "Connected to...".
However, it doesn't seem to be doing any hashing..
I can see that it connected to my pool (on my local pool server) but it doesn't do anything past the output above. It sits there at "Connected to...".
If I read your output correctly the miner is waiting for the pool to authorize the worker. But there where the authorization message should appear I only see "Warning: value is type " what indicates that the pool sends out a defect stratum message. Please check that and also that the pool supports the extended mining.notify message with the personalization string given by pool.
When you plan to release 0.50?
Thanks for helping me, seems for Minex it makes no difference with HIGH or VERYHIGH, can you check it?
Maybe something to do with drivers as using older drivers than latest ATI
Thanks for helping me, seems for Minex it makes no difference with HIGH or VERYHIGH, can you check it?
Maybe something to do with drivers as using older drivers than latest ATI
Planning to do so beginning of next week
What does this error mean and how do I fix it? http://prntscr.com/kwtp0d
Good question... hmm ... I do not know much about hive. But I will contact the team so they integrate 0.5 asap.
What does this error mean and how do I fix it? http://prntscr.com/kwtp0d
When you plan to release 0.50?
Thanks for helping me, seems for Minex it makes no difference with HIGH or VERYHIGH, can you check it?
Maybe something to do with drivers as using older drivers than latest ATI
Thanks for helping me, seems for Minex it makes no difference with HIGH or VERYHIGH, can you check it?
Maybe something to do with drivers as using older drivers than latest ATI
Thank you. That worked!
However, it doesn't seem to be doing any hashing..
I can see that it connected to my pool (on my local pool server) but it doesn't do anything past the output above. It sits there at "Connected to...".
However, it doesn't seem to be doing any hashing..
Code:
-------------------------------------------------
Welcome to lolMiner 0.43
This software is only meant for pool mining
with the Equihash 96.5, 144.5 or 192.7 algorithm
Made by Lolliedieb, August 2018
-------------------------------------------------
lolMiner is configured to mine Auto Switching(AUTO144), Equihash 144.5
Setup Miner...
Using device with id 0 (Radeon RX 580 Series)
Using device with id 1 (Radeon RX 580 Series)
Using device with id 2 (Radeon RX 580 Series)
Using device with id 3 (Radeon RX 580 Series)
Using device with id 4 (Radeon RX 580 Series)
Using device with id 5 (Radeon RX 580 Series)
Using device with id 6 (Radeon RX 580 Series)
Using device with id 7 (Radeon RX 580 Series)
Using device with id 8 (Radeon RX 580 Series)
Connecting to pool...
Connected to 192.168.1.137:3036
Subscribed to stratum server
New target received: 00a0000000000000
New job received: d216
Warning: value is type
Lost connection to stratum server 192.168.1.137:3036 or server not reachable.
Trying to connect in 5 seconds
Connected to 192.168.1.137:3036
I can see that it connected to my pool (on my local pool server) but it doesn't do anything past the output above. It sits there at "Connected to...".
I'm trying to mine ANON with AUTO144 and i'm getting errors.. anyone know what I'm doing wrong?
The configuration is looking good so far. The error message is a bit vague I have to admit. I will try to improve them soon.
There are two potential reasons:
1) The miner fails the memory check. That could be on 4G cards, when some driver environment variables are not set.
For Windows use
Code:
setx GPU_FORCE_64BIT_PTR 1
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
before starting the software, on Linux names of the variables are the same, they are set with "export NAME=value".
2) The miner does not find the kernel / the kernel directory. Ensure it is in the folder where you start the miner.
-------------
Update of the 0.5 development status:
| Algorithm | AMD | Nvidia |
| 96/5 | Ready | In Tuning |
| 144/5 | Ready | Ready |
| 192/7 | Ready | In Testing |
| Aion | In Tuning | In Tuning |
| (210/9) | (Stratum ready) | (Stratum ready) |
I'm trying to mine ANON with AUTO144 and i'm getting errors.. anyone know what I'm doing wrong?
config (i have the correct stuff in the pool config, just removed it for this post):
running with:
Code:
-------------------------------------------------
Welcome to lolMiner 0.43
This software is only meant for pool mining
with the Equihash 96.5, 144.5 or 192.7 algorithm
Made by Lolliedieb, August 2018
-------------------------------------------------
lolMiner is configured to mine Auto Switching(AUTO144), Equihash 144.5
Setup Miner...
Using device with id 0 (Radeon RX 580 Series)
Using device with id 1 (Radeon RX 580 Series)
Using device with id 2 (Radeon RX 580 Series)
Using device with id 3 (Radeon RX 580 Series)
Using device with id 4 (Radeon RX 580 Series)
Using device with id 5 (Radeon RX 580 Series)
Using device with id 6 (Radeon RX 580 Series)
Using device with id 7 (Radeon RX 580 Series)
Using device with id 8 (Radeon RX 580 Series)
Warning: Your device with id 0 is currently not supported by lolMiner or by the specific algorithm you selected.
Warning: Your device with id 1 is currently not supported by lolMiner or by the specific algorithm you selected.
Warning: Your device with id 2 is currently not supported by lolMiner or by the specific algorithm you selected.
Warning: Your device with id 3 is currently not supported by lolMiner or by the specific algorithm you selected.
Warning: Your device with id 4 is currently not supported by lolMiner or by the specific algorithm you selected.
Warning: Your device with id 5 is currently not supported by lolMiner or by the specific algorithm you selected.
Warning: Your device with id 6 is currently not supported by lolMiner or by the specific algorithm you selected.
Warning: Your device with id 7 is currently not supported by lolMiner or by the specific algorithm you selected.
Warning: Your device with id 8 is currently not supported by lolMiner or by the specific algorithm you selected.
Error: lolMiner does not support any of the detected / selected devices algorithms on the selected algorithm.
config (i have the correct stuff in the pool config, just removed it for this post):
Code:
{
"DEFAULTS" : {
"DEVICES" : "AUTO",
"APIPORT" : 0,
"PLATFORM": "AUTO"
},
"ANON": {
"COIN": "AUTO144",
"POOLS": [
{"POOL" : "pool-ip-address",
"PORT" : "pool-port",
"USER" : "myaddress.worker",
"PASS" : "x"}
]
}
}
running with:
Code:
./lolMiner -userCFG=cfg.json -profile=ANON
Hmm have not seen this till now, but may be. ctrl+c is a bit difficult to handle because it stops program immediately, so I even can not catch this to wait until cards have stopped what they just did to exit gracefully. Maybe I must think of an other way to stop the miner.
Ok, my bad. I tried to double up a single power cable to one of the Vega 64's instead of using two separate power inputs. Correcting that config resolved the crash (which never had a kernel, panic, btw. It would simply reboot, which spoke to hardware level behavior).
Sorry for the false alarm.
Thanks I added this line "PASS" : "x"
"WORKBATCH" : "HIGH"}
To my user config file, but soon as I run the miner goes crazy, doesnt work windows keep popping up.
In next version can you check it, also why the need for two windows, can we keep all in one like other miners.
"WORKBATCH" : "HIGH"}
To my user config file, but soon as I run the miner goes crazy, doesnt work windows keep popping up.
In next version can you check it, also why the need for two windows, can we keep all in one like other miners.
You missed a "," because every line needs a comma at its end except for the last line in the block - I think its the json parser complaining here.
---------
So I'm seeing an odd behavior with 144.5 mining (zelcash in this case, 2 Vega64's, 3 Vega56's). If/when I lose connection to the pool, the moment the worker is reauthorized, my linux box crashes and reboots:
...
and then the immediate reboot. I don't see the kernel panic in the log, but I see ubuntu 18 uses syslog caching by default. I've removed caching and we'll see if it catches something on the next crash.
This is more of an FYI unless you see something in your reconnect code that might cause a panic. However, I'm not even sure whether the lost connection is a symptom of an imminent crash or the actual cause. Who knows, it could simply be instability with one of my risers...
I'll see if I can track down more info in the logs next time.
edit: I also notice that if I ctrl-c out of the miner, it's a 50/50 toss up that restating the miner causes a reboot on reconnect. So this is likely related. Perhaps something about the state that the card is left in during an abnormal stop? Reuse that card and cause the panic? I find that I usually have to power off the clear the cards before the system is stable again. Just speculating...
I'm undervolting and using the latest amd 18.30 drivers for ubuntu.
...
and then the immediate reboot. I don't see the kernel panic in the log, but I see ubuntu 18 uses syslog caching by default. I've removed caching and we'll see if it catches something on the next crash.
This is more of an FYI unless you see something in your reconnect code that might cause a panic. However, I'm not even sure whether the lost connection is a symptom of an imminent crash or the actual cause. Who knows, it could simply be instability with one of my risers...
I'll see if I can track down more info in the logs next time.
edit: I also notice that if I ctrl-c out of the miner, it's a 50/50 toss up that restating the miner causes a reboot on reconnect. So this is likely related. Perhaps something about the state that the card is left in during an abnormal stop? Reuse that card and cause the panic? I find that I usually have to power off the clear the cards before the system is stable again. Just speculating...
I'm undervolting and using the latest amd 18.30 drivers for ubuntu.
Hmm have not seen this till now, but may be. ctrl+c is a bit difficult to handle because it stops program immediately, so I even can not catch this to wait until cards have stopped what they just did to exit gracefully. Maybe I must think of an other way to stop the miner.
I'm bit confused where to set: Setting the WorkBatch (MNX, Equihash 96.5 only)
Can you provide me a example line and in where to place it.
In your guide it does not mention this cheers.
Can you provide me a example line and in where to place it.
In your guide it does not mention this cheers.
All option are used either as "PARAMETER" : VALUE in config file or -parameter=value in command line. So here it is "WORKBATCH" : "HIGH" (Or for example "WORKBATCH":12 for a fixed number) or -workbatch=HIGH in cmd. The parameter controls how many instances of 96/5 are allowed to run at same time / how much of the available GPU memory the miner is allowed to use.
-------------
By the way, current 0.5 development status:
| Algorithm | AMD | Nvidia |
| 96/5 | In testing | In Tuning |
| 144/5 | Ready | In testing |
| 192/7 | Ready | In testing |
| Aion | In dev | In dev |
| (210/9) | (Stratum ready) | (Stratum ready) |
Thanks I added this line "PASS" : "x"
"WORKBATCH" : "HIGH"}
To my user config file, but soon as I run the miner goes crazy, doesnt work windows keep popping up.
In next version can you check it, also why the need for two windows, can we keep all in one like other miners.
So I'm seeing an odd behavior with 144.5 mining (zelcash in this case, 2 Vega64's, 3 Vega56's). If/when I lose connection to the pool, the moment the worker is reauthorized, my linux box crashes and reboots:
-----------------
Average speed (5s): 34.0 sol/s | 32.6 sol/s | 33.4 sol/s | 30.8 sol/s | 27.6 sol/s Total: 158.3 sol/s
Submitting share
Share accepted
Submitting share
Submitting share
Share accepted
Share accepted
Average speed (5s): 34.2 sol/s | 32.0 sol/s | 30.6 sol/s | 29.0 sol/s | 28.2 sol/s Total: 154.0 sol/s
Submitting share
Share accepted
Lost connection to stratum server equigems.online:9000 or server not reachable.
Trying to connect in 5 seconds
Lost connection to stratum server equigems.online:9000 or server not reachable.
Trying to connect in 5 seconds
Connected to equigems.online:9000
Subscribed to stratum server
New target received: 00a0000000000000
New job received: cccd
Authorized worker:
-----------------
and then the immediate reboot. I don't see the kernel panic in the log, but I see ubuntu 18 uses syslog caching by default. I've removed caching and we'll see if it catches something on the next crash.
This is more of an FYI unless you see something in your reconnect code that might cause a panic. However, I'm not even sure whether the lost connection is a symptom of an imminent crash or the actual cause. Who knows, it could simply be instability with one of my risers...
I'll see if I can track down more info in the logs next time.
edit: I also notice that if I ctrl-c out of the miner, it's a 50/50 toss up that restating the miner causes a reboot on reconnect. So this is likely related. Perhaps something about the state that the card is left in during an abnormal stop? Reuse that card and cause the panic? I find that I usually have to power off the clear the cards before the system is stable again. Just speculating...
I'm undervolting and using the latest amd 18.30 drivers for ubuntu.
-----------------
Average speed (5s): 34.0 sol/s | 32.6 sol/s | 33.4 sol/s | 30.8 sol/s | 27.6 sol/s Total: 158.3 sol/s
Submitting share
Share accepted
Submitting share
Submitting share
Share accepted
Share accepted
Average speed (5s): 34.2 sol/s | 32.0 sol/s | 30.6 sol/s | 29.0 sol/s | 28.2 sol/s Total: 154.0 sol/s
Submitting share
Share accepted
Lost connection to stratum server equigems.online:9000 or server not reachable.
Trying to connect in 5 seconds
Lost connection to stratum server equigems.online:9000 or server not reachable.
Trying to connect in 5 seconds
Connected to equigems.online:9000
Subscribed to stratum server
New target received: 00a0000000000000
New job received: cccd
Authorized worker:
-----------------
and then the immediate reboot. I don't see the kernel panic in the log, but I see ubuntu 18 uses syslog caching by default. I've removed caching and we'll see if it catches something on the next crash.
This is more of an FYI unless you see something in your reconnect code that might cause a panic. However, I'm not even sure whether the lost connection is a symptom of an imminent crash or the actual cause. Who knows, it could simply be instability with one of my risers...
I'll see if I can track down more info in the logs next time.
edit: I also notice that if I ctrl-c out of the miner, it's a 50/50 toss up that restating the miner causes a reboot on reconnect. So this is likely related. Perhaps something about the state that the card is left in during an abnormal stop? Reuse that card and cause the panic? I find that I usually have to power off the clear the cards before the system is stable again. Just speculating...
I'm undervolting and using the latest amd 18.30 drivers for ubuntu.
-------------
By the way, current 0.5 development status:
By the way, current 0.5 development status:
| Algorithm | AMD | Nvidia |
| 96/5 | In testing | In Tuning |
| 144/5 | Ready | In testing |
| 192/7 | Ready | In testing |
| Aion | In dev | In dev |
| (210/9) | (Stratum ready) | (Stratum ready) |
Awesome, very much looking forward to the Aion support
Good evening, I am trying to mine on ANON, and I contend that on my 6 gpu, I have one that turns to 4 sol / s while the others turn to 20 sol / s, I have 2 x r9280x and 2 x hd7990, I think it's one of my r9280x that has the problem, and it's the same with the BTG. I have no problem when I mine zcash with claymore. Can you give me the procedure, if you want more information, I'll give it to you.
{
"DEFAULTS" : {
"PLATFORM" : "AUTO",
"DEVICES" : "AUTO"
},
"EXAMPLE_BTG" :
{
"COIN" : "BTG",
"POOLS" : [
{"POOL" : "europe.equihash-hub.miningpoolhub.com",
"PORT" : "20595",
"USER" : "lezartnono19.R9280x",
"PASS" : "x"}
]
},
"EXAMPLE_ANON" :
{
"COIN" : "AUTO144",
"POOLS" : [
{"POOL" : "anon.suprnova.cc",
"PORT" : "7060",
"USER" : "lezartnono19.R9280x",
"PASS" : "x"}
]
}
}
{
"DEFAULTS" : {
"PLATFORM" : "AUTO",
"DEVICES" : "AUTO"
},
"EXAMPLE_BTG" :
{
"COIN" : "BTG",
"POOLS" : [
{"POOL" : "europe.equihash-hub.miningpoolhub.com",
"PORT" : "20595",
"USER" : "lezartnono19.R9280x",
"PASS" : "x"}
]
},
"EXAMPLE_ANON" :
{
"COIN" : "AUTO144",
"POOLS" : [
{"POOL" : "anon.suprnova.cc",
"PORT" : "7060",
"USER" : "lezartnono19.R9280x",
"PASS" : "x"}
]
}
}
192/5 
I just wanted to check if you guys read carefully
Of cause its 192/7 
By the way, current 0.5 development status:
Please, dont forget fix password for yiimp pools: c=LTC,mc=INN/GUN/GBXNo.worry, there are more changes then just new mining codes. This is also on the List
192/5
By the way, current 0.5 development status:
Please, dont forget fix password for yiimp pools: c=LTC,mc=INN/GUN/GBX I'm bit confused where to set: Setting the WorkBatch (MNX, Equihash 96.5 only)
Can you provide me a example line and in where to place it.
In your guide it does not mention this cheers.
Can you provide me a example line and in where to place it.
In your guide it does not mention this cheers.
All option are used either as "PARAMETER" : VALUE in config file or -parameter=value in command line. So here it is "WORKBATCH" : "HIGH" (Or for example "WORKBATCH":12 for a fixed number) or -workbatch=HIGH in cmd. The parameter controls how many instances of 96/5 are allowed to run at same time / how much of the available GPU memory the miner is allowed to use.
-------------
By the way, current 0.5 development status:
| Algorithm | AMD | Nvidia |
| 96/5 | In testing | In Tuning |
| 144/5 | Ready | In testing |
| 192/7 | Ready | In testing |
| Aion | In dev | In dev |
| (210/9) | (Stratum ready) | (Stratum ready) |
I'm bit confused where to set: Setting the WorkBatch (MNX, Equihash 96.5 only)
Can you provide me a example line and in where to place it.
In your guide it does not mention this cheers.
Can you provide me a example line and in where to place it.
In your guide it does not mention this cheers.
"EXAMPLE_ANON" :
{
"COIN" : "AUTO144",
"POOLS" : [
{"POOL" : "ANON.suprnova.cc",
"PORT" : "7060",
"USER" : "myanonimous.banic",
"PASS" : "x"}
]
like this. at the first example!
well..it s working now . thanx. would be better if would rise the hasrate with rx cards
{
"COIN" : "AUTO144",
"POOLS" : [
{"POOL" : "ANON.suprnova.cc",
"PORT" : "7060",
"USER" : "myanonimous.banic",
"PASS" : "x"}
]
like this. at the first example!
well..it s working now . thanx. would be better if would rise the hasrate with rx cards
Jump to: