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

[ksenter]

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!

[-ck]

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.

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  .

Nah, just that it found a bug in it.

[TR4L]

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?

[Aurum]

http://ck.kolivas.org/apps/cgminer/temp/

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?

Win 7 64-bit SP1
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"
}

[P_Shep]

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
      }
   ],

[mgio]

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?

[juhakall]

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?

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.

[mgio]

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?

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".

[P_Shep]

http://ck.kolivas.org/apps/cgminer/temp/

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?

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.

[wolfskill]

Have been running 3.6.1 with the new files since 10-14-13 11:23pm EST, no issues.  Currently 5:13pm EST.

WolfSkill

[techman05]

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.

[-ck]

http://ck.kolivas.org/apps/cgminer/temp/

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?

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.

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

[P_Shep]

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

Oh.

Thought you have some other trickery in there :/

[viperzero]

linux/win/osx/mip/r-pi 3.6.1

+ RK3066 (ug802 etc android linux stick versions...)

I have been running for a week with 3.5 without errors on UG802 mkII with very low overhead under 2.5% CPU 

I am going to make UG802 my main mining platform because it only chews around 6 W and also serves multiple other purposes like web/development & backup server.


New RK3188 is on the way and might give this newest version a shot too.

Wondering should I upgrade to latest because 3.5 seems robust as a rock on rk3066. I'll put some beer pizza money on the way when my wallet updates. Thanks to BFL don't expect to get drunk overfed though.

Great work!

[-ck]

linux/win/osx/mip/r-pi 3.6.1

+ RK3066 (ug802 etc android linux stick versions...)

I have been running for a week with 3.5 without errors on UG802 mkII with very low overhead under 2.5% CPU 

I am going to make UG802 my main mining platform because it only chews around 6 W and also serves multiple other purposes like web/development & backup server.

New RK3188 is on the way and might give this newest version a shot too.

Wondering should I upgrade to latest because 3.5 seems robust as a rock on rk3066. I'll put some beer pizza money on the way when my wallet updates. Thanks to BFL don't expect to get drunk overfed though.

Great work!

Probably wait. There will likely be a 3.6.2 just around the corner, though so far 3.6.1 is kicking goals on linux.

[-ck]

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).

[viperzero]

Probably wait. There will likely be a 3.6.2 just around the corner, though so far 3.6.1 is kicking goals on linux.

Thanks for info. I am very happy overall with ministick arm xubuntu + Cgminer combo performance. Finally bitcoind catched the blockchain and BTC on the way. Seemed I also accidentally revealed CPU-hog from my previous post, xfce rotating screensaver referring nonexistent content 

[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\"}"

[kano]

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?

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".

It's never been in there and I can't ever remember anyone asking for it
(though I could have forgotten )
The 5s is also pretty unreliable ...
I'll add it soonish ... when I prioritise it ...

[Askit2]

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