This miner is way too slow for state-of-the-art CPU miner. In fact, this is last resort if you want to mine on 32-bit machine.

With secondary backup pool connection in yam miner things are not so terrible, but still time to time connection in unstable.

Again, networking layer in yam miner was specially designed to survive situations when pools are under heavy DDoS, but pool diversity is definitely what helps a lot.

I guess now everybody understands why I was opposing releasing yam with single pool support...

Can you check if you are definitely running 64-bit kernel on your Mac?

Open "About This Mac"/"Software" and look for "64-bit Kernel and Extensions" under "System Software Overview"

or use

uname -a

from terminal.

If you are running 32-bit kernel, it will not be possible to use yam with it - yam is 64-bit executable, and there is no plan for now to revert to 32-bit because of much lower performance.

I am perfectly aware of these situations, so I will explain in few more details:

1. Illegal Instruction. Problem is that older OSes do not set up CPUs to operate new instruction sets, such as AES-NI and AVX2, properly. Most performance critical portions of yam manually coded in assembly, so I use instructions of my choice, and recompiling will not help. Specifying macosx-version-min simply disables some parts of instruction sets, but assembly code will not be affected, so issue will definitely persist.

What you can do is a) try to run generic build; b) check if your CPU supports needed instruction sets (some more details on this are also in readme.txt).

In fact, this is NOT MacOS X specific issue, it is also known to be in: Windows 7 without SP1 (does not run Haswell builds because of no AVX2 support prior to SP1); AVX misdetection in XEN virtualization environment and bug in Linux kernel

2. Abort trap: 6

This is also known issue, documented in "known issues" in readme.txt

It will occur, for example, if you misspell parameter name. I am looking for proper ways to resolve this already for a long time. It has to do with gcc-specific exception handling, boost libraries and symbol visibility settings. Still no clean solution, because of factoring out exceptions completely is unrealistic.

AWS EC2 uses XEN, and it has a widely known bug in AVX virtualization.

Try Nehalem build.

Look up microarchitecture for your cpu model at cpu world. Builds named after microarchitectures and follow gcccpu feature set naming (march and mtune).

Thanks.

I guess maintainers of groestlcoin.org shall update miner performance charts basing on those stats

New M7q version of yam miner is available. Major addition is support GroestlCoin (GRS) mining.
GroestlCoin mining with yam M7q brings major performance improvement on modern Haswell CPUs on Win64, Linux64 and MacOS X.
More docs in readme.txt included in distribution.

yam M7q available for downloads at regular locations:

https://mega.co.nz/#F!h0tkXSxZ!f62uoUXogkxQmP2xO8Ib-g
http://sdrv.ms/18wfjYX
http://pan.baidu.com/s/1xOOWa
https://www.dropbox.com/sh/jvp4wwek8jpohj7/RlW6hzYqTz

Also not really clear where shall I make request? By PMing? Do you add forum names manually? If so, it is easy with my name - same as here, same as in the Investors list.

If you carefully look at the output of the non-working config, you will see that there are only Incomplete rounds - no single round ever completed. Please provide more detalied information on configuration of non-working machine: size of PHYSICAL RAM, CPU type, version of miner used (architecture), number of threads in use, and mining-params line from your config.

This behaviour is typical when 1) there is lack of RAM, and swap file/partition used by OS; 2) On multi-CPU machines with NUMA architectures when you run single process across multiple physical CPUs and memory being accessed via QPI link.

Next question is to see what is CPU load of your system and if there any disk activity. If CPU load is very low, then there are again two major cases: 1) Disk swapping; 2) Unstable connection (pool connects and then disconnects or conn times out) and miner is unable to get work.

Situation when both conns are on-line shall be very rare, and its persistence is a clear indication of networking/connection issues.

Thanks. Enjoy.

I am developer of yam miner (this is CPU miner that supports MaxCoin). I prepare new release of the miner and updating default config, so I would like to test my miner with miningpoolhub and need invite for that.

Regards,
yvg1900

I recommend mentioning extra ports on Getting STarted page - it is good I was passing by this message, so will add these to default yam config. Backup ports are very important for mining stability.

Is anyone experience probs getting account details editing unlock e-mail confirmations from Block Quarry?

Also - FYI - testing of flipsidemining with yam is positive for now, which means we can soon have yam with full NRS support.

In fact it shows 10 last transactions (as per default value of count parameter) but does not accept count value (mistakes it for account name?)

There is definitely something unclear - I have at least one block mined on 3 of March, and still have 0.0 stake - can you provide explanation how does it work?

Also listtransactions in Debug window does not show right number of transactions, besides of GUI shows right number and displays all the transactions correctly.

Any ideas/way to test?

Is there minimum investment amount for that premium no-trade-fee status :-)  ?

Is your pool using getwork? I may add support for your pool in upcoming yam release.

yvg1900

Hi,

Note that new version of pts miner is available, and pls take care of huge pages config to achieve better perf.

Also look at my comment at reddit for some extra info on miner update.

yvg1900

Hi all,

If someone is in contact with devs of this distro, I encourage you to point them that new version is available, and they shall take care of huge pages config to achieve better perf.

yvg1900