Bitcoin Forum
September 21, 2019, 08:31:59 AM *
News: Latest Bitcoin Core release: 0.18.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 [284] 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 ... 366 »
  Print  
Author Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching  (Read 227081 times)
dazzmore
Newbie
*
Offline Offline

Activity: 23
Merit: 0


View Profile
December 19, 2018, 03:28:39 AM
 #5661

Hi Dok, is there any way to find out which GPU (I have mix 56's & 64's with different memories) crashed the system? I've tried searching log but can't really tell. TIA
1569054719
Hero Member
*
Offline Offline

Posts: 1569054719

View Profile Personal Message (Offline)

Ignore
1569054719
Reply with quote  #2

1569054719
Report to moderator
1569054719
Hero Member
*
Offline Offline

Posts: 1569054719

View Profile Personal Message (Offline)

Ignore
1569054719
Reply with quote  #2

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

Posts: 1569054719

View Profile Personal Message (Offline)

Ignore
1569054719
Reply with quote  #2

1569054719
Report to moderator
1569054719
Hero Member
*
Offline Offline

Posts: 1569054719

View Profile Personal Message (Offline)

Ignore
1569054719
Reply with quote  #2

1569054719
Report to moderator
1569054719
Hero Member
*
Offline Offline

Posts: 1569054719

View Profile Personal Message (Offline)

Ignore
1569054719
Reply with quote  #2

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

Activity: 1120
Merit: 582


View Profile WWW
December 19, 2018, 07:08:59 AM
 #5662

Hi Dok, is there any way to find out which GPU (I have mix 56's & 64's with different memories) crashed the system? I've tried searching log but can't really tell. TIA

depends how the system crashed, if blue screen or freeze then you can't do much i guess.
If just a card dropped out, that will be in the log.

SRBPolaris thread - HERE   |   SRBMiner thread - HERE
http://www.srbminer.com
lsHaKeRl
Newbie
*
Offline Offline

Activity: 18
Merit: 0


View Profile
December 19, 2018, 12:26:40 PM
 #5663

Hi Dok, is there any way to find out which GPU (I have mix 56's & 64's with different memories) crashed the system? I've tried searching log but can't really tell. TIA

Hi Mate!

It´s easy to find out which Card is "damaged", just go to device Manager and just activate 1 GPU Card 1 by 1 and run the miner with just 1 ID, then let run the miner.

maybe it helps.  Roll Eyes

Greetings
Patrick
doktor83
Hero Member
*****
Offline Offline

Activity: 1120
Merit: 582


View Profile WWW
December 19, 2018, 02:05:55 PM
 #5664

V1.7.3
- Bringing back support for GCN1 cards [pitcairn, tahiti ...]
- Heavy_mode 2 is now an improved 3 with a little less hash and less errors than 3
- Small OCL optimisations for Vegas
- Added parameter 'off_temperature' to gpu_conf, to protect GPU from overheating
- Added parameter 'old_mode' to gpu_conf, which creates the kernel with the old method
- Added new algo 'Hycon'
- Added new algo 'Upx'
- Added new algo 'Stellitev8'
- Renamed algo 'freehaven' to 'swap'


+ Even if unintentionally, but SRB became slower and slower on old GCN1 cards because optimisations that were good for newer gpu's were a kill for those oldes.
I managed to borrow a tahiti card (280x) for a few days, and create a new kernel that is now working OK with these oldies. Speeds should be acceptable now Smiley

+ As you know there are 3 heavy modes available. This is how it goes now :
1. Slowest but shouldn't produce any compute errors
2. Faster than 1, it is a re-worked 3, a little bit slower than 3, but with less errors
3. The fastest but it can produce the most compute errors

I think 2 could be the winner here because my tests of 12hr show :
1. 0 errors
2. 1 error
3. 4 errors


Of course the default one is still 1, because it is the most stable mode.

+ Added a gpu_conf only parameter 'off_temperature'. I think this will be very useful. What it does is it turns off that one particular overheated GPU until it cools down by 15c, then it's turned back on.
Default is 85c, so that means if a GPU reaches 85c, miner turns it off automatically (while the other GPU's are still working), and it waits until it cools down by 15c, in this case that is 70c.
When temperature is < 70c the GPU is automatically turned back on and it continues to work.
The '15c' difference can't be changed.

+ Added a gpu_conf only parameter 'old_mode'. With the changes i made in 1.7.2, that allow the creation of kernels on drivers newer than 18.6.1, algos that use a scratchpad <=1MB (litev7, mox, dark, upx) suffer from a hashrate drop on Vegas (maybe others too, i didn't test). So if you set this parameter to true, it will create kernel the old way, and the speed on these algos should be back.
Don't forget, if you use old_mode : true, and compile the kernel on a driver newer than 18.6.1, you probably won't be finding any shares!

+ Added 3 new algos :

- upx [ https://bitcointalk.org/index.php?topic=5058404.0 ]
- hycon [ https://hycon.io ]
- stellitev8 [ https://bitcointalk.org/index.php?topic=2813261.0 ]

Stellitev8 will be active when stellite forks.

SRBPolaris thread - HERE   |   SRBMiner thread - HERE
http://www.srbminer.com
GKumaran
Jr. Member
*
Offline Offline

Activity: 137
Merit: 1


View Profile
December 19, 2018, 03:00:11 PM
 #5665

Thank you for the new version Dok !!  Cheesy
Restores 1mb algo speeds to their original high speeds !!

For vega users :  the key word being GPU_Conf "ONLY"

Code:
"gpu_conf" :
[
{ "id" : 0, "intensity" : 0, "worksize" : 8, "fragments" : 1, "double_threads" : true, "old_mode" : true }
]
doktor83
Hero Member
*****
Offline Offline

Activity: 1120
Merit: 582


View Profile WWW
December 19, 2018, 03:11:03 PM
 #5666

Thank you for the new version Dok !!  Cheesy
Restores 1mb algo speeds to their original high speeds !!

For vega users :  the key word being GPU_Conf "ONLY"

Code:
"gpu_conf" :
[
{ "id" : 0, "intensity" : 0, "worksize" : 8, "fragments" : 1, "double_threads" : true, "old_mode" : true }
]

Yes, i should use font size 300, because even if there are separate sections for gpu_conf and other parameters in the readme, and on the first page, somehow people dont see it  Roll Eyes

SRBPolaris thread - HERE   |   SRBMiner thread - HERE
http://www.srbminer.com
zeef
Newbie
*
Offline Offline

Activity: 249
Merit: 0


View Profile
December 19, 2018, 03:20:46 PM
 #5667

V1.7.3
- Bringing back support for GCN1 cards [pitcairn, tahiti ...]
- Heavy_mode 2 is now an improved 3 with a little less hash and less errors than 3
- Small OCL optimisations for Vegas
- Added parameter 'off_temperature' to gpu_conf, to protect GPU from overheating
- Added parameter 'old_mode' to gpu_conf, which creates the kernel with the old method
- Added new algo 'Hycon'
- Added new algo 'Upx'
- Added new algo 'Stellitev8'
- Renamed algo 'freehaven' to 'swap'


+ Even if unintentionally, but SRB became slower and slower on old GCN1 cards because optimisations that were good for newer gpu's were a kill for those oldes.
I managed to borrow a tahiti card (280x) for a few days, and create a new kernel that is now working OK with these oldies. Speeds should be acceptable now Smiley

+ As you know there are 3 heavy modes available. This is how it goes now :
1. Slowest but shouldn't produce any compute errors
2. Faster than 1, it is a re-worked 3, a little bit slower than 3, but with less errors
3. The fastest but it can produce the most compute errors

I think 2 could be the winner here because my tests of 12hr show :
1. 0 errors
2. 1 error
3. 4 errors


Of course the default one is still 1, because it is the most stable mode.

+ Added a gpu_conf only parameter 'off_temperature'. I think this will be very useful. What it does is it turns off that one particular overheated GPU until it cools down by 15c, then it's turned back on.
Default is 85c, so that means if a GPU reaches 85c, miner turns it off automatically (while the other GPU's are still working), and it waits until it cools down by 15c, in this case that is 70c.
When temperature is < 70c the GPU is automatically turned back on and it continues to work.
The '15c' difference can't be changed.

+ Added a gpu_conf only parameter 'old_mode'. With the changes i made in 1.7.2, that allow the creation of kernels on drivers newer than 18.6.1, algos that use a scratchpad <=1MB (litev7, mox, dark, upx) suffer from a hashrate drop on Vegas (maybe others too, i didn't test). So if you set this parameter to true, it will create kernel the old way, and the speed on these algos should be back.
Don't forget, if you use old_mode : true, and compile the kernel on a driver newer than 18.6.1, you probably won't be finding any shares!

+ Added 3 new algos :

- upx [ https://bitcointalk.org/index.php?topic=5058404.0 ]
- hycon [ https://hycon.io ]
- stellitev8 [ https://bitcointalk.org/index.php?topic=2813261.0 ]

Stellitev8 will be active when stellite forks.

Thanks for new version.

When could we see support for a more recent amd drivers?

Thanks
doktor83
Hero Member
*****
Offline Offline

Activity: 1120
Merit: 582


View Profile WWW
December 19, 2018, 03:38:56 PM
 #5668


Thanks for new version.

When could we see support for a more recent amd drivers?

Thanks

What do you mean?
It works with the latest drivers also

SRBPolaris thread - HERE   |   SRBMiner thread - HERE
http://www.srbminer.com
zeef
Newbie
*
Offline Offline

Activity: 249
Merit: 0


View Profile
December 19, 2018, 04:10:33 PM
 #5669


Thanks for new version.

When could we see support for a more recent amd drivers?

Thanks

What do you mean?
It works with the latest drivers also

hmm ok nice..

As i seen recommend 18.6.1. did not want to risk.

1 - Can i install it and mine normally without change anything in my config_?

2 - Other question dok, i notice that auto intensity from version 1.7.0 was [56] and now is [60] ,for vega 64, why such increase? is safe to maintain that?

3 - In my rigs i use winver v1709 and disable all updates. I want to use in my desktop pc one vega 64, its ok to install last winver and amd drivers with no lose in performance? Smiley in rigs im not updating anything, only for new drives if you say is safe Smiley Cool

Many thanks for help  Cool
Dubai-Industry
Newbie
*
Offline Offline

Activity: 10
Merit: 0


View Profile
December 19, 2018, 05:43:23 PM
 #5670

Many thanks to the creator of this great miner!
justoiurii
Newbie
*
Offline Offline

Activity: 89
Merit: 0


View Profile
December 20, 2018, 08:54:53 AM
 #5671

Hi, DOK) Thanks for the upgrade)
UPX algo, RX 480 8G, bc drivers, intens 0 - 3890H/sec (wow!!!). I'm afraid a little) Is it - OK?
Bllacky
Newbie
*
Offline Offline

Activity: 22
Merit: 0


View Profile
December 20, 2018, 09:02:42 AM
 #5672

Hi,

There is an issue with your miner.
The kernel cache created for the
Radeon 280X and Radeon 270X are created for monero with the same name: g9_CNV8_w16_f8_hm1_ha.srb
If you have a system which combines 280X and 270X cards, then you can't use both card, since the kernel generated for one type will fail on the other.

You should generate different kernels for the 280X and 270X. Thank you.
wgestickley
Newbie
*
Offline Offline

Activity: 75
Merit: 0


View Profile
December 20, 2018, 11:29:43 AM
 #5673

Hey Doc,

- will the different Heavy Mode (1-3) effect only 8GB or also 4GB Versions Cards?
- when will Stellite fork approximately?
doktor83
Hero Member
*****
Offline Offline

Activity: 1120
Merit: 582


View Profile WWW
December 20, 2018, 12:01:26 PM
 #5674

Hi,

There is an issue with your miner.
The kernel cache created for the
Radeon 280X and Radeon 270X are created for monero with the same name: g9_CNV8_w16_f8_hm1_ha.srb
If you have a system which combines 280X and 270X cards, then you can't use both card, since the kernel generated for one type will fail on the other.

You should generate different kernels for the 280X and 270X. Thank you.

You are right, the whole GCN1 family is put under the same id (g9), i supposed that a pitcairn binary should work on a tahiti etc.it looks like it's not that way.
I will separate them in the next version.

Can you tell me how are speeds now with the tahiti and pitcairn, compared to other miners?

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

Activity: 1120
Merit: 582


View Profile WWW
December 20, 2018, 12:02:47 PM
 #5675

Hey Doc,

- will the different Heavy Mode (1-3) effect only 8GB or also 4GB Versions Cards?
- when will Stellite fork approximately?

Why don't you try and see for yourself ? Smiley
It should have effect on both cards.

IDK about Stellite fork because they still don't know, and don't have a date yet.

SRBPolaris thread - HERE   |   SRBMiner thread - HERE
http://www.srbminer.com
wgestickley
Newbie
*
Offline Offline

Activity: 75
Merit: 0


View Profile
December 20, 2018, 12:29:58 PM
 #5676

Hey Doc,

- will the different Heavy Mode (1-3) effect only 8GB or also 4GB Versions Cards?
- when will Stellite fork approximately?

Why don't you try and see for yourself ? Smiley
It should have effect on both cards.

IDK about Stellite fork because they still don't know, and don't have a date yet.


Yeah, of course i will do it!
But i am currently on the road and want to calculate how many of my Cards in my Farm could be effected :-)

Last Time, with Version 1.7.2 i think there was no difference in the 3 Versions or have i done a failure?
Can i put it also on top of the config File where the General stuff for all Cards are or have i to do it in the line for each card where i set intensitiy for each card etc???
Bllacky
Newbie
*
Offline Offline

Activity: 22
Merit: 0


View Profile
December 20, 2018, 12:50:02 PM
 #5677

Hi,

There is an issue with your miner.
The kernel cache created for the
Radeon 280X and Radeon 270X are created for monero with the same name: g9_CNV8_w16_f8_hm1_ha.srb
If you have a system which combines 280X and 270X cards, then you can't use both card, since the kernel generated for one type will fail on the other.

You should generate different kernels for the 280X and 270X. Thank you.

You are right, the whole GCN1 family is put under the same id (g9), i supposed that a pitcairn binary should work on a tahiti etc.it looks like it's not that way.
I will separate them in the next version.

Can you tell me how are speeds now with the Tahiti and Pitcairn, compared to other miners?

It's a bit complicated with the speeds.
I would say they definitely went up for most cards, the 270X has a massive boost, hashing now at 400H/s.
The 280X is now hashing at around 440 H/s which is also an improvement.
The 290 went down to 460H/s initially from 540H/s, but after some tweaking, it went up to 520 H/s.

I only use R9 cards with your miner, the Vegas I have are mining ETH.

There also seems to be an issue with the off-temperature
this is a config example:
{ "id" : 0, "kernel": 1, "intensity" : 60, "worksize" : 16, "threads" : 1, "double_threads" : false, "target_temperature" : 90, "target_fan_speed": 2500, "off_temperature":90, "adl_type": 1},

But the miner still switches-off the video cards at 85C.
Also, I'm not sure if the fan controls work well for Pitcairn cards, most of the time they read 0 rpm or somthing like 10000 rpm and don't seem to spin at all.
doktor83
Hero Member
*****
Offline Offline

Activity: 1120
Merit: 582


View Profile WWW
December 20, 2018, 05:21:34 PM
Last edit: December 20, 2018, 05:44:20 PM by doktor83
 #5678

Thanks for all the info!

You example could be written as :

{ "id" : 0, "intensity" : 60, "worksize" : 16, "threads" : 1, "target_temperature" : 90, "target_fan_speed": 2500, "off_temperature":90, "adl_type": 1}

I tested the off_temperature on on a few rigs, it was OK, but going to check again.
Edit : ok found the problem, going to fix in next version

Until then you can set "off_temperature" outside gpu_conf

Quote
Also, I'm not sure if the fan controls work well for Pitcairn cards, most of the time they read 0 rpm or somthing like 10000 rpm and don't seem to spin at all.

For those oldies adl_type 2 should be used (in 1.7.3 it is now auto set for GCN1 cards), but to be honest i don't know if the target temperature and fan speed stuff work on those cards, i couldn't test it.

SRBPolaris thread - HERE   |   SRBMiner thread - HERE
http://www.srbminer.com
1.2-GIGAHASH
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
December 20, 2018, 06:01:46 PM
 #5679

Thanks for good software!
zeef
Newbie
*
Offline Offline

Activity: 249
Merit: 0


View Profile
December 21, 2018, 01:09:43 PM
 #5680


Thanks for new version.

When could we see support for a more recent amd drivers?

Thanks

What do you mean?
It works with the latest drivers also

hmm ok nice..

As i seen recommend 18.6.1. did not want to risk.

1 - Can i install it and mine normally without change anything in my config_?

2 - Other question dok, i notice that auto intensity from version 1.7.0 was [56] and now is [60] ,for vega 64, why such increase? is safe to maintain that?

3 - In my rigs i use winver v1709 and disable all updates. I want to use in my desktop pc one vega 64, its ok to install last winver and amd drivers with no lose in performance? Smiley in rigs im not updating anything, only for new drives if you say is safe Smiley Cool

4 - Its possible to put in log the gpu temps?

Many thanks for help    Cool
Pages: « 1 ... 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 [284] 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 ... 366 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!