Author

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

member
Activity: 363
Merit: 16
My vega win 10 1803 rigs don´t do this. However, I downloaded 1.5.8. 14 hours ago, run the miner and it was running ever since.
I took a look inside 1.5.7 folder but only on one of the rigs I found 2 files. So I guess it is not miner related, more some issue with driver or setup..

Anyway, I am using this miner since 1.5.7 version. 1.5.8. has even better hashrate. Working very stable. I dumped xmr stak that was working fine for me and the hashrate difference is incredible.

Doktor83, I assume you are Serbian, right? Smiley Pozdrav iz HR
Please, can you try to explain this.
XMR stak on supportxmr pool shows exactly the same 24 hour hashrate both the pool and software, yet the CAST and SRB show mush bigger miner hashrate, but supportxmr hashrate reports almost 20% less. (I counted and calculated hashrate)

I tried some other pool and hashrate was reported correctly. What could be the cause of this? The miner and the pool both report all good shares

Attention Vega owners
SRBMINER 1.5.8 + Adrenalin 18.5.2 rig vega64x6 = 12200H/s, rig vega56x6=12000h/s
this with power tables from vega mining guide and 1408/800 and 1100/800
awesome!

1408 and 1100 with only 800??? which power play tables?!?!
everything under 875v and all miners crash instant
jr. member
Activity: 158
Merit: 5
Doktor, a temporary fix would be to allow gpu config to point to SRB files (Only for power users...) so users can tell SRBMiner to use specific file per gpu. (Same if all cards are identical, of course)
member
Activity: 190
Merit: 59
My vega win 10 1803 rigs don´t do this. However, I downloaded 1.5.8. 14 hours ago, run the miner and it was running ever since.
I took a look inside 1.5.7 folder but only on one of the rigs I found 2 files. So I guess it is not miner related, more some issue with driver or setup..

Anyway, I am using this miner since 1.5.7 version. 1.5.8. has even better hashrate. Working very stable. I dumped xmr stak that was working fine for me and the hashrate difference is incredible.

Doktor83, I assume you are Serbian, right? Smiley Pozdrav iz HR
Please, can you try to explain this.
XMR stak on supportxmr pool shows exactly the same 24 hour hashrate both the pool and software, yet the CAST and SRB show mush bigger miner hashrate, but supportxmr hashrate reports almost 20% less. (I counted and calculated hashrate)

I tried some other pool and hashrate was reported correctly. What could be the cause of this? The miner and the pool both report all good shares

Attention Vega owners
SRBMINER 1.5.8 + Adrenalin 18.5.2 rig vega64x6 = 12200H/s, rig vega56x6=12000h/s
this with power tables from vega mining guide and 1408/800 and 1100/800
awesome!
newbie
Activity: 16
Merit: 0
Everyone with this problem uses 18.5.1 drivers ?
I use dag fix beta drivers, and have same issue...

Only with V1.5.8 ?
1.5.6
1.5.7
1.5.8 - not tested yet
sr. member
Activity: 1484
Merit: 253
Everyone with this problem uses 18.5.1 drivers ?
I use dag fix beta drivers, and have same issue...

Only with V1.5.8 ?
I have this issue with 18.5.1 and 18.5.2 on 1.5.7 and 1.5.8 versions. Windows 10 1803 x64. And wrong names of cards. 1st 2 RX 580 cards detects as R9 200 series. I have 3rd card r9 270X.
newbie
Activity: 417
Merit: 0
Everyone with this problem uses 18.5.1 drivers ?

i have Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23 driver

PS. Misli mda si prije koristio samo prva cetri slova za kompilaciju i on je prepoznao to a sad koristi  10 slova pa stalno radi nanovo compiliranje.

687f. prije
687f********** - 1.5.8 verzija

mozda i grijesim Smiley
hero member
Activity: 2548
Merit: 626
Everyone with this problem uses 18.5.1 drivers ?
I use dag fix beta drivers, and have same issue...

Only with V1.5.8 ?
newbie
Activity: 16
Merit: 0
Everyone with this problem uses 18.5.1 drivers ?
I use dag fix beta drivers, and have same issue...
hero member
Activity: 2548
Merit: 626
Everyone with this problem uses 18.5.1 drivers ?
newbie
Activity: 417
Merit: 0
Hi Dok
V1.5.8 on startup, it generates the .srb file again
This is normal?


It should be generated once for every different gpu, after that on miner start that file should be read, not created again.

