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

[miter_myles]

AMU1: TIMEOUT GetResults took 1711ms but was 100ms

I am also seeing these kinds of messages too...

[-ck]

AMU1: TIMEOUT GetResults took 1711ms but was 100ms

I am also seeing these kinds of messages too...

The occasional timeout like this is okay, it's a kind of USB communication error.

[miter_myles]

AMU1: TIMEOUT GetResults took 1711ms but was 100ms

I am also seeing these kinds of messages too...

The occasional timeout like this is okay, it's a kind of USB communication error.

Rgr that - it appears lowering my diff on btcguild 2 from 4 made them go away and also report a faster MH back to the dashboard... (have 31 BEs connected.. ) 

Appreciate the reply!

MM

[OtaconEmmerich]

The Hub works perfectly fine on the PC, It spits out errors even with one BE is connected to the Hub. I'm thinking it's some kinda software issue as I don't have a normal Arch install.

BE draws way more power then most other devices. As I am sure you have read it is far over spec for usb1 and usb2. It might be in spec for usb3. People get around the power issue by wiring the hub in question to a higher current source like a computer PS. Then you just have to worry about the Vias on the board carrying the current without failing.

Good luck.

I don't think power is the issue, Like I said it works fine when plugged into the OTG cable alone. When I just plug just ONE BE into the Hub it spits out the errors till after a while a the BE's LED starts glowing green. I think it's a software (I'm running Linux on a tablet which is kinda iffy) or the hub acting weird. I'm gunna try running debug mode and figuring it out before tonight. I mostly want this setup so I can mine at night to save on power costs.

[-ck]

I don't think power is the issue, Like I said it works fine when plugged into the OTG cable alone. When I just plug just ONE BE into the Hub it spits out the errors till after a while a the BE's LED starts glowing green. I think it's a software (I'm running Linux on a tablet which is kinda iffy) or the hub acting weird. I'm gunna try running debug mode and figuring it out before tonight. I mostly want this setup so I can mine at night to save on power costs.

Could be overheating. Try a simple fan over them for a while as a straight forward test.

[OtaconEmmerich]

Nope, I always run a fan on them. I've got one of the 92mm Antec USB ones and a Desktop fan for a backup. Like I said, it runs perfectly fine without the HUB. Gunna go work on debugging now.

[kano]

Nope, I always run a fan on them. I've got one of the 92mm Antec USB ones and a Desktop fan for a backup. Like I said, it runs perfectly fine without the HUB. Gunna go work on debugging now.

https://asktom.cf/index.php?topic=28402.msg2938585#msg2938585

(the bit you ignored when you replied)

[OtaconEmmerich]

Woops! I mis-read it before Kano, I just saw the edit now. Yeah, I'll get to running that.

[Askit2]

May I ask why you don't use the normal cgminer binary with the -G flag ?

Because if you use standard CGMiner.exe and your only ASIC mining it will require OpenCL SDK/Runtime to be installed to run.  If you use CGMiner-nogpu.exe then you don't need any AMD software at all.

 Well that makes far too much sense. TIL. Thank you.

When I compile on Linux or windows I have 0 AMD software installed. It isn't required at all. You can run without having OpenCL. I do it frequently both pre and post the no GPU versions. Just use the switch for no gpu mining. I have run the official binaries built with support but it didn't matter except I could use it.

[BTC-engineer]

I've a basic question about the impact of hw-errors inside cgminer and on the over-all mining result at a pool.

I'm just doing different firmware optimizations inside the current BFL firmware for my ASIC singles and want to make sure that my understanding of the hw-error counter inside cgminer is really correct.

Let's say I'm getting an average hashrate of 100GH with 0% hw-errors showing up inside cgminer and nothing else is going wrong (retries, network problems etc.). In this case I would assume that I've also have an average hashrate of 100GH at the pool, right?

Now let's say cgminer is showing me 1% hw-errors. My basic understanding of software like cgminer is, that it's checking the mining result of the mining device and if the result is wrong, this result will not be forwarded to the pool and the hw-error counter is going up. Is my assumption correct, that in this case the average hashrate at the pool will be 99GH? Or is there anything else (relevant overhead, etc.) caused by hw-errors which has to be kept in mind when thinking about the over-all mining result at a pool?
 

[os2sam]

In this case I would assume that I've also have an average hashrate of 100GH at the pool, right?

It sounds like your implying that the pools estimate of your hash rate is correct??  If so it is not!

The pool has no idea what your hash rate is.  It's just an estimate.

With most pools you can change the time period which the hash rate is estimated for which will influence how fast and how accurate your estimate will be.

[BTC-engineer]

In this case I would assume that I've also have an average hashrate of 100GH at the pool, right?

It sounds like your implying that the pools estimate of your hash rate is correct??  If so it is not!

The pool has no idea what your hash rate is.  It's just an estimate.

With most pools you can change the time period which the hash rate is estimated for which will influence how fast and how accurate your estimate will be.

No, I don't imply this. I know about the pool hashrate estimation based on shares during a specified time period.

My questions are regarding the impact of the hw-error counter.

[chanson]

I've been away for a while and decided to give 3.3 another shot since kano et al are singing its praises everywhere.

3.3.4 using libusb-1.0.16-rc10 compiled from sourceforge still shuts down half of my 4x AM USB eruptors when running on Debian amd64 with USB disconnects. If there's some sort of logs you would like let me to post, let me know what you would like to see, but compiling a newer libusb absolutely *does not* solve the problem.

Back to 3.1.1 where everything works fine.

[xyzzy099]

I've been away for a while and decided to give 3.3 another shot since kano et al are singing its praises everywhere.

3.3.4 using libusb-1.0.16-rc10 compiled from sourceforge still shuts down half of my 4x AM USB eruptors when running on Debian amd64 with USB disconnects. If there's some sort of logs you would like let me to post, let me know what you would like to see, but compiling a newer libusb absolutely *does not* solve the problem.

Back to 3.1.1 where everything works fine.

I seem to be having a similar problem on Win7x64 with WinUSB (via Zadig).  I have 10 BEs, and every couple of hours, at least one will stop working with an error like this:

Code:

AMU0: Comms error (werr=-7 amt=0)

I tried using different hubs and tried using no more than 4 BEs in each 7-port HUB, in case it was a power issue, but nothing helps.

I have not tried using 3.1.1 yet, but I guess that is my next step.  This is very frustrating.

[Edit: I should add that if CGMiner is restarted, it will not pick up the BE that apparently failed.  It will seem to be OK, in that Windows says it is OK, and working, but the LED will stay on steady, and I have to manually unplug and replug it to get it to be seen by CGMINER.]

[Karin]

Unofficial Mac binaries updated to 3.3.4 at http://spaceman.ca/cgminer.

This directly relates to the whole libusb monologue I've been having in here over the last month
That specifically means your libusb on your mac is bugged - the timeout option when doing I/O isn't working
The README says how to build with a working libusb and it works on Linux and Windows - no idea about a Mac ...
Tell whoever Karin is to read the README ...

Karin, read the README 

I'm Karin!

I keep a very close eye on the readme's (even following their changes on github), and I've tried using rc10 but if I recall it had no effect on this bug on Macs, so I instead include the latest libusb in my builds.

Kano makes it sounds like the error confidently lies within libusb, so I'll do a full spectrum of tests with various libusb versions.  If I can find a version that works I will update cgminer for Mac OS X and Asteroid (my Mac GUI to cgminer) accordingly.

Otherwise, we'll have to dig deeper into libusb, and any errors generated from cgminer (and what the community can help with) would be our best bet in figuring out the issue with libusb + Macs.  I'll try and do these test builds tonight and will post back with what I find.

[ISAWHIM]

I have an issue with the latest CGMINER...

Instead of showing the number of "Accepted" and "Rejected" A: 2 R:1 HW: 0... it shows the "last diff" of the last accepted block for accepted and rejected, eg, for my scrypt-coins it shows...
A: 70687 R :68799 (Wow, great, 70687 accepted blocks and only 68799 rejects! From submitting two blocks!) lol

Those are the DIFFs of the coins I am mining, 70.7K and 68.8K were the two found.

Why did this change, and how do I get it back to show the NUMBER of accepted so I can see when ACCEPTED vs REJECTED, to gauge the effectiveness of the coins I am mining. Without knowing the number of accepted coins, that stat is useless. Why would we care what the DIFF was, in the stats?

This is not what it should be showing us... something is wrong... as per the readme and sample screen-shots...

Each column is as follows:
5s:  A 5 second exponentially decaying average hash rate
avg: An all time average hash rate
Q:   The number of requested (Queued) work items from the pools
A:   The number of Accepted shares
R:   The number of Rejected shares
HW:  The number of HardWare errors
E:   The Efficiency defined as number of shares returned / work item
U:   The Utility defined as the number of shares / minute

I also notice it is throwing-off other stats... hope this throw-off isn't going to change the way the program makes judgement about connections...

Note: This is the windows compiled version 3.3.4, mining bottlecaps at the moment version 1.4.1.

[Skitzzo]

I'm Karin!

I keep a very close eye on the readme's (even following their changes on github), and I've tried using rc10 but if I recall it had no effect on this bug on Macs, so I instead include the latest libusb in my builds.

Kano makes it sounds like the error confidently lies within libusb, so I'll do a full spectrum of tests with various libusb versions.  If I can find a version that works I will update cgminer for Mac OS X and Asteroid (my Mac GUI to cgminer) accordingly.

Otherwise, we'll have to dig deeper into libusb, and any errors generated from cgminer (and what the community can help with) would be our best bet in figuring out the issue with libusb + Macs.  I'll try and do these test builds tonight and will post back with what I find.

I appreciate it! Let me know if you figure anything out. I'd be happy to help in any way I can and/or send you a small tip for your time as I'm basically sitting dead in the water until I can get this sorted.

[kano]

Unofficial Mac binaries updated to 3.3.4 at http://spaceman.ca/cgminer.

This directly relates to the whole libusb monologue I've been having in here over the last month
That specifically means your libusb on your mac is bugged - the timeout option when doing I/O isn't working
The README says how to build with a working libusb and it works on Linux and Windows - no idea about a Mac ...
Tell whoever Karin is to read the README ...

Karin, read the README 

I'm Karin!

I keep a very close eye on the readme's (even following their changes on github), and I've tried using rc10 but if I recall it had no effect on this bug on Macs, so I instead include the latest libusb in my builds.

Kano makes it sounds like the error confidently lies within libusb, so I'll do a full spectrum of tests with various libusb versions.  If I can find a version that works I will update cgminer for Mac OS X and Asteroid (my Mac GUI to cgminer) accordingly.

Otherwise, we'll have to dig deeper into libusb, and any errors generated from cgminer (and what the community can help with) would be our best bet in figuring out the issue with libusb + Macs.  I'll try and do these test builds tonight and will post back with what I find.

Yes the problem is clearly libusb.
As I have already stated, I can run two different libusb versions on the same architecture and one works while the other doesn't.
The test problem that I've mentioned in here a few times is standalone code (bits and pieces of the code I've written in cgminer - but modified) and that shows if timeouts are working ... and if they are matching the expected values also.

https://asktom.cf/index.php?topic=28402.msg2817682;topicseen#msg2817682
https://asktom.cf/index.php?topic=28402.msg2846296;topicseen#msg2846296
https://asktom.cf/index.php?topic=28402.msg2938585;topicseen#msg2938585

That specific version - libusb-1.0.16-rc10 - works on Linux and Windows
I've seen other 1.0.16 versions that don't work ... thus using the 'latest' libusb is not guaranteed to solve it.
Also, libusb has 2 sources: libusb and libusbx, and some OSs provide libusbx instead of libusb

The README also states how to use the libusb mentioned

[Trongersoll]

There probably a simple answer to this, what do you do when the number of erupters you are running pushes the display off the bottom of the screen. So far I've been getting by with a smaller font, but that will only work so long.

[mdude77]

There probably a simple answer to this, what do you do when the number of erupters you are running pushes the display off the bottom of the screen. So far I've been getting by with a smaller font, but that will only work so long.

resize the window.  click on the box in top left, click properties.  go to layout and increase the window height.  you may need to restart it for it to take effect.  (I assume you're talking windows)

M