[Dev] NeoScrypt GPU Miner - Public Beta Test
-
Did you delete the .bin file before starting up sgminer ?
I found the kernal wouldn’t work with either my versions of cg, but it did work on sg for me.
Swapped out the .cl and deleted the bin files. Started it up, sgminer put together the new bin file, and now it starts like normal every time.
Yes, all pre-existing bins were deleted beforehand. I use cgwatcher, and I have vbs + bat scripts that are scheduled to auto delete all the bins from the cg/sgminer folder(s) when I stop or restart the miner.
-
same for me 280x 14.9beta2 nothing but HW errors! tried w48-512 I 13-15
I am afraid we will have to wait for Wolf0, or someone else, to debug the code in his kernel to find out what’s going on. I couldn’t get a single worksize, thread-concurrency, thread number, or intensity setting to work on any of the AMD GCN cards I use.
Also, if you haven’t done so already, consider sending a small donation to Wolf0 for his work. He doesn’t have any obligation to release his personal kernels to us. His FTC address is posted a few pages back. He also accepts donations in LTC https://litecointalk.org/index.php?topic=17533.0
-
Ah ok…
It works on my nVidia, but slower.
This is all somewhat worrying.
Let’s wait on wolf I suppose.
-
Yeah, issues here too…
SGminer 4.2.2/5.0 (wolf0 build)
Run with the same bins, runs the exact same speed.
Delete the bins, 50% speed increase, but 100% hw errors, no accepted.
-
13-xx driver gives accepted share but speed equal to 14.9 drivers with previous kernel
-
Yeah, issues here too…
SGminer 4.2.2/5.0 (wolf0 build)
Run with the same bins, runs the exact same speed.
Delete the bins, 50% speed increase, but 100% hw errors, no accepted.
Running same bins will always give you same speed. As long as settings stay the same, cg/sgminer detects the existing bins and will skip using the AMD opencl compiler to compile an optimized bin from the new kernel.
-
13-xx driver gives accepted share but speed equal to 14.9 drivers with previous kernel
Well that is pretty interesting, but still disappointing. I hope we don’t have a regression back to having to create bins in 13.x catalyst drivers, and then using them with 14.9.
-
And with CGminer
[2014-11-11 05:17:21] Started cgminer 3.7.7b
[2014-11-11 05:17:22] Probing for an alive pool
[2014-11-11 05:17:23] Pool 0 difficulty changed to 64
[2014-11-11 05:17:24] Error -11: Building Program (clBuildProgram)
[2014-11-11 05:17:24] “C:\Users\molton\AppData\Local\Temp\OCL6112T14.cl”, line 367: warning:
variable “t” was declared but never referenced
uint4 t, st[4];
^“C:\Users\molton\AppData\Local\Temp\OCL6112T14.cl”, line 486: error:
identifier "WOR
[2014-11-11 05:17:24] Failed to init GPU thread 0, disabling device 0
[2014-11-11 05:17:24] Restarting the GPU from the menu will not fix this.
[2014-11-11 05:17:24] Try restarting cgminer.
Press enter to continue:then
ST: 0 SS: 0 NB: 3 LW: 5 GF: 0 RF: 0
Connected to stratum.gun.theblocksfactory.com diff 64 with stratum as user slow
Block: 18375c6c267580d5… Diff:11.5K Started: [05:18:32] Best share: 0[P]ool management [S]ettings [D]isplay options [Q]uit
GPU 0: 46.0C 975RPM | OFF / 0.000h/s | A:0 R:0 HW:0 WU:0.0/m I:15
GPU 1: 43.0C 1042RPM | OFF / 0.000h/s | A:0 R:0 HW:0 WU:0.0/m I:15
GPU 2: 53.0C 1461RPM | OFF / 0.000h/s | A:0 R:0 HW:0 WU:0.0/m I:15
GPU 3: 52.0C 1410RPM | OFF / 0.000h/s | A:0 R:0 HW:0 WU:0.0/m I:15^
“C:\Users\molton\AppData\Local\Temp\OCL6112T44.cl”, line 486: error:
identifier "WOR
[2014-11-11 05:18:42] Failed to init GPU thread 10, disabling device 3
[2014-11-11 05:18:42] Error -11: Building Program (clBuildProgram)
[2014-11-11 05:18:42] “C:\Users\molton\AppData\Local\Temp\OCL6112T47.cl”, line 367: warning:
variable “t” was declared but never referenced
uint4 t, st[4];
^“C:\Users\molton\AppData\Local\Temp\OCL6112T47.cl”, line 486: error:
identifier "WOR
[2014-11-11 05:18:42] Failed to init GPU thread 11, disabling device 3C:\- coinage\-aneoscrypt\GPU\neoscrypt-cgminer-3.7.7b>pause
Press any key to continue . . . -
crossing bins gave only HW…
-
LOL, I think we have been punked… ;)
-
Tmuir has been able to get a 100%+ increase… I’ve pm’d him to get him to share his results here.
-
Tmuir has been able to get a 100%+ increase… I’ve pm’d him to get him to share his results here.
- configs, drivers, card used?
with 13.xx driver there was a big increase, it managed to hash accepted shares with equal speed as my 14.9 drivers
-
Once he’s about I’m sure he will have no issue’s giving all details.
I hope you don’t mind this Tmuir :(
[8:01:09 PM] Tmuir: yes got 100% improvement, just installing catalyst 14.9 to see if that makes a differnce
[8:01:20 PM] Tmuir: need to use sgminer
[8:07:59 PM] Tmuir: updated to catalyst 14.9 and now I’m getting 110kh/s, prior to this I was getting 39Kh/s so that is about 175% increase
[8:14:21 PM] Tmuir: whoops sorry its only doing hw at 110
[8:31:51 PM] Tmuir: with 13.12 the new kernal gives me about 100% increaseThis is all I’m going on.
-
Once he’s about I’m sure he will have no issue’s giving all details.
I hope you don’t mind this Tmuir :(
This is all I’m going on.
Apparently 14.6 or 14.7 drivers are the key.
Trying it out now, but it’s slow going doing a driver swap via remote desktop on a phone…
-
Just ran it again and i was mistaken 100% HW errors on an nVidia GT 630M
-
Works for me was only getting 39kh/s with my Gigabyte GV-R7870C-2GD, now getting 71 to 73kh/s.
This is with the sgminer, replace the old file and delete the bin and restart. everything else the same.
Didn’t get it to play with cgminer yet though.
This is with catalyst 13.12
-
Working for me, after a little bit of tweaking. 280kh/s per card on Windows - Gigabyte R9 280x.
-
Update, changed from 13.12 to 14.4 (latest catalyst doesn’t work but 14.14 does) and took another jump to just over 100kh/s, so I’m getting 150% improvement over what I was previously
-
3x 280X not overclocked. It can go up to 400Kh/s or more when I play with clock
[url=http://postimg.org/image/3lq5wr9sf/]
[/url] -
3x 280X not overclocked. It can go up to 400Kh/s or more when I play with clock
Settings?
