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

[sdjernes]

Having some issues with AM Prisma using the USB adapter

Cgminer 4.7.1
Rasp Pi running latest wheezy
compiled using: --enable-blockerupter --enable-icarus --without-curses

./cgminer -o stratum+tcp://us1.ghash.io:3333 -u xxxx -p xxxx --bet-clk 23

Cgminer spits out a bunch of errors

[2014-11-06 17:44:02] BET0: Unexpected value 00 received                   
[2014-11-06 17:44:02] BET0: Sync Error                   
[2014-11-06 17:44:02] BET0: Unexpected value 58 received                   
[2014-11-06 17:44:02] BET0: Sync Error                   
[2014-11-06 17:44:02] BET0: Unexpected value 58 received   

it then segfaults after a little bit.

I am not sure if my cgminer command is wrong or the USB dongle is the issue.. I have tried plugging directly into Pi and also a power USB hub with the same results.

I get this also but if I restart CGminer a few times it eventually starts hashing fine.  Seems that there is something odd with the driver or the chips put out some odd crap at first after power up.

However I have a question about the -bet-clk=23 thing  According to CGminer docs this value is x10 so to get 240 you would want 24, which is the default value of the setting.  Am I understanding this wrong?  Do we need to run the Prisma at 230 not 240?  At --bet-clk=23 my unit will not do stable over 800Ghs

[1643309611]

1643309611

[1643309611]

1643309611

[Blazed]

I tried 24 with same results..does not seem to matter. I guess I will just try 1 board and see what it does for me.

[-ck]

Yep sorry the block erupter driver is absolutely submitted and maintained by AM and I don't have the hardware so I can't help you directly but I suspect the driver is buggy (it should never segfault for example). Hopefully they chime in here with support and fix the bugs.

[-ck]

Sorry for stupid question.

Latest releases do not work at all
Is it only me or ?

It's only you. We can't help you without you giving us any information whatsoever on what the problem is.

[SVK]

Sorry for stupid question.

Latest releases do not work at all
Is it only me or ?

It's only you. We can't help you without you giving us any information whatsoever on what the problem is.

My bad

Downloaded 4 latest version(4.7.1, 4.7.0, 4.6.1, 4.6.0), created .bat file and nothing, just black window appeared for a split of a second.
Same bat file works with 4.5.0 version.

I'm using Win 7 and I have habanero board.
(I'm mining with 4.5.0 but wanted to try newer versions)

Thank you very much

[-ck]

Downloaded 4 latest versions, created .bat file and nothing, just black window appeared for a split of a second.
Same bat file works with 4.5.0 version.

I'm using Win 7 and I have habanero board.
(I'm mining with 4.5.0 but wanted to try newer versions)

Open a command prompt and run cgminer directly with your commands (and add -T) instead of clicking on the bat file and it will tell you what's wrong instead of just disappearing taking the error with it.

[Blazed]

Yep sorry the block erupter driver is absolutely submitted and maintained by AM and I don't have the hardware so I can't help you directly but I suspect the driver is buggy (it should never segfault for example). Hopefully they chime in here with support and fix the bugs.

"Hopefully they chime in here with support and fix the bugs" LOL not going to hold my breath on that one.

[SVK]

Downloaded 4 latest versions, created .bat file and nothing, just black window appeared for a split of a second.
Same bat file works with 4.5.0 version.

I'm using Win 7 and I have habanero board.
(I'm mining with 4.5.0 but wanted to try newer versions)

Open a command prompt and run cgminer directly with your commands (and add -T) instead of clicking on the bat file and it will tell you what's wrong instead of just disappearing taking the error with it.

Many thanks for your help
I have noticed that there is missing Cgminer.exe in all of above mentioned versions.

I will try it tomorrow morning.

Open command prompt and paste everything from bat file and I will add -T at the end.

Thank you very much

[-ck]

Yep sorry the block erupter driver is absolutely submitted and maintained by AM and I don't have the hardware so I can't help you directly but I suspect the driver is buggy (it should never segfault for example). Hopefully they chime in here with support and fix the bugs.

"Hopefully they chime in here with support and fix the bugs" LOL not going to hold my breath on that one.

They did manage to submit the code to mainline cgminer which is infinitely more than I was expecting.

[sdjernes]

The following is a questing from the Debian pkg-bitcoin-dev group and I am interested too:

If you are familiar, could you explain this? Why should we not be
 using system libusb?

- Added yet more warnings suggesting not to use the system libusb in configure.

Debian Jessie and Unstable (SID) libusb
libusb-1.0-0 (2:1.0.19-1)

[-ck]

The following is a questing from the Debian pkg-bitcoin-dev group and I am interested too:

If you are familiar, could you explain this? Why should we not be
 using system libusb?

- Added yet more warnings suggesting not to use the system libusb in configure.

Debian Jessie and Unstable (SID) libusb
libusb-1.0-0 (2:1.0.19-1)

This is an annoying issue we've been dealing with for as long as we've been using libusb and the answer to your question is as frustrating as can be.

Libusb had a hostile fork a few years back with libusbx and the main libusb development had slowed to a crawl. Virtually every distribution eventually moved to libusbx simply because it was the more actively developed branch. However at the time we found that every time we tried to migrate to libusbx it added substantial instability to the devices we were communicating with as most asic usb miners were actually pretty hastily slapped together and not very tolerant. Kano did a lot of investigation and found that there were numerous occasions where sending timeout based requests to libusb it simply would not return. The issue was amplified on windows and almost universal on usb1.1 devices which unfortunately many asic manufacturers decided to use (despite being a 15 year old protocol instead of usb2). Eventually the development of libusb was stopped and there was an alleged merge between the libusbx and libusb code and libusbx inherited the original libusb name with what appears to have been a somewhat strained truce between the original libusb developer and the libusbx devs. Unfortunately what happened was they built on the libusbx code and it appears that whatever it was that made the original libusb more stable never made it back into the maintained branch. We ended up finding the end of life libusb that we were using was still the most stable and none of the extra features in the newer libusbx based code were of any advantage and it conferred more instability. Here is the last time I tried moving to the merged libusbs:
https://bitcointalk.org/index.php?topic=28402.msg4816354#msg4816354

If you follow the few pages of testing (and ignore the pages of trolling) you'll see how I end up giving up on libusbx again.
And here is where I reverted to our own included libusb code :
https://bitcointalk.org/index.php?topic=28402.msg4989440#msg4989440

The same problems still exist with the current libusb included in distributions.

Now you're probably saying we should have submitted bug reports to libusbx instead of including libusb however we spent a ridiculous amount of time trying to find where the problem was in the first place and asic driver development was nothing short of frantic at the time and the amount of time we spent on it was far in excess of what we wanted already and it was detracting from further cgminer and driver development so I gave up and stuck to the libusb we included since it basically worked and was stable - what else can one ask? It also was not clear which was the real libusb... You'll also see that I was dependent on users to do the testing since I wasn't the one reproducing the problems so I couldn't do any cycle of test and report upstream. I doubt you'll be able to get any of those users with the old hardware engaged in that cycle of discussion now with libusb devs.

EDIT: Here's where Kano first tracked down the problem:
https://bitcointalk.org/index.php?topic=28402.msg2948402;topicseen#msg2948402
https://bitcointalk.org/index.php?topic=28402.msg2970018;topicseen#msg2970018

Adding the --with-system-libusb was put there for platforms where there was no udev support and building would fail (eg openwrt) forcing them to use the system libusb instead of the included one. However I've since added a --disable-udev option which makes it build even there. If I removed the system-libusb option and silently built my own included libusb for the packagers they'd be none the wiser.

[Buchi-88]

New release: Version 4.7.1, 4th November 2014

Minor bugfix release after dusk.


Human readable changelog:


- If different USB devices contain the same communication chip, provided the USB device has a product id set, cgminer will no longer try to use the wrong driver on it (eg LIN vs BFLSC).

THX for your efforts 

[Xian01]

Con.

Why do you suck so much ? </s>

https://forums.butterflylabs.com/bitcoin-pools/350-eclipse-mining-consortium-no-fee-pps-dgm-sms-2fa-gbt-stratum-vardiff-162.html#post86766

[-ck]

Why do you suck so much ? </s>

https://forums.butterflylabs.com/bitcoin-pools/350-eclipse-mining-consortium-no-fee-pps-dgm-sms-2fa-gbt-stratum-vardiff-162.html#post86766

Hah is there anything that guy won't attack? Now I'm really worried that my reputation will be tarnished by someone so esteemed in the bitcoin community.

[knowndragon]

I am very new to mining and want to try my luck solo mining. I can get the cgminer to run on a pool no problem. I plan on pool mining too. My problem is when I try and set up cgminer for solo mining I keep getting pool0 slow/down or url or credentials invalid. I am going to keep cgminer pool mining for now. What information do I need to supply in order to get help with fixing this issue? Thank you in advance. 

[kano]

I am very new to mining and want to try my luck solo mining. I can get the cgminer to run on a pool no problem. I plan on pool mining too. My problem is when I try and set up cgminer for solo mining I keep getting pool0 slow/down or url or credentials invalid. I am going to keep cgminer pool mining for now. What information do I need to supply in order to get help with fixing this issue? Thank you in advance. 

Try solo.ckpool.org ...
https://bitcointalk.org/index.php?topic=763510.0

The page there even explains how to mine there

Otherwise you'll need to setup a local bitcoind and learn all about doing that and also tuning it so you don't lose the block if you ever find one.

Also, don't "expect" to find one very soon using solo, unless you have something like 400THs or more of mining.

[knowndragon]

I am very new to mining and want to try my luck solo mining. I can get the cgminer to run on a pool no problem. I plan on pool mining too. My problem is when I try and set up cgminer for solo mining I keep getting pool0 slow/down or url or credentials invalid. I am going to keep cgminer pool mining for now. What information do I need to supply in order to get help with fixing this issue? Thank you in advance. 

Try solo.ckpool.org ...
https://bitcointalk.org/index.php?topic=763510.0

The page there even explains how to mine there

Otherwise you'll need to setup a local bitcoind and learn all about doing that and also tuning it so you don't lose the block if you ever find one.

Also, don't "expect" to find one very soon using solo, unless you have something like 400THs or more of mining.

This is what I was afraid of. I did invest in some miners and have bitcoin-qt downloading and syncing transactions. I am running cgminer and have followed some strange guides. I know solo mining isn't the best and most of my hashing power is going to be involved in a pool. I want to set up some major hash for a lottery for none the less.

bitcoin.conf in the appdata is has follows.

server=1
gen=1
rpcuser=?
rpcpassword=?
rpcallowip=127.0.0.1
rpcport=8332
daemon=1
listen=1

cgminer.conf is has follows.

{
"pools" : [
   {
      "url" : "http://127.0.0.1:8332",
      "user" : "?",
      "pass" : "?"
   }
],

"intensity" : "15",
"gpu-engine" : "0-1050,",
"gpu-fan" : "0-85,",
"gpu-memclock" : "1500,",
"gpu-powertune" : "20,",
"temp-cutoff" : "95,",
"temp-overheat" : "85,",
"temp-target" : "75,",

"auto-fan" : true,
"auto-gpu" : true,
"expiry" : "120",
"failover-only" : true,
"gpu-threads" : "2",
"log" : "5",
"queue" : "1",
"scan-time" : "30",
"temp-hysteresis" : "3",

"kernel-path" : "/usr/local/bin"
}

My deliveries don't start coming in till Wed. I would like to be able to have it sorted out and ready to go by then. Mining Bitcoin is not for the faint of heart. It isn't cheap but I believe I have the equipment coming to pay out my investment and keep me vested in it and bring a little profit. The equipment I speak of is not graphics cards either but some major hashing power. I am not trying to offend anyone but I am trying to take this serious. I will have two computer running five miners by the end of the month. I also have two computers sitting by idle and 4 800+ psu's.

I will say this I was able to stratum proxy solo mine but I didn't do it for long because of still learning how to tune things. If I don't use the mining proxy I get the pool0 slow/down error. Any help would be appreciated and has well I know I am late to the game but still see a profit to be made. At least I know I don't want to buy a pizza with 10,000 bitcoins. Also any tuning tutorials for bitcoin-qt that way I don't destroy or burn any bitcoins.

Thank you in advance for any help. It will be appreciated.

[-ck]

cgminer.conf is has follows.

Code:

{
"pools" : [
{
"url" : "http://127.0.0.1:8332",
"user" : "?",
"pass" : "?"
}
],

"intensity" : "15",
"gpu-engine" : "0-1050,",
"gpu-fan" : "0-85,",
"gpu-memclock" : "1500,",
"gpu-powertune" : "20,",
"temp-cutoff" : "95,",
"temp-overheat" : "85,",
"temp-target" : "75,",

"auto-fan" : true,
"auto-gpu" : true,
"expiry" : "120",
"failover-only" : true,
"gpu-threads" : "2",
"log" : "5",
"queue" : "1",
"scan-time" : "30",
"temp-hysteresis" : "3",

"kernel-path" : "/usr/local/bin"
}

Your cgminer configuration shouldn't even include any GPU commands whatsoever. This suggests to me that you're starting with some absolutely ancient version of cgminer. The solo mining component in cgminer was heavily rewritten a long time after GPU mining was removed. Please grab the latest cgminer and start again.

[knowndragon]

cgminer.conf is has follows.

Code:

{
"pools" : [
{
"url" : "http://127.0.0.1:8332",
"user" : "?",
"pass" : "?"
}
],

"intensity" : "15",
"gpu-engine" : "0-1050,",
"gpu-fan" : "0-85,",
"gpu-memclock" : "1500,",
"gpu-powertune" : "20,",
"temp-cutoff" : "95,",
"temp-overheat" : "85,",
"temp-target" : "75,",

"auto-fan" : true,
"auto-gpu" : true,
"expiry" : "120",
"failover-only" : true,
"gpu-threads" : "2",
"log" : "5",
"queue" : "1",
"scan-time" : "30",
"temp-hysteresis" : "3",

"kernel-path" : "/usr/local/bin"
}

Your cgminer configuration shouldn't even include any GPU commands whatsoever. This suggests to me that you're starting with some absolutely ancient version of cgminer. The solo mining component in cgminer was heavily rewritten a long time after GPU mining was removed. Please grab the latest cgminer and start again.

Nice to meet you guys by the way. Yes I was using some old software. 3.3.1 I believe. I was following a guide off youtube. I was just hoping to get use to cgminer seeing has rockminer has a download of it. I plan on having a small farm though. I guess I am just chomping at the bit. I just download 4.7 don't know how to run it without the miners but atleast I will have it when the first one shows. Thank you guys for the help and hope you will be there in the future.

[Askit2]

Why do you suck so much ? </s>

https://forums.butterflylabs.com/bitcoin-pools/350-eclipse-mining-consortium-no-fee-pps-dgm-sms-2fa-gbt-stratum-vardiff-162.html#post86766

Hah is there anything that guy won't attack? Now I'm really worried that my reputation will be tarnished by someone so esteemed in the bitcoin community.

At this point I would say he won't attack his employers. Or should that be previous employers if the BTC wallet in the other thread belongs to a principal and they liquidated it while being under investigation.

I'm glad you have a sense of humor.