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

[LARTAS]

Hi Mr Ckolivas
Is the New version without ZOMBI's for cointerra devices?
Thanks

[-ck]

Hi Dr Ckolivas
Is the New version without ZOMBIEs for cointerra devices?

Yes it is.

[LARTAS]

Hi Dr Ckolivas
Is the New version without ZOMBIEs for cointerra devices?

Yes it is.

Thanks¡¡¡¡¡

[JoseSan]

One Cointerra difference I noticed - I guess I get a lot of hardware errors, but compared to 4.2.3, 4.5.0 is spamming "CTA 0: Notify bad match work", due to the change from a debug-log error to a warning:

https://github.com/ckolivas/cgminer/commit/0df5ca450874b790a418d928440f199bb70ad0ce#diff-742994a60422e991277c4e9150c70b41R400

The full debug log reads like:

CTA0: invalid nonce - HW error                                                                                       
CTA 0: Notify bad match work                                                                                         
False match sent: work id 398 midstate c97c5ce931b02152910c4b3a75784b309a22087b57011e49e2a9840b323424b0  blkhdr 6655f$
False match reports: work id 0x0169 MCU id 0x65030000 work diff 64.0                                                 
False match tested: nonce 0xc7b58fe8 noffset 41 813b0654da5ab31bfUü\205į×S¢®:^X                                     
False match devdiff set to 64.0 share diff calc 0

It's totally aesthetic so I'm not complaining. Was there a reason for the change?

[Buchi-88]

THX for the new version, i will test it 😋

[Rob7]

1. I tray below command for Rockminers, but it doesn't work

The second version
  --usb BAS:1,BFL:1,MMQ:0,ICA:0,KLN:0
allows you to specify how many devices to choose based on each device
driver cgminer has - the current USB drivers are:
AVA, BAS, BFL, BF1, DRB, HFA, ICA, KLN and MMQ.

What name is correct for:
ANU - Antminer U2
LIN - Rockminer R32
LIR - Rockminer RK/R3

2. Hotplug

--hotplug <arg>     Seconds between hotplug checks (0 means never check)

What is default value?

[os2sam]

2. Hotplug

--hotplug <arg>     Seconds between hotplug checks (0 means never check)

What is default value?

Just a WAG but I would say 5 seconds

"--hotplug <arg>     Set hotplug check time to <arg> seconds (0=never default: 5) - only with libusb

[aurel57]

I am having problems logging on to my S3. I was logged in last night and this morning it asked me to reenter my password to log in. When I did this is what I see:

/usr/lib/lua/luci/dispatcher.lua:448: Failed to execute function dispatcher target for entry '/'.
The called action terminated with an exception:
/usr/lib/lua/luci/sauth.lua:87: Session data invalid!
stack traceback:
   [C]: in function 'assert'
   /usr/lib/lua/luci/dispatcher.lua:448: in function 'dispatch'
   /usr/lib/lua/luci/dispatcher.lua:195: in function </usr/lib/lua/luci/dispatcher.lua:194>

It is still hashing on my pool ( @ 410-420 GH/s on 218.75 freq) and I have tried to log in a few more times with always the same results. Not sure if it's safe to power down or to use the reset button? Any help would be appreciated.

[nst6563]

Has anyone gotten CGMiner 4.5 to run with the Gridseed A1 units?  I see A1 files in it, I've compiled it with the A1 support....but it never detects the A1 hardware when I run it. 

command line:  sudo ./cgminer -o pooladdress -u username -p password --bitmine-a1-options 16000:800000:2000

The unit has a built in rpi and the A1 controller board is connected to the GPIO pins.  I've tried running on the image that came with the hardware, as well as compiling on a generic raspbian image....same result....it doesn't find the A1 hardware. 

What am I missing?

The hardware I'm speaking of is this one in particular:

[Askit2]

I am having problems logging on to my S3. I was logged in last night and this morning it asked me to reenter my password to log in. When I did this is what I see:

/usr/lib/lua/luci/dispatcher.lua:448: Failed to execute function dispatcher target for entry '/'.
The called action terminated with an exception:
/usr/lib/lua/luci/sauth.lua:87: Session data invalid!
stack traceback:
   [C]: in function 'assert'
   /usr/lib/lua/luci/dispatcher.lua:448: in function 'dispatch'
   /usr/lib/lua/luci/dispatcher.lua:195: in function </usr/lib/lua/luci/dispatcher.lua:194>

It is still hashing on my pool ( @ 410-420 GH/s on 218.75 freq) and I have tried to log in a few more times with always the same results. Not sure if it's safe to power down or to use the reset button? Any help would be appreciated.

I'm positive this is where you want to post this question

https://bitcointalk.org/index.php?topic=671189.3740

The LuCi and openwrt are not by con or the cgminer crew. It is possible one of the nice folks on here will know the answer though. Bitmain and openwrt would have actually done the programming for that part.

EDIT: I can't wait for a binary that uses a new version of cgminer. I really should look into if its possible to add a config file and have everything work as I like more then 3 backups.

[aurel57]

I am having problems logging on to my S3. I was logged in last night and this morning it asked me to reenter my password to log in. When I did this is what I see:

/usr/lib/lua/luci/dispatcher.lua:448: Failed to execute function dispatcher target for entry '/'.
The called action terminated with an exception:
/usr/lib/lua/luci/sauth.lua:87: Session data invalid!
stack traceback:
   [C]: in function 'assert'
   /usr/lib/lua/luci/dispatcher.lua:448: in function 'dispatch'
   /usr/lib/lua/luci/dispatcher.lua:195: in function </usr/lib/lua/luci/dispatcher.lua:194>

It is still hashing on my pool ( @ 410-420 GH/s on 218.75 freq) and I have tried to log in a few more times with always the same results. Not sure if it's safe to power down or to use the reset button? Any help would be appreciated.

I'm positive this is where you want to post this question

https://bitcointalk.org/index.php?topic=671189.3740

The LuCi and openwrt are not by con or the cgminer crew. It is possible one of the nice folks on here will know the answer though. Bitmain and openwrt would have actually done the programming for that part.

EDIT: I can't wait for a binary that uses a new version of cgminer. I really should look into if its possible to add a config file and have everything work as I like more then 3 backups.

Thank you. I have posted it there as well. Also PM Bitmain and he has now gotten back with me and said he has forward my problem to a engineer and I will hear something back.

[zhaodong1982]

New version: 4.5.0, 29th July 2014

Mainly new and updated drivers.


Human readable changelog:

- Driver for new device Hashratio, uses direct USB as per all other devices to work generically on any PC platform.
- Completely rewritten driver for avalon2/3 to use direct USB for generic PC usage, with automatic default voltage and frequency settings if not specified, on screen information, and much smarter fan control.
- Merged KnC updates for Neptune support.
- Changed the cointerra driver to not fail on old firmware with checksum errors, allowing people with these devices to easily generically plug them into their PCs.
- Put lots more documentation into READMEs.
- Fixed the windows packages to have windows style end of lines again and be readable in notepad.


Full changelog:

- Fix windows build for hashratio and ava2
- Demote bad checksum message in cointerra driver but allow message to still be
parsed since it won't allow existing firmwares to work otherwise
- Reorder and document the configure options
- Merge https://github.com/KnCMiner/cgminer into knc
- Change default voltage on ava2 to 0.666V because Satan
- Enable combined building of avalon2 and hashratio
- Fix stratum embedded fpgas to not duplicate work with other devices
- Implement smarter PID type fan control for ava2 allowing more generous
temperatures and far lower fan speeds for optimal power and noise usage. Adjust
default frequency to 450 as per recommendation.
- Fix various warnings in ava2
- Go back to polling design since async will not work for ava2 and fix various
read design errors
- Fix error in 2nd read functions for av2 and hro
- Correct init and read sequence for ava2, and convert from a polling mechanism
to a separate read thread
- Initial commit of ava2 conversion to direct USB
- Display frequency and voltage with ava2 on the statline
- Store fan percentage and display temp and fan percent for ava2
- Set avalon2 frequency and voltage to appropriate defaults if none are
specified on the command line
- Demote some ava2 messages that don't need to be errors and remove unused works
array
- Fix broken fan logic for ava2
- Fix hexdump on 64bit
- rockminer frequency is between 200 and 400 MHz
- fix jansson include path in cgminer-api compile instructions
- Remove requirement for ifndefs for avalon2 from the generic driver work
function
- Fix hashratio device name
- Make submit_nonce2_nonce return whether the share was valid or not
- Reinstate missing necessary init sequence for hashratio
- Handle disconnected hashratio devices
- Add hashratio frequency command line
- Fix stratum updates not being passed to hashratio devices and clean up
- Move to updated avalon2 type driver model for hashratio device
- Initial import and conversion of hashratio driver to direct USB
- Increase the internal buffer for API response,   as "stats" command response
can grow greater than 8K
- Detach test pool thread only if we have a blocking startup

Thanks for your hardwork! ckolivas!

[allcoinminer]

"--load-balance Change multipool strategy from failover to quota based balance"
What this means exactly? Will this only just load balance equally to the set pools?
Can we set custom % wise quota for each pool? I found this option in Antminer S3.
Example: 10% to Pool 1, 50% to Pool2 and 40% to Pool 3?
It will be great if this is answered in context with the Antminer S3 too.

[Newar]

"--load-balance Change multipool strategy from failover to quota based balance"
What this means exactly? Will this only just load balance equally to the set pools?
Can we set custom % wise quota for each pool? I found this option in Antminer S3.
Example: 10% to Pool 1, 50% to Pool2 and 40% to Pool 3?
It will be great if this is answered in context with the Antminer S3 too.

from the readme:
https://github.com/ckolivas/cgminer/blob/master/README

LOAD BALANCE:
This strategy sends work to all the pools on a quota basis. By default, all
pools are allocated equal quotas unless specified with --quota. This
apportioning of work is based on work handed out, not shares returned so is
independent of difficulty targets or rejected shares. While a pool is disabled
or dead, its quota is dropped until it is re-enabled. Quotas are forward
looking, so if the quota is changed on the fly, it only affects future work.
If all pools are set to zero quota or all pools with quota are dead, it will
fall back to a failover mode. See quota below for more information.

The failover-only flag has special meaning in combination with load-balance
mode and it will distribute quota back to priority pool 0 from any pools that
are unable to provide work for any reason so as to maintain quota ratios
between the rest of the pools.

Easiest I think is to change it from within cgminer. Hit "P" and it should be self explanatory from there. Once done and back in the main screen hit "S" and write a config file. From then on change your command line to load that config file at start up ( --config or -c ).

[allcoinminer]

"--load-balance Change multipool strategy from failover to quota based balance"
What this means exactly? Will this only just load balance equally to the set pools?
Can we set custom % wise quota for each pool? I found this option in Antminer S3.
Example: 10% to Pool 1, 50% to Pool2 and 40% to Pool 3?
It will be great if this is answered in context with the Antminer S3 too.

from the readme:
https://github.com/ckolivas/cgminer/blob/master/README

LOAD BALANCE:
This strategy sends work to all the pools on a quota basis. By default, all
pools are allocated equal quotas unless specified with --quota. This
apportioning of work is based on work handed out, not shares returned so is
independent of difficulty targets or rejected shares. While a pool is disabled
or dead, its quota is dropped until it is re-enabled. Quotas are forward
looking, so if the quota is changed on the fly, it only affects future work.
If all pools are set to zero quota or all pools with quota are dead, it will
fall back to a failover mode. See quota below for more information.

The failover-only flag has special meaning in combination with load-balance
mode and it will distribute quota back to priority pool 0 from any pools that
are unable to provide work for any reason so as to maintain quota ratios
between the rest of the pools.

Easiest I think is to change it from within cgminer. Hit "P" and it should be self explanatory from there. Once done and back in the main screen hit "S" and write a config file. From then on change your command line to load that config file at start up ( --config or -c ).

Thanks for digging it for me.

[Newar]

I have been absent from the thread for a while (what can I say, cgminer just runs ).

However a few days ago I built again from github on Ubuntu 14.04 and I noticed that the output on the screen is now different. It looks very much like the output in the blue window below. The whole top section is gone and it does not react to any input like p, d, s, or q. What do I need to do to get the "old" way of displaying back?

This pic somewhat illustrates it (I know the second window in the screenshot is Phoenix, but what I see from the freshly built cgminer is very similar).

[...]

[rav3n_pl]

You DO realize, that since 3.7.2 cgminer is NOT supporting GPU anymore?

[Newar]

You DO realize, that since 3.7.2 cgminer is NOT supporting GPU anymore?

If this is directed at me, yes, I do.

My question has nothing to do with GPUs. It's about how the window is layed out.

[-ck]

However a few days ago I built again from github on Ubuntu 14.04 and I noticed that the output on the screen is now different. It looks very much like the output in the blue window below. The whole top section is gone and it does not react to any input like p, d, s, or q. What do I need to do to get the "old" way of displaying back?

You built without libncurses dev installed.

[00pmac00]

Hi. this thread is huge and my searches are getting me nowhere, and i am newb at this but trying, my failing has forced me to join the forum to ask.

Why is it that cgminer will only see one of my r-box units out of the 2, they are both plugged into different usb ports. but i could only ever get one to work when i could get it to work.

i appreciate your time. thanks in advance