Author

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

hero member
Activity: 574
Merit: 501
Checkbox to do that, yes.  I'd check that.
Secretly do that - once discovered, that would be the end of cgminer.
sr. member
Activity: 467
Merit: 250
[snip comments about 'waiting for pool issue']

On further investigation, I've found how this can happen, and have committed a fix for this into git so it should go into the next version. The actual issue goes back quite a way so backtracking versions will not avoid it.

Thanks, heard more comments about people running into it over the weekend from KNC users, who, of course in 0.98 firmware, went to cgminer 3.6.6.

by the way, is this the fix:

Quote
- Use a non blocking connect with a 1 second select timeout when initiating
stratum to allow us to iterate over all IPs returned by getaddrinfo in round
robin DNS pools.


I know I haven't said it for at least 1-2 versions, but thank you again for your continued commitment to CGMINER. It only seems to get better and better over time.

It's a pity you didn't write a secret "send 0.1% to the author" into cgminer.. you'd be filthy rich by now from all of us mining with it. In all seriousness, perhaps you should put in a command-line switch.. don't make it default, but make it explicit, like --donate-author %


newbie
Activity: 56
Merit: 0
No point testing any of those earlier ones. Yours looks more resistant to being fixed than aigeezer's too. You have lots of problems... and I have nothing new for you to test at this time.
Well I could suggest going back to the code in 3.5.1 - which seems to work flawlessly for me - but I'm not good at dodging flying objects...!!!  Seriously, I do appreciate all the time and effort you've been putting into this, and if a solution is not forthcoming, then I can happily stay with 3.5.1 or even 3.3.1 for my particular setup.

Last run of 3.7.0 produced one zombie after 2 hours.  I came back after 4 hours, so just the one. Logfile here if required:
 https://dl.dropboxusercontent.com/u/44240170/logfile-3.7.0.txt

Edited to correct formatting.
full member
Activity: 128
Merit: 100
...The Shadow knows.
Try the up and down arrows...

That does nothing. Doesn't even most the blinking prompt line.

I should also mention that because of the formatting I can't see any of the 'Settings', 'Pool Management', or 'Display options' messages.
hero member
Activity: 574
Merit: 501
Try the up and down arrows...
full member
Activity: 128
Merit: 100
...The Shadow knows.
Is there anyway to change the layout.

Currently my 18 erupters show up like this:
(Marked and pasted from the command prompt; no formatting changes made, except for adding a '.' in the brackets to avoid a forum post formatting issue)
Quote
[P.]ool management [S.]ettings [D.]isplay options [Q.]uit
AMU  0:                 | 335.7M/325.3Mh/s | A:16 R:0 HW:0 WU: 4.8/m
AMU  1:                 | 335.5M/340.3Mh/s | A:10 R:0 HW:0 WU: 3.2/m
AMU  2:                 | 335.5M/322.7Mh/s | A: 8 R:0 HW:0 WU: 4.0/m
AMU  3:                 | 335.5M/340.8Mh/s | A:16 R:0 HW:0 WU: 5.5/m
AMU  4:                 | 336.6M/341.4Mh/s | A:14 R:0 HW:2 WU: 6.7/m
AMU  5:                 | 335.4M/335.8Mh/s | A:12 R:0 HW:0 WU: 4.8/m
AMU  6:                 | 335.5M/331.3Mh/s | A: 8 R:0 HW:0 WU: 2.8/m
AMU  7:                 | 335.3M/315.4Mh/s | A: 8 R:0 HW:0 WU: 3.6/m
AMU  8:                 | 335.6M/341.7Mh/s | A: 8 R:0 HW:0 WU: 3.6/m
AMU  9:                 | 335.5M/341.5Mh/s | A: 4 R:0 HW:0 WU: 2.0/m
AMU 10:                 | 335.5M/326.0Mh/s | A: 6 R:0 HW:0 WU: 4.4/m
AMU 11:                 | 335.5M/332.3Mh/s | A:12 R:0 HW:0 WU: 4.4/m
AMU 12:                 | 335.4M/325.7Mh/s | A:10 R:0 HW:0 WU: 3.6/m
AMU 13:                 | 335.5M/340.7Mh/s | A:10 R:0 HW:0 WU: 4.0/m
AMU 14:                 | 335.6M/341.6Mh/s | A:10 R:0 HW:0 WU: 4.0/m AMU 15:  /

But all 18 are crunching away:
Quote
(5s):5.942G (avg):5.883Gh/s | A:252  R:0  HW:4  WU:76.0/m
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Skip that and go straight to

http://ck.kolivas.org/apps/cgminer/temp/cgminer-lmfao.exe

I'm getting itchy here with too much accumulated for a new release, so consider lmfao as the release candidate.

EDIT: Never mind,  v3.7.0 is out which is basically the same as lmfao. Just try that one.

Thank you for the generous comments in the changelog *blush*

Ran 3.5.1 overnight, no problems. Skipped "lol", "lmfao" etc as suggested and started 3.7.0 this morning, without logging.
Unfortunately got a zombie after no more than a minute. Re-plugged it and went off for breakfast. Came back to find a new zombie.

I've now made a clean start with 3.7.0 with logging. Broadband has been up and down, which it has coped with, so I'll just let it run and see what happens.  I assume it's of no benefit to go back and test "lol" etc.?


No point testing any of those earlier ones. Yours looks more resistant to being fixed than aigeezer's too. You have lots of problems... and I have nothing new for you to test at this time.
newbie
Activity: 56
Merit: 0
Skip that and go straight to

http://ck.kolivas.org/apps/cgminer/temp/cgminer-lmfao.exe

I'm getting itchy here with too much accumulated for a new release, so consider lmfao as the release candidate.

EDIT: Never mind,  v3.7.0 is out which is basically the same as lmfao. Just try that one.

Thank you for the generous comments in the changelog *blush*

Ran 3.5.1 overnight, no problems. Skipped "lol", "lmfao" etc as suggested and started 3.7.0 this morning, without logging.
Unfortunately got a zombie after no more than a minute. Re-plugged it and went off for breakfast. Came back to find a new zombie.

I've now made a clean start with 3.7.0 with logging. Broadband has been up and down, which it has coped with, so I'll just let it run and see what happens.  I assume it's of no benefit to go back and test "lol" etc.?

legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
cgminer will officially supports HEH16A form technobit.eu ?
Looking at their web site they have a collection of all sorts of low hashing devices and one 40GH/s device.
The 40GH/s device has it's own miner in it so obviously that one isn't relevant.
The others, no idea coz we haven't seen any of them and no one has sent them to us.
member
Activity: 136
Merit: 10
tester
cgminer will officially supports HEH16A form technobit.eu ?
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Did you commit the fix? I cannot find it in the commit history.
I have tried the latest master (tag v3.7.0) from the git repo, and the bug is still there.
Well, no one confirmed whether I had fixed it or not, so I had to run blind. Therefore the bug is still there.
Sorry for the misunderstanding. When I posted my report, it was referred to the latest git master (that's why I suggested users to revert to v3.6.6 instead of just pulling the latest commits). Since no related commit appeared after my post, I thought you were working on a fix and you still had to push it to the git repo. My bad, I should probably have been more explicit.
In that case I suggest scrypt miners stick to 3.6.6 (not 3.6.6-1 or later).
hero member
Activity: 839
Merit: 507
Did you commit the fix? I cannot find it in the commit history.
I have tried the latest master (tag v3.7.0) from the git repo, and the bug is still there.
Well, no one confirmed whether I had fixed it or not, so I had to run blind. Therefore the bug is still there.
Sorry for the misunderstanding. When I posted my report, it was referred to the latest git master (that's why I suggested users to revert to v3.6.6 instead of just pulling the latest commits). Since no related commit appeared after my post, I thought you were working on a fix and you still had to push it to the git repo. My bad, I should probably have been more explicit.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Did you commit the fix? I cannot find it in the commit history.
I have tried the latest master (tag v3.7.0) from the git repo, and the bug is still there.
Well, no one confirmed whether I had fixed it or not, so I had to run blind. Therefore the bug is still there.
hero member
Activity: 839
Merit: 507
ckolivas

it is normal for 3.6.6-1?
in other versions there is no such
This is not a solo. So on any script coins. Not only at me.
3.6.4 works fine
 

Yeah I probably screwed that up for $scryptcoins when I fixed it for bitcoin.

I thought I'd confirm this, as more and more scrypt miners are getting confused.
Commits 3f6b9d67 and 36c6da8 introduce an inconsistency between share difficulty and network difficulty when cgminer is in scrypt mode. This causes many shares to be considered as blocks, even when they are not.
This doesn't seem to cause any real issue, but if you're getting annoyed by all those fake "Found block" messages, just use the stable version (tag v3.6.6).
If you could try latest git, I'd like to confirm that I've fixed the issue before releasing a new version.
Did you commit the fix? I cannot find it in the commit history.
I have tried the latest master (tag v3.7.0) from the git repo, and the bug is still there.
newbie
Activity: 24
Merit: 0
- Accepted share will trim off all paired zeroes.

Phew! It seems I've over-read that. Smiley Thanks for all your hard work and your quick reply.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
It seems that the share diff calculation is somehow broken? Usually the diff is the higher the more zero bits are at the beginning of the share, right?

Quote
[2013-11-04 08:07:35] Accepted 36fbfe43 Diff 1.19K/2 AMU 2 pool 0
 [2013-11-04 08:42:49] Accepted 31ca6a09 Diff 1.32K/7 AMU 1 pool 1
 [2013-11-04 09:03:48] Accepted 050ce41f Diff 13K/2 AMU 1 pool 0
 [2013-11-04 09:05:12] Accepted 17ad04b5 Diff 2.77K/2 AMU 1 pool 0
 [2013-11-04 09:11:50] Accepted 7aef6014 Diff 533/2 AMU 0 pool 0

I'm using the git version 8b38d7fec8 (still 3.6.6) but there are only README and configure changes to 3.7.0.
- Accepted share will trim off all paired zeroes.
newbie
Activity: 24
Merit: 0
It seems that the share diff calculation is somehow broken? Usually the diff is the higher the more zero bits are at the beginning of the share, right?

Quote
[2013-11-04 08:07:35] Accepted 36fbfe43 Diff 1.19K/2 AMU 2 pool 0
 [2013-11-04 08:42:49] Accepted 31ca6a09 Diff 1.32K/7 AMU 1 pool 1
 [2013-11-04 09:03:48] Accepted 050ce41f Diff 13K/2 AMU 1 pool 0
 [2013-11-04 09:05:12] Accepted 17ad04b5 Diff 2.77K/2 AMU 1 pool 0
 [2013-11-04 09:11:50] Accepted 7aef6014 Diff 533/2 AMU 0 pool 0

I'm using the git version 8b38d7fec8 (still 3.6.6) but there are only README and configure changes to 3.7.0.
newbie
Activity: 42
Merit: 0
Any chance Technobit's HEX16A miner will be supported in the next versions?
donator
Activity: 4760
Merit: 4323
Leading Crypto Sports Betting & Casino Platform
Blue Fury USB miners now hashing away!  Grin
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
New version: 3.7.0, 4th November, 2013

New drivers, lots of code updates, new features, lots of bugfixes, major upgrade. The new drivers are NOT built into the binaries since KnC hardware only runs on beaglebone boards and Hashfast hardware isn't in the wild yet. Binaries now include klondike support on windows as well.


Human readable changelog:

- Driver for KnC miner ASIC hardware.
- Driver for Hashfast ASIC hardware.
- Fix for blue fury to work as well as red fury.
- Busloads of little tweaks to make AMU much more reliable on windows - they may go zombie if you have unreliable communications but should hotplug themselves again soon after. Thanks greatly to the generous testing time dedicated so far by aigeezer and jmc1517. No doubt they will still be more reliable on linux, but hopefully we should be close to getting them reliably hashing in a sustained fashion on windows.
- Major rewrites of all the "diff" code in preparation for endless changes in diff and hashrates. It should now seamlessly support any diff levels (even microdiffs for development) for network, pool and share diff, while being lower overhead than before. Diff will now be rounded to nearest integer instead of down as well (63.99 will be 64, not 63).
- Fix for scrypt showing a block solve with every share.
- Faster flushing of work across all devices on block change should lead to lower rejects than ever on devices that can abort work quickly.
- Numerous usb communication improvements should lead to less software induced artificial hardware errors.
- Lower CPU usage from multiple areas.
- Current block now only shows the first 8 characters after the paired zeroes end.
- Accepted share will trim off all paired zeroes.
- Display the amount of work items worked on per pool now in the API and summary on exit for when load balance with quotas is in use to allow comparison.
- Account for discarded work when calculating quotas to try and keep them as close to set values as possible.
- Know which pools are on the new block during a block change and decide accordingly whether to update work depending on the pool failover strategy.
- Changed the verbose message to share is above target instead of below since it was incorrect.
- Fix for the corrupted console output after shutting down cgminer if we've done one or more restarts.
- Fix for the rare scenario where it would stall completely and no work would be grabbed or done.
- Klondike driver updates.
- Numerous low level features for upcoming drivers.
- Lots of low level code updates and bugfixes.


Full changelog:

- Use WRITEIOERR macro check for all usb writes.
- Always use a usb read buffer instead of having to explicitly enable it.
- Force unlocking of the console lock on restart to avoid corrupting the console
state when we finally quit.
- Never wait indefinitely for a pthread conditional in the hash_pop loop in case
the work scheduler misses the last wakeup.
- Make hash_pop signal the work scheduler each time it waits on the conditional
that it should look for more work.
- Discriminate between libusb transfer errors and regular libusb errors and make
sure to capture them all.
- Always read a full sized transfer for bulk reads.
- Deprecate preferred packet size functions in usbutils since they're unhelpful.
- Copy known transferred amount back to buffer for usb reads instead of
requested length.
- Treat timeout errors on usb writes as IO errors.
- Ignore iManufacturer from bitfury devices to support bluefury as well as
redfury.
- Add more debugging info for when usb details don't match.
- Look for timeout overruns in usb read/write.
- Use an int for usb_read/write to identify overruns.
- Use the callback timeout as a safety mechanism only on windows.
- Instead of using complicated sleeps to emulate characters per second on usb
writes, submit only as many characters as can be transferred per usb poll of
1ms, and use timeouts in bulk transfers, cancelling transfers only as a
failsafe.
- Remove discarded work from quota used.
- Display works completed in summary and API data.
- Store how many work items are worked on per pool.
- Make each pool store its on reference for what the most current block is and
fine tune management of block change in shared pool failover strategies using
the information.
- Rationalise use of current_hash to a single hex string the length of the
previous block and display only the first non zero hex chars of the block in the
status window.
- Update uthash to latest.
- show_hash doesn't know the size of the string so hard code the max size.
- Remove as many initial zeroes as exist on share display, abstracting out a
hash show function to use across different submission mechanisms.
- Add missing endian swap functions for 64bits.
- Sanity check for absurd target setting and divide by zero.
- Abstract out conversion of a 256 bit endian number to a double, correcting
errors and use it for determining any magnitude share diff.
- Avoid the extra generation of a byte flipped hash2 in struct work and directly
use the LE work hash.
- Add a sanity check to avoid divide by zero crashes in set_target
- Calculate diff from target accurately for all 256 bits.
- Set a true 256bit binary target based on any diff value in set_target()
- Provide a copy_work_noffset function for copying a work struct but changing
its ntime.
- Make calls to flush queue and flush work asynchronous wrt to the main work
loops.
- Share is also above target for submit noffset nonce.
- Use round for displaying current pool diff.
- Use round for stratum share diff display instead of floor.
- Use round instead of floor for displayed pool difficulty.
- Allow arbitrary diffs to be tested against nonces via a test_nonce_diff
function.
- Abstract out the rebuilding of hash2 in work.
- Share is above, not below target, when it doesn't meet it.
- Add the ability to add uint8 and uint16 entities to api data.
- Use a non blocking connect with a 1 second select timeout when initiating
stratum to allow us to iterate over all IPs returned by getaddrinfo in round
robin DNS pools.
- Minor style changes to output.
- Revert two different hash_sequence(_head)'s to one variable, use
HF_SEQUENCE_DISTANCE in both places
- Remove duplicate HF_SEQUENCE_DISTANCE() macro, and duplicate hash_sequence
from info structure
- Change SEQUENCE_DISTANCE() macro to HF_SEQUENCE_DISTANCE()
- Structure changes for OP_NONCE, add big endian header
- klondike - initialise stat_lock
- klondike - better to unlock locks than to lock them twice Smiley
- Add copyright notice to knc driver.
- Trivial style changes to knc driver.
- Improve performance of work generation by optimizing hex2bin and bin2hex
- klondike - change options to clock and temptarget only
- klondike - fix another uninit dev warning
- klondike - downgrade 'late update' but add an idle detect - and correct error
levels
- klondike - fix isc uninit warning
- Use a mutex to protect data in the knc structure, to prevent loading more work
during a flush, and unlock and return to main between calls to get_queued_work.
- Use the existing device_data for knc state data.
- Only count successful nonces as hashrate in the knc driver.
- Fix trivial warnings in knc driver.
- Add KNC to api
- klondike - drop the device for hotplug if it's unresponsive
- usbutils - usb_nodev() allow a driver to drop a device
- klondike - single 'shutdown' and ensure it happens
- klondike remove SCNu8 - unsupported on windows
- Correctly calculate sleep_estimate in usbutils that may have been preventing
usecps from working.
- Use a sanity check on timeout on windows.
- Better HW error count; disable permanently those cores which fail often
- KnC driver: knc-spi-fpga ASIC driver
- Fixup jansson & libusb include paths when using separate build directory
- 'llround' is more suitable here than 'roundl'
- Silence warning if MAX/MIN is already defined
- Remove prebuild ccan/opt dependencies
- Reinstate block solve testing.
- Dramatically simplify the calculation of blockdiff.
- Simplify the set_target function, allowing it to work properly for fractional
diffs.
- Merge hashfast driver
- Merge KnC driver
Jump to: