HellDiverUK
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 19, 2013, 08:31:12 AM |
|
Seems that the cgminer README doesn't updated with this information. cgminer doesn't have a word processor built in, nor does it play videos. Should those be mentioned in the README too? ![Huh](https://bitcointalk.org/Smileys/default/huh.gif)
|
|
|
|
kuzetsa
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 19, 2013, 09:58:54 AM |
|
Please note, the documented change was in the documentation, but it was in the file named "NEWS" along with all the other news about various changes made to cgminer: Version 3.8.0 - 10th November 2013
- api update version to 2.0 and remove GPU form API-README -Remove now unused scrypt files. - api.c remove all GPU/gpu references and correct code as required - Rudimentary removal of GPU OpenCL and Scrypt features from api.c - Reorder configure alphabetically for devices to compile and fail if no support is selected to be compiled in. - BaB update/format some comments - BlackArrowBitfury early GPIO V1 driver - Fine tune the reading of results in bitfury driver to not lose any across work restarts or corrupt due to store results not parsed during restart. - Send a zero length packet at the end of every usb transfer on windows in case libusb internally has batched them into one maxpacket sized. - Framework for ntime rolling, keep looking for OP_USB_INIT replies when other packets received - Configure source for a new BaB driver - sha2 allow external access to some macros and the K array - Fixed a math issue when reporting fan speed on the status line. - Use the main hashlist to store work done in the bitfury driver and remove work from the list by time, thereby fixing the duplicates at startup. Count hardware errors for when no match occurs. - Add a get and queue helper work function. - Remove GPU mining code. - Use libusb's own zero length packet support unless we have to emulate it on windows since only libusb knows for sure if it's needed. - Unlock the avalon qlock while sending tasks to not hold the lock for an extended period. - Sleep in avalon send task on return to the function to allow other code to work during the sleep period. - Send zero length packets when terminating a usb write aligned to maxpacketsize. - Do the driver flush in avalon code lockless since it can lead to deadlocks. - Reset the work_restart bool after the scanwork loop in case the driver flushes work synchronously. - Only check for the stratum clean message if we have had a valid message. - Get rid of the stage thread since all work can be asynchronously added now via hash_push anyway. - Remove the now incorrect faq entry regarding scrypt difficulty. - Check for fatal read errors and break out of the read loop in avalon. - Send errors are basically fatal in avalon driver so break out of the send tasks loop. - Make the avalon driver return -1 for hash count when usb fails, allowing the main loop code to send it the shutdown flag. - Break out of the hash work loops when a failure is detected instead of dropping into mt disable. - Use usbutils' own ftdi parser for avalon and the ftdir's own latency for managing timeouts since we can wait on reads with completely asynchronous reads+writes. - Use usbutils' own cps function for slowing rate of usb writes on avalon. - Fix build for no libcurl - Check length before submitting sync transfers
|
|
|
|
ewibit
Legendary
Offline
Activity: 2955
Merit: 1050
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 19, 2013, 12:06:25 PM |
|
Are you attempting to mine something not bitcoin, and are you on the latest version?
./cgminer -V ./cgminer: /usr/local/lib/libcurl.so.4: no version information available (required by ./cgminer) cgminer 3.8.2
with rotate to other alt coins (PPC, ZET) edit: now I have uncommended testnet=0 perhaps this is necessary in bitcoin.conf ![Huh](https://bitcointalk.org/Smileys/default/huh.gif)
|
|
|
|
-ck (OP)
Legendary
Offline
Activity: 4214
Merit: 1644
Ruu \o/
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 19, 2013, 12:09:01 PM |
|
Are you attempting to mine something not bitcoin, and are you on the latest version?
./cgminer -V ./cgminer: /usr/local/lib/libcurl.so.4: no version information available (required by ./cgminer) cgminer 3.8.2
with rotate to other alt coins (PPC, ZET) As predicted, and that's unsupported.
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
chr0me
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 108
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 19, 2013, 06:49:53 PM |
|
Getting hex2bin scan fail.
What happened to cgminer-nogpu.exe in 3.8?
|
- I do translations! PM me if interested - 19sfw2W3dAFrzerkxLS26aL4HuYGpN1LNP
|
|
|
|
chr0me
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 108
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 19, 2013, 07:02:56 PM |
|
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
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 19, 2013, 07:09:52 PM |
|
tried my first time to compile cgminer on my mac with osx 10.9. this is my configuration: ------------------------------------------------------------------------ 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: 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. 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.
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.
|
|
|
|
jedimstr
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 19, 2013, 07:24:16 PM |
|
tried my first time to compile cgminer on my mac with osx 10.9. this is my configuration: ------------------------------------------------------------------------ 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: 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. 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.
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
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 19, 2013, 07:27:28 PM |
|
You may have an easier time compiling it if you use Homebrew.
+1 Homebrew makes this stuff noob-proof.
|
|
|
|
3ds
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 19, 2013, 07:34:00 PM |
|
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-optionsSee: https://bitcointalk.org/index.php?topic=322129.msg3638926#msg3638926
|
|
|
|
CeeCee
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 19, 2013, 07:52:14 PM |
|
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.
|
|
|
|
CustomDesigned
Newbie
Offline
Activity: 35
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 19, 2013, 10:04:41 PM |
|
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
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 19, 2013, 10:13:36 PM |
|
... am i doing something wrong? should i just ignore them? cgminer is working, just tested with a block erupter.
This is also 'somewhat' wrong: 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.
|
|
|
|
Thndr
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 78
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 19, 2013, 11:05:20 PM |
|
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
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 108
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 19, 2013, 11:49:23 PM |
|
Why doesn't --bitburner-fury-options work?
|
- I do translations! PM me if interested - 19sfw2W3dAFrzerkxLS26aL4HuYGpN1LNP
|
|
|
CumpsD
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 20, 2013, 02:47:23 PM |
|
I just hooked up 2 BFL Jala's and am getting this: [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
Activity: 1450
Merit: 1013
Cryptanalyst castrated by his government, 1952
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 20, 2013, 06:18:11 PM Last edit: November 22, 2013, 12:46:36 PM by aigeezer |
|
Just got some weirdness in the "undead" test (Win7 64). https://bitcointalk.org/index.php?topic=28402.msg3611753#msg3611753Edit 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
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 71
Merit: 10
The way of the future...
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 21, 2013, 02:52:53 PM |
|
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
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 21, 2013, 02:57:27 PM |
|
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.
|
|
|
|
|