Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching - page 320. (Read 237263 times)
April 18, 2018, 08:18:47 AM
excuse me , noob question, what is ADL ?
April 18, 2018, 08:15:26 AM
do you get this with kernel 3? you have 512mb 6950?
--kernel 3ATI hd6870 1GB DDR5 (OC, timings moded)
Claymor 9.7 - 290 Hs
SRB 1.4.4 - 154 Hs+-
xmrstak - 171 Hs+-
April 18, 2018, 07:35:05 AM
V1.4.4
- Fixed (hopefully) situation when miner hashed in 'empty' for a long time
- Added mining session average speed display
- Removed greedybastard switch
ah, im tired. Please all of you having the 'devfee stuck' or 'miner not doing anything' problem, download this version and test.
It should be ok now.
Also removed the greedy switch. This is just taking too much of my free time, and i think the devfee % is not something terrible.
I hope everything will be stable now and i can get myself on the overclocking stuff and the API finally.
- Fixed (hopefully) situation when miner hashed in 'empty' for a long time
- Added mining session average speed display
- Removed greedybastard switch
ah, im tired. Please all of you having the 'devfee stuck' or 'miner not doing anything' problem, download this version and test.
It should be ok now.
Also removed the greedy switch. This is just taking too much of my free time, and i think the devfee % is not something terrible.
I hope everything will be stable now and i can get myself on the overclocking stuff and the API finally.
1.4.4 still crashes instantly when pressing "h" to see hashrate on all of my 15 rigs.
Miner is still rather unstable with restarts every 15-20 minutes.
The machines are stable on all other different software out there - And it has been stable for months.
--adldisable seems to have done the trick for now, going to test it a bit more.
can you tell on which cards do you have to use the --adldisable ?
I am only using MSI RX570 Armor 4GBs - All on 18.1 driver, not tested with newer ones as I have simply not had the time to tinker with it, it is working in general though.
With --adldisable it is stable, at least for the last 13 hours it has been stable on the two rigs that im testing it on now, tweaked intensity and are getting slight faster speeds than GGS now aswell, overall seems quite okay.
Hm on that card adl should work , at least with blockchain drivers it works.
April 18, 2018, 07:28:00 AM
V1.4.4
- Fixed (hopefully) situation when miner hashed in 'empty' for a long time
- Added mining session average speed display
- Removed greedybastard switch
ah, im tired. Please all of you having the 'devfee stuck' or 'miner not doing anything' problem, download this version and test.
It should be ok now.
Also removed the greedy switch. This is just taking too much of my free time, and i think the devfee % is not something terrible.
I hope everything will be stable now and i can get myself on the overclocking stuff and the API finally.
- Fixed (hopefully) situation when miner hashed in 'empty' for a long time
- Added mining session average speed display
- Removed greedybastard switch
ah, im tired. Please all of you having the 'devfee stuck' or 'miner not doing anything' problem, download this version and test.
It should be ok now.
Also removed the greedy switch. This is just taking too much of my free time, and i think the devfee % is not something terrible.
I hope everything will be stable now and i can get myself on the overclocking stuff and the API finally.
1.4.4 still crashes instantly when pressing "h" to see hashrate on all of my 15 rigs.
Miner is still rather unstable with restarts every 15-20 minutes.
The machines are stable on all other different software out there - And it has been stable for months.
--adldisable seems to have done the trick for now, going to test it a bit more.
can you tell on which cards do you have to use the --adldisable ?
I am only using MSI RX570 Armor 4GBs - All on 18.1 driver, not tested with newer ones as I have simply not had the time to tinker with it, it is working in general though.
With --adldisable it is stable, at least for the last 13 hours it has been stable on the two rigs that im testing it on now, tweaked intensity and are getting slight faster speeds than GGS now aswell, overall seems quite okay.
April 18, 2018, 07:26:34 AM
do you get this with kernel 3? you have 512mb 6950?
I use kernel 3 and my card is 2024 mb
April 18, 2018, 06:22:52 AM
Hi guys, one question, i have 6 rx580 8g doing 1050hs in CN Heavy . It's stable, without memory erros and etc. But when dev fee starts hashrate drops to 800/900+ and stays instable and after some 1 hour+ all cards stays at 1050 again. Wich could be the problem? Or is that a normal?
Thanks
Edit:
I'm using { "id" : x, "intensity" : 58, "worksize" : 16, "threads" : 2}, for all.
It's happening now:
https://i.imgur.com/P9GRh2r.png
Thanks
Edit:
I'm using { "id" : x, "intensity" : 58, "worksize" : 16, "threads" : 2}, for all.
It's happening now:
https://i.imgur.com/P9GRh2r.png
its normal, and its not because of devfee. heavy algo fluctuates a few hundred mhs.
Ok , thanks
Gj btw April 18, 2018, 06:15:03 AM
Hi guys, one question, i have 6 rx580 8g doing 1050hs in CN Heavy . It's stable, without memory erros and etc. But when dev fee starts hashrate drops to 800/900+ and stays instable and after some 1 hour+ all cards stays at 1050 again. Wich could be the problem? Or is that a normal?
Thanks
Edit:
I'm using { "id" : x, "intensity" : 58, "worksize" : 16, "threads" : 2}, for all.
It's happening now:
Thanks
Edit:
I'm using { "id" : x, "intensity" : 58, "worksize" : 16, "threads" : 2}, for all.
It's happening now:
its normal, and its not because of devfee. heavy algo fluctuates a few hundred mhs.
April 18, 2018, 06:11:18 AM
Hi guys, one question, i have 6 rx580 8g doing 1050hs in CN Heavy . It's stable, without memory erros and etc. But when dev fee starts hashrate drops to 800/900+ and stays instable and after some 1 hour+ all cards stays at 1050 again. Wich could be the problem? Or is that a normal?
Thanks
Edit:
I'm using { "id" : x, "intensity" : 58, "worksize" : 16, "threads" : 2}, for all.
It's happening now:
https://i.imgur.com/P9GRh2r.png
Thanks
Edit:
I'm using { "id" : x, "intensity" : 58, "worksize" : 16, "threads" : 2}, for all.
It's happening now:
https://i.imgur.com/P9GRh2r.png
April 18, 2018, 01:26:38 AM
Tell me how in the batch file to customize for each card its intensity?
all info you need is in the first post
April 18, 2018, 12:38:54 AM
Tell me how in the batch file to customize for each card its intensity?
April 17, 2018, 11:31:58 PM
Doctor, did you fix issue with launching Pitcairn card alone when it 3rd GPU?
V1.3.2
- Hopefully fixed bug when in 'gpu_conf' you want to set only one GPU
April 17, 2018, 11:30:49 PM
I was mining fine with (6x)Vega 64 on UltraHeavy(the lite one) despite not knowing the config.
Ive set intensity 110, worksize 16 adn threads 2 = 18000h
I did not tried any other config cuz 18k was fine to me. I know it could do more in this algo.
Doctor,
My doubt is, setting threads 2 in the config lines and not changing top from false to true will it work with 2?
Looks you do have the same parameter in two places.
PS. I do not recommend IPBC support pool cuz of the pool config setting too high diff. My client stayed 10min without sending hash with diff 2500000. This do not look a mistake at all...
This one is better: https://cryptoknight.cc/ipbc/
Can someone share a config to Vega 64 that makes it hash 2k in Monero7 algo?
Ive set intensity 110, worksize 16 adn threads 2 = 18000h
I did not tried any other config cuz 18k was fine to me. I know it could do more in this algo.
Doctor,
My doubt is, setting threads 2 in the config lines and not changing top from false to true will it work with 2?
Looks you do have the same parameter in two places.
PS. I do not recommend IPBC support pool cuz of the pool config setting too high diff. My client stayed 10min without sending hash with diff 2500000. This do not look a mistake at all...
This one is better: https://cryptoknight.cc/ipbc/
Can someone share a config to Vega 64 that makes it hash 2k in Monero7 algo?
let me quote you this from the first page :
"DON'T comment out or remove intensity and double_threads setting at the top of the config file, just leave it as-is, because when you use a per card setting, those settings will be ignored."
April 17, 2018, 11:29:30 PM
V1.4.4
- Fixed (hopefully) situation when miner hashed in 'empty' for a long time
- Added mining session average speed display
- Removed greedybastard switch
ah, im tired. Please all of you having the 'devfee stuck' or 'miner not doing anything' problem, download this version and test.
It should be ok now.
Also removed the greedy switch. This is just taking too much of my free time, and i think the devfee % is not something terrible.
I hope everything will be stable now and i can get myself on the overclocking stuff and the API finally.
- Fixed (hopefully) situation when miner hashed in 'empty' for a long time
- Added mining session average speed display
- Removed greedybastard switch
ah, im tired. Please all of you having the 'devfee stuck' or 'miner not doing anything' problem, download this version and test.
It should be ok now.
Also removed the greedy switch. This is just taking too much of my free time, and i think the devfee % is not something terrible.
I hope everything will be stable now and i can get myself on the overclocking stuff and the API finally.
1.4.4 still crashes instantly when pressing "h" to see hashrate on all of my 15 rigs.
Miner is still rather unstable with restarts every 15-20 minutes.
The machines are stable on all other different software out there - And it has been stable for months.
--adldisable seems to have done the trick for now, going to test it a bit more.
can you tell on which cards do you have to use the --adldisable ?
April 17, 2018, 11:06:42 PM
do you get this with kernel 3? you have 512mb 6950?
April 17, 2018, 10:24:26 PM
Hello everyone!
Does this miner support TeraScale/VLIW Radeon GPUs?
Does this miner support TeraScale/VLIW Radeon GPUs?
it should work, but you wont get speeds like on old claymore.
Which card do you have?
And yeah, hashing speed is only half compared to Claymore v9.7...
download v 1.4.3 and add --usekernel 3 in the bat like this :
%EXE% --config config.txt --pools pools.txt --usekernel 3
this is a test kernel im working on for those oldies
Thanks for caring about old GPUs (most devs don't), I'll give it a try!
Another problem with all miners I've tried (except Claymore v9.7) is that there is no "low intensity" option, which means the UI is lagging a lot (if you want to use your PC while mining).
I wish someone could replicate Claymore v9.7 characteristics and I'd gladly pay a mining fee...
can you download 1.4.4 now and try again with --usekernel 3 parameter in bat, but set start intensity to 10 , and use only 1 thread. Then work up the intensity as much as you can.
I tried intensity to 10, 67 H/s only, then I increased it to 12 and the entire PC froze. :\
I don't understand why GPU mining it's so hard compared to CPU mining where you just set the available CPU cores...
Radeon 5770 (Juniper) has 800 ALUs (10 Compute Units x 16 SIMD x 5 ALUs).
I don't even understand what intensity is supposed to do ALU-wise... why not allow us to set ALUs manually?
Claymore uses hashcount option and optimal value is 320 hashes (320 ALUs?), 2MB each = 320 x 2 = 640MB of VRAM needed. The GPU has 1024MB of VRAM, so I can still use the PC while mining with no lagging.
Is it so hard to write proper VLIW assembly (from what I've heard at least) and only Claymore has mastered this art of programming? Just wondering...
hi DOK, I get 320 h/s and with claymore 9.7 360 h/s, both results with OC, excellent work, a little more and you get over it, congratulations. (DISCUSS MY ENGLISH, I USE GOOGLE TRANSLATOR JAJAJAJAJA)
***** I have a 6950 with 6970 bios and drivers 14.4 *****
April 17, 2018, 09:33:50 PM
I was mining fine with (6x)Vega 64 on UltraHeavy(the lite one) despite not knowing the config.
Ive set intensity 110, worksize 16 adn threads 2 = 18000h
I did not tried any other config cuz 18k was fine to me. I know it could do more in this algo.
Doctor,
My doubt is, setting threads 2 in the config lines and not changing top from false to true will it work with 2?
Looks you do have the same parameter in two places.
PS. I do not recommend IPBC support pool cuz of the pool config setting too high diff. My client stayed 10min without sending hash with diff 2500000. This do not look a mistake at all...
This one is better: https://cryptoknight.cc/ipbc/
Can someone share a config to Vega 64 that makes it hash 2k in Monero7 algo?
Just force diff with wallet.diff Ive set intensity 110, worksize 16 adn threads 2 = 18000h
I did not tried any other config cuz 18k was fine to me. I know it could do more in this algo.
Doctor,
My doubt is, setting threads 2 in the config lines and not changing top from false to true will it work with 2?
Looks you do have the same parameter in two places.
PS. I do not recommend IPBC support pool cuz of the pool config setting too high diff. My client stayed 10min without sending hash with diff 2500000. This do not look a mistake at all...
This one is better: https://cryptoknight.cc/ipbc/
Can someone share a config to Vega 64 that makes it hash 2k in Monero7 algo?
April 17, 2018, 08:18:09 PM
I was mining fine with (6x)Vega 64 on UltraHeavy(the lite one) despite not knowing the config.
Ive set intensity 110, worksize 16 adn threads 2 = 18000h
I did not tried any other config cuz 18k was fine to me. I know it could do more in this algo.
Doctor,
My doubt is, setting threads 2 in the config lines and not changing top from false to true will it work with 2?
Looks you do have the same parameter in two places.
PS. I do not recommend IPBC support pool cuz of the pool config setting too high diff. My client stayed 10min without sending hash with diff 2500000. This do not look a mistake at all...
This one is better: https://cryptoknight.cc/ipbc/
Can someone share a config to Vega 64 that makes it hash 2k in Monero7 algo?
Ive set intensity 110, worksize 16 adn threads 2 = 18000h
I did not tried any other config cuz 18k was fine to me. I know it could do more in this algo.
Doctor,
My doubt is, setting threads 2 in the config lines and not changing top from false to true will it work with 2?
Looks you do have the same parameter in two places.
PS. I do not recommend IPBC support pool cuz of the pool config setting too high diff. My client stayed 10min without sending hash with diff 2500000. This do not look a mistake at all...
This one is better: https://cryptoknight.cc/ipbc/
Can someone share a config to Vega 64 that makes it hash 2k in Monero7 algo?
April 17, 2018, 07:51:46 PM
write intensities, algorithm and gpu memory. so it is unclear.
April 17, 2018, 07:28:55 PM
Has anyone had any luck with 1 thread on rx570s? Best I can get is 650h/s using 2 threads intensity 29 and workload 8, anyone have any insights?
Sorry 4gb cards on heavy
Edit: got 730 with 1 thread 60 intensity
Thanks,
--J
Sorry 4gb cards on heavy
Edit: got 730 with 1 thread 60 intensity
Thanks,
--J
April 17, 2018, 06:14:38 PM
Hello everyone!
Does this miner support TeraScale/VLIW Radeon GPUs?
Does this miner support TeraScale/VLIW Radeon GPUs?
it should work, but you wont get speeds like on old claymore.
Which card do you have?
And yeah, hashing speed is only half compared to Claymore v9.7...
download v 1.4.3 and add --usekernel 3 in the bat like this :
%EXE% --config config.txt --pools pools.txt --usekernel 3
this is a test kernel im working on for those oldies
Thanks for caring about old GPUs (most devs don't), I'll give it a try!
Another problem with all miners I've tried (except Claymore v9.7) is that there is no "low intensity" option, which means the UI is lagging a lot (if you want to use your PC while mining).
I wish someone could replicate Claymore v9.7 characteristics and I'd gladly pay a mining fee...
can you download 1.4.4 now and try again with --usekernel 3 parameter in bat, but set start intensity to 10 , and use only 1 thread. Then work up the intensity as much as you can.
I tried intensity to 10, 67 H/s only, then I increased it to 12 and the entire PC froze. :\
I don't understand why GPU mining it's so hard compared to CPU mining where you just set the available CPU cores...
Radeon 5770 (Juniper) has 800 ALUs (10 Compute Units x 16 SIMD x 5 ALUs).
I don't even understand what intensity is supposed to do ALU-wise... why not allow us to set ALUs manually?
Claymore uses hashcount option and optimal value is 320 hashes (320 ALUs?), 2MB each = 320 x 2 = 640MB of VRAM needed. The GPU has 1024MB of VRAM, so I can still use the PC while mining with no lagging.
Is it so hard to write proper VLIW assembly (from what I've heard at least) and only Claymore has mastered this art of programming? Just wondering...
Jump to: