Author

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

newbie
Activity: 36
Merit: 0
There is a big problem since version 1.4.0, I have only pool rejected results (low difficulty share).

No problem with version 1.3.2

I had the same problem but figured it out, it was because the information for pools has now moved to the pools file, the config file no long holds the pool information Smiley

Ok thank you !
newbie
Activity: 51
Merit: 0
There is a big problem since version 1.4.0, I have only pool rejected results (low difficulty share).

No problem with version 1.3.2

I had the same problem but figured it out, it was because the information for pools has now moved to the pools file, the config file no long holds the pool information Smiley
newbie
Activity: 36
Merit: 0
There is a big problem since version 1.4.0, I have only pool rejected results (low difficulty share).

No problem with version 1.3.2
sr. member
Activity: 2142
Merit: 353
Xtreme Monster
After 7 hours I’ve got 9 hw errors and 17 block expires on nanopool. Is this normal? What’s most worrying are those hw errors. HWinfo reports no errors, though. Really appreciate your opinions.

expired block means the share you sent got old because the block expired in the meantime.
Hw error means gpu result did not pass cpu validation. So if you want try lowering intensity, or mem clock for ex.

Is it different than stale shares? I wonder what could be expired block, stales shares mean you send the work/share/result after the block was found.
jr. member
Activity: 156
Merit: 1
thanks doktor for this miner (and I like the "iamagreedybastard" option, even if I don't use it!)

Mining heavy with 1xRX480 4 GB + 1xRX580 8 GB, the hashrate reported by the pool starts above 5000 H/S for the 2 cards when I launch the miner and decrease to 1600 H/S in something like 5 minutes... (Win 10, August blockchain driver, SRBMiner V1.4.1)

On the miner window, hashrate is always around 1600 H/S but I can clearly see that just after starting, it displays "pool accepted result xxxx" very fast corrsponding to higher hashrate and then the pace slowly decrease...

Any idea?
iwm
newbie
Activity: 7
Merit: 0
Hi there!

Trying new 1.4.1 version and it have a strange bug - in pools.txt config I can't use DOT on the wallet string. Trying to make Nanopool
.., but with DOT miner doesn't work. Devs, please, fix this bug! Thx!  Wink
full member
Activity: 1274
Merit: 105
What location should I use in the pool file if I don't know where the pool is located?
newbie
Activity: 19
Merit: 0
Who's got a hd 6950 and can test something for me?

I have, I do not speak English but I use the translator
newbie
Activity: 65
Merit: 0
Could we have an option to keep our pools list in our config file like before? ie, if no pools file look in config file?  I usually keep a long list of configs for easily switching between cryptos depending on the difficulty, and it's helpful to keep all info in one file.
newbie
Activity: 26
Merit: 0
doktor83,

Very nice work.  I can confirm that 110.5 is the optimal intensity for Vega 56 reference air cards at this point using Blockchain drivers.


intensity 120 for Vega 56 reference
hero member
Activity: 935
Merit: 1001
I don't always drink...
doktor83,

Very nice work.  I can confirm that 110.5 is the optimal intensity for Vega 56 reference air cards at this point using Blockchain drivers.

I can now confirm that your miner is beating the latest XMR-Stak stellitequestion-compiled-0 miner with better temperature and hashrate, not by much, but still better.

The only thing keeping me from full utilization is the API send for remote monitoring.  I know you are working on it and I anxiously await it.
newbie
Activity: 59
Merit: 0
After 7 hours I’ve got 9 hw errors and 17 block expires on nanopool. Is this normal? What’s most worrying are those hw errors. HWinfo reports no errors, though. Really appreciate your opinions.


Hw error means gpu result did not pass cpu validation. So if you want try lowering intensity, or mem clock for ex.

So this means the shares were wasted and not sent to the pool? My local hashrate is 5057 and the pool reports the average hashrates between 4990 and greater than 5000. Is this ok so I can ignore the hw errors by srbminer?

THank you.
hero member
Activity: 2548
Merit: 626
After 7 hours I’ve got 9 hw errors and 17 block expires on nanopool. Is this normal? What’s most worrying are those hw errors. HWinfo reports no errors, though. Really appreciate your opinions.

expired block means the share you sent got old because the block expired in the meantime.
Hw error means gpu result did not pass cpu validation. So if you want try lowering intensity, or mem clock for ex.
hero member
Activity: 2548
Merit: 626
Who's got a hd 6950 and can test something for me?
newbie
Activity: 59
Merit: 0
After 7 hours I’ve got 9 hw errors and 17 block expires on nanopool. Is this normal? What’s most worrying are those hw errors. HWinfo reports no errors, though. Really appreciate your opinions.
newbie
Activity: 5
Merit: 0
tried changing name of .exe file?
Oh.Thanks,thats works!
newbie
Activity: 65
Merit: 0
Already mining 24hrs+, the local results are 4.4kh/s, and by the pool i'm getting 4.8-5.2! Really incredible miner, thanks  Cool
newbie
Activity: 13
Merit: 0
For those running Vega.  Below are some of my settings a hashrates. These are on a reference 56 running 950 mem, non soft table mods. Stock bios on the newest drivers - non-blockchain.

All below running V1 on Stellite.

Intensity/thread/worksize/hash

118/2/8/1863
119/2/8/1859
120/2/8/1888
109/2/16/1869
109.5/2/16/1892
110/2/16/1893
110.5/2/16/1932
111/2/16/1890
109.5/2/20/1851
92/2/20/1731
100/2/24/1793
105/2/24/1814
110/2/24/1832
115/2/24/1857
120/2/24/1892  *Locked Win - hard reset required after a few minutes then had to uninstall drivers and cards then re-install*

Appears worksize 16 was the sweetspot. Someone with modded cards running higher clockspeeds give it a run and post some results.

hmmm... I'll have to do some more testing... after seeing this...

I'm running stock bios XFX RX Vega 56 cards GPU 1407/950 MEM 925/900 with 85% pp tables running 6 cards pulling 1140-1160watts from the wall. Also running latest AMD Adrenalin 18.3.4 drivers.

112/2/16/1886 <--stable running V1 on Electroneum

If I turn the memory up to 950MHz then I can get into the 1920-1940 h/s but its not stable for all the cards. Now with the latest version and the logging is improved I should be able to narrow down the card or cards that are giving me issues.
jr. member
Activity: 153
Merit: 2
For those running Vega.  Below are some of my settings a hashrates. These are on a reference 56 running 950 mem, non soft table mods. Stock bios on the newest drivers - non-blockchain.

All below running V1 on Stellite.

Intensity/thread/worksize/hash

118/2/8/1863
119/2/8/1859
120/2/8/1888
109/2/16/1869
109.5/2/16/1892
110/2/16/1893
110.5/2/16/1932
111/2/16/1890
109.5/2/20/1851
92/2/20/1731
100/2/24/1793
105/2/24/1814
110/2/24/1832
115/2/24/1857
120/2/24/1892  *Locked Win - hard reset required after a few minutes then had to uninstall drivers and cards then re-install*

Appears worksize 16 was the sweetspot. Someone with modded cards running higher clockspeeds give it a run and post some results.




newbie
Activity: 59
Merit: 0
Hi all,

What is worksize? I read it’s the local gpu thread, but how many of these are there in an rx 570?

Thank you.
Jump to: