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

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

No comment....

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

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)

I stand corrected.

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.

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

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

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.

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

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?

Tell you what - since you clearly can't understand what is written in the README, come visit IRC, send me 1 BTC and I'll help you.
Wasting space in here repeating what's in the READMEs is ... a waste of space.
A lot of effort has gone into the READMEs by ckolivas and myself and I wrote all the original version of the USB code and README for USB so I've no idea what's difficult about it for anyone who knows a bit about using a computer.
Since it will obviously take some time to tell you all the keys to press - come to IRC (in my sig)

I don't see BitFORCE SHA256 SC if it is unplugged...

It is obvious to you I guess but not to me... To me this looks like sjldjlashfioedclas slojndalen siposajkdakl sjkdsjowm

And it is the last version so this is what you get out...

And it might be in README but it is not in English that I understand... The only thing that I find it that you need to run it as admin and I did...

EDIT: This is the part I should be reading right in ASIC readme?

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

And this in FPGA...

When mining on windows, the driver being used will determine if mining will work.

If the driver doesn't allow mining, you will get a "USB init," error message
i.e. one of:
 open device failed, err %d, you need to install a Windows USB driver for the device
or
 claim interface %d failed, err %d

The best solution for this is to use a tool called Zadig to set the driver:
 http://sourceforge.net/projects/libwdi/files/zadig/

This allows you set the driver for the device to be WinUSB which is usually
required to make it work if you're having problems

With Zadig, you may need to run it as administrator and if your device is
plugged in but you cannot see it, use the Menu: Options -> List All Devices

You must also make sure you are using the latest libusb-1.0.dll supplied
with cgminer (not the libusbx version)

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

Doesn't work or I don't understand it... But after doing that BFGminer stop working...

OK ... how is this not obvious?


I know I updated the message to match it exactly recently, but sheesh, it was pretty close before ...

Edit: also note that the READMEs even tell you what to do if it doesn't see your device ...

Doesn't seem too difficult to me.  Could be worded better I guess

-----------------------ASIC Readme-------------------------
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 directoy in the DOWNLOADS link above.
-------------------------------------------------------------

Here is my interpretation of the above paragraph and the steps I took

1. Unplug all Erupters
2. Run Zadig - Install WinUSB (I may have rebooted, can't remember for sure) - I could not install WinUSB while Erupters were plugged in.
3. Plug in one Erupter, verify that it is set to WinUSB.  If not set it to WinUSB.
4. Close Zadig, plug in the rest of the Erupters, run CGMiner.
Done

You really need to make this README more dumber friendly...

I have no idea that this refers to my problem:
When mining on windows, the driver being used will determine if mining will work.

If the driver doesn't allow mining, you will get a "USB init," error message
i.e. one of:
 open device failed, err %d, you need to install a Windows USB driver for the device
or
 claim interface %d failed, err %d


And why is then saying WinUSB not Zadig?

And why dose it work on a BFGminer?

EDIT: Zagid doesn't detect my device...  And please don't send me to another readme... I will say BFGminer is fine in this case...

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.

Read any of README, ASIC-README or even FPGA-README that tells you how to setup the windows driver ...
FPGA-README also has the link to download it rather than typing the name Zadig into google

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