Bitcoin Forum
December 04, 2016, 12:05:35 AM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 [421] 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 ... 830 »
  Print  
Author Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.9.2  (Read 4815702 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
Math Man
Full Member
***
Offline Offline

Activity: 150


View Profile
December 09, 2012, 06:43:24 AM
 #8401

I just did a git pull to update cgminer on my rigs, and I noticed that it says I'm running version 2.10.0.  Did I time warp to the future?
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1480809935
Hero Member
*
Offline Offline

Posts: 1480809935

View Profile Personal Message (Offline)

Ignore
1480809935
Reply with quote  #2

1480809935
Report to moderator
-ck
Moderator
Legendary
*
Offline Offline

Activity: 1988


Ruu \o/


View Profile WWW
December 09, 2012, 06:45:43 AM
 #8402

I just did a git pull to update cgminer on my rigs, and I noticed that it says I'm running version 2.10.0.  Did I time warp to the future?
Nope. It's not tagged as such, but it's there to demonstrate the substantially different code base if anyone's running it. That will be the version when it is finally released. Release versions are tagged in git (except when I forget to do it).

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
Math Man
Full Member
***
Offline Offline

Activity: 150


View Profile
December 09, 2012, 06:49:19 AM
 #8403

I just did a git pull to update cgminer on my rigs, and I noticed that it says I'm running version 2.10.0.  Did I time warp to the future?
Nope. It's not tagged as such, but it's there to demonstrate the substantially different code base if anyone's running it. That will be the version when it is finally released. Release versions are tagged in git (except when I forget to do it).

Dang.  I was hoping I just figured out how to time travel.
-ck
Moderator
Legendary
*
Offline Offline

Activity: 1988


Ruu \o/


View Profile WWW
December 09, 2012, 06:51:02 AM
 #8404

I just did a git pull to update cgminer on my rigs, and I noticed that it says I'm running version 2.10.0.  Did I time warp to the future?
Nope. It's not tagged as such, but it's there to demonstrate the substantially different code base if anyone's running it. That will be the version when it is finally released. Release versions are tagged in git (except when I forget to do it).

Dang.  I was hoping I just figured out how to time travel.
Shit if you did that, you'd go back and mine with your current hardware 2 years ago.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
crazyates
Legendary
*
Offline Offline

Activity: 938



View Profile
December 09, 2012, 09:32:21 AM
 #8405

I just did a git pull to update cgminer on my rigs, and I noticed that it says I'm running version 2.10.0.  Did I time warp to the future?
Nope. It's not tagged as such, but it's there to demonstrate the substantially different code base if anyone's running it. That will be the version when it is finally released. Release versions are tagged in git (except when I forget to do it).
Dang.  I was hoping I just figured out how to time travel.
Shit if you did that, you'd go back and mine with your current hardware 2 years ago.
Do we finally have an answer for February/March of 2011?!
http://bitcoin.atspace.com/mysteryminer.html

Tips? 1crazy8pMqgwJ7tX7ZPZmyPwFbc6xZKM9
Previous Trade History - Sale Thread
chewie
Member
**
Offline Offline

Activity: 75


View Profile
December 09, 2012, 11:53:33 PM
 #8406

Any idea why 2.9.7 seems to crash every 10 hours, while 2.9.6 ran just fine untouched for days?  I'm on my normally w7, 4x7970 set up.
Inaba
Legendary
*
Offline Offline

Activity: 1260



View Profile WWW
December 10, 2012, 01:11:20 AM
 #8407

The only crashes I have seen with 2.9.7 is when a backup stratum pool goes down, back up and then down again.  If the backup pool stays down or stays up, it doesn't seem to crash.

If you're searching these lines for a point, you've probably missed it.  There was never anything there in the first place.
-ck
Moderator
Legendary
*
Offline Offline

Activity: 1988


Ruu \o/


View Profile WWW
December 10, 2012, 03:01:13 AM
 #8408

<Farnsworth>Good news everyone</>

Okay after a day of debugging on windows, I found the disconnect crash bug was actually in libcurl itself, which was rather awkward but anyway it means it should get better if you download and use the following dll instead:

http://ck.kolivas.org/apps/cgminer/temp/libcurl-4.dll

Just put it into your cgminer directory, replacing the existing libcurl dll.

EDIT: I've repackaged the 2.9.7 release for win32 as 2.9.7-1 including the fixed dll. I urge anyone on windows to update at least the dll. The package is otherwise the same version of cgminer.

EDIT2: Bug submitted to curl maintainers so hopefully it will be fixed next version: https://sourceforge.net/tracker/?func=detail&aid=3594381&group_id=976&atid=100976

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
December 10, 2012, 11:18:36 AM
 #8409

<Farnsworth>Good news everyone</>

Okay after a day of debugging on windows, I found the disconnect crash bug was actually in libcurl itself, which was rather awkward but anyway it means it should get better if you download and use the following dll instead:

http://ck.kolivas.org/apps/cgminer/temp/libcurl-4.dll

Just put it into your cgminer directory, replacing the existing libcurl dll.

EDIT: I've repackaged the 2.9.7 release for win32 as 2.9.7-1 including the fixed dll. I urge anyone on windows to update at least the dll. The package is otherwise the same version of cgminer.

EDIT2: Bug submitted to curl maintainers so hopefully it will be fixed next version: https://sourceforge.net/tracker/?func=detail&aid=3594381&group_id=976&atid=100976

Hurrayy!!!

Updated...

Thanks.

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
-ck
Moderator
Legendary
*
Offline Offline

Activity: 1988


Ruu \o/


View Profile WWW
December 10, 2012, 11:37:50 AM
 #8410

New release: Version 2.10.0, 10th December 2012

Huge upgrade of lots of code and features, so comes with the usual warnings about potential instability of the new version.


Human readable changelog:

The main change to this is a completely new work scheduler where all work spawns from. The old work scheduler would spawn threads that all tried to grab work as best as they could, and this would lead to much more work than necessary being grabbed from getwork pools, and potentially hitting the pool at precisely the same time from multiple threads making a getwork failure more likely. It was also very difficult to track how much work was really available at any one time since all the threads were off doing their own thing. Centralising the work creation means it is strictly tracked now and as soon as one work item is taken, the scheduler will generate or download another one. The advantage here is to maximise the amount of work we can get from any source, be it getwork without rolltime, with rolltime, gbt, or stratum,  or combinations of the above. It is also much less likely to have dips in providing work, should lead to less getwork failures, and scale to higher hashrates even with the old getwork protocols.

When the primary pool is stratum, GBT (or getwork in failover mode), no backup connections will be maintained to backup pools. The total number of connections when mining stratum now should be extremely small.

New MMQ driver courtesy of Kano, shows each device separately now.

New ztex drivers courtesy of Denis and Peter

Threads should now have unique names on flavours of unix (sorry windows users).

More *BSD support.

Lots of work under the hood and other minor goodies. Check full changelog.


Full changelog:

- Include prctl header for thread renaming to work.
- Set tv_idle time if a pool is not active when input from the menu.
- usb display message when device is in use/another cgminer
- libztex: avoid the use of libusb_error_name()
- minor unlikely zero pointer test
- BeaverCreek doesn't like BFI INT patching.
- Only stratum pools that are idle need to be kicked via cnx_needed.
- mmq - abbreviate the temperature numbers
- Do not do any setup if opt_api_listen is disabled in api.c.
- usbutils.c uninitialised usbstat for non-primary mmqs
- Only set the lagging flag for select_pool() on failed getwork if we're not in
opt_fail_only mode.
- libztex: in case the selectFpga() failed set the selected fpga to unknown
- Modified windows-build.txt to update git instructions.
- libztex: use a function for the twice called firmware reset code
- libztex: removed an unused struct member (ztex->valid)
- driver-ztex: support for broken fpga on a multifpga board
- Set the pool lagging flag on startup to avoid it being shown initially, and
only unset it once the maximum number of staged work items has been reached.
- Avoid recursive locking of the stgd lock. (bug found by Luke-jr).
- Return value of keep_sockalive is no longer used.
- Remove dependency on mstcpip.h for windows build by making curl version >=
7.25.0 mandatory on windows builds, and use curl functions for keepalive
whenever possible instead.
- Make main() the getwork scheduler once everything is set up, so that all app
exits use the kill_work and quit paths.
- ztex: more style and whitespace fixes
- libztex: silenced another warning
- Set successful connect to true on auth stratum to allow summary on exit from
single stratum pool.
- Only consider work stale for stratum of different job_id if it's not a share.
- Increment version preempting changed version signifying different codebase to
2.9
- Hash_pop should signal further waiters on its own pthread conditional in case
there are multiple waiters.
- Check the job_id has not changed on stratum work when deciding if the work is
stale as might occur across disconnections.
- Perform pool_resus on getwork pool that generates work in getwork_thread.
- Set pool lagging message for getwork pool that falls to zero staged in getwork
thread.
- Stage extra work when the primary pool is a getwork pool without rolltime.
- Do not try to clean up twice if kill message is given.
- Only recalculate total_staged in getwork thread if required.
- Include the correct config header in libztex and include it before other
includes.
- Implement a completely new getwork scheduler. Stage all work from the one
thread, making it possible to serialise all requests minimising the number of
getworks requested or local work generated. Use a pthread conditional to wake up
the thread whenever work is removed to generate enough work to stay above the
watermark set by opt_queue. Remove all remnants of the old queueing mechanism,
deleting the now defunct queued count.
- libztex: fixed some warnings and removed some whitespaces
- libztex: silenced some warnings
- Remove all references to the now unused workio_cmd structure.
- Remove the old workio command queue thread, replacing it with a kill
conditional to exit the program.
- Remove getwork command from workio_cmd queues and do them directly from
queue_request.
- Begin tearing down the old workio command queues by removing submit commands
from there and submit them asynchronously via their own threads.
- Update windows build instructions.
- Set pool probed to true on successful authorisation with stratum to avoid it
being pinged later with pool_getswork.
- driver-ztex: libztex_setFreq() must be called before ztex_releaseFpga()
- driver-ztex: changed two pairs of malloc()/memset() to calloc()
- libztex: Read bitstream file in 2kb blocks with simpler and faster code
- Added the binary versions of ztex_ufm1_15d4.ihx and ztex_ufm1_15y1.ihx
- Trivial space removal.
- libztex: Add firmware download support for ZTEX 1.15d and 1.15x
- libztex: Factor out local version of libusb_get_string_descriptor_ascii()
- Shut up some boring old cpu warnings.
- Style changes.
- Allow pool active to be called on stratum or disabled pools in the watchpool
thread if the pool has not been probed.
- libztex: Make log messages say bitstream when refering to bitstreams
- libztex: Don't return error when a bitstream was already configured
- libztex: Read bitstream file in 64kb blocks with simpler and faster code
- libztex: Verify that the mining firmware is not a dummy firmware
- libztex: Match mining firmware ZTEX descriptor against the dummy firmware
- Combine shared padding into one char.
- libztex: Start download sequence only after reading in the new firmware
- libztex: Download mining firmware to all devices with dummy firmware
- lock (most of) the threaded statistics updates
- README stats don't add up
- usbutils.c remove compiler warning
- Make need connection return true if a pool is idle.
- API add Best Share to summary
- Check on creating new GBT work if the structures are up to date and update
them as required rather than regularly.
- Update windows build instructions.
- Enable backup stratum connections for getwork when the primary pool doesn't
have longpoll aka solo mining.
- Check for correct absence of opt_fail_only in cnx_needed.
- Remove unused variable.
- The specification for stratum has been elaborated to say that a changed diff
applies only to new work so do not retarget when submitting shares.
- Use a variable length string array in submit_upstream_work to cope with
massive GBT submissions.
- API lock access to some summary statistics (and copy them)
- Suspend stratum connections to backup pools when there is no requirement to
potentially grab work from them.
- Fix missing export for RenameThread.
- enumerate the mining threadnames
- MMQ avoid possible number overrun crashes
- mmq usb v0.4 + api usb stats
- setting the name of the threads for linux,freebsd,openbsd and osx code is
borrowed from bitcoins util.c, so it is already tested
- Don't show broken WU value with scrypt mining.
- Style police.
- Remove unused getwork times in getswork.
- Fix readme wordwrap.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
Joshwaa
Hero Member
*****
Offline Offline

Activity: 489



View Profile
December 10, 2012, 12:38:19 PM
 #8411

On the new version 2.10.0  My BFL boxes all are showing the same MHash rates, but all my 7970's have gone from 680Mhash to 603MHash.  Any thoughts?

Like what I said : 1JosHWaA2GywdZo9pmGLNJ5XSt8j7nzNiF
Don't like what I said : 1FuckU1u89U9nBKQu4rCHz16uF4RhpSTV
Don't Like BFL's Project Management : 1FuckbFLZpmWLuyHyFJw1RGkWm3yRM1L5D
kano
Legendary
*
Offline Offline

Activity: 1918


Linux since 1997 RedHat 4


View Profile
December 10, 2012, 12:58:57 PM
 #8412

cut/paste ...

2.10.0
An Xubuntu 11.04 x86_64 executable is in my github downloads called cgminer-2.10.0a
https://github.com/kanoi/cgminer/downloads
(it also works on Fedora 16 and 17)

For anyone who didn't realise, it's just the executable file to put in place of 'cgminer'
Nothing else needs changing
First get and extract the full binary release from ckolivas and then copy my file in place of 'cgminer'

No problems so far on my GPU or 'BFL+2xICA'

Since I'm no longer GPU mining, I just run it for a while on my single 6950 to see what happens

BFL+ICAs (1.6GH/s) on OzCoin Stratum with fixed 8 diff

(MMQ is ... still ... doing new code testing)

The same configure options as cvolivas' binary version
In case anyone was wondering:
CFLAGS="-O2 -W -Wall" ./autogen.sh --enable-icarus --enable-bitforce --enable-ztex --enable-modminer --enable-scrypt
make clean
make

Pool: https://kano.is BTC: 1KanoiBupPiZfkwqB7rfLXAzPnoTshAVmb
CKPool and CGMiner developer, IRC FreeNode #ckpool and #cgminer kanoi
Help keep Bitcoin secure by mining on pools with Stratum, the best protocol to mine Bitcoins with ASIC hardware
rav3n_pl
Legendary
*
Offline Offline

Activity: 1320


Don`t panic! Organize!


View Profile
December 10, 2012, 01:37:31 PM
 #8413

2.10.0 exe file for GPU only (scrypt enabled) on my skydrive if any1 intrested Smiley

1Rav3nkMayCijuhzcYemMiPYsvcaiwHni  Bitcoin stuff on my OneDrive
My RPC CoinControl for any coin https://bitcointalk.org/index.php?topic=929954
My SatoshDice bot https://bitcointalk.org/index.php?topic=897685
BitcoinOxygen
Sr. Member
****
Offline Offline

Activity: 336



View Profile WWW
December 10, 2012, 02:09:39 PM
 #8414

Is there a compiled version of CGminer for windows with icarus, bitforce, ztex, and modminer support.

BTCOxygen PPS Mining Pool 2% Fee  <<<  Join Now
kano
Legendary
*
Offline Offline

Activity: 1918


Linux since 1997 RedHat 4


View Profile
December 10, 2012, 10:35:16 PM
 #8415

Is there a compiled version of CGminer for windows with icarus, bitforce, ztex, and modminer support.
Yeah the files at the download link called cgminer*win32.7z or cgminer*win32.zip

Pool: https://kano.is BTC: 1KanoiBupPiZfkwqB7rfLXAzPnoTshAVmb
CKPool and CGMiner developer, IRC FreeNode #ckpool and #cgminer kanoi
Help keep Bitcoin secure by mining on pools with Stratum, the best protocol to mine Bitcoins with ASIC hardware
-ck
Moderator
Legendary
*
Offline Offline

Activity: 1988


Ruu \o/


View Profile WWW
December 10, 2012, 10:38:58 PM
 #8416

On the new version 2.10.0  My BFL boxes all are showing the same MHash rates, but all my 7970's have gone from 680Mhash to 603MHash.  Any thoughts?
My 7970s are performing exactly the same with 2.10 as with 2.9. Coincidence related to some other problem for you perhaps?

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
Aion2n
Hero Member
*****
Offline Offline

Activity: 483


MSI R7970 Lightning


View Profile
December 10, 2012, 11:00:00 PM
 #8417

My 7970 lightning with 2.10 have the same (690 Mh/s) rates as 2.9.7  Smiley

Благодарности принимаю на: WMX X607679930678 | BTC:1GKKSCAVRKADpsktcz1txyNaYCvX8hr9sv | LTC: LQk3uX51bwU4g1NVtRSdLQvUQko6RrKZkr | FTC: 6jfXP4Vo6YcdnDat3AEJRjgiGsx9W2pF48 | NMC: NCaLhdDMCgYAztVELBaUoU7hguUAssZjur
NVC: 4RtbCF49F69XmEPLJEmD4vZrf8idExddym | TCR: 122BmXhKE5XFNuBXoVJC3jMBM1cbrwE9S1 | PPC: PNHcmpSycTfFbTxQfwPCbofZxy6BrqXHVS | MNC: MUBxk3xyrqTD2ZGENQ2F3nh5oCQ4qzQSDk
vapourminer
Legendary
*
Online Online

Activity: 890

what is this "brake pedal" you speak of?


View Profile
December 11, 2012, 12:08:33 AM
 #8418

question on how cgminer figures intensity.

on dynamic with both 2.9.7.0/1 and 2.10.0 when I fire up folding@home on the cpu (which loads the 4 cores to 100%) cgminer drops intensity down to -8 or so on my 6870. stop folding and intensity goes to 4 or 5 where it should be.

dunno if previous versions of cgminer do this as I just upgraded to an i5 3570k; I didnt fold on the other CPU.

AFAIK folding does not touch the GPU in any way when not displaying folding graphics (which i never do) and it runs @ idle priority.

does cgminer figure CPU load into dynamic intensity?

win7 64 bit
cgminer 2.10.0
11.11 driver
12.4 SDK
HD6870

anyhow, setting "I" manually is fine. and I LOVE the stratum support! dunno how you do it but cgminer just keeps getting better!
-ck
Moderator
Legendary
*
Offline Offline

Activity: 1988


Ruu \o/


View Profile WWW
December 11, 2012, 12:18:27 AM
 #8419

question on how cgminer figures intensity.

on dynamic with both 2.9.7.0/1 and 2.10.0 when I fire up folding@home on the cpu (which loads the 4 cores to 100%) cgminer drops intensity down to -8 or so on my 6870. stop folding and intensity goes to 4 or 5 where it should be.
cgminer times how long it takes for the gpu code to "return" after it's been given work. Unfortunately with windows, the timer resolution is so shithouse at 15ms that I have to sample many many iterations of the GPU code and then average them to see how long it took. This means that between giving the GPU code, there are short periods dependent on CPU code, and windows' scheduler does not seem to give this CPU code priority even though folding@home should be idle priority. So it ends up counting delays of the CPU scheduling as though the GPU had spent more time on its work. So it's a combination of the shit windows timer resolution and the shit windows scheduling that makes dynamic not work that well for your test case.
I LOVE the stratum support! dunno how you do it but cgminer just keeps getting better!
Thanks  Cheesy

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
Joshwaa
Hero Member
*****
Offline Offline

Activity: 489



View Profile
December 11, 2012, 12:36:35 AM
 #8420

On the new version 2.10.0  My BFL boxes all are showing the same MHash rates, but all my 7970's have gone from 680Mhash to 603MHash.  Any thoughts?
My 7970s are performing exactly the same with 2.10 as with 2.9. Coincidence related to some other problem for you perhaps?

I figured it out. Drivers! They crashed when i first started CGMiner for some reason, so I had to reset all the clocks.  Thanks for the replies.

Like what I said : 1JosHWaA2GywdZo9pmGLNJ5XSt8j7nzNiF
Don't like what I said : 1FuckU1u89U9nBKQu4rCHz16uF4RhpSTV
Don't Like BFL's Project Management : 1FuckbFLZpmWLuyHyFJw1RGkWm3yRM1L5D
Pages: « 1 ... 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 [421] 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 ... 830 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!