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

[Ntrain2k]

Any tips for getting the correct speed out of CGMiner for the new/old R-boxes?

I've tried several flavors, including the one from rockminer and can't get anywhere near the speed I get with bfgminer which runs the new r-boxes slow to begin with.

[1498331593]

1498331593

[1498331593]

1498331593

[1498331593]

1498331593

[cat2]

Can somebody point me to download of cgminer for raspberry pi running pidora with gridseed 5 chip. Also never compiled anything before so instructions for that or cgminer already compiled would be helpful.

[morda]

im going to sound like a noob, but could anyone explain to me how to set up the config file for the cgminer?
cos when im manually inserting pool data when it promotes for it, the miner says pool invalid

[Newar]

im going to sound like a noob, but could anyone explain to me how to set up the config file for the cgminer?
cos when im manually inserting pool data when it promotes for it, the miner says pool invalid

Check out https://github.com/ckolivas/cgminer/blob/master/example.conf
Easiest is to save the config file from the menu to get you started.
What do you enter for pool information?

[sdjernes]

Please note that the build of CGminer 4.7.0 currently in Debian unstable probably will not work. It was compiled with some of the drivers enabled that should only be enabled on dedicated hardware.   

I am working with the Debian pkg-bitcoin-dev team to get this fixed.

[-ck]

New release: Version 4.7.1, 4th November 2014

Minor bugfix release after dusk.


Human readable changelog:

- We used to yield after dropping locks in cgminer to allow low power machines (eg RPi) to work properly with heavily threaded code. Now it only does this on machines where one CPU only is detected otherwise it is wasteful but probably will have no demonstrable effect in anything but microbenchmarks.
- Changed the configure build system to make it impossible to build more than one device in if the chosen driver was meant to be used standalone, along with more explicit tagging of standalone drivers in the configure help. This should make it easier to choose a more suitable configuration for distribution packaging.
- Added yet more warnings suggesting not to use the system libusb in configure.
- Check if pools are alive more frequently if there is only one pool enabled.
- Don't think that unhandled stratum messages are untracked shares, just filter them out.
- Added support for mining.ping which is a stratum extension in ckpool.
- Changed the use of suggest-diff to the newly agreed upon standard of putting the diff in the json parameters.
- Fixed a crash that happens when write is chosen from the menu and the hashratio driver is built into the binary.
- We did not stop receiving stratum messages from pools that we disabled from the menu previously.
- If "restart" was chosen from the menu, any sockets to old pools were not closed down leading to many persistent connections to the pool with each restart. Now these are properly closed (though quit and start again is always more reliable than a restart anyway).
- Work utility meter was broken in the last release due to maxdiff being set very high for any drivers that didn't set it. Instead maxdiff is assumed to be 1 now unless the driver has it explicitly set showing support for internal driver diff.
- If the pool priority order is changed while running and we save the config from the menu it will now save the new priority order.
- Hashfast voltage support for Yoli/Habanero/Bitcrane etc. boards (see ASIC-README)
- SP30 driver improvements, fixing the hashrate meter.
- Fixed API taking both an IPV6 and IPV4 address.
- Fixed OSX build.
- Added the ability to build libusb without libudev (eg. on BBB)
- Fixed a small delay in generating more work when queue is set to zero.
- If different USB devices contain the same communication chip, provided the USB device has a product id set, cgminer will no longer try to use the wrong driver on it (eg LIN vs BFLSC).
- Added support for more USB3 hubs on windows.
- Fixed the hashfast driver not building when libcurl is disabled.


Full changelog:

- Selectively yield on dropping a lock only on single CPU platforms
- Make it impossible to configure in more than one device that is meant to be
standalone. Add more information to configure help, along with comments for new
drivers.
- Add warning against system libusb in configure help
- stratum_rthread sleep only 3s when all the pool have disconnected
- Filter responses that don't have a result
- Implement support for pool ping and json integers of zero in getversion and
ping
- Fix segfault when writing config with hashratio built in
- Save pools in priority order at time of writing config
- Set the correct flag for close on exec for sockets
- Suspend stratum on removing a pool
- Set CLOEXEC on sockets on linux
- Drivers that take a diff should specify a max diff or it is assumed they don't
support one so set max_diff to 1 if unset
- Send hfa generic frame only if voltage was specified on the command line for
that device
- Set hashfast voltage settings only when really needed
- Hashfast voltage support
- Increase max diff on sp30 to 1024
- Reset ipv6 flag to false in every api-allow loop
- undeclared identifier 'IPV6_ADD_MEMBERSHIP' fix for apple
- two back temps spondoolies2
- two back temps spondoolies
- correct suggest_difficulty json rpc call
- Add more usb3 hub identifiers for windows
- Set driver max diff to large value if unset
- Wake gws on get queued
- Implement blacklisting of attempting to match known products from ones without
identifiers
- Fix hfa driver building without libcurl
- Enable building libusb without udev
- Fix off by one calculation error in sp30 leading zeroes
- Send correct diff work to sp30 for hashmeter to be correct
- Do the sleep in spondoolies_queue_full_sp30 after dropping the lock
- Minor tidy in sp30 driver
- Fix sp30 warnings

[Newar]

New release: Version 4.7.1, 4th November 2014
[...]

As far as I can tell github is still at 4.7.0? I was looking forward to the Hashfast addition and just pulled and built, but 4.7.0 is the latest tag ( git tag -l ). So, now I wonder is it in there or not yet?

[kuzetsa]

New release: Version 4.7.1, 4th November 2014
[...]

As far as I can tell github is still at 4.7.0? I was looking forward to the Hashfast addition and just pulled and built, but 4.7.0 is the latest tag ( git tag -l ). So, now I wonder is it in there or not yet?

either a mysterious delay happened with github or your local git repo hadn't been refreshed, or maybe some other reason it wasn't showing up when you looked???

it looks fine to me:

Code:

commit 72375c3ec5b2a94243ae32cc43f3a36d2375eab0
Author: Con Kolivas <kernel@kolivas.org>
Date:   Tue Nov 4 16:14:53 2014 +1100

https://github.com/ckolivas/cgminer/releases/tag/v4.7.1

[Newar]

[...] mysterious [...]

Don't know what the problem was, I had also tried to hard reset to master to no avail. I then removed the cgminer folder entirely and cloned again and it showed v4.7.1 (git tag -l), but it still built 4.7.0. I then selected 4.7.1 manually (git checkout tags/v4.7.1) and that finally did the trick.

[...]
- Hashfast voltage support for Yoli/Habanero/Bitcrane etc. boards (see ASIC-README)
[...]

Thank you!


Spotted this when building on a RPi with --enable-hashfast:

./configure: line 11925: -pthread: command not found

A quick search in the tread showed this error in reference to Avalon devices.

As far as I can tell it has no influence on running cgminer in this case, however.

[-ck]

Spotted this when building on a RPi with --enable-hashfast:

./configure: line 11925: -pthread: command not found

It's a harmless warning due to a minor config script error in the included libusb. Ignore.

[Ntrain2k]

Has anyone else ran into a problem getting the new cgminer to run the r-boxes at full speed?

[AngusCanine]

is there a downloadable openwrt files for the newer ant s1's after 3.12 offered at bitmain ?

[SVK]

Sorry for stupid question.

Latest releases do not work at all
Is it only me or ?

Thank you

[Gologuzan]

hi all,
i have a question.
i am using cgminer on one of my miners, and i have a problem.
when i turn on miner it connect to internet and hash perfectly. BUT when internet get disconnected, miner sound alarm,
and when it gets internet, alarm stops but miner does not start hashing. i need to reset it through putty and then it starts hashing normally.
so i guess that  i need some script that resets cgminer when internet comes back.
miner is using rPi.

thx for your time.

[Blazed]

Having some issues with AM Prisma using the USB adapter

Cgminer 4.7.1
Rasp Pi running latest wheezy
compiled using: --enable-blockerupter --enable-icarus --without-curses

./cgminer -o stratum+tcp://us1.ghash.io:3333 -u xxxx -p xxxx --bet-clk 23

Cgminer spits out a bunch of errors

[2014-11-06 17:44:02] BET0: Unexpected value 00 received                   
[2014-11-06 17:44:02] BET0: Sync Error                   
[2014-11-06 17:44:02] BET0: Unexpected value 58 received                   
[2014-11-06 17:44:02] BET0: Sync Error                   
[2014-11-06 17:44:02] BET0: Unexpected value 58 received   

it then segfaults after a little bit.

I am not sure if my cgminer command is wrong or the USB dongle is the issue.. I have tried plugging directly into Pi and also a power USB hub with the same results.

[sdjernes]

Having some issues with AM Prisma using the USB adapter

Cgminer 4.7.1
Rasp Pi running latest wheezy
compiled using: --enable-blockerupter --enable-icarus --without-curses

./cgminer -o stratum+tcp://us1.ghash.io:3333 -u xxxx -p xxxx --bet-clk 23

Cgminer spits out a bunch of errors

[2014-11-06 17:44:02] BET0: Unexpected value 00 received                   
[2014-11-06 17:44:02] BET0: Sync Error                   
[2014-11-06 17:44:02] BET0: Unexpected value 58 received                   
[2014-11-06 17:44:02] BET0: Sync Error                   
[2014-11-06 17:44:02] BET0: Unexpected value 58 received   

it then segfaults after a little bit.

I am not sure if my cgminer command is wrong or the USB dongle is the issue.. I have tried plugging directly into Pi and also a power USB hub with the same results.

I get this also but if I restart CGminer a few times it eventually starts hashing fine.  Seems that there is something odd with the driver or the chips put out some odd crap at first after power up.

However I have a question about the -bet-clk=23 thing  According to CGminer docs this value is x10 so to get 240 you would want 24, which is the default value of the setting.  Am I understanding this wrong?  Do we need to run the Prisma at 230 not 240?  At --bet-clk=23 my unit will not do stable over 800Ghs

[Blazed]

I tried 24 with same results..does not seem to matter. I guess I will just try 1 board and see what it does for me.

[-ck]

Yep sorry the block erupter driver is absolutely submitted and maintained by AM and I don't have the hardware so I can't help you directly but I suspect the driver is buggy (it should never segfault for example). Hopefully they chime in here with support and fix the bugs.

[-ck]

Sorry for stupid question.

Latest releases do not work at all
Is it only me or ?

It's only you. We can't help you without you giving us any information whatsoever on what the problem is.

[SVK]

Sorry for stupid question.

Latest releases do not work at all
Is it only me or ?

It's only you. We can't help you without you giving us any information whatsoever on what the problem is.

My bad

Downloaded 4 latest version(4.7.1, 4.7.0, 4.6.1, 4.6.0), created .bat file and nothing, just black window appeared for a split of a second.
Same bat file works with 4.5.0 version.

I'm using Win 7 and I have habanero board.
(I'm mining with 4.5.0 but wanted to try newer versions)

Thank you very much