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

[P_Shep]

Won't really help. The debug version only does something if it crashes.

Oh.

Thought you have some other trickery in there :/

I wish. The debug builds in there are based on 3.6.1 currently so they will likely have the memory leak bug inherent in the included libusb. That said, sometimes strangely issues go away on debug builds due to a bug showing up only with optimisations enabled (debug builds have no compiler optimisations).

yeah, stopped working with a stream of mem errors again. actually -11, not -7
giving 3.5.1 another bash now.

[P_Shep]

Why's my API output garbled???
(3.6.1 windows binary)

...

Does java API summary get the same result?

Edit: or to see the JSON version: java API "{\"command\":\"summary\"}"

comes out fine both formats there.

[kano]

Why's my API output garbled???
(3.6.1 windows binary)

...

Does java API summary get the same result?

Edit: or to see the JSON version: java API "{\"command\":\"summary\"}"

comes out fine both formats there.

That means the problem is the code you are using to read the API, not the API.
e.g. a php, json,python or whatever you are using update issue?

[-ck]

On the newest CGMiner 3.6.1 I have an issue on Linux. This problem is on a Raspberry Pi. It wasn't noticeable until I added more jalapeno's.
What happens is this. After running for a while it appears Linux runs out of USB devices. I know the problem is actually my USB devices errors.

The reason this seems like a problem is that when it runs out of devices in 22K shares or so 4 devices will not be working. It happens one at a time until it runs out completely. When it runs out the devices will be back to their initial numbering ex BAJ 7 and zombie. the only fix seems to be to quit cgminer so that it will start over. The hashrate is very low. I assume given enough other errors I would lose all 9.

Since no device was over 3% errors I would have assumed that it wouldn't get disabled as fast as it does. Most errors I notice are in response to a temp request. The reply is in process,0x(something),0x(something)(sometimes a third 0x(something) sometimes 0x00x00x00. At least that is how I remember it. I think that error was on 3.5.1. Current error looks like this

Code:

 [2013-10-16 03:33:04] BAJ 28 usb read err:(1) **UNKNOWN**
 [2013-10-16 03:33:04] BAJ28: QueJobStatus failed (err=1 amt=0)
 [2013-10-16 03:33:04] BAJ 28 failure, disabling!

I am not running the newest raspbian. I use one from 2/13. It holds up longer while mining and less frequently locks up the UI.

I have a different problem on Windows. Using a USB 2 or USB 3 hub the error rate is low. Using usb 1  hub I get devices that have accepted in the single digits like 9 to 300+ errors. I will likely pick up a USB 2.0 hub tomorrow. I see this a lot. I don't think its an error though.

Code:

USB BAJ read 2 bugger buffering 2 extra bytes

On the former issue, you've probably run out of semaphores due to the limit being lower on an RPi. Can't remember offhand how to change them but they require a few sysctl options.

On the latter, that's not a bug but just verbose information you can ignore mostly.

[P_Shep]

Why's my API output garbled???
(3.6.1 windows binary)

...

Does java API summary get the same result?

Edit: or to see the JSON version: java API "{\"command\":\"summary\"}"

comes out fine both formats there.

That means the problem is the code you are using to read the API, not the API.
e.g. a php, json,python or whatever you are using update issue?

Yeah, seems to be the php json_decode() function has stopped working. Bizzare.

[-ck]

New version: 3.6.2, 17th October 2013

New release, 2 new library versions. Finally gave up and moved to libusbx which works less bad on windows with the asynchronous code cgminer uses. Also a new jansson in tree full build.

Human readable changelog:

- New version of jansson has some minor bugfixes, but more importantly now is built properly from within the build tree such that changes to configuration will rebuild it. Alas this makes ./configure now take even longer.
- Change from libusb-1.0.16-rc10 to libusbx-1.0.17. libusb on windows with asynchronous transfers had memory leaks galore and eventually would fail. libusbx does not have this problem, but some people are reporting write timeout issues with it on prolonged use. Linux has no such issues.
- Updates to the way usb work is "scheduled" which might help decrease the risk of timeouts on windows.
- Fixes to the shutdown routine that would get stuck waiting for usb transfers that would never be able to complete.
- Changed the driver model in icarus devices to a slightly lower overhead newer code.
- BF1s weren't showing any WU when hashing, this has been fixed.
- Some earlier BFL SC minirigs were not being properly detected due to inconsistencies in the firmware responses.
- Workarounds to the ./autogen stage of building when people build from git. Note this still does not fully work on macosx but 'autoreconf -fi' should be enough to have the same effect for now.


Full changelog:

- Remove unused components of jansson
- Remove unused parts of libusb
- Work around older libtoolize that fails without top ltmain.sh not being
present during autogen
- Fix open coded use of autoreconf in autogen
- Update jansson to only build parts we require and suited to our build
environment.
- Initial import of jansson-2.5
- Prevent further USB transfers from occurring once the shutdown signal has been
sent to prevent transfers getting stuck and libusb failing to shut down.
- Make the USB polling thread poll every second to potentially aid longer
timeout transfers.
- Set device_diff on work in get_work to not be missed with drivers that use
get_work directly.
- Convert icarus driver to hash_driver_work model.
- bflsc - also allow ' 0' in DEVICES IN CHAIN
- bflsc - allow a 0 in DEVICES IN CHAIN
- Add needed EXTRA_DIST for libusbx.
- Update libusbx configure.ac changes.
- Revert libusb Makefile changes from going to libusbx.
- Fix trivial libusbx warnings.
- Convert libusb-1.0.16-rc10 to libusbx-1.0.17

[Aurum]

3.6.2 won't even run on Win7:
[2013-10-16 07:08:27] BAS 1 usb write err:(-5) LIBUSB_ERROR_NOT_FOUND
[2013-10-16 07:08:27] BAS1: RequestQueJob failed (err=-5 amt=0)

[P_Shep]

3.6.2 won't even run on Win7:
[2013-10-16 07:08:27] BAS 1 usb write err:(-5) LIBUSB_ERROR_NOT_FOUND
[2013-10-16 07:08:27] BAS1: RequestQueJob failed (err=-5 amt=0)

Works for me.

[jamesg]

3.6.2 won't even run on Win7:
[2013-10-16 07:08:27] BAS 1 usb write err:(-5) LIBUSB_ERROR_NOT_FOUND
[2013-10-16 07:08:27] BAS1: RequestQueJob failed (err=-5 amt=0)

Pro tip: Don't use Windoze for mining.  

[os2sam]

3.6.2 won't even run on Win7:
[2013-10-16 07:08:27] BAS 1 usb write err:(-5) LIBUSB_ERROR_NOT_FOUND
[2013-10-16 07:08:27] BAS1: RequestQueJob failed (err=-5 amt=0)

Pro tip: Don't use Windoze for mining.  

What else is there?

[Joshwaa]

3.6.2 won't even run on Win7:
[2013-10-16 07:08:27] BAS 1 usb write err:(-5) LIBUSB_ERROR_NOT_FOUND
[2013-10-16 07:08:27] BAS1: RequestQueJob failed (err=-5 amt=0)

Pro tip: Don't use Windoze for mining.  

What else is there?

Was that just sarcasm from sam? Your getting the hang of it!

[Karin]

I've tried on my Mac build environments and while I can compile and launch cgminer just fine, as well as GPU mine, when attempting to use a USB-based Block Erupter I get the following message and cgminer subsequently quits.

Code:

Failed pipe errno=24 in usbutils.c init_usb_transfer():2215

It looks as though it is perhaps able to do a brief moment (before the first poll?(?)) of hashing, as sometimes I get an accepted share out from it and sometimes not, as shown on the "Summary of runtime statistics" output after cgminer quits.

The last successful version for me on Mac is 3.5.1.  I've tested 3.6.1 and 3.6.2 and both generate the error.  cgminer is built entirely from the included source, no other libs used.  Using "--usb-dump 0" and "--verbose" provides no additional details.  Please let me know if I can help further!

[TR4L]

Just an FYI to ckolivas and kano.  I was trying to mine with 3.6.1 but it wouldn't allow me to run scrypt. I thought I was doing something wrong until I tried 2.11.4 and 3.1.1 and it worked.  Didn't change anything (copied and pasted my .conf files).  I'm running Ubuntu 12.04 LTS, I tried both:  "kernel" : "scrypt", and "scrypt" : true,  and neither worked. 

[LordTheron]

Hello,

I've updated cgminer to the latest one and now none of my bfl miners work. I get usb errors on all of them.  I'm running it on windows 7. Works fine on 3.4.3.. Any idea what may be wrong?

[techman05]

Hello,

I've updated cgminer to the latest one and now none of my bfl miners work. I get usb errors on all of them.  I'm running it on windows 7. Works fine on 3.4.3.. Any idea what may be wrong?

May not be related but if we changing lib do we have newer winusb to install now?

[-ck]

Yay windows. At this rate I'll inadvertently completely deprecate windows support 

Gonna have to think on this. The rewrite started out trying to fix windows but instead linux keeps getting better and windows and osx worse.

[streetuff]

Yay windows. At this rate I'll inadvertently completely deprecate windows support 

Gonna have to think on this. The rewrite started out trying to fix windows but instead linux keeps getting better and windows and osx worse.

+1

[TR4L]

Yay windows. At this rate I'll inadvertently completely deprecate windows support 

Gonna have to think on this. The rewrite started out trying to fix windows but instead linux keeps getting better and windows and osx worse.

Are you also dropping scrypt mining?

[-ck]

Yay windows. At this rate I'll inadvertently completely deprecate windows support 

Gonna have to think on this. The rewrite started out trying to fix windows but instead linux keeps getting better and windows and osx worse.

Are you also dropping scrypt mining?

I didn't say I was intentionally doing anything. However, since you asked, scrypt mining is being deprecated at some stage in the future. While there is still incentive for me to maintain it I will do so, but if it becomes a support maintenance burden and there is no incentive for me to maintain it, I will deprecate it. For the time being it is not like that. If scrypt has suddenly stopped working then it is almost certainly the same old problem of having done a system upgrade between versions and that is what has broken scrypt since the cgminer code for it has not changed in many many versions. If you have an older version of cgminer that is still working despite the system upgrade, that is normal - because cgminer caches the old kernel binary (as a .bin file) and the system upgrade can't affect it.

[-ck]

Yay windows. At this rate I'll inadvertently completely deprecate windows support 

Gonna have to think on this. The rewrite started out trying to fix windows but instead linux keeps getting better and windows and osx worse.

+1

LOL, you want me to deprecate support for other OSes? I've gotta admit, I say that jokingly almost every single day. The reality is that 85% of my downloads from my site are for the windows binaries though. Let's call 3.5.1 the  last stable version for windows for the time being.