Pages:
Author

Topic: [ANN] Best sgminer so far for x22i/lyra2Z/phi2/allium on AMD - page 8. (Read 28318 times)

full member
Activity: 169
Merit: 100
Zjazz and Wildrig don't support Tahiti.
jr. member
Activity: 120
Merit: 4
I ran beta5f from a new folder, so no old bins. I also tried using a bin file made by beta5f with old beta and got the same error.

Just found a "bug" in the code. I guess you are not using "-w 256", right?
in file kernel/x22i.cl, line 1115, change "256" to "WORKSIZE" may solve your problem.
Yes, I usually use -w 128. Can you copy the whole line here please so I can search for it and edit? I use notepad to edit stuff lol, so no line numbers there.
Tried using -w 256. It works but I get 1.4 mhs, same hashrate as in beta5e++

I just updated the release files. Can you download again and try the new files?
Now it works fine with -w 128. No improvements in hashrate over previous beta for me. Seems that 1.4 mhs is the maximum hashrate I can get from such an old card with these settings:Smiley

Which driver are you using? The improvement I made for this new release is pretty driver dependent. I made some changes tuned for the driver I am using (almost the newest version). If you are using old driver there may not be improvement.
Adrenalin 18.5.1 on win7. Which driver would you recommend?

That seems pretty new. I guess that's all it can do for your card. Maybe the performance can be improved in next release.
What's the hashrate of other miners, like zjass or wiildog?
full member
Activity: 169
Merit: 100
I ran beta5f from a new folder, so no old bins. I also tried using a bin file made by beta5f with old beta and got the same error.

Just found a "bug" in the code. I guess you are not using "-w 256", right?
in file kernel/x22i.cl, line 1115, change "256" to "WORKSIZE" may solve your problem.
Yes, I usually use -w 128. Can you copy the whole line here please so I can search for it and edit? I use notepad to edit stuff lol, so no line numbers there.
Tried using -w 256. It works but I get 1.4 mhs, same hashrate as in beta5e++

I just updated the release files. Can you download again and try the new files?
Now it works fine with -w 128. No improvements in hashrate over previous beta for me. Seems that 1.4 mhs is the maximum hashrate I can get from such an old card with these settings:Smiley

Which driver are you using? The improvement I made for this new release is pretty driver dependent. I made some changes tuned for the driver I am using (almost the newest version). If you are using old driver there may not be improvement.
Adrenalin 18.5.1 on win7. Which driver would you recommend?
jr. member
Activity: 120
Merit: 4
I ran beta5f from a new folder, so no old bins. I also tried using a bin file made by beta5f with old beta and got the same error.

Just found a "bug" in the code. I guess you are not using "-w 256", right?
in file kernel/x22i.cl, line 1115, change "256" to "WORKSIZE" may solve your problem.
Yes, I usually use -w 128. Can you copy the whole line here please so I can search for it and edit? I use notepad to edit stuff lol, so no line numbers there.
Tried using -w 256. It works but I get 1.4 mhs, same hashrate as in beta5e++

I just updated the release files. Can you download again and try the new files?
Now it works fine with -w 128. No improvements in hashrate over previous beta for me. Seems that 1.4 mhs is the maximum hashrate I can get from such an old card with these settings:Smiley

Which driver are you using? The improvement I made for this new release is pretty driver dependent. I made some changes tuned for the driver I am using (almost the newest version). If you are using old driver there may not be improvement.
full member
Activity: 169
Merit: 100
I ran beta5f from a new folder, so no old bins. I also tried using a bin file made by beta5f with old beta and got the same error.

Just found a "bug" in the code. I guess you are not using "-w 256", right?
in file kernel/x22i.cl, line 1115, change "256" to "WORKSIZE" may solve your problem.
Yes, I usually use -w 128. Can you copy the whole line here please so I can search for it and edit? I use notepad to edit stuff lol, so no line numbers there.
Tried using -w 256. It works but I get 1.4 mhs, same hashrate as in beta5e++

I just updated the release files. Can you download again and try the new files?
Now it works fine with -w 128. No improvements in hashrate over previous beta for me. Seems that 1.4 mhs is the maximum hashrate I can get from such an old card with these settings:Smiley
jr. member
Activity: 120
Merit: 4
I ran beta5f from a new folder, so no old bins. I also tried using a bin file made by beta5f with old beta and got the same error.

Just found a "bug" in the code. I guess you are not using "-w 256", right?
in file kernel/x22i.cl, line 1115, change "256" to "WORKSIZE" may solve your problem.
Yes, I usually use -w 128. Can you copy the whole line here please so I can search for it and edit? I use notepad to edit stuff lol, so no line numbers there.
Tried using -w 256. It works but I get 1.4 mhs, same hashrate as in beta5e++

I just updated the release files. Can you download again and try the new files?
full member
Activity: 169
Merit: 100
I ran beta5f from a new folder, so no old bins. I also tried using a bin file made by beta5f with old beta and got the same error.

Just found a "bug" in the code. I guess you are not using "-w 256", right?
in file kernel/x22i.cl, line 1115, change "256" to "WORKSIZE" may solve your problem.
Yes, I usually use -w 128. Can you copy the whole line here please so I can search for it and edit? I use notepad to edit stuff lol, so no line numbers there.
Tried using -w 256. It works but I get 1.4 mhs, same hashrate as in beta5e++
jr. member
Activity: 120
Merit: 4
I ran beta5f from a new folder, so no old bins. I also tried using a bin file made by beta5f with old beta and got the same error.

Just found a "bug" in the code. I guess you are not using "-w 256", right?
in file kernel/x22i.cl, line 1115, change "256" to "WORKSIZE" may solve your problem.
full member
Activity: 169
Merit: 100
I ran beta5f from a new folder, so no old bins. I also tried using a bin file made by beta5f with old beta and got the same error.
jr. member
Activity: 120
Merit: 4
full member
Activity: 169
Merit: 100
Beta5f:  Error -54 enqueueing kernel search10 onto command queue. (clEnqueueNDRangeKernel)
GPU 0 failure, disabling!

Maybe you can try a lower -I number, like "-I 22". Also set "-g 1" may help.
I use intensity 16 and -g 1 didn't help. Previous beta works fine.

Log doesn't clear anything up I think

Quote
[08:52:29] Started sgminer v5.6.1.3
[08:52:29] * using Jansson 2.11
[08:52:30] CL Platform vendor: Advanced Micro Devices, Inc.
[08:52:30] CL Platform name: AMD Accelerated Parallel Processing
[08:52:30] CL Platform version: OpenCL 2.1 AMD-APP (2580.6)
[08:52:30] Platform devices: 1
[08:52:30]    0   Tahiti
[08:52:30] Probing for an alive pool
[08:52:30] Testing pool.dapool.me
[08:52:30] Stratum extranonce subscribe for pool.dapool.me
[08:52:31] Stratum authorisation success for pool.dapool.me
[08:52:31] pool.dapool.me alive
[08:52:31] Startup GPU initialization... Using settings from pool pool.dapool.me.
[08:52:31] Startup Pool No = 0
[08:52:31] Init GPU thread 0 GPU 0 virtual GPU 0
[08:52:31] CL Platform vendor: Advanced Micro Devices, Inc.
[08:52:31] CL Platform name: AMD Accelerated Parallel Processing
[08:52:31] CL Platform version: OpenCL 2.1 AMD-APP (2580.6)
[08:52:31] Platform devices: 1
[08:52:31]    0   Tahiti
[08:52:31] List of devices:
[08:52:31]    0   Tahiti
[08:52:31] Selected 0: Tahiti
[08:52:31] Maximum work size for this GPU (0) is 256.
[08:52:31] Your GPU (#0) has 32 compute units, and all AMD cards in the 7 series or newer (GCN cards)       have 64 shaders per compute unit - this means it has 2048 shaders.
[08:52:31] Initialising kernel x22i.cl with nfactor 10, n 1024
[08:52:31] initCl() finished. Found Tahiti
[08:52:31] pool.dapool.me difficulty changed to 0.025
[08:52:31] New block: 00000000000730795947fe963006e80b18be11c8bc55eaad72f35b64cab07595... diff 7.81K
[08:52:33] Work update message received
[08:52:33] Error -54: Enqueueing kernel search10 onto command queue. (clEnqueueNDRangeKernel)
[08:52:33] GPU 0 failure, disabling!

jr. member
Activity: 120
Merit: 4
Beta5f:  Error -54 enqueueing kernel search10 onto command queue. (clEnqueueNDRangeKernel)
GPU 0 failure, disabling!

Maybe you can try a lower -I number, like "-I 22". Also set "-g 1" may help.
jr. member
Activity: 120
Merit: 4


Beta5f release. x22i over 25% faster than beta5e, lyra2rev2 over 4x faster.
https://github.com/fancyIX/sgminer-phi2-branch/releases

Lyra2rev2?  or lyra2z... confused there... didn't know you did lyra2rev2.  not that it matters cause lyra2rev2 is asic country now

Lyra2re2.
It's almost impossible to to 4x faster for lyra2Z.
full member
Activity: 169
Merit: 100
Beta5f:  Error -54 enqueueing kernel search10 onto command queue. (clEnqueueNDRangeKernel)
GPU 0 failure, disabling!
sr. member
Activity: 703
Merit: 272


Beta5f release. x22i over 25% faster than beta5e, lyra2rev2 over 4x faster.
https://github.com/fancyIX/sgminer-phi2-branch/releases

Lyra2rev2?  or lyra2z... confused there... didn't know you did lyra2rev2.  not that it matters cause lyra2rev2 is asic country now
jr. member
Activity: 120
Merit: 4
It would be nice if this miner supported mining on the Blake2b algorithm and Siacoin. Now it is a very profitable cryptocurrency for this algorithm, but there are still no miners for video cards that would support it.

Will take a look. Thanks.
jr. member
Activity: 120
Merit: 4
Supports Windows and Linux. Supports windows driver and Linux AMDGPU Pro driver. Supports most cards. Comes with pre-built binary kernels to speed up Ellesmere and Vega cards.


https://github.com/fancyIX/sgminer-phi2-branch/releases/tag/5.6.1.3.b4b

Estimated speed:
phi2, rx 580: 1800khs; vega 56: 3300khs
lyra2Z, rx 580: 830khs; vega 56: 1620khs

I know that's far below the speed of tdxminer or teamredminer, but it's supports windows and Vega on Linux. And I am working on improving it. Hope one day it can be comparable with tdxminer.

Beta5 release, about 30% faster
https://github.com/fancyIX/sgminer-phi2-branch/releases/tag/5.6.1.3.b5

Beta5b release:
https://github.com/fancyIX/sgminer-phi2-branch/releases/tag/5.6.1.3.b5b
Speed compare of release (beta5b) than previous release (beta5): 580 +25%, Vega56 +35% for phi2, and 580 -15%, Vega56 +35% for lyra2Z .

Beta5c release, added allium support. Others are the same as beta5b.
https://github.com/fancyIX/sgminer-phi2-branch/releases/tag/5.6.1.3.b5c

Beta5d release, much faster than beta5c, especially for 580.
https://github.com/fancyIX/sgminer-phi2-branch/releases/tag/5.6.1.3.b5d

Beta 5e release, now support x22i. Others keep the same as beta5d:
https://github.com/fancyIX/sgminer-phi2-branch/releases
Will improve the performance further.

Beta5f release. x22i over 25% faster than beta5e, lyra2rev2 over 4x faster.
https://github.com/fancyIX/sgminer-phi2-branch/releases
member
Activity: 223
Merit: 10
It would be nice if this miner supported mining on the Blake2b algorithm and Siacoin. Now it is a very profitable cryptocurrency for this algorithm, but there are still no miners for video cards that would support it.
newbie
Activity: 19
Merit: 0
x22i - 1.4 mhs on r9 280x
How could you get this result at 280x? My r9 cards give out 880 hs
https://i.imgur.com/57XqqbQ.png
-w 128 -I 16
bios and clocks are stock
Unfortunately, my result has not improved, it seems to me that the problem is in the old driver, tomorrow I will be reinstalling.
full member
Activity: 169
Merit: 100
x22i - 1.4 mhs on r9 280x
How could you get this result at 280x? My r9 cards give out 880 hs

-w 128 -I 16
bios and clocks are stock
Pages:
Jump to: