|
doktor83 (OP)
|
 |
May 09, 2019, 02:17:55 PM |
|
V1.8.8- Reduced CPU usage up to ~50%, can be noticed on algos with small scratchpad - User is now informed about tweaking status on the screen too, not just in log - No more --gpureorder, device ordering by bus id is now the default/only display mode - Added parameter --watchdogrounds , which controls after how many rounds will watchdog trigger - min_rig_speed_duration default is 1 minute now, because of the new --watchdogrounds parameter - Fixed a few cosmetical things on web stats + If not using 'old_mode', on weak CPU's the cpu usage could go boom on algos with small scratchpad (UPX2, Turtle). In this version i managed to lower the cpu usage up to ~50%. This also brings a small hashrate increase for RX cards on UPX2 as a side effect  + The default (and only) device ordering mode from now on is ascending by bus id, as it is in OverdriveNTool. Parameter --gpureorder is removed. + Because of some trouble with gpu/min_rig_speed watchdog and kernel precompilation on CN/R (V4), a new parameter --watchdogrounds was added, so you can control after how many check-rounds will the watchdog trigger. The GPU crash watchdog has a fixed interval of 30 seconds = 1 round. That means it will trigger miner restart only after --watchdogrounds * 30 sec (default number of rounds is 5). 5 * 30 = 150 sec ~ 2.5 minutes. If gpu crashes and can't recover for 2.5 minutes, the miner will trigger the restart action. min_rig_speed parameter is also affected by --watchdogrounds from now on. The 'min_rig_speed_duration' parameter default value is now 60 sec, this is the value as the above for the gpu crash watchdog, except that you can change the value of this to anything >= 30 sec. Taking the default value of 60 seconds and 5 rounds, it is 5 * 60 = 300 sec = 5 minute, that means if for 5 minutes the 'min_rig_speed' < total hashing speed, then it will trigger miner restart. hi, my vega 64 CN-R algo without tweaking Hashrate dropped from 2040 to 1970 moving from 187 to 188 , same config and same pool file and same coin. interesting is that my vega 56 didnt get affected. Im running low voltage settings on both cards (at the most stable possible setting) Im running into the same issue. what did you do to fix? Read back a few posts |
|
|
|
|
|
|
|
|
|
|
|
|
Transactions must be included in a block to be properly completed. When you send a transaction, it is broadcast to miners. Miners can then optionally include it in their next blocks. Miners will be more inclined to include your transaction if it has a higher transaction fee.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
Fredeslim
Newbie
 Offline
