I added your URL to hosts file per your PM directions, it ran for almost 24 hours before finally shutting down.  This is the end of the log file.



So here is your log telling me, "Don't be a dick."

I believe you are correct and it is a “me” problem and not a “you” problem... 😁
Auto intensity for 1.6.4 is 57 and 1.6.7 is 55, but a weird thing happened.  I was running .4 and immediately after quitting and starting .7, without a reboot, they have the almost the same hashrate.

Thanks for your support and work you do!

Same card settings but not sure in miner as I’ve always used auto intensity 0 and never messed with worksize.

I’m assuming it was bundled kernel because on first run, all miner said was loading kernel... didn’t get a compiling kernel message.  SRB 1.6.7 was installed in a completely separate folder than 1.6.4.

on version 1.6.5 there are no problems

How do you conclude that I don't care what you say and what you think?  I said I don't care if you like how I respond or not.   Obviously I care what you say and think or I wouldn't be posting here.  Plus, you are the only one who can fix your closed-source software.  I don't "think you did nothing."  I said that unless what you were doing earlier today is something that you do daily, then it isn't the problem as I experience it daily, randomly, on different rigs and sometimes never on others.

Spread hate?  I don't hate anyone.  I am frustrated with your software.  This isn't raging.

There is no antivirus or URL blockers on my rigs.  All firewalls are given permission for srbminer for each and every new release.  That was your suggestion as to why your miner quits for some of my rigs.  It is not correct.
My language usage is my choice based on my frustration with your software, not what you said.  You don't like it?  I don't care.  And I don't think that what you were doing earlier today has anything to do with the same connection errors to srbminer.com yesterday, the day before that, etc., unless you do it everyday.  Your program is buggy when switching back to the miner from your dev fee miner.  That is easily ascertained and it is frustrating when you have over 30 rigs that just randomly quit without resuming mining.  That software decision is YOUR choice.  I prefer your software, but I have no problem telling you about it's confounding complications either.

This problem has been ongoing since well before the release of 18.6.1 or even 18.3.4 for that matter.  It has nothing to do with drivers and everything to do with dev fee switching.

My language is well justified considering your PM you sent me.  Interesting how you couldn't solve the problem when I alerted you to it months ago.  So what is the solution?

You are wasting your time complaining.  I complained about the same thing months ago.  The dev's conclusion was that I was blocking access to srbminer.com.  He made me feel like he thought I was trying to cheat him.  F#ck that, bullsh!t.  There is an bug in his code.  Simple as that.

Hey Dok, love your miner but wanted to pass this along...

Been mining XTL with 8 card 480/580 rig using amd 18.6.1.  Tried new 1.6.7 version and was getting around 50hs less per card than on 1.6.4.  Might not sound like much, but x 8 cards adds up.  Changed back to older version...

I lost 100HS on CN-Heavy algo with new version on same settings after I alter the intensity letting miner to compile cache.

Intensity 61.3 (letting 1.6.7 to compile for 61.3 )

Vega 64 SRBminer 1.6.5   CN-haven : 1630 HS

Vega 64 SRBminer 1.6.7   CN-haven : 1520 HS

Intensity 61  (not Letting 1.6.7 to compile, default setting 0 )

Vega 64 SRBminer 1.6.5   CN-haven : 1580 HS

Vega 64 SRBminer 1.6.7   CN-haven : 1545 HS


The new cache is not efficient as before.

hi why i can't setting api for monitoring rig
every time I attach a API config to config txt always force close

1.8.8.2 driver

all card use GPU and MEM 900mv
3/vega56(64bios)+1vega64LE - All samsung mem.

all work -v7 and heavy/tube haven
must disable/enable and first start with 60int 1 min and start again with 56 int.

i try v7- stelite - tube- loki - haven - fast(msr)- aloy and arto

all give better HR

TUBE

Heavy-LOKI

FAST-MSR

V7-graft and STL Arto give a little less

Alooy give 4300Hr

Having a hard time configure, before i just open config.txt anfd ez, now its always giving me error, i open config and delert all and leave only config-heavy and error, i pass my config of old srb and tryed other things and always error or starting with cryptonightv7, can i have some help how to put mining at heavy.

{
"pools" :
[
	{"pool" : "loki.miner.rocks:5555", "wallet" : "change-this-to-your-wallet", "password" : "x"}
]
}

What about hashrate for Vega 56 on monero per card !!!

Hi Doktor,

Accoding to you recomendation I changed drivers to Adr.18.6.1(prev. was blockchain)
and faced with hash rate double decreased.
Iw was ~1900h/s on old drivers, but now it ~830h/s for rx570-4 on CN fast.
Compute mode enabled(SRBMiner-CN.exe --setcomputemode).

Please, help. Ireaaly dont want to return to blockchain drv.

Isn't there a Monero fork in the works supposed to go live very soon?
Cryptonight v2?
I thought XMR was supposed to fork on 1st September... Maybe I got that wrong.

Have you got a new miner version ready in any case?

EDIT: I found it. September 16th. There's some time left.

Doktor,

With v1.6.6 on 2 rigs, 2 x Vega56 and 4 x Vega64, and reboot script updated in the config file.

The Vega64 rig is stable mining XMR and has not triggered the reboot file since Aug 28.

The Vega56 rig however, reboots every half hour like clockwork.

I am tempted to revert to v1.6.5 but if you can figure out whats wrong - I will avoid the downtime.

How many performance increase have you found?
Maybe try it later when I am back home

Which driver do you use?