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

[techman05]

So far so good for me. Mines been running for about 40 minutes with load balancing.

[-ck]

3.6.6 reports two zombies (literally) after about 20 minutes. I'll restart it shortly with logging on.

3.6.6 is almost identical to the experimental .exe you last downloaded.

[aigeezer]

3.6.6 reports two zombies (literally) after about 20 minutes. I'll restart it shortly with logging on.

3.6.6 is almost identical to the experimental .exe you last downloaded.

OK, thanks for the info. Behavior seems about the same. Working fine with logging, only running with log for about half an hour so far though.

[-ck]

3.6.6 reports two zombies (literally) after about 20 minutes. I'll restart it shortly with logging on.

3.6.6 is almost identical to the experimental .exe you last downloaded.

OK, thanks for the info. Behavior seems about the same. Working fine with logging, only running with log for about half an hour so far though.

It's still bizarre that it would not go zombie with logging on only. Either way it will be nice to know what error specifically causes cgminer to consider the device dead. All we can do is keep watching and maybe capture something on the log.

[os2sam]

New release: Version 3.6.6 - 26th October 2013

A new stable release building on top of 3.6.4 that should be a safe upgrade path after the earlier unstable 3.6 releases. Please pay attention for the options have changed.

CKolivias, could next update have an error pop up if it doesn't find a file its looking for like the config file. When it doesn't find the file it just flashes and closes without any error. Maybe say "missing startup item "cgminer.conf" and a generic press any key to exit message?

Using windows 7 (though I'd think somthing like this would be same in linux versions).

Thanks, I've just been going up in versions so fast I'm forgetting to move my config file.

In the mean time a work around is to put a "pause" in your .bat file.

[Roy Badami]

No command line options, everything is inside the ~/.cgminer/cgminer.conf

Oh, thanks, Pontius - I'd not even known that one can set arbitrary options in the conf file.  That's just made my life complete

roy

[jmc1517]

Following this thread with interest.

I have been running 3.3.1 for - ooh ages - without problems.  I'm using a Windows 7 64bit core i7 cpu with 34 Erupters plugged in to 3 Anker 10-port hubs and a powered 4-port hub.  The hubs are all plugged into motherboard usb slots.

No real problems with 3.3.1 apart from the odd zombie maybe every 10-14 days.

Upgraded to 3.6.4 and loads of timeouts and zombies almost instantly.  Powered off hubs, restarted. Same problem, so went back to 3.3.1 - sweet as a nut!

Today I have tried 3.6.6 and it ran for about 15 minutes, then one zombie appeared and timeouts stated to come up.  Then another zombie and more timeouts.  Seems to get worse after the first timeout appears, then it's pretty much regular timeout after timeout. So I've reverted to 3.3.1, powered the hubs off/on and everything is working smoothly again.

Just for the info...


* Today I  have tried 3.6.6

[Krak]

I've been noticing a lot of these duplicate shares lately (3.5.0 and 3.6.6).

Code:

[2013-10-26 13:59:00] Accepted 2aa206aa Diff 6/4 BAJ 0 pool 0
[2013-10-26 13:59:00] Rejected 2aa206aa Diff 6/4 BAJ 0 pool 0

Is there something wrong with my Jalapeno or is this just normal crappy BFL behavior? It's been throwing out about 1% hardware errors too.

[-ck]

Following this thread with interest.

I have been running 3.3.1 for - ooh ages - without problems.  I'm using a Windows 7 64bit core i7 cpu with 34 Erupters plugged in to 3 Anker 10-port hubs and a powered 4-port hub.  The hubs are all plugged into motherboard usb slots.

No real problems with 3.3.1 apart from the odd zombie maybe every 10-14 days.

Upgraded to 3.6.4 and loads of timeouts and zombies almost instantly.  Powered off hubs, restarted. Same problem, so went back to 3.3.1 - sweet as a nut!

Today I have tried 3.6.6 and it ran for about 15 minutes, then one zombie appeared and timeouts stated to come up.  Then another zombie and more timeouts.  Seems to get worse after the first timeout appears, then it's pretty much regular timeout after timeout. So I've reverted to 3.3.1, powered the hubs off/on and everything is working smoothly again.

Do you see a message just before one of them goes zombie about any usb errors in particular?

[-ck]

I've been noticing a lot of these duplicate shares lately (3.5.0 and 3.6.6).

Code:

[2013-10-26 13:59:00] Accepted 2aa206aa Diff 6/4 BAJ 0 pool 0
[2013-10-26 13:59:00] Rejected 2aa206aa Diff 6/4 BAJ 0 pool 0

Is there something wrong with my Jalapeno or is this just normal crappy BFL behavior? It's been throwing out about 1% hardware errors too.

Probably hardware related, but probably also nothing to worry about as it's just how a form of hw errors manifest on that particular device.

[vayvanne]

Code:

AMU 0 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
Accepted 00779ffc Diff 547/16 BAJ 0 pool 0
AMU 0 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
AMU 0 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
AMU 0 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
AMU 0 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
Accepted 0eb891f7 Diff 17/16 BAJ 0 pool 0
AMU 0 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
Accepted 0e692c25 Diff 17/16 BAJ 0 pool 0

I got this with 3.6.4 temp binaries after tens hours of hashing. Regular binaries was producing this more quickly.
Driver version is 6.1.7600.16385.
Now testing 3.6.6. No issues yet during last hour.

[-ck]

Found another little buglet. Uploading another cgminer-nogpu.exe into the temp directory. Windows users with AMU issues please try it.

http://ck.kolivas.org/apps/cgminer/temp/cgminer-nogpu.exe

[-ck]

Found another little buglet. Uploading another cgminer-nogpu.exe into the temp directory. Windows users with AMU issues please try it.

http://ck.kolivas.org/apps/cgminer/temp/cgminer-nogpu.exe

I know you're all tested out, but this one's a big fix for AMUs...

[rav3n_pl]

Stared on 2x USB erupters + 1x BFL 30GH/s
What should I expect? ;]

[-ck]

Stared on 2x USB erupters + 1x BFL 30GH/s
What should I expect? ;]

Thanks.

Hopefully... nothing untoward \o/

Anyway I sneaked up fresh binary packages anyway with the -1 suffix since it's an obvious bugfix, but not big enough to warrant a new version.

[jmc1517]

Do you see a message just before one of them goes zombie about any usb errors in particular?

I've downloaded the latest 3.6.6. cgminer-nogpu.exe but it still gives me a couple of zombies after 10 minutes and also continuous timeouts on another AMU which is NOT one of the zombies.

I've now restarted with a logfile - see below for the exact details.

Another thing I noticed, which may or may not be important:- When I first ran cgminer-nogpu after changing from 3.3.1, I didn't bother to power the hubs off/on, and when cgminer-nogpu started up it turned off all the green LEDs on all 34 erupters - i.e. it found them all - but it was only showing 33 erupters (0-32).  Cgwatcher was reporting 33 devices also.  As far as I could see, shares were being processed from all the AMUs (green flashes) - so what happened to the missing device?  I powered off/on after that and got all 34 devices working as normal.  Not sure if it's important, but I thought it worth mentioning as I haven't seen this behaviour before, as cgwatcher has always reported the correct number of devices, even if they were not showing on the cgminer screen.

Ah, just about to post, and now I have errors and a logfile. Here's an extract:

Code:

 [2013-10-27 10:59:29] Started cgminer 3.6.6
 :
 [2013-10-27 11:05:21] Accepted 0db97324 Diff 18/8 AMU 31 pool 0 
  :
 [2013-10-27 11:05:59] AMU 31 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:05:59] AMU31: Comms error (werr=-7 amt=0)
 [2013-10-27 11:06:00] AMU 31 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:06:00] AMU31: Comms error (werr=-7 amt=0)
 [2013-10-27 11:06:01] AMU 31 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:06:01] AMU31: Comms error (werr=-7 amt=0)
 [2013-10-27 11:06:02] AMU 31 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:06:02] AMU31: Comms error (werr=-7 amt=0)
 [2013-10-27 11:06:03] AMU 31 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:06:03] AMU31: Comms error (werr=-7 amt=0)
 [2013-10-27 11:06:04] AMU 31 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:06:04] AMU31: Comms error (werr=-7 amt=0)
 [2013-10-27 11:06:05] AMU 31 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:06:05] AMU31: Comms error (werr=-7 amt=0)
 [2013-10-27 11:06:05] Accepted 031d7613 Diff 82/8 AMU 20 pool 0 
 [2013-10-27 11:06:06] AMU 31 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:06:06] AMU31: Comms error (werr=-7 amt=0)
 [2013-10-27 11:06:07] Accepted 1928fe55 Diff 10/8 AMU 5 pool 0 
 [2013-10-27 11:06:16] Stratum from pool 0 detected new block
 [2013-10-27 11:06:16] Rejected 035c23e1 Diff 76/8 AMU 21 pool 0 (Job '84396' not found) 
 [2013-10-27 11:06:16] Rejected 0b03fc59 Diff 23/8 AMU 29 pool 0 (Job '84396' not found) 
 [2013-10-27 11:06:16] Accepted 0432dd08 Diff 60/8 AMU 19 pool 0 
 [2013-10-27 11:06:18] Accepted 1d3203f8 Diff 8/8 AMU 31 pool 0
 :
 [2013-10-27 11:10:59] Accepted 1772e531 Diff 10/8 AMU 13 pool 0 
 :
 [2013-10-27 11:13:27] AMU 13 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:13:27] AMU13: Comms error (werr=-7 amt=0)
 [2013-10-27 11:13:28] AMU 13 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:13:28] AMU13: Comms error (werr=-7 amt=0)
 [2013-10-27 11:13:28] Accepted 0c9c1e70 Diff 20/8 AMU 28 pool 0 
 [2013-10-27 11:13:29] Accepted 057ce3b2 Diff 46/8 AMU 27 pool 0 
 [2013-10-27 11:13:29] Accepted 160bf5ea Diff 11/8 AMU 5 pool 0 
 [2013-10-27 11:13:29] AMU 13 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:13:29] AMU13: Comms error (werr=-7 amt=0)
 [2013-10-27 11:13:30] AMU 13 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:13:30] AMU13: Comms error (werr=-7 amt=0)
 [2013-10-27 11:13:31] AMU 13 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:13:31] AMU13: Comms error (werr=-7 amt=0)
 [2013-10-27 11:13:31] Accepted 1bdbce81 Diff 9/8 AMU 18 pool 0 
 [2013-10-27 11:13:31] Accepted 1df086ca Diff 8/8 AMU 25 pool 0 
 [2013-10-27 11:13:32] AMU 13 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:13:32] AMU13: Comms error (werr=-7 amt=0)
 [2013-10-27 11:13:33] AMU 13 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:13:33] AMU13: Comms error (werr=-7 amt=0)
 [2013-10-27 11:13:34] AMU 13 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:13:34] AMU13: Comms error (werr=-7 amt=0)
 [2013-10-27 11:13:34] Accepted 0db2ded2 Diff 18/8 AMU 21 pool 0 
 [2013-10-27 11:13:35] AMU 13 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:13:35] AMU13: Comms error (werr=-7 amt=0)
 [2013-10-27 11:13:36] Accepted 0ff4b00e Diff 16/8 AMU 14 pool 0 
 [2013-10-27 11:13:40] Accepted 0f865896 Diff 16/8 AMU 13 pool 0 
 :
 [2013-10-27 11:13:55] Accepted 19b8a6cd Diff 9/8 AMU 13 pool 0 
 :
 [2013-10-27 11:14:22] AMU 13 SendWork usb write err:(-4) LIBUSB_ERROR_NO_DEVICE
 [2013-10-27 11:14:22] AMU13: Comms error (werr=-4 amt=0)
 [2013-10-27 11:14:22] AMU 13 failure, disabling!
 [2013-10-27 11:14:22] Thread 13 being disabled
 :
 [2013-10-27 11:14:30] Icarus detect (5:34) failed to initialise (incorrect device?)

The full log is here:
  https://dl.dropboxusercontent.com/u/44240170/logfile.txt

Does it help?

[jmc1517]

Just realised that that last run was without the --debug option.  Trying again with --debug and logging turned on :/

[aigeezer]

3.6.6 reports two zombies (literally) after about 20 minutes. I'll restart it shortly with logging on.

3.6.6 is almost identical to the experimental .exe you last downloaded.

OK, thanks for the info. Behavior seems about the same. Working fine with logging, only running with log for about half an hour so far though.

It's still bizarre that it would not go zombie with logging on only. Either way it will be nice to know what error specifically causes cgminer to consider the device dead. All we can do is keep watching and maybe capture something on the log.

My 3.6.6 test with logging on has run for just under 24 hours  - log size is 1.16GB. Nothing unusual happened - no errors of any kind that I can see, but I haven't read every line of the log.   

13 AMUs and one BAL, Win 7 64.

I'll shut it down shortly to try your new "little buglet" fix.

[-ck]

3.6.6 reports two zombies (literally) after about 20 minutes. I'll restart it shortly with logging on.

3.6.6 is almost identical to the experimental .exe you last downloaded.

OK, thanks for the info. Behavior seems about the same. Working fine with logging, only running with log for about half an hour so far though.

It's still bizarre that it would not go zombie with logging on only. Either way it will be nice to know what error specifically causes cgminer to consider the device dead. All we can do is keep watching and maybe capture something on the log.

My 3.6.6 test with logging on has run for just under 24 hours  - log size is 1.16GB. Nothing unusual happened - no errors of any kind that I can see, but I haven't read every line of the log.   

13 AMUs and one BAL, Win 7 64.

I'll shut it down shortly to try your new "little buglet" fix.

So I'm assuming that turning debugging on is having some subtle effect on timing, slowing down writes to the device or something like that, and is indirectly making your devices more stable. So that gives me some other avenues to check out. Give the bugfix a try and I'll make some other binaries trying other shit out, thanks.

[aigeezer]

So I'm assuming that turning debugging on is having some subtle effect on timing, slowing down writes to the device or something like that, and is indirectly making your devices more stable. So that gives me some other avenues to check out. Give the bugfix a try and I'll make some other binaries trying other shit out, thanks.

Yes, that's how it feels to me.

The bugfix version is up and running now, without logging. It's been fine for the first 10 minutes. If it fails, I'll restart it with logging on.

Edit: AMU 8 went zombie 14 minutes into the run. I'll rerun with logging and see if anything shows up.