hi can you add neoscrypt please?
i was hoping for MTP : / lol i feel like maybe AMD can really shine on MTP, but there's no good optimized public miners. miner devs if you see this, get on that shit money to be made man This
|
|
|
Uploaded hotfix.
Works now, thanks Xevan algo: 2.4 mhs on stock rx470 (win7)
|
|
|
New beta doesn't work for me. It says "Failed to start opencl threads". Version 0.15.3.8 works fine
|
|
|
ps: also almost finished xevan(two hashfuncs left to be 100% complete) and continue working on x16
Nice
|
|
|
Sorry, but no, I won't work on Lyra2z family algorithms. As I know fancyIX work on it, try his sgminer fork. Any chance on adding Xevan algo? There's sgminer for it, but it only works properly on older cards (tahiti and pitcairn). Tried using it with polaris but it gives hardware errors.
|
|
|
Hi. Does this miner need some special parameters to work with miningrigrentals? I use wildrig.exe --print-full --algo hmq1725 --opencl-threads auto --opencl-launch auto --url us-central01.miningrigrentals.com:3333 --user username.rig --pass x if ERRORLEVEL 1000 goto custom timeout /t 5 goto loop
:custom echo Some error happened, put custom command here timeout /t 5 goto loop and only get this
|
|
|
Recently, there have been a lot of rumors that Ethereum will move to a new hashing algorithm. Maybe you decide to make a miner under ProgPOW
ProgPow seems a good algo to apply gcn dpp instructions. Thanks for the info. Will work on it. Do you have any plans on adding x21s and x16rt?
|
|
|
Beta5f+ x22i: 1.5 mhs on r9 280x
|
|
|
I actually didn't mean that OP secretly mined with it . Should've used "made" instead of "released". My bad.
|
|
|
r9 280x 15 mhs on lyra2rev2. If only this miner had been released when this algo wasn't asic ridden
|
|
|
Zjazz and Wildrig don't support Tahiti.
|
|
|
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: 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?
|
|
|
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:
|
|
|
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 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.
|
|
|
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 [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!
|
|
|
Beta5f: Error -54 enqueueing kernel search10 onto command queue. (clEnqueueNDRangeKernel) GPU 0 failure, disabling!
|
|
|
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
|
|
|
x22i - 1.4 mhs on r9 280x
|
|
|
|