[ANN] sgminer v5 - optimized X11/X13/NeoScrypt/Lyra2RE/etc. kernel-switch miner

[jch9678]

Got it running around 310Kh.

I think i'll take that instead of tweaking further to gain just a little bit more.

Thank you all!

So what settings did you end up with that gave you 310

[Hamuki]

Can someone help me please?

I cant get this to work.

I am trying to solo mine for fun on just 1 card in my PC.

Its a R9 280x Windforce 3x Rev2.0 card.

Can someone make a complete Bat file for me that I can use?

I just want to use 50% of the power on the GPU. It isnt that well, it got a little damaged from when I tried to mine scrypt on it, and it wasnt happy. So I dont want to push it too much.

Its for solo mining and I need to know how I switch from one coin to another.

Thank you so much!

Have a great day!

EDIT:

P.S Just write the config here, ill just copy and paste it and make it to a BAT file.

[Zuikkis]

Got it running around 310Kh.

I think i'll take that instead of tweaking further to gain just a little bit more.

Thank you all!

310 is pretty much the maximum for r9 290 on the publicly available kernel.

[go6ooo1212]

I think Wolf0's private kernel is about 60% faster...

[go6ooo1212]

I think Wolf0's private kernel is about 60% faster...

More like 85% - 90%.

Hah , you rule the code, respect...

[DragonSlayer]

Are there any other guides on building windows binaries?  I prefer to build Win64 if all possible.  I have follow the instruction in the doc folder to no end.  These are not very up to date.  I would help submit updates to the build docs if I ever get a successful build that works.

Here is what happen when I tried the cross-build.

Code:

root@miner:/home/sgminer/winbuild# CPPFLAGS="-I`pwd`/home/win32/include" LDFLAGS="-L`pwd`/home/win32/lib -lcurldll" ../autogen.sh --prefix=/usr/local/i586-mingw32 --host=i586-mingw32msvc --build=i686-linux --enable-scrypt --enable-opencl
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
configure.ac:24: installing './compile'
configure.ac:17: installing './config.guess'
configure.ac:17: installing './config.sub'
configure.ac:22: installing './install-sh'
configure.ac:22: installing './missing'
Makefile.am: installing './depcomp'
root@miner:/home/sgminer/winbuild# make
make: *** No targets specified and no makefile found.  Stop.

Thanks

[damm315er]

Try 13, like damm315er is using.

Thx wolf, 13 is giving me 240. Still far away from +300

Try xI 3 or 4, but specify thread concurrency with it. Set it to 16384.

Also, what clocks?

I know this was a while ago but ystarnaud said that xintensity and rawintensity are unused.  

https://bitcointalk.org/index.php?topic=632503.msg9475388#msg9475388

That was on Nov. 7 so I guess xI does now work with neo.  That's good news I was about to make a bunch of bins with different intensities with the 13.12 drivers and then upgrade to 14.6 rc2.  Is making bins with 13.12 a waste of time?

xI works on SG5 dev, and the wolf build. (although I've had crap luck using both xintensity and rawintensity because my GPU's are in the bottlenecked category)

The bin creation then driver upgrade isn't required for SGminer, it is only required on CGminer.  With SGminer, install the 14.9 or later drivers on the machine, and drop the 14.6 files in the SGminer folder.

Last I knew, to solo mine still requires CGminer tho.  Someone please correct me if I'm wrong.

[damm315er]

Got it running around 310Kh.

I think i'll take that instead of tweaking further to gain just a little bit more.

Thank you all!

310 is pretty much the maximum for r9 290 on the publicly available kernel.

Well, I can get about 7% better than the 310, but don't expect me to hand out the specifics..  (WHOOOO!!! 7%!!!  lol)

[damm315er]

Try 13, like damm315er is using.

Thx wolf, 13 is giving me 240. Still far away from +300

Try xI 3 or 4, but specify thread concurrency with it. Set it to 16384.

Also, what clocks?

I know this was a while ago but ystarnaud said that xintensity and rawintensity are unused.  

https://bitcointalk.org/index.php?topic=632503.msg9475388#msg9475388

That was on Nov. 7 so I guess xI does now work with neo.  That's good news I was about to make a bunch of bins with different intensities with the 13.12 drivers and then upgrade to 14.6 rc2.  Is making bins with 13.12 a waste of time?