But generate non stop- every start miner crate  new .srb ..
in 10 hour i have 40 .srb file and use 100MB for disk space. This is not normal.
you must fix this.

https://image.prntscr.com/image/zO_QGLM2QZulfBv-qTp5wA.jpg

before u have 1 file : 687f.   without extension and this is it. now you co,mpile  every time when start .before you compile only 1 time for 1 algo.
sr. member
Activity: 1484
Merit: 253
Hi Dok
V1.5.8 on startup, it generates the .srb file again
This is normal?


It should be generated once for every different gpu, after that on miner start that file should be read, not created again.

Hi Doktor, I think this could be better communicated by the program. It *always* says "compiling" although it's just reading the cached / pre-compiled one. If the program finds a pre-compiled srb file, it could say "loading pre-compiled library" or something like that instead of compiling.
It happens on 18.5.1 and newer drivers. SRB miner wrong reads cards IDs. Because of it each start it have new ID's of cards and creats new kernel bins.
Look at names of .srb files. After name of card it place long string of numbers before end. And each time this numbers are differes.

It's exists 1 method to prevent this. But it's not a solution. Disable compute mode on Radeon Settings and than enable it again for each card.
But I think that doctor must update miner to support latest AMD drivers without issues.
jr. member
Activity: 288
Merit: 1
Hi Dok
V1.5.8 on startup, it generates the .srb file again
This is normal?


It should be generated once for every different gpu, after that on miner start that file should be read, not created again.


on rx 560 card generate each start
jr. member
Activity: 158
Merit: 5
Hi Dok
V1.5.8 on startup, it generates the .srb file again
This is normal?


It should be generated once for every different gpu, after that on miner start that file should be read, not created again.

Hi Doktor, I think this could be better communicated by the program. It *always* says "compiling" although it's just reading the cached / pre-compiled one. If the program finds a pre-compiled srb file, it could say "loading pre-compiled library" or something like that instead of compiling.
member
Activity: 363
Merit: 16
the srb file contains what?

is it better to generate new one if i change voltage/frequences?

and i set my card to 1408MHz (can see in HWInfo on idle) but after starting SRBMiner it shows 1387MHz - shutdown miner = 1408MHz?!
hero member
Activity: 2548
Merit: 626
Hi Dok
V1.5.8 on startup, it generates the .srb file again
This is normal?


It should be generated once for every different gpu, after that on miner start that file should be read, not created again.
newbie
Activity: 2
Merit: 0
Hi Dok
V1.5.8 on startup, it generates the .srb file again
This is normal?
newbie
Activity: 19
Merit: 0


U can enable “show bus I’ds” in the ODT settings :-)

i dont have that setting for some reason on my rigs, am using OverdriveNTools

Open OverDrivenTool > right click on title bar > settings > enable: show.. bus number > restart OverDrivenTool

ah works perfect, thank you. tried searching on google how to do this and could not come up with anything, just shows how awesome this community is
jr. member
Activity: 70
Merit: 3


U can enable “show bus I’ds” in the ODT settings :-)

i dont have that setting for some reason on my rigs, am using OverdriveNTools

Open OverDrivenTool > right click on title bar > settings > enable: show.. bus number > restart OverDrivenTool
newbie
Activity: 19
Merit: 0
i got this error . "HW error: BUS_ID_1: 1"
but share still accepted.
what dose it mean?
and what should i do?
thank you.

Quote
[2018-05-19 17:24:53] stats: Accepted/Total shares: 2/2

[2018-05-19 17:24:53] stats: Average time to find share: 50 seconds
[2018-05-19 17:24:53] stats: HW error: BUS_ID_1: 1


HW error means result from GPU on BUS ID 1 couldn't be validated, so it's discarded. It was not accepted. You should lower intensity or there is too much overclocking, that causes bad results.
Bus id's are used now for GPU identification cause they are unique, so if it says BUS ID 1, then it's BUS ID 1 in overdriventool, gpuz etc etc. It's easier to identify which card causes problems.


is there any way to identify GPUs by busID on overdriveNTool?

I am trying to troubleshoot some cards but the only way i am able to do it at the moment is by changing clock speeds to find out which busID/GPU corresponds to which GPU in the miner (they don't match)

Very time consuming process indeed but I believe the bus ID move is a good step

U can enable “show bus I’ds” in the ODT settings :-)

i dont have that setting for some reason on my rigs, am using OverdriveNTools
jr. member
Activity: 70
Merit: 3
all rigs -> v1.5.8

Thanks again doktor  Smiley
Jump to: