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

[kano]

Try again ... it works ... I wrote it

PWC solo & 5750 (about 80 kHash), Last Valid Work is 1751 seconds old just now and still growing. I already noticed that this value was higher than 2000 seconds. On the other side, faster card (7950) and different scrypt coin has lower values but I see 244 seconds timeout just now... These values are related to coin and GPU hashrate.

The time will of course relate to the speed of the device.

Until you find a nonce, the device has done nothing successfully.

How long on average ... well that of course will directly relate to the hash rate and how many hashes are required on average per nonce.

For BTC sha256 you need to do on average 2^32 hashes per nonce - so for 100MH/s that's 43seconds for 2^32 hashes.
21 times that is 15 minutes - so yeah if a 100MH/s device finds no valid shares in 15 minutes then you can be pretty sure something is wrong.

Until a device actually returns a valid nonce, you can't be sure it really is working properly.

I guess on scrypt you have a problem coz it may take months minutes to do any work, so I guess you can't really be sure there is something wrong very quickly. However, in your case you went way, way past the point where "Last Valid Work" would definitely mean something is wrong.
I will also add that with scrypt, if you try to push the performance up too much, you could easily get exactly what you said, where the device might keep returning invalid nonces but still appear to be OK from cgminer's point of view - send work, get reply.
The problem there of course is that you'd have to keep a history of HW errors since if it works OK for 3 days and then starts spitting out constant HW errors due to whatever is the cause, the HW error rate won't increase very fast.

I've never bother to scrypt GPU mine ... I prefer to have my GPUs idle or playing Minecraft for my kids - they use so much energy mining ...

[Zanatos666]

Figure it out... Readme is missing restart computer...

EDIT: And just to let you know. This is the second time I come hire ready to make a donation and second time thinking why... First time I was pointed in every but the right direction(most of the time reading README) not to waist anyone time and it end up probably being a bug in cgminer that I found workaround since none took me seriously thinking that I just doing something wrong since this is impossible... I bet it was never investigated since new version still have it... and I did post what happens and how did I solve it.

This time first anser did help me to understand that BFL instructions aren't correct but didn't help much understanding what is wrong that it still doesn't work only disable my workaround. And what I figure out then. Missing instruction in README that I was send to read and use... Will it be fixed?

Lucko, what are you trying to use here, USB Block Erupters, or a BFL ASIC device? They are two different things (FPGA vs ASIC), and therefore have two different set of instructions and ways to configure them.  If you are using USB Block Erupters, or some other USB FPGA device, then you should refer to the FPGA README, and not the ASIC README.

[ChipGeek]

I recently moved my BFL FPGA from its own RPi over to the same RPi that I'm running my BFL ASIC (Jalapeno) on.  I just noticed this message:

Code:

 cgminer version 3.3.1 - Started: [2013-08-02 13:40:59]
--------------------------------------------------------------------------------
 (5s):8.193G (avg):8.459Gh/s | A:342  R:4  HW:1  WU:126.3/m
 ST: 2  SS: 0  NB: 2  LW: 418  GF: 0  RF: 0
 Connected to us1.eclipsemc.com diff 4 with stratum as user <user>
 Block: 004d593153a097d8...  Diff:31.3M  Started: [13:43:03]  Best share: 902
--------------------------------------------------------------------------------
 [P]ool management [S]ettings [D]isplay options [Q]uit
 BAJ 0:  max 34C 3.91V | 7.779G/7.754Gh/s | A:305 R:4 HW:1 WU:116.1/m
 BFL 0:  52.6C         | 874.9M/802.2Mh/s | A: 41 R:0 HW:0 WU: 11.5/m
--------------------------------------------------------------------------------

 [2013-08-02 13:42:22] Accepted 198e49ab Diff 10/4 BAJ 0 pool 0
 [2013-08-02 13:42:22] Accepted 0147e043 Diff 199/4 BAJ 0 pool 0
 [2013-08-02 13:42:23] BFL0: took 20136ms - longer than 7000ms
 [2013-08-02 13:42:23] Accepted 0455b72a Diff 59/4 BAJ 0 pool 0
 [2013-08-02 13:42:26] Accepted 2d2ea71e Diff 5/4 BAJ 0 pool 0

Do I need to do anything about this?  Is it really taking 20 seconds to do a work unit?  Am I getting credit for these work units?  Should I just put the FPGA back on its own RPi? 

(I know - "Stop mining with an FPGA" and I will when I need to ship it back for my SC Single - hopefully this month.)

[-ck]

Figure it out... Readme is missing restart computer...

EDIT: And just to let you know. This is the second time I come hire ready to make a donation and second time thinking why... First time I was pointed in every but the right direction(most of the time reading README) not to waist anyone time and it end up probably being a bug in cgminer that I found workaround since none took me seriously thinking that I just doing something wrong since this is impossible... I bet it was never investigated since new version still have it... and I did post what happens and how did I solve it.

This time first anser did help me to understand that BFL instructions aren't correct but didn't help much understanding what is wrong that it still doesn't work only disable my workaround. And what I figure out then. Missing instruction in README that I was send to read and use... Will it be fixed?

Lucko, what are you trying to use here, USB Block Erupters, or a BFL ASIC device? They are two different things (FPGA vs ASIC), and therefore have two different set of instructions and ways to configure them.  If you are using USB Block Erupters, or some other USB FPGA device, then you should refer to the FPGA README, and not the ASIC README.

No, the USB block erupters are also ASIC devices and the ASIC README applies.

[-ck]

I recently moved my BFL FPGA from its own RPi over to the same RPi that I'm running my BFL ASIC (Jalapeno) on.  I just noticed this message:

Code:

 cgminer version 3.3.1 - Started: [2013-08-02 13:40:59]
--------------------------------------------------------------------------------
 (5s):8.193G (avg):8.459Gh/s | A:342  R:4  HW:1  WU:126.3/m
 ST: 2  SS: 0  NB: 2  LW: 418  GF: 0  RF: 0
 Connected to us1.eclipsemc.com diff 4 with stratum as user <user>
 Block: 004d593153a097d8...  Diff:31.3M  Started: [13:43:03]  Best share: 902
--------------------------------------------------------------------------------
 [P]ool management [S]ettings [D]isplay options [Q]uit
 BAJ 0:  max 34C 3.91V | 7.779G/7.754Gh/s | A:305 R:4 HW:1 WU:116.1/m
 BFL 0:  52.6C         | 874.9M/802.2Mh/s | A: 41 R:0 HW:0 WU: 11.5/m
--------------------------------------------------------------------------------

 [2013-08-02 13:42:22] Accepted 198e49ab Diff 10/4 BAJ 0 pool 0
 [2013-08-02 13:42:22] Accepted 0147e043 Diff 199/4 BAJ 0 pool 0
 [2013-08-02 13:42:23] BFL0: took 20136ms - longer than 7000ms
 [2013-08-02 13:42:23] Accepted 0455b72a Diff 59/4 BAJ 0 pool 0
 [2013-08-02 13:42:26] Accepted 2d2ea71e Diff 5/4 BAJ 0 pool 0

Do I need to do anything about this?  Is it really taking 20 seconds to do a work unit?  Am I getting credit for these work units?  Should I just put the FPGA back on its own RPi? 

(I know - "Stop mining with an FPGA" and I will when I need to ship it back for my SC Single - hopefully this month.)

You don't need to do anything as it is harmless apart from a tiny bit of lost work but it will be more reliable if you upgrade your libusb or change to archlinux based which has the latest libusb.

[Zanatos666]

Figure it out... Readme is missing restart computer...

EDIT: And just to let you know. This is the second time I come hire ready to make a donation and second time thinking why... First time I was pointed in every but the right direction(most of the time reading README) not to waist anyone time and it end up probably being a bug in cgminer that I found workaround since none took me seriously thinking that I just doing something wrong since this is impossible... I bet it was never investigated since new version still have it... and I did post what happens and how did I solve it.

This time first anser did help me to understand that BFL instructions aren't correct but didn't help much understanding what is wrong that it still doesn't work only disable my workaround. And what I figure out then. Missing instruction in README that I was send to read and use... Will it be fixed?

Lucko, what are you trying to use here, USB Block Erupters, or a BFL ASIC device? They are two different things (FPGA vs ASIC), and therefore have two different set of instructions and ways to configure them.  If you are using USB Block Erupters, or some other USB FPGA device, then you should refer to the FPGA README, and not the ASIC README.

No, the USB block erupters are also ASIC devices and the ASIC README applies.

I stand corrected.

[kano]

Figure it out... Readme is missing restart computer...

EDIT: And just to let you know. This is the second time I come hire ready to make a donation and second time thinking why... First time I was pointed in every but the right direction(most of the time reading README) not to waist anyone time and it end up probably being a bug in cgminer that I found workaround since none took me seriously thinking that I just doing something wrong since this is impossible... I bet it was never investigated since new version still have it... and I did post what happens and how did I solve it.

This time first anser did help me to understand that BFL instructions aren't correct but didn't help much understanding what is wrong that it still doesn't work only disable my workaround. And what I figure out then. Missing instruction in README that I was send to read and use... Will it be fixed?

Lucko, what are you trying to use here, USB Block Erupters, or a BFL ASIC device? They are two different things (FPGA vs ASIC), and therefore have two different set of instructions and ways to configure them.  If you are using USB Block Erupters, or some other USB FPGA device, then you should refer to the FPGA README, and not the ASIC README.

No, the USB block erupters are also ASIC devices and the ASIC README applies.

I stand corrected.

Don't worry - they are actually both the same for how to deal with USB.
I actually added an update in current git for ASIC-README saying to read FPGA-README for the AMUs since if you want to override the default settings on the AMU you need to use the --icarus-* commands in the FPGA-README (though there really is no need to change the settings)

[kano]

I recently moved my BFL FPGA from its own RPi over to the same RPi that I'm running my BFL ASIC (Jalapeno) on.  I just noticed this message:

...
Do I need to do anything about this?  Is it really taking 20 seconds to do a work unit?  Am I getting credit for these work units?  Should I just put the FPGA back on its own RPi?  

(I know - "Stop mining with an FPGA" and I will when I need to ship it back for my SC Single - hopefully this month.)

It usually means it throttled due to heat.
If you get lots of them, use a lower speed firmware or cool the environment down.

[Lucko]

I'm sure this was answered but can't find it using search and reading all is out of the question...

Jalapeno

 [2013-08-02 09:57:22] USB init, open device failed, err -12, you need to install a WinUSB driver for - BFL device 7:2

I'm googling and the only solution that work was use BFGminer... Now I'm sure it is possible to use cgminer but have no idea how... Where do I get that driver?

I found one on net but didn't work... And according to Jalapeno how-to it should be plug and play...

No comment....

[notme]

I'm sure this was answered but can't find it using search and reading all is out of the question...

Jalapeno

 [2013-08-02 09:57:22] USB init, open device failed, err -12, you need to install a WinUSB driver for - BFL device 7:2

I'm googling and the only solution that work was use BFGminer... Now I'm sure it is possible to use cgminer but have no idea how... Where do I get that driver?

I found one on net but didn't work... And according to Jalapeno how-to it should be plug and play...

No comment....

Your answer is contained in the first 48 lines of the ASIC-README file.

$ head -48  ASIC-README
SUPPORTED DEVICES

Currently supported devices include the Avalon, the Butterfly Labs SC range
of devices and the ASICMINER block erupters.

The BFL devices should come up as one of the following:

BAJ: BFL ASIC Jalapeño
BAL: BFL ASIC Little Single
BAS: BFL ASIC Single
BAM: BFL ASIC Minirig

BFL devices need the --enable-bflsc option when compiling cgminer yourself.

Avalon will come up as AVA.

Avalon devices need the --enable-avalon option when compiling cgminer.

ASICMINER block erupters will come up as AMU.

ASICMINER devices need the --enable-icarus option when compiling cgminer.
Also note that the AMU is managed by the Icarus driver which is detailed
in the FPGA-README


GETTING STARTED WITH BUTTERFLY LABS ASICS

Unlike other software, cgminer uses direct USB communication instead of the
ancient serial USB communication to be much faster, more reliable and use a
lot less CPU. For this reason, setting up for mining with cgminer on these
devices requires different drivers.


WINDOWS:

On windows, the direct USB support requires the installation of a WinUSB
driver (NOT the ftdi_sio driver), and attach it to the Butterfly labs device.
The easiest way to do this is to use the zadig utility which will install the
drivers for you and then once you plug in your device you can choose the
"list all devices" from the "option" menu and you should be able to see the
device as something like: "BitFORCE SHA256 SC". Choose the install or replace
driver option and select WinUSB. You can either google for zadig or download
it from the cgminer directory in the DOWNLOADS link above.

When you first switch a device over to WinUSB with zadig and it shows that
correctly on the left of the zadig window, but it still gives permission
errors, you may need to unplug the USB miner and then plug it back in

