Topic: [ANN][BLC] Blakecoin Blake-256 for GPU/FPGA With Merged Mined Pools Stable Net - page 133. (Read 409571 times)

got a Lancelot mining that pool with kramble's python Blakecoin miner and can getwork somethings not setup right  

are you on a win x86 or x64?

Tried that too:

2014-02-03 12:44:16 | Device 0 opened (A5VOPER6)
2014-02-03 12:44:16 | Connected to 2 FPGAs
2014-02-03 12:44:16 | FPGA 0 is running at 100MHz
2014-02-03 12:44:16 | FPGA 1 is running at 100MHz
2014-02-03 12:44:16 | Connected to server
2014-02-03 12:44:16 | 0: Error getting work! Retrying...
2014-02-03 12:44:17 | 1: Error getting work! Retrying...
2014-02-03 12:44:17 | 0: Error getting work! Retrying...
2014-02-03 12:44:17 | 1: Error getting work! Retrying...
2014-02-03 12:44:17 | 0: Error getting work! Retrying...
2014-02-03 12:44:17 | 1: Error getting work! Retrying...
2014-02-03 12:44:17 | 0: Error getting work! Retrying...
2014-02-03 12:44:17 | 1: Error getting work! Retrying...
2014-02-03 12:44:17 | Long-poll: connected to ny1.blakecoin.com:8337
2014-02-03 12:44:17 | 0: Error getting work! Retrying...
2014-02-03 12:44:17 | 1: Error getting work! Retrying...
2014-02-03 12:44:18 | 0: Error getting work! Retrying...
2014-02-03 12:44:18 | 1: Error getting work! Retrying...
2014-02-03 12:44:18 | 0: Error getting work! Retrying...
2014-02-03 12:44:18 | 1: Error getting work! Retrying...
2014-02-03 12:44:18 | 0: Error getting work! Retrying...
2014-02-03 12:44:18 | 1: Error getting work! Retrying...
2014-02-03 12:44:18 | 0: Error getting work! Retrying...
2014-02-03 12:44:18 | 1: Error getting work! Retrying...
2014-02-03 12:44:19 | 0: Error getting work! Retrying...
2014-02-03 12:44:19 | 1: Error getting work! Retrying...
2014-02-03 12:44:19 | 0: Error getting work! Retrying...
2014-02-03 12:44:19 | 1: Error getting work! Retrying...
2014-02-03 12:44:19 | 0: Error getting work! Retrying...
2014-02-03 12:44:19 | 1: Error getting work! Retrying...
2014-02-03 12:44:19 | 0: Error getting work! Retrying...
2014-02-03 12:44:19 | 1: Error getting work! Retrying...
2014-02-03 12:44:20 | 0: Error getting work! Retrying...
2014-02-03 12:44:20 | 1: Error getting work! Retrying...
2014-02-03 12:44:20 | 0: Error getting work! Retrying...
2014-02-03 12:44:20 | 1: Error getting work! Retrying...
2014-02-03 12:44:20 | 0: Error getting work! Retrying...
2014-02-03 12:44:20 | 1: Error getting work! Retrying...
2014-02-03 12:44:20 | 0: Error getting work! Retrying...
2014-02-03 12:44:20 | 1: Error getting work! Retrying...
2014-02-03 12:44:20 | 0: Error getting work! Retrying...
2014-02-03 12:44:20 | 1: Error getting work! Retrying...
2014-02-03 12:44:21 | 0: Error getting work! Retrying...
2014-02-03 12:44:21 | 1: Error getting work! Retrying...
2014-02-03 12:44:21 | 0: Error getting work! Retrying...
2014-02-03 12:44:21 | 1: Error getting work! Retrying...
2014-02-03 12:44:21 | 0: Error getting work! Retrying...
2014-02-03 12:44:21 | 1: Error getting work! Retrying...
2014-02-03 12:44:21 | 0: Error getting work! Retrying...
2014-02-03 12:44:21 | 1: Error getting work! Retrying...
2014-02-03 12:44:21 | 0: Error getting work! Retrying...
2014-02-03 12:44:22 | Exiting...

try getwork is on port 8337
http://eu1.blakecoin.com
http://ny1.blakecoin.com

might be quicker than waiting for a block find?

Solo!

Haha.

which pool? or is that solo ?

Ah ha!

Unplugged the X6500, plugged it back in, now it works, haha.

But nothing but rejected:

2014-02-03 12:30:34 | Device 0 opened (A5VOPER6)
2014-02-03 12:30:34 | Connected to 2 FPGAs
2014-02-03 12:30:35 | FPGA 0 is running at 100MHz
2014-02-03 12:30:35 | FPGA 1 is running at 100MHz
2014-02-03 12:30:35 | Connected to server
2014-02-03 12:30:37 | rejected 4e7dae8eL
2014-02-03 12:30:41 | rejected 24330c9aL
2014-02-03 12:30:43 | rejected 335cff23L
2014-02-03 12:30:43 | rejected 74275a99L
2014-02-03 12:30:48 | rejected 4e7dae8eL
2014-02-03 12:30:51 | rejected 24330c9aL
2014-02-03 12:30:54 | rejected 335cff23L
2014-02-03 12:30:54 | rejected 74275a99L
2014-02-03 12:31:36 | rejected 30ca017fL
2014-02-03 12:31:38 | rejected 7b92ffe3L
2014-02-03 12:31:46 | rejected 272f58c7L
2014-02-03 12:31:47 | rejected 30ca017fL
2014-02-03 12:31:49 | rejected 7b92ffe3L
2014-02-03 12:32:01 | rejected 417a37ceL
0 kH/s | 0/14/0 100.00%/0.00%

Ugh, now I can't get mine.bat to work.

Before I just spammed it a couple times but now nothing.

Run Summary:
-------------
Traceback (most recent call last):
  File "mine.py", line 271, in
    logger.printSummary(settings)
  File "C:\Users\block_000\Desktop\x6500-miner-master\ConsoleLogger.py", line 21
0, in printSummary
    self.say('Device: %d' % self.devicenum, True, True)
AttributeError: 'ConsoleLogger' object has no attribute 'devicenum'

That's good to know. I've actually switched to using cgminer. It needs to be compiled specifically for the lancelot via #define LANCELOT_52 in driver-icarus.c ... I was lazy and didn't bother to make it a command line option or rebuild the bitstream for the CM1-style protocol). Anyway its working fine, with the added bonus of automatic failover.

I've still got the problem of the raspberry pi network stack hanging roughly once a day, but that's been solved with a watchdog and automatic reboot, so its been running fine for the last few weeks (I even flashed the lancelot MCS bitsteam, so it should survive a power outage, not that we get many of them here).

Jude: Good luck with X6500, hopefully we can get this working soon.

Thanks for the response Kramble!

I will give this a shot.

I am still using your python Blakecoin miner for the Lancelot boards and set that to diff 1 works a treat on the pools

OK, thanks, I was a little confused about the diff, but I did recall kr105's as sometimes reporting diff 2 and sometimes diff 4 on the dashboard. Anyway the worst that can happen is an increased reject rate, which is not ideal from the pool's point of view, but fairly harmless if it's just for testing. The FPGA always returns diff 1 shares, so unless there is an issue with hardware errors there will be no problem on your pools.

Once we've actually got some shares accepted on pool, the mining script can be tweaked to fix any target issues (see my previous post on the workaround).

my pools are fixed diff 1 so work should get accepted if the share is diff 1 and the miner can submit it, kr105's pool blakecoinpool.org is diff 2  

getwork is on port 8337
http://eu1.blakecoin.com
http://ny1.blakecoin.com

give it a try 

There is an easy work-around, just uncomment line 104 of mine.py. This will submit all shares regardless of the difficulty target, which is harmless when solo mining, and since (AFAIK, Blue may want to chip in here) the blakecoin pools are currently fixed diff=1 (even though the dashboard may report higher), it should be OK there too.

A slightly more sophisticated fix would retain the subsequent CheckTarget() and logger calls, but always return True.

cool 

if you see any other issues just let me know 

Yeps, all back to normal.

ahh ok I see an error: Potential Double Payout detected

checking DB now

Edit:
should be fixed now

did you get a payout and can you see unconfirmed?

pool eu1 my account... wallets don't have workers...

Since 7 this morning there are no credit transactions for my account on eu1... So I see the confirmed coins but no unconfirmed ones...

perhaps more than most, but i feel like im still only scratching the surface. i studied network communications at university and loved protocols and encoding schemes, but cryptography wasn't something i started learning about until i discovered bitcoin

Network hash rate slowly getting higher.