Bitcoin Forum
December 08, 2016, 12:19:07 AM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 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 672 673 674 675 676 677 678 [679] 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 ... 830 »
  Print  
Author Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.9.2  (Read 4822043 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.
aigeezer
Legendary
*
Offline Offline

Activity: 1280


Cryptanalyst castrated by his government, 1952


View Profile
November 19, 2013, 07:00:33 PM
 #13561

Getting hex2bin scan fail.

What happened to cgminer-nogpu.exe in 3.8?

https://bitcointalk.org/index.php?topic=28402.msg3538435#msg3538435
1481156347
Hero Member
*
Offline Offline

Posts: 1481156347

View Profile Personal Message (Offline)

Ignore
1481156347
Reply with quote  #2

1481156347
Report to moderator
1481156347
Hero Member
*
Offline Offline

Posts: 1481156347

View Profile Personal Message (Offline)

Ignore
1481156347
Reply with quote  #2

1481156347
Report to moderator
1481156347
Hero Member
*
Offline Offline

Posts: 1481156347

View Profile Personal Message (Offline)

Ignore
1481156347
Reply with quote  #2

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

Posts: 1481156347

View Profile Personal Message (Offline)

Ignore
1481156347
Reply with quote  #2

1481156347
Report to moderator
1481156347
Hero Member
*
Offline Offline

Posts: 1481156347

View Profile Personal Message (Offline)

Ignore
1481156347
Reply with quote  #2

1481156347
Report to moderator
1481156347
Hero Member
*
Offline Offline

Posts: 1481156347

View Profile Personal Message (Offline)

Ignore
1481156347
Reply with quote  #2

1481156347
Report to moderator
chr0me
Member
**
Offline Offline

Activity: 108


View Profile
November 19, 2013, 07:02:56 PM
 #13562


Cheers.

I'm having trouble getting cgminer to differentiate between the Bitburner Furys and XXs. Regardless of using --bitburner-fury-options it uses the --avalon-options for all devices.

- I do translations! PM me if interested -
19sfw2W3dAFrzerkxLS26aL4HuYGpN1LNP
CeeCee
Full Member
***
Offline Offline

Activity: 233


View Profile
November 19, 2013, 07:09:52 PM
 #13563

tried my first time to compile cgminer on my mac with osx 10.9.

this is my configuration:
Code:
------------------------------------------------------------------------
cgminer 3.8.2
------------------------------------------------------------------------


Configuration Options Summary:

  libcurl(GBT+getwork).: Enabled: -L/opt/local/lib -lcurl
  curses.TUI...........: FOUND: -lncurses

  Avalon.ASICs.........: Enabled
  BlackArrow.ASICs.....: Enabled
  BFL.ASICs............: Enabled
  BitForce.FPGAs.......: Enabled
  BitFury.ASICs........: Enabled
  Hashfast.ASICs.......: Disabled
  Icarus.ASICs/FPGAs...: Enabled
  Klondike.ASICs.......: Enabled
  KnC.ASICs............: Disabled
  ModMiner.FPGAs.......: Enabled

Compilation............: make (or gmake)
  CPPFLAGS.............:
  CFLAGS...............: -g -O2
  LDFLAGS..............:  -framework CoreFoundation -framework IOKit
  LDADD................: -ldl -L/opt/local/lib -lcurl  compat/jansson-2.5/src/.libs/libjansson.a -lpthread    -lm compat/libusb-1.0/libusb/.libs/libusb-1.0.a -lobjc

Installation...........: make install (as root if needed, with 'su' or 'sudo')
  prefix...............: /usr/local

and i got these warnings:
Code:
  CC     cgminer-api.o
api.c:1136:6: warning: format specifies type 'long' but the argument has type '__darwin_suseconds_t' (aka 'int') [-Wformat]
                                        ((struct timeval *)(root->data))->tv_usec);
                                        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/secure/_stdio.h:47:56: note: expanded from macro 'sprintf'
  __builtin___sprintf_chk (str, 0, __darwin_obsz(str), __VA_ARGS__)
                                                       ^
1 warning generated.
Code:
  CC     cgminer-driver-bflsc.o
driver-bflsc.c:836:29: warning: implicit conversion from 'double' to 'unsigned int' changes value from 71.58 to 71 [-Wliteral-conversion]
        sc_info->default_ms_work = BAS_WORK_TIME;
                                 ~ ^~~~~~~~~~~~~
./driver-bflsc.h:313:23: note: expanded from macro 'BAS_WORK_TIME'
#define BAS_WORK_TIME 71.58
                      ^~~~~
driver-bflsc.c:846:30: warning: implicit conversion from 'double' to 'unsigned int' changes value from 71.58 to 71 [-Wliteral-conversion]
                sc_info->default_ms_work = BAM_WORK_TIME;
                                         ~ ^~~~~~~~~~~~~
./driver-bflsc.h:312:23: note: expanded from macro 'BAM_WORK_TIME'
#define BAM_WORK_TIME 71.58
                      ^~~~~
driver-bflsc.c:853:31: warning: implicit conversion from 'double' to 'unsigned int' changes value from 954.4400000000001 to 954 [-Wliteral-conversion]
                        sc_info->default_ms_work = BAJ_WORK_TIME;
                                                 ~ ^~~~~~~~~~~~~
./driver-bflsc.h:317:23: note: expanded from macro 'BAJ_WORK_TIME'
#define BAJ_WORK_TIME 954.44
                      ^~~~~~
driver-bflsc.c:859:31: warning: implicit conversion from 'double' to 'unsigned int' changes value from 143.17 to 143 [-Wliteral-conversion]
                        sc_info->default_ms_work = BAL_WORK_TIME;
                                                 ~ ^~~~~~~~~~~~~
./driver-bflsc.h:315:23: note: expanded from macro 'BAL_WORK_TIME'
#define BAL_WORK_TIME 143.17
                      ^~~~~~
4 warnings generated.
Code:
  CC     cgminer-driver-icarus.o
driver-icarus.c:1163:21: warning: format specifies type 'long' but the argument has type '__darwin_suseconds_t' (aka 'int') [-Wformat]
                                elapsed.tv_sec, elapsed.tv_usec);
                                                ^~~~~~~~~~~~~~~
./logging.h:39:42: note: expanded from macro 'applog'
                        snprintf(tmp42, sizeof(tmp42), fmt, ##__VA_ARGS__); \
                                                              ^
/usr/include/secure/_stdio.h:57:62: note: expanded from macro 'snprintf'
  __builtin___snprintf_chk (str, len, 0, __darwin_obsz(str), __VA_ARGS__)
                                                             ^
driver-icarus.c:1199:20: warning: format specifies type 'long' but the argument has type '__darwin_suseconds_t' (aka 'int') [-Wformat]
                        elapsed.tv_sec, elapsed.tv_usec);
                                        ^~~~~~~~~~~~~~~
./logging.h:39:42: note: expanded from macro 'applog'
                        snprintf(tmp42, sizeof(tmp42), fmt, ##__VA_ARGS__); \
                                                              ^
/usr/include/secure/_stdio.h:57:62: note: expanded from macro 'snprintf'
  __builtin___snprintf_chk (str, len, 0, __darwin_obsz(str), __VA_ARGS__)
                                                             ^
2 warnings generated.

am i doing something wrong? should i just ignore them?
cgminer is working, just tested with a block erupter.

1CeeCee4mFTHjCnZ4rSJWchLFhW5agirDb
jedimstr
Hero Member
*****
Offline Offline

Activity: 784



View Profile
November 19, 2013, 07:24:16 PM
 #13564

tried my first time to compile cgminer on my mac with osx 10.9.

this is my configuration:
Code:
------------------------------------------------------------------------
cgminer 3.8.2
------------------------------------------------------------------------


Configuration Options Summary:

  libcurl(GBT+getwork).: Enabled: -L/opt/local/lib -lcurl
  curses.TUI...........: FOUND: -lncurses

  Avalon.ASICs.........: Enabled
  BlackArrow.ASICs.....: Enabled
  BFL.ASICs............: Enabled
  BitForce.FPGAs.......: Enabled
  BitFury.ASICs........: Enabled
  Hashfast.ASICs.......: Disabled
  Icarus.ASICs/FPGAs...: Enabled
  Klondike.ASICs.......: Enabled
  KnC.ASICs............: Disabled
  ModMiner.FPGAs.......: Enabled

Compilation............: make (or gmake)
  CPPFLAGS.............:
  CFLAGS...............: -g -O2
  LDFLAGS..............:  -framework CoreFoundation -framework IOKit
  LDADD................: -ldl -L/opt/local/lib -lcurl  compat/jansson-2.5/src/.libs/libjansson.a -lpthread    -lm compat/libusb-1.0/libusb/.libs/libusb-1.0.a -lobjc

Installation...........: make install (as root if needed, with 'su' or 'sudo')
  prefix...............: /usr/local

and i got these warnings:
Code:
  CC     cgminer-api.o
api.c:1136:6: warning: format specifies type 'long' but the argument has type '__darwin_suseconds_t' (aka 'int') [-Wformat]
                                        ((struct timeval *)(root->data))->tv_usec);
                                        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/secure/_stdio.h:47:56: note: expanded from macro 'sprintf'
  __builtin___sprintf_chk (str, 0, __darwin_obsz(str), __VA_ARGS__)
                                                       ^
1 warning generated.
Code:
  CC     cgminer-driver-bflsc.o
driver-bflsc.c:836:29: warning: implicit conversion from 'double' to 'unsigned int' changes value from 71.58 to 71 [-Wliteral-conversion]
        sc_info->default_ms_work = BAS_WORK_TIME;
                                 ~ ^~~~~~~~~~~~~
./driver-bflsc.h:313:23: note: expanded from macro 'BAS_WORK_TIME'
#define BAS_WORK_TIME 71.58
                      ^~~~~
driver-bflsc.c:846:30: warning: implicit conversion from 'double' to 'unsigned int' changes value from 71.58 to 71 [-Wliteral-conversion]
                sc_info->default_ms_work = BAM_WORK_TIME;
                                         ~ ^~~~~~~~~~~~~
./driver-bflsc.h:312:23: note: expanded from macro 'BAM_WORK_TIME'
#define BAM_WORK_TIME 71.58
                      ^~~~~
driver-bflsc.c:853:31: warning: implicit conversion from 'double' to 'unsigned int' changes value from 954.4400000000001 to 954 [-Wliteral-conversion]
                        sc_info->default_ms_work = BAJ_WORK_TIME;
                                                 ~ ^~~~~~~~~~~~~
./driver-bflsc.h:317:23: note: expanded from macro 'BAJ_WORK_TIME'
#define BAJ_WORK_TIME 954.44
                      ^~~~~~
driver-bflsc.c:859:31: warning: implicit conversion from 'double' to 'unsigned int' changes value from 143.17 to 143 [-Wliteral-conversion]
                        sc_info->default_ms_work = BAL_WORK_TIME;
                                                 ~ ^~~~~~~~~~~~~
./driver-bflsc.h:315:23: note: expanded from macro 'BAL_WORK_TIME'
#define BAL_WORK_TIME 143.17
                      ^~~~~~
4 warnings generated.
Code:
  CC     cgminer-driver-icarus.o
driver-icarus.c:1163:21: warning: format specifies type 'long' but the argument has type '__darwin_suseconds_t' (aka 'int') [-Wformat]
                                elapsed.tv_sec, elapsed.tv_usec);
                                                ^~~~~~~~~~~~~~~
./logging.h:39:42: note: expanded from macro 'applog'
                        snprintf(tmp42, sizeof(tmp42), fmt, ##__VA_ARGS__); \
                                                              ^
/usr/include/secure/_stdio.h:57:62: note: expanded from macro 'snprintf'
  __builtin___snprintf_chk (str, len, 0, __darwin_obsz(str), __VA_ARGS__)
                                                             ^
driver-icarus.c:1199:20: warning: format specifies type 'long' but the argument has type '__darwin_suseconds_t' (aka 'int') [-Wformat]
                        elapsed.tv_sec, elapsed.tv_usec);
                                        ^~~~~~~~~~~~~~~
./logging.h:39:42: note: expanded from macro 'applog'
                        snprintf(tmp42, sizeof(tmp42), fmt, ##__VA_ARGS__); \
                                                              ^
/usr/include/secure/_stdio.h:57:62: note: expanded from macro 'snprintf'
  __builtin___snprintf_chk (str, len, 0, __darwin_obsz(str), __VA_ARGS__)
                                                             ^
2 warnings generated.

am i doing something wrong? should i just ignore them?
cgminer is working, just tested with a block erupter.

You may have an easier time compiling it if you use Homebrew.

Then you just have to tap nwolls' formula:

brew tap nwoolls/xgminer
brew install cgminer

HellDiverUK
Hero Member
*****
Offline Offline

Activity: 574


View Profile
November 19, 2013, 07:27:28 PM
 #13565


You may have an easier time compiling it if you use Homebrew.


+1

Homebrew makes this stuff noob-proof.
3ds
Full Member
***
Offline Offline

Activity: 224


View Profile
November 19, 2013, 07:34:00 PM
 #13566

I'm having trouble getting cgminer to differentiate between the Bitburner Furys and XXs. Regardless of using --bitburner-fury-options it uses the --avalon-options for all devices.

Interesting: I have trouble with BitBurner Fury and cgminer, too. My single Board mines always with ~30GH/s It seems no matter what I set with --bitburner-fury-options or --avalon-options

See: https://bitcointalk.org/index.php?topic=322129.msg3638926#msg3638926

Mining Hardware? -> cex.io
Trade over 60 different types of cryptocurrencies -> cryptsy.com
CeeCee
Full Member
***
Offline Offline

Activity: 233


View Profile
November 19, 2013, 07:52:14 PM
 #13567


You may have an easier time compiling it if you use Homebrew.


+1

Homebrew makes this stuff noob-proof.
but the way i tried to compile was easy too. just './configure' and then 'make'. all needed libs where already installed with macports/fink. just want to ask about the warnings. but thanks for your advice i will give this a try.

1CeeCee4mFTHjCnZ4rSJWchLFhW5agirDb
CustomDesigned
Newbie
*
Offline Offline

Activity: 26


View Profile
November 19, 2013, 10:04:41 PM
 #13568

Hmm, the changes to 3.8.2 seem to concern avalon, and I have Icarus.  So it likely won't help me, but I'll give it a try on next restart.

I have 4 USB ASIC Miners, which cgminer detects at Icarus.  It runs for 2-4 hours before half the units are disabled with a message like the following:

 [2013-11-18 17:49:20] AMU 4 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-11-18 17:49:20] AMU4: Comms error (werr=-7 amt=22)
 [2013-11-18 17:49:20] AMU 4 failure, disabling!

For a while, the failed units are discovered again via hotplug:

 [2013-11-18 17:49:23] Hotplug: Icarus added AMU 5

But hotplug eventually fails to rediscover failed units.  However, restarting cgminer does rediscover them.

Restarted with cgminer this morning with 3.8.2 + patches from git master.  It has been 6 hours, and 8 ASICs have gone zombie, and then been rediscovered without issue.  So, this looks like a keeper on Fedora 19!

With this approach, the AMU number will keep rising.  How high can it go before restarting is advisable?  Does each disabled AMU use memory?  Or is it just a matter of overflowing 2^31 ?  Restarting weekly is probably a sane policy. 
kano
Legendary
*
Offline Offline

Activity: 1932


Linux since 1997 RedHat 4


View Profile
November 19, 2013, 10:13:36 PM
 #13569

...
am i doing something wrong? should i just ignore them?
cgminer is working, just tested with a block erupter.

This is also 'somewhat' wrong:
Quote
 BlackArrow.ASICs.....: Enabled

They only work on linux with an RPi.

It will just create an empty driver that does nothing and causes no problems on non-linux systems - so will be no problem on non-linux - but it's also pointless including it.

Aside: on linux it will actually attempt the GPIO/SPI initialisation of the board which might be problematic depending on what hardware you have.

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
Thndr
Jr. Member
*
Offline Offline

Activity: 53


View Profile
November 19, 2013, 11:05:20 PM
 #13570

Hey I know 3.8.0+ doesn't support GPU, but I have a question that may have been answered before:

Catalyst 13.9+ seems to crash CGminer 2.10.5+ with it's OpenCL driver.

I've noticed since Catalyst 13.4+ that it doesn't have an option to install/update specifically the Amd APP SDK Runtime driver, but it automatically installs the newest version when you install the display driver.


Is there a solution to get it working with the latest GPU CGminer, or do I have to keep using 2.10.4? Or do you recommend me switching to a different miner? If so, what do you suggest?
chr0me
Member
**
Offline Offline

Activity: 108


View Profile
November 19, 2013, 11:49:23 PM
 #13571

Why doesn't --bitburner-fury-options work?

- I do translations! PM me if interested -
19sfw2W3dAFrzerkxLS26aL4HuYGpN1LNP
CumpsD
Sr. Member
****
Offline Offline

Activity: 476


View Profile
November 20, 2013, 02:47:23 PM
 #13572

I just hooked up 2 BFL Jala's and am getting this:

Quote
[2013-11-20 14:44:17] Started cgminer 3.6.3
 [2013-11-20 14:44:17] Loaded configuration file /home/btc/cgminer.conf
 [2013-11-20 14:44:17] USB scan devices: checking for BFL devices
 [2013-11-20 14:44:17] RES: thread starting
 [2013-11-20 14:44:18] BFL looking for and found BFL 0403:6014
 [2013-11-20 14:44:18] USB lock BitForce 1-5
 [2013-11-20 14:44:18] RES: BitForce (1:5) lock=1
 [2013-11-20 14:44:18] USB res lock BitForce 1-5
 [2013-11-20 14:44:18] RES: BitForce (1:5) lock ok=1
 [2013-11-20 14:44:18] USB init, iManufacturer mismatch - BFL device 1:5
 [2013-11-20 14:44:18] USB free BFL
 [2013-11-20 14:44:18] USB unlock BitForce 1-5
 [2013-11-20 14:44:18] BFL looking for and found BFL 0403:6014
 [2013-11-20 14:44:18] RES: BitForce (1:5) lock=0
 [2013-11-20 14:44:18] USB res unlock BitForce 1-5
 [2013-11-20 14:44:18] USB lock BitForce 1-4
 [2013-11-20 14:44:18] RES: BitForce (1:4) lock=1
 [2013-11-20 14:44:18] USB res lock BitForce 1-4
 [2013-11-20 14:44:18] RES: BitForce (1:4) lock ok=1
 [2013-11-20 14:44:18] USB init, iManufacturer mismatch - BFL device 1:4
 [2013-11-20 14:44:18] USB free BFL
 [2013-11-20 14:44:18] USB unlock BitForce 1-4
 [2013-11-20 14:44:18] BFL looking for BFL 0403:6014 but found 0424:ec00 instead
 [2013-11-20 14:44:18] RES: BitForce (1:4) lock=0
 [2013-11-20 14:44:18] BFL looking for BFL 0403:6014 but found 0424:9512 instead
 [2013-11-20 14:44:18] USB res unlock BitForce 1-4
 [2013-11-20 14:44:18] BFL looking for BFL 0403:6014 but found 1d6b:0002 instead

 [2013-11-20 14:44:18] USB init, iManufacturer mismatch - BFL device 1:4

What am I doing wrong to get this?

----
Nevermind, probably forgot to compile it in
aigeezer
Legendary
*
Offline Offline

Activity: 1280


Cryptanalyst castrated by his government, 1952


View Profile
November 20, 2013, 06:18:11 PM
 #13573

Just got some weirdness in the "undead" test (Win7 64).

https://bitcointalk.org/index.php?topic=28402.msg3611753#msg3611753

Edit update: my undead run has now gone over 96 hours without a crash. Latest quirks include finding AMUs 17 18 19 21 26 30-33 running and 0-3 flagged as zombies. Unplugging the hub reset them to 0-11, all zombies and one missing for some reason. Replugging the hub set them as 34-46 (all accounted for). A while later I saw an LED on and one AMU flagged as a zombie in the display. Before I could intervene, it repaired itself. The "zombie" label went off and the unit started hashing again - I didn't notice what number it was assigned to, distracted because I had never seen that display change happen before - perhaps it's not unusual. Presently the AMUs are allocated 34-40 and 43-48. I didn't see 41 or 42 get reallocated, but presumably they are now 47 and 48.

Edit update: 120 hours in to the undead run. One more zombie, reported as AMU0 (but see above list of numbers allocated). It restarted fine when swapped. Allocations are now 34 35 36 38 40 43 44 48-53, so several have been successfully reallocated without intervention in the last 24 hours.


bitcoinanon
Member
**
Offline Offline

Activity: 71


The way of the future...


View Profile
November 21, 2013, 02:52:53 PM
 #13574

OK so I have compiled cgminer onto my laptop running Ubuntu. But when i run cgminer and it runs the config file it follows with an error saying that no devices were found. I have three klondike 16's hooked up to a usb hub. I followed directions but i did not install ADL_SDK. I did not think I needed it since i am not gpu mining. Do i need something else? OR do i Need ADL_SDK?
HellDiverUK
Hero Member
*****
Offline Offline

Activity: 574


View Profile
November 21, 2013, 02:57:27 PM
 #13575


Catalyst 13.9+ seems to crash CGminer 2.10.5+ with it's OpenCL driver.



Use the 12.8 drivers.  They were the only ones that ever worked properly for me.
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2002


Ruu \o/


View Profile WWW
November 21, 2013, 07:52:14 PM
 #13576

OK so I have compiled cgminer onto my laptop running Ubuntu. But when i run cgminer and it runs the config file it follows with an error saying that no devices were found. I have three klondike 16's hooked up to a usb hub. I followed directions but i did not install ADL_SDK. I did not think I needed it since i am not gpu mining. Do i need something else? OR do i Need ADL_SDK?

No. Did you copy the udev rules file?

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

Activity: 71


The way of the future...


View Profile
November 21, 2013, 07:55:44 PM
 #13577

OK so I have compiled cgminer onto my laptop running Ubuntu. But when i run cgminer and it runs the config file it follows with an error saying that no devices were found. I have three klondike 16's hooked up to a usb hub. I followed directions but i did not install ADL_SDK. I did not think I needed it since i am not gpu mining. Do i need something else? OR do i Need ADL_SDK?

No. Did you copy the udev rules file?

I did try to copy that file into the 01-cgminer.rules file but terminal did not respond. I rebooted and my computer still did not recognize the miners. Perhaps I am using the wrong code. But it was from the ASIC readme.
kano
Legendary
*
Offline Offline

Activity: 1932


Linux since 1997 RedHat 4


View Profile
November 21, 2013, 08:00:45 PM
 #13578

OK so I have compiled cgminer onto my laptop running Ubuntu. But when i run cgminer and it runs the config file it follows with an error saying that no devices were found. I have three klondike 16's hooked up to a usb hub. I followed directions but i did not install ADL_SDK. I did not think I needed it since i am not gpu mining. Do i need something else? OR do i Need ADL_SDK?

No. Did you copy the udev rules file?

I did try to copy that file into the 01-cgminer.rules file but terminal did not respond. I rebooted and my computer still did not recognize the miners. Perhaps I am using the wrong code. But it was from the ASIC readme.

Firstly
lsusb
should show something like:
Code:
Bus 001 Device 007: ID 04d8:f60a Microchip Technology, Inc.
for each Klondike ... just to be sure they are plugged in Smiley

Next
./cgminer -n
should show details about each

Also try running as sudo ./cgminer .... to see if it is a privilege (udev) problem
(i.e. you didn't do what the README says to do)

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
bitcoinanon
Member
**
Offline Offline

Activity: 71


The way of the future...


View Profile
November 21, 2013, 08:15:53 PM
 #13579

is there code to check if my user has plugdev permissions?

Edit: I figured it out. Went through the steps one more time and then did a hard reboot from terminal. I booted cgminer and the k16's began hashing.
CustomDesigned
Newbie
*
Offline Offline

Activity: 26


View Profile
November 21, 2013, 09:37:41 PM
 #13580


Restarted with cgminer this morning with 3.8.2 + patches from git master.  It has been 6 hours, and 8 ASICs have gone zombie, and then been rediscovered without issue.  So, this looks like a keeper on Fedora 19!

With this approach, the AMU number will keep rising.  How high can it go before restarting is advisable?  Does each disabled AMU use memory?  Or is it just a matter of overflowing 2^31 ?  Restarting weekly is probably a sane policy. 

After approx. 2 days, half of the ASIC units are zombies again.  BUT, now simply restarting the software did not awake them.  I had to unplug, and replug the failed units.  (Fortunately, when they aren't hashing, they don't burn your fingers!) 

This reminds me of the ALWAC II [ http://en.wikipedia.org/wiki/Axel_Wenner-Gren ] at Naval Research Labs.  It had 256 bytes all electronic (vacuum tube) RAM, which was paged in its entirety from a magnetic drum memory.  Computations within the page of RAM were blindingly fast by the standards of the day, and the Fortran compiler was able to optimize for this.  However, because 256 bytes (with parity) was a lot of vacuum tubes, the failure rate was fairly high.  You needed to run your program 3 times, and if it got the same answer 2 out of 3 times, you were good.   

Why does this remind me of USB ASIC mining?  Well, a ground breaking invention on the ALWAC was a parity bit on each byte of memory.  Each byte was on its own vacuum tube board, with a neon (high reliability) lamp which glowed when the parity check failed.  An apprentice had a cart of vacuum tubes, and would race down the aisle to each board that was lit, replace all 9 tubes (they could be tested and the good ones recycled later), and run to the next.  That's what I feel like, checking for the green LEDs on the USB ASIC array, and replugging the units.
Pages: « 1 ... 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 672 673 674 675 676 677 678 [679] 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 ... 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!