xI works on SG5 dev, and the wolf build. (although I've had crap luck using both xintensity and rawintensity because my GPU's are in the bottlenecked category)

The bin creation then driver upgrade isn't required for SGminer, it is only required on CGminer.  With SGminer, install the 14.9 or later drivers on the machine, and drop the 14.6 files in the SGminer folder.

Last I knew, to solo mine still requires CGminer tho.  Someone please correct me if I'm wrong.

Using 13.12 isn't required at all with my kernels, whether you use CGMiner or SGMiner. Solo mining requires CGMiner - SGMiner cannot do it currently.

True, 13.12 was only needed with the original kernel, Wolf's likes 14.6.

[jch9678]

Try 13, like damm315er is using.

Thx wolf, 13 is giving me 240. Still far away from +300

Try xI 3 or 4, but specify thread concurrency with it. Set it to 16384.

Also, what clocks?

I know this was a while ago but ystarnaud said that xintensity and rawintensity are unused.  

https://bitcointalk.org/index.php?topic=632503.msg9475388#msg9475388

That was on Nov. 7 so I guess xI does now work with neo.  That's good news I was about to make a bunch of bins with different intensities with the 13.12 drivers and then upgrade to 14.6 rc2.  Is making bins with 13.12 a waste of time?

xI works on SG5 dev, and the wolf build. (although I've had crap luck using both xintensity and rawintensity because my GPU's are in the bottlenecked category)

The bin creation then driver upgrade isn't required for SGminer, it is only required on CGminer.  With SGminer, install the 14.9 or later drivers on the machine, and drop the 14.6 files in the SGminer folder.

Last I knew, to solo mine still requires CGminer tho.  Someone please correct me if I'm wrong.

Using 13.12 isn't required at all with my kernels, whether you use CGMiner or SGMiner. Solo mining requires CGMiner - SGMiner cannot do it currently.

True, 13.12 was only needed with the original kernel, Wolf's likes 14.6.

Thanks guys, I appreciate it. Unfortunately, I missed these replies and went ahead and tested with 13.12.  That's a couple hours I'd like to have back.  Is there a particular reason you like installing >14.9 drivers and then drop the 14.6 files into the directory?  I usually just use 14.6 rc2.  Maybe it's more stable?, my new windows install seems to have developed stability issues.

[varthshenon]

I'm getting HW errors in neoscrypt all the time 
Using 14.12 driver
I know it's the driver and the kernel problem, can anyone give me the kernel file or the bin file for 280x?

Thanks 

EDIT : Someone sent me the .bin thanks

[cohnhead]

hi ...if anyone can give some advice, it would be appreciated

I have 3x290's getting about 6.3mhz each... running sgminer 5  , using catalyst 14.7 r3 driver, mining algo x11....no other settings than X 64 w64.

Can I be getting better speeds using 14.6 drivers...and or other settings ie mem clock etc

thanks

[Mario241077]

I'm getting HW errors in neoscrypt all the time 
Using 14.12 driver
I know it's the driver and the kernel problem, can anyone give me the kernel file or the bin file for 280x?

Thanks 

EDIT : Someone sent me the .bin thanks

look here the discription

https://bitcointalk.org/index.php?topic=725450.260

[drr0ss]

hi ...if anyone can give some advice, it would be appreciated

I have 3x290's getting about 6.3mhz each... running sgminer 5  , using catalyst 14.7 r3 driver, mining algo x11....no other settings than X 64 w64.

Can I be getting better speeds using 14.6 drivers...and or other settings ie mem clock etc

thanks

You can buy the miner from Wolf0

[adaseb]

No I stopped using Lyra. It was profitable for many the first 2 hours and then the difficulty jumped and the price crashed on the excahnges.

All that mining for nothing.

[Atomicat]

hi ...if anyone can give some advice, it would be appreciated

I have 3x290's getting about 6.3mhz each... running sgminer 5  , using catalyst 14.7 r3 driver, mining algo x11....no other settings than X 64 w64.

Can I be getting better speeds using 14.6 drivers...and or other settings ie mem clock etc

thanks

Nope and nope but you can crank your clocks up until they squeak.  I've found power limit at about 1150/1500, then x11 throttles the core clock down.  Unfortunately it's a matter of power, not temperature, so cooling isn't the thing at that point. 

[deznuts]

Any suggestions for my 290x Neoscrypt settings? Not sure what I am doing wrong to get such crap results. Also how are my 7970/7950 speeds? Running sgminer 5.1.0-dev. Maybe I am using a crap bin or neoscrypt.cl?

290x = 291kh/s (1100mhz core / 1450mhz memory)
--thread-concurrency 8192 -I 13 -g 2 --worksize 96

7970 = 322kh/s (1100mhz core / 1600mhz memory)
7950 = 272kh/s (1000mhz core / 1500mhz memory)
--thread-concurrency 8192 --xintensity 3 -g 2 --worksize 64

I seem to get great results if using xI of 3 or 2 without using TC and a worksize of 64, but I get constant HW errors. As soon as I add TC then no more HW errors, but speeds drop hard.

[deznuts]

Any suggestions for my 290x Neoscrypt settings? Not sure what I am doing wrong to get such crap results. Also how are my 7970/7950 speeds? Running sgminer 5.1.0-dev. Maybe I am using a crap bin or neoscrypt.cl?

290x = 291kh/s (1100mhz core / 1450mhz memory)
--thread-concurrency 8192 -I 13 -g 2 --worksize 96

7970 = 322kh/s (1100mhz core / 1600mhz memory)
7950 = 272kh/s (1000mhz core / 1500mhz memory)
--thread-concurrency 8192 --xintensity 3 -g 2 --worksize 64

I seem to get great results if using xI of 3 or 2 without using TC and a worksize of 64, but I get constant HW errors. As soon as I add TC then no more HW errors, but speeds drop hard.

That's pretty good for the stock miner.

Really? 7970 outpacing the 290x. Sucks for me at least it seems that Neoscrypt is dying off in terms of profitability so hopefully x11 or x13 go back up.

[deznuts]

Any suggestions for my 290x Neoscrypt settings? Not sure what I am doing wrong to get such crap results. Also how are my 7970/7950 speeds? Running sgminer 5.1.0-dev. Maybe I am using a crap bin or neoscrypt.cl?

290x = 291kh/s (1100mhz core / 1450mhz memory)
--thread-concurrency 8192 -I 13 -g 2 --worksize 96

7970 = 322kh/s (1100mhz core / 1600mhz memory)
7950 = 272kh/s (1000mhz core / 1500mhz memory)
--thread-concurrency 8192 --xintensity 3 -g 2 --worksize 64

I seem to get great results if using xI of 3 or 2 without using TC and a worksize of 64, but I get constant HW errors. As soon as I add TC then no more HW errors, but speeds drop hard.

That's pretty good for the stock miner.

Really? 7970 outpacing the 290x. Sucks for me at least it seems that Neoscrypt is dying off in terms of profitability so hopefully x11 or x13 go back up.

290X can get a little higher, but not much more than the 7970.

Any suggestions on settings?

[deznuts]

Any suggestions for my 290x Neoscrypt settings? Not sure what I am doing wrong to get such crap results. Also how are my 7970/7950 speeds? Running sgminer 5.1.0-dev. Maybe I am using a crap bin or neoscrypt.cl?

290x = 291kh/s (1100mhz core / 1450mhz memory)
--thread-concurrency 8192 -I 13 -g 2 --worksize 96

7970 = 322kh/s (1100mhz core / 1600mhz memory)
7950 = 272kh/s (1000mhz core / 1500mhz memory)
--thread-concurrency 8192 --xintensity 3 -g 2 --worksize 64

I seem to get great results if using xI of 3 or 2 without using TC and a worksize of 64, but I get constant HW errors. As soon as I add TC then no more HW errors, but speeds drop hard.

That's pretty good for the stock miner.

Really? 7970 outpacing the 290x. Sucks for me at least it seems that Neoscrypt is dying off in terms of profitability so hopefully x11 or x13 go back up.

290X can get a little higher, but not much more than the 7970.

Any suggestions on settings?

I don't use that one, but a 1500 memclock would probably help.

I will give that a try. Do you have a link to the newest neoscrypt.cl you released? Is it the same one implemented into 5.1.0-dev?

Edit: 1500 memory hit 302k. Btw I am running sgminer-5.1-dev-2014-11-13-win32 any reason to get a newer one?