I just need the no-gpu file I use right?
I let you know in the morning if I don't awake to errors. At least the eroupters go bright green when then poop out.
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 204. (Read 5805531 times)
October 17, 2013, 10:00:21 PM
October 17, 2013, 09:48:47 PM
Hey, 3.6.3 just had a memory error again 
. I was able to close cgminer by pressing q but still ended up closing and moving back to 3.5.1 
It ran for what seemed all night and then I had to close it for whatever reason and I saw the no memory flickering in my screen
.
I hope you can eventually find a work around or permanent fix for this and make it "pretty" again
[without requiring the need to dump windows].
Woah woah, believe it or not this is good news (I think). I have an idea, and will post some experimental exes again shortly.. I was able to close cgminer by pressing q but still ended up closing and moving back to 3.5.1 It ran for what seemed all night and then I had to close it for whatever reason and I saw the no memory flickering in my screen
.I hope you can eventually find a work around or permanent fix for this and make it "pretty" again
[without requiring the need to dump windows].http://ck.kolivas.org/apps/cgminer/temp/
October 17, 2013, 09:30:00 PM
Hey, 3.6.3 just had a memory error again . I was able to close cgminer by pressing q but still ended up closing and moving back to 3.5.1
It ran for what seemed all night and then I had to close it for whatever reason and I saw the no memory flickering in my screen .
I hope you can eventually find a work around or permanent fix for this and make it "pretty" again [without requiring the need to dump windows].
Woah woah, believe it or not this is good news (I think). I have an idea, and will post some experimental exes again shortly. . I was able to close cgminer by pressing q but still ended up closing and moving back to 3.5.1 It ran for what seemed all night and then I had to close it for whatever reason and I saw the no memory flickering in my screen
.I hope you can eventually find a work around or permanent fix for this and make it "pretty" again
[without requiring the need to dump windows]. October 17, 2013, 09:26:55 PM
Hey, 3.6.3 just had a memory error again . I was able to close cgminer by pressing q but still ended up closing and moving back to 3.5.1
It ran for what seemed all night and then I had to close it for whatever reason and I saw the no memory flickering in my screen .
I hope you can eventually find a work around or permanent fix for this and make it "pretty" again [without requiring the need to dump windows].
. I was able to close cgminer by pressing q but still ended up closing and moving back to 3.5.1 It ran for what seemed all night and then I had to close it for whatever reason and I saw the no memory flickering in my screen
.I hope you can eventually find a work around or permanent fix for this and make it "pretty" again
[without requiring the need to dump windows]. 
October 17, 2013, 06:00:10 PM
With --usb you can say how many devices to find or how many each driver should find
So for each cgminer
--usb BAS:1
would grab only one BAS device.
If you use
--usb :1
it would grab the first device of any USB mining devices that you have. (this also has the minor advantage that it stops polling for hot-plugged devices until the current device disconnects)
Kano, Thanks!!! This has been the best tip for running Block Eruptors. I was constantly loosing them one by one and then restarting cgminer. But when I added --usb :29 it finds all my BEs and then if one stops it finds it again and it reappears with a higher AMU number, but every time I look since I added than command I find all 29 running!!!So for each cgminer
--usb BAS:1
would grab only one BAS device.
If you use
--usb :1
it would grab the first device of any USB mining devices that you have. (this also has the minor advantage that it stops polling for hot-plugged devices until the current device disconnects)
Is there a conf file syntax for this or command-line only? (I like to keep everything in one place.)
Does hotplug polling have much cost? Just curious.
Also, I rolled back to cgminer-nogpu.exe 2.5.1 and BFLs and BEs run fine. My GPU miners don't care 2.6.2 or whatever.
"usb" : ":29",
USB polling is ok for most people, but some see weird side effects on things like keyboards and mice.
(libusb must be doing something at a low level on windows that can cause this for some people?)
October 17, 2013, 05:33:37 PM
With --usb you can say how many devices to find or how many each driver should find
So for each cgminer
--usb BAS:1
would grab only one BAS device.
If you use
--usb :1
it would grab the first device of any USB mining devices that you have. (this also has the minor advantage that it stops polling for hot-plugged devices until the current device disconnects)
Kano, Thanks!!! This has been the best tip for running Block Eruptors. I was constantly loosing them one by one and then restarting cgminer. But when I added --usb :29 it finds all my BEs and then if one stops it finds it again and it reappears with a higher AMU number, but every time I look since I added than command I find all 29 running!!!So for each cgminer
--usb BAS:1
would grab only one BAS device.
If you use
--usb :1
it would grab the first device of any USB mining devices that you have. (this also has the minor advantage that it stops polling for hot-plugged devices until the current device disconnects)
Is there a conf file syntax for this or command-line only? (I like to keep everything in one place.)
Does hotplug polling have much cost? Just curious.
Also, I rolled back to cgminer-nogpu.exe 2.5.1 and BFLs and BEs run fine. My GPU miners don't care 2.6.2 or whatever.
October 17, 2013, 05:19:22 PM
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?
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.
Completely at a loss of how to fix this.
json_decode() is corrupting the data, and it's a built-in feature of PHP (5.2 in my case).
Googling around, I'm not seeing anyone else with the same problem.
absolutely stumped :/
October 17, 2013, 03:52:14 PM
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.
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!
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!
Thanks for the new version! I'm getting this same error on Mac in the latest cgminer version though, 3.6.3. I may try to play around with shoehorning in other libusb versions to see if I can get one working that way.
EDIT: Try latest git please.
October 17, 2013, 03:48:52 PM
[2013-10-17 10:02:15] BAJ33: QueFlush failed no data returned (err=0 amt=0)
[2013-10-17 10:02:15] Thread 33 failure, exiting
[2013-10-17 10:02:15] BAJ2: QueFlush failed no data returned (err=0 amt=0)
[2013-10-17 10:02:15] BAJ0: RequestResults failed no data returned (err=0 amt=
0)
[2013-10-17 10:02:15] Thread 2 failure, exiting
[2013-10-17 10:02:15] BAJ7: QueFlush failed no data returned (err=0 amt=0)
[2013-10-17 10:02:15] Thread 7 failure, exiting
[2013-10-17 10:02:15] BAJ1: QueFlush failed no data returned (err=0 amt=0)
got same error as version 3.61 with win 8
Is this on shutdown? If so, I know about it thanks.[2013-10-17 10:02:15] Thread 33 failure, exiting
[2013-10-17 10:02:15] BAJ2: QueFlush failed no data returned (err=0 amt=0)
[2013-10-17 10:02:15] BAJ0: RequestResults failed no data returned (err=0 amt=
0)
[2013-10-17 10:02:15] Thread 2 failure, exiting
[2013-10-17 10:02:15] BAJ7: QueFlush failed no data returned (err=0 amt=0)
[2013-10-17 10:02:15] Thread 7 failure, exiting
[2013-10-17 10:02:15] BAJ1: QueFlush failed no data returned (err=0 amt=0)
got same error as version 3.61 with win 8
EDIT: If you're building from git, try latest git master.
October 17, 2013, 03:32:23 PM
Would it be possible to make it listen to "--bitburner-fury-options" instead of the --avalon-options parameter? That would make it possible to run both Bitburner XX and Bitburner Fury devices in 1 CGminer window.
When using the newest Bitburner Fury firmware, the device now identifies as BBF. Is it possible to add a separate options parameter for the BBF?
October 17, 2013, 03:24:03 PM
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.
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!
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!
Thanks for the new version! I'm getting this same error on Mac in the latest cgminer version though, 3.6.3. I may try to play around with shoehorning in other libusb versions to see if I can get one working that way.
October 17, 2013, 12:34:10 PM
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?
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.
Completely at a loss of how to fix this.
json_decode() is corrupting the data, and it's a built-in feature of PHP (5.2 in my case).
Googling around, I'm not seeing anyone else with the same problem.
absolutely stumped :/
October 17, 2013, 12:30:23 PM
3.6.3 is working on my router with a bit of crow-barring:
https://bitcointalksearch.org/topic/m.3356610
Not using windows anymore.
https://bitcointalksearch.org/topic/m.3356610
Not using windows anymore.
October 17, 2013, 12:16:25 PM
[2013-10-17 10:02:15] BAJ33: QueFlush failed no data returned (err=0 amt=0)
[2013-10-17 10:02:15] Thread 33 failure, exiting
[2013-10-17 10:02:15] BAJ2: QueFlush failed no data returned (err=0 amt=0)
[2013-10-17 10:02:15] BAJ0: RequestResults failed no data returned (err=0 amt=
0)
[2013-10-17 10:02:15] Thread 2 failure, exiting
[2013-10-17 10:02:15] BAJ7: QueFlush failed no data returned (err=0 amt=0)
[2013-10-17 10:02:15] Thread 7 failure, exiting
[2013-10-17 10:02:15] BAJ1: QueFlush failed no data returned (err=0 amt=0)
got same error as version 3.61 with win 8
[2013-10-17 10:02:15] Thread 33 failure, exiting
[2013-10-17 10:02:15] BAJ2: QueFlush failed no data returned (err=0 amt=0)
[2013-10-17 10:02:15] BAJ0: RequestResults failed no data returned (err=0 amt=
0)
[2013-10-17 10:02:15] Thread 2 failure, exiting
[2013-10-17 10:02:15] BAJ7: QueFlush failed no data returned (err=0 amt=0)
[2013-10-17 10:02:15] Thread 7 failure, exiting
[2013-10-17 10:02:15] BAJ1: QueFlush failed no data returned (err=0 amt=0)
got same error as version 3.61 with win 8
October 17, 2013, 11:19:44 AM
Just updated to windows 8.1 and my BFL SC Jalepeno would no longer work.
Heads up for anyone else having issues, the problem is not with cgminer but the USB driver. You just need to open zadig again and apply the WinUSB driver.
X
Heads up for anyone else having issues, the problem is not with cgminer but the USB driver. You just need to open zadig again and apply the WinUSB driver.
X
October 17, 2013, 10:09:40 AM
Shoot, I forgot to try 3.6.2 last night. Sorry. I just switched over to 3.6.3 though, so we'll see how that runs. Thanks again for all of your hard work.
October 17, 2013, 07:48:33 AM
When I done paying off some things I give you something. it may just not have whatever they gave you to make you go wow. 
October 17, 2013, 05:50:14 AM
New version: 3.6.3 - 17th October 2013
Just because I can't stand having a release out that is causing lots of problems, here's a release capitalising on the least worst aspects of 3.6 so far (for windows). Linux users seem fine regardless of which 3.6 release they use
Human readable changelog:
- Rolled back to libusb-1.0.16-rc10 instead of libusbx. This one intrinsically had the least worst incidence of run-over timeouts but had the issue with memory leaks when they're all done manually from within cgminer on windows. So as a compromise, the linux version does all timeouts from cgminer and the other OS versions use libusb's own timeouts and try to cancel transfers if they go beyond the libusb timeouts only. This will not completely obliterate the timeout issues on windows but should ameliorate them. It also should avoid running out of memory on windows due to the intrinsic leaks. Linux users should be blissfully unaffected by any of these issues and just benefit from the better performance/lower overhead.
- Kano added the overall MHS to summary (amazing what a BTC donation can do as an incentive - people take note!)
- Reverted some other internal usb changes that were unhelpful and possibly counterproductive.
Full changelog:
- API add 'MHS %ds' to 'summary'
- Optional lock tracking and stats via the API
- Speed up polling repeat again in usb poll thread and handle async after the
message to disable polling is complete.
- Revert to using timeouts on !linux since libusb leaks memory without them.
- Revert to libusb instead of libusbx
Just because I can't stand having a release out that is causing lots of problems, here's a release capitalising on the least worst aspects of 3.6 so far (for windows). Linux users seem fine regardless of which 3.6 release they use
Human readable changelog:
- Rolled back to libusb-1.0.16-rc10 instead of libusbx. This one intrinsically had the least worst incidence of run-over timeouts but had the issue with memory leaks when they're all done manually from within cgminer on windows. So as a compromise, the linux version does all timeouts from cgminer and the other OS versions use libusb's own timeouts and try to cancel transfers if they go beyond the libusb timeouts only. This will not completely obliterate the timeout issues on windows but should ameliorate them. It also should avoid running out of memory on windows due to the intrinsic leaks. Linux users should be blissfully unaffected by any of these issues and just benefit from the better performance/lower overhead.
- Kano added the overall MHS to summary (amazing what a BTC donation can do as an incentive - people take note!)
- Reverted some other internal usb changes that were unhelpful and possibly counterproductive.
Full changelog:
- API add 'MHS %ds' to 'summary'
- Optional lock tracking and stats via the API
- Speed up polling repeat again in usb poll thread and handle async after the
message to disable polling is complete.
- Revert to using timeouts on !linux since libusb leaks memory without them.
- Revert to libusb instead of libusbx
October 17, 2013, 03:50:18 AM
Yay windows. At this rate I'll ... completely deprecate windows support 
... actually expected that ages ago ...
Just sent you and Kano a little M$ Windoze support motivation.
Thanks for your efforts,
Sam
I can very well say the API still works perfectly on windows
I don't suppose you want that 5s MHs added to the summary also?
I'll do it shortly just in case
October 17, 2013, 03:07:41 AM
3.6.2 isn't quiting on Linux. Well it quits and doesn't ever stop completely.
I am guess that it shouldn't stop on que flush. Since this happens reguardless of the zombie units I can't just stop it by asking nicely for it to stop after a number of shares.
Anything I can do to help you find the problem I will be happy to do.
Code:
cgminer version 3.6.2 - Started: [2013-10-17 00:53:31]
--------------------------------------------------------------------------------
(2s):43.64G (avg):45.73Gh/s | A:5756 R:0 HW:11 WU:651.9/m
ST: 2 SS: 0 NB: 1 LW: 5819 GF: 0 RF: 0
Connected to multiple pools with block change notify
Block: 000902dd937a4e9a... Diff:268M Started: [00:53:30] Best share: 48.3K
--------------------------------------------------------------------------------
[P]ool management [S]ettings [D]isplay options [Q]uit
BAJ 0: max 43C 3.93V | 5.278G/5.255Gh/s | A:555 R:0 HW: 0 WU: 70.8/m
BAJ 1: max 41C 3.85V | 5.207G/5.172Gh/s | A:615 R:0 HW: 0 WU: 76.4/m
BAJ 2: max 44C 3.60V | 5.186G/4.959Gh/s | A:506 R:0 HW: 0 WU: 74.1/m
BAJ 6: max 45C 3.90V | 5.662G/5.411Gh/s | A:804 R:0 HW: 0 WU: 78.9/m
BAJ 7: max 43C 3.55V | 5.067G/5.165Gh/s | A:613 R:0 HW:11 WU: 74.5/m
BAJ 27: max 44C 3.99V | 5.495G/5.556Gh/s | A:333 R:0 HW: 0 WU: 82.3/m
BAJ 29: max 45C 4.02V | 5.071G/5.383Gh/s | A: 41 R:0 HW: 0 WU: 86.4/m
BAJ 32: max 44C 3.50V | 5.494G/5.481Gh/s | A:123 R:0 HW: 0 WU: 82.8/m
BAJ 33: max 45C 2.46V | 5.909G/5.447Gh/s | A: 65 R:0 HW: 0 WU: 78.3/m
--------------------------------------------------------------------------------
[2013-10-17 00:53:30] Pool 2 difficulty changed to 32
0)
[2013-10-17 01:02:15] BAJ2: RequestResults failed no data returned (err=0 amt=
0)
[2013-10-17 01:02:15] BAJ1: RequestResults failed no data returned (err=0 amt=
0)
[2013-10-17 01:02:15] BAJ6: RequestResults failed no data returned (err=0 amt=
0)
[2013-10-17 01:02:15] BAJ33: QueFlush failed no data returned (err=0 amt=0)
[2013-10-17 01:02:15] Thread 33 failure, exiting
[2013-10-17 01:02:15] BAJ2: QueFlush failed no data returned (err=0 amt=0)
[2013-10-17 01:02:15] BAJ0: RequestResults failed no data returned (err=0 amt=
0)
[2013-10-17 01:02:15] Thread 2 failure, exiting
[2013-10-17 01:02:15] BAJ7: QueFlush failed no data returned (err=0 amt=0)
[2013-10-17 01:02:15] Thread 7 failure, exiting
[2013-10-17 01:02:15] BAJ1: QueFlush failed no data returned (err=0 amt=0)
Anything I can do to help you find the problem I will be happy to do.
Jump to: