OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1

[kano]

Yeah most of that is in the README ... that's why the message says to read it

[LeviWalker]

Cross compiling is not for the inexperienced. I suggest you take the top off the cointerror, pull out the usb cables from the beaglebone controller and plug them into any pc running linux. The device works fine from any controller running cgminer.

I have two of these myself and was just thinking the same thing. Mine actually run fine (good actually) so I dont know if there would be anything to gain other than experience by doing this. I am running your CKPool in the same rack as the miners so what do you think about running these with cgminer on the server? Its a virtual environment so I can easily add another server for mining only if that would be better.

[-ck]

Cross compiling is not for the inexperienced. I suggest you take the top off the cointerror, pull out the usb cables from the beaglebone controller and plug them into any pc running linux. The device works fine from any controller running cgminer.

I have two of these myself and was just thinking the same thing. Mine actually run fine (good actually) so I dont know if there would be anything to gain other than experience by doing this. I am running your CKPool in the same rack as the miners so what do you think about running these with cgminer on the server? Its a virtual environment so I can easily add another server for mining only if that would be better.

Up until my cointerra turned into a blast furnace and tried to weld itself to my shelf, I ran it off a PC instead of the BBB built in and found the USB communications much more reliable where errors were virtually non existent and latency was lower, so I definitely think there's an advantage (provided you have ridiculously cheap electricity, otherwise these make great boat anchors).

[LeviWalker]

Up until my cointerra turned into a blast furnace and tried to weld itself to my shelf, I ran it off a PC instead of the BBB built in and found the USB communications much more reliable where errors were virtually non existent and latency was lower, so I definitely think there's an advantage (provided you have ridiculously cheap electricity, otherwise these make great boat anchors).

Thanks I think I will give that a shot today.

[opentoe]

My antminer S5's aren't shutting down when they hit 80C or above. Could this be a cgminer issue? The temps start runaway when you already have been mining and get disconnected from the pool/network. Even if the miner isn't hashing the fan will slow down and the temps will start to run away. Soon as I saw 90c I think it was I powered mine off right away. Now, if you turn on the miner from the start with no connection to a pool it will be fine. This only happens while you were hashing then get disconnected. What's really weird is my Dad also has an S5 and the same thing happened to him. He was hashing on the Guild and he heard the beeping, walked over to his miners and the fan was not spinning. Then he felt the heat coming off the top and smelled that metal heat type smell and quickly powered off both miners. If we both weren't home and this happened we'd be in trouble, possibly a fire? I also posted this on the Official S5 page, hopefully there will be some kind of fix. I tried using M's monitor program but that only gives you an alert if the temp goes over a certain amount. It doesn't power it off.

Was told this issue is probably in the bitmaintech driver code and they need to resolve it.

[-ck]

My antminer S5's aren't shutting down when they hit 80C or above.

Was told this issue is probably in the bitmaintech driver code and they need to resolve it.

This.

[opentoe]

10-4

[opentoe]

What does this mean? I'm grabbing it from the output of cgminer. I only have two pools setup and the third one is a blank. Is that what it is trying to test, the third one that has nothing in it?



 [2015-03-20 23:16:33] (5s):1.426T (1m):669.1G (5m):482.2G (15m):230.1G (avg):1.132Th/s
[2015-03-20 23:16:34] Testing pool
 [2015-03-20 23:16:34] HTTP request failed: <url> malformed
 [2015-03-20 23:16:34] Failed to getaddrinfo for stratum+tcp://:(null)
[2015-03-20 23:16:36] Submitting share 00000000 to pool 0
 [2015-03-20 23:16:36] Accepted 000000e0 Diff 0/1024 BTM 0 pool 0
 [2015-03-20 23:16:38] (5s):1.399T (1m):656.7G (5m):480.3G (15m):229.8G (avg):1.129Th/s

[Mikestang]

My antminer S5's aren't shutting down when they hit 80C or above.

Was told this issue is probably in the bitmaintech driver code and they need to resolve it.

This.

Isn't that a safety feature?  Aren't they supposed to shut down around 80*C?

[os2sam]

I've just received to BFL Monarch's.  They identify themselves to Windoze as BitFORCE SHA256 SC and CGMiner 4.9.1 identifies them as a BAS.  Then I get a steady stream of errors saying "RequestQueJobStatus failed <err=0 amt=20>.
Thanks,
Sam

[-ck]

They identify themselves to Windoze as BitFORCE SHA256 SC and CGMiner 4.9.1 identifies them as a BAS. 

What a pain. That's the identifier for their 65nm hardware. No idea why they put it on mofarchs as well

65nm so far showed up as:
"BitFORCE SHA256 SC"

while 28nm as:
"BitFORCE SC-28nm"

The old FPGA showed up as:
"BitFORCE SHA256"
and then 28nm started showing up as this too.

Now they're mixing the 65nm identifiers with their "new"er hardware. If BFL didn't have bigger problems, I'd say they were doing it deliberately, but this is probably just plain screwup on their part I guess.

What does the iManufacturer field list?

[os2sam]

They identify themselves to Windoze as BitFORCE SHA256 SC and CGMiner 4.9.1 identifies them as a BAS.  

What does the iManufacturer field list?

Is this what your asking for?

Code:

C:\cgm491>CGMINER -D -T
 [2015-03-21 17:30:07] Started cgminer 4.9.1

snip

[2015-03-21 17:30:08] USB scan devices: checking for BAS devices
[2015-03-21 17:30:08] BAS looking for BAS 0403:6014 but found 8086:27ca instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27ca instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27ca instead
[2015-03-21 17:30:08] BAS looking for BAS 0403:6014 but found 8086:27c9 instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27c9 instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27c9 instead
[2015-03-21 17:30:08] BAS looking for BAS 0403:6014 but found 8086:27cb instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27cb instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27cb instead
[2015-03-21 17:30:08] BAS looking for BAS 0403:6014 but found 8086:27c8 instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27c8 instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27c8 instead
[2015-03-21 17:30:08] BAS looking for BAS 0403:6014 but found 8086:27cc instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27cc instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27cc instead
[2015-03-21 17:30:08] BAS looking for and found BAS 0403:6014
[2015-03-21 17:30:08] USB lock BitForceSC 5-1
[2015-03-21 17:30:08] RES: BitForceSC (5:1) lock=1
[2015-03-21 17:30:08] USB res lock BitForceSC 5-1
[2015-03-21 17:30:08] RES: BitForceSC (5:1) lock ok=1
[2015-03-21 17:30:08] USB init - BAS device 5:1 usbver=0200 prod='BitFORCE SHA256 SC' manuf='BUTTERFLY LABS' serial='FTYM9T5M'
[2015-03-21 17:30:08] BAS0: reset got err 0
[2015-03-21 17:30:08] BAS: cgid 0 SetLatency got err 0
[2015-03-21 17:30:08] BAS0: setdata got err 0
[2015-03-21 17:30:08] BAS0: setbaud got err 0
[2015-03-21 17:30:08] BAS0: setflowctrl got err 0
[2015-03-21 17:30:08] BAS0: setmodemctrl got err 0
[2015-03-21 17:30:08] BAS0: purgetx got err 0
[2015-03-21 17:30:08] BAS0: purgerx got err 0
[2015-03-21 17:30:08] BitForceSC detect (5:1) Warning unknown firmware ' 1.4.30x00' using Ver2
[2015-03-21 17:30:08] BAS: cgid 0 SetLatency got err 0
[2015-03-21 17:30:08] BitForceSC (5:1) identified as: 'BAS'
[2015-03-21 17:30:08] BAS looking for BAS 0403:6014 but found 058f:6377 instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 058f:6377 instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 058f:6377 instead

[-ck]

Is this what you're asking for?

Code:

C:\cgm491>CGMINER -D -T
 [2015-03-21 17:30:07] Started cgminer 4.9.1
[2015-03-21 17:30:08] USB init - BAS device 5:1 usbver=0200 prod='BitFORCE SHA256 SC' manuf='BUTTERFLY LABS' serial='FTYM9T5M'

Yes that's it.

Try this:

http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

[os2sam]

Is this what you're asking for?

Code:

C:\cgm491>CGMINER -D -T
 [2015-03-21 17:30:07] Started cgminer 4.9.1
[2015-03-21 17:30:08] USB init - BAS device 5:1 usbver=0200 prod='BitFORCE SHA256 SC' manuf='BUTTERFLY LABS' serial='FTYM9T5M'

Yes that's it.

Try this:

http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

That did it, it's hashing.
Thanks,
Sam

Edit: So do think this is a fix or a preliminary test?  Also what is the driver instance name for the --usb options?
Thanks a bunch, again.

[-ck]

Edit: So do think this is a fix or a preliminary test?  Also what is the driver instance name for the --usb options?
Thanks a bunch, again.

This code should just become part of the next release. It's still all under the same device name for all bflsc driver devices so BAS. The code was never rewritten to account for variants detected after the fact and black/whitelist them (it would be a massive rewrite and manufacturers have all but made this venture worthless).

[Mikestang]

I am having a bit of difficulty getting solo mining to work.  I run a full node (PIX >8.5), I can mine to pools no problem, so the problem is internal somewhere.

My bitcoin.conf file looks like

Code:

server=1
rpcuser=(name)
rpcpassword=(password)
rpcallowip=127.0.0.1
rpcport=8332

I start cgminer 4.9.0 with

Code:

cgminer.exe -o 127.0.0.1:8332 -u (name) -p (password) --btc-address (address)

and I end up with

and never seem to "connect" and the program closes.

Any ideas what I'm doing wrong?

[os2sam]

I am having a bit of difficulty getting solo mining to work.  I run a full node (PIX >8.5), I can mine to pools no problem, so the problem is internal somewhere.

My bitcoin.conf file looks like

Code:

server=1
rpcuser=(name)
rpcpassword=(password)
rpcallowip=127.0.0.1
rpcport=8332

I start cgminer 4.9.0 with

Code:

cgminer.exe -o 127.0.0.1:8332 -u (name) -p (password) --btc-address (address)

and I end up with

and never seem to "connect" and the program closes.

Any ideas what I'm doing wrong?

Try http:// before the IP address.

cgminer.exe -o http://127.0.0.1:8332 -u (name) -p (password) --btc-address (address)

[Mikestang]

Try http:// before the IP address.

cgminer.exe -o http://127.0.0.1:8332 -u (name) -p (password) --btc-address (address)

Doh, thanks. Working.

[os2sam]

Try http:// before the IP address.

cgminer.exe -o http://127.0.0.1:8332 -u (name) -p (password) --btc-address (address)

Doh, thanks. Working.

Glad to hear it.  Happy solo mining.

[Mikestang]

Glad to hear it.  Happy solo mining.

Thanks, just as a back-up.