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

[-ck]

I'm unable to compile 3.4.0 on Mac OS X:

Code:

util.c: In function ‘cgtimer_time’:
util.c:891: warning: implicit declaration of function ‘clock_gettime’
util.c:891: error: ‘CLOCK_MONOTONIC’ undeclared (first use in this function)
util.c:891: error: (Each undeclared identifier is reported only once
util.c:891: error: for each function it appears in.)
util.c: In function ‘nanosleep_abstime’:
util.c:899: warning: implicit declaration of function ‘clock_nanosleep’
util.c:899: error: ‘CLOCK_MONOTONIC’ undeclared (first use in this function)
util.c:899: error: ‘TIMER_ABSTIME’ undeclared (first use in this function)

Seems like clock_gettime(CLOCK_MONOTONIC, ...) is not available on OS X.

Yay for more unimplemented POSIX features on an operating system that claims to be POSIX. More like POSOSX.

Will create a generic workaround for the next version.

[Karin]

Unofficial Mac binaries updated to 3.3.4 at http://spaceman.ca/cgminer.

This directly relates to the whole libusb monologue I've been having in here over the last month
That specifically means your libusb on your mac is bugged - the timeout option when doing I/O isn't working
The README says how to build with a working libusb and it works on Linux and Windows - no idea about a Mac ...
Tell whoever Karin is to read the README ...

Karin, read the README 

I'm Karin!

I keep a very close eye on the readme's (even following their changes on github), and I've tried using rc10 but if I recall it had no effect on this bug on Macs, so I instead include the latest libusb in my builds.

Kano makes it sounds like the error confidently lies within libusb, so I'll do a full spectrum of tests with various libusb versions.  If I can find a version that works I will update cgminer for Mac OS X and Asteroid (my Mac GUI to cgminer) accordingly.

Otherwise, we'll have to dig deeper into libusb, and any errors generated from cgminer (and what the community can help with) would be our best bet in figuring out the issue with libusb + Macs.  I'll try and do these test builds tonight and will post back with what I find.

Yes the problem is clearly libusb.
As I have already stated, I can run two different libusb versions on the same architecture and one works while the other doesn't.
The test problem that I've mentioned in here a few times is standalone code (bits and pieces of the code I've written in cgminer - but modified) and that shows if timeouts are working ... and if they are matching the expected values also.

https://bitcointalk.org/index.php?topic=28402.msg2817682;topicseen#msg2817682
https://bitcointalk.org/index.php?topic=28402.msg2846296;topicseen#msg2846296
https://bitcointalk.org/index.php?topic=28402.msg2938585;topicseen#msg2938585

That specific version - libusb-1.0.16-rc10 - works on Linux and Windows
I've seen other 1.0.16 versions that don't work ... thus using the 'latest' libusb is not guaranteed to solve it.
Also, libusb has 2 sources: libusb and libusbx, and some OSs provide libusbx instead of libusb

The README also states how to use the libusb mentioned

Okay, I've solved this problem on Mac OS X by using libusb-1.0.2.  Unfortunately, this version is from 2009, but it has worked well in testing with my own admittedly limited gear (one USB block erupter, one GPU).

I ran 44 test cases to determine this: 22 versions of libusb, 20 versions of libusbx, and a few alternates I located around the web.  They span every official release and release candidate of the two libusb branches since 2009.

6 would not configure, 1 would not compile, 4 would not link with cgminer, 5 would not successfully access the USB device, 28 exhibited "TIMEOUT GetResults took 2000ms but was 100ms" errors, and only one worked without errors and generated the correct output (libusb-1.0.2).  I could not get kano's usbfail.c to compile, so I simply built 44 versions of cgminer statically linked to the different libusb builds and ran my tests over 10 minutes of runtime each.

I've updated my cgminer for Mac OS X universal binaries as of a few moments ago, and will be submitting my findings to the other Mac cgminer projects (asteroid, xgminer, multiminer, macminer) for their own testing.

If this does indeed work for others, then the next step would be to approach the libusbx people and/or dig into the code myself, so that we can get a newer libusb/libusbx but with the correct operability of v1.0.2.  Or perhaps 1.0.2 is fine.

[Krak]

Since upgrading to cgminer 3.4.0, my Jalapeno went from ~5.7 GH/s to ~5.5 GH/s. Should I let it cool down and restart it? I think something like that was discussed in this thread before.

[Trongersoll]

Since upgrading to cgminer 3.4.0, my Jalapeno went from ~5.7 GH/s to ~5.5 GH/s. Should I let it cool down and restart it? I think something like that was discussed in this thread before.

it seems starting hash rate is partially determined based on Temperature at startup. so yeah, let it cool. some people have been refrigerateing them prior to turn on.

[Krak]

it seems starting hash rate is partially determined based on Temperature at startup. so yeah, let it cool. some people have been refrigerateing them prior to turn on.

Hmm, refrigerating doesn't sound like a good idea. Wouldn't there be a problem with moisture?

[Trongersoll]

it seems starting hash rate is partially determined based on Temperature at startup. so yeah, let it cool. some people have been refrigerateing them prior to turn on.

Hmm, refrigerating doesn't sound like a good idea. Wouldn't there be a problem with moisture?

*shrug* i only know what it read here. maybe they  put them in a plastic bag or frost free freezer. Pure water isn't a great conductor. It is the impurities in most water that causes problems. (doning protective vest)

[-Redacted-]

The problem isn't so much when they are in the freezer as it is the water that condenses on them after you take it out....

[Krak]

Stuck it in the fridge for about 30 minutes and it doesn't seem to have helped. If anything, it looks like it's gotten worse; down to ~5.4 GH/s now.

[chanson]

Since upgrading to cgminer 3.4.0, my Jalapeno went from ~5.7 GH/s to ~5.5 GH/s. Should I let it cool down and restart it? I think something like that was discussed in this thread before.

You can isolate whether it is the Jalapeno startup or changes in 3.4.0 by comparing hash rates with your previous version of cgminer.

[miter_myles]

Just wanted to say that it seems 3.4.0 has made my HW errors on the USB BEs drop significantly... very nice!  thx!

[Samael82]

Hi! I'm trying to mine beyond firewall and proxy, so i use tor's vidalia to connect to the work servers.
Intresting detail - if we have an http and stratum proxy on mining pool, http redirects cgminer to stratum, and cgminer works correctly.
But if we have "plain stratum", cgminer can not conect to it through tor's socks5. For example, I'm mining LTC on litepool.ru right now. I connect to it through 8337 port, old getwork protocol. I used to mine on 50btc.com, where was getting connect throug old port too.
But when i trying to connetc to liteguard.com, which have only plain strtum proto, cgminer says "credentials are invalid" or pool is down.
If you teach it to work with stratum through socks5, it will be superior!

[OtaconEmmerich]

Just wanted to say that it seems 3.4.0 has made my HW errors on the USB BEs drop significantly... very nice!  thx!

What was it before and what is it now?

[Zanatos666]

Stuck it in the fridge for about 30 minutes and it doesn't seem to have helped. If anything, it looks like it's gotten worse; down to ~5.4 GH/s now.

That doesnt sound like a particularly good idea.  Have you tried removing the casing and inverting the fan so its blowing down?

[os2sam]

Stuck it in the fridge for about 30 minutes and it doesn't seem to have helped. If anything, it looks like it's gotten worse; down to ~5.4 GH/s now.

That doesnt sound like a particularly good idea.  Have you tried removing the casing and inverting the fan so its blowing down?

I did that a couple days ago and my temp went from 45C to 35C.

[Zanatos666]

Stuck it in the fridge for about 30 minutes and it doesn't seem to have helped. If anything, it looks like it's gotten worse; down to ~5.4 GH/s now.

That doesnt sound like a particularly good idea.  Have you tried removing the casing and inverting the fan so its blowing down?

I did that a couple days ago and my temp went from 45C to 35C.

I did that when I flashed my firmware.  Even with the increased hash rate, I went from ~42 to ~38.  Just breathes better.

[crazyates]

Stuck it in the fridge for about 30 minutes and it doesn't seem to have helped. If anything, it looks like it's gotten worse; down to ~5.4 GH/s now.

That doesnt sound like a particularly good idea.  Have you tried removing the casing and inverting the fan so its blowing down?

I did that a couple days ago and my temp went from 45C to 35C.

I did that when I flashed my firmware.  Even with the increased hash rate, I went from ~42 to ~38.  Just breathes better.

Did you guys keep the big 120mm fans, or get rid of them along with the case? If you got rid of them, I'd imagine just the two smaller fans would be a lot quieter than all 4.

[KyrosKrane]

Greetings.

I'm a recent entry into the world of ASIC mining. I've got a small array of 31 ASICMiner Block Erupters that I'm trying to set up as a "fire-and-forget" setup that I can just run in a remote location (where I get free electricity).  Eventually I plan to run this off a Raspberry Pi, but that's a story for another day.

Right now, I'm using a Windows 8 x64 PC as a host. I've consistently been getting crashes when running cgminer.  Here's my setup:

6x D-Link DUB-H7 hubs

Hub #1 is the "master" hub.  The other five connect to it.  Hub 1 also holds a USB fan and a single block erupter.
Hubs 2-5 each contain six block erupters.  Each is plugged into hub #1.
Hub #1 is connected to my host PC.

I ran the zadig tool and configured the drivers.

With cgminer 3.3.1, if I plug in the array first, then start cgminer, cgminer will instantly crash.  If I start cgminer first, then plug in the array, it seems to work.  At least, I didn't experience any crash issues.  However, this is unsustainable as I plan to run this rig remotely, so I need to be able to reboot the machine periodically without having to unplug and replug the array.

With cgminer 3.4.0, I can start it with the array plugged in, and it hashes normally, at expected values.  However, after about 1-12 hours (varies), it crashes as per the screenshot below:



In this screenshot, it crashed after only about an hour of running.

My config file only contains my pool info, no other options.  I start cgminer with a shortcut in the startup folder in windows, which just runs the executable - no command line options.  Alternately, when restarting cgminer after a crash, I double-click on the .exe.

Any thoughts on what I might be doing wrong?

I'm thinking of just using the looping-restart batch file someone posted earlier in the thread, but that's just a workaround, not a fix.

(Side note: My PC has an AMD APU, which cgminer picks up and runs for an extra 50MH/s.  Bonus! )

[os2sam]

Hubs 2-5 each contain six block erupters.  Each is plugged into hub #1.

What is the current rating of your hub power supplies?  You need more than 3 Amps as each Erupter draws .5 Amp.

[Zanatos666]

Stuck it in the fridge for about 30 minutes and it doesn't seem to have helped. If anything, it looks like it's gotten worse; down to ~5.4 GH/s now.

That doesnt sound like a particularly good idea.  Have you tried removing the casing and inverting the fan so its blowing down?

I did that a couple days ago and my temp went from 45C to 35C.

I did that when I flashed my firmware.  Even with the increased hash rate, I went from ~42 to ~38.  Just breathes better.

Did you guys keep the big 120mm fans, or get rid of them along with the case? If you got rid of them, I'd imagine just the two smaller fans would be a lot quieter than all 4.

Its a single 92mm fan.  I kept it, its not bad.  Its sitting on top of my desk in an office.  I get enough of people talking around me, plus I have headphone on 99% of the time so I never hear it.

[KyrosKrane]

Hubs 2-5 each contain six block erupters.  Each is plugged into hub #1.

What is the current rating of your hub power supplies?  You need more than 3 Amps as each Erupter draws .5 Amp.

3A, 5V power supplies.  Over on the USB hub thread, these have been consistently reported as supporting 6BE each, sometimes 6 + a fan.