Search content
Sort by
Showing 20 of 20 results by stonefoz
Re: [ANN][MOON] Mooncoin: You know where it's headed! LAUNCHING 12/30 @ 1PM EST
Only thing I have confirmed is, reasons to not use multipool again. I may not have the most impressive numbers for mining, but assured none will be pointed at multipool again.
As soon as the site quits getting "accidentally" unplugged, I'm empty every scrap of pocket change, other shit coins, and it'll be silent then on.
As soon as the site quits getting "accidentally" unplugged, I'm empty every scrap of pocket change, other shit coins, and it'll be silent then on.
Re: Bitmit - Bitcoin shopping mall - Bitcoin market place - Bitcoin auction house
If BitMit is shutting down, what will happen to orders and payments that are still in escrow?
What'll happen? At least one guy is going to hold out till the bitter end. I am holding on payment in escrow, for item that hasn't been received. It's been more than 30 days. The item was held up in China post and returned to the shipper. I have received nothing and GlobalBTC still has the item. I've asked for a refund and instead have been told it's reshipped. I have no desire to wait another 30days. Refund my coins. There isn't another 30days this time.
order: 32653
tracking # RB844557973CN
17track.net
already tried adding it numerous times dude 
trust me this shit is messed up.. if you can compile it feel free to gimme advice
so far i've gotten, "well some builds may be broken"
lol
so people may want to know their screwed if they see the getting started page on the SRC pool i'm on for example
whether it says to go grab it and compile it etc
people passing around failed messy broken git code links s pretty lame !
luckily no one seems to care hahha
and someone posting misc builds proves nothing.. doesn't mean it was current from GIT
trust me this shit is messed up.. if you can compile it feel free to gimme advice
so far i've gotten, "well some builds may be broken"
lol
so people may want to know their screwed if they see the getting started page on the SRC pool i'm on for example
whether it says to go grab it and compile it etc
people passing around failed messy broken git code links s pretty lame !
luckily no one seems to care hahha
and someone posting misc builds proves nothing.. doesn't mean it was current from GIT
NO NO NO, IT IS NOT ADDED.
be nice to get uncle_bobs newest git code to work.. GCC on windows throws compiler errors. *STILL
can ANYONE get it to build ?
this is the best code base ? or should i go with the other one ?
here is my build log..
can ANYONE get it to build ?
this is the best code base ? or should i go with the other one ?
here is my build log..
Code:
$ make
make all-recursive
make[1]: Entering directory `/c/code/quarkminer'
Making all in compat
make[2]: Entering directory `/c/code/quarkminer/compat'
Making all in jansson
make[3]: Entering directory `/c/code/quarkminer/compat/jansson'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/c/code/quarkminer/compat/jansson'
make[3]: Entering directory `/c/code/quarkminer/compat'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/c/code/quarkminer/compat'
make[2]: Leaving directory `/c/code/quarkminer/compat'
make[2]: Entering directory `/c/code/quarkminer'
x86_64-w64-mingw32-gcc -std=gnu99 -DHAVE_CONFIG_H -I. -fno-strict-aliasing -I./
compat/jansson -I/c/mingw64/include -msse4.1 -O3 -MT minerd-quark.o -MD -MP -M
F .deps/minerd-quark.Tpo -c -o minerd-quark.o `test -f 'quark.c' || echo './'`qu
ark.c
quark.c: In function 'quarkhash':
quark.c:95:13: warning: assignment discards 'const' qualifier from pointer targe
t type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
mv -f .deps/minerd-quark.Tpo .deps/minerd-quark.Po
x86_64-w64-mingw32-gcc -std=gnu99 -msse4.1 -O3 -o minerd.exe minerd-cpu-miner
.o minerd-util.o minerd-sha2.o minerd-sha2-arm.o minerd-sha2-x86.o minerd-sha2-x
64.o minerd-scrypt.o minerd-scrypt-arm.o minerd-scrypt-x86.o minerd-scrypt-x64.o
minerd-quark.o minerd-grso.o -L/c/mingw64/lib -lcurl -lwldap32 -lws2_32 compat/
jansson/libjansson.a -lpthread -lws2_32
minerd-grso.o:grso.c:(.text+0x0): multiple definition of `grsoTransform'
minerd-quark.o:quark.c:(.text+0x1170): first defined here
minerd-grso.o:grso.c:(.text+0x3d0): multiple definition of `grsoOutputTransforma
tion'
minerd-quark.o:quark.c:(.text+0x7d0): first defined here
minerd-grso.o:grso.c:(.rdata+0x0): multiple definition of `grsoT7'
minerd-quark.o:quark.c:(.rdata+0x70): first defined here
minerd-grso.o:grso.c:(.rdata+0x800): multiple definition of `grsoT6'
minerd-quark.o:quark.c:(.rdata+0x870): first defined here
minerd-grso.o:grso.c:(.rdata+0x1000): multiple definition of `grsoT5'
minerd-quark.o:quark.c:(.rdata+0x1070): first defined here
minerd-grso.o:grso.c:(.rdata+0x1800): multiple definition of `grsoT4'
minerd-quark.o:quark.c:(.rdata+0x1870): first defined here
minerd-grso.o:grso.c:(.rdata+0x2000): multiple definition of `grsoT3'
minerd-quark.o:quark.c:(.rdata+0x2070): first defined here
minerd-grso.o:grso.c:(.rdata+0x2800): multiple definition of `grsoT2'
minerd-quark.o:quark.c:(.rdata+0x2870): first defined here
minerd-grso.o:grso.c:(.rdata+0x3000): multiple definition of `grsoT1'
minerd-quark.o:quark.c:(.rdata+0x3070): first defined here
minerd-grso.o:grso.c:(.rdata+0x3800): multiple definition of `grsoT0'
minerd-quark.o:quark.c:(.rdata+0x3870): first defined here
collect2.exe: error: ld returned 1 exit status
make[2]: *** [minerd.exe] Error 1
make[2]: Leaving directory `/c/code/quarkminer'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/c/code/quarkminer'
make: *** [all] Error 2
make all-recursive
make[1]: Entering directory `/c/code/quarkminer'
Making all in compat
make[2]: Entering directory `/c/code/quarkminer/compat'
Making all in jansson
make[3]: Entering directory `/c/code/quarkminer/compat/jansson'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/c/code/quarkminer/compat/jansson'
make[3]: Entering directory `/c/code/quarkminer/compat'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/c/code/quarkminer/compat'
make[2]: Leaving directory `/c/code/quarkminer/compat'
make[2]: Entering directory `/c/code/quarkminer'
x86_64-w64-mingw32-gcc -std=gnu99 -DHAVE_CONFIG_H -I. -fno-strict-aliasing -I./
compat/jansson -I/c/mingw64/include -msse4.1 -O3 -MT minerd-quark.o -MD -MP -M
F .deps/minerd-quark.Tpo -c -o minerd-quark.o `test -f 'quark.c' || echo './'`qu
ark.c
quark.c: In function 'quarkhash':
quark.c:95:13: warning: assignment discards 'const' qualifier from pointer targe
t type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
mv -f .deps/minerd-quark.Tpo .deps/minerd-quark.Po
x86_64-w64-mingw32-gcc -std=gnu99 -msse4.1 -O3 -o minerd.exe minerd-cpu-miner
.o minerd-util.o minerd-sha2.o minerd-sha2-arm.o minerd-sha2-x86.o minerd-sha2-x
64.o minerd-scrypt.o minerd-scrypt-arm.o minerd-scrypt-x86.o minerd-scrypt-x64.o
minerd-quark.o minerd-grso.o -L/c/mingw64/lib -lcurl -lwldap32 -lws2_32 compat/
jansson/libjansson.a -lpthread -lws2_32
minerd-grso.o:grso.c:(.text+0x0): multiple definition of `grsoTransform'
minerd-quark.o:quark.c:(.text+0x1170): first defined here
minerd-grso.o:grso.c:(.text+0x3d0): multiple definition of `grsoOutputTransforma
tion'
minerd-quark.o:quark.c:(.text+0x7d0): first defined here
minerd-grso.o:grso.c:(.rdata+0x0): multiple definition of `grsoT7'
minerd-quark.o:quark.c:(.rdata+0x70): first defined here
minerd-grso.o:grso.c:(.rdata+0x800): multiple definition of `grsoT6'
minerd-quark.o:quark.c:(.rdata+0x870): first defined here
minerd-grso.o:grso.c:(.rdata+0x1000): multiple definition of `grsoT5'
minerd-quark.o:quark.c:(.rdata+0x1070): first defined here
minerd-grso.o:grso.c:(.rdata+0x1800): multiple definition of `grsoT4'
minerd-quark.o:quark.c:(.rdata+0x1870): first defined here
minerd-grso.o:grso.c:(.rdata+0x2000): multiple definition of `grsoT3'
minerd-quark.o:quark.c:(.rdata+0x2070): first defined here
minerd-grso.o:grso.c:(.rdata+0x2800): multiple definition of `grsoT2'
minerd-quark.o:quark.c:(.rdata+0x2870): first defined here
minerd-grso.o:grso.c:(.rdata+0x3000): multiple definition of `grsoT1'
minerd-quark.o:quark.c:(.rdata+0x3070): first defined here
minerd-grso.o:grso.c:(.rdata+0x3800): multiple definition of `grsoT0'
minerd-quark.o:quark.c:(.rdata+0x3870): first defined here
collect2.exe: error: ld returned 1 exit status
make[2]: *** [minerd.exe] Error 1
make[2]: Leaving directory `/c/code/quarkminer'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/c/code/quarkminer'
make: *** [all] Error 2
Makefile.am must have "grso.c" added to "minerd_SOURCES", it shouldn't be there. At least some of the functions can get in-lined and confuse the compiler less, if all compiled at once.
quark.c just #includes "bunch of .c file". it shouldn't be also made separately. Anyway, you're log shows that it is brought in from #includes and compiled separate.
Edit Makefile.am, run autogen.sh, "make distclean", configure with CFLAGS, and make.
I know someone else had posted windows builds. I don't have a working system to test it, would require setting up probably cygwin... I can try it all out in a vm, but i wouldn't optimize around it.
Repost. Updated
AMD Bulldozer optimized client Win64bit and maybe some intels
---===---===---===---
built from StoneFoz version1 Which doubled speed and beyond
v2 was having many issues (+reject, +orphan for me) , bin below is version 1
8150 Stock 8 cores = .8~1.1 mhash
8350 Stock 8 cores = 1~?? mhash
4300 Stock 4 cores = .46+ mhash=+
Bulldozer 1 (more compatable) and Bulldozer gen 2 (more specialized)
https://sourceforge.net/projects/philosopherstone/files/QRK/
Tips appreciated: QRK: QQVzchEu7aqAfc71NZa1TYi3toih6abCtk
Re-posting because this is not AMD bulldozer only, and may in fact work on the newer intels as well.
this is not the uber optimized client, will post when over 2mhash per chip
AMD Bulldozer optimized client Win64bit and maybe some intels
---===---===---===---
built from StoneFoz version1 Which doubled speed and beyond
v2 was having many issues (+reject, +orphan for me) , bin below is version 1
8150 Stock 8 cores = .8~1.1 mhash
8350 Stock 8 cores = 1~?? mhash
4300 Stock 4 cores = .46+ mhash=+
Bulldozer 1 (more compatable) and Bulldozer gen 2 (more specialized)
https://sourceforge.net/projects/philosopherstone/files/QRK/
Tips appreciated: QRK: QQVzchEu7aqAfc71NZa1TYi3toih6abCtk
Re-posting because this is not AMD bulldozer only, and may in fact work on the newer intels as well.
this is not the uber optimized client, will post when over 2mhash per chip
and i'm telling you AGAIN it crashes on my Intel CPU (both versions in the archive)
i downloaded it before and tried them all and i re-downloaded just now and tried them all..
arguing doesn't make code run lol
Intel Core 2 Duo E7500 = fail / crash on start up - win 7 x64
and yeah i checked and these are 64bit builds not x86
and your welcome for the constructive feedback and time and effort i took to test this everyone
edit:
I'd love to know how that guy is compiling code from GitHub.. all its giving me is compiler errors with mingw on windows
i can get various previous version of the code to run just fine..
i often see "get the tarball" but how am i suppose to find that ?
all i can see on the github page is the button that says download zip or that other page with the .zip + targz
and that can't be the tarball because i see these devs constantly telling people asking for help compiling it code to not use it and use the tarball
when autogen.sh fails etc.. so obviously the tarball should have more files inside the archive in it so you don't have to run that command right ?
this quark miner stuff is severe pain in the ass for a noob to come along and get the newest version and compile.
these miners should have dedicated topic or do they already ?
bottom line: I'm figuring it all out on my own anyway, so whatever keep scrolling guys lol
started in on linux and c/c++ well over a decade ago and its sucks balls i can't use VS as an ide
so yes i am a noob but no i am not.. i may start a new thread soon with a tutorial on building this on windows for people..
Sorry, I'm not quite the wizard with autotools. Anyway, compile it on either linux, or someone has been successful with mingw or cygwin. Autotools doesn't do MSVS. SO HERE:
git clone https://github.com/uncle-bob/quarkcoin-cpuminer.git
cd quarkcoin-cpuminer
sh autogen.sh
./configure CFLAGS="-msse2"
make
-msse2 is not optional, should be built into the build scripts. However, I've avoided getting good with autotools this long, might as well not start now. Really anyone have a simple examples for autotools? They seem to all turn into a huge pita quickly. Step two might be cmake or anything else.
really though, the code at:
http://stonefoz.myfastmail.com/
is probably the best, first release where fast is first.
I've been monkeying around with stuff on github, should be faster later, just not anytime soon. Rewriting large bits and it's going to be broken some times.
latest optimized version cpu miner for quark with sse4 support (win64).
(compiled from source https://github.com/uncle-bob/quarkcoin-cpuminer (without CHEAT option))
http://rghost.ru/48483424
(compiled from source https://github.com/uncle-bob/quarkcoin-cpuminer (without CHEAT option))
http://rghost.ru/48483424
Thanks, any chance of an AVX version (if there is any speed boost)?
AVX? likely not any time soon. The code for both SSE4 and AVX requires a expensive startup and finish, just for one round. It's currently slower. The default is an assembly routine wrote by the original creators for the groestl hash.
The largest problem now is actually size. We're swapping between 6 different things all at once, all the time. Small changes in loop sizes make 30% differences in speed.
Out of the six; skein bmw and jh are already so much faster that it's a wast of time to improve them. Smaller however it important. It's slow to keep track of more stuff. Those three combined only use around 15% of the cpu, combined.
Next step personally is to shrink everything some more. New features should get worked in after that.
latest optimized version cpu miner for quark with sse4 support (win64).
(compiled from source https://github.com/uncle-bob/quarkcoin-cpuminer (without CHEAT option))
http://rghost.ru/48483424
This miner is a great for Intel processor. I have ~ 150KHs\core( was 115KHs\core) on my i5 3330.(compiled from source https://github.com/uncle-bob/quarkcoin-cpuminer (without CHEAT option))
http://rghost.ru/48483424
And for AMD processor did not notice much of a difference.
Can someone help me out with some test cases? I have three different generations of AMD chips, no Intel. While there is code that successfully uses sse4, I personally do not see a improvement with what I have. Intel may be a different story? The largest problem with increasing the speed, with what I have to test, is size. There is much code and initialization data. At any rate, I for the most part am modifying code originally designed to work fast on considerably larger data. The SSE4 code does a expensive startup and finish, just to do one round. The original post may easily be faster until that is worked on. It's still really close, but is faster.
Anyone that feel like being a guanine pig, run the "makeprof.sh" script and send me the "a.txt" that it produces. It'll just time the hash function and list the cpu used. It could would be greatly appreciated.
Oh, and the CHEAT options is disabled by default, it's a great boost for some old processors that I should just retire. Not so good most of the time.
it's the same, there is a binary posted about 3 pages back that someone was nice enough to make. If you feel adventures the source has been moved to github
I can upload a binary as well if there's interest.
That would be great, I would like to see it tested on something not AMD first. There is a "makeprofile.sh" script. It now has enough warnings that I worry it may have issues if not tested. Looks good right now, but the goal is fast, not necessarily good. Anyway, if the middle two lines match anything else the script prints out, at least two hashes where done correctly....
Oh, and there is a new option.
./configure CFLAGS="-msse2 -O3 -DCHEAT"
needs testing but the idea is that it's faster to just try a new nonce that run groestl twice. Anytime that section is found to be needed ran, it just give up. Half of the hashes end up being garbage. But, it now does more than twice the speed, for a net gain. EXPERIMENTAL, need to be ran to see if actually improves payouts as it may be losing shares. Still runs that section when required, but never twice.
it's the same, there is a binary posted about 3 pages back that someone was nice enough to make. If you feel adventures the source has been moved to github.
Compared to the original miner though, it is about 85% faster, uses SSE2 along with ASM for two of the rounds.
Compared to the original miner though, it is about 85% faster, uses SSE2 along with ASM for two of the rounds.
Finally put my code up on github.
https://github.com/uncle-bob/quarkcoin-cpuminer
I'm looking for suggestions or ideas. Groestl-Hash seem to be the deal breaker right now. It's taking up as much time as all other 5 hashes combined. Any speed up for Groestl would be a win. Currently the V1 release confuses the compiler slightly less and is a smidgen faster. However I think this code is currently the best option for speeding up beyond that. It's still around twice as fast as the default miner.
Added bonus, almost everything for quark now fits a single function. While it won't fit on a GPU until the code size is reduced and memory is shrunk, it's just yet. Consider this my last update for cpuminer.
I wrote this cause I'm greedy, and so I leave my tipjar.
BTC: 1DaSUSqcr13G4QJYamsecW6yHh95QTT39R
QRK: QQRNpg7aGHcvgEFvXEk1DoCtLydboVsAzf
https://github.com/uncle-bob/quarkcoin-cpuminer
I'm looking for suggestions or ideas. Groestl-Hash seem to be the deal breaker right now. It's taking up as much time as all other 5 hashes combined. Any speed up for Groestl would be a win. Currently the V1 release confuses the compiler slightly less and is a smidgen faster. However I think this code is currently the best option for speeding up beyond that. It's still around twice as fast as the default miner.
Added bonus, almost everything for quark now fits a single function. While it won't fit on a GPU until the code size is reduced and memory is shrunk, it's just yet. Consider this my last update for cpuminer.
I wrote this cause I'm greedy, and so I leave my tipjar.
BTC: 1DaSUSqcr13G4QJYamsecW6yHh95QTT39R
QRK: QQRNpg7aGHcvgEFvXEk1DoCtLydboVsAzf
from what i can see, cpu miner takes dual quad xeon l5420 from 290000 to 320000 so a reasonable improvement over the wallet but not a massive amount on ubuntu 64tbit
And the improved version posted a page or two ago takes it to 600 kH/s. I can vouch for that figure personally, being the proud owner of one of those machines.
Matthew:out
Hi,
Do you mean this one
https://github.com/Neisklar/quarkcoin-cpuminer
built with this
CFLAGS="-O3 -Wall -msse2" ./configure ?
if not please can you print full command to config with
i'm seeing 41000 per core? so x 8 about 320 000kh?
Dual quad l5420 ? are you sure you are getting 600 000?
that's the one i am using?
also is your machine windows 64 bit or ubuntu?
nope, the only one that needs sse2 is
http://stonefoz.myfastmail.com/cpuminer-quark2.zip
I replaced two of the slowest parts with asm and sse2 instructions, doubles the hash rate.
MUST BE COMPILED WITH
CFLAGS="-sse2"
thanks so if i download this one
http://stonefoz.myfastmail.com/cpuminer-quark2.zip
i just compile with this even for 64 bit?
CFLAGS="-sse2" ./configure
that is the only thing i put on that command line?
Well, "-O3" doesn't hurt.... is a bit faster but I'd check the "makeprofile.sh" script. Does a simple test to make sure it's producing mostly accurate result.
I haven't tested it on Intel, so the compiler might choke if pushed too far.
And so far it's 64bit only. 32bit doesn't have much room to improve speed, keep your older machines running something else.
from what i can see, cpu miner takes dual quad xeon l5420 from 290000 to 320000 so a reasonable improvement over the wallet but not a massive amount on ubuntu 64tbit
And the improved version posted a page or two ago takes it to 600 kH/s. I can vouch for that figure personally, being the proud owner of one of those machines.
Matthew:out
Hi,
Do you mean this one
https://github.com/Neisklar/quarkcoin-cpuminer
built with this
CFLAGS="-O3 -Wall -msse2" ./configure ?
i'm seeing 41000 per core? so x 8 about 320 000kh?
Dual quad l5420 ? are you sure you are getting 600 000?
that's the one i am using?
also is your machine windows 64 bit or ubuntu?
nope, the only one that needs sse2 is
http://stonefoz.myfastmail.com/cpuminer-quark2.zip
I replaced two of the slowest parts with asm and sse2 instructions, doubles the hash rate.
MUST BE COMPILED WITH
CFLAGS="-sse2"
More hideous speed hacks. While not quite as impressive as my first release, I'm cleaning up the code so we eventually get a proper quark-hash function.
Currently it does vast amounts of unnecessary work when it only needs to run on one size, one thing, more blocks.
http://stonefoz.myfastmail.com/cpuminer-quark2.zip
At least on my machine.
Per core, "stock" 70/Khs, V1 107/KHs, this is V2 at 115/KHs
I wrote this cause I'm greedy, and so I leave my tip jar
BTC:1DaSUSqcr13G4QJYamsecW6yHh95QTT39R
LTC:LcsdTfxZhs3e1vx9WmrwbMiE7uTtDqjh1g
QRK:QQRNpg7aGHcvgEFvXEk1DoCtLydboVsAzf
Currently it does vast amounts of unnecessary work when it only needs to run on one size, one thing, more blocks.
http://stonefoz.myfastmail.com/cpuminer-quark2.zip
At least on my machine.
Per core, "stock" 70/Khs, V1 107/KHs, this is V2 at 115/KHs
I wrote this cause I'm greedy, and so I leave my tip jar
BTC:1DaSUSqcr13G4QJYamsecW6yHh95QTT39R
LTC:LcsdTfxZhs3e1vx9WmrwbMiE7uTtDqjh1g
QRK:QQRNpg7aGHcvgEFvXEk1DoCtLydboVsAzf
Code:
make[2]: Entering directory `/root/AMDquark/cpuminer-quark'
gcc -std=gnu99 -msse2 -pthread -o minerd minerd-cpu-miner.o minerd-util.o minerd-sha2.o minerd-sha2-arm.o minerd-sha2-x86.o minerd-sha2-x64.o minerd-scrypt.o minerd-scrypt-arm.o minerd-scrypt-x86.o minerd-scrypt-x64.o minerd-quark.o minerd-grso.o -L/usr/lib/x86_64-linux-gnu -lcurl -Wl,-Bsymbolic-functions -Wl,-z,relro compat/jansson/libjansson.a -lpthread
minerd-grso.o: In function `grsoTransform':
grso.c:(.text+0xd2): undefined reference to `grsoQ1024ASM'
grso.c:(.text+0xe1): undefined reference to `grsoP1024ASM'
minerd-grso.o: In function `grsoOutputTransformation':
grso.c:(.text+0x1ad): undefined reference to `grsoP1024ASM'
collect2: ld returned 1 exit status
make[2]: *** [minerd] Error 1
make[2]: Leaving directory `/root/AMDquark/cpuminer-quark'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/AMDquark/cpuminer-quark'
make: *** [all] Error 2
gcc -std=gnu99 -msse2 -pthread -o minerd minerd-cpu-miner.o minerd-util.o minerd-sha2.o minerd-sha2-arm.o minerd-sha2-x86.o minerd-sha2-x64.o minerd-scrypt.o minerd-scrypt-arm.o minerd-scrypt-x86.o minerd-scrypt-x64.o minerd-quark.o minerd-grso.o -L/usr/lib/x86_64-linux-gnu -lcurl -Wl,-Bsymbolic-functions -Wl,-z,relro compat/jansson/libjansson.a -lpthread
minerd-grso.o: In function `grsoTransform':
grso.c:(.text+0xd2): undefined reference to `grsoQ1024ASM'
grso.c:(.text+0xe1): undefined reference to `grsoP1024ASM'
minerd-grso.o: In function `grsoOutputTransformation':
grso.c:(.text+0x1ad): undefined reference to `grsoP1024ASM'
collect2: ld returned 1 exit status
make[2]: *** [minerd] Error 1
make[2]: Leaving directory `/root/AMDquark/cpuminer-quark'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/AMDquark/cpuminer-quark'
make: *** [all] Error 2
appears ungooglable.
grsoQ1024ASM is inline asm, included from grso.c.
Which version of gcc are you running?
was tested on
gcc:4.6.3
distro:gentoo 64bit
cpu:amd bulldozer 64bit
It's fast, I'll post then all in one place,
the source code:
http://stonefoz.myfastmail.com/cpuminer-quark.zip
the binary: please check if it loads the right libraries. "minerd-bin" is the real thing and "minerd" is a script to set the LD_LIBRARY_PATH current directory. Who knows? you might already have libjannson installed.
http://stonefoz.myfastmail.com/cpuminer-quark-bin.zip
I wrote this cause I'm greedy, and so I leave my tipjar
BTC:1DaSUSqcr13G4QJYamsecW6yHh95QTT39R
LTC:LcsdTfxZhs3e1vx9WmrwbMiE7uTtDqjh1g
QRK:QQRNpg7aGHcvgEFvXEk1DoCtLydboVsAzf
the source code:
http://stonefoz.myfastmail.com/cpuminer-quark.zip
the binary: please check if it loads the right libraries. "minerd-bin" is the real thing and "minerd" is a script to set the LD_LIBRARY_PATH current directory. Who knows? you might already have libjannson installed.
http://stonefoz.myfastmail.com/cpuminer-quark-bin.zip
I wrote this cause I'm greedy, and so I leave my tipjar
BTC:1DaSUSqcr13G4QJYamsecW6yHh95QTT39R
LTC:LcsdTfxZhs3e1vx9WmrwbMiE7uTtDqjh1g
QRK:QQRNpg7aGHcvgEFvXEk1DoCtLydboVsAzf
I just listed what I got and have tested. cpuminer runs a almost full copy on each core, so you should have between 70-120/Khs * 8. Just a guess, you're mileage may very. More cores more faster.
[/quote]
Thanks so your .zip file contains the optimized QRK based on those CFLAGS?
[/quote]
Nope, just the code. I can upload a binary, I'll have to compile it static.. pita and all. be a while....
I've included the libraries that ldd at least lists...? should run on most 64bit platforms. cpuminer looks to expect it to be dynamic. Which is fine, but I'm not practiced at distributing binaries.
http://stonefoz.myfastmail.com/cpuminer-quark-bin.zip
What about 8 core Operton Linux 64bit?
[/quote]
I just listed what I got and have tested. cpuminer runs a almost full copy on each core, so you should have between 70-120/Khs * 8. Just a guess, you're mileage may very. More cores more faster.
The "JH" section really needs to be updated with an AVX version, which unfortunatly will just be for Haswell, Bulldozer, Piledriver and newer chips. Half of the time is spent currently in the jhF8 function which is coded for SSE2 emmintrin. AVX can more than double that speed for an estimated 25% gain again.
The "Groestl" section is optimized assembly found at the NIST competition site, has the fastest startup which is important when only hashing block headers. Sure there are faster implementations for "big" data, but it's the fastest for quick startup for one run.
Amd optimized cpuminer. probably works on Intel? but code had been targeted for amd with caches at least as bit as the old Opterons.
Must be built with CFLAGS="-msse2", tested on 64bit linux. "jh_sse2_opt32.h" has not been edited for 32bit builds and is currently broken.
4Ghz bulldozer is running 107/Khs per core. Total 428/Khs
2.4Ghz Opteron is running 78/Khs per core. Total 312/Khs.
2.8Ghz Semepron 145 is running 112/Khz per core.
Will be working on replacing sse2 with newer avx, should greatly improve the "JH" has sections along with "Groestl". Those two lost the SHA3 partially based on speed. Skien, BMW, and Blake already run screeming fast.
http://stonefoz.myfastmail.com/cpuminer-quark.zip
Must be built with CFLAGS="-msse2", tested on 64bit linux. "jh_sse2_opt32.h" has not been edited for 32bit builds and is currently broken.
4Ghz bulldozer is running 107/Khs per core. Total 428/Khs
2.4Ghz Opteron is running 78/Khs per core. Total 312/Khs.
2.8Ghz Semepron 145 is running 112/Khz per core.
Will be working on replacing sse2 with newer avx, should greatly improve the "JH" has sections along with "Groestl". Those two lost the SHA3 partially based on speed. Skien, BMW, and Blake already run screeming fast.
http://stonefoz.myfastmail.com/cpuminer-quark.zip
https://github.com/uncle-bob
for nearly a 30% improvement in hash rate
on an amd four-core 2.4 Ghz my hash rate has went from 123502 to 163519. I'm mining around 6000 QRK a day with this code. I'm hoping that with an increase in the hashrate, for at least anyone that can compile code will uptick the price on QRK.
I really don't do windows, so I'll have to leave making a new binary up to someone else.
Well, quark coin is very cpu bound and hardly optimized. I've been getting blocks a few times and hour with doing just a little bit of optimization on the client. Looks like I have to post a newbie post before getting access to anything else.
I was wishing to post a link to my github for quarkcoin, they don't look to be worth much so perhaps the price will do something if the hashrate can go up.
https://github.com/uncle-bob/quark
Check back in an hour.
I was wishing to post a link to my github for quarkcoin, they don't look to be worth much so perhaps the price will do something if the hashrate can go up.
https://github.com/uncle-bob/quark
Check back in an hour.