Author

Topic: [ANN] sgminer v5 - optimized X11/X13/NeoScrypt/Lyra2RE/etc. kernel-switch miner - page 155. (Read 877859 times)

member
Activity: 81
Merit: 1002
It was only the wind.
Hi,
i use PIMP- 1.5.7 sgminer-multialgo
can somebody help me with config for 290x for x11. i have 5.2mh till now
290- 5mh
280x-4.2mh
Thank in advance  Wink Smiley

Seems decent for stock SG5.
hero member
Activity: 658
Merit: 500
I may start up the little thing I was doing, compiling SG5 for Win x64 every week or so again. Seems like people could use it.

Why do these miner's need compiling every week ?
is it because they are changed regularly in some way on git hub?

Usually, developers change things. That's how new features get added and stuff. Tongue

Anyway, I did it more for people who couldn't compile themselves but still wanted the absolute latest in terms of speed improvements and features.

Yeah right nice, I don't know how to compile.
So if someone compiles a miner on their own machine is the resulting miner then tuned more to that machine than others ?
shouldn't be
the only problem with not doing it yourself is the possibility of getting a virus either intentionally added or sneaking in from the builders computer on one of the dll's
  "shouldn't be"
But miners with different drivers that makes a difference yeah?
what drivers is your sg 5-mod compiled with?

getting a virus yeah well thats why ya dont use an .exe of someone's who you don't know :-)
i am using 14.6 drivers
legendary
Activity: 1050
Merit: 1293
Huh?
getting a virus yeah well thats why ya dont use an .exe of someone's who you don't know :-)

It doesn't especially have to be a .exe .... just be careful..
member
Activity: 81
Merit: 1002
It was only the wind.
I have three rig's all pointing to the Nicehash multi port's and all pointing to the same user
the miner's on all 3 rig's at the same time are restarting  about 4 of 5 times in 24 hours
 
anyone know why does Nicehash cause this ?

cheers

More than likely, the offers to buy hashrate are changing in favor of a different algorithm?


If you mean my miner is also switching algo ?
I have seen my miner switch algo without restarting !
         

Oh, you mean the actual rig is rebooting? I doubt that has anything to do with the pool...
No the rig is not rebooting
sgminer is restarting which does NOT happen when sgminer switches algo



Might be a bug in SG5? Ask about it on their github.
hero member
Activity: 528
Merit: 500
I may start up the little thing I was doing, compiling SG5 for Win x64 every week or so again. Seems like people could use it.

Why do these miner's need compiling every week ?
is it because they are changed regularly in some way on git hub?

Usually, developers change things. That's how new features get added and stuff. Tongue

Anyway, I did it more for people who couldn't compile themselves but still wanted the absolute latest in terms of speed improvements and features.

Yeah right nice, I don't know how to compile.
So if someone compiles a miner on their own machine is the resulting miner then tuned more to that machine than others ?
shouldn't be
the only problem with not doing it yourself is the possibility of getting a virus either intentionally added or sneaking in from the builders computer on one of the dll's
  "shouldn't be"
But miners with different drivers that makes a difference yeah?
what drivers is your sg 5-mod compiled with?

getting a virus yeah well thats why ya dont use an .exe of someone's who you don't know :-)
hero member
Activity: 658
Merit: 500
I may start up the little thing I was doing, compiling SG5 for Win x64 every week or so again. Seems like people could use it.

Why do these miner's need compiling every week ?
is it because they are changed regularly in some way on git hub?

Usually, developers change things. That's how new features get added and stuff. Tongue

Anyway, I did it more for people who couldn't compile themselves but still wanted the absolute latest in terms of speed improvements and features.

Yeah right nice, I don't know how to compile.
So if someone compiles a miner on their own machine is the resulting miner then tuned more to that machine than others ?
shouldn't be
the only problem with not doing it yourself is the possibility of getting a virus either intentionally added or sneaking in from the builders computer on one of the dll's
member
Activity: 81
Merit: 1002
It was only the wind.
I have three rig's all pointing to the Nicehash multi port's and all pointing to the same user
the miner's on all 3 rig's at the same time are restarting  about 4 of 5 times in 24 hours
 
anyone know why does Nicehash cause this ?

cheers

More than likely, the offers to buy hashrate are changing in favor of a different algorithm?


If you mean my miner is also switching algo ?
I have seen my miner switch algo without restarting !
         

Oh, you mean the actual rig is rebooting? I doubt that has anything to do with the pool...
hero member
Activity: 528
Merit: 500
I may start up the little thing I was doing, compiling SG5 for Win x64 every week or so again. Seems like people could use it.

Why do these miner's need compiling every week ?
is it because they are changed regularly in some way on git hub?

Usually, developers change things. That's how new features get added and stuff. Tongue

Anyway, I did it more for people who couldn't compile themselves but still wanted the absolute latest in terms of speed improvements and features.

Yeah right nice, I don't know how to compile.
So if someone compiles a miner on their own machine is the resulting miner then tuned more to that machine than others ?
hero member
Activity: 658
Merit: 500
Do git clone --recursive https://github.com/sgminer-dev/sgminer.git to get sgminer instead of downloading it the way you are, or use git submodule init and git submodule update before configuring
still not working Sad
still shows you dont have jasson... in mingw shell, goto your sgminer dir and enter git submodule update --init and see if it downloads it if not then there is a problem with git
i have to open a git shell separately (not the one i use for mingw) then use git submodule update --init, then go back to mingw and do the rest from autoreconf -fvi on
member
Activity: 81
Merit: 1002
It was only the wind.
I have three rig's all pointing to the Nicehash multi port's and all pointing to the same user
the miner's on all 3 rig's at the same time are restarting  about 4 of 5 times in 24 hours
 
anyone know why does Nicehash cause this ?

cheers

More than likely, the offers to buy hashrate are changing in favor of a different algorithm?
full member
Activity: 125
Merit: 100
Wolf0  how compile dll's?
full member
Activity: 125
Merit: 100
How do I compile this on windows 7 with mingw?

github directions gives me:

Code:
sgminer 5.0.0
------------------------------------------------------------------------


Configuration Options Summary:

  Use git version......: no
  libcurl(GBT+getwork).: Enabled: -LC:/MinGW/lib -lcurl -lcurldll
  curses.TUI...........: FOUND: -lpdcurses
  OpenCL...............: FOUND. GPU mining support enabled
  ADL..................: SDK found, GPU monitoring support enabled

Compilation............: make (or gmake)
  CPPFLAGS.............:
  CFLAGS...............: -O2 -msse2
  LDFLAGS..............:
  LDADD................:  -LC:/MinGW/lib -lcurl -lcurldll   submodules/jansson/s
rc/.libs/libjansson.a -lpthread -lOpenCL   -lws2_32 -lm

Installation...........: make install (as root if needed, with 'su' or 'sudo')
  prefix...............: /usr/local

then I do make and not happy:

Code:
make  all-recursive
make[1]: Entering directory `/home/um/sgminer-master'
Making all in lib
make[2]: Entering directory `/home/um/sgminer-master/lib'
  GEN    arg-nonnull.h
  GEN    c++defs.h
  GEN    warn-on-use.h
  GEN    signal.h
  GEN    string.h
make  all-recursive
make[3]: Entering directory `/home/um/sgminer-master/lib'
make[4]: Entering directory `/home/um/sgminer-master/lib'
  CC     dummy.o
  CC     memmem.o
  CC     sigaction.o
  CC     sigprocmask.o
  AR     libgnu.a
make[4]: Leaving directory `/home/um/sgminer-master/lib'
make[3]: Leaving directory `/home/um/sgminer-master/lib'
make[2]: Leaving directory `/home/um/sgminer-master/lib'
Making all in submodules
make[2]: Entering directory `/home/um/sgminer-master/submodules'
Making all in jansson
make[3]: Entering directory `/home/um/sgminer-master/submodules/jansson'
make[3]: *** No rule to make target `all'.  Stop.
make[3]: Leaving directory `/home/um/sgminer-master/submodules/jansson'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/um/sgminer-master/submodules'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/um/sgminer-master'
make: *** [all] Error 2

win x64 version compiled by Visual Studio https://www.dropbox.com/s/hicczty4rhfr0o7/sgminer%20win%20x64.rar?dl=0
hero member
Activity: 528
Merit: 500
I may start up the little thing I was doing, compiling SG5 for Win x64 every week or so again. Seems like people could use it.

Why do these miner's need compiling every week ?
is it because they are changed regularly in some way on git hub?
newbie
Activity: 28
Merit: 0
Do git clone --recursive https://github.com/sgminer-dev/sgminer.git to get sgminer instead of downloading it the way you are, or use git submodule init and git submodule update before configuring



still not working Sad

Code:
------------------------------------------------------------------------
sgminer 5.0.0
------------------------------------------------------------------------


Configuration Options Summary:

  Use git version......: yes
  libcurl(GBT+getwork).: Enabled: -LC:/MinGW/lib -lcurl -lcurldll
  curses.TUI...........: FOUND: -lpdcurses
  OpenCL...............: FOUND. GPU mining support enabled
  ADL..................: SDK found, GPU monitoring support enabled

Compilation............: make (or gmake)
  CPPFLAGS.............:
  CFLAGS...............: -O2 -msse2
  LDFLAGS..............:
  LDADD................:  -LC:/MinGW/lib -lcurl -lcurldll   submodules/jansson/s
rc/.libs/libjansson.a -lpthread -lOpenCL   -lws2_32 -lm

Installation...........: make install (as root if needed, with 'su' or 'sudo')
  prefix...............: /usr/local

then:

Code:
$ make
make  all-recursive
make[1]: Entering directory `/home/um/sgminer'
Making all in lib
make[2]: Entering directory `/home/um/sgminer/lib'
  GEN    arg-nonnull.h
  GEN    c++defs.h
  GEN    warn-on-use.h
  GEN    signal.h
  GEN    string.h
make  all-recursive
make[3]: Entering directory `/home/um/sgminer/lib'
make[4]: Entering directory `/home/um/sgminer/lib'
  CC     dummy.o
  CC     memmem.o
  CC     sigaction.o
  CC     sigprocmask.o
  AR     libgnu.a
make[4]: Leaving directory `/home/um/sgminer/lib'
make[3]: Leaving directory `/home/um/sgminer/lib'
make[2]: Leaving directory `/home/um/sgminer/lib'
Making all in submodules
make[2]: Entering directory `/home/um/sgminer/submodules'
Making all in jansson
make[3]: Entering directory `/home/um/sgminer/submodules/jansson'
make[3]: *** No rule to make target `all'.  Stop.
make[3]: Leaving directory `/home/um/sgminer/submodules/jansson'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/um/sgminer/submodules'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/um/sgminer'
make: *** [all] Error 2
member
Activity: 81
Merit: 1002
It was only the wind.
does
 "failover-switch-delay" : "300",
or anything else apart from my password code have any effect on the time it takes to switch algo ?

cheers 

No.
hero member
Activity: 658
Merit: 500
How do I compile this on windows 7 with mingw?

github directions gives me:

Code:
sgminer 5.0.0
------------------------------------------------------------------------


Configuration Options Summary:

  Use git version......: no
  libcurl(GBT+getwork).: Enabled: -LC:/MinGW/lib -lcurl -lcurldll
  curses.TUI...........: FOUND: -lpdcurses
  OpenCL...............: FOUND. GPU mining support enabled
  ADL..................: SDK found, GPU monitoring support enabled

Compilation............: make (or gmake)
  CPPFLAGS.............:
  CFLAGS...............: -O2 -msse2
  LDFLAGS..............:
  LDADD................:  -LC:/MinGW/lib -lcurl -lcurldll   submodules/jansson/s
rc/.libs/libjansson.a -lpthread -lOpenCL   -lws2_32 -lm

Installation...........: make install (as root if needed, with 'su' or 'sudo')
  prefix...............: /usr/local

then I do make and not happy:

Code:
make  all-recursive
make[1]: Entering directory `/home/um/sgminer-master'
Making all in lib
make[2]: Entering directory `/home/um/sgminer-master/lib'
  GEN    arg-nonnull.h
  GEN    c++defs.h
  GEN    warn-on-use.h
  GEN    signal.h
  GEN    string.h
make  all-recursive
make[3]: Entering directory `/home/um/sgminer-master/lib'
make[4]: Entering directory `/home/um/sgminer-master/lib'
  CC     dummy.o
  CC     memmem.o
  CC     sigaction.o
  CC     sigprocmask.o
  AR     libgnu.a
make[4]: Leaving directory `/home/um/sgminer-master/lib'
make[3]: Leaving directory `/home/um/sgminer-master/lib'
make[2]: Leaving directory `/home/um/sgminer-master/lib'
Making all in submodules
make[2]: Entering directory `/home/um/sgminer-master/submodules'
Making all in jansson
make[3]: Entering directory `/home/um/sgminer-master/submodules/jansson'
make[3]: *** No rule to make target `all'.  Stop.
make[3]: Leaving directory `/home/um/sgminer-master/submodules/jansson'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/um/sgminer-master/submodules'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/um/sgminer-master'
make: *** [all] Error 2

Do git clone --recursive https://github.com/sgminer-dev/sgminer.git to get sgminer instead of downloading it the way you are, or use git submodule init and git submodule update before configuring
newbie
Activity: 28
Merit: 0
How do I compile this on windows 7 with mingw?

github directions gives me:

Code:
sgminer 5.0.0
------------------------------------------------------------------------


Configuration Options Summary:

  Use git version......: no
  libcurl(GBT+getwork).: Enabled: -LC:/MinGW/lib -lcurl -lcurldll
  curses.TUI...........: FOUND: -lpdcurses
  OpenCL...............: FOUND. GPU mining support enabled
  ADL..................: SDK found, GPU monitoring support enabled

Compilation............: make (or gmake)
  CPPFLAGS.............:
  CFLAGS...............: -O2 -msse2
  LDFLAGS..............:
  LDADD................:  -LC:/MinGW/lib -lcurl -lcurldll   submodules/jansson/s
rc/.libs/libjansson.a -lpthread -lOpenCL   -lws2_32 -lm

Installation...........: make install (as root if needed, with 'su' or 'sudo')
  prefix...............: /usr/local

then I do make and not happy:

Code:
make  all-recursive
make[1]: Entering directory `/home/um/sgminer-master'
Making all in lib
make[2]: Entering directory `/home/um/sgminer-master/lib'
  GEN    arg-nonnull.h
  GEN    c++defs.h
  GEN    warn-on-use.h
  GEN    signal.h
  GEN    string.h
make  all-recursive
make[3]: Entering directory `/home/um/sgminer-master/lib'
make[4]: Entering directory `/home/um/sgminer-master/lib'
  CC     dummy.o
  CC     memmem.o
  CC     sigaction.o
  CC     sigprocmask.o
  AR     libgnu.a
make[4]: Leaving directory `/home/um/sgminer-master/lib'
make[3]: Leaving directory `/home/um/sgminer-master/lib'
make[2]: Leaving directory `/home/um/sgminer-master/lib'
Making all in submodules
make[2]: Entering directory `/home/um/sgminer-master/submodules'
Making all in jansson
make[3]: Entering directory `/home/um/sgminer-master/submodules/jansson'
make[3]: *** No rule to make target `all'.  Stop.
make[3]: Leaving directory `/home/um/sgminer-master/submodules/jansson'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/um/sgminer-master/submodules'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/um/sgminer-master'
make: *** [all] Error 2
newbie
Activity: 3
Merit: 0
Keeping an eye on this one.
legendary
Activity: 2716
Merit: 1094
Black Belt Developer
Can also confirm lost 2 MH/s total mining X11 combined with my 3x R9 270s and my 1x R9 280X on 14.9 drivers

All right, then I'm sure I fucked up my test somehow.

Did you delete the old .bin's from whatever drivers you had before, and had new ones generated for 14.9 drivers?

Of course I did. I'm gonna re-do the test now, though. 14.6 vs. 14.9 on both my X11 kernels.

Ooookay... this is odd. The hashrate changed - so it seems the driver did as well. Further, I fetched the date on fglrx each time before starting (14.6 being May 29 2014 and 14.9 being Sept 2 2014) so it DID change. As for the bin files, yes, I removed them; I double-checked. Anyway, Savage, this is what I've got, columns are GPU/clocks/mine/stock, rows are obviously GPUs.

Code:
Running driver version 14.6:
270X - 1155/1500 - 3.64 - 2.80
290X - 1045/1600 - 7.96 - 4.86
7950 - 1155/1500 - 5.03 - 4.01
280X - 1155/1500 - 5.77 - 4.54


Running driver version 14.9:
270X - 1155/1500 - 3.64 - 2.80
290X - 1045/1600 - 7.98 - 4.95
7950 - 1155/1500 - 5.03 - 4.05
280X - 1155/1500 - 5.75 - 4.60

changes are too small: probably just compiler variance.
compiling the same .cl file with the same settings may result in different hashrates (I believe a 2% range is common).
the file size changes too.
it doesn't happen with all the kernels but I'm sure it does on x11 as well as on my groestl, for example.

EDIT: so long for those fine optimizations which result in 1% improvement and you think it's good... and it's nothing instead ;-)

I don't understand your last comment. If you're saying my optimizations get 1% improvement, then you're reading the table wrong, because the third COLUMN is my kernel's hashrate, the fourth is the stock kernel's hashrate with the same GPU, driver, and clocks.

Example: On driver version 14.9, my 290X achieved a hashrate of 7.98MH/s with my kernel, and 4.95MH/s with the kernel that is on SGMiner's master branch right now. The clocks were the same for both runs, 1045/1600.

sorry, I didn't mean that.
I was just saying that to me and other developers I know, it often happened that an optimization which led to a 1% improvement, or even more, in the end turned out to be just that variance, so not an optimization at all. It probably happened to you as well.
hero member
Activity: 528
Merit: 500
I'm gonna re-do the test now, though. 14.6 vs. 14.9

Did I miss driver 14.7 being tested as not good ?
Jump to: