Author

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

newbie
Activity: 36
Merit: 0
It seems there's an issue with Haven Algorithm and V1.6.1

The miner crashes.

Tested on 2 rigs, same problem

No issue with V1.6.0
Same problem here.
1.6.0 works on Haven, 1.6.1 not.

windows version, driver version, config file and log would be more helpful.

Windows 10 Pro (1709)
AMD Drivers 18.3.4

Config :

{
/* Type can be : normal, normalv7, lite, litev7, heavy, ipbc  */
"cryptonight_type" : "haven",

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

/* To use 2 threads per card set double_threads to true  */
"double_threads" : true,
}

Log :

[2018-07-01 20:54:27] Miner version: 1.6.1
[2018-07-01 20:54:28] AMD Platform ID: 0
[2018-07-01 20:54:28] AMD platform FOUND
[2018-07-01 20:54:28] Found 6 AMD devices
[2018-07-01 20:54:28] GPU0: Radeon RX 580 Series [Ellesmere] [8192 MB][Intensity 51.0][W: 8][T: 2][K: 1][BUS: 3]
[2018-07-01 20:54:28] GPU1: Radeon RX 580 Series [Ellesmere] [8192 MB][Intensity 51.0][W: 8][T: 2][K: 1][BUS: 5]
[2018-07-01 20:54:28] GPU2: Radeon RX 580 Series [Ellesmere] [8192 MB][Intensity 51.0][W: 8][T: 2][K: 1][BUS: 1]
[2018-07-01 20:54:28] GPU3: Radeon RX 580 Series [Ellesmere] [8192 MB][Intensity 51.0][W: 8][T: 2][K: 1][BUS: 2]
[2018-07-01 20:54:28] GPU4: Radeon RX 580 Series [Ellesmere] [8192 MB][Intensity 51.0][W: 8][T: 2][K: 1][BUS: 6]
[2018-07-01 20:54:28] GPU5: Radeon RX 580 Series [Ellesmere] [8192 MB][Intensity 51.0][W: 8][T: 2][K: 1][BUS: 4]
[2018-07-01 20:54:28] ADL is enabled
[2018-07-01 20:54:28] Cryptonight Haven mode enabled
[2018-07-01 20:54:28] DevFee pools loaded
[2018-07-01 20:54:28] DevFee pool SET
[2018-07-01 20:54:28] DevFee address SET
[2018-07-01 20:54:28] Starting init of mining threads
[2018-07-01 20:54:28] Compiling kernel for DEVICE BUS ID 3 ...
[2018-07-01 20:54:46] Loading kernel for DEVICE BUS ID 3 ...
[2018-07-01 20:54:47] Loading kernel for DEVICE BUS ID 5 ...
[2018-07-01 20:54:48] Loading kernel for DEVICE BUS ID 5 ...
[2018-07-01 20:54:50] Loading kernel for DEVICE BUS ID 1 ...
[2018-07-01 20:54:51] Loading kernel for DEVICE BUS ID 1 ...
[2018-07-01 20:54:52] Loading kernel for DEVICE BUS ID 2 ...
[2018-07-01 20:54:53] Loading kernel for DEVICE BUS ID 2 ...
[2018-07-01 20:54:55] Loading kernel for DEVICE BUS ID 6 ...
[2018-07-01 20:54:56] Loading kernel for DEVICE BUS ID 6 ...
[2018-07-01 20:54:57] Loading kernel for DEVICE BUS ID 4 ...
[2018-07-01 20:54:58] Loading kernel for DEVICE BUS ID 4 ...
[2018-07-01 20:54:59] ADL initialised successfully!
[2018-07-01 20:54:59] Finished init of mining threads
[2018-07-01 20:54:59] Main pool: haven.miner.rocks:4005
[2018-07-01 20:54:59] Gpu watchdog started
[2018-07-01 20:54:59] API disabled
[2018-07-01 20:54:59] json_send: {"method":"login","params":{"login":"hvi1aCqoAZF19J8pijvqnrUkeAeP8Rvr4XyfDMGJcarhbL15KgYKM1hN7kiHMu3fer5k8JJ8YRLKCah DKFgLFgJMYAfnJHXgHSJ5DKiNBvfPa.150000","pass":"w=ROGUE1","agent":"SRBMiner Cryptonight AMD GPU miner/1.6.1","rigid":""},"id":1}
[2018-07-01 20:54:59] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"id":"852671046905748","job":{"blob":"0303e0c6e4d905a32e31781e4376180d21c487d484c9050d142e92873de727e342319454c658e70 000000091040058cfa39eb12f19ee8b41815fef19d51d991149d237adcd55c50b6b85e106","job_id":"236919075889465","target":"d96f0000"},"status":"OK"}}
[2018-07-01 20:54:59] Connected to haven.miner.rocks:4005
[2018-07-01 20:55:00] sock_ready: User logged in
[2018-07-01 20:55:00] pool_have_job: Pool sent a new job (ID: 236919075889465)
[2018-07-01 20:55:11] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0303e0c6e4d905a32e31781e4376180d21c487d484c9050d142e92873de727e342319454c658e70 0000000d67680d5be05fa737cdc2d13ae3919bcb835d948037987bf788ce1f6b944f58206","job_id":"937923625437735","target":"d96f0000"}}
[2018-07-01 20:55:11] pool_have_job: Pool sent a new job (ID: 937923625437735)


Then the miner crashes
sr. member
Activity: 661
Merit: 250
How can we test this with testnet pool ?
My 1.6.1 doesn't seems recognize "cryptonight_type" : "bittubev2",

{
/* Type can be : normal, normalv7, lite, litev7, heavy, ipbc, artocash, alloy, marketcash, b2n  */
"cryptonight_type" : "bittubev2",
"intensity" : 0,
"double_threads" : true
}

Miner says :
cryptonight_type can be : [normal, normalv7, lite, litev7, heavy, ipbc, artocash, alloy]

That is not 1.6.1. Download 1.6.1 from here : http://www.srbminer.com/downloads/SRBMiner-CN-V1-6-1.zip


When using an unkown algo, this is what you get on 1.6.1 :
cryptonight_type can be : [normal, normalv7, lite, litev7, heavy, bittubev2, artocash, alloy, marketcash, b2n, stellitev4, haven, fast]
You right, my bad. My .bat doesn't use the good directory Sad
hero member
Activity: 2548
Merit: 626
How can we test this with testnet pool ?
My 1.6.1 doesn't seems recognize "cryptonight_type" : "bittubev2",

{
/* Type can be : normal, normalv7, lite, litev7, heavy, ipbc, artocash, alloy, marketcash, b2n  */
"cryptonight_type" : "bittubev2",
"intensity" : 0,
"double_threads" : true
}

Miner says :
cryptonight_type can be : [normal, normalv7, lite, litev7, heavy, ipbc, artocash, alloy]

That is not 1.6.1. Download 1.6.1 from here : http://www.srbminer.com/downloads/SRBMiner-CN-V1-6-1.zip


When using an unkown algo, this is what you get on 1.6.1 :
cryptonight_type can be : [normal, normalv7, lite, litev7, heavy, bittubev2, artocash, alloy, marketcash, b2n, stellitev4, haven, fast]
sr. member
Activity: 661
Merit: 250
BITTUBE FORK INCOMING (block 110.000)

Get ready (v1.6.1) :

Example for Vega cards

config.txt :

{
"cryptonight_type" : "bittubev2",
"intensity" : 56,
"double_threads" : true
}

pools.txt :

{
"pools" :
[
   {"pool" : "mining.bit.tube:15555",
    "wallet" : "your-wallet",
    "password" : "x"
    }
]
}

How can we test this with testnet pool ?
My 1.6.1 doesn't seems recognize "cryptonight_type" : "bittubev2",

{
/* Type can be : normal, normalv7, lite, litev7, heavy, ipbc, artocash, alloy, marketcash, b2n  */
"cryptonight_type" : "bittubev2",
"intensity" : 0,
"double_threads" : true
}

Miner says :
cryptonight_type can be : [normal, normalv7, lite, litev7, heavy, ipbc, artocash, alloy]
hero member
Activity: 2548
Merit: 626
It seems there's an issue with Haven Algorithm and V1.6.1

The miner crashes.

Tested on 2 rigs, same problem

No issue with V1.6.0
Same problem here.
1.6.0 works on Haven, 1.6.1 not.

windows version, driver version, config file and log would be more helpful.
sr. member
Activity: 661
Merit: 250
It seems there's an issue with Haven Algorithm and V1.6.1

The miner crashes.

Tested on 2 rigs, same problem

No issue with V1.6.0
Same problem here.
1.6.0 works on Haven, 1.6.1 not.
newbie
Activity: 36
Merit: 0
It seems there's an issue with Haven Algorithm and V1.6.1

The miner crashes.

Tested on 2 rigs, same problem

No issue with V1.6.0
hero member
Activity: 2548
Merit: 626
BITTUBE FORK INCOMING (block 110.000)

Get ready (v1.6.1) :

Example for Vega cards

config.txt :

{
"cryptonight_type" : "bittubev2",
"intensity" : 56,
"double_threads" : true
}

pools.txt :

{
"pools" :
[
   {"pool" : "mining.bit.tube:15555",
    "wallet" : "your-wallet",
    "password" : "x"
    }
]
}
hero member
Activity: 2548
Merit: 626
guys, help me to configurate SRB 1.6.1. for StelliteV4
I always have crushes miner

config.txt :

{
"cryptonight_type" : "stellitev4",
"intensity" : 0,
"double_threads" : true
}

pools.txt :

{
"pools" :
[
   {
   "pool" : "communitypool.stellite.cash:6688",
    "wallet" : "your-wallet",
    "password" : "x"
    }
]
}
hero member
Activity: 2548
Merit: 626
Doctor, maybe you add in statistics effective speed (accepted by pool)? To prevent questions about differenece between miner speed and pools speed.

Those questions can never be prevented, no matter what i do to the miner.
All i can say is that the miner is not showing fake or higher values just to make the miner happy.
I am sure everyone knows what is the best for him, and if it's switching to another mining software, i am ok with that, i can't force anyone to use SRBMiner Smiley

sr. member
Activity: 1484
Merit: 253
Doctor, maybe you add in statistics effective speed (accepted by pool)? To prevent questions about differenece between miner speed and pools speed.
jr. member
Activity: 158
Merit: 5
newbie
Activity: 30
Merit: 0
guys, help me to configurate SRB 1.6.1. for StelliteV4
I always have crushes miner
jr. member
Activity: 238
Merit: 3
what are your fine tune values?
if you increase the intensity too much then your hashrate might fluctuate a lot and the miner will become slower overall, despite showing higher hashrates.
full member
Activity: 504
Merit: 122
My 8x RX470/570 rig is showing 7400h/s hash rate, but unfortunately, i guess that SRBMiner is not showing the right value, because i mined for 24h and the pool show about 6700h/s.
I tested 3x different pools and coins, looks like my fine tune with intensity doesn't work in the real world, only show increased numbers at the miner.
newbie
Activity: 3
Merit: 0
Dok, do you know why rig with 13 GPU (RX570) gets stuck on "loading kernel" all the time?

I need to restart the rig 3 or 5 times (sometimes even more) until I can finally load all kernels...
newbie
Activity: 61
Merit: 0

Still same situation unfortunately

start with  --adldisable
with series R9 2xx,3xx it helps

Thanks for the suggestion, unfortunately no improvement.

sorry i have no idea, i tried on win7 and win10 machines and it's working ok.

Ok no worries, only seems to happen with Stellite algo for now, I will try to investigate more during the weekend.

Tried some more algos and seems to be the same issue for Haven also. The miner crashes when starting to send result back to pool. Also tried my r9 290s and r9 380s separately and they both crash with these algos. No problems with regular v7 or heavy.

Can anyone with these cards try if their miner also crashes when mining stellite or haven?
newbie
Activity: 301
Merit: 0
hi guys is normal to windows defender detect srbminer.exe like:

Trojan:Win32/Occamy.C

I was mining for 2 weeks but today had detected and kill the .exe   Smiley

Thanks

Yes. Happened to every single miner I've ever used. Someone with a trojan will package the miner in it and mine for them on the infected PC.

I just have a wallets folder that I white list.

I thought was an false positive!!

Dont understand your sentence :" Someone with a trojan will package the miner in it and mine for them on the infected PC"

I just add an exclution to windows defender,

Hello guys, I see this is a very good miner. However, come to my attention this post, what does the community says about this. Can we trust in this miner if it is download from the officials sites??

Thanks for answer

im waiting too
jr. member
Activity: 158
Merit: 5


I have been developing this after forking from sebseb's work, added pushbullet notifications / dropdown for easy worker selection / market value (tradeogre only, so far, altex will come next) / coin switching for same algo coins.

The advantage of using this coin switch, even manually, is that there's no hashrate drop between pools/coins.

Currently the auto coin switching is dumb, is based on market value, but you'll be able to fine tune the selection process by using your speculative expectations: I'll be adding "Ignore market value above" "Ignore market value below" and "Override market value" options in GUI for easy and dynamic setup so you can mine based on difficulty of coin without being affected by fluctuating markets.

Give it a go from https://github.com/hesido/cryptonote-switching-relay-proxy

Planned features:
  • Fine tune auto-switch logic
  • Wait for round end before switch (to not lose shares in longer rounds in pplns, and ethical mining for PPS :=) )
  • Aggregate notifications

Fantasy feature:
If SRB miner supports coin switching by XMR-Proxy standards, do different algo coin switching.

It would be a nice "selling" point for SRB miner, wouldn't it Wink

Notes:
The proxy is tested to work with XMR-Stak, and should be able to work with other miners too.

In your miner, you just point to localhost or the ip that you host the proxy but in case of bugs or connection errors, make sure you define backup pools in your miner also Smiley)

Use at your own risk, monitor the software often, this is Work In Progess software.



newbie
Activity: 156
Merit: 0
Although the srbminer was working usper stable with my Vega rigs and gave me amazing nominal hashrate, my adventure with srbminer comes to the end

After a lot of monitoring I figured out that srbminer and cast.xmr give me much less real hashrate than the miner hashrate. I have tried several pools and difference goes as much as 20%. I don't know why, one of the rigs is correct (12KH/s reported by miner and pool) and others vary from 11.5 to even 10KH/s real hashrate. I have 0 invalid shares, everything works beautiful, but my hashes are missing.

Although XMR STAK gives me less hashrate, it is spot on with what the pool reports. I have read few pages ago that older versions of srbminer do not have this issue, but I can't find them online anymore.

After long time, back to where I started, hello XMR STAK, sorry doc, your miner is awesome but difference is too high for me.

I took the time and tested latest STAK 2.4.5, to see is hashrate on pool = hashrate in miner like you say.


https://i.imgur.com/oo57Vi3.jpg


As you can see on the image, STAK running for more than 6 hours.
Miner shows 1775hs as average for 15m.
Pool shows 1674hs as average for 6 hours.

If my math is correct : 1775 - 1674 = 101 hs difference.
If i had 6 vegas that is : 6 * 101hs = 606 hs dissapeared somewhere.

Look at the graph, that is what is called luck.
Sometimes 50 found shares, then only 6.

What i want to show you with this is that you can never have the same hashrate ALL THE TIME in your miner as on your pool.
Sometimes it will be less, sometimes more, and that is totally normal.

Jump to: