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

[os2sam]

Here they are, my two SHA-256 miners, I have tried to update to the cgminer-4.9.0, but it was impossible.
With cgminer-4.9.0 I only get that works the AMU unit.

While you can see a very funny screenshot of them running happyly into cgminer-4.8.0

Thank you very much.

I just tried CGMiner with my Jalapeno and found that it doesn't work as well.  CGMiner says no devices found but cgminer -n shows the Jalapeno as being there.  It has been working fine with 4.7.1 which is what I had been using.

I don't have any bfl hardware any more. Can someone who has one start it with the extra options "-D -T 2>log.txt" and after it's failed at startup stop it and post the output of log.txt here (preferably within code tags).

The file exceeds the 64,000 character limit of the message so here's a link to it

https://dl.dropboxusercontent.com/u/65145036/log.txt

[1713481572]

1713481572

[1713481572]

1713481572

[1713481572]

1713481572

[-ck]

The file exceeds the 64,000 character limit of the message so here's a link to it

https://dl.dropboxusercontent.com/u/65145036/log.txt

Thanks Sam. I found the problem from your debug. If you're building on linux can you try latest git? If not, can you try the windows binary in temp here:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

[os2sam]

The file exceeds the 64,000 character limit of the message so here's a link to it

https://dl.dropboxusercontent.com/u/65145036/log.txt

Thanks Sam. I found the problem from your debug. If you're building on linux can you try latest git? If not, can you try the windows binary in temp here:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

I dropped in the Windoze binary and the Jalapeno works, but now the Block Erupters don't.  You want a new log.txt?

[-ck]

The file exceeds the 64,000 character limit of the message so here's a link to it

https://dl.dropboxusercontent.com/u/65145036/log.txt

Thanks Sam. I found the problem from your debug. If you're building on linux can you try latest git? If not, can you try the windows binary in temp here:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

I dropped in the Windoze binary and the Jalapeno works, but now the Block Erupters don't.  You want a new log.txt?

That's probably a new battle with AM's broken blockerupter driver.

sigh...

Sure why not give me the log to confirm. Thanks.

[os2sam]

The file exceeds the 64,000 character limit of the message so here's a link to it

https://dl.dropboxusercontent.com/u/65145036/log.txt

Thanks Sam. I found the problem from your debug. If you're building on linux can you try latest git? If not, can you try the windows binary in temp here:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

I dropped in the Windoze binary and the Jalapeno works, but now the Block Erupters don't.  You want a new log.txt?

That's probably a new battle with AM's broken blockerupter driver.

sigh...

Sure why not give me the log to confirm. Thanks.

Here you go.  The original 4.9.0 worked with the BE's.  Please let me know if it is too much effort to run this down.  After reading your post about the new versions not adding anything for the older hardware I'm not sure how much work it's really worth.

https://dl.dropboxusercontent.com/u/65145036/log2.txt

Thanks,
Sam

[-ck]

That's probably a new battle with AM's broken blockerupter driver.

sigh...

Sure why not give me the log to confirm. Thanks.

Here you go.  The original 4.9.0 worked with the BE's.  Please let me know if it is too much effort to run this down.  After reading your post about the new versions not adding anything for the older hardware I'm not sure how much work it's really worth.

Yes I'm aware the original 4.9.0 worked with the AMUs. I mean the recent piece of shit Asicminer hardware known as BET they generically called blockerupter still. The original binary I distributed did not contain the driver for it (that asicminer themselves contributed and never fixed) because it was broken. The binary you just downloaded contains the driver for the BET by request of someone earlier on this forum thread. It is indeed the conflict of that driver which actually releases the blockerupters but in the meantime it seems to have created a unique windows privilege conflict of some sort. I suspect that --usb BET:0 will fix that one for now but you may need to replug all your devices before trying again.

[os2sam]

That's probably a new battle with AM's broken blockerupter driver.

sigh...

Sure why not give me the log to confirm. Thanks.

Here you go.  The original 4.9.0 worked with the BE's.  Please let me know if it is too much effort to run this down.  After reading your post about the new versions not adding anything for the older hardware I'm not sure how much work it's really worth.

Yes I'm aware the original 4.9.0 worked with the AMUs. I mean the recent piece of shit Asicminer hardware known as BET they generically called blockerupter still. The original binary I distributed did not contain the driver for it (that asicminer themselves contributed and never fixed) because it was broken. The binary you just downloaded contains the driver for the BET by request of someone earlier on this forum thread. It is indeed the conflict of that driver which actually releases the blockerupters but in the meantime it seems to have created a unique windows privilege conflict of some sort. I suspect that --usb BET:0 will fix that one for now but you may need to replug all your devices before trying again.

Adding the BET:0 to my command line did the trick.  Everything is running fine now.
Thanks,
Sam

[-ck]

Adding the BET:0 to my command line did the trick.  Everything is running fine now.

Thanks Sam, in which case can I ask one more thing to try. Please redownload that temp binary (which I've updated) and use it without the BET:0 addition?

[tZKtdvt6]

Adding the BET:0 to my command line did the trick.  Everything is running fine now.

Thanks Sam, in which case can I ask one more thing to try. Please redownload that temp binary (which I've updated) and use it without the BET:0 addition?

cgminer.exe???
I am using linux!

[-ck]

Hello,

can anybody say to me how to get the file log, please?

I want to generate this file in my computer too and link it to this thread.

Thank you very much.

p.d. I compiled sucessfully the cgminer-master and I added --enable-icarus to the AMU, --enable-bitforce and --enable-bflsc to the jalapeño, into linux, and only get that connect the AMU unit.

I already gave you all the instructions above. Posting the same question over and over again only annoys everyone and I will delete any copies of the same question.

start it with the extra options "-D -T 2>log.txt"

[os2sam]

Adding the BET:0 to my command line did the trick.  Everything is running fine now.

Thanks Sam, in which case can I ask one more thing to try. Please redownload that temp binary (which I've updated) and use it without the BET:0 addition?

Done.  Working great.  It did take longer to startup.
Thanks again,
Sam

[tZKtdvt6]

Hello,

can anybody say to me how to get the file log, please?

I want to generate this file in my computer too and link it to this thread.

Thank you very much.

p.d. I compiled sucessfully the cgminer-master and I added --enable-icarus to the AMU, --enable-bitforce and --enable-bflsc to the jalapeño, into linux, and only get that connect the AMU unit.

I already gave you all the instructions above. Posting the same question over and over again only annoys everyone and I will delete any copies of the same question.

start it with the extra options "-D -T 2>log.txt"

Excuse to me Sir.,
I wasn't sure if you were typing that to me, excuse to me again, please.
Here you have what you need, I hope be well:
https://app.box.com/s/pr52ffsusnexi27743nb
Thank you very much.

[tZKtdvt6]

Please check the new item, because I have changed the before link and content.

Thank you very much.

[Economics]

From reading the change log it seems that CGMiner will support Butterfly Labs Monarch's, but when I look at the Monarch specifications, it says it only supports BFGMiner.  Why is that?  I'd prefer to stay with CGMiner for my Monarch's.

Specifications are here:
  http://www.butterflylabs.com/upload/manuals/monarch_specifications_and_setup_guide.pdf

--E

[-ck]

From reading the change log it seems that CGMiner will support Butterfly Labs Monarch's, but when I look at the Monarch specifications, it says it only supports BFGMiner.  Why is that?  I'd prefer to stay with CGMiner for my Monarchs.

The "relationship" between bfl and cgminer has always been awkward and strained. They've never directly supported running cgminer on it and they employed the fork miner author to write their official driver, though they then sent us devices to write drivers for them. Cgminer supports the monarchs fine, even if BFL doesn't say so.

[Economics]

From reading the change log it seems that CGMiner will support Butterfly Labs Monarch's, but when I look at the Monarch specifications, it says it only supports BFGMiner.  Why is that?  I'd prefer to stay with CGMiner for my Monarchs.

The "relationship" between bfl and cgminer has always been awkward and strained. They've never directly supported running cgminer on it and they employed the fork miner author to write their official driver, though they then sent us devices to write drivers for them. Cgminer supports the monarchs fine, even if BFL doesn't say so.

Thank you!  I'll continue to use CGMiner.

--E

[tZKtdvt6]

What about the document that I uploaded?
Have you seen it?

[wolf_miner]

Hi, I have a A2 chip miner that run cgminer 3.9 on raspberryPI and the two blade are connected to PI through gpio port at raspberryPI. As you can see in the screen the two blade are identified by BA1 0 and BA1 1.
Is possible to run two instances of cgminer each running only one blade? Like instance 1 running device BA1 0 and instance 2 running device BA1 1. Now the startup string was like this one.

Code:

sudo ./cgminer -o stratum+tcp://abcd-p x --A1Pll1 1300 --A1Pll2 1300 --diff 4096 --api-listen --api-network --cs 8 --stmcu 0 --hwreset --no-submit-stale --lowmem

Thanks in advance W_M

[Taugeran]

Hi, I have a A2 chip miner that run cgminer 3.9 on raspberryPI and the two blade are connected to PI through gpio port at raspberryPI. As you can see in the screen the two blade are identified by BA1 0 and BA1 1.
Is possible to run two instances of cgminer each running only one blade? Like instance 1 running device BA1 0 and instance 2 running device BA1 1. Now the startup string was like this one.

Code:

sudo ./cgminer -o stratum+tcp://abcd-p x --A1Pll1 1300 --A1Pll2 1300 --diff 4096 --api-listen --api-network --cs 8 --stmcu 0 --hwreset --no-submit-stale --lowmem

Thanks in advance W_M

If I remember correctly the a2 chip is scrypt which the official cgminer no longer supports

[tZKtdvt6]

Is anybody that can, please, check the following documents and say to me anything about it.
It is uploaded because I can't got that the Jalapeño and the small usb stick miner work with the last
cgminer update, which is, 4.9.0.
The link to the document that I have uploaded for it is:

https://app.box.com/s/pr52ffsusnexi27743nb