OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 79.

sovie

sr. member

Activity: 1274

Merit: 265

hello

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: dlasher on July 25, 2014, 01:59:57 PM

ok, I went back 15 pages, but didn't see this answered, so I hope I'm safe in asking:

Antminer S3 support yet? I see S1 & S2 folders, but no S3 folder yet.. Hoping Kano has a binary soon..

Trying to compile my own, but getting the build env right is... painful.

Not yet sorry. I believe he is/will be working on it.

dlasher

sr. member

Activity: 467

Merit: 250

ok, I went back 15 pages, but didn't see this answered, so I hope I'm safe in asking:

Antminer S3 support yet? I see S1 & S2 folders, but no S3 folder yet.. Hoping Kano has a binary soon..

Trying to compile my own, but getting the build env right is... painful.

Askit2

hero member

Activity: 981

Merit: 500

DIV - Your "Virtual Life" Secured and Decentralize

Quote from: Bearfrog on July 24, 2014, 09:22:59 PM

Quote from: -ck on July 24, 2014, 01:50:47 AM

Quote from: Bearfrog on July 24, 2014, 01:29:18 AM

I am having trouble with CGMiner connecting to slush's pool. At the beginning of the week everything was mining just fine. Then suddenly stopped with no real reason. Having done reading I have a logfile.txt with verbose debug in it. I am running Win7 64 with a directly plugged in icefury ASIC. I am including the text from the logfile, having changed only the worker name and password. Any insight would be helpful.

Code:

[2014-07-23 22:06:45] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:06:46] Select timeout/failed connect
[2014-07-23 22:06:47] Select timeout/failed connect
[2014-07-23 22:06:47] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:06:47] Initiate stratum failed
[2014-07-23 22:06:52] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:06:53] Select timeout/failed connect
[2014-07-23 22:06:54] Select timeout/failed connect
[2014-07-23 22:06:54] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:06:54] Initiate stratum failed
[2014-07-23 22:06:55] Waiting for work to be available from pools.
[2014-07-23 22:06:59] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:00] Select timeout/failed connect
[2014-07-23 22:07:01] Select timeout/failed connect
[2014-07-23 22:07:01] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:01] Initiate stratum failed
[2014-07-23 22:07:06] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:07] Select timeout/failed connect
[2014-07-23 22:07:08] Select timeout/failed connect
[2014-07-23 22:07:08] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:08] Initiate stratum failed
[2014-07-23 22:07:13] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:14] Select timeout/failed connect
[2014-07-23 22:07:15] Select timeout/failed connect
[2014-07-23 22:07:15] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:15] Initiate stratum failed
[2014-07-23 22:07:20] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:21] Select timeout/failed connect
[2014-07-23 22:07:22] Select timeout/failed connect
[2014-07-23 22:07:22] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:22] Initiate stratum failed
[2014-07-23 22:07:27] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:28] Select timeout/failed connect
[2014-07-23 22:07:29] Select timeout/failed connect
[2014-07-23 22:07:29] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:30] Initiate stratum failed
[2014-07-23 22:07:35] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:36] Select timeout/failed connect
[2014-07-23 22:07:37] Select timeout/failed connect
[2014-07-23 22:07:37] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:37] Initiate stratum failed
[2014-07-23 22:07:42] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:43] Select timeout/failed connect
[2014-07-23 22:07:44] Select timeout/failed connect
[2014-07-23 22:07:44] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:44] Initiate stratum failed
[2014-07-23 22:07:45] No servers were found that could be used to get work from.
[2014-07-23 22:07:45] Please check the details from the list below of the servers you have input
[2014-07-23 22:07:45] Most likely you have input the wrong URL, forgotten to add a port, or have not set up workers
[2014-07-23 22:07:45] Pool: 0 URL: stratum+tcp://stratum.bitcoin.cz:3333 User: workernamehere Password: password
[2014-07-23 22:07:45] No servers could be used! Exiting.

(I put code tags around your original post).

It looks like you simply cannot connect to slush for now. If the pool is actually still up (and it appears to be), sometimes internet connectivity can have selective routing issues that stop you getting to one particular place. If you're on linux, the following command can help you diagnose the presence of that issue:

Code:

mtr --report -w stratum.bitcoin.cz

Not sure what you'd use on win*

You should always have at least one backup pool and ideally a local solo mine as a final backup in case of such issues.

Well I tried to connect to a different mining pool and am still having the issue of not connecting. I guess I will start trying to configure bfgminer but that one gives me headaches. I am a total noob when it comes to mining.

Slush's pool always takes a bit of time on my miners to start up. I have backup pools. Actually I have 3 miners with different main pools that use the other pools as a backup and my own bitcoin instance as a final fall back occasionally with 7 servers I still have trouble getting work to keep them busy. I have not checked the trouble getting work message since v4. something. Not constantly unable to connect though. As was suggested setup a backup pool. It doesn't really matter as much what pool.

Have a bitcoin instance running you can mine to. You can actually have bitcoin-qt running as a daemon on windows. I do it currently. Getting a config file setup might take a little looking. Knowing what version of windows, what version of the wallet you use and the required parameters it isn't hard to get a local instance up and running. I will say it is likely a good idea not to use bitcoin-qt without running a separate daemon instance. I do this but I do occasionally get crashes in bitcoin-qt.

Have you perhaps used the other pool from that computer before? If you have maybe you have a corrupt/old DNS entry for both. The following could help for that but you will experience some delays the next time it tries to get a connection to a site you have been to recently. If I am right its related to a Windows specific issue wherein a bad DNS lookup will get stored until it is timed out and that takes I think it was 2 weeks.

Code:

ipconfig /flushdns

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: Bearfrog on July 24, 2014, 09:22:59 PM

Well I tried to connect to a different mining pool and am still having the issue of not connecting. I guess I will start trying to configure bfgminer but that one gives me headaches. I am a total noob when it comes to mining.

That fork got all its stratum networking code from cgminer so you'll likely have the same issues.

Bearfrog

newbie

Activity: 2

Merit: 0

Quote from: -ck on July 24, 2014, 01:50:47 AM

Quote from: Bearfrog on July 24, 2014, 01:29:18 AM

I am having trouble with CGMiner connecting to slush's pool. At the beginning of the week everything was mining just fine. Then suddenly stopped with no real reason. Having done reading I have a logfile.txt with verbose debug in it. I am running Win7 64 with a directly plugged in icefury ASIC. I am including the text from the logfile, having changed only the worker name and password. Any insight would be helpful.

Code:

[2014-07-23 22:06:45] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:06:46] Select timeout/failed connect
[2014-07-23 22:06:47] Select timeout/failed connect
[2014-07-23 22:06:47] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:06:47] Initiate stratum failed
[2014-07-23 22:06:52] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:06:53] Select timeout/failed connect
[2014-07-23 22:06:54] Select timeout/failed connect
[2014-07-23 22:06:54] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:06:54] Initiate stratum failed
[2014-07-23 22:06:55] Waiting for work to be available from pools.
[2014-07-23 22:06:59] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:00] Select timeout/failed connect
[2014-07-23 22:07:01] Select timeout/failed connect
[2014-07-23 22:07:01] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:01] Initiate stratum failed
[2014-07-23 22:07:06] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:07] Select timeout/failed connect
[2014-07-23 22:07:08] Select timeout/failed connect
[2014-07-23 22:07:08] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:08] Initiate stratum failed
[2014-07-23 22:07:13] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:14] Select timeout/failed connect
[2014-07-23 22:07:15] Select timeout/failed connect
[2014-07-23 22:07:15] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:15] Initiate stratum failed
[2014-07-23 22:07:20] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:21] Select timeout/failed connect
[2014-07-23 22:07:22] Select timeout/failed connect
[2014-07-23 22:07:22] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:22] Initiate stratum failed
[2014-07-23 22:07:27] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:28] Select timeout/failed connect
[2014-07-23 22:07:29] Select timeout/failed connect
[2014-07-23 22:07:29] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:30] Initiate stratum failed
[2014-07-23 22:07:35] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:36] Select timeout/failed connect
[2014-07-23 22:07:37] Select timeout/failed connect
[2014-07-23 22:07:37] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:37] Initiate stratum failed
[2014-07-23 22:07:42] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:43] Select timeout/failed connect
[2014-07-23 22:07:44] Select timeout/failed connect
[2014-07-23 22:07:44] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:44] Initiate stratum failed
[2014-07-23 22:07:45] No servers were found that could be used to get work from.
[2014-07-23 22:07:45] Please check the details from the list below of the servers you have input
[2014-07-23 22:07:45] Most likely you have input the wrong URL, forgotten to add a port, or have not set up workers
[2014-07-23 22:07:45] Pool: 0 URL: stratum+tcp://stratum.bitcoin.cz:3333 User: workernamehere Password: password
[2014-07-23 22:07:45] No servers could be used! Exiting.

(I put code tags around your original post).

It looks like you simply cannot connect to slush for now. If the pool is actually still up (and it appears to be), sometimes internet connectivity can have selective routing issues that stop you getting to one particular place. If you're on linux, the following command can help you diagnose the presence of that issue:

Code:

mtr --report -w stratum.bitcoin.cz

Not sure what you'd use on win*

You should always have at least one backup pool and ideally a local solo mine as a final backup in case of such issues.

Well I tried to connect to a different mining pool and am still having the issue of not connecting. I guess I will start trying to configure bfgminer but that one gives me headaches. I am a total noob when it comes to mining.

smesterj

member

Activity: 84

Merit: 10

Quote from: techman05 on July 14, 2014, 07:54:58 PM

If you followed the setup and provided an address I assume you'd see it in you wallet "if" you complete a block.

If you decide to mine for the bitcoin after your experiment join a pool. You might be able to get .01 a week with 180Ghs. If you want to try solo mining try something like julecoin. Probably the same setup for straight bitcoining(meaning you have to sell them into bitcoin) and a whole lot less difficulty[and I'm not mining it Tongue

].

You were right, thanks. I started mining on BTCguild 3 days ago and got;
BTC Account Balance.
Earnings 0.00652110
Withdrawals 0.00000000
Account Balance 0.00652110

Using 4 r-boxes;
Total Mining Speed Total Shares Total Rejects
130.46 GH/s 6,718k 17,124 (0.25%)

Thanks for all your help, will be able to donate in a couple of weeks I guess. Cool

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: Bearfrog on July 24, 2014, 01:29:18 AM

I am having trouble with CGMiner connecting to slush's pool. At the beginning of the week everything was mining just fine. Then suddenly stopped with no real reason. Having done reading I have a logfile.txt with verbose debug in it. I am running Win7 64 with a directly plugged in icefury ASIC. I am including the text from the logfile, having changed only the worker name and password. Any insight would be helpful.

Code:

[2014-07-23 22:06:45] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:06:46] Select timeout/failed connect
[2014-07-23 22:06:47] Select timeout/failed connect
[2014-07-23 22:06:47] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:06:47] Initiate stratum failed
[2014-07-23 22:06:52] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:06:53] Select timeout/failed connect
[2014-07-23 22:06:54] Select timeout/failed connect
[2014-07-23 22:06:54] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:06:54] Initiate stratum failed
[2014-07-23 22:06:55] Waiting for work to be available from pools.
[2014-07-23 22:06:59] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:00] Select timeout/failed connect
[2014-07-23 22:07:01] Select timeout/failed connect
[2014-07-23 22:07:01] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:01] Initiate stratum failed
[2014-07-23 22:07:06] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:07] Select timeout/failed connect
[2014-07-23 22:07:08] Select timeout/failed connect
[2014-07-23 22:07:08] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:08] Initiate stratum failed
[2014-07-23 22:07:13] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:14] Select timeout/failed connect
[2014-07-23 22:07:15] Select timeout/failed connect
[2014-07-23 22:07:15] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:15] Initiate stratum failed
[2014-07-23 22:07:20] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:21] Select timeout/failed connect
[2014-07-23 22:07:22] Select timeout/failed connect
[2014-07-23 22:07:22] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:22] Initiate stratum failed
[2014-07-23 22:07:27] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:28] Select timeout/failed connect
[2014-07-23 22:07:29] Select timeout/failed connect
[2014-07-23 22:07:29] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:30] Initiate stratum failed
[2014-07-23 22:07:35] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:36] Select timeout/failed connect
[2014-07-23 22:07:37] Select timeout/failed connect
[2014-07-23 22:07:37] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:37] Initiate stratum failed
[2014-07-23 22:07:42] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:43] Select timeout/failed connect
[2014-07-23 22:07:44] Select timeout/failed connect
[2014-07-23 22:07:44] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:44] Initiate stratum failed
[2014-07-23 22:07:45] No servers were found that could be used to get work from.
[2014-07-23 22:07:45] Please check the details from the list below of the servers you have input
[2014-07-23 22:07:45] Most likely you have input the wrong URL, forgotten to add a port, or have not set up workers
[2014-07-23 22:07:45] Pool: 0 URL: stratum+tcp://stratum.bitcoin.cz:3333 User: workernamehere Password: password
[2014-07-23 22:07:45] No servers could be used! Exiting.

(I put code tags around your original post).

It looks like you simply cannot connect to slush for now. If the pool is actually still up (and it appears to be), sometimes internet connectivity can have selective routing issues that stop you getting to one particular place. If you're on linux, the following command can help you diagnose the presence of that issue:

Code:

mtr --report -w stratum.bitcoin.cz

Not sure what you'd use on win*

You should always have at least one backup pool and ideally a local solo mine as a final backup in case of such issues.

Bearfrog

newbie

Activity: 2

Merit: 0

I am having trouble with CGMiner connecting to slush's pool. At the beginning of the week everything was mining just fine. Then suddenly stopped with no real reason. Having done reading I have a logfile.txt with verbose debug in it. I am running Win7 64 with a directly plugged in icefury ASIC. I am including the text from the logfile, having changed only the worker name and password. Any insight would be helpful.

Code:

[2014-07-23 22:06:42] Started cgminer 4.4.2
[2014-07-23 22:06:42] USB scan devices: checking for AVA devices
[2014-07-23 22:06:42] RES: thread starting
[2014-07-23 22:06:42] AVA looking for BTB 0403:6001 but found 8086:1c2d instead
[2014-07-23 22:06:42] AVA looking for BBF 0403:6001 but found 8086:1c2d instead
[2014-07-23 22:06:42] AVA looking for AVA 0403:6001 but found 8086:1c2d instead
[2014-07-23 22:06:42] AVA looking for BTB 0403:6001 but found 8086:1c26 instead
[2014-07-23 22:06:42] AVA looking for BBF 0403:6001 but found 8086:1c26 instead
[2014-07-23 22:06:42] AVA looking for AVA 0403:6001 but found 8086:1c26 instead
[2014-07-23 22:06:42] AVA looking for BTB 0403:6001 but found 0489:e00f instead
[2014-07-23 22:06:42] AVA looking for BBF 0403:6001 but found 0489:e00f instead
[2014-07-23 22:06:42] AVA looking for AVA 0403:6001 but found 0489:e00f instead
[2014-07-23 22:06:42] AVA looking for BTB 0403:6001 but found 04d8:00de instead
[2014-07-23 22:06:42] AVA looking for BBF 0403:6001 but found 04d8:00de instead
[2014-07-23 22:06:42] AVA looking for AVA 0403:6001 but found 04d8:00de instead
[2014-07-23 22:06:42] AVA looking for BTB 0403:6001 but found 05ca:18c0 instead
[2014-07-23 22:06:42] AVA looking for BBF 0403:6001 but found 05ca:18c0 instead
[2014-07-23 22:06:42] AVA looking for AVA 0403:6001 but found 05ca:18c0 instead
[2014-07-23 22:06:42] AVA looking for BTB 0403:6001 but found 8087:0024 instead
[2014-07-23 22:06:42] AVA looking for BBF 0403:6001 but found 8087:0024 instead
[2014-07-23 22:06:42] AVA looking for AVA 0403:6001 but found 8087:0024 instead
[2014-07-23 22:06:42] AVA looking for BTB 0403:6001 but found 8087:0024 instead
[2014-07-23 22:06:42] AVA looking for BBF 0403:6001 but found 8087:0024 instead
[2014-07-23 22:06:42] AVA looking for AVA 0403:6001 but found 8087:0024 instead
[2014-07-23 22:06:42] AVA looking for BTB 0403:6001 but found 8087:07d6 instead
[2014-07-23 22:06:42] AVA looking for BBF 0403:6001 but found 8087:07d6 instead
[2014-07-23 22:06:42] AVA looking for AVA 0403:6001 but found 8087:07d6 instead
[2014-07-23 22:06:42] AVA looking for BTB 0403:6001 but found 1033:0194 instead
[2014-07-23 22:06:42] AVA looking for BBF 0403:6001 but found 1033:0194 instead
[2014-07-23 22:06:42] AVA looking for AVA 0403:6001 but found 1033:0194 instead
[2014-07-23 22:06:42] USB scan devices: checking for BAS devices
[2014-07-23 22:06:42] BAS looking for BAS 0403:6014 but found 8086:1c2d instead
[2014-07-23 22:06:42] BAS looking for BAS 0403:6014 but found 8086:1c26 instead
[2014-07-23 22:06:42] BAS looking for BAS 0403:6014 but found 0489:e00f instead
[2014-07-23 22:06:42] BAS looking for BAS 0403:6014 but found 04d8:00de instead
[2014-07-23 22:06:42] BAS looking for BAS 0403:6014 but found 05ca:18c0 instead
[2014-07-23 22:06:42] BAS looking for BAS 0403:6014 but found 8087:0024 instead
[2014-07-23 22:06:42] BAS looking for BAS 0403:6014 but found 8087:0024 instead
[2014-07-23 22:06:42] BAS looking for BAS 0403:6014 but found 8087:07d6 instead
[2014-07-23 22:06:42] BAS looking for BAS 0403:6014 but found 1033:0194 instead
[2014-07-23 22:06:42] USB scan devices: checking for BF1 devices
[2014-07-23 22:06:43] BF1 looking for BF1 03eb:204b but found 8086:1c2d instead
[2014-07-23 22:06:43] BF1 looking for BXF 198c:b1f1 but found 8086:1c2d instead
[2014-07-23 22:06:43] BF1 looking for OSM 198c:b1f1 but found 8086:1c2d instead
[2014-07-23 22:06:43] BF1 looking for NFU 04d8:00de but found 8086:1c2d instead
[2014-07-23 22:06:43] BF1 looking for BXM 0403:6014 but found 8086:1c2d instead
[2014-07-23 22:06:43] BF1 looking for BF1 03eb:204b but found 8086:1c26 instead
[2014-07-23 22:06:43] BF1 looking for BXF 198c:b1f1 but found 8086:1c26 instead
[2014-07-23 22:06:43] BF1 looking for OSM 198c:b1f1 but found 8086:1c26 instead
[2014-07-23 22:06:43] BF1 looking for NFU 04d8:00de but found 8086:1c26 instead
[2014-07-23 22:06:43] BF1 looking for BXM 0403:6014 but found 8086:1c26 instead
[2014-07-23 22:06:43] BF1 looking for BF1 03eb:204b but found 0489:e00f instead
[2014-07-23 22:06:43] BF1 looking for BXF 198c:b1f1 but found 0489:e00f instead
[2014-07-23 22:06:43] BF1 looking for OSM 198c:b1f1 but found 0489:e00f instead
[2014-07-23 22:06:43] BF1 looking for NFU 04d8:00de but found 0489:e00f instead
[2014-07-23 22:06:43] BF1 looking for BXM 0403:6014 but found 0489:e00f instead
[2014-07-23 22:06:43] BF1 looking for BF1 03eb:204b but found 04d8:00de instead
[2014-07-23 22:06:43] BF1 looking for BXF 198c:b1f1 but found 04d8:00de instead
[2014-07-23 22:06:43] BF1 looking for OSM 198c:b1f1 but found 04d8:00de instead
[2014-07-23 22:06:43] BF1 looking for and found NFU 04d8:00de
[2014-07-23 22:06:43] USB lock bitfury 2-2
[2014-07-23 22:06:43] RES: bitfury (2:2) lock=1
[2014-07-23 22:06:43] USB res lock bitfury 2-2
[2014-07-23 22:06:43] RES: bitfury (2:2) lock ok=1
[2014-07-23 22:06:43] USB init - NFU device 2:2 usbver=0200 prod='NanoFury NF1 v0.7' manuf='Microchip Technology Inc.' serial='0000093694'
[2014-07-23 22:06:43] NFU 0: Found at 2:2
[2014-07-23 22:06:43] NF1 0: Pin dir 0 0
[2014-07-23 22:06:43] NF1 0: Pin dir 1 1
[2014-07-23 22:06:43] NF1 0: Pin dir 2 1
[2014-07-23 22:06:43] NF1 0: Pin dir 3 1
[2014-07-23 22:06:43] NF1 0: Pin dir 4 0
[2014-07-23 22:06:43] NF1 0: Pin dir 5 1
[2014-07-23 22:06:43] NF1 0: Pin dir 6 0
[2014-07-23 22:06:43] NF1 0: Pin dir 7 0
[2014-07-23 22:06:43] NF1 0: Pin dir 8 1
[2014-07-23 22:06:43] NF1 0: Pin val 0 1
[2014-07-23 22:06:43] NF1 0: Pin val 1 0
[2014-07-23 22:06:43] NF1 0: Pin val 2 0
[2014-07-23 22:06:43] NF1 0: Pin val 3 0
[2014-07-23 22:06:43] NF1 0: Pin val 4 0
[2014-07-23 22:06:43] NF1 0: Pin val 5 0
[2014-07-23 22:06:43] NF1 0: Pin val 6 1
[2014-07-23 22:06:43] NF1 0: Pin val 7 0
[2014-07-23 22:06:43] NF1 0: Pin val 8 0
[2014-07-23 22:06:43] NF1 0: Pin des 0 0
[2014-07-23 22:06:43] NF1 0: Pin des 1 0
[2014-07-23 22:06:43] NF1 0: Pin des 2 0
[2014-07-23 22:06:43] NF1 0: Pin des 3 0
[2014-07-23 22:06:43] NF1 0: Pin des 4 1
[2014-07-23 22:06:43] NF1 0: Pin des 5 0
[2014-07-23 22:06:43] NF1 0: Pin des 6 0
[2014-07-23 22:06:43] NF1 0: Pin des 7 0
[2014-07-23 22:06:43] NF1 0: Pin des 8 0
[2014-07-23 22:06:43] NF1 0: SPI sending 1 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 1 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 1 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 1 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 1 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 1 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 1 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 1 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 1 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 1 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 1 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 1 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 1 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 1 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 1 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 1 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 1 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 1 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 1 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 1 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 1 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 1 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 1 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 1 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 1 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 1 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 1 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 1 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 1 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 1 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 1 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 1 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 1 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 1 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 1 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 1 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 1 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 1 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 317 bytes total
[2014-07-23 22:06:43] NF1 0: SPI sending 60 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 60 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 60 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 60 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 60 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 60 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 60 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 60 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 60 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 60 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: SPI sending 17 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 0 bytes status 0x20
[2014-07-23 22:06:43] NF1 0: SPI sending 0 bytes
[2014-07-23 22:06:43] NF1 0: SPI transfer success, received 17 bytes status 0x10
[2014-07-23 22:06:43] NF1 0: Successfully initialised 2:2
[2014-07-23 22:06:43] BF1 looking for BF1 03eb:204b but found 05ca:18c0 instead
[2014-07-23 22:06:43] BF1 looking for BXF 198c:b1f1 but found 05ca:18c0 instead
[2014-07-23 22:06:43] BF1 looking for OSM 198c:b1f1 but found 05ca:18c0 instead
[2014-07-23 22:06:43] BF1 looking for NFU 04d8:00de but found 05ca:18c0 instead
[2014-07-23 22:06:43] BF1 looking for BXM 0403:6014 but found 05ca:18c0 instead
[2014-07-23 22:06:43] BF1 looking for BF1 03eb:204b but found 8087:0024 instead
[2014-07-23 22:06:43] BF1 looking for BXF 198c:b1f1 but found 8087:0024 instead
[2014-07-23 22:06:43] BF1 looking for OSM 198c:b1f1 but found 8087:0024 instead
[2014-07-23 22:06:43] BF1 looking for NFU 04d8:00de but found 8087:0024 instead
[2014-07-23 22:06:43] BF1 looking for BXM 0403:6014 but found 8087:0024 instead
[2014-07-23 22:06:43] BF1 looking for BF1 03eb:204b but found 8087:0024 instead
[2014-07-23 22:06:43] BF1 looking for BXF 198c:b1f1 but found 8087:0024 instead
[2014-07-23 22:06:43] BF1 looking for OSM 198c:b1f1 but found 8087:0024 instead
[2014-07-23 22:06:43] BF1 looking for NFU 04d8:00de but found 8087:0024 instead
[2014-07-23 22:06:43] BF1 looking for BXM 0403:6014 but found 8087:0024 instead
[2014-07-23 22:06:43] BF1 looking for BF1 03eb:204b but found 8087:07d6 instead
[2014-07-23 22:06:43] BF1 looking for BXF 198c:b1f1 but found 8087:07d6 instead
[2014-07-23 22:06:43] BF1 looking for OSM 198c:b1f1 but found 8087:07d6 instead
[2014-07-23 22:06:43] BF1 looking for NFU 04d8:00de but found 8087:07d6 instead
[2014-07-23 22:06:43] BF1 looking for BXM 0403:6014 but found 8087:07d6 instead
[2014-07-23 22:06:43] BF1 looking for BF1 03eb:204b but found 1033:0194 instead
[2014-07-23 22:06:43] BF1 looking for BXF 198c:b1f1 but found 1033:0194 instead
[2014-07-23 22:06:43] BF1 looking for OSM 198c:b1f1 but found 1033:0194 instead
[2014-07-23 22:06:43] BF1 looking for NFU 04d8:00de but found 1033:0194 instead
[2014-07-23 22:06:43] BF1 looking for BXM 0403:6014 but found 1033:0194 instead
[2014-07-23 22:06:43] USB scan devices: checking for CTA devices
[2014-07-23 22:06:44] CTA looking for CTA 1cbe:0003 but found 8086:1c2d instead
[2014-07-23 22:06:44] CTA looking for CTA 1cbe:0003 but found 8086:1c26 instead
[2014-07-23 22:06:44] CTA looking for CTA 1cbe:0003 but found 0489:e00f instead
[2014-07-23 22:06:44] CTA looking for CTA 1cbe:0003 but found 04d8:00de instead
[2014-07-23 22:06:44] CTA looking for CTA 1cbe:0003 but found 05ca:18c0 instead
[2014-07-23 22:06:44] CTA looking for CTA 1cbe:0003 but found 8087:0024 instead
[2014-07-23 22:06:44] CTA looking for CTA 1cbe:0003 but found 8087:0024 instead
[2014-07-23 22:06:44] CTA looking for CTA 1cbe:0003 but found 8087:07d6 instead
[2014-07-23 22:06:44] CTA looking for CTA 1cbe:0003 but found 1033:0194 instead
[2014-07-23 22:06:44] USB scan devices: checking for HFA devices
[2014-07-23 22:06:44] HFA looking for HFA 297c:0001 but found 8086:1c2d instead
[2014-07-23 22:06:44] HFA looking for HFA 297c:0001 but found 8086:1c26 instead
[2014-07-23 22:06:44] HFA looking for HFA 297c:0001 but found 0489:e00f instead
[2014-07-23 22:06:44] HFA looking for HFA 297c:0001 but found 04d8:00de instead
[2014-07-23 22:06:44] HFA looking for HFA 297c:0001 but found 05ca:18c0 instead
[2014-07-23 22:06:44] HFA looking for HFA 297c:0001 but found 8087:0024 instead
[2014-07-23 22:06:44] HFA looking for HFA 297c:0001 but found 8087:0024 instead
[2014-07-23 22:06:44] HFA looking for HFA 297c:0001 but found 8087:07d6 instead
[2014-07-23 22:06:44] HFA looking for HFA 297c:0001 but found 1033:0194 instead
[2014-07-23 22:06:44] USB scan devices: checking for ICA devices
[2014-07-23 22:06:44] ICA looking for ICA 067b:2303 but found 8086:1c2d instead
[2014-07-23 22:06:44] ICA looking for AMU 10c4:ea60 but found 8086:1c2d instead
[2014-07-23 22:06:44] ICA looking for LIN 10c4:ea60 but found 8086:1c2d instead
[2014-07-23 22:06:44] ICA looking for ANU 10c4:ea60 but found 8086:1c2d instead
[2014-07-23 22:06:44] ICA looking for BLT 0403:6001 but found 8086:1c2d instead
[2014-07-23 22:06:44] ICA looking for LLT 0403:6001 but found 8086:1c2d instead
[2014-07-23 22:06:44] ICA looking for CMR 0403:6014 but found 8086:1c2d instead
[2014-07-23 22:06:44] ICA looking for CMR 0403:8350 but found 8086:1c2d instead
[2014-07-23 22:06:44] ICA looking for ICA 067b:2303 but found 8086:1c26 instead
[2014-07-23 22:06:44] ICA looking for AMU 10c4:ea60 but found 8086:1c26 instead
[2014-07-23 22:06:44] ICA looking for LIN 10c4:ea60 but found 8086:1c26 instead
[2014-07-23 22:06:44] ICA looking for ANU 10c4:ea60 but found 8086:1c26 instead
[2014-07-23 22:06:44] ICA looking for BLT 0403:6001 but found 8086:1c26 instead
[2014-07-23 22:06:44] ICA looking for LLT 0403:6001 but found 8086:1c26 instead
[2014-07-23 22:06:44] ICA looking for CMR 0403:6014 but found 8086:1c26 instead
[2014-07-23 22:06:44] ICA looking for CMR 0403:8350 but found 8086:1c26 instead
[2014-07-23 22:06:44] ICA looking for ICA 067b:2303 but found 0489:e00f instead
[2014-07-23 22:06:44] ICA looking for AMU 10c4:ea60 but found 0489:e00f instead
[2014-07-23 22:06:44] ICA looking for LIN 10c4:ea60 but found 0489:e00f instead
[2014-07-23 22:06:44] ICA looking for ANU 10c4:ea60 but found 0489:e00f instead
[2014-07-23 22:06:44] ICA looking for BLT 0403:6001 but found 0489:e00f instead
[2014-07-23 22:06:44] ICA looking for LLT 0403:6001 but found 0489:e00f instead
[2014-07-23 22:06:44] ICA looking for CMR 0403:6014 but found 0489:e00f instead
[2014-07-23 22:06:44] ICA looking for CMR 0403:8350 but found 0489:e00f instead
[2014-07-23 22:06:44] ICA looking for ICA 067b:2303 but found 04d8:00de instead
[2014-07-23 22:06:44] ICA looking for AMU 10c4:ea60 but found 04d8:00de instead
[2014-07-23 22:06:44] ICA looking for LIN 10c4:ea60 but found 04d8:00de instead
[2014-07-23 22:06:44] ICA looking for ANU 10c4:ea60 but found 04d8:00de instead
[2014-07-23 22:06:44] ICA looking for BLT 0403:6001 but found 04d8:00de instead
[2014-07-23 22:06:44] ICA looking for LLT 0403:6001 but found 04d8:00de instead
[2014-07-23 22:06:44] ICA looking for CMR 0403:6014 but found 04d8:00de instead
[2014-07-23 22:06:44] ICA looking for CMR 0403:8350 but found 04d8:00de instead
[2014-07-23 22:06:44] ICA looking for ICA 067b:2303 but found 05ca:18c0 instead
[2014-07-23 22:06:44] ICA looking for AMU 10c4:ea60 but found 05ca:18c0 instead
[2014-07-23 22:06:44] ICA looking for LIN 10c4:ea60 but found 05ca:18c0 instead
[2014-07-23 22:06:44] ICA looking for ANU 10c4:ea60 but found 05ca:18c0 instead
[2014-07-23 22:06:44] ICA looking for BLT 0403:6001 but found 05ca:18c0 instead
[2014-07-23 22:06:44] ICA looking for LLT 0403:6001 but found 05ca:18c0 instead
[2014-07-23 22:06:44] ICA looking for CMR 0403:6014 but found 05ca:18c0 instead
[2014-07-23 22:06:44] ICA looking for CMR 0403:8350 but found 05ca:18c0 instead
[2014-07-23 22:06:44] ICA looking for ICA 067b:2303 but found 8087:0024 instead
[2014-07-23 22:06:44] ICA looking for AMU 10c4:ea60 but found 8087:0024 instead
[2014-07-23 22:06:44] ICA looking for LIN 10c4:ea60 but found 8087:0024 instead
[2014-07-23 22:06:44] ICA looking for ANU 10c4:ea60 but found 8087:0024 instead
[2014-07-23 22:06:44] ICA looking for BLT 0403:6001 but found 8087:0024 instead
[2014-07-23 22:06:44] ICA looking for LLT 0403:6001 but found 8087:0024 instead
[2014-07-23 22:06:44] ICA looking for CMR 0403:6014 but found 8087:0024 instead
[2014-07-23 22:06:44] ICA looking for CMR 0403:8350 but found 8087:0024 instead
[2014-07-23 22:06:44] ICA looking for ICA 067b:2303 but found 8087:0024 instead
[2014-07-23 22:06:44] ICA looking for AMU 10c4:ea60 but found 8087:0024 instead
[2014-07-23 22:06:44] ICA looking for LIN 10c4:ea60 but found 8087:0024 instead
[2014-07-23 22:06:44] ICA looking for ANU 10c4:ea60 but found 8087:0024 instead
[2014-07-23 22:06:44] ICA looking for BLT 0403:6001 but found 8087:0024 instead
[2014-07-23 22:06:44] ICA looking for LLT 0403:6001 but found 8087:0024 instead
[2014-07-23 22:06:44] ICA looking for CMR 0403:6014 but found 8087:0024 instead
[2014-07-23 22:06:44] ICA looking for CMR 0403:8350 but found 8087:0024 instead
[2014-07-23 22:06:44] ICA looking for ICA 067b:2303 but found 8087:07d6 instead
[2014-07-23 22:06:44] ICA looking for AMU 10c4:ea60 but found 8087:07d6 instead
[2014-07-23 22:06:44] ICA looking for LIN 10c4:ea60 but found 8087:07d6 instead
[2014-07-23 22:06:44] ICA looking for ANU 10c4:ea60 but found 8087:07d6 instead
[2014-07-23 22:06:44] ICA looking for BLT 0403:6001 but found 8087:07d6 instead
[2014-07-23 22:06:44] ICA looking for LLT 0403:6001 but found 8087:07d6 instead
[2014-07-23 22:06:44] ICA looking for CMR 0403:6014 but found 8087:07d6 instead
[2014-07-23 22:06:44] ICA looking for CMR 0403:8350 but found 8087:07d6 instead
[2014-07-23 22:06:44] ICA looking for ICA 067b:2303 but found 1033:0194 instead
[2014-07-23 22:06:44] ICA looking for AMU 10c4:ea60 but found 1033:0194 instead
[2014-07-23 22:06:44] ICA looking for LIN 10c4:ea60 but found 1033:0194 instead
[2014-07-23 22:06:44] ICA looking for ANU 10c4:ea60 but found 1033:0194 instead
[2014-07-23 22:06:44] ICA looking for BLT 0403:6001 but found 1033:0194 instead
[2014-07-23 22:06:44] ICA looking for LLT 0403:6001 but found 1033:0194 instead
[2014-07-23 22:06:44] ICA looking for CMR 0403:6014 but found 1033:0194 instead
[2014-07-23 22:06:44] ICA looking for CMR 0403:8350 but found 1033:0194 instead
[2014-07-23 22:06:44] USB scan devices: checking for ICA devices
[2014-07-23 22:06:45] ICA looking for ICA 067b:2303 but found 8086:1c2d instead
[2014-07-23 22:06:45] ICA looking for AMU 10c4:ea60 but found 8086:1c2d instead
[2014-07-23 22:06:45] ICA looking for LIN 10c4:ea60 but found 8086:1c2d instead
[2014-07-23 22:06:45] ICA looking for ANU 10c4:ea60 but found 8086:1c2d instead
[2014-07-23 22:06:45] ICA looking for BLT 0403:6001 but found 8086:1c2d instead
[2014-07-23 22:06:45] ICA looking for LLT 0403:6001 but found 8086:1c2d instead
[2014-07-23 22:06:45] ICA looking for CMR 0403:6014 but found 8086:1c2d instead
[2014-07-23 22:06:45] ICA looking for CMR 0403:8350 but found 8086:1c2d instead
[2014-07-23 22:06:45] ICA looking for ICA 067b:2303 but found 8086:1c26 instead
[2014-07-23 22:06:45] ICA looking for AMU 10c4:ea60 but found 8086:1c26 instead
[2014-07-23 22:06:45] ICA looking for LIN 10c4:ea60 but found 8086:1c26 instead
[2014-07-23 22:06:45] ICA looking for ANU 10c4:ea60 but found 8086:1c26 instead
[2014-07-23 22:06:45] ICA looking for BLT 0403:6001 but found 8086:1c26 instead
[2014-07-23 22:06:45] ICA looking for LLT 0403:6001 but found 8086:1c26 instead
[2014-07-23 22:06:45] ICA looking for CMR 0403:6014 but found 8086:1c26 instead
[2014-07-23 22:06:45] ICA looking for CMR 0403:8350 but found 8086:1c26 instead
[2014-07-23 22:06:45] ICA looking for ICA 067b:2303 but found 0489:e00f instead
[2014-07-23 22:06:45] ICA looking for AMU 10c4:ea60 but found 0489:e00f instead
[2014-07-23 22:06:45] ICA looking for LIN 10c4:ea60 but found 0489:e00f instead
[2014-07-23 22:06:45] ICA looking for ANU 10c4:ea60 but found 0489:e00f instead
[2014-07-23 22:06:45] ICA looking for BLT 0403:6001 but found 0489:e00f instead
[2014-07-23 22:06:45] ICA looking for LLT 0403:6001 but found 0489:e00f instead
[2014-07-23 22:06:45] ICA looking for CMR 0403:6014 but found 0489:e00f instead
[2014-07-23 22:06:45] ICA looking for CMR 0403:8350 but found 0489:e00f instead
[2014-07-23 22:06:45] ICA looking for ICA 067b:2303 but found 04d8:00de instead
[2014-07-23 22:06:45] ICA looking for AMU 10c4:ea60 but found 04d8:00de instead
[2014-07-23 22:06:45] ICA looking for LIN 10c4:ea60 but found 04d8:00de instead
[2014-07-23 22:06:45] ICA looking for ANU 10c4:ea60 but found 04d8:00de instead
[2014-07-23 22:06:45] ICA looking for BLT 0403:6001 but found 04d8:00de instead
[2014-07-23 22:06:45] ICA looking for LLT 0403:6001 but found 04d8:00de instead
[2014-07-23 22:06:45] ICA looking for CMR 0403:6014 but found 04d8:00de instead
[2014-07-23 22:06:45] ICA looking for CMR 0403:8350 but found 04d8:00de instead
[2014-07-23 22:06:45] ICA looking for ICA 067b:2303 but found 05ca:18c0 instead
[2014-07-23 22:06:45] ICA looking for AMU 10c4:ea60 but found 05ca:18c0 instead
[2014-07-23 22:06:45] ICA looking for LIN 10c4:ea60 but found 05ca:18c0 instead
[2014-07-23 22:06:45] ICA looking for ANU 10c4:ea60 but found 05ca:18c0 instead
[2014-07-23 22:06:45] ICA looking for BLT 0403:6001 but found 05ca:18c0 instead
[2014-07-23 22:06:45] ICA looking for LLT 0403:6001 but found 05ca:18c0 instead
[2014-07-23 22:06:45] ICA looking for CMR 0403:6014 but found 05ca:18c0 instead
[2014-07-23 22:06:45] ICA looking for CMR 0403:8350 but found 05ca:18c0 instead
[2014-07-23 22:06:45] ICA looking for ICA 067b:2303 but found 8087:0024 instead
[2014-07-23 22:06:45] ICA looking for AMU 10c4:ea60 but found 8087:0024 instead
[2014-07-23 22:06:45] ICA looking for LIN 10c4:ea60 but found 8087:0024 instead
[2014-07-23 22:06:45] ICA looking for ANU 10c4:ea60 but found 8087:0024 instead
[2014-07-23 22:06:45] ICA looking for BLT 0403:6001 but found 8087:0024 instead
[2014-07-23 22:06:45] ICA looking for LLT 0403:6001 but found 8087:0024 instead
[2014-07-23 22:06:45] ICA looking for CMR 0403:6014 but found 8087:0024 instead
[2014-07-23 22:06:45] ICA looking for CMR 0403:8350 but found 8087:0024 instead
[2014-07-23 22:06:45] ICA looking for ICA 067b:2303 but found 8087:0024 instead
[2014-07-23 22:06:45] ICA looking for AMU 10c4:ea60 but found 8087:0024 instead
[2014-07-23 22:06:45] ICA looking for LIN 10c4:ea60 but found 8087:0024 instead
[2014-07-23 22:06:45] ICA looking for ANU 10c4:ea60 but found 8087:0024 instead
[2014-07-23 22:06:45] ICA looking for BLT 0403:6001 but found 8087:0024 instead
[2014-07-23 22:06:45] ICA looking for LLT 0403:6001 but found 8087:0024 instead
[2014-07-23 22:06:45] ICA looking for CMR 0403:6014 but found 8087:0024 instead
[2014-07-23 22:06:45] ICA looking for CMR 0403:8350 but found 8087:0024 instead
[2014-07-23 22:06:45] ICA looking for ICA 067b:2303 but found 8087:07d6 instead
[2014-07-23 22:06:45] ICA looking for AMU 10c4:ea60 but found 8087:07d6 instead
[2014-07-23 22:06:45] ICA looking for LIN 10c4:ea60 but found 8087:07d6 instead
[2014-07-23 22:06:45] ICA looking for ANU 10c4:ea60 but found 8087:07d6 instead
[2014-07-23 22:06:45] ICA looking for BLT 0403:6001 but found 8087:07d6 instead
[2014-07-23 22:06:45] ICA looking for LLT 0403:6001 but found 8087:07d6 instead
[2014-07-23 22:06:45] ICA looking for CMR 0403:6014 but found 8087:07d6 instead
[2014-07-23 22:06:45] ICA looking for CMR 0403:8350 but found 8087:07d6 instead
[2014-07-23 22:06:45] ICA looking for ICA 067b:2303 but found 1033:0194 instead
[2014-07-23 22:06:45] ICA looking for AMU 10c4:ea60 but found 1033:0194 instead
[2014-07-23 22:06:45] ICA looking for LIN 10c4:ea60 but found 1033:0194 instead
[2014-07-23 22:06:45] ICA looking for ANU 10c4:ea60 but found 1033:0194 instead
[2014-07-23 22:06:45] ICA looking for BLT 0403:6001 but found 1033:0194 instead
[2014-07-23 22:06:45] ICA looking for LLT 0403:6001 but found 1033:0194 instead
[2014-07-23 22:06:45] ICA looking for CMR 0403:6014 but found 1033:0194 instead
[2014-07-23 22:06:45] ICA looking for CMR 0403:8350 but found 1033:0194 instead
[2014-07-23 22:06:45] USB scan devices: checking for KLN devices
[2014-07-23 22:06:45] KLN looking for KLN 04d8:f60a but found 8086:1c2d instead
[2014-07-23 22:06:45] KLN looking for KLI 04d8:f60a but found 8086:1c2d instead
[2014-07-23 22:06:45] KLN looking for KLN 04d8:f60a but found 8086:1c26 instead
[2014-07-23 22:06:45] KLN looking for KLI 04d8:f60a but found 8086:1c26 instead
[2014-07-23 22:06:45] KLN looking for KLN 04d8:f60a but found 0489:e00f instead
[2014-07-23 22:06:45] KLN looking for KLI 04d8:f60a but found 0489:e00f instead
[2014-07-23 22:06:45] KLN looking for KLN 04d8:f60a but found 04d8:00de instead
[2014-07-23 22:06:45] KLN looking for KLI 04d8:f60a but found 04d8:00de instead
[2014-07-23 22:06:45] KLN looking for KLN 04d8:f60a but found 05ca:18c0 instead
[2014-07-23 22:06:45] KLN looking for KLI 04d8:f60a but found 05ca:18c0 instead
[2014-07-23 22:06:45] KLN looking for KLN 04d8:f60a but found 8087:0024 instead
[2014-07-23 22:06:45] KLN looking for KLI 04d8:f60a but found 8087:0024 instead
[2014-07-23 22:06:45] KLN looking for KLN 04d8:f60a but found 8087:0024 instead
[2014-07-23 22:06:45] KLN looking for KLI 04d8:f60a but found 8087:0024 instead
[2014-07-23 22:06:45] KLN looking for KLN 04d8:f60a but found 8087:07d6 instead
[2014-07-23 22:06:45] KLN looking for KLI 04d8:f60a but found 8087:07d6 instead
[2014-07-23 22:06:45] KLN looking for KLN 04d8:f60a but found 1033:0194 instead
[2014-07-23 22:06:45] KLN looking for KLI 04d8:f60a but found 1033:0194 instead
[2014-07-23 22:06:45] USB scan devices: checking for DRB devices
[2014-07-23 22:06:45] DRB looking for DRB 03eb:2404 but found 8086:1c2d instead
[2014-07-23 22:06:45] DRB looking for DRB 03eb:2404 but found 8086:1c26 instead
[2014-07-23 22:06:45] DRB looking for DRB 03eb:2404 but found 0489:e00f instead
[2014-07-23 22:06:45] DRB looking for DRB 03eb:2404 but found 04d8:00de instead
[2014-07-23 22:06:45] DRB looking for DRB 03eb:2404 but found 05ca:18c0 instead
[2014-07-23 22:06:45] DRB looking for DRB 03eb:2404 but found 8087:0024 instead
[2014-07-23 22:06:45] DRB looking for DRB 03eb:2404 but found 8087:0024 instead
[2014-07-23 22:06:45] DRB looking for DRB 03eb:2404 but found 8087:07d6 instead
[2014-07-23 22:06:45] DRB looking for DRB 03eb:2404 but found 1033:0194 instead
[2014-07-23 22:06:45] Pushing sem post to thread 0
[2014-07-23 22:06:45] Waiting on sem in miner thread
[2014-07-23 22:06:45] Probing for an alive pool
[2014-07-23 22:06:45] Popping work from get queue to get work
[2014-07-23 22:06:45] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:06:46] Select timeout/failed connect
[2014-07-23 22:06:47] Select timeout/failed connect
[2014-07-23 22:06:47] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:06:47] Initiate stratum failed
[2014-07-23 22:06:52] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:06:53] Select timeout/failed connect
[2014-07-23 22:06:54] Select timeout/failed connect
[2014-07-23 22:06:54] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:06:54] Initiate stratum failed
[2014-07-23 22:06:55] Waiting for work to be available from pools.
[2014-07-23 22:06:59] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:00] Select timeout/failed connect
[2014-07-23 22:07:01] Select timeout/failed connect
[2014-07-23 22:07:01] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:01] Initiate stratum failed
[2014-07-23 22:07:06] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:07] Select timeout/failed connect
[2014-07-23 22:07:08] Select timeout/failed connect
[2014-07-23 22:07:08] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:08] Initiate stratum failed
[2014-07-23 22:07:13] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:14] Select timeout/failed connect
[2014-07-23 22:07:15] Select timeout/failed connect
[2014-07-23 22:07:15] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:15] Initiate stratum failed
[2014-07-23 22:07:20] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:21] Select timeout/failed connect
[2014-07-23 22:07:22] Select timeout/failed connect
[2014-07-23 22:07:22] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:22] Initiate stratum failed
[2014-07-23 22:07:27] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:28] Select timeout/failed connect
[2014-07-23 22:07:29] Select timeout/failed connect
[2014-07-23 22:07:29] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:30] Initiate stratum failed
[2014-07-23 22:07:35] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:36] Select timeout/failed connect
[2014-07-23 22:07:37] Select timeout/failed connect
[2014-07-23 22:07:37] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:37] Initiate stratum failed
[2014-07-23 22:07:42] Testing pool stratum+tcp://stratum.bitcoin.cz:3333
[2014-07-23 22:07:43] Select timeout/failed connect
[2014-07-23 22:07:44] Select timeout/failed connect
[2014-07-23 22:07:44] Failed to connect to stratum on stratum.bitcoin.cz:3333
[2014-07-23 22:07:44] Initiate stratum failed
[2014-07-23 22:07:45] No servers were found that could be used to get work from.
[2014-07-23 22:07:45] Please check the details from the list below of the servers you have input
[2014-07-23 22:07:45] Most likely you have input the wrong URL, forgotten to add a port, or have not set up workers
[2014-07-23 22:07:45] Pool: 0 URL: stratum+tcp://stratum.bitcoin.cz:3333 User: workernamehere Password: password
[2014-07-23 22:07:45] No servers could be used! Exiting.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: os2sam on July 23, 2014, 09:50:42 PM

Is there any other benefit to getwork besides deepbit?

None remains. That's why you can build cgminer without getwork support these days with the --disable-libcurl option when building it for a much leaner build for stratum support only.

os2sam

legendary

Activity: 3583

Merit: 1094

Think for yourself

Quote from: -ck on July 23, 2014, 09:22:06 PM

Quote from: os2sam on July 23, 2014, 08:46:10 PM

Quote from: -ck on July 22, 2014, 07:53:53 PM

Quote from: os2sam on July 22, 2014, 07:45:07 PM

Why does CGMiner keep identifying my Jalapeno as a BXM? I have to start a CGMiner instance first for my Jalapeno with a --usb bas:1 and then start the other instances for my other miners. It's not a big deal but 4.2.3 did this and 4.4.2 still does, but if I have to restart it I have to shut all instances down and restart them in the correct order.

Wow you still run one of those?

Presumably it's because they both use the same communication chip and I never tested this combination of hardware since my Jalapeno has long since been gotten rid of. You should try disabling the bxm instead of enabling the others with --usb BXM:0

OK, I'll add that to my command line.

I also see that my worker on deepbit crashes every day or two now with 4.4.2. 4.2.3 was stable.

Try the debug build on that then please, though it's likely to be deep in the ageing getwork code...

http://ck.kolivas.org/apps/cgminer/debug/

