Got one quick bug with temp. First it won't quit when I press q. Second it seems like some devices are dropping off. It said amu 1 not responding marked as dead.
I've had it on since I lated reported about 3 hrs ago, so at least I didn't come back to a complete wtf situation.
I'm swapping back to 3.5.1 for another few hours and make sure one of my euroupters didn't poop. If you get tweak in before that pm me and I'll try another temp file. I probably check in before that but we'll see what happens.
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 207. (Read 5805670 times)
October 15, 2013, 04:34:04 PM
October 15, 2013, 04:13:27 PM
Have been running 3.6.1 with the new files since 10-14-13 11:23pm EST, no issues. Currently 5:13pm EST.
WolfSkill
WolfSkill
October 15, 2013, 04:06:42 PM
I replaced cgminer-nogpu.exe with the one in the above temp folder. I get ever increasing lines of:
AMU 0 usb write err:(-7) LIBUSB_ERROR_TIMEOUT
Odd. What hardware are you using?AMU 0 usb write err:(-7) LIBUSB_ERROR_TIMEOUT
I got this after a couple of hours too.
Win cgminer-nogpu 3.6.1, with 1 BFL SC 60GHz
Now trying the debug version you put up.
October 15, 2013, 03:50:30 PM
I've been using the cgminer API to get statistics about my mining devices.
One thing I can't seem to find is the current hashrate (or 5sec average hashrate). I see an average hashrate that appears to be since the machines was started but I don't see the current hashrate.
If this statistic is not available, how can I calculate it from what is available?
One thing I can't seem to find is the current hashrate (or 5sec average hashrate). I see an average hashrate that appears to be since the machines was started but I don't see the current hashrate.
If this statistic is not available, how can I calculate it from what is available?
You can sum the 5s hashrate of each device from the devs reply. It's a good question though why this can't be included in the summary reply.
oh thanks! It was in "devs". I thought I had tried every command. Yeah, it would make sense if it was in "summary".
October 15, 2013, 03:44:37 PM
I've been using the cgminer API to get statistics about my mining devices.
One thing I can't seem to find is the current hashrate (or 5sec average hashrate). I see an average hashrate that appears to be since the machines was started but I don't see the current hashrate.
If this statistic is not available, how can I calculate it from what is available?
One thing I can't seem to find is the current hashrate (or 5sec average hashrate). I see an average hashrate that appears to be since the machines was started but I don't see the current hashrate.
If this statistic is not available, how can I calculate it from what is available?
You can sum the 5s hashrate of each device from the devs reply. It's a good question though why this can't be included in the summary reply.
October 15, 2013, 03:37:20 PM
I've been using the cgminer API to get statistics about my mining devices.
One thing I can't seem to find is the current hashrate (or 5sec average hashrate). I see an average hashrate that appears to be since the machines was started but I don't see the current hashrate.
If this statistic is not available, how can I calculate it from what is available?
One thing I can't seem to find is the current hashrate (or 5sec average hashrate). I see an average hashrate that appears to be since the machines was started but I don't see the current hashrate.
If this statistic is not available, how can I calculate it from what is available?
October 15, 2013, 03:28:44 PM
Why's my API output garbled???
(3.6.1 windows binary)
"SUMMARY": [
{
"Elapsed": 8429,
"MHS av": 6,
+43.+1,
"Found Blocks": 0,
"Getworks": 196,
"Accepted": 2399,
"Rejected": 17,
"Hardware Errors": 553,
"Utility": 2-.1.,
"Discarded": 374,
"Stale": 0,
"Get Failures": 0,
"Local Work": 309488,
"Remote Failures": 0,
"Network Blocks": 27,
"Total MH": 5-.2,
4320.2-,
1,
"Work Utility": 8-0./3,
"Difficulty Accepted": 11/4,
.,
"Difficulty Rejected": 8-4,
"Difficulty Stale": 0,
"Best Share": 246339597,
"Device Hardware%": 0.51/-,
"Device Rejected%": 0.72,
,
,
"Pool Rejected%": 0.703.,
"Pool Stale%": 0
}
],
(3.6.1 windows binary)
"SUMMARY": [
{
"Elapsed": 8429,
"MHS av": 6,
+43.+1,
"Found Blocks": 0,
"Getworks": 196,
"Accepted": 2399,
"Rejected": 17,
"Hardware Errors": 553,
"Utility": 2-.1.,
"Discarded": 374,
"Stale": 0,
"Get Failures": 0,
"Local Work": 309488,
"Remote Failures": 0,
"Network Blocks": 27,
"Total MH": 5-.2,
4320.2-,
1,
"Work Utility": 8-0./3,
"Difficulty Accepted": 11/4,
.,
"Difficulty Rejected": 8-4,
"Difficulty Stale": 0,
"Best Share": 246339597,
"Device Hardware%": 0.51/-,
"Device Rejected%": 0.72,
,
,
"Pool Rejected%": 0.703.,
"Pool Stale%": 0
}
],
October 15, 2013, 03:24:13 PM
I replaced cgminer-nogpu.exe with the one in the above temp folder. I get ever increasing lines of:
AMU 0 usb write err:(-7) LIBUSB_ERROR_TIMEOUT
Odd. What hardware are you using?AMU 0 usb write err:(-7) LIBUSB_ERROR_TIMEOUT
AMD FX-8350 Vishera CPU
8 GB DDR3
2 x Radeon HD 7970 running cgminer.exe 3.6.1 in a separate instance.
153 GB HDD
28 Block Eruptors on powered USB hubs with WinUSB drivers running in their own instance of cgminer-nogpu.exe 3.6.1
{
"pools" : [
{
"url" : "stratum+tcp://pool1.us.multipool.us:3332",
"MultiPool" : " BitCoin (BTC) ",
"user" : "Aurum.Miner",
"pass" : "pw"
}
],
"failover-only" : true,
"api-mcast-port" : "4028",
"api-port" : "4028",
"hotplug" : "15",
"log" : "5",
"shares" : "0",
"kernel-path" : "/usr/local/bin",
"icarus-options" : "115200:1:1",
"icarus-timing" : "3.0=100"
}
October 15, 2013, 03:08:05 PM
I'm running:
Linux 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Every time I open CGminer, I get a segmentation fault error and it doesn't matter what version I use. I can't seem to get it to work. Can anyone help me?
Linux 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Every time I open CGminer, I get a segmentation fault error and it doesn't matter what version I use. I can't seem to get it to work. Can anyone help me?
October 15, 2013, 03:00:35 PM
Should 3.6.1 be working? I've had it on for maybe 1 Minute with no errors showing on windows 7.
I'm using block eroupters if that makes any difference.
Current one runs out of memory eventually on windows. The binaries in temp/ are currently the best 3.6.1 working ones for windows.I'm using block eroupters if that makes any difference.
yeah it just hit. it was running fine since this morning and now I got it. Only difference I did was running bitcoin-qt ver 8.5.
Does whats happening with the version of lib mean you found its peak
. October 15, 2013, 02:58:58 PM
Btw, it ran all night. So far so good.
In that case it's definitely better. We may have to finally move libusb to libusbx then.Yeah it's been running for about 18 hours so far. So it's probably not going to crash, I think.
Thanks for all your hard work!
October 15, 2013, 02:57:39 PM
Should 3.6.1 be working? I've had it on for maybe 1 Minute with no errors showing on windows 7.
I'm using block eroupters if that makes any difference.
Current one runs out of memory eventually on windows. The binaries in temp/ are currently the best 3.6.1 working ones for windows.I'm using block eroupters if that makes any difference.
yeah it just hit. it was running fine since this morning and now I got it. Only difference I did was running bitcoin-qt ver 8.5.
I've went along and copied the files from temp folder. Hopefully you've found what to kill and we'll be on 3.6.2 shortly.
October 15, 2013, 02:42:37 PM
I replaced cgminer-nogpu.exe with the one in the above temp folder. I get ever increasing lines of:
AMU 0 usb write err:(-7) LIBUSB_ERROR_TIMEOUT
Odd. What hardware are you using?AMU 0 usb write err:(-7) LIBUSB_ERROR_TIMEOUT
October 15, 2013, 02:41:48 PM
Btw, it ran all night. So far so good.
In that case it's definitely better. We may have to finally move libusb to libusbx then. October 15, 2013, 02:39:14 PM
Should 3.6.1 be working? I've had it on for maybe 1 Minute with no errors showing on windows 7.
I'm using block eroupters if that makes any difference.
Current one runs out of memory eventually on windows. The binaries in temp/ are currently the best 3.6.1 working ones for windows. I'm using block eroupters if that makes any difference.
October 15, 2013, 02:38:09 PM
wouldn't see so bad to report if git hub had report bugs option for cgminer on. then all the things you find wouldn't get buried over. This post is at least 600 pages deep 
.
People were using it for support instead of bug reporting. . October 15, 2013, 12:20:32 PM
wouldn't see so bad to report if git hub had report bugs option for cgminer on. then all the things you find wouldn't get buried over. This post is at least 600 pages deep .
. October 15, 2013, 11:51:29 AM
I am re-compiling on Windows to get ready for some Bitfury's
The precompiled Windoze binaries don't work?
The pre-compiled exe's work fine, but it is open source and I like to compile my own for a number of various reasons.
OK, that's cool.
I'm guessing you already looked in the windows-build file?
I'll just shut up now.
Good Luck,
Sam
NP Sam
The problem been around a while and I have not found the answer in this thread or any of the build docs, etc. I was trying to stay out of the dev's way until I really started to need it as they have been very busy doing all this fantastic work on ASIC support.
October 15, 2013, 11:02:59 AM
Should 3.6.1 be working? I've had it on for maybe 1 Minute with no errors showing on windows 7.
I'm using block eroupters if that makes any difference.
I'm using block eroupters if that makes any difference.
October 15, 2013, 10:30:29 AM
3.6.1 isn't working for me. (win7x64 - 33 usb block erupters). I let it run for a while, then it stopped mining, repeatedly saying something like USB write error_no_mem.
I tried to copy/paste the error but lost it. I can get it again if need be.
And FFS LOL windows. Always with the new and exciting modes of failure. This suggests a memory leak within the windows specific part of the libusb code. Anyway now that timeouts are managed differently it means we can try libusbx instead of libusb, so I'm putting up some testing binaries that use it. Please try them, but I'm not holding much to hope.I tried to copy/paste the error but lost it. I can get it again if need be.
http://ck.kolivas.org/apps/cgminer/temp/
AMU 0 usb write err:(-7) LIBUSB_ERROR_TIMEOUT
Jump to: