Bitcoin Forum
August 14, 2018, 09:13:58 PM *
News: Latest stable version of Bitcoin Core: 0.16.2  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 [621] 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 ... 847 »
  Print  
Author Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.10.0  (Read 5760317 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.
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2604
Merit: 1121


Ruu \o/


View Profile WWW
September 09, 2013, 11:43:00 PM
 #12401

SOLVED! (sort of, eventually)

Conclusion:

Nvidia should stick to GFX chipsets.

Xubuntu 13.04 performed poorly compared to 12.04 (I reinstalled 12.04)

I need to learn more  Grin
Thanks for investigating. Having coded parts of kernels that report CPU usage, I should point out that the CPU usage is not as clear as you may think, so while it appears that 13.04 is worse than 12.04 (37 vs 33% you said), it may be a measuring artefact difference, whereas 12% vs 33% is more likely to be significant.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org 1% Fee Solo mining at solo.ckpool.org
-ck
1534281238
Hero Member
*
Offline Offline

Posts: 1534281238

View Profile Personal Message (Offline)

Ignore
1534281238
Reply with quote  #2

1534281238
Report to moderator
1534281238
Hero Member
*
Offline Offline

Posts: 1534281238

View Profile Personal Message (Offline)

Ignore
1534281238
Reply with quote  #2

1534281238
Report to moderator
1534281238
Hero Member
*
Offline Offline

Posts: 1534281238

View Profile Personal Message (Offline)

Ignore
1534281238
Reply with quote  #2

1534281238
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1534281238
Hero Member
*
Offline Offline

Posts: 1534281238

View Profile Personal Message (Offline)

Ignore
1534281238
Reply with quote  #2

1534281238
Report to moderator
Trongersoll
Hero Member
*****
Offline Offline

Activity: 490
Merit: 500



View Profile
September 10, 2013, 12:09:04 AM
 #12402

is there a reason that you moved from ubuntu 12.04 to 13.04? it seems like every time i try and do something simple, like upgrade cgminer, i have to jump through hoops. I'm running cgminer 3.3.1. i'm having trouble adding a new Hub and more ASICminer erupters. i've got about 34 running, one in the new hub works but any more gets errors and not recognised. at one point i had 3 working in the new hub, but repowering it dropped me down to one. I figured if i asked for help you would just tell me to use the latest cgminer. so i downloaded your prebuilt one. I noticed the 13.04 but figured it was a typo. So now i have to upgrade my Ubuntu version or rebuild the package for 12.04? If i try and rebuild it am i going to run into another "gotcha". I was so happy with 3.3.1, i just downloaded it and it worked.  Sad
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2604
Merit: 1121


Ruu \o/


View Profile WWW
September 10, 2013, 12:21:55 AM
 #12403

is there a reason that you moved from ubuntu 12.04 to 13.04? it seems like every time i try and do something simple, like upgrade cgminer, i have to jump through hoops. I'm running cgminer 3.3.1. i'm having trouble adding a new Hub and more ASICminer erupters. i've got about 34 running, one in the new hub works but any more gets errors and not recognised. at one point i had 3 working in the new hub, but repowering it dropped me down to one. I figured if i asked for help you would just tell me to use the latest cgminer. so i downloaded your prebuilt one. I noticed the 13.04 but figured it was a typo. So now i have to upgrade my Ubuntu version or rebuild the package for 12.04? If i try and rebuild it am i going to run into another "gotcha". I was so happy with 3.3.1, i just downloaded it and it worked.  Sad
I've been building with 13.04 for ages. It just so happens that previous builds worked on 12.04->13.04 simply because all the libraries matched and now do not that I added the latest version of libusb. When exactly should I upgrade to a newer operating system? Well that's the nature of heavy development. If you find a version that works for you and your hardware, stick with it, but mining is a very fluid environment that is still in massive flux and development where the hardware, protocol and expectations continue to change. If you're on linux, you'll always be much better off building it for yourself, and I only reluctantly offer binaries - it is actually not hard to build it yourself. Windows is a totally different world where building the binary is hard work, so I try to make one binary work on as many different versions as possible. People newer to the linux world use their windows experience but that's not the best way to use linux.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org 1% Fee Solo mining at solo.ckpool.org
-ck
Trongersoll
Hero Member
*****
Offline Offline

Activity: 490
Merit: 500



View Profile
September 10, 2013, 12:34:29 AM
 #12404

is there a reason that you moved from ubuntu 12.04 to 13.04? it seems like every time i try and do something simple, like upgrade cgminer, i have to jump through hoops. I'm running cgminer 3.3.1. i'm having trouble adding a new Hub and more ASICminer erupters. i've got about 34 running, one in the new hub works but any more gets errors and not recognised. at one point i had 3 working in the new hub, but repowering it dropped me down to one. I figured if i asked for help you would just tell me to use the latest cgminer. so i downloaded your prebuilt one. I noticed the 13.04 but figured it was a typo. So now i have to upgrade my Ubuntu version or rebuild the package for 12.04? If i try and rebuild it am i going to run into another "gotcha". I was so happy with 3.3.1, i just downloaded it and it worked.  Sad
I've been building with 13.04 for ages. It just so happens that previous builds worked on 12.04->13.04 simply because all the libraries matched and now do not that I added the latest version of libusb. When exactly should I upgrade to a newer operating system? Well that's the nature of heavy development. If you find a version that works for you and your hardware, stick with it, but mining is a very fluid environment that is still in massive flux and development where the hardware, protocol and expectations continue to change. If you're on linux, you'll always be much better off building it for yourself, and I only reluctantly offer binaries - it is actually not hard to build it yourself. Windows is a totally different world where building the binary is hard work, so I try to make one binary work on as many different versions as possible. People newer to the linux world use their windows experience but that's not the best way to use linux.

yeah when to upgrade is always a tough call. I'm just afraid that if try and recompile it for 12.04 I'm going to run into a whole bunch of incompatibilities. I just wish this whole USB thing worked like it is supposed to. nothing is ever easy. well, sometimes it is easy, but we forget those times.
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2604
Merit: 1121


Ruu \o/


View Profile WWW
September 10, 2013, 12:44:51 AM
 #12405

yeah when to upgrade is always a tough call.
Strictly speaking, I move to the latest Ubuntu 3 months after it is released, and 2 releases are usually binary compatible, which means they get a year of binary compatibility before I move on. 13.04 came out in April and 13.10 is due out in a month (as per the .04 .10 nomenclature).

Primary developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org 1% Fee Solo mining at solo.ckpool.org
-ck
abbeytim
Sr. Member
****
Offline Offline

Activity: 435
Merit: 250


View Profile
September 10, 2013, 05:29:02 AM
 #12406

I want to mine on a gpu on the same pc in a different pool  that my asics are on but I try  --disable-Icarus it crashes is there another command??

-ck
Moderator
Legendary
*
Offline Offline

Activity: 2604
Merit: 1121


Ruu \o/


View Profile WWW
September 10, 2013, 05:35:34 AM
 #12407

I want to mine on a gpu on the same pc in a different pool  that my asics are on but I try  --disable-Icarus it crashes is there another command??


That's cause there is no such command. Try --usb :0

Primary developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org 1% Fee Solo mining at solo.ckpool.org
-ck
abbeytim
Sr. Member
****
Offline Offline

Activity: 435
Merit: 250


View Profile
September 10, 2013, 06:05:08 AM
 #12408

 Grin works ty
spacebob
Newbie
*
Offline Offline

Activity: 13
Merit: 0


View Profile
September 10, 2013, 12:23:33 PM
 #12409

So I got a kinda weird issue.

I started mining on my Raspberry Pi (O/S: Raspian) with 5 Block Eruptors on a DLink DUB-7 on August 19th using cgminer 3.3.4 and followed the included instructions on how to compile the libusb libraries myself. It worked great and it ran non-stop for a few weeks. The other day I decided to update cgminer to 3.4.2. After mining for about 20 minutes the Pi seemed to locked up. My SSH session died and I couldn't ping the Pi anymore. I figured it was just a fluke so I restarted the Pi but, again, after mining for about 20 minutes the Pi locks up.

I figured that this must have just been an issue with the newest version of cgminer so I went back to 3.3.4 with no luck. 3.3.4 now causes the Pi to lock up as well. I thought that maybe the Pi was overheating so I tried doing something else intensive; watching a 1080p movie over my LAN for 2hrs+ but it worked great and never locked up. I also tried mining just with 1 miner but the Pi still locked up.

Perhaps there is an issue with the newest packages for the Pi? How can I provide some more detailed info to see what is going on? Anything else I can try to resolve the issue?
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2604
Merit: 1121


Ruu \o/


View Profile WWW
September 10, 2013, 12:31:44 PM
 #12410

So I got a kinda weird issue.

I started mining on my Raspberry Pi (O/S: Raspian) with 5 Block Eruptors on a DLink DUB-7 on August 19th using cgminer 3.3.4 and followed the included instructions on how to compile the libusb libraries myself. It worked great and it ran non-stop for a few weeks. The other day I decided to update cgminer to 3.4.2. After mining for about 20 minutes the Pi seemed to locked up. My SSH session died and I couldn't ping the Pi anymore. I figured it was just a fluke so I restarted the Pi but, again, after mining for about 20 minutes the Pi locks up.

I figured that this must have just been an issue with the newest version of cgminer so I went back to 3.3.4 with no luck. 3.3.4 now causes the Pi to lock up as well. I thought that maybe the Pi was overheating so I tried doing something else intensive; watching a 1080p movie over my LAN for 2hrs+ but it worked great and never locked up. I also tried mining just with 1 miner but the Pi still locked up.

Perhaps there is an issue with the newest packages for the Pi? How can I provide some more detailed info to see what is going on? Anything else I can try to resolve the issue?
If going back to the previous version doesn't resolve the issue, how can the new version be responsible?

Primary developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org 1% Fee Solo mining at solo.ckpool.org
-ck
spacebob
Newbie
*
Offline Offline

Activity: 13
Merit: 0


View Profile
September 10, 2013, 12:43:49 PM
 #12411

So I got a kinda weird issue.

I started mining on my Raspberry Pi (O/S: Raspian) with 5 Block Eruptors on a DLink DUB-7 on August 19th using cgminer 3.3.4 and followed the included instructions on how to compile the libusb libraries myself. It worked great and it ran non-stop for a few weeks. The other day I decided to update cgminer to 3.4.2. After mining for about 20 minutes the Pi seemed to locked up. My SSH session died and I couldn't ping the Pi anymore. I figured it was just a fluke so I restarted the Pi but, again, after mining for about 20 minutes the Pi locks up.

I figured that this must have just been an issue with the newest version of cgminer so I went back to 3.3.4 with no luck. 3.3.4 now causes the Pi to lock up as well. I thought that maybe the Pi was overheating so I tried doing something else intensive; watching a 1080p movie over my LAN for 2hrs+ but it worked great and never locked up. I also tried mining just with 1 miner but the Pi still locked up.

Perhaps there is an issue with the newest packages for the Pi? How can I provide some more detailed info to see what is going on? Anything else I can try to resolve the issue?
If going back to the previous version doesn't resolve the issue, how can the new version be responsible?

I'm not saying the newest version is responsible for the issue. I was just describing what I've tried so far.

Quote
Perhaps there is an issue with the newest packages for the Pi
What I meant by this is maybe updating my Pi's firmware and packages are causing the issue.
PatMan
Hero Member
*****
Offline Offline

Activity: 924
Merit: 1000


Watch out for the "Neg-Rep-Dogie-Police".....


View Profile WWW
September 10, 2013, 02:53:21 PM
 #12412

SOLVED! (sort of, eventually)

Conclusion:

Nvidia should stick to GFX chipsets.

Xubuntu 13.04 performed poorly compared to 12.04 (I reinstalled 12.04)

I need to learn more  Grin
Thanks for investigating. Having coded parts of kernels that report CPU usage, I should point out that the CPU usage is not as clear as you may think, so while it appears that 13.04 is worse than 12.04 (37 vs 33% you said), it may be a measuring artefact difference, whereas 12% vs 33% is more likely to be significant.

You're welcome! And thanks for the reply. Yeah, I've been really happy with 12.04 - the thinking behind trying 13.04 was that maybe the drivers for my usb controllers had been updated and/or improved in the newer version, but if they had it didn't seem to cure the problem, the opposite in fact. I liked the new desktop look though..... Cheesy Another thing that put me off a little was that the installation no longer fitted on a CD, not that it makes much difference since as soon as I install an OS I immediately set about uninstalling everything that isn't needed for mining anyway - gimp, Thunderbird, gstreamer etc. I run the OS on a small 40GB ssd & keep all the wallet data (5 different coins ATM) on a separate, larger & faster ssd in an effort to decrease latency.
It still strikes me as a little funny that the expensive super duper nvidia chipset was outclassed & outperformed by a £8 amazon cheap n' cheerful add-on card.... Cheesy
As you say, it's a case of horses for courses, I'll be sticking with 12.04 for the time being, but if I decide on upgrading the mobo to a non-nvidia chipset type I might try 13.04 again.

"When one person is deluded it is called insanity - when many people are deluded it is called religion" - Robert M. Pirsig.  I don't want your coins, I want change.
Amazon UK BTC payment service - https://bitcointalk.org/index.php?topic=301229.0 - with FREE delivery!
http://www.ae911truth.org/ - http://rethink911.org/ - http://rememberbuilding7.org/
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2604
Merit: 1121


Ruu \o/


View Profile WWW
September 10, 2013, 09:04:03 PM
 #12413

So I got a kinda weird issue.

I started mining on my Raspberry Pi (O/S: Raspian) with 5 Block Eruptors on a DLink DUB-7 on August 19th using cgminer 3.3.4 and followed the included instructions on how to compile the libusb libraries myself. It worked great and it ran non-stop for a few weeks. The other day I decided to update cgminer to 3.4.2. After mining for about 20 minutes the Pi seemed to locked up. My SSH session died and I couldn't ping the Pi anymore. I figured it was just a fluke so I restarted the Pi but, again, after mining for about 20 minutes the Pi locks up.

I figured that this must have just been an issue with the newest version of cgminer so I went back to 3.3.4 with no luck. 3.3.4 now causes the Pi to lock up as well. I thought that maybe the Pi was overheating so I tried doing something else intensive; watching a 1080p movie over my LAN for 2hrs+ but it worked great and never locked up. I also tried mining just with 1 miner but the Pi still locked up.

Perhaps there is an issue with the newest packages for the Pi? How can I provide some more detailed info to see what is going on? Anything else I can try to resolve the issue?
If going back to the previous version doesn't resolve the issue, how can the new version be responsible?

I'm not saying the newest version is responsible for the issue. I was just describing what I've tried so far.

Quote
Perhaps there is an issue with the newest packages for the Pi
What I meant by this is maybe updating my Pi's firmware and packages are causing the issue.
No idea then sorry. Perhaps your Pi is coincidentally failing or as you say, some upgraded other package is responsible.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org 1% Fee Solo mining at solo.ckpool.org
-ck
johnyj
Legendary
*
Offline Offline

Activity: 1848
Merit: 1000


Beyond Imagination


View Profile
September 10, 2013, 09:12:01 PM
 #12414

After I installed the latest libudev-dev package, the linux froze at the beginning of start up, two leds on keyboard just flashes and no response from keyboard/mouse. I can never enter the system anymore, even with ssh

The prompt at frozen point is:

/init: line 318: can't open /root/dev/console: no such file (only part of the text were displayed, see below)



vulgartrendkill
Hero Member
*****
Offline Offline

Activity: 518
Merit: 500



View Profile WWW
September 10, 2013, 09:19:13 PM
 #12415

hey there folks,

i`m having the TIMEOUT warning on 2 of my block erupters.  I`ve had a search of this thread and I can only find reference to it in relation to Linux.  As i`m running a window 7 pc, are there any steps i can take to rectify the error?  I`ve read about the libusb file being correct in cgminer 3.4.2 and that this file may be the issue. do I have to place this file else where to work?

Thanks guys

nwoolls
Hero Member
*****
Offline Offline

Activity: 840
Merit: 1001


View Profile WWW
September 10, 2013, 11:39:44 PM
 #12416

Hi there. Any update on these items? Do you need access to an OS X box? Let me know if there's anything else I can do to help.

I am trying to compile from the Git source on OS X. I am cloning into a brand new, clean directory. From there I autogen.sh like I always have, and I get an error:

Code:
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: error: cannot find input file: `Makefile.in'

Here is more error info, which may help pinpoint the issue:

Code:
configure.ac:39: error: required file '../../ltmain.sh' not found
libusb/Makefile.am:4: warning: source file 'os/darwin_usb.c' is in a subdirectory,
libusb/Makefile.am:4: but option 'subdir-objects' is disabled
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the 'subdir-objects'
automake: automake option hasn't been enabled.  For now, the corresponding output
automake: object file(s) will be placed in the top-level directory.  However,
automake: this behaviour will change in future Automake versions: they will
automake: unconditionally cause object files to be placed in the same subdirectory
automake: of the corresponding sources.
automake: You are advised to start using 'subdir-objects' option throughout your
automake: project, to avoid future incompatibilities.
libusb/Makefile.am:3: warning: source file 'os/linux_usbfs.c' is in a subdirectory,
libusb/Makefile.am:3: but option 'subdir-objects' is disabled
libusb/Makefile.am:33: warning: source file 'os/linux_netlink.c' is in a subdirectory,
libusb/Makefile.am:33: but option 'subdir-objects' is disabled
libusb/Makefile.am:33: warning: source file 'os/linux_udev.c' is in a subdirectory,
libusb/Makefile.am:33: but option 'subdir-objects' is disabled
libusb/Makefile.am:5: warning: source file 'os/openbsd_usb.c' is in a subdirectory,
libusb/Makefile.am:5: but option 'subdir-objects' is disabled
libusb/Makefile.am:6: warning: source file 'os/poll_windows.c' is in a subdirectory,
libusb/Makefile.am:6: but option 'subdir-objects' is disabled
libusb/Makefile.am:6: warning: source file 'os/windows_usb.c' is in a subdirectory,
libusb/Makefile.am:6: but option 'subdir-objects' is disabled
libusb/Makefile.am:42: warning: source file 'os/threads_windows.c' is in a subdirectory,
libusb/Makefile.am:42: but option 'subdir-objects' is disabled
libusb/Makefile.am:42: warning: source file 'os/threads_posix.c' is in a subdirectory,
libusb/Makefile.am:42: but option 'subdir-objects' is disabled
autoreconf: automake failed with exit status: 1

Here's the error compiling from the release tarball:

Code:
  CCLD   cgminer
Undefined symbols for architecture x86_64:
  "_CFDictionaryCreateMutable", referenced from:
      _darwin_init in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFDictionarySetValue", referenced from:
      _darwin_init in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFGetTypeID", referenced from:
      _darwin_devices_detached in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFNumberCreate", referenced from:
      _darwin_init in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFNumberGetTypeID", referenced from:
      _darwin_devices_detached in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFNumberGetValue", referenced from:
      _darwin_get_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_devices_detached in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFRelease", referenced from:
      _darwin_get_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_kernel_driver_active in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_release_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_close in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_init in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_devices_detached in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      ...
  "_CFRetain", referenced from:
      _darwin_open in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFRunLoopAddSource", referenced from:
      _darwin_claim_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_open in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFRunLoopGetCurrent", referenced from:
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFRunLoopRemoveSource", referenced from:
      _darwin_release_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_close in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFRunLoopRun", referenced from:
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFRunLoopStop", referenced from:
      _darwin_exit in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFUUIDGetConstantUUIDWithBytes", referenced from:
      _darwin_claim_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _usb_get_next_device in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFUUIDGetUUIDBytes", referenced from:
      _darwin_claim_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _usb_get_next_device in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_IOCreatePlugInInterfaceForService", referenced from:
      _darwin_claim_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _usb_get_next_device in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_IOIteratorIsValid", referenced from:
      _usb_get_next_device in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_IOIteratorNext", referenced from:
      _darwin_get_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _process_new_device in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _usb_get_next_device in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_devices_detached in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_IONotificationPortCreate", referenced from:
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_IONotificationPortDestroy", referenced from:
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_IONotificationPortGetRunLoopSource", referenced from:
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_IOObjectRelease", referenced from:
      _darwin_get_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_kernel_driver_active in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_claim_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _process_new_device in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _usb_get_next_device in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_init in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      ...
  "_IORegistryEntryCreateCFProperty", referenced from:
      _darwin_get_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_kernel_driver_active in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_devices_detached in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_IOServiceAddMatchingNotification", referenced from:
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_IOServiceGetMatchingServices", referenced from:
      _darwin_init in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_IOServiceMatching", referenced from:
      _darwin_init in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "___CFConstantStringClassReference", referenced from:
      CFString in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      CFString in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      CFString in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      CFString in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_kCFAllocatorDefault", referenced from:
      _darwin_get_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_kernel_driver_active in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_init in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_devices_detached in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_kCFAllocatorSystemDefault", referenced from:
      _usb_get_next_device in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_kCFRunLoopCommonModes", referenced from:
      _darwin_open in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_kCFRunLoopDefaultMode", referenced from:
      _darwin_release_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_claim_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_close in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_kCFTypeDictionaryKeyCallBacks", referenced from:
      _darwin_init in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_kCFTypeDictionaryValueCallBacks", referenced from:
      _darwin_init in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_kIOMasterPortDefault", referenced from:
      _darwin_init in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_objc_registerThreadWithCollector", referenced from:
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
ld: symbol(s) not found for architecture x86_64
collect2: ld returned 1 exit status
make[2]: *** [cgminer] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

MultiMiner: Any Miner, Any Where, on Any Device |  Xgminer: Mine with popular miners on Mac OS X
btc: 1BmXY4ZZQh1iHSVre658gM1gPAEtDnq8rv  |  ltc: LP1SsHZTDexndkvRKsqAkXNsienPHwaMb5  |  hardware: nwoolls at gmail dot com
tk1337
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250



View Profile
September 11, 2013, 03:17:35 AM
 #12417

It appears that the API is reporting a different number of accepted shares than what is being shown on the output. Not sure if this is intentional for some reason or if this is an already known issue (sorry, not going through 600+ pages). Small example: CGMiner Output screen says 8105 accepted shares, the API returns 6786 for said device (1319 difference, seems to be across the board for each device).

Please let me know if you would like me to supply the data from the API vs. data on the output.

If I helped you & you feel generous, donate some BTC to -> 1337tkvMSeY2fNgyNXVshAZixnGxLxuSmy
Do you like cheap GH/s? | MobileMinerApp Plugin for MinePeon
kano
Legendary
*
Offline Offline

Activity: 2534
Merit: 1046


Linux since 1997 RedHat 4


View Profile
September 11, 2013, 03:28:35 AM
 #12418

It appears that the API is reporting a different number of accepted shares than what is being shown on the output. Not sure if this is intentional for some reason or if this is an already known issue (sorry, not going through 600+ pages). Small example: CGMiner Output screen says 8105 accepted shares, the API returns 6786 for said device (1319 difference, seems to be across the board for each device).

Please let me know if you would like me to supply the data from the API vs. data on the output.
Nope, I don't see it on any of my 4 instances.
You'll need to provide more info.
Also ... try java API summary and java API devs and compare those outputs to the screen.

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #kano.is Majority developer of the ckpool code
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
tk1337
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250



View Profile
September 11, 2013, 03:52:29 AM
 #12419

It appears that the API is reporting a different number of accepted shares than what is being shown on the output. Not sure if this is intentional for some reason or if this is an already known issue (sorry, not going through 600+ pages). Small example: CGMiner Output screen says 8105 accepted shares, the API returns 6786 for said device (1319 difference, seems to be across the board for each device).

Please let me know if you would like me to supply the data from the API vs. data on the output.
Nope, I don't see it on any of my 4 instances.
You'll need to provide more info.
Also ... try java API summary and java API devs and compare those outputs to the screen.

CGMiner API summary reports a total accepted as 47634, CGMiner output shows the total as 57407, a difference of 9773 divide that by the number of devices (7), looking at a difference of around 1396 per device.

I'm falling asleep here, but I'll post screenshots & data to back up this tomorrow morning.

Edit: This is on linux (MinePeon distro) with ASIC USB Erupters only, however others are reporting an error with BFL devices as well on the same distro, I wrote a stand alone call (separate from MinePeon's WebUI) to see if there was any difference in what the WebUI was getting from CGMiner API versus what the WebUI was showing. Turns out, there is no difference in the WebUI on MinePeon's side, but it appears the difference is coming from CGMiner's API, as at the time of the call the numbers are off from what what the output screen is displaying.

If I helped you & you feel generous, donate some BTC to -> 1337tkvMSeY2fNgyNXVshAZixnGxLxuSmy
Do you like cheap GH/s? | MobileMinerApp Plugin for MinePeon
Krak
Hero Member
*****
Offline Offline

Activity: 591
Merit: 500



View Profile WWW
September 11, 2013, 03:54:35 AM
 #12420

It appears that the API is reporting a different number of accepted shares than what is being shown on the output. Not sure if this is intentional for some reason or if this is an already known issue (sorry, not going through 600+ pages). Small example: CGMiner Output screen says 8105 accepted shares, the API returns 6786 for said device (1319 difference, seems to be across the board for each device).

Please let me know if you would like me to supply the data from the API vs. data on the output.
Maybe you're using a pool with variable difficulty and you're at a hashrate that keeps you bouncing around between difficulty 1 and 2 shares?

BTC: 1KrakenLFEFg33A4f6xpwgv3UUoxrLPuGn
Pages: « 1 ... 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 [621] 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 ... 847 »
  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!