Is there any other benefit to getwork besides deepbit?

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: os2sam on July 23, 2014, 08:46:10 PM

Quote from: -ck on July 22, 2014, 07:53:53 PM

Quote from: os2sam on July 22, 2014, 07:45:07 PM

Why does CGMiner keep identifying my Jalapeno as a BXM? I have to start a CGMiner instance first for my Jalapeno with a --usb bas:1 and then start the other instances for my other miners. It's not a big deal but 4.2.3 did this and 4.4.2 still does, but if I have to restart it I have to shut all instances down and restart them in the correct order.

Wow you still run one of those?

Presumably it's because they both use the same communication chip and I never tested this combination of hardware since my Jalapeno has long since been gotten rid of. You should try disabling the bxm instead of enabling the others with --usb BXM:0

OK, I'll add that to my command line.

I also see that my worker on deepbit crashes every day or two now with 4.4.2. 4.2.3 was stable.

Try the debug build on that then please, though it's likely to be deep in the ageing getwork code...

http://ck.kolivas.org/apps/cgminer/debug/

os2sam

legendary

Activity: 3583

Merit: 1094

Think for yourself

Quote from: -ck on July 22, 2014, 07:53:53 PM

Quote from: os2sam on July 22, 2014, 07:45:07 PM

Why does CGMiner keep identifying my Jalapeno as a BXM? I have to start a CGMiner instance first for my Jalapeno with a --usb bas:1 and then start the other instances for my other miners. It's not a big deal but 4.2.3 did this and 4.4.2 still does, but if I have to restart it I have to shut all instances down and restart them in the correct order.

Wow you still run one of those?

Presumably it's because they both use the same communication chip and I never tested this combination of hardware since my Jalapeno has long since been gotten rid of. You should try disabling the bxm instead of enabling the others with --usb BXM:0

OK, I'll add that to my command line.

I also see that my worker on deepbit crashes every day or two now with 4.4.2. 4.2.3 was stable.

J4bberwock

hero member

Activity: 840

Merit: 1000

Quote from: -ck on July 17, 2014, 12:49:50 AM

New release: Version 4.4.2, 17th July 2014

A stable/bugfix/driver update release for accumulated issues while I was away.

Human readable changelog:

- Rbox now accepts frequencies up to 400

Thanks for this one, I'm now able to test my overvolting. Still disappointing at the moment, I'm only getting 37GH and almost 0 HW errors with a frequency of 320. 340 looks stable too, I'll let it run all night lo g at 336 to check what it says.
When I tried to compile after changing the value in Icarus driver, it was still resetting to 270 if a value over 290 was entered.

Jay_Pal

legendary

Activity: 1493

Merit: 1003

Quote from: -ck on July 22, 2014, 07:53:53 PM

Quote from: os2sam on July 22, 2014, 07:45:07 PM

Why does CGMiner keep identifying my Jalapeno as a BXM? I have to start a CGMiner instance first for my Jalapeno with a --usb bas:1 and then start the other instances for my other miners. It's not a big deal but 4.2.3 did this and 4.4.2 still does, but if I have to restart it I have to shut all instances down and restart them in the correct order.