Activity: 3
Merit: 0
|
|
May 09, 2019, 02:29:13 PM |
|
V1.8.8- Reduced CPU usage up to ~50%, can be noticed on algos with small scratchpad - User is now informed about tweaking status on the screen too, not just in log - No more --gpureorder, device ordering by bus id is now the default/only display mode - Added parameter --watchdogrounds , which controls after how many rounds will watchdog trigger - min_rig_speed_duration default is 1 minute now, because of the new --watchdogrounds parameter - Fixed a few cosmetical things on web stats + If not using 'old_mode', on weak CPU's the cpu usage could go boom on algos with small scratchpad (UPX2, Turtle). In this version i managed to lower the cpu usage up to ~50%. This also brings a small hashrate increase for RX cards on UPX2 as a side effect + The default (and only) device ordering mode from now on is ascending by bus id, as it is in OverdriveNTool. Parameter --gpureorder is removed. + Because of some trouble with gpu/min_rig_speed watchdog and kernel precompilation on CN/R (V4), a new parameter --watchdogrounds was added, so you can control after how many check-rounds will the watchdog trigger. The GPU crash watchdog has a fixed interval of 30 seconds = 1 round. That means it will trigger miner restart only after --watchdogrounds * 30 sec (default number of rounds is 5). 5 * 30 = 150 sec ~ 2.5 minutes. If gpu crashes and can't recover for 2.5 minutes, the miner will trigger the restart action. min_rig_speed parameter is also affected by --watchdogrounds from now on. The 'min_rig_speed_duration' parameter default value is now 60 sec, this is the value as the above for the gpu crash watchdog, except that you can change the value of this to anything >= 30 sec. Taking the default value of 60 seconds and 5 rounds, it is 5 * 60 = 300 sec = 5 minute, that means if for 5 minutes the 'min_rig_speed' < total hashing speed, then it will trigger miner restart. hi, my vega 64 CN-R algo without tweaking Hashrate dropped from 2040 to 1970 moving from 187 to 188 , same config and same pool file and same coin. interesting is that my vega 56 didnt get affected. Im running low voltage settings on both cards (at the most stable possible setting) Im running into the same issue. what did you do to fix? Read back a few posts you suggest changing the intensity? |
|
|
|
|
|
doktor83 (OP)
|
|
May 09, 2019, 04:07:40 PM |
|
you suggest changing the intensity?
No, i suggest reading the 1.8.8 release notes No more --gpureorder, device ordering by bus id is now the default/only display mode [NOTE: if you are using gpu_conf or --cgpuid, please run --listdevices to check if you are using the right deviceid!]
|
|
|
|
Fredeslim
Newbie
Offline
Activity: 3
Merit: 0
|
|
May 09, 2019, 05:03:04 PM |
|
you suggest changing the intensity?
No, i suggest reading the 1.8.8 release notes No more --gpureorder, device ordering by bus id is now the default/only display mode [NOTE: if you are using gpu_conf or --cgpuid, please run --listdevices to check if you are using the right deviceid!]
oh you mean setup the config file as this examples shows. { "cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"gpu_conf" :
[
{
"id" : 0,
"intensity" : 112,
"worksize" : 16,
"threads" : 2,
"tweak_profile" : 3
},
{
"id" : 1,
"intensity" : 112,
"worksize" : 16,
"threads" : 2,
"tweak_profile" : 4
},
{
"id" : 2,
"intensity" : 111,
"worksize" : 16,
"threads" : 2,
"tweak_profile" : 4
},
{
"id" : 3,
"intensity" : 110,
"worksize" : 16,
"threads" : 2,
"tweak_profile" : 5
}] } |
|
|
|
|
|
doktor83 (OP)
|
|
May 09, 2019, 05:05:59 PM |
|
you suggest changing the intensity?
No, i suggest reading the 1.8.8 release notes No more --gpureorder, device ordering by bus id is now the default/only display mode [NOTE: if you are using gpu_conf or --cgpuid, please run --listdevices to check if you are using the right deviceid!]
oh you mean setup the config file as this examples shows. I mean your device id's changed and are now ordered by busid, so what was id 3 is now maybe id 2, you should identify your devices with --listdevices , and edit your config according to those device id's. |
|
|
|
jimmyD30
Jr. Member
Offline
Activity: 64
Merit: 1
|
|
May 10, 2019, 03:06:05 PM |
|
Hello, does anyone know the difference b/w ‘normalv4_64‘ and ‘normalv4’ algos?
|
|
|
|
|
|
doktor83 (OP)
|
|
May 10, 2019, 03:07:17 PM |
|
Hello, does anyone know the difference b/w ‘normalv4_64‘ and ‘normalv4’ algos?
normalv4 = CN/R normalv4_64 not in use atm |
|
|
|
Rabotaet
Newbie
Offline
Activity: 15
Merit: 0
|
|
May 10, 2019, 05:12:35 PM |
|
1) Precompiling program BUS.....
Finished program precompilation BUS...
....infinitely............
2)When the miner starts, it displays a message
Error: Description = Invalid query
What does this mean?
|
|
|
|
|
|
doktor83 (OP)
|
|
May 10, 2019, 06:29:17 PM |
|
1) Precompiling program BUS.....
Finished program precompilation BUS...
....infinitely............
2)When the miner starts, it displays a message
Error: Description = Invalid query
What does this mean?
Can you upload a logfile somewhere? |
|
|
|
|
doktor83 (OP)
|
|
May 11, 2019, 05:26:18 AM |
|
anyone knows why my computer uses a tweak a few moments later, often sight out and black screen....help me doc  Its hard to help if you dont provide any information |
|
|
|
jimmyD30
Jr. Member
Offline
Activity: 64
Merit: 1
|
|
May 11, 2019, 04:22:23 PM |
|
Hello, does anyone know the difference b/w ‘normalv4_64‘ and ‘normalv4’ algos?
normalv4 = CN/R normalv4_64 not in use atm :-) Probably (hopefully?) a special kernel for my Vega ‘64’s? |
|
|
|
|
Rabotaet
Newbie
Offline
Activity: 15
Merit: 0
|
|
May 11, 2019, 08:06:39 PM |
|
|
|
|
|
|
NCarter84
Jr. Member
Offline
Activity: 195
Merit: 4
|
|
May 12, 2019, 03:54:23 AM |
|
Is there a way to elevate via command line? I know with JCE he had the '--elevate' option.
|
|
|
|
|
|
doktor83 (OP)
|
|
May 12, 2019, 09:19:54 AM
Last edit: May 12, 2019, 10:10:26 AM by doktor83 |
|
[2019-05-11 22:47:31] GPU0: Radeon RX 560 Series [baffin] [2048 MB][I: 26.0][W: 32][T: 2][F: 8][BUS: 1]
[2019-05-11 22:47:31] GPU1: Radeon RX 560 Series [baffin] [2048 MB][I: 26.0][W: 32][T: 2][F: 8][BUS: 1]
[2019-05-11 22:47:31] GPU2: Radeon RX 560 Series [baffin] [2048 MB][I: 26.0][W: 32][T: 2][F: 8][BUS: 5]
[2019-05-11 22:47:31] GPU3: Radeon RX 560 Series [baffin] [2048 MB][I: 26.0][W: 32][T: 2][F: 8][BUS: 5]
Something is messed up, gpu's have same bus id's, and that shouldn't happen. Driver is reporting it bad. Try to DDU & reinstall video drivers. Or if using the duplicateid parameter disable it |
|
|
|
Markyz23
Newbie
Offline
Activity: 30
Merit: 0
|
|
May 12, 2019, 11:21:08 AM |
|
Hei doctor.
Is AMD HD 7750 supported?
|
|
|
|
|
livada
Newbie
Offline
Activity: 417
Merit: 0
|
|
May 12, 2019, 06:45:51 PM |
|
i try send PM but ypou block mesage and i must send this... You block AMD mem TWEAK forever with 1.8.8? After start srbminer 1.8.8 AMD mem TWEAK not work. restart not solved this . ALways say EIO error. Any sugest or i must reinstal windows if use 1.8.8 version? 1.8.7 and 1.8.6 block AMD tweak but after restart all work. Now 1.8.8 block AMD tweak forever  WTF |
|
|
|
|
|
doktor83 (OP)
|
|
May 12, 2019, 07:39:23 PM |
|
i try send PM but ypou block mesage and i must send this... You block AMD mem TWEAK forever with 1.8.8? After start srbminer 1.8.8 AMD mem TWEAK not work. restart not solved this . ALways say EIO error. Any sugest or i must reinstal windows if use 1.8.8 version? 1.8.7 and 1.8.6 block AMD tweak but after restart all work. Now 1.8.8 block AMD tweak forever WTF It does not 'block forever', if miner is not running nothing is 'blocked'. Restart solves everything. Use --disabletweaking as i told many times and use ElioVP's tool. Don't mix and you are good. |
|
|
|
livada
Newbie
Offline
Activity: 417
Merit: 0
|
|
May 12, 2019, 07:52:15 PM
Last edit: May 12, 2019, 08:03:32 PM by livada |
|
i try send PM but ypou block mesage and i must send this... You block AMD mem TWEAK forever with 1.8.8? After start srbminer 1.8.8 AMD mem TWEAK not work. restart not solved this . ALways say EIO error. Any sugest or i must reinstal windows if use 1.8.8 version? 1.8.7 and 1.8.6 block AMD tweak but after restart all work. Now 1.8.8 block AMD tweak forever WTF It does not 'block forever', if miner is not running nothing is 'blocked'. Restart solves everything. Use --disabletweaking as i told many times and use ElioVP's tool. Don't mix and you are good. read my post. after start 1.8.8 AMD tweak block forever. Now i not start AMD tweak. afterr restart AMD not work. you block this forever. this is big prbolem now . Now i must reinstal Win? howe you block this? give me any soluton for unblock EIO.dll. you block in registry? not in memory. if block only in memopry after restart amd must work. i not tell not work in SRBMINER aMD not work with cli mode gui mode or any miner after 1.8.8 start. block FOREVER And i understud why you block AMD tweak befoe start but not understud why you not UNBLOCK AMD tweak after close srb miner? |
|
|
|
|
|
doktor83 (OP)
|
|
May 12, 2019, 08:21:46 PM |
|
i try send PM but ypou block mesage and i must send this... You block AMD mem TWEAK forever with 1.8.8? After start srbminer 1.8.8 AMD mem TWEAK not work. restart not solved this . ALways say EIO error. Any sugest or i must reinstal windows if use 1.8.8 version? 1.8.7 and 1.8.6 block AMD tweak but after restart all work. Now 1.8.8 block AMD tweak forever WTF It does not 'block forever', if miner is not running nothing is 'blocked'. Restart solves everything. Use --disabletweaking as i told many times and use ElioVP's tool. Don't mix and you are good. read my post. after start 1.8.8 AMD tweak block forever. Now i not start AMD tweak. afterr restart AMD not work. you block this forever. this is big prbolem now . Now i must reinstal Win? howe you block this? give me any soluton for unblock EIO.dll. you block in registry? not in memory. if block only in memopry after restart amd must work. i not tell not work in SRBMINER aMD not work with cli mode gui mode or any miner after 1.8.8 start. block FOREVER And i understud why you block AMD tweak befoe start but not understud why you not UNBLOCK AMD tweak after close srb miner? Im tired of this, and dont have anything else to add. You are wrong, its not 'blocking forever'. Tested on few rigs + got a few guys test it for me. After restart all good. I know you will continue your rage, but i wont react to it anymore, dont want to repeat myself 100x times again. |
|
|
|
livada
Newbie
Offline
Activity: 417
Merit: 0
|
|
May 12, 2019, 08:32:57 PM
Last edit: May 12, 2019, 08:43:19 PM by livada |
|
i try send PM but ypou block mesage and i must send this... You block AMD mem TWEAK forever with 1.8.8? After start srbminer 1.8.8 AMD mem TWEAK not work. restart not solved this . ALways say EIO error. Any sugest or i must reinstal windows if use 1.8.8 version? 1.8.7 and 1.8.6 block AMD tweak but after restart all work. Now 1.8.8 block AMD tweak forever WTF It does not 'block forever', if miner is not running nothing is 'blocked'. Restart solves everything. Use --disabletweaking as i told many times and use ElioVP's tool. Don't mix and you are good. read my post. after start 1.8.8 AMD tweak block forever. Now i not start AMD tweak. afterr restart AMD not work. you block this forever. this is big prbolem now . Now i must reinstal Win? howe you block this? give me any soluton for unblock EIO.dll. you block in registry? not in memory. if block only in memory after restart and must work. i not tell not work in SRBMINER AMD not work with cli mode gui mode or any miner after 1.8.8 start. block FOREVER And i understud why you block AMD tweak befoe start but not understud why you not UNBLOCK AMD tweak after close srb miner? Im tired of this, and dont have anything else to add. You are wrong, its not 'blocking forever'. Tested on few rigs + got a few guys test it for me. After restart all good. I know you will continue your rage, but i wont react to it anymore, dont want to repeat myself 100x times again.
HOW YOU BLOCK ELIO AMD MEM TWAEK. GIVE ANY SOLUTION FOR UNBLOCK THIS. you broke my woindows adn you say this BEST MINER? and yes im angry . you hapy after any program broke your windows?and not problem for not help with this. you only use for all but give nothing. i restaret windows and i send every day this problem in this topic forever like you block forever EIO.dll And you say you tested not bug.but i see on your first page :fixed bug this . fixed bug other etc. how you have any bug if you tested? if you tested you never must repair any bug....this is big shit . you not test this and you repair this in other version but you so so overwhelmed to admit that you took the program and deliberately blocked it. |
|
|
|
|
|
