|
1101
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.6.8 - V8 & algo switching
|
on: October 18, 2018, 03:39:28 PM
|
heyho, Im new to SRBMiner since today. All my Vega Rigs are running fine so far...except one  Im trying to give each card manual settings, however it doesnt seem to work -> always get parseError. These are the settings im trying to use: "gpu_conf" :
[
{ "id" : 0, "intensity" : 120, "worksize" : 16, "threads" : 2},
{ "id" : 1, "intensity" : 120, "worksize" : 16, "threads" : 2},
{ "id" : 2, "intensity" : 120, "worksize" : 16, "threads" : 2},
{ "id" : 3, "intensity" : 120, "worksize" : 16, "threads" : 2},
{ "id" : 4, "intensity" : 120, "worksize" : 16, "threads" : 2},
{ "id" : 5, "intensity" : 120, "worksize" : 16, "threads" : 2},
{ "id" : 6, "intensity" : 120, "worksize" : 16, "threads" : 2},
{ "id" : 7, "intensity" : 120, "worksize" : 16, "threads" : 2},
{ "id" : 8, "intensity" : 120, "worksize" : 16, "threads" : 2}
] what am I doing wrong? Thanks in advance Post the whole config, this part looks OK |
|
|
|
|
1106
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.6.8 - V8 & algo switching
|
on: October 18, 2018, 09:38:11 AM
|
Hey Doc, SRBMiner API call: { "rig_name": "GKMiner", "cryptonight_type": "normalv7", "miner_version": "1.6.8", "driver_version": "24.20.11021.1000", [u][b]"mining_time": 2[/b][/u], "total_devices": 6, "total_threads": 12, "hashrate_total_now": 0, "hashrate_total_1min": 0, "hashrate_total_5min": 0, "hashrate_total_30min": 0, "hashrate_total_max": 0, "pool": { "pool": "asia.cryptonight-hub.miningpoolhub.com:20580", "difficulty": 0, [u][b]"time_connected": "1970-01-01 05:30:00", "uptime": 1539850156[/b][/u], "latency": 0, "last_job_received": 1 }, "shares": { "total": 0, "accepted": 0, "accepted_stale": 0, "rejected": 0, "avg_find_time": 0 }, "devices": [ { "device": "GPU0", "device_id": 0, "model": "Radeon RX Vega", "bus_id": 19, "kernel_id": 1, "hashrate": 0, "core_clock": 1630, "memory_clock": 1100, "temperature": 41, "fan_speed_rpm": 3795 }, { "device": "GPU1", "device_id": 1, "model": "Radeon RX Vega", "bus_id": 13, "kernel_id": 1, "hashrate": 0, "core_clock": 1630, "memory_clock": 1100, "temperature": 40, "fan_speed_rpm": 3743 }, { "device": "GPU2", "device_id": 2, "model": "Radeon RX Vega", "bus_id": 16, "kernel_id": 1, "hashrate": 0, "core_clock": 1630, "memory_clock": 1100, "temperature": 40, "fan_speed_rpm": 3819 }, { "device": "GPU3", "device_id": 3, "model": "Radeon RX Vega", "bus_id": 9, "kernel_id": 1, "hashrate": 0, "core_clock": 1630, "memory_clock": 1100, "temperature": 38, "fan_speed_rpm": 3833 }, { "device": "GPU4", "device_id": 4, "model": "Radeon RX Vega", "bus_id": 3, "kernel_id": 1, "hashrate": 0, "core_clock": 1630, "memory_clock": 1100, "temperature": 38, "fan_speed_rpm": 3760 }, { "device": "GPU5", "device_id": 5, "model": "Radeon RX Vega", "bus_id": 6, "kernel_id": 1, "hashrate": 0, "core_clock": 1630, "memory_clock": 1100, "temperature": 39, "fan_speed_rpm": 3809 } ]}This is an API call made after the miner has started( "mining_time": 2), but before it is connected to the pool ( "time_connected": "1970-01-01 05:30:00", "uptime": 1539850156). Can u fix this, so the Uptime shows 0 instead of the UNIX timestamp? Its throwing the charts crazy. going to check it out  |
|
|
|
|
1110
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.6.8 - V8 & algo switching
|
on: October 17, 2018, 10:15:30 AM
|
Dok, is there a way to incorporate MoneroV8 into the pools-algoswitch file, i.e. moneroocean would switch to MoneroV8 automatically if it's included there? I'd like to keep using the normal algoswitching until the fork - and then, arguably, moneroocean would switch everyone to Monerov8 after the fork.
...or do I need to restrict mining to XMR and populate the pools-fork.txt file with the v7 and v8 pools for it to switch?
if you are using MO, and the pool sends you a new job that is V8, miner will restart automatically with the v8 settings, so you don't need the pools-fork.txt trick. Fantastic! I'll just add the v8 settings and pool under the algoswitch and bob's my uncle. If profitability lives up to expectations MO should switch to V8 pretty much straight after the fork goes live. We will see I am working on algo switching without miner restart, and everything works when NOT using MO (manual pool switch, that has different algo), but i still have to find why app crashes badly with MO algo switching  |
|
|
|
|
1111
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.6.8 - V8 & algo switching
|
on: October 17, 2018, 10:02:23 AM
|
Dok, is there a way to incorporate MoneroV8 into the pools-algoswitch file, i.e. moneroocean would switch to MoneroV8 automatically if it's included there? I'd like to keep using the normal algoswitching until the fork - and then, arguably, moneroocean would switch everyone to Monerov8 after the fork.
...or do I need to restrict mining to XMR and populate the pools-fork.txt file with the v7 and v8 pools for it to switch?
if you are using MO, and the pool sends you a new job that is V8, miner will restart automatically with the v8 settings, so you don't need the pools-fork.txt trick. |
|
|
|
|
1116
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.6.8 - V8 & algo switching
|
on: October 16, 2018, 06:25:43 AM
|
relative to pitcairn 370 2gb
I get a maximum of 370 h / s on v8
1000 - 1420 gpu / mem
-i 27 -w 16 -k 1
but new problems have arisen
there are compute errors on these maps
I tried the 18.6.1, 18.5.2 driver
changed the intensity of the core frequency and memory errors appear again
then tested v7 - 490h / s
970 - 1400 gpu / mem
-i 30 -w 8 -k 1
compute errors again
question where is the problem?
try on blockchain drivers, one of the users reported to me that on r7 370 on blockchain drivers works good with 1.6.8 |
|
|
|
|
1119
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.6.8 - V8 & algo switching
|
on: October 15, 2018, 07:03:43 PM
|
Loving this miner!
Just a quick query, is there any built in hash rate monitoring? Did I miss it?
Sometimes Vega's are dropping hash and a hash watch dog where you can set a threshold before the miner restarts would be awesome!
I guess you haven't check the first page, or the readme.txt. config.txt "min_rig_speed" : number - in H/S, it defines the minimum rig hashing speed we want to maintain. If 5 minute average hashing speed is less than this, miner restarts. "min_rig_speed_duration" : number - in seconds (minimum is 30 sec), defines the time period for average hashing speed calculation, used with 'min_rig_speed' parameter |
|
|
|
|
1120
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.6.8 - V8 & algo switching
|
on: October 14, 2018, 07:53:16 PM
|
Hi
Excuse me because I am very new, I am trying to configure the intensities of the gpus manually.
If I use this configuration it works fine
{
"cryptonight_type" : "bittubev2",
"intensity" : 0,
"double_threads" : true
}
I'm trying to use this configuration but I do not know if it's okay
{
"cryptonight_type" : "bittubev2",
"gpu_conf" :
[
{ "id" : 0, "intensity" : 54, "worksize" : 8, "threads" : 2},
{ "id" : 1, "intensity" : 54, "worksize" : 8, "threads" : 2},
{ "id" : 2, "intensity" : 54, "worksize" : 8, "threads" : 2},
{ "id" : 3, "intensity" : 54, "worksize" : 8, "threads" : 2}
]
}
When the active rig is blocked, so I continue to use the initial configuration for now.
My gpus are rx 580/570
Is the configuration I try in manual wrong?
This should work: {
"cryptonight_type" : "bittubev2",
"intensity" : 0,
"double_threads" : true,
"gpu_conf" :
[
{
"id" : 0,
"intensity" : 54,
"worksize" : 8,
"threads" : 2
},
{
"id" : 1,
"intensity" : 54,
"worksize" : 8,
"threads" : 2
},
{
"id" : 2,
"intensity" : 54,
"worksize" : 8,
"threads" : 2
},
{
"id" : 3,
"intensity" : 54,
"worksize" : 8,
"threads" : 2
}
]
}
When the active rig is blocked This i don't understand |
|
|
|
|
Show Posts
