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

[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. 

[Anonymailer]

Hi, I notice the last version precompiled for Mac OS X is still at 4.3.3 so I've compiled 4.9.1 for Mac users here:

http://fabulouspanda.co.uk/commandline/cgminer/

[Justbyteme]

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

Hi ck,

  I have a similar problem to the one above and I tried the cgminer.exe too. I read through the readme.txt files but, I could not find any init commands to control the Vcore of the bfl chips. My vcore starts to fluctuate wildly after awhile. Is there any command to lock the Vcore down? I really don't want to damage my bfl miner. I would really appreciate a little help.    Just tell me how much btc I should send.

Thank you,
justbyteme

[-ck]

 I have a similar problem to the one above and I tried the cgminer.exe too. I read through the readme.txt files but, I could not find any init commands to control the Vcore of the bfl chips. My vcore starts to fluctuate wildly after awhile. Is there any command to lock the Vcore down? I really don't want to damage my bfl miner. I would really appreciate a little help.    Just tell me how much btc I should send.

Last I read of the documentation, there is no way to perform software control of the vcore.

[frankenmint]

Hello,

I'm using an m6 board by 100TH mine.  Its connected to a raspberry pi running minepeon. When I run CGminer this happens:

Looks like I got my hands on a peice of the 100TH original mining hardware! (my friend did anyway, good for him)  So now I have it and I'm trying to get it running, but it seems like I get this error from CG Miner every time I try to start it up:  Minion BlackArrow: failed2 to enable GPIO pin 24 interrup
t (13) - you need to be root?




Anyone have ideas or faced this issue before?  I'm running the latest copy of minepeon and have no idea how to fix it.

I tried using Sudo but this is what happens (same result):

Any ideas?

[-ck]

I'm using an m6 board by 100TH mine.  Its connected to a raspberry pi running minepeon. When I run CGminer this happens:

Never heard of such a device, but you're also using an absolutely ancient version of cgminer so if it there is driver code in there (and it appears it may be related to the blackarrow devices) then there may be billions of changes to the code between that old version and the current one.

[kano]

Hello,

I'm using an m6 board by 100TH mine.  Its connected to a raspberry pi running minepeon. When I run CGminer this happens:

...

Any ideas?

Yeah no idea why that's an old version of cgminer in there.

However, the bab driver I wrote should work with all the V1 and V2 butfury boards.
It certainly works with the BlackArrow clone V1 and V2 boards.

The bitfury boards - well it probably works with them, but bitfury expected me to pay them if I wanted to get the driver working on their hardware - so that was a definite "piss off I'm not doing that" back before I first did the bab driver.
i.e. firstly when I requested to BUY hardware from bitfury they rejected me before we even got to discussing a price, and 2ndly later when someone else from bitfury offered to sell me hardware, 2 things 1) the price was above what the boards would have ever made in BTC 2) they wanted to profit heavily in the sell price - so yeah I'm not all that interested is paying a company to then go write a driver for their hardware.

How that relates to an M6 board - I've no idea - and I've never tried it and almost certainly never will.

Edit: I should also add I did some free cgminer work to help them before being rejected when I asked to buy stuff
The cgminer mcast code idea I came up with (Aug 2013) was originally for them (for nothing)

[twebit]

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).

Interesting, this is what I need for my BFL miners and the speed I'm getting is more than bfgminer, the one they recommends us to use.
Mining at Westhash through a proxy and the test version of cgminer doesn't show very good speed ie: 0000's and low temp but using the test version of cgminer alone works great.

I'm in a pickle. I like the speed of the test version of cgminer but it doesn't handle the #xnsub of westhash so I go to the proxy and LP doesn't mine well.   (also when switching pools it crashes)
What to do? Wait for new version?

[Lawsford]

I'm trying to mine with the f2pool but I'm stuck in there : http://image.noelshack.com/fichiers/2015/13/1427583500-1427580065-capture.png
And It's doing nothing. How can I do ?

[Jay_Pal]

I'm trying to mine with the f2pool but I'm stuck in there : http://image.noelshack.com/fichiers/2015/13/1427583500-1427580065-capture.png
And It's doing nothing. How can I do ?

You can start by posting:
- what hardware are you trying to use
- for USB devices under Windows, have you read the rest of the topic regarding Zadig drivers?
- tell if you ever used CGMiner in earlier versions and if it worked

The print screen and your description are far too scarce to help you

[kano]

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).

Interesting, this is what I need for my BFL miners and the speed I'm getting is more than bfgminer, the one they recommends us to use.
Mining at Westhash through a proxy and the test version of cgminer doesn't show very good speed ie: 0000's and low temp but using the test version of cgminer alone works great.

I'm in a pickle. I like the speed of the test version of cgminer but it doesn't handle the #xnsub of westhash so I go to the proxy and LP doesn't mine well.   (also when switching pools it crashes)
What to do? Wait for new version?

cgminer is a BTC bitcoin miner, not an alt-coin miner.
You won't find #xnsub in it since, although it's next to impossible to find the true details of what that does, it's for alt-coin switching on that proxy.
If it has trouble there, pick another proxy pool or use a proper pool.

[twebit]

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).

Interesting, this is what I need for my BFL miners and the speed I'm getting is more than bfgminer, the one they recommends us to use.
Mining at Westhash through a proxy and the test version of cgminer doesn't show very good speed ie: 0000's and low temp but using the test version of cgminer alone works great.

I'm in a pickle. I like the speed of the test version of cgminer but it doesn't handle the #xnsub of westhash so I go to the proxy and LP doesn't mine well.   (also when switching pools it crashes)
What to do? Wait for new version?

cgminer is a BTC bitcoin miner, not an alt-coin miner.
You won't find #xnsub in it since, although it's next to impossible to find the true details of what that does, it's for alt-coin switching on that proxy.
If it has trouble there, pick another proxy pool or use a proper pool.

OK I was taking about bitcoin but it's ok I'm mining there without the #xnsub because rates are high right now. Thanks. here's info on what it does https://www.westhash.com/index.jsp?p=software#devs

[hiima]

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

I am having this same problem, I'm new to Monarch mining, had a Jalapeno. Do I have to compile my own cgminer or can I put that file into 4.9.1 folder and run from there?

[twebit]

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[Suspicious link removed]

I am having this same problem, I'm new to Monarch mining, had a Jalapeno. Do I have to compile my own cgminer or can I put that file into 4.9.1 folder and run from there?

Ya I just downloaded that .exe and put it in the 4.9.1 folder and it works. you have to install the winusb driver using zdiag here http://ck.kolivas.org/apps/cgminer/zadig/ and from the program menu select "list all devices"