SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching - page 244.

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: MaxMidnite on June 02, 2018, 01:10:58 PM

Quote from: doktor83 on June 02, 2018, 12:41:28 PM

V1.5.8
- Fixed a bug in pool switching process
- Fixed a bug in watchdog's "reboot_script"
- Changed default devfee pool for Heavy algo

+ I would like to politely ask everyone if they appreciate my work, to switch their miners to this new version.

The default devfee pool for heavy algo was pool.sumokoin.com, which is under the control of the origin Sumo team.
They self-decided, without any community voting or anything to switch their algo back to now ASIC friendly Cryptonight from block 137500.
That will happen in about two days.
What this means to users of SRBMiner/Me ? On previous versions if you mine any coin on 'heavy' algo from monday, the devfee will connect to pool.sumokoin.com using 'heavy' algo,
but the pool will be using classic CN, so shares will be ALL rejected, and i won't be getting the 0.85% fee.

Thank you in advance, if you are going to support me and going to switch to this version.

The results did not change between kernels maybe little hash change 1-5hash.
Another question if I set,

/* Intensity 0-> auto intensity, or value from 1-300 */
"intensity" : 0,

The confusion is does it take the intensity auto or the gpu_conf values??

If you set intensity in gpu_conf, the setting on top of the config will get disabled, so the one from gpu_conf will be used.

MaxMidnite

newbie

Activity: 143

Merit: 0

Quote from: doktor83 on June 02, 2018, 12:41:28 PM

V1.5.8
- Fixed a bug in pool switching process
- Fixed a bug in watchdog's "reboot_script"
- Changed default devfee pool for Heavy algo

+ I would like to politely ask everyone if they appreciate my work, to switch their miners to this new version.

The default devfee pool for heavy algo was pool.sumokoin.com, which is under the control of the origin Sumo team.
They self-decided, without any community voting or anything to switch their algo back to now ASIC friendly Cryptonight from block 137500.
That will happen in about two days.
What this means to users of SRBMiner/Me ? On previous versions if you mine any coin on 'heavy' algo from monday, the devfee will connect to pool.sumokoin.com using 'heavy' algo,
but the pool will be using classic CN, so shares will be ALL rejected, and i won't be getting the 0.85% fee.

Thank you in advance, if you are going to support me and going to switch to this version.

The results did not change between kernels maybe little hash change 1-5hash.
Another question if I set,

/* Intensity 0-> auto intensity, or value from 1-300 */
"intensity" : 0,

The confusion is does it take the intensity auto or the gpu_conf values??

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: heavyarms1912 on June 02, 2018, 12:47:05 PM

Quote from: doktor83 on June 02, 2018, 12:41:28 PM

V1.5.8
- Fixed a bug in pool switching process
- Fixed a bug in watchdog's "reboot_script"
- Changed default devfee pool for Heavy algo

+ I would like to politely ask everyone if they appreciate my work, to switch their miners to this new version.

The default devfee pool for heavy algo was pool.sumokoin.com, which is under the control of the origin Sumo team.
They self-decided, without any community voting or anything to switch their algo back to now ASIC friendly Cryptonight from block 137500.
That will happen in about two days.
What this means to users of SRBMiner/Me ? On previous versions if you mine any coin on 'heavy' algo from monday, the devfee will connect to pool.sumokoin.com using 'heavy' algo,
but the pool will be using classic CN, so shares will be ALL rejected, and i won't be getting the 0.85% fee.

Thank you in advance, if you are going to support me and going to switch to this version.

Switching now. Can i just replace the .exe file in the miner directory?

thank you, yes its enough if you were using one of the newer versions > 1.4.0

heavyarms1912

full member

Activity: 729

Merit: 114

Quote from: doktor83 on June 02, 2018, 12:41:28 PM

V1.5.8
- Fixed a bug in pool switching process
- Fixed a bug in watchdog's "reboot_script"
- Changed default devfee pool for Heavy algo

+ I would like to politely ask everyone if they appreciate my work, to switch their miners to this new version.

The default devfee pool for heavy algo was pool.sumokoin.com, which is under the control of the origin Sumo team.
They self-decided, without any community voting or anything to switch their algo back to now ASIC friendly Cryptonight from block 137500.
That will happen in about two days.
What this means to users of SRBMiner/Me ? On previous versions if you mine any coin on 'heavy' algo from monday, the devfee will connect to pool.sumokoin.com using 'heavy' algo,
but the pool will be using classic CN, so shares will be ALL rejected, and i won't be getting the 0.85% fee.

Thank you in advance, if you are going to support me and going to switch to this version.

Switching now. Can i just replace the .exe file in the miner directory?

doktor83

hero member

Activity: 2548

Merit: 626

V1.5.8
- Fixed a bug in pool switching process
- Fixed a bug in watchdog's "reboot_script"
- Changed default devfee pool for Heavy algo

+ I would like to politely ask everyone if they appreciate my work, to switch their miners to this new version.

The default devfee pool for heavy algo was pool.sumokoin.com, which is under the control of the origin Sumo team.
They self-decided, without any community voting or anything to switch their algo back to now ASIC friendly Cryptonight from block 137500.
That will happen in about two days.
What this means to users of SRBMiner/Me ? On previous versions if you mine any coin on 'heavy' algo from monday, the devfee will connect to pool.sumokoin.com using 'heavy' algo,
but the pool will be using classic CN, so shares will be ALL rejected, and i won't be getting the 0.85% fee.

Thank you in advance, if you are going to support me and going to switch to this version.

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: ALEX_RAA on June 02, 2018, 09:11:34 AM

Quote from: doktor83 on May 29, 2018, 09:27:39 AM

Quote from: ALEX_RAA on May 29, 2018, 09:11:10 AM

v. 1.5.6 still have problem - if some gpus stop hashing the miner not hangs but just stoped and not showing any information further. So if i see that and press some key (space or h for example) it will show that gpu's hash speed is 0 and make reconnect to pool and after it will work good for some time.

sorry but i dont understand,can you turn on logging and share that?

so marked area is when i see that one of rigs do no sending shares more than 2 minutes. Miner just not doing anything after returning to
user mining and than i have to press H or S and see hash speed is 0
it's v 1.5.6

p.s. i have to admit that in v 1.5.6 this situations happens not often

how is that time is jumping :

16:56:39
17:03:33
16:57:40
16:57:17

after that is all good.

Have you turned on logging as i asked?

rig1313

newbie

Activity: 16

Merit: 0

Quote from: ALEX_RAA on June 02, 2018, 09:11:34 AM

Quote from: doktor83 on May 29, 2018, 09:27:39 AM

Quote from: ALEX_RAA on May 29, 2018, 09:11:10 AM

v. 1.5.6 still have problem - if some gpus stop hashing the miner not hangs but just stoped and not showing any information further. So if i see that and press some key (space or h for example) it will show that gpu's hash speed is 0 and make reconnect to pool and after it will work good for some time.

sorry but i dont understand,can you turn on logging and share that?

https://thumb.ibb.co/gwXGTJ/Screenshot_at_02_17_06_45.png

so marked area is when i see that one of rigs do no sending shares more than 2 minutes. Miner just not doing anything after returning to
user mining and than i have to press H or S and see hash speed is 0
it's v 1.5.6

p.s. i have to admit that in v 1.5.6 this situations happens not often

i have this problem too

ALEX_RAA

newbie

Activity: 78

Merit: 0

Quote from: doktor83 on May 29, 2018, 09:27:39 AM

Quote from: ALEX_RAA on May 29, 2018, 09:11:10 AM

v. 1.5.6 still have problem - if some gpus stop hashing the miner not hangs but just stoped and not showing any information further. So if i see that and press some key (space or h for example) it will show that gpu's hash speed is 0 and make reconnect to pool and after it will work good for some time.

sorry but i dont understand,can you turn on logging and share that?

https://thumb.ibb.co/gwXGTJ/Screenshot_at_02_17_06_45.png

so marked area is when i see that one of rigs do no sending shares more than 2 minutes. Miner just not doing anything after returning to
user mining and than i have to press H or S and see hash speed is 0
it's v 1.5.6

p.s. i have to admit that in v 1.5.6 this situations happens not often

MaxMidnite

newbie

Activity: 143

Merit: 0

Quote from: doktor83 on June 01, 2018, 03:16:58 PM

Quote from: MaxMidnite on June 01, 2018, 12:05:00 PM

Quote from: doktor83 on June 01, 2018, 11:55:43 AM

Quote from: MaxMidnite on June 01, 2018, 11:52:33 AM

Using latest version, thank you for stellitev4 support.
HashRate is also very nice, one thing I get alot of
Pool rejected result 0x0001704C (low difficulty share)
Other miners do not show me this message, what it mean?
Anything to worry about?

it means you are using wrong algorithm. What are you trying to mine?

Also where do I add the "Kernel" can you give example as I added:

/* Intensity 0-> auto intensity, or value from 1-300 */
"intensity" : 0,
"kernel" : 4,

Tried each Kernel and made no difference in hash, so thinking put it in wrong place?

Thanks man

Not there, you put it in gpu_conf :

"gpu_conf" :
[
   { "id" : 0, "intensity" : 80, "worksize" : 8, "threads" : 1, "kernel" : 1},
   { "id" : 1, "intensity" : 40, "worksize" : 8, "threads" : 2, "kernel" : 2},
   { "id" : 3, "intensity" : 30, "worksize" : 8, "threads" : 2, "kernel" : 3},
   { "id" : 4, "intensity" : 90, "worksize" : 8, "threads" : 1, "kernel" : 4}
]

What GPU's do you have?

Thanks Man,

The results did not change between kernels maybe little hash change 1-5hash.
Another question if I set,

/* Intensity 0-> auto intensity, or value from 1-300 */
"intensity" : 0,

The confusion is does it take the intensity auto or the gpu_conf values??

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: istr on June 02, 2018, 01:23:49 AM

Also what means compute errors?

This is how it works :

Gpu gets a job to work on and returns results. Those results are then verified on the CPU, and if the CPU gets the same result as GPU did, that is a valid share and is sent to the pool.
If the GPU result isn't the same the result CPU got, that is a compute error, and that share won't be sent to the pool, because its not valid.

Compute errors can happen for a few reasons: bad timings, too much overclock/underclock, too high intensity.

ALEX_RAA

newbie

Activity: 78

Merit: 0

Quote from: doktor83 on June 01, 2018, 04:06:37 PM

Quote from: trifo on June 01, 2018, 03:56:12 PM

No, only 1.5.7 version... Tested...

yes i decided finally to put a virus into it, now is time to steal all your pictures from my documents Wink

aaaaa

hesido

jr. member

Activity: 158

Merit: 5

Quote from: istr on June 02, 2018, 01:23:49 AM

Also what means compute errors?
I've installed a new Gigabyte rx580 8gb card.
I have no memory errors, no hang ups, working fine but only this new card reports 1 or 2 compute errors in stats in a day!

It means there are uncaught memory errors which produced a bad share, which got caught by SRBminer and was not submitted. Some of my microns exhibit memory errors but almost never produce a bad share (but a memory error reported is an error caught and "fixed", the mem errors which don't get caught are the problem), but my Hynix ones never display a mem error in monitoring software yet they produce bad shares once in a while. If bad shares by a specific card is above 0.5% (compared to what it produces on its own), you may reduce mem freq by 10mhz or up the voltage. Just 10mhz may work wonders.

istr

newbie

Activity: 24

Merit: 0

Quote from: doktor83 on May 31, 2018, 01:22:33 AM

Quote from: istr on May 31, 2018, 01:00:33 AM

Quote from: doktor83 on May 30, 2018, 04:39:19 AM

Quote from: istr on May 30, 2018, 04:28:28 AM

Hi Doc!

A strange behavior!
I've noticed that a long time ago but now I've decided to tell you.
It may help you debugging the code.

I've automated startup procedure for the miner whenever windows starts.
Let's take for example one of my rigs with 6 cards.
Windows boots and after a while miner starts.
After some time of stabilization watching memory usage in task manager I see it stable at ~286 - 290 M.
If I kill the miner process and start it again giving it time to stabilize it stays at ~560 - 570 M.
That's why I was saying all the time about "memory management".
I don't know but this is the behavior.
It may help.

Greetings!

ps: in heavy algo.

well if you would follow this thread regulary you would know that this is very well known, and can be fixed by just fireing up GPU-Z Wink

You know something Doc, you didn't understand me.
I'm not talking about the known hashrate drop problem which I first introduced to the community the temporary solution with GPU-Z
but about different seized memory (MB) into 2 different runs of miner which of course may related.
No hard feelings!

No hard feelings, we did not understand eachother.
Also i don't take notes who said/wrote what and when , so i couldn't know you found this nice 'fix'.

Is this behaviour you are referring to happening every time (like first run always less mem used, second run always ok) ?
I see other miners have this 'problem' too on heavy.

Yes, happening all the time.
Miner uses about half the mem every time machine reboots and for every next run about double of that.

Also what means compute errors?
I've installed a new Gigabyte rx580 8gb card.
I have no memory errors, no hang ups, working fine but only this new card reports 1 or 2 compute errors in stats in a day!

dingdongtobias

newbie

Activity: 156

Merit: 0

Really? Some people still so retarded that they have an urge to share with the community if a well known miner was reported as virus?
Thank you for saving us from the evil!

UnclWish

sr. member

Activity: 1484

Merit: 253

Quote from: doktor83 on June 01, 2018, 04:06:37 PM

Quote from: trifo on June 01, 2018, 03:56:12 PM

No, only 1.5.7 version... Tested...

yes i decided finally to put a virus into it, now is time to steal all your pictures from my documents Wink

I don't think you will be glad to see them )))))))

Sgsg666

jr. member

Activity: 113

Merit: 1

Quote from: trifo on June 01, 2018, 04:40:35 PM

Observation and info for you only... Windows Defender delete version 1.5.7 previous versions no...

dude previous versions does gets deleted too if i tried to run miner without windows defender exclusion.

trifo

newbie

Activity: 29

Merit: 0

Observation and info for you only... Windows Defender delete version 1.5.7 previous versions no...

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: trifo on June 01, 2018, 03:56:12 PM

No, only 1.5.7 version... Tested...

yes i decided finally to put a virus into it, now is time to steal all your pictures from my documents Wink

trifo

newbie

Activity: 29

Merit: 0

No, only 1.5.7 version... Tested...

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: trifo on June 01, 2018, 03:42:58 PM

Version 1.5.7 deleted by antivirus...

also version 1.5.6, 1.5.5 and so on

Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching - page 244. (Read 237263 times)