Pool Fee %: 15  Not so good... And I cannot follow my stats in this pool. For me it works, but i really don't know what I'm testing  How can we specify custom diff ? |
|
|
|
Pool Fee %: 15 |
|
|
|
V1.5.1- Finally added API, now you can monitor your rigs with 3rd party apps - Added parameter "restart_devices_on_startup_script" in config file, if "restart_devices_on_startup" is used, this new parameter can run a batch file from the miner directory after resetting the GPU's + If you need to disable/enable your Vegas before mining, or after miner restart, you use the "restart_devices_on_startup" parameter. You will probably want to set your overclocking settings after this (OverdriveNTool or something). This is what "restart_devices_on_startup_script" option is for, put the name of the batch file here (that is in miner directory), and set everything you need in that .bat. After the devices are disabled/enabled, this batch file will run. + RESTful API IS HERE FINALLYNow you got monitoring capabilities for your favorite rig monitoring tool. API is read only, that means you can't set anything, it just gives you back info about actual settings. To turn on API use "api_enabled" : true in the config file. Default port is 21555, but you can change it using "api_port" parameter. If you want you can name your rig with "api_rig_name" : "myrigname" so you can easily identify it in the monitoring app. When enabled it returns a json string with lots of goodies. You can access it on http://127.0.0.1:21555. Here is an example from a rig : {
"rig_name": "R9380",
"cryptonight_type": "heavy",
"mining_time": 168,
"total_devices": 4,
"total_threads": 8,
"hashrate_total_now": 1881,
"hashrate_total_5min": 0,
"hashrate_total_30min": 0,
"hashrate_total_max": 1968,
"pool": {
"pool": "pool.sumokoin.com:5555",
"difficulty": 160003,
"time_connected": "2018-05-03 14:30:36",
"uptime": 167,
"latency": 148
},
"shares": {
"total": 5,
"accepted": 5,
"rejected": 0,
"avg_find_time": 33
},
"devices": [
{
"device": "GPU0",
"device_id": 0,
"model": "AMD Radeon (TM) R9 380 Series",
"bus_id": 5,
"kernel_id": 1,
"hashrate": 500,
"core_clock": 880,
"memory_clock": 1600,
"temperature": 52,
"fan_speed_rpm": 1457
},
{
"device": "GPU1",
"device_id": 1,
"model": "AMD Radeon (TM) R9 380 Series",
"bus_id": 2,
"kernel_id": 1,
"hashrate": 500,
"core_clock": 880,
"memory_clock": 1600,
"temperature": 59,
"fan_speed_rpm": 1983
},
{
"device": "GPU2",
"device_id": 2,
"model": "AMD Radeon (TM) R9 380 Series",
"bus_id": 1,
"kernel_id": 1,
"hashrate": 444,
"core_clock": 880,
"memory_clock": 1600,
"temperature": 59,
"fan_speed_rpm": 1987
},
{
"device": "GPU3",
"device_id": 3,
"model": "AMD Radeon (TM) R9 380 Series",
"bus_id": 3,
"kernel_id": 1,
"hashrate": 486,
"core_clock": 880,
"memory_clock": 1600,
"temperature": 56,
"fan_speed_rpm": 1835
}
]
}
Thanks ! |
|
|
|
63 seconds between ANN and first operational pool. Is this really possible ? |
|
|
|
Trying to test custom timings functionality, but launching Boost mode on a RX580 without bios mod immediately crash gpu  |
|
|
|
What are the values we need to play first in custom memory timings ? Thanks
That's hard to say. The safest bet is to run the miner at a memory clock rate *lower* than the default one and capture the timings *while the miner is running.* For example, if the stock memory clock rate is 2000 Mhz, you could try 1750Mhz or 1625Mhz. Alternatively, you could try an existing strap for your memory vendor, but that's rather tricky. Once you have a working set of memory timings, then you should try to zero out TFAW and T32AW to see if that would work. You could also lower TRRD. An important thing to note is that the automatic optimizer would not touch these three parameters, so you need to experiment yourself. Generally speaking, Samsung GDDR5 is quite happy with TFAW=0 and T32AW=0, whereas you need to raise T32AW slightly for Hynix. Will try to play with TFAW, T32AW and TRRD, thanks  |
|
|
|
|
What are the values we need to play first in custom memory timings ? Thanks
|
|
|
|
|
Why deposit addresses take so long time to be created ?
I'm trying to create a SUN address, since long minutes, refreshed page, logout/login, and always no address ...
That was the same with all addresses created on other coins.
Really painful ...
EDIT : 1h30 later, always no SUN address ...
|
|
|
|
I was mining fine with (6x)Vega 64 on UltraHeavy(the lite one) despite not knowing the config. Ive set intensity 110, worksize 16 adn threads 2 = 18000h I did not tried any other config cuz 18k was fine to me. I know it could do more in this algo. Doctor,My doubt is, setting threads 2 in the config lines and not changing top from false to true will it work with 2? Looks you do have the same parameter in two places. PS. I do not recommend IPBC support pool cuz of the pool config setting too high diff. My client stayed 10min without sending hash with diff 2500000. This do not look a mistake at all...
This one is better: https://cryptoknight.cc/ipbc/Can someone share a config to Vega 64 that makes it hash 2k in Monero7 algo? Just force diff with wallet.diff |
|
|
|
|
What hashrate can we expect on 1070/1070ti ? Thanks
|
|
|
|
Wanna more than 200 at RX550 2Gb Buffin unlocked!
Please, help with config((
This card does 400 to 450. Mine does with Claymore, not with SRB. |
|
|
|
|
Problem about devfee is not really a devfee problem ...
I now run rigs with the nofee option and I always have the problem : miner stop founding share ...
|
|
|
|
Any news on my devfee problem ?
And on a version with command line parameters and not in config file ?
Thanks
working on devfee and logging, command line parameters not important right now. Elaborate, why isn't config file ok for you? To configure new coin with your miner, we are forced to do it on each rig. Very time consuming when you have to do it on few rigs. With miner having full command line parameters, i've just to configure it in my tool and miner starts/restarts without having remote session on rig. |
|
|
|
|
Any news on my devfee problem ?
And on a version with command line parameters and not in config file ?
Thanks
|
|
|
|
|
Log for devfee problem shows nothing :
[2018-04-10 12:04:28] GPU0: 692.0 H/S [yellowblack{T: 51c, RPM: 1126}]
[2018-04-10 12:04:28] GPU1: 692.0 H/S [yellowblack{T: 51c, RPM: 1126}]
[2018-04-10 12:04:28] GPU2: 692.0 H/S [yellowblack{T: 65c, RPM: 1104}]
[2018-04-10 12:04:28] GPU3: 669.0 H/S [yellowblack{T: 65c, RPM: 1104}]
[2018-04-10 12:04:28] yellowblack{Total: 2745.0 H/S}
[2018-04-10 12:04:31] limeblack{Pool accepted result 0x0000F8F6}
[2018-04-10 12:04:59] limeblack{Pool accepted result 0x0000FE46}
[2018-04-10 12:05:08] limeblack{Pool accepted result 0x0001769B}
[2018-04-10 12:05:12] limeblack{Pool accepted result 0x00019751}
[2018-04-10 12:05:27] limeblack{Pool accepted result 0x000064BE}
[2018-04-10 12:05:45] limeblack{Pool accepted result 0x0000CD77}
[2018-04-10 12:06:09] limeblack{Pool accepted result 0x00016F5C}
[2018-04-10 12:06:16] limeblack{Pool accepted result 0x0000EBDE}
[2018-04-10 12:06:30] limeblack{Pool accepted result 0x00018995}
[2018-04-10 12:06:34] limeblack{Pool accepted result 0x00014BB4}
[2018-04-10 12:07:24] limeblack{Pool accepted result 0x0000297A}
[2018-04-10 12:07:28] GPU0: 693.0 H/S [yellowblack{T: 51c, RPM: 1127}]
[2018-04-10 12:07:28] GPU1: 687.0 H/S [yellowblack{T: 51c, RPM: 1127}]
[2018-04-10 12:07:28] GPU2: 692.0 H/S [yellowblack{T: 65c, RPM: 1104}]
[2018-04-10 12:07:28] GPU3: 678.0 H/S [yellowblack{T: 65c, RPM: 1104}]
[2018-04-10 12:07:28] yellowblack{Total: 2750.0 H/S}
[2018-04-10 12:07:49] limeblack{Pool accepted result 0x000198C0}
[2018-04-10 12:08:00] limeblack{Pool accepted result 0x0000C054}
[2018-04-10 12:08:10] limeblack{Pool accepted result 0x00000A11}
[2018-04-10 12:08:11] limeblack{Pool accepted result 0x00003780}
[2018-04-10 12:08:18] limeblack{Pool accepted result 0x00002B69}
[2018-04-10 12:08:33] Pool sent a new job (ID: 9494)
[2018-04-10 12:08:46] limeblack{Pool accepted result 0x0000498B}
[2018-04-10 12:08:49] limeblack{Pool accepted result 0x00006AA7}
[2018-04-10 12:08:53] limeblack{Pool accepted result 0x0000060B}
[2018-04-10 12:08:58] limeblack{Pool accepted result 0x00019AC4}
[2018-04-10 12:09:09] limeblack{Pool accepted result 0x000040D9}
[2018-04-10 12:09:23] Connected to devfee pool
[2018-04-10 12:10:28] GPU0: 692.0 H/S [yellowblack{T: 51c, RPM: 1129}]
[2018-04-10 12:10:28] GPU1: 696.0 H/S [yellowblack{T: 51c, RPM: 1129}]
[2018-04-10 12:10:28] GPU2: 692.0 H/S [yellowblack{T: 65c, RPM: 1105}]
[2018-04-10 12:10:28] GPU3: 678.0 H/S [yellowblack{T: 65c, RPM: 1105}]
[2018-04-10 12:10:28] yellowblack{Total: 2758.0 H/S}
[2018-04-10 12:13:28] GPU0: 694.0 H/S [yellowblack{T: 51c, RPM: 1128}]
[2018-04-10 12:13:28] GPU1: 693.0 H/S [yellowblack{T: 51c, RPM: 1128}]
[2018-04-10 12:13:28] GPU2: 692.0 H/S [yellowblack{T: 64c, RPM: 1105}]
[2018-04-10 12:13:28] GPU3: 678.0 H/S [yellowblack{T: 64c, RPM: 1105}]
[2018-04-10 12:13:28] yellowblack{Total: 2757.0 H/S}
[2018-04-10 12:16:29] GPU0: 693.0 H/S [yellowblack{T: 51c, RPM: 1127}]
[2018-04-10 12:16:29] GPU1: 694.0 H/S [yellowblack{T: 51c, RPM: 1127}]
[2018-04-10 12:16:29] GPU2: 692.0 H/S [yellowblack{T: 65c, RPM: 1104}]
[2018-04-10 12:16:29] GPU3: 682.0 H/S [yellowblack{T: 65c, RPM: 1104}]
[2018-04-10 12:16:29] yellowblack{Total: 2761.0 H/S}
[2018-04-10 12:19:29] GPU0: 684.0 H/S [yellowblack{T: 51c, RPM: 1127}]
[2018-04-10 12:19:29] GPU1: 694.0 H/S [yellowblack{T: 51c, RPM: 1127}]
[2018-04-10 12:19:29] GPU2: 692.0 H/S [yellowblack{T: 65c, RPM: 1102}]
[2018-04-10 12:19:29] GPU3: 670.0 H/S [yellowblack{T: 65c, RPM: 1102}]
[2018-04-10 12:19:29] yellowblack{Total: 2740.0 H/S}
[2018-04-10 12:22:29] GPU0: 692.0 H/S [yellowblack{T: 51c, RPM: 1127}]
[2018-04-10 12:22:29] GPU1: 686.0 H/S [yellowblack{T: 51c, RPM: 1127}]
[2018-04-10 12:22:29] GPU2: 692.0 H/S [yellowblack{T: 65c, RPM: 1103}]
[2018-04-10 12:22:29] GPU3: 678.0 H/S [yellowblack{T: 65c, RPM: 1103}]
[2018-04-10 12:22:29] yellowblack{Total: 2748.0 H/S}
[2018-04-10 12:25:29] GPU0: 692.0 H/S [yellowblack{T: 51c, RPM: 1129}]
[2018-04-10 12:25:29] GPU1: 694.0 H/S [yellowblack{T: 51c, RPM: 1129}]
[2018-04-10 12:25:29] GPU2: 694.0 H/S [yellowblack{T: 65c, RPM: 1101}]
[2018-04-10 12:25:29] GPU3: 671.0 H/S [yellowblack{T: 65c, RPM: 1101}]
[2018-04-10 12:25:29] yellowblack{Total: 2751.0 H/S}
[2018-04-10 12:28:30] GPU0: 693.0 H/S [yellowblack{T: 51c, RPM: 1127}]
[2018-04-10 12:28:30] GPU1: 683.0 H/S [yellowblack{T: 51c, RPM: 1127}]
[2018-04-10 12:28:30] GPU2: 692.0 H/S [yellowblack{T: 65c, RPM: 1105}]
[2018-04-10 12:28:30] GPU3: 668.0 H/S [yellowblack{T: 65c, RPM: 1105}]
[2018-04-10 12:28:30] yellowblack{Total: 2736.0 H/S}
[2018-04-10 12:31:30] GPU0: 680.0 H/S [yellowblack{T: 51c, RPM: 1127}]
[2018-04-10 12:31:30] GPU1: 695.0 H/S [yellowblack{T: 51c, RPM: 1127}]
[2018-04-10 12:31:30] GPU2: 693.0 H/S [yellowblack{T: 65c, RPM: 1106}]
[2018-04-10 12:31:30] GPU3: 678.0 H/S [yellowblack{T: 65c, RPM: 1106}]
[2018-04-10 12:31:30] yellowblack{Total: 2746.0 H/S}
[2018-04-10 12:34:30] GPU0: 692.0 H/S [yellowblack{T: 51c, RPM: 1129}]
[2018-04-10 12:34:30] GPU1: 692.0 H/S [yellowblack{T: 51c, RPM: 1129}]
[2018-04-10 12:34:30] GPU2: 694.0 H/S [yellowblack{T: 65c, RPM: 1105}]
[2018-04-10 12:34:30] GPU3: 678.0 H/S [yellowblack{T: 65c, RPM: 1105}]
[2018-04-10 12:34:30] yellowblack{Total: 2756.0 H/S}
[2018-04-10 12:37:31] GPU0: 692.0 H/S [yellowblack{T: 51c, RPM: 1131}]
[2018-04-10 12:37:31] GPU1: 693.0 H/S [yellowblack{T: 51c, RPM: 1131}]
[2018-04-10 12:37:31] GPU2: 692.0 H/S [yellowblack{T: 65c, RPM: 1104}]
[2018-04-10 12:37:31] GPU3: 678.0 H/S [yellowblack{T: 65c, RPM: 1104}]
[2018-04-10 12:37:31] yellowblack{Total: 2755.0 H/S}
[2018-04-10 12:40:31] GPU0: 692.0 H/S [yellowblack{T: 51c, RPM: 1129}]
[2018-04-10 12:40:31] GPU1: 693.0 H/S [yellowblack{T: 51c, RPM: 1129}]
[2018-04-10 12:40:31] GPU2: 692.0 H/S [yellowblack{T: 65c, RPM: 1103}]
[2018-04-10 12:40:31] GPU3: 678.0 H/S [yellowblack{T: 65c, RPM: 1103}]
[2018-04-10 12:40:31] yellowblack{Total: 2755.0 H/S}
[2018-04-10 12:43:31] GPU0: 685.0 H/S [yellowblack{T: 51c, RPM: 1131}]
[2018-04-10 12:43:31] GPU1: 692.0 H/S [yellowblack{T: 51c, RPM: 1131}]
[2018-04-10 12:43:31] GPU2: 692.0 H/S [yellowblack{T: 65c, RPM: 1103}]
[2018-04-10 12:43:31] GPU3: 678.0 H/S [yellowblack{T: 65c, RPM: 1103}]
[2018-04-10 12:43:31] yellowblack{Total: 2747.0 H/S}
[2018-04-10 12:46:31] GPU0: 692.0 H/S [yellowblack{T: 51c, RPM: 1129}]
[2018-04-10 12:46:31] GPU1: 693.0 H/S [yellowblack{T: 51c, RPM: 1129}]
[2018-04-10 12:46:31] GPU2: 692.0 H/S [yellowblack{T: 65c, RPM: 1103}]
[2018-04-10 12:46:31] GPU3: 679.0 H/S [yellowblack{T: 65c, RPM: 1103}]
[2018-04-10 12:46:31] yellowblack{Total: 2756.0 H/S}
[2018-04-10 12:49:32] GPU0: 691.0 H/S [yellowblack{T: 51c, RPM: 1131}]
[2018-04-10 12:49:32] GPU1: 692.0 H/S [yellowblack{T: 51c, RPM: 1131}]
[2018-04-10 12:49:32] GPU2: 682.0 H/S [yellowblack{T: 65c, RPM: 1103}]
[2018-04-10 12:49:32] GPU3: 672.0 H/S [yellowblack{T: 65c, RPM: 1103}]
[2018-04-10 12:49:32] yellowblack{Total: 2737.0 H/S}
[2018-04-10 12:52:32] GPU0: 692.0 H/S [yellowblack{T: 52c, RPM: 1130}]
[2018-04-10 12:52:32] GPU1: 692.0 H/S [yellowblack{T: 52c, RPM: 1130}]
[2018-04-10 12:52:32] GPU2: 692.0 H/S [yellowblack{T: 65c, RPM: 1102}]
[2018-04-10 12:52:32] GPU3: 669.0 H/S [yellowblack{T: 65c, RPM: 1102}]
[2018-04-10 12:52:32] yellowblack{Total: 2745.0 H/S}
[2018-04-10 12:55:32] GPU0: 693.0 H/S [yellowblack{T: 51c, RPM: 1129}]
[2018-04-10 12:55:32] GPU1: 692.0 H/S [yellowblack{T: 51c, RPM: 1129}]
[2018-04-10 12:55:32] GPU2: 692.0 H/S [yellowblack{T: 65c, RPM: 1101}]
[2018-04-10 12:55:32] GPU3: 678.0 H/S [yellowblack{T: 65c, RPM: 1101}]
[2018-04-10 12:55:32] yellowblack{Total: 2755.0 H/S}
[2018-04-10 12:58:32] GPU0: 692.0 H/S [yellowblack{T: 51c, RPM: 1127}]
[2018-04-10 12:58:32] GPU1: 693.0 H/S [yellowblack{T: 51c, RPM: 1127}]
[2018-04-10 12:58:32] GPU2: 692.0 H/S [yellowblack{T: 64c, RPM: 1104}]
[2018-04-10 12:58:32] GPU3: 678.0 H/S [yellowblack{T: 64c, RPM: 1104}]
[2018-04-10 12:58:32] yellowblack{Total: 2755.0 H/S}
|
|
|
|
Any issue with devfee ? Just installed v1.3.1 on few rigs. Mining SUMO, with heavy algo. 2 of them have switched on devfee and I think they have never returned on main pool after that. Using usa server for devfee. No pics of that for the moment I've just enabled log EDIT : like that ! 18mn doing nothing !  i will make a more informative logging, so we can find out what is happening. Did it reconnect to your pool after those 18 minutes, or that never happened? After night, i've now 4 rigs in this case : doing nothing after switched to devfee, since hours ... |
|
|
|
|
Hi, can you please correct your ORE profitability, it gives incorrect value.
Thanks
|
|
|
|
Any issue with devfee ? Just installed v1.3.1 on few rigs. Mining SUMO, with heavy algo. 2 of them have switched on devfee and I think they have never returned on main pool after that. Using usa server for devfee. No pics of that for the moment I've just enabled log EDIT : like that ! 18mn doing nothing ! |
|
|
|
|
Any plan to have full command line parameters and not a config file ?
|
|
|
|
|
Show Posts
