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

Jay_Pal

legendary

Activity: 1493

Merit: 1003

Quote from: Lawsford on March 29, 2015, 05:59:13 AM

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

Lawsford

newbie

Activity: 10

Merit: 0

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 ?

twebit

member

Activity: 91

Merit: 10

Quote from: -ck on March 21, 2015, 07:18:07 PM

Quote from: os2sam on March 21, 2015, 06:55:07 PM

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

(also when switching pools it crashes)
What to do? Wait for new version?

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: frankenmint on March 26, 2015, 10:33:21 PM

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 Tongue

The cgminer mcast code idea I came up with (Aug 2013) was originally for them (for nothing)

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: frankenmint on March 26, 2015, 10:33:21 PM

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.

frankenmint

legendary

Activity: 1456

Merit: 1018

HoneybadgerOfMoney.com Weed4bitcoin.com

Hello,

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

Quote from: frankenmint on March 26, 2015, 05:22:38 PM

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

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: Justbyteme on March 25, 2015, 12:53:44 PM

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.

Justbyteme

newbie

Activity: 39

Merit: 0

Quote from: -ck on March 21, 2015, 06:43:48 PM

Quote from: os2sam on March 21, 2015, 06:38:48 PM

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

Anonymailer

hero member

Activity: 662

Merit: 500

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/

Mikestang

legendary

Activity: 1274

Merit: 1000

Quote from: os2sam on March 22, 2015, 08:41:37 PM

Glad to hear it. Happy solo mining.

Thanks, just as a back-up. Cool

os2sam

legendary

Activity: 3583

Merit: 1094

Think for yourself

Quote from: Mikestang on March 22, 2015, 08:37:43 PM

Quote from: os2sam on March 22, 2015, 08:26:17 PM

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

legendary

Activity: 1274

Merit: 1000

Quote from: os2sam on March 22, 2015, 08:26:17 PM

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

legendary

Activity: 3583

Merit: 1094

Think for yourself

Quote from: Mikestang on March 22, 2015, 06:32:58 PM

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

legendary

Activity: 1274

Merit: 1000

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?

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: os2sam on March 21, 2015, 06:55:07 PM

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

os2sam

legendary

Activity: 3583

Merit: 1094

Think for yourself

Quote from: -ck on March 21, 2015, 06:43:48 PM

Quote from: os2sam on March 21, 2015, 06:38:48 PM

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

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: os2sam on March 21, 2015, 06:38:48 PM

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

legendary

Activity: 3583

Merit: 1094

Think for yourself

Quote from: -ck on March 21, 2015, 05:54:13 PM

Quote from: os2sam on March 21, 2015, 03:14:05 PM

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

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: os2sam on March 21, 2015, 03:14:05 PM

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

legendary

Activity: 3583

Merit: 1094

Think for yourself

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 .
Thanks,
Sam

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