ASIC devices seem to generate good hash rates, but no accepted, no rejected, only HW errors.

seftonde · December 2013

Hello

I've been using macminer for a couple days now. I can mine with CPUminer, mining fast coins, in the miningpool.co pool with no problems.

However, I have three ASIC Sapphire Block erruptor USB sticks that I'm trying to get to work. I can start up the FPGA/ASIC miner and I got it to run, kindof. It shows a rate of 900 - 1,200 MHs, which seems normal (sticks are rated at 333 MHs apiece). However, however long I run it, I never get any 'accepted' or 'rejected' numbers, always 0 for both. And of course my mining pool shows no credit at all. (Same mining pool that works fine with CPU mining at a 12-18Khs rate). API output shows a lot of HW errors. I don't understand how the devices can show reasonable hash rates, but no accepted, no rejected and only Hardware errors?

Any ideas where I should look?

FabulousPanda · December 2013

Let me just make sure - are you using them to mine BTC or have you set --scrypt?

What version of Mac OS are you running and what if anything have you done driver wise?

seftonde · December 2013

Hello FP,

Using them to mine FastCoin from https://www.miningpool.co/stats/FST/.

I can connect to that addres and successfully mine fastcoin with my CPU, so I know my connection/pool is set correctly.

My son has used them successfully on his pc to mine bitcoin, so I know the devices are good.

Drivers are installed, using the macosx drivers from the device web site:

http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx

part of log that makes me think maybe drivers are working:

[2013-12-19 06:49:44] Acquired exclusive advisory lock on /dev/cu.SLAB_USBtoUART2

[2013-12-19 06:49:44] bifury: Successfully opened /dev/cu.SLAB_USBtoUART2

[2013-12-19 06:49:46] Acquired exclusive advisory lock on /dev/cu.Bluetooth-Incoming-Port

OSX = Mavericks version 10.9.1.

However! WHen I was writing this email I started it up to get the agove logs and the voice said 'authorization failed' ( I usually have my sound off). Wonder if that could be telling me that my pool is indeed set up incorrectly? (even though I can mine with cpu)?

Sorry, not sure what you mean by 'setting script'. Parms are -S all.

Thanks - and apologies if maybe I'm missing something obvious or trying something that is not possible!

Daniel

seftonde · December 2013

Not to bore you with logs, but here is a portion that shows both devices (BEE and ICA), but also shows the setting of the "HW failed" error.

[2013-12-19 07:03:40] Generated stratum header 00000001357fc7547289e18da86a5c1b0d8032c6ab3a644266cb775f9f7fc1cb2d36ba85edfe8b705dbcc9451edcd993e764665eda746e13b764ec2b260d5092f418a05052b2e0981d00ef5200000000

[2013-12-19 07:03:40] Work job_id 4192 nonce2 07000000

[2013-12-19 07:03:40] Generated target 000000000ffff000000000000000000000000000000000000000000000000000

[2013-12-19 07:03:40] Generated stratum work

[2013-12-19 07:03:40] Pushing work 36701 from pool 0 to hash queue

[2013-12-19 07:03:41] Acquired exclusive advisory lock on /dev/cu.SLAB_USBtoUART6

[2013-12-19 07:03:41] ICA 0 sent: ea743141c3d5e0b4e09ec4ef3383d36b83c43a75203f4e9764c0b121f10dcddf000000000000000000000000000000000000000052ef001d95e0b2522790a900

[2013-12-19 07:03:41] ICA 0: invalid nonce (c4cc0b8b) - HW error

[2013-12-19 07:03:41] ICA 0 nonce = 0x8b0bccc4 = 0x1617998a hashes (4.744119s)

[2013-12-19 07:03:41] ICA 0: Autodetect device speed: 78 MH/s

[2013-12-19 07:03:41] ICA 0: Seems too slow to be an Icarus; calibrating with short timing

[2013-12-19 07:03:41] [thread 0: 752635517 hashes, 130362.1 khash/sec]

[2013-12-19 07:03:41] ICA 0: Popping work from get queue to get work

[2013-12-19 07:03:41] Selecting pool 0 for work

[2013-12-19 07:03:41] ICA 0: Got work 36698 from get queue to get work for thread 0

[2013-12-19 07:03:41] Generated stratum header 00000001357fc7547289e18da86a5c1b0d8032c6ab3a644266cb775f9f7fc1cb2d36ba85d94afa74d5d2b7134f88fba663bfabede94a605b640b144294c41a70331d74e552b2e0991d00ef5200000000

[2013-12-19 07:03:41] Work job_id 4192 nonce2 08000000

[2013-12-19 07:03:41] Generated target 000000000ffff000000000000000000000000000000000000000000000000000

[2013-12-19 07:03:41] Generated stratum work

[2013-12-19 07:03:41] Pushing work 36704 from pool 0 to hash queue

[2013-12-19 07:03:41] Acquired exclusive advisory lock on /dev/cu.SLAB_USBtoUART2

[2013-12-19 07:03:41] BEE 0 sent: cdf1b12fa86f1bc0b8766d25700dcce5557a09d25ffda1e092080bad9567e17f000000000000000000000000000000000000000052ef001d95e0b2529eb38dbf

[2013-12-19 07:03:41] BEE 0: invalid nonce (ffffffff) - HW error

[2013-12-19 07:03:41] BEE 0 nonce = 0xffffffff = 0x100000000 hashes (1.420746s)

[2013-12-19 07:03:41] [thread 1: 4294967296 hashes, 2984678.3 khash/sec]

[2013-12-19 07:03:41] BEE 0: Popping work from get queue to get work

[2013-12-19 07:03:41] Selecting pool 0 for work

[2013-12-19 07:03:41] BEE 0: Got work 36701 from get queue to get work for thread 1

[2

FabulousPanda · December 2013

There are two primary hashing algorithms, SHA-256 which Bitcoin uses and Scrypt which Litecoin and Fastcoin use. You can't use ASIC devices to mine scrypt currencies, that's why this isn't working!

seftonde · December 2013

Hi FP,

Excellent! Thank you very much for the information. I knew (hoped) it would be something obvious and simple like that. I'll stick to fastcoin (very successfully mined with MacMiner/CPU) and leave the bitcoin to my son.

take care,

Daniel

Howdy, Stranger!

Quick Links

Categories

ASIC devices seem to generate good hash rates, but no accepted, no rejected, only HW errors.

Comments

Leave a Comment