Where's the Meerkat?
Please support FabulousPanda by checking out our latest creation:
Long term stability updates, clean ups and driver updates.
full changelog for cgminer 4.9.2 here
- If a pool supports full stratum resume (currently only ckpool pools do), which means an interrupted stratum connection can resume and submit any shares worked on in the interim without losing work, a message will now be displayed when the reconnect negotiated a resume.
If a dead pool was removed previously there was still a thread in the background trying to connect to it. This has been fixed.
Avalon 4 updates to use less power.
Fix an intermittent crash with the BFL SC 28nm devices.
Fix support for BFL SC 65nm devices failing on last release.
Fix the BET driver not being able to restart a new instance when the first fails.
Basic FreeBSD compilation support.
Other minor build changes and fixes for potential issues.
Fix for a huge long-standing memory leak with the BXF driver which affected bi*fury, hex*fury and OneString miners.
Formatting fixes for miner.php
Work should be freed when aged, fixing a massive memory leak for bxf devices
miner.php fix single rig summary/config field formatting
miner.php fix single rig total formatting
- Cointerra driver
- Bitmine A1 driver
- Avalon2U driver
- TUI now has a wider status window
The original curses display was never designed with many devices with vast amount of information displayable, and that is still the case now, but the ASIC era has made it that we do need more than previously, but I am trying to keep the display as concise as possible with the most meaningful information.
- USB menu has changed
- ANU devices aka AntminerU1 usb sticks will now take any arbitrary frequency with --anu-freq and cgminer will try to find the nearest frequency it can set it to, instead of being restricted to 25MHz increments.
- Hashfast device failures will be detected sooner
- Hashfast fan speeds by default will go down to 5%
- The menu now shows hashfast clock speed as detected by the device (which may be different to the requested speed) and fanspeed%
- Hashfast board temperature is now taken into consideration when looking for the hottest component and displaying temperature and adjusting fanspeed
- Hashfast clock speeds per die in the API should more accurately represent what speed they really are.
- Hashfast restarts should be a little more reliable
- Klondike, avalon, bab, drillbit will display more info on screen
- Pools that silently drop stratum shares submitted will not induce a memory leak in cgminer
- If no connection is present at startup, cgminer will be able to connect to a dead pool later when it comes alive
- ./autogen.sh from git will not error if given no arguments but will instead not try to configure the build
- A warning will come up if someone selects system libusb, advising against it (given how few versions of libusb actually work well).
- Fix a couple of potential hangs
- Temperature for devices that support it will now show up in the api devs command
- Icarus and bitfury devices that stop producing shares will now be sent a reset after a minute of no activity, and if they do not respond within another minute will be dropped, allowing cgminer to attempt to re-hotplug them. This has been proven effective at bringing back U1 miners that stop hashing.
- Fix unresponsive bitfury devices from ending up OFF that would not disappear and/or restart
- Bab driver updates disabling cores that stop working and reduce the cpu usage substantially
- miner.php updates
- Allow benchmarking from a --benchfile
- Other minor bugfixes and trivial cosmetic differences
New releases: 3.12.3 - 8th February 2014
Palindromic double hotfix release... Embarrassed ckolivas...
- Fix for the sitting idle doing nothing bug.
- Add temperature to API devs call for hashfast devices
- Brought back USB reset attempts on communication errors.
- Fixed the need for adding icarus-timing when overclocking antminer U1devices.
- Antminer U1 support
- Numerous fixes for behaviour surrounding USB errors - pipe and IO errors, and no more attempting to reset the device since it's rarely helpful and occasionally harmful.
- Libusb and libusbx have finally reconciled their differences and merged all their fixes together into a new official libusb release, so the main change in this version is updating the core code to include this latest libusb. Hopefully this might increase compatibility with some USB3 hubs on windows and make it more reliable (based on the changelogs I can see in libusb). This is the reason for the minor version number update to 12 as it's quite a substantial code change, hopefully only for the better!
- Increased the hashfast overheat limit default to 90 after extensive discussions with the engineers who designed the devices.
- Fixed a crash in the nanofury USB stick code.
- Fixed the displayed diff shown being wrong when solo mining.
- bab driver fixes courtesy of Kano.
- 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 Tongue
-- 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.
- Minion driver courtesy of Kano. (More info about this from him hopefully).
- Nanofury driver. These are set up the same as every other USB device is on cgminer. Tested on both windows and linux (sorry no osx to test). Note the hashrate is once again based on only valid shares so may appear lower than other software using this device. No HW errors are currently counted (though they're most definitely there in abundance due to bitfury design). This is a driver based on all the other ones out there with a completely rewritten model to suit how cgminer drivers work.
- Hashfast driver fixes (no I still don't have one).
- Fixed BXF devices slowing down over time.
- Driver for drillbit ASICs.
- Fixes for various KnC hardware errors, with improvements to hashrate. Note this is not a comprehensive fix for the hardware errors specific to rEligius - you will find a substantial drop in hardware errors if you start cgminer with the quiet and text only options (-q -T). An updated binary is here: http://ck.kolivas.org/apps/cgminer/kncminer/
- Updated bi*fury driver with support for the latest firmware. This includes dynamic clocking based on temperature which tries to maintain a constant temperature set intiially to 82 degrees but adjustable with --bxf-temp-target .
- Much more API output for bxf devices.
- Less spewing of errors when bxf devices are removed/die
- Updates to hashfast driver code
- Fixes for working with proxies that use small nonce2 sizes
- BFL SC devices will now throttle 3 degrees below cutoff (82 degrees) and cut off work at the lower 85 degrees, restarting when they get below 80. If you wish to aim for a higher maximum, use the --temp-cutoff feature (90 was the old maximum). If you set it to zero it will disable this behaviour. (I'm preparing for our summer here Wink)
- BFL SC devices will be less aggressive with their fan control now, allowing temps to drift up a little more before going to maximum speed.
- Fixes for builds with --with-system-libusb enabled not working with older libusbs. (Note that using this option is not recommended unless you can't install udev anyway).
- Fixes for warnings with ./autogen.sh
- Code cleanups of unused GPU code
- Cgminer will now try to issue a USB reset on devices that have failed to hopefully get them back up and running again.
- Dramatically improved communications for USB1.1 devices on hubs that don't have multiple transaction translators or have none (like USB3 hubs). The USB1.1 devices currently affected are Asicminer Block Erupters and Red/Blue fury USB sticks.
- Fixes for leaving too many open files problem with repeatedly hotplugging devices on low resource systems (eg RPi).
- Fix a potential API crash.
- The build will be much quieter around the jansson part now.
- More hashfast driver additions (no, the real hardware still doesn't exist).
- More fixes to make usb communications more forgiving and robust which may improve reliability and speeds.
- Timeout overruns won't show unless you have verbose mode on now.
- Voltage displayed for BFL SC devices is the 2nd voltage which is allegedly more relevant.
- API stats for BFL SC devices now show a nonce and hardware error count per core.
- Json API commands should work again.
- More fixes for upcoming hashfast hardware.
- Lowmem mode has been extended to use USB sync transfers
- BXF devices should align better with other devices on the display.
- Devices will now initialise before trying to connect to pools.
This is the last version of cgminer to support CPU, GPU and Scrypt mining