[Lucko]

Your answer is contained in the first 48 lines of the ASIC-README file.

And it didn't work... So don't send me to read if you can't

[notme]

Are you saying you have installed zadig and used it to install the WinUSB driver for your hardware?

Your original post seems to indicate you were looking for the driver:

Where do I get that driver?

I am trying to understand the situation in order to help you.  Please drop the attitude.  You are not describing your issue clearly enough for anyone to solve your problem for you.

[kano]

Please read my comment before.
Filling up this thread with more of the READMEs is pointless.
https://bitcointalk.org/index.php?topic=28402.msg2853463#msg2853463

[Lucko]

Are you saying you have installed zadig and used it to install the WinUSB driver for your hardware?

Your original post seems to indicate you were looking for the driver:

Where do I get that driver?

I am trying to understand the situation in order to help you.  Please drop the attitude.  You are not describing your issue clearly enough for anyone to solve your problem for you.

How come this is not clear... When I needed help there was none now all of you are looking to help...

Figure it out... Readme is missing restart computer...

If it is not clear from that I solved it...

[notme]

Are you saying you have installed zadig and used it to install the WinUSB driver for your hardware?

Your original post seems to indicate you were looking for the driver:

Where do I get that driver?

I am trying to understand the situation in order to help you.  Please drop the attitude.  You are not describing your issue clearly enough for anyone to solve your problem for you.

How come this is not clear... When I needed help there was none now all of you are looking to help...

Figure it out... Readme is missing restart computer...

If it is not clear from that I solved it...

It's been less than 18 hours since your first post.  I'm sorry our FREE TECH SUPPORT was not quick enough for you.

[Lucko]

It's been less than 18 hours since your first post.  I'm sorry our FREE TECH SUPPORT was not quick enough for you.

It wouldn't be free if it would be TECH SUPPORT(ok it would be but you would get a donation as I stetted)... 2 times I needed help and the bug reported first time is still in cgminer... And that time when I was reporting it I was told it not a bug it is is you or your system(but it is not since I found workaround)... This time it was read readme that didn't work... Needed to do something that was not in README...

[notme]

It's been less than 18 hours since your first post.  I'm sorry our FREE TECH SUPPORT was not quick enough for you.

It wouldn't be free if it would be TECH SUPPORT(ok it would be but you would get a donation as I stetted)... 2 times I needed help and the bug reported first time is still in cgminer... And that time when I was reporting it I was told it not a bug it is is you or your system(but it is not since I found workaround)... This time it was read readme that didn't work... Needed to do something that was not in README...

Exactly.  Normally you would be have to pay people to help you.  But instead you come here begging for advice and then get pissy when people try to help you.  I get it, all you know how to do is complain.  cgminer is open source.  If you have a bugfix or a documentation update, please submit a pull request.  Until then, be happy that thousands of hours have been spent by other people building the FREE software you are taking for granted.

[Lucko]

OK so add to ASIC readme:

In same cases you need to restart a computer. (don't know what was so special in my case so that is why I'm adding in same cases)

And that other bug.

If you have more then 5 GPUs it can happen that you are unable to increase intensity over 8. No idea why... When I had 5 in a miner it worked but when I added 3 more I could not. All GPUs were hashing at the speed of the slowest. But if you increase difficulty from 4 to 10 or more you could... So that was my workaround...

Or is that wrong way of submitting problems?

[notme]

OK so add to ASIC readme:

In same cases you need to restart a computer

And that other bug.

If you have more then 5 GPUs it can happen that you are unable to increase intensity over 8. No idea why... When I had 5 in a miner it worked but when I added 3 more I could not. All GPUs were hashing at the speed of the slowest. But if you increase difficulty from 4 to 10 or more you could... So that was my workaround...

Or is that wrong way of submitting problems?

Thank you for making an effort.  The general procedure goes like this:
1. Fork this repo: https://github.com/ckolivas/cgminer
2. Make you changes
3. Submit a pull request for your changes

You can easily make the README change yourself.  Unless you are a programmer, you probably can't track down the other bug to fix it.  For that one, you could try the IRC channel and ask if one of the developers there has the hardware and is willing to look at the problem.  However, I doubt GPU related code is very high priority at this point since GPU miners are a dying breed.

[Lucko]

Agree about GPU especially since this is only in case of SHA mining... Scrypt is always difficulty above 10 so it works OK...