Bitcoin Forum
January 18, 2022, 11:34:39 AM *
News: Latest Bitcoin Core release: 22.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 [179] 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 ... 365 »
  Print  
Author Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching  (Read 235786 times)
fellowbeing
Newbie
*
Offline Offline

Activity: 15
Merit: 0


View Profile WWW
July 23, 2018, 01:26:43 PM
 #3561

Vega FEs are allergic to 18.3.4 and I'll get less hash-rate on Alloy/Heavy and CN7, on Alloy there is alot of STALE shares too, so the only viable driver is 18.6.1.

Results for a rig having 5 Vega FEs SRB Miner 1.6.4:
driver 18.6.1
CN7  = 11060 H/s
Alloy = 5670 H/s
note: Mining Alloy, on DevFee we get miner crash or error

driver 18.3.4
CN7  = 10900 H/s
Alloy = 5580 H/s
note: Mining Alloy, there is a lot of STALE shares.

Results for a rig having 5 Vega FEs SRB Miner 1.6.1:
driver 18.6.1
CN7  = 10910 H/s
Alloy = 5630 H/s

driver Blockchain Aug 23
CN7  = 10910 H/s
Alloy = 5630 H/s

=========================================
So in conclusion:
18.3.4 won't work for Vega FEs. For Alloy we have to use 1.6.1 and we get similar hashrates as blockchain driver.

Edited: The said crash/error occurs not on DevFee but right after when resuming!

Stales are not a problem if they are accepted,i guess the difficulty on the pool you use is low, and the pool sends jobs quickly, so that is why you get a lot of stales, but if they are accepted then you have no problem.
Also could you turn on logging (use --logfile log.txt in bat added) maybe i can get more info on the crash ?
If i understand you correctly only on 18.6.1 is the miner crashing, on 18.3.4 it isnt ?

Yes, I'll do this and see what we get. Regarding the drivers, I think 18.3.4 is just not working for me, even on CN7 I get lower hash-rate simiar to what I used to get on Blockchain driver about 150 H/s less or 50 H/s less on heavy/Alloy, but 18.6.1 has been very stable for me. So I avoid 18.3.4 totally. As for heavy/Alloy algo while using the SRB 1.6.4, I get GPU crash right after DevFee sometimes recovers after resetting the miner but other times I have to close the miner and restart it manually. I noticed this happened on 1.6.1 too but apparently less often. I don't have a clue what the cause could be, but I guess it might be something to do with change of algo from Alloy to DevFee and back. Unfortunately I have not had the chance to try any other heavy algo yet. I'll set the log and see what happens and come back. Thanks
1642505679
Hero Member
*
Offline Offline

Posts: 1642505679

View Profile Personal Message (Offline)

Ignore
1642505679
Reply with quote  #2

1642505679
Report to moderator
1642505679
Hero Member
*
Offline Offline

Posts: 1642505679

View Profile Personal Message (Offline)

Ignore
1642505679
Reply with quote  #2

1642505679
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1642505679
Hero Member
*
Offline Offline

Posts: 1642505679

View Profile Personal Message (Offline)

Ignore
1642505679
Reply with quote  #2

1642505679
Report to moderator
1642505679
Hero Member
*
Offline Offline

Posts: 1642505679

View Profile Personal Message (Offline)

Ignore
1642505679
Reply with quote  #2

1642505679
Report to moderator
1642505679
Hero Member
*
Offline Offline

Posts: 1642505679

View Profile Personal Message (Offline)

Ignore
1642505679
Reply with quote  #2

1642505679
Report to moderator
doktor83
Hero Member
*****
Offline Offline

Activity: 1876
Merit: 621


View Profile WWW
July 23, 2018, 01:55:44 PM
 #3562

Vega FEs are allergic to 18.3.4 and I'll get less hash-rate on Alloy/Heavy and CN7, on Alloy there is alot of STALE shares too, so the only viable driver is 18.6.1.

Results for a rig having 5 Vega FEs SRB Miner 1.6.4:
driver 18.6.1
CN7  = 11060 H/s
Alloy = 5670 H/s
note: Mining Alloy, on DevFee we get miner crash or error

driver 18.3.4
CN7  = 10900 H/s
Alloy = 5580 H/s
note: Mining Alloy, there is a lot of STALE shares.

Results for a rig having 5 Vega FEs SRB Miner 1.6.1:
driver 18.6.1
CN7  = 10910 H/s
Alloy = 5630 H/s

driver Blockchain Aug 23
CN7  = 10910 H/s
Alloy = 5630 H/s

=========================================
So in conclusion:
18.3.4 won't work for Vega FEs. For Alloy we have to use 1.6.1 and we get similar hashrates as blockchain driver.

Edited: The said crash/error occurs not on DevFee but right after when resuming!

Stales are not a problem if they are accepted,i guess the difficulty on the pool you use is low, and the pool sends jobs quickly, so that is why you get a lot of stales, but if they are accepted then you have no problem.
Also could you turn on logging (use --logfile log.txt in bat added) maybe i can get more info on the crash ?
If i understand you correctly only on 18.6.1 is the miner crashing, on 18.3.4 it isnt ?

Yes, I'll do this and see what we get. Regarding the drivers, I think 18.3.4 is just not working for me, even on CN7 I get lower hash-rate simiar to what I used to get on Blockchain driver about 150 H/s less or 50 H/s less on heavy/Alloy, but 18.6.1 has been very stable for me. So I avoid 18.3.4 totally. As for heavy/Alloy algo while using the SRB 1.6.4, I get GPU crash right after DevFee sometimes recovers after resetting the miner but other times I have to close the miner and restart it manually. I noticed this happened on 1.6.1 too but apparently less often. I don't have a clue what the cause could be, but I guess it might be something to do with change of algo from Alloy to DevFee and back. Unfortunately I have not had the chance to try any other heavy algo yet. I'll set the log and see what happens and come back. Thanks


There is no change of algo when doing devfee mining, if you mine alloy then the devfee is also doing alloy, if mining heavy then its heavy etc.
Also did you try switching pools manually (by defining more than one pool in pools.txt and pressing p) ? Is this crashing the miner ?

SRBMiner-MULTI thread - HERE
http://www.srbminer.com
qwep1
Hero Member
*****
Offline Offline

Activity: 608
Merit: 500


View Profile
July 23, 2018, 09:09:34 PM
 #3563

hi all what setting for bittube for 580 4 gb

              ▄▄██▄▄
          ▄▄██████████▄▄
      ▄▄██████████████████▄▄
  ▄▄██████████▀▀ ▀▀██████████▄▄
▄█████████▀▀          ▀▀█████████▄
██████▀▀        ▄▄        ▀▀██████
██████      ▄▄██████▄▄      ██████
██████    ██████████████    ██████
██████    ██████████████    ██████
██████    ██████████████    ██████
██████      ▀▀██████▀▀      ██████
██████          ▀▀        ▄▄██████
▀█████    ▄▄          ▄▄█████████▀
   ▀▀█    ████▄▄ ▄▄██████████▀▀
          ████████████████▀▀
          ▀▀██████████▀▀
              ▀▀██▀▀
P H O R E

     █
    █
   █
  █
   █
    █
   █
  █
 █
    KryptKoin rebranded to Phore   
     █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █
PoS 3.0  -  Masternodes  -  Obfuscation


     █
    █
   █
  █
   █
    █
   █
  █
 █
.


            ▄▄██▄▄
        ▄▄██████████▄▄
    ▄▄████████▀▀████████▄▄
 ▄████████▀▀      ▀▀████████▄
▐█████▀▀              ▀▀█████▌
▐████       ▄▄██▄▄       ████▌
▐████    ▄██████████▄    ████▌
▐████    ████████████    ████▌
▐████    ▀██████████▀    ████▌
▐████       ▀▀██▀▀       ████▌
 ▀███                 ▄▄█████▌
    ▀    █▄▄      ▄▄████████▀
         █████▄▄████████▀▀
         ▀██████████▀▀
            ▀▀██▀▀
UAGet
Newbie
*
Offline Offline

Activity: 70
Merit: 0


View Profile
July 24, 2018, 05:37:58 AM
 #3564

Hi! Are there plans to support the purk algorithm?
doktor83
Hero Member
*****
Offline Offline

Activity: 1876
Merit: 621


View Profile WWW
July 24, 2018, 06:33:03 AM
Last edit: July 24, 2018, 09:37:19 AM by doktor83
 #3565

hi all what setting for bittube for 580 4 gb

Auto intensity should be good enough, also you can try the value auto gives + 1.
4GB cards work better with 1 thread on tube.

so this should be good:


{
"cryptonight_type" : "bittubev2",
"intensity" : 0,
"double_threads" : false,
}

SRBMiner-MULTI thread - HERE
http://www.srbminer.com
doktor83
Hero Member
*****
Offline Offline

Activity: 1876
Merit: 621


View Profile WWW
July 24, 2018, 06:33:40 AM
 #3566

Hi! Are there plans to support the purk algorithm?

Nope, it's not cryptonight algo.

SRBMiner-MULTI thread - HERE
http://www.srbminer.com
kryx
Newbie
*
Offline Offline

Activity: 91
Merit: 0


View Profile
July 24, 2018, 07:55:11 AM
 #3567


Does this miner works with the old R9 280x ?
                       
Anyone tried?
doktor83
Hero Member
*****
Offline Offline

Activity: 1876
Merit: 621


View Profile WWW
July 24, 2018, 07:56:14 AM
 #3568


Does this miner works with the old R9 280x ?
                       
Anyone tried?

yes it works

SRBMiner-MULTI thread - HERE
http://www.srbminer.com
chafer99
Member
**
Offline Offline

Activity: 93
Merit: 10


View Profile
July 24, 2018, 09:34:50 AM
 #3569

SRB is best for my 4xR380 (CN7 - 740H/s per card - 1050/1600Mhz) but very unstable: "application has been blocked from accessing graphics hardware".
The same problems as default settings (1000/1500Mhz). Driver 18.5.1 whql, Win10 (1803). Claymore 11.3 is OK.

What settings for RX580 8Gb? I got only 820H/s in CN7 (intensity 60/8/2, 1430/2200Mhz).
doktor83
Hero Member
*****
Offline Offline

Activity: 1876
Merit: 621


View Profile WWW
July 24, 2018, 09:44:35 AM
 #3570

SRB is best for my 4xR380 (CN7 - 740H/s per card - 1050/1600Mhz) but very unstable: "application has been blocked from accessing graphics hardware".
The same problems as default settings (1000/1500Mhz). Driver 18.5.1 whql, Win10 (1803). Claymore 11.3 is OK.

What settings for RX580 8Gb? I got only 820H/s in CN7 (intensity 60/8/2, 1430/2200Mhz).

Application blocked text = driver crash
Try with 1 thread, i had better results with 1 thread when testing on 380 4g.

56/8/2 is ok for 580 8g.
Are you using a custom strap? Memory brand?

SRBMiner-MULTI thread - HERE
http://www.srbminer.com
JuanHungLo
Hero Member
*****
Offline Offline

Activity: 935
Merit: 1001


I don't always drink...


View Profile
July 24, 2018, 11:01:50 AM
 #3571

Hi! Are there plans to support the purk algorithm?

Nope, it's not cryptonight algo.


From Purk's page:
Quote
Based on Boolberry & CryptoNote technology,...

Bull markets are born on pessimism, grow on skepticism, mature on optimism, and die on euphoria. - John Templeton
doktor83
Hero Member
*****
Offline Offline

Activity: 1876
Merit: 621


View Profile WWW
July 24, 2018, 11:04:04 AM
 #3572

Hi! Are there plans to support the purk algorithm?

Nope, it's not cryptonight algo.


From Purk's page:
Quote
Based on Boolberry & CryptoNote technology,...

From purk.miner.rocks :

Quote
Please use supported mining apps and configs for wildkeccak

SRBMiner-MULTI thread - HERE
http://www.srbminer.com
SpceGhst
Jr. Member
*
Offline Offline

Activity: 270
Merit: 4


View Profile
July 24, 2018, 11:12:21 AM
 #3573

Hi! Are there plans to support the purk algorithm?

Nope, it's not cryptonight algo.


From Purk's page:
Quote
Based on Boolberry & CryptoNote technology,...

If you read the ANN thread, algo is wild keccak...
https://bitcointalk.org/index.php?topic=3213127.0
chafer99
Member
**
Offline Offline

Activity: 93
Merit: 10


View Profile
July 24, 2018, 11:31:26 AM
 #3574

SRB is best for my 4xR380 (CN7 - 740H/s per card - 1050/1600Mhz) but very unstable: "application has been blocked from accessing graphics hardware".
The same problems as default settings (1000/1500Mhz). Driver 18.5.1 whql, Win10 (1803). Claymore 11.3 is OK.

What settings for RX580 8Gb? I got only 820H/s in CN7 (intensity 60/8/2, 1430/2200Mhz).

Application blocked text = driver crash
Try with 1 thread, i had better results with 1 thread when testing on 380 4g.

56/8/2 is ok for 580 8g.
Are you using a custom strap? Memory brand?

Thanks, now intensity 56, thread 1 - 700H/s (R380 2g, samsung) looks stable. (previous 31/8/2 - 740H/s)

RX580 in default (no custom straps/mem). But not bad in Heavy algo - 1000H/s
JuanHungLo
Hero Member
*****
Offline Offline

Activity: 935
Merit: 1001


I don't always drink...


View Profile
July 24, 2018, 11:32:35 AM
 #3575

Hi! Are there plans to support the purk algorithm?

Nope, it's not cryptonight algo.


From Purk's page:
Quote
Based on Boolberry & CryptoNote technology,...

If you read the ANN thread, algo is wild keccak...
https://bitcointalk.org/index.php?topic=3213127.0


I read, and plenty.

https://cryptonote.org/cns/cns008.txt

http://cpucoinlist.com/cryptocurrency-algorithms/wild-keccack/

The original question from UAGet was not inordinate.  It was a reasonable question.

Bull markets are born on pessimism, grow on skepticism, mature on optimism, and die on euphoria. - John Templeton
doktor83
Hero Member
*****
Offline Offline

Activity: 1876
Merit: 621


View Profile WWW
July 24, 2018, 11:36:30 AM
 #3576

SRB is best for my 4xR380 (CN7 - 740H/s per card - 1050/1600Mhz) but very unstable: "application has been blocked from accessing graphics hardware".
The same problems as default settings (1000/1500Mhz). Driver 18.5.1 whql, Win10 (1803). Claymore 11.3 is OK.

What settings for RX580 8Gb? I got only 820H/s in CN7 (intensity 60/8/2, 1430/2200Mhz).

Application blocked text = driver crash
Try with 1 thread, i had better results with 1 thread when testing on 380 4g.

56/8/2 is ok for 580 8g.
Are you using a custom strap? Memory brand?

Thanks, now intensity 56, thread 1 - 700H/s (R380 2g, samsung) looks stable. (previous 31/8/2 - 740H/s)

RX580 in default (no custom straps/mem). But not bad in Heavy algo - 1000H/s

When i was testing r9 380 with double threads i could not go beyond intensity 28-29, it simply always crashed the driver.

SRBMiner-MULTI thread - HERE
http://www.srbminer.com
doktor83
Hero Member
*****
Offline Offline

Activity: 1876
Merit: 621


View Profile WWW
July 24, 2018, 11:37:54 AM
 #3577

Hi! Are there plans to support the purk algorithm?

Nope, it's not cryptonight algo.


From Purk's page:
Quote
Based on Boolberry & CryptoNote technology,...

If you read the ANN thread, algo is wild keccak...
https://bitcointalk.org/index.php?topic=3213127.0


I read, and plenty.

https://cryptonote.org/cns/cns008.txt

http://cpucoinlist.com/cryptocurrency-algorithms/wild-keccack/

The original question from UAGet was not inordinate.  It was a reasonable question.

so i checked out the opencl kernel of purk and it has nothing to do with cryptonight algo.
That's why there are wildkeccak miners for purk, not cryptonight miners.

SRBMiner-MULTI thread - HERE
http://www.srbminer.com
chafer99
Member
**
Offline Offline

Activity: 93
Merit: 10


View Profile
July 24, 2018, 12:18:30 PM
Last edit: July 24, 2018, 12:47:18 PM by chafer99
 #3578

SRB is best for my 4xR380 (CN7 - 740H/s per card - 1050/1600Mhz) but very unstable: "application has been blocked from accessing graphics hardware".
The same problems as default settings (1000/1500Mhz). Driver 18.5.1 whql, Win10 (1803). Claymore 11.3 is OK.

What settings for RX580 8Gb? I got only 820H/s in CN7 (intensity 60/8/2, 1430/2200Mhz).

Application blocked text = driver crash
Try with 1 thread, i had better results with 1 thread when testing on 380 4g.

56/8/2 is ok for 580 8g.
Are you using a custom strap? Memory brand?

Thanks, now intensity 56, thread 1 - 700H/s (R380 2g, samsung) looks stable. (previous 31/8/2 - 740H/s)

RX580 in default (no custom straps/mem). But not bad in Heavy algo - 1000H/s

When i was testing r9 380 with double threads i could not go beyond intensity 28-29, it simply always crashed the driver.

at 31 intensity works, but after 4-5 hours driver crashed, (the same as 28-30 intensity).
https://imgur.com/oTgtb0p
hesido
Jr. Member
*
Offline Offline

Activity: 155
Merit: 5


View Profile
July 24, 2018, 09:42:20 PM
 #3579

SRB is best for my 4xR380 (CN7 - 740H/s per card - 1050/1600Mhz) but very unstable: "application has been blocked from accessing graphics hardware".
The same problems as default settings (1000/1500Mhz). Driver 18.5.1 whql, Win10 (1803). Claymore 11.3 is OK.

What settings for RX580 8Gb? I got only 820H/s in CN7 (intensity 60/8/2, 1430/2200Mhz).

Application blocked text = driver crash
Try with 1 thread, i had better results with 1 thread when testing on 380 4g.

56/8/2 is ok for 580 8g.
Are you using a custom strap? Memory brand?

Thanks, now intensity 56, thread 1 - 700H/s (R380 2g, samsung) looks stable. (previous 31/8/2 - 740H/s)

RX580 in default (no custom straps/mem). But not bad in Heavy algo - 1000H/s

When i was testing r9 380 with double threads i could not go beyond intensity 28-29, it simply always crashed the driver.

at 31 intensity works, but after 4-5 hours driver crashed, (the same as 28-30 intensity).
https://imgur.com/oTgtb0p


Try to adjust your OC, most instabilities I've had could be solved by throwing more voltage at the cards or reducing the frequencies.
chafer99
Member
**
Offline Offline

Activity: 93
Merit: 10


View Profile
July 25, 2018, 04:35:47 AM
 #3580

SRB is best for my 4xR380 (CN7 - 740H/s per card - 1050/1600Mhz) but very unstable: "application has been blocked from accessing graphics hardware".
The same problems as default settings (1000/1500Mhz). Driver 18.5.1 whql, Win10 (1803). Claymore 11.3 is OK.

What settings for RX580 8Gb? I got only 820H/s in CN7 (intensity 60/8/2, 1430/2200Mhz).

Application blocked text = driver crash
Try with 1 thread, i had better results with 1 thread when testing on 380 4g.

56/8/2 is ok for 580 8g.
Are you using a custom strap? Memory brand?

Thanks, now intensity 56, thread 1 - 700H/s (R380 2g, samsung) looks stable. (previous 31/8/2 - 740H/s)

RX580 in default (no custom straps/mem). But not bad in Heavy algo - 1000H/s

When i was testing r9 380 with double threads i could not go beyond intensity 28-29, it simply always crashed the driver.

at 31 intensity works, but after 4-5 hours driver crashed, (the same as 28-30 intensity).
https://imgur.com/oTgtb0p


Try to adjust your OC, most instabilities I've had could be solved by throwing more voltage at the cards or reducing the frequencies.

Yes, i tried OC, other miners, algos, etc.(claymore pow7, zcash, ethash is OK). This problem (crash driver) they only cards conected to splitter-PCIe:
https://ae01.alicdn.com/kf/HTB167XXaBUSMeJjSszeq6AKgpXae/CY-PCI-e-Express-1x-to-4-Port-1x-Switch-Multiplier-Splitter-Hub-Riser-Card-with.jpg_640x640.jpg
Pages: « 1 ... 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 [179] 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 ... 365 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!