Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 140. (Read 5805649 times)

BaB driver changes are:
Support for both V1 and V2 controller (automatically)
Automatic tuning of all the chips performance.
Redesign of nonce reply handling to remove all the problems I copied from chainminer (there were a few)
Dramatic drop in HW errors due to a few things: not corrupting the replies, ignoring raw E0 replies and of course (not new) checking the nonces more extensively
A bucket load of statistics in the API stats that will tell you what's going on with each chip
Included is a 5 minute history that is used for performance tuning (all fields that have "History" in the name)
Here's an example with a single 16 chip board:
The last 8 are the parameters you can supply with --bab-options to tune it (see ASIC-README)
I've run it fine with 1 board and with 6 boards (I have both)
I am still tuning it and it may need some adjustment to handle the large setups of 24 boards - but I've not had access to one since before the last lot of changes.

Yeah ! pretty good job , like usualy..    thanx CK

New release: Version 3.11.0, 25th January 2014

Finally a proper release for hashfast devices and a substantially updated bab driver.


Human readable changelog:

- A proper working hashfast driver tested working on a real device, including the windows version.
- Substantially updated BAB driver courtesy of Kano. Hopefully he can give us a summary of the changes there.
- Generic fixes for the reconnect bug on btcguild (unsure if other issues still exist).
- Work is discarded on a stratum reconnect message from the pool now (as btcguild uses) to avoid working on invalid work on switching URLs.
- Fixed the stuck line at the top of the log window.
- Message about block change detected no longer mentions longpoll.
- API now has a field "Last getwork" in summary which can be used to see that we are still getting work from pools. This is useful if you are trying to determine if a device is dead for device reasons or simply isn't getting work from any pools. It uses the same numbering in seconds with the "Last Valid Work" returned in the device API. If "Last getwork" is not incrementing, there is no work for any devices.
- Added a --nfu-bits command to allow you to set the clock speed on nanofury/icefury usb sticks. Note that the default was 54 so is now 50 to be in keeping with USB2 power limit standards. This means IT WILL BE SLOWER compared to 3.10.0 unless you change it with this option back to 54. The driver is otherwise unchanged so any other differences you see are pure variance.
- Threads names have been changed so they will show up with different, consistent names in your process manager of choice.
- Building will now not include libbitfury on every configuration unnecessarily.
- The crash on device removal has been fixed.
- Fixes for lean configurations that failed to build.

- Hashfast driver changes:
-- Should be more robust with respect to initialisation and dropouts
-- If the device stops returning shares, cgminer will reset the device, and if it cannot, it will drop it, which usually allows it to be re-hotplugged again.
-- If a device needs to be reset for not returning shares, and the clockspeed is still overclocked, cgminer will lower the clocks further on every reset.
-- Devices will be throttled if they reach 85 degrees. With water cooling they usually drop in temperature very rapidly. This can be configured with --hfa-temp-overheat
-- Hashrate displayed will be based on valid shares returned so should more accurately represent what the pool will see you hashing at. It will look very unstable initially. Earlier boards do have some loss so the previously displayed hashrate was always over. You can compare the total hashes estimated by this as "Calc hashcount" to compare with "Raw hashcount" the device has worked on in the API stats to see how they differ.
-- Max temp on screen will not show if it's an obvious error showing something like 512
-- The API will show board temperatures
-- Windows builds work
-- Babyjets show up as HFB while Sierras show up as HFS. Custom devices will come up with the generic HFA name. Note that if you are trying to select them with the --usb command, they are all seen as HFA due to the fact that cgminer can only tell them apart after they have been initialised and running.


Full changelog:

- Add hashfast documentation to ASIC README
- Support the variable HFA naming throughout the driver notices.
- Set the global hfa hash clock rate to equal the lowest if we are lowering it
for a device reset since it may be re-hotplugged after failing reset.
- Decrease the hfa clock rate if it is overclocked and we have had to try
resetting it.
- Put a sanity check on the measured temperature in the hfa driver for obviously
wrong values.
- Avoid calling applog from within hfa statline before to avoid a deadlock.
- Add throttling control to hfa driver, configurable at command line, nominally
set to 85 degrees.
- Reset hfa device if no valid hashes are seen for 1 minute from the last work.
- Store when the last getwork was retrieved and display it in the API summary.
- bab - also report dead chip count screen
- Count share based hashes in the hfa driver with the device diff to get more
frequent updates.
- Only count 2/3 of the accumulated hashes on each pass through the hfa scan
work loop to smooth out displayed hashrate.
- bab add total history HW% to API stats
- Test valid nonces in the hashfast driver allowing us to check against the
target when trying to submit them.
- No point casting a double to a uint64
- Convert the hfa hashmeter to one based on successful share return and display
the raw and calculated hash totals in the API.
- bab - remove libbitfury dependency since it requires USB
- Add description to hfa hash clock command.
- Add hfa board temperatures to API output.
- Wait for up to 0.5 seconds in the hashfast scanwork loop if no jobs are
required.
- Label HFA devices as B or S when their configuration matches babyjet or
sierra.
- Fix libbitfury being compiled in always by mistake.
- bab - spelling
- Add bab-options
- bab - tune the chip speed based on error rates
- bab record/report spie and miso errors
- Win32 falsely comes up as big endian pulling in the wrong hf protocol header.
- Remove unused components in hashfast driver.
- Check in all usb communication places for hashfast driver that the device
still exists.
- Do not send a usb reset on a usb read pipe error.
- Don't replace usb pipe errors with the pipe reset return code.
- Updated hf protocol header.
- The search for extra nonce is not worth performing in the hashfast driver.
- Add core address to hfa parse nonce debugging.
- Retry sending a frame once if it has failed in hfa_send_frame
- Add extra hfa usb init errors.
- Quiet now unused variable warning in hfa detect.
- Remove unused variable.
- Add board temperature to hfa debug
- Make submit_tested_work return a bool about whether it meets the work target
or not.
- Provide a helper function for determining dev runtime and use it in the
hashmeters used.
- Look for hfa usb init header for 2 seconds, then resend the init twice more
before failing.
- Really only set up the hfa crc table once.
- Generically increase the queue if we are mining on a pool without local work
generation each time we run out of work.
- Change new block detection message since longpoll is rarely relevant today.
- Change the default clockspeed bits on nanofury devices to 50 and add a command
line option to allow it to be changed.
- Use unused line at the top of the log window which often gets stuck
unchanging.
- Clear pool work on a stratum reconnect message.
- bab record/report spie and miso errors
- bab - cleanup old work for dead chips also
- bab add avg fail tests to API stats
- bab report bank/board/chip for dead and v.slow chips
- bab process all nonce replies per chip together
- bab reduce work delays
- bab record the number of E0s discarded
- bab - modified result parsing
- bab restore removed unused flag
- configure - correct minion name
- bab only scan valid nonce offsets
- bab record continuous (and max) bad nonces
- bab display Banks/Boards/Chips in the device window
- Modify thread naming to make them easier to identify
- bab reduce the work send delay
- bab remove results polling
- bab report SPI wait in seconds
- bab report missing chips at start and API
- bab ensure there's enough space for the nonce reply
- bab correct stats 'Send Max'
- bab allow long enough wait on ioctl() per board
- bab more I/O stats
- api.c 2014
- api allow any size stats data
- bab add processed links which excludes expired links skipped
- bab report chips per bank, hw% and ghs per chip
- bab lock access to new_nonces to ensure correct reporting
- bab report V2 banks/boards during initialisation
- bab expire chip work
- bab use only k_lists and make work handling more refined
- klist - allow adding to tail
- bab remove old unused #define
- bab correct for master git
- correct klist reallocs
- klist lists for bab
- api.c correct DEVICECODE and ordering
- Maxchips should be 384 (16 chips/board 24 boards/controller)
- bab more detailed stats and delay less when waiting for a buffer
- api add data type AVG float 3 decimal
- bab - add V2 detect with bug fix in detect
- api.c set the actual version number to 3.0
- API V3.0 unlimited socket reply size
- README update --usb
- Check for loss of device in usb read before any other code on the usbdev
- Change stratum strings under stratum_lock in reconnect and free old strings.
- Add mcp2210 compilation to want_libbitfury configs.
- Fix HF driver typo.

I am having trouble getting cgminer to even run with a 7990.

Thread with details: https://litecointalk.org/index.php?topic=13980.0

If we were smart we would have had updates turned off and set to manual mode to reduce accidental restarts. I'm sure Linux has its own way of updates that can tick you off. I only knew when there was updates when it was a new release or installed a new program when I messed with Linux. Windows at least tries to keep it up front. I still wish it brought current programs back up and then locked the pc with some sort of notification about it.

Btw you do realize the btc guild problem is probably both Linux and windows alike.

Anyone knows why all of a sudden the CGMiner on a Jupiter stopped displaying the usual lines: [2014-01-25 02:33:12] Accepted 227772c5 Diff 1.9K/1024 KnC 0 pool 0

It's not Quiet mode. When I press D it quickly goes to a blank screen and then it reverts back. It happened on 5 machines with 3.8.1 and 3.9.0
I try to turn Quiet mode blindly by doing D/Q a couple of times, but nothing.

Any ideas?

This reason alone made me give up windoze. Not to mention the frequent restarts because of updates .Set up a raspberry pi changed some of the instructions to compile newest version and been happily hashing since December with no down time. If you don"t like soldering then save some money and skip the lcd.

http://learn.adafruit.com/piminer-raspberry-pi-bitcoin-miner/

Cheers, 

Yeah that was my problem libpthread "isn't" installed, you need to uninstall that version and install it via shell. That was one error I googled and edited in the windows compile file. After that I'm still in the dark waiting for ckolivias to check his pm's and see what the hecks going on with the make. We don't need two people getting eaten out by minGW user email lists.

--enable-hashfast dies when checking c compiler
-enable-hashfast dies when checking for cross compiling
default CFLAGS="-O2 -msse2" ./configure dies when it thinks libpthread is not installed.  But I have all libpthread packages installed in MinGW, so this baffles me.

That's why I am asking for someone who already can successfully build a windows build to do so with --enable-hashfast, because I have spent much time and effort in attempting to do so and have not been successful

Is it giving an error when it crashes? Other than trying changing it to --enable-hashfast instead of hashfast-enable make sure your packages are right and that the version your compiling has hashfast built in. I haven't successfully gotten cgminer to compile but you can read my edited howto on my github version that I tried to use to solve a problem with winsock errors popping up on being made with "make"  here https://github.com/techman05/cgminer .

Hope that helps

Can someone please build a windows version with hashfast-enable?  I have been unable to build it following the windows build instructions, it keeps crashing when I try to ./configure.

I'm set for level 16 in load balance mode with about 25Ghashes pointed at it. If you have it right, it shows up after less than 30 minutes. I was trying to watch a flash video when I last noticed my computer getting chunky which eventually led to me trying to fast disable btcguild ,but it was too late and then to get stability back I ended up voluntarily rebooting my system (pc was looking to update my display , network drivers and .net service packs, so I needed to anyway) Picture below is not from most recent event but how I found it after leaving home for a few days not knowing this would happen.

I hope that gives you something to look into and hope it has nothing to do with pm to check winsock headers having problems with compiling.

It seems there is also a problem with stratum+tcp://stratum.triplemining.com:3334 now. It is always marked as dead. The old version is running on another machine - there the pool is alive. Restart doesn't change anything on one of the machines.

Thanks for checking. Maybe it helps checking the issue with a p2pool:

I noticed --nfy-bits - thanks :-)

libcurl-4.dll is missing from my computer, this is the error message I keep getting, when tryin to open the cgminer.exe

Been looking into it. I was unable to reproduce this at all locally so perhaps it's better or perhaps I just don't have the right combo of hashrate and circumstances. I've done some generic changes to make it more robust. There may well be a second issue with btcg related to the frequent restarts it's had lately but I have no firm leads on that.

The php function I'm using is from the MinePeon OS for the Raspberry Pi and I just used it as it worked and I managed to get all other functions to work just this 'zero' that caused the problem.
https://github.com/MineForeman/minepeon-base/blob/master/http/inc/miner.inc.php

AddPool works fine using:
cgminer("addpool",$poolAddress . "," . $poolUser . "," . $poolPass);


EDIT: GOT IT!
cgminer('zero','all,true');
Returns "[Msg] => ZeroedAllstatswithsummary" and has indeed reset the stats to '0'

I was misreading the "|" as if it was asking for "zero,all","true" but instead its the other way around "zero","all,true"

No idea what that PHP you are using is, but as the API-README says, the zero command is:

zero|Which,true/false

i.e.
zero|all,true

or JSON
{"command":"zero","parameter":"all,true"}

Edit: I will add that it looks exactly the same as:
addpool, poolpriority, poolquota, setconfig, pgaset, ascset
So I guess none of those worked for you either

Tripe equal in PHP: operands must be equal and of the same type (rtfm)

=== is the same as == but also compares the type as well value, and must be the same to return 1 otherwise it'll return 0 regardless if the value is the same.


"cgminer(zero)" returns "[Msg] => Missingzeroparameters" Obviously
"cgminer(zero,all)" returns "[Msg] => Missingparameter:true/false"

But adding the true/false parameter still returns the same Msg..
"cgminer(zero,all,false)" returns "[Msg] => Missingparameter:true/false"

I've gone through pretty much every other API command and they all seem to work but for the life of me this one just won't work