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

[dingdongtobias]

Guys,

first, thanks to all that didn't care and made fun of me when I reported missing hashrate problem. I tried hard to explain that the cast-xmr and srbminer report incorrect or inconsistent hashrate, for example my vega rigs are hashing up to 20% less on the pool than what the miner reports, just to be stomped by armada of forumeers who try to teach me basic math, finally, I was advised to find another miner if I don't like this one - and I did

last few days I tried new  miner called JCE, the guy just made a beta version for GPUs, and my Vegas not only hash better than SRBminer (7xVega 56 14350) but every single hash is counted by the pool properly. This leads me to conclusion that srb and cast have issues with counting or are reporting false hashrate. I will now support new guy and his miner.

If doktor83 ever cares to fix this problem, I will be happy to provide support and more details.

Have fun and enjoy your mining

I am glad you finally found something that is working for you.
But please, next time don't come back just to advertise another miner.

[1642506048]

1642506048

[1642506048]

1642506048

[1642506048]

1642506048

[1642506048]

1642506048

[doktor83]

V1.6.2
- Added support for Italocoin new algo (from block 55.000)
- Auto intensity for Vega cards improved, also managed to increase hashing speed on Vega cards for about ~1-1.5% (mainly on heavy algos)
- If user uses non existing GPU id in gpu_conf, it will be ignored, no error will be thrown
- Fixed miner crash when using a non AES capable CPU on some algos
- Added Windows version and build in log
- Added video driver version in log
- Added info about CPU AES support in log
- Statistics now shows number of stale shares that were accepted by pool
- Added parameter 'min_rig_speed_duration' that can set period for 'min_rig_speed' parameter (minimum is 30 sec), default is 5 min

+ I finally bought a Vega 56 card, so in the next releases i will try to improve the performance for Vegas. For now a little speedup of about 1-1.5% is achieved, mainly on Heavy based algos (Heavy, Haven, Bittube, Italo)

+ If you use a non existant id in gpu_conf, it will now be ignored, only id's that exist in your system will be used

+ There was a bug in soft AES that caused miner crash on Stellite and Haven algos, this is now fixed

+ Added accepted stale shares number in statistics. It can't know the number of real accepted stale shares on pool side, but the logic is simple, if a new job is received, but the miner sends a result in the mean time that is for the previous job, and this share gets accepted by the pool, miner will treat this like an accepted stale share.

+ min_rig_speed_duration can set the time you want to check the average hashrate for 'min_rig_speed' parameter. Default is 5 min.

[RuMiner]

+ I finally bought a Vega 56 card, so in the next releases i will try to improve the performance for Vegas.

have you made the best Vega miner without any Vega card? WOW, that's a master skill

Thanks for next release. It would be nice to get email on further updates ;-)

[abg00]

V1.6.2

- Fixed miner crash when using a non AES capable CPU on some algos

- Added info about CPU AES support in log

have aes kernel error on rx550 card 2gb

[RuMiner]

upd hashrate lowered since 1.6.1 on Vegas 56 about 20 h/s per card

[dragonmike]

Guys,

first, thanks to all that didn't care and made fun of me when I reported missing hashrate problem. I tried hard to explain that the cast-xmr and srbminer report incorrect or inconsistent hashrate, for example my vega rigs are hashing up to 20% less on the pool than what the miner reports, just to be stomped by armada of forumeers who try to teach me basic math, finally, I was advised to find another miner if I don't like this one - and I did

last few days I tried new  miner called JCE, the guy just made a beta version for GPUs, and my Vegas not only hash better than SRBminer (7xVega 56 14350) but every single hash is counted by the pool properly. This leads me to conclusion that srb and cast have issues with counting or are reporting false hashrate. I will now support new guy and his miner.

If doktor83 ever cares to fix this problem, I will be happy to provide support and more details.

Have fun and enjoy your mining

I am glad you finally found something that is working for you.
But please, next time don't come back just to advertise another miner.

It's a very very pertinent and valid observation however.
Especially since JCE is claiming a lot of devs "cheat" with their closed-source miners. If his miner's hashrate coincides with what the pools report - and SRB, Cast etc do not - there is a problem, isn't there?

[doktor83]

V1.6.2

- Fixed miner crash when using a non AES capable CPU on some algos

- Added info about CPU AES support in log

have aes kernel error on rx550 card 2gb

don't copy this version over older ones, or if you do, delete .srb files.

[doktor83]

Guys,

first, thanks to all that didn't care and made fun of me when I reported missing hashrate problem. I tried hard to explain that the cast-xmr and srbminer report incorrect or inconsistent hashrate, for example my vega rigs are hashing up to 20% less on the pool than what the miner reports, just to be stomped by armada of forumeers who try to teach me basic math, finally, I was advised to find another miner if I don't like this one - and I did

last few days I tried new  miner called JCE, the guy just made a beta version for GPUs, and my Vegas not only hash better than SRBminer (7xVega 56 14350) but every single hash is counted by the pool properly. This leads me to conclusion that srb and cast have issues with counting or are reporting false hashrate. I will now support new guy and his miner.

If doktor83 ever cares to fix this problem, I will be happy to provide support and more details.

Have fun and enjoy your mining

I am glad you finally found something that is working for you.
But please, next time don't come back just to advertise another miner.

It's a very very pertinent and valid observation however.
Especially since JCE is claiming a lot of devs "cheat" with their closed-source miners. If his miner's hashrate coincides with what the pools report - and SRB, Cast etc do not - there is a problem, isn't there?

Someone who works on a closed source miner says that closed source miners cheat and steal, ironic
As always, i say : nobody forces you to use SRBMiner, if you think something is not ok, don't use it

[doktor83]

upd hashrate lowered since 1.6.1 on Vegas 56 about 20 h/s per card

It shouldn't be . Algo and settings?

[dragonmike]

Guys,

first, thanks to all that didn't care and made fun of me when I reported missing hashrate problem. I tried hard to explain that the cast-xmr and srbminer report incorrect or inconsistent hashrate, for example my vega rigs are hashing up to 20% less on the pool than what the miner reports, just to be stomped by armada of forumeers who try to teach me basic math, finally, I was advised to find another miner if I don't like this one - and I did

last few days I tried new  miner called JCE, the guy just made a beta version for GPUs, and my Vegas not only hash better than SRBminer (7xVega 56 14350) but every single hash is counted by the pool properly. This leads me to conclusion that srb and cast have issues with counting or are reporting false hashrate. I will now support new guy and his miner.

If doktor83 ever cares to fix this problem, I will be happy to provide support and more details.

Have fun and enjoy your mining

I am glad you finally found something that is working for you.
But please, next time don't come back just to advertise another miner.

It's a very very pertinent and valid observation however.
Especially since JCE is claiming a lot of devs "cheat" with their closed-source miners. If his miner's hashrate coincides with what the pools report - and SRB, Cast etc do not - there is a problem, isn't there?

Someone who works on a closed source miner says that closed source miners cheat and steal, ironic
As always, i say : nobody forces you to use SRBMiner, if you think something is not ok, don't use it

That's not really a satisfying answer however!... And completely avoids the point.
Do you have a logical explanation for the behaviour? Why would hashrate produced by your miner reported by the pool be noticeably lower than JCE's?

[RuMiner]

upd hashrate lowered since 1.6.1 on Vegas 56 about 20 h/s per card

It shouldn't be . Algo and settings?

normalv7, intensity 112.
rig Vega56x4, was 7900 -> 7820
rig Vega56x8, was 15540 -> 15250
auto intensity got 119, last rig lowered to 15150

[doktor83]

Guys,

first, thanks to all that didn't care and made fun of me when I reported missing hashrate problem. I tried hard to explain that the cast-xmr and srbminer report incorrect or inconsistent hashrate, for example my vega rigs are hashing up to 20% less on the pool than what the miner reports, just to be stomped by armada of forumeers who try to teach me basic math, finally, I was advised to find another miner if I don't like this one - and I did

last few days I tried new  miner called JCE, the guy just made a beta version for GPUs, and my Vegas not only hash better than SRBminer (7xVega 56 14350) but every single hash is counted by the pool properly. This leads me to conclusion that srb and cast have issues with counting or are reporting false hashrate. I will now support new guy and his miner.

If doktor83 ever cares to fix this problem, I will be happy to provide support and more details.

Have fun and enjoy your mining

I am glad you finally found something that is working for you.
But please, next time don't come back just to advertise another miner.

It's a very very pertinent and valid observation however.
Especially since JCE is claiming a lot of devs "cheat" with their closed-source miners. If his miner's hashrate coincides with what the pools report - and SRB, Cast etc do not - there is a problem, isn't there?

Someone who works on a closed source miner says that closed source miners cheat and steal, ironic
As always, i say : nobody forces you to use SRBMiner, if you think something is not ok, don't use it

That's not really a satisfying answer however!... And completely avoids the point.
Do you have a logical explanation for the behaviour? Why would hashrate produced by your miner reported by the pool be noticeably lower than JCE's?

because all miners steal and his is the only one not doing that is the answer you want to hear.

i am really tired of discussions of this type, so i am out.

[doktor83]

upd hashrate lowered since 1.6.1 on Vegas 56 about 20 h/s per card

It shouldn't be . Algo and settings?

normalv7, intensity 112.
rig Vega56x4, was 7900 -> 7820
rig Vega56x8, was 15540 -> 15250
auto intensity got 119, last rig lowered to 15150

set it to intensity 120 by hand,or try 121 and set persistent memory to true, maybe this will give a little boost

worksize 8, threads 2

[dragonmike]

Guys,

first, thanks to all that didn't care and made fun of me when I reported missing hashrate problem. I tried hard to explain that the cast-xmr and srbminer report incorrect or inconsistent hashrate, for example my vega rigs are hashing up to 20% less on the pool than what the miner reports, just to be stomped by armada of forumeers who try to teach me basic math, finally, I was advised to find another miner if I don't like this one - and I did

last few days I tried new  miner called JCE, the guy just made a beta version for GPUs, and my Vegas not only hash better than SRBminer (7xVega 56 14350) but every single hash is counted by the pool properly. This leads me to conclusion that srb and cast have issues with counting or are reporting false hashrate. I will now support new guy and his miner.

If doktor83 ever cares to fix this problem, I will be happy to provide support and more details.

Have fun and enjoy your mining

I am glad you finally found something that is working for you.
But please, next time don't come back just to advertise another miner.

It's a very very pertinent and valid observation however.
Especially since JCE is claiming a lot of devs "cheat" with their closed-source miners. If his miner's hashrate coincides with what the pools report - and SRB, Cast etc do not - there is a problem, isn't there?

Someone who works on a closed source miner says that closed source miners cheat and steal, ironic
As always, i say : nobody forces you to use SRBMiner, if you think something is not ok, don't use it

That's not really a satisfying answer however!... And completely avoids the point.
Do you have a logical explanation for the behaviour? Why would hashrate produced by your miner reported by the pool be noticeably lower than JCE's?

because all miners steal and his is the only one not doing that is the answer you want to hear.

i am really tired of discussions of this type, so i am out.

Wrong, it's the answer I DON'T want to hear.
But so far I have not got any acceptable answer. Whether you're tired of discussions of this type (which haven't featured hardly at all in this thread until now by the way, and I've been contributing in it from day 1 - so a bit quick to be tired about them I would think) or not. Provide a logical explanation/theory. If not, all props to you. But don't blame people for calling it out.

[livada]

upd hashrate lowered since 1.6.1 on Vegas 56 about 20 h/s per card

It shouldn't be . Algo and settings?

normalv7, intensity 112.
rig Vega56x4, was 7900 -> 7820
rig Vega56x8, was 15540 -> 15250
auto intensity got 119, last rig lowered to 15150

vega 56 have best HR with 112/16 v7 and 56/8 heavy. i have colorpower(samsung) and saphire nitro(hynix) this is bes setup for vega 56 card
vega 64  wont 120/8 v7 and 60/8 heavy.

HR is identical or better on 1.6.2 version.

veg56/64bios samsung - 2000+HR
veg56/stock hynix - 1850-1900HR
https://image.prntscr.com/image/S7hq0o12RGq5Rk5Z3Y8qmQ.jpg

[vmozara]

I never called anybody a cheater, I just wanted to point out there is an issue, issue that your clients cost money, and you don't care to provide a simple elaboration or just ask if I could provide more details.

Therefore, it is not you who are out, it is me who is out from your broken/cheating miner, but I will not be out of this topic - every time somebody asks about missing hashrate I will not allow forum trolls to stomp on the guy, instead I will try to explain what happens and how to calculate the hashrate and see himself if srbminer is good for him or not.

[RuMiner]

livada do you have Vega64 firmware on your Vega56? My 56's don't overclock mem over 970 MHz on stock bios. That is the difference obviously. Vega64 didn't change hashrate, too.

[livada]

Guys,

first, thanks to all that didn't care and made fun of me when I reported missing hashrate problem. I tried hard to explain that the cast-xmr and srbminer report incorrect or inconsistent hashrate, for example my vega rigs are hashing up to 20% less on the pool than what the miner reports, just to be stomped by armada of forumeers who try to teach me basic math, finally, I was advised to find another miner if I don't like this one - and I did

last few days I tried new  miner called JCE, the guy just made a beta version for GPUs, and my Vegas not only hash better than SRBminer (7xVega 56 14350) but every single hash is counted by the pool properly. This leads me to conclusion that srb and cast have issues with counting or are reporting false hashrate. I will now support new guy and his miner.

If doktor83 ever cares to fix this problem, I will be happy to provide support and more details.

Have fun and enjoy your mining

I am glad you finally found something that is working for you.
But please, next time don't come back just to advertise another miner.

It's a very very pertinent and valid observation however.
Especially since JCE is claiming a lot of devs "cheat" with their closed-source miners. If his miner's hashrate coincides with what the pools report - and SRB, Cast etc do not - there is a problem, isn't there?

Someone who works on a closed source miner says that closed source miners cheat and steal, ironic
As always, i say : nobody forces you to use SRBMiner, if you think something is not ok, don't use it

That's not really a satisfying answer however!... And completely avoids the point.
Do you have a logical explanation for the behaviour? Why would hashrate produced by your miner reported by the pool be noticeably lower than JCE's?

because all miners steal and his is the only one not doing that is the answer you want to hear.

i am really tired of discussions of this type, so i am out.

Wrong, it's the answer I DON'T want to hear.
But so far I have not got any acceptable answer. Whether you're tired of discussions of this type (which haven't featured hardly at all in this thread until now by the way, and I've been contributing in it from day 1 - so a bit quick to be tired about them I would think) or not. Provide a logical explanation/theory. If not, all props to you. But don't blame people for calling it out.

i dont wont read your mesage  but i read. go ask your POOL DEV why you cheat . I post before 5-7 day my situation. Miner work OK. You say not work ok. Go use other miner and this is it. Chg your pool. i use  nano and rock and  miner HR is identical  for nano or rock HR. you say not. ok i not trust you you not trust me and ok .go use other miner i use this and all happy.

[livada]

livada do you have Vega64 firmware on your Vega56? My 56's don't overclock mem over 970 MHz on stock bios. That is the difference obviously. Vega64 didn't change hashrate, too.

samsung  have 64bios - 1100mem/905mv - 3vega from wall -530-540W v7algo - 520W heavy algo
hynix have stock bios - 900-990mem /940mv - 6vega nitro 1030-1040W v7 algo - 1020W heavy algo

u must use softpowertable for this.

this is hynix nitro+ with 64bios but reset every 10- 15 hour -stock is beter option
https://image.prntscr.com/image/JNQz5ihgSzaCs0Dk5H9dYQ.jpg

and this is identical miner but all card have stock bios- nitro+ hynix

https://image.prntscr.com/image/gi8kK6N2S6WKIjl6rH4g1A.jpg

[abg00]

V1.6.2

- Fixed miner crash when using a non AES capable CPU on some algos

- Added info about CPU AES support in log

have aes kernel error on rx550 card 2gb

don't copy this version over older ones, or if you do, delete .srb files.

work but rate poor and need set lower intensity
was 5170 from 12 rx550\2gb in 1.4.3 Intensity 27
now 4870 in 1.6.2 Intensity 26

algo normalv7