Wow you still run one of those?

Presumably it's because they both use the same communication chip and I never tested this combination of hardware since my Jalapeno has long since been gotten rid of. You should try disabling the bxm instead of enabling the others with --usb BXM:0

I also run a Jalapeño but it reports as BAJ

Code:

cgminer version 4.4.1 - Started: [2014-07-22 23:02:16]
----------------------------------------------------------------------------------------------------
(5s):32.93G (1m):31.49G (5m):31.39G (15m):31.37G (avg):31.27Gh/s
A:319422 R:1023 HW:15774 WU:424.9/m | ST: 88 SS: 0 NB: 80 LW: 659492 GF: 0 RF: 0
Connected to diff 25 with stratum as user
Block: 3b15cdd8... Diff:17.3G Started: [11:28:41] Best share: 1.59M
----------------------------------------------------------------------------------------------------
[U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
0: BAJ FTWS9K4J: max 43C 0.99V | 4.857G / 4.659Gh/s WU:64.8/m A:48461 R: 98 HW: 42
1: BXM 0 : | 4.307G / 4.253Gh/s WU:60.0/m A:44138 R:365 HW: 0
2: BXM 1 : | 4.063G / 4.060Gh/s WU:56.9/m A:41083 R:162 HW: 0
3: BXM 2 : | 4.368G / 4.351Gh/s WU:61.1/m A:47006 R:184 HW: 0
6: ANU 2 : | 2.062G / 2.023Gh/s WU:27.1/m A:20849 R: 0 HW:1408
7: ANU 3 : | 1.778G / 2.006Gh/s WU:26.7/m A:19406 R: 79 HW:1871
8: ANU 4 : | 2.002G / 1.867Gh/s WU:21.5/m A:15847 R: 29 HW:5686
9: ANU 5 : | 2.072G / 2.068Gh/s WU:29.0/m A:23488 R: 29 HW: 219
10: ANU 6 : | 2.028G / 1.970Gh/s WU:25.0/m A:19242 R: 48 HW:2834
11: ANU 7 : | 2.052G / 1.952Gh/s WU:24.6/m A:14848 R: 29 HW:2664
12: ANU 8 : | 1.855G / 2.058Gh/s WU:28.2/m A:10385 R: 0 HW: 199
----------------------------------------------------------------------------------------------------
[2014-07-23 11:37:44] Accepted 079bd82b Diff 34/25 ANU 6 pool 0
[2014-07-23 11:37:47] Accepted 0424cc8f Diff 62/25 BXM 2 pool 0
[2014-07-23 11:37:53] Accepted 0319cacb Diff 83/25 BXM 0 pool 0
[2014-07-23 11:38:04] Accepted 04700042 Diff 58/25 ANU 7 pool 0
[2014-07-23 11:38:14] Accepted 05822b1f Diff 46/25 BXM 1 pool 0
[2014-07-23 11:38:33] Accepted 0321818c Diff 82/25 ANU 2 pool 0
[2014-07-23 11:38:34] Accepted d8185714 Diff 303/25 ANU 8 pool 0
[2014-07-23 11:38:39] Accepted 073888e7 Diff 35/25 BXM 1 pool 0
[2014-07-23 11:38:41] Accepted 0838dae7 Diff 31/25 ANU 4 pool 0
[2014-07-23 11:38:51] Accepted 01f3a8a5 Diff 131/25 BXM 0 pool 0
[2014-07-23 11:38:52] Accepted 482b9700 Diff 908/25 BXM 2 pool 0
[2014-07-23 11:38:56] Accepted 017d39c2 Diff 172/25 ANU 5 pool 0
[2014-07-23 11:39:03] Accepted 054a6d96 Diff 48/25 ANU 7 pool 0
[2014-07-23 11:39:04] Accepted 016dacdc Diff 179/25 BAJ 0 pool 0
[2014-07-23 11:39:07] Accepted 05dde3fc Diff 44/25 BAJ 0 pool 0
[2014-07-23 11:39:11] Accepted 07182656 Diff 36/25 ANU 5 pool 0
[2014-07-23 11:39:12] Accepted 0427d46e Diff 62/25 ANU 6 pool 0

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: os2sam on July 22, 2014, 07:45:07 PM

Why does CGMiner keep identifying my Jalapeno as a BXM? I have to start a CGMiner instance first for my Jalapeno with a --usb bas:1 and then start the other instances for my other miners. It's not a big deal but 4.2.3 did this and 4.4.2 still does, but if I have to restart it I have to shut all instances down and restart them in the correct order.

Wow you still run one of those?

Presumably it's because they both use the same communication chip and I never tested this combination of hardware since my Jalapeno has long since been gotten rid of. You should try disabling the bxm instead of enabling the others with --usb BXM:0

os2sam

legendary

Activity: 3583

Merit: 1094

Think for yourself

Quote from: tolip_wen on July 22, 2014, 07:44:27 PM

I did not read the whole thread.

Oh, come on, read the whole thread. It's very edifying.

os2sam

legendary

Activity: 3583

Merit: 1094

Think for yourself

Why does CGMiner keep identifying my Jalapeno as a BXM? I have to start a CGMiner instance first for my Jalapeno with a --usb bas:1 and then start the other instances for my other miners. It's not a big deal but 4.2.3 did this and 4.4.2 still does, but if I have to restart it I have to shut all instances down and restart them in the correct order.

tolip_wen

sr. member

Activity: 386

Merit: 250

Please forgive if this has been posted here before.
I admit it is a drive by post, I did not read the whole thread.
I did search, I know similar exists, I blunder on anyways!

How to build cgminer on a KnCMiner Neptune while it hashes

My directory tree is as follows

/config
/config/opkg.cache
/config/other
/config/other/cgminer
/config/other/jansson-2.5

If ya dosent likes it season to taste...

First you need a build environment.
I save the downloaded opkg files for faster reconfig.
(better ways exist but I have not implimented yet, I just wait for reinstall of opkg files)

Code:

mkdir /config/opkg.cache

cat >/etc/opkg/feeds.conf <<\EOF
src/gz noarch http://feeds.angstrom-distribution.org/feeds/v2013.06/ipk/eglibc/all/
src/gz base http://feeds.angstrom-distribution.org/feeds/v2013.06/ipk/eglibc/armv7ahf-vfp-neon/base/
src/gz beaglebone http://feeds.angstrom-distribution.org/feeds/v2013.06/ipk/eglibc/armv7ahf-vfp-neon/machine/beaglebone/
EOF

opkg --cache /config/opkg.cache install update-alternatives
opkg --cache /config/opkg.cache install automake autoconf make gcc cpp binutils git less pkgconfig-dev ncurses-dev libtool nano bash i2c-tools-dev
while ! opkg --cache /config/opkg.cache install libcurl-dev; do true; done

ln -s /usr/bin/arm-angstrom-linux-gnueabi-gcc /usr/bin/gcc
ln -s /usr/bin/arm-angstrom-linux-gnueabi-ar /usr/bin/ar
ln -s /usr/bin/arm-angstrom-linux-gnueabi-nm /usr/bin/nm

At this point most compile stuff kinda works.
You can skip the symlinks if you want to modify every Makefile and ./config you will probably ever use Wink

You may need more symlinks to default program names for other build projects.

The following scripts do not assume symlinks exist

I struggled with errors compiling the jansson-2.5 that comes with the KnC cgminer git.
Operator error is suspected!

I forced my intentions

Code:

mkdir /config/other
cd /config/other
curl http://www.digip.org/jansson/releases/jansson-2.5.tar.bz2 | tar -xjvp
cd /config/other/jansson-2.5
./configure --prefix=/usr CC=arm-angstrom-linux-gnueabi-gcc NM=arm-angstrom-linux-gnueabi-nm
make install && ldconfig
cd /config/other

next need to grab bleeding edge cgminer code from KnC git

Code:

cd /config/other
git clone git://github.com/KnCMiner/cgminer
cd cgminer

Skip this part if my jansson-2.5 challenge was operator error

Code:

cd /config/other/cgminer/compat
mv jansson-2.5 jansson-2.5.orig
cp -r /config/other/jansson-2.5 .
cd ..

finally try and build cgminer

Code:

autoconf
./configure CC=arm-angstrom-linux-gnueabi-gcc NM=arm-angstrom-linux-gnueabi-nm AR=arm-angstrom-linux-gnueabi-ar --enable-knc
make cgminer
make api-example
ls -alrt

If everything worked you should see new 'cgminer' and 'api-example' at the bottom of dir list.

You can run it in place or copy it over the original.
The following will preserve the original as /usr/bin/cgminer.orig and replace existing with new and run it.
This is also needed after reboot to run new cgminer

Code:

/etc/init.d/cgminer.sh stop
mv /usr/bin/cgminer /usr/bin/cgminer.orig
cp /config/other/cgminer/cgminer /usr/bin
/etc/init.d/cgminer.sh restart

At this point IF IT WORKS it is running
wait a few for cgminer to start then ....

'screen -r'

same as always
N'Joy!

HUGE disclaimer, above scripts are from memory, cut, and paste.
There may exist errors, I am not gonna rerun it and see until I have too!

YMMV

EDIT
The build stuff is swiped from the README.ASIC in bfgminer.
I did not figure out any of it.

Jay_Pal

legendary

Activity: 1493

Merit: 1003

Quote from: techman05 on July 15, 2014, 01:33:34 PM

Tell your friend to go on amazon if they want eroupters. I had someone buy off a bunch of my set a short while ago though I didn't ask why. I kept hoping there was life after bitcoin for eroupters but nothing ever passed my way (like folding at home support or bonzi gpu applications [which do seti and a bunch of other group processing programs]

Ankers work for most but they are 3.0 and will cause pain if you plug in a 3.0 port (zombies and disappearing devices. I'm hoping 3.0 will be bitcoin friendly if people start building on its spec though.

Post again once you get your hubs. I'd hope that'll be the issue and your friend will get their free eroupter.

Got the hubs and they're working great!
The Ants even got recognized without the BE's!!!
BTW, they are 3.0 but I've kept the cables in the box and plugged 2.0 cables, since I have no 3.0 USB ports on this computer.

Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 79. (Read 5805508 times)