Quote from: bytemaster on November 14, 2013, 04:31:19 PM
Solo mining is not profitable, if you use this you should have your own mini farm.

I have 15 macs, that combined only have the expectation to earn 1 block per day.   If you solo mine right now with a high end machine you should expect one block every 2 weeks.  Of course the difficulty will rise over 2 weeks and orphans are high, so solo mining is more like one block every month+. 

I just pushed a patch to gain another 10%

https://github.com/InvictusInnovations/coyote_miner

May I have a new patched Linux binary please?

Trying hard to compile from source and now I am stuck with Boost 1.54 installation...

I am using Ubuntu 13.10 x64.

Quote from: ryen123 on November 14, 2013, 04:27:52 PM
Just curious. Anyone solo mining with this miner have managed to mined a block yet?

the same question, anyone got a block with this miner?

Quote from: bytemaster on November 14, 2013, 07:09:47 PM
Increasing memory will hurt performance, due to increased cache misses.

Weird, i thought that protoshares were supposed to be very memory heavy.  Will the 1.5 GB requirement increase as the difficulty goes up?  What would be the most ideal setup for mining protoshares then? What is more important fast RAM or RAM timings? Is a large CPU Cache important?

Thanks!

Quote from: bytemaster on November 14, 2013, 04:31:19 PM
Solo mining is not profitable, if you use this you should have your own mini farm.

I have 15 macs, that combined only have the expectation to earn 1 block per day.   If you solo mine right now with a high end machine you should expect one block every 2 weeks.  Of course the difficulty will rise over 2 weeks and orphans are high, so solo mining is more like one block every month+. 

I just pushed a patch to gain another 10%

https://github.com/InvictusInnovations/coyote_miner

Hi,
Thanks for the update and the great work. Would you mind giving some basic guidelines how to build your miner for windows.

Quote from: masterofmyself on November 14, 2013, 05:35:53 PM

Quote from: bytemaster on November 13, 2013, 06:24:42 PM
https://github.com/InvictusInnovations/coyote_miner

This miner is 4x faster than the miner I was using with my pool and might be faster than ypool.   Give it a shot.  It does not work with with my mining pool as I want to support standard pools and encourage decentralization.   

We are working on a new mining pool to work with this miner.

Enjoy!

mac version  http://the-iland.net/static/downloads/mac_gw_miner.0.1.0.tar.gz
linux version: http://the-iland.net/static/downloads/linux_gw_miner.0.1.0.tar.gz
win64 version: windows: http://the-iland.net/static/downloads/windows_gw_miner.0.1.0.zip

Honestly, I'm a noob at this, but am really excited about the opportunity to be apart of this.  I need help getting this miner to run on my Mac 10.6.8 OSX.  When I open the download, it takes me to the Terminal, and I get an "Illegal instruction" error.  Can anyone help me with this?

Do you have an old 32 bit mac?  These are 64 bit only.

Increasing memory will hurt performance, due to increased cache misses. 

Quote from: bytemaster on November 14, 2013, 04:31:19 PM
Solo mining is not profitable, if you use this you should have your own mini farm.

I have 15 macs, that combined only have the expectation to earn 1 block per day.   If you solo mine right now with a high end machine you should expect one block every 2 weeks.  Of course the difficulty will rise over 2 weeks and orphans are high, so solo mining is more like one block every month+. 

I just pushed a patch to gain another 10%

https://github.com/InvictusInnovations/coyote_miner

I git pulled and recompiled, trying it out now, seems to be a bit faster.  Can you tell me though, is it usual that this miner should use such small amount of memory? It's only using about 1.5 GB of memory, can i increase this amount? will increasing it add any benefit to mining speed?

Quote from: bytemaster on November 13, 2013, 06:24:42 PM
https://github.com/InvictusInnovations/coyote_miner

This miner is 4x faster than the miner I was using with my pool and might be faster than ypool.   Give it a shot.  It does not work with with my mining pool as I want to support standard pools and encourage decentralization.   

We are working on a new mining pool to work with this miner.

Enjoy!

mac version  http://the-iland.net/static/downloads/mac_gw_miner.0.1.0.tar.gz
linux version: http://the-iland.net/static/downloads/linux_gw_miner.0.1.0.tar.gz
win64 version: windows: http://the-iland.net/static/downloads/windows_gw_miner.0.1.0.zip

Honestly, I'm a noob at this, but am really excited about the opportunity to be apart of this.  I need help getting this miner to run on my Mac 10.6.8 OSX.  When I open the download, it takes me to the Terminal, and I get an "Illegal instruction" error.  Can anyone help me with this?

I get this message on make:

QuoteIn file included from /usr/local/include/boost/atomic/detail/platform.hpp:22:0,
                 from /usr/local/include/boost/atomic/atomic.hpp:17,
                 from /usr/local/include/boost/atomic.hpp:12,
                 from /usr/local/include/boost/thread/pthread/once_atomic.hpp:20,
                 from /usr/local/include/boost/thread/once.hpp:20,
                 from /usr/local/include/boost/thread.hpp:17,
                 from /home/ubuntu/coyote_miner_update/fc/src/thread/thread_d.hpp:4,
                 from /home/ubuntu/coyote_miner_update/fc/src/thread/thread.cpp:5:
/usr/local/include/boost/atomic/detail/gcc-atomic.hpp: In member function 'void fc::thread_d::process_tasks()':
/usr/local/include/boost/atomic/detail/gcc-atomic.hpp:1081:95: error: invalid memory model for '__atomic_exchange'
         return __atomic_exchange_n(&v_, v, atomics::detail::convert_memory_order_to_gcc(order));
                                                                                               ^
make[2]: *** [fc/CMakeFiles/fc.dir/src/thread/thread.cpp.o] Error 1
make[1]: *** [fc/CMakeFiles/fc.dir/all] Error 2
make: *** [all] Error 2

I'm using Boost 1.55

Switched to Boost 1.54, compiles fine.

Solo mining is not profitable, if you use this you should have your own mini farm.

I have 15 macs, that combined only have the expectation to earn 1 block per day.   If you solo mine right now with a high end machine you should expect one block every 2 weeks.  Of course the difficulty will rise over 2 weeks and orphans are high, so solo mining is more like one block every month+. 

I just pushed a patch to gain another 10%

https://github.com/InvictusInnovations/coyote_miner

Just curious. Anyone solo mining with this miner have managed to mined a block yet?

Quote from: ciklop1974 on November 14, 2013, 02:49:10 PM
Hello everyone. I'm trying to run a miner and it does not work. Wallet run like a server.
My conffile is:
server=1
rpcuser=login
rpcpassword=pass
rpcallowip=127.0.0.1
My bat-file is:
gw_miner.exe 127.0.0.1  -u login -p pass
pause
Its not work. I have this:

You should run the miner as: gw_miner.exe 127.0.0.1  login pass
and not as: gw_miner.exe 127.0.0.1  -u login -p pass

All work. :D

Hello everyone. I'm trying to run a miner and it does not work. Wallet run like a server.
My conffile is:
server=1
rpcuser=login
rpcpassword=pass
rpcallowip=127.0.0.1
My bat-file is:
gw_miner.exe 127.0.0.1  -u login -p pass
pause
Its not work. I have this:

Quote from: ryen123 on November 14, 2013, 05:07:01 AM
Inside your .conf file if you have -rpcport inside, delete it. Restart wallet and try the mining client again. Make it something like this.

rpcuser=your_username
rpcpassword=your_password
rpcallowip=127.0.0.1
server=1

Had the "rpcport" line deleted and it worked! Thanks!
My configuration was given by others and I did not notice this.