-ck (OP)
Legendary
Offline
Activity: 4242
Merit: 1644
Ruu \o/
|
|
June 10, 2013, 07:34:32 AM |
|
Okay, clearly I am missing something. I have my Jalapeno plugged directly into my rpi. Should I not be doing that in order to get cgminer to recognize it? I am running it headless, just my rpi with my jalapeno plugged into it and using putty for anything, not using a keyboard. So, maybe I missed something. I have a USB 2.0 hub I could use if that for some reason solves the problem.
https://bitcointalk.org/index.php?topic=28402.msg2409598#msg2409598Try increasing the timeout and recompiling. Some jalepenos appear to be taking >850 ms to respond to the initial getinfo request in linux. There's a change that directly addresses this already in git master, so compiling from git master should do it.
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
stormos
Newbie
Offline
Activity: 56
Merit: 0
|
|
June 10, 2013, 10:52:24 AM |
|
There is a problem with 3.2.xx on GPU only machines running windows 7 and catalyst driver 13.4 CGMiner crashes at start Oldest drivers or previous versions of cgminer work fine [2013-06-10 14:37:52] Started cgminer 3.2.1 [2013-06-10 14:37:52] Loaded configuration file cgminer.conf [2013-06-10 14:37:52] RES: thread starting [2013-06-10 14:37:52] CL Platform 0 vendor: Advanced Micro Devices, Inc. [2013-06-10 14:37:52] CL Platform 0 name: AMD Accelerated Parallel Processing [2013-06-10 14:37:52] CL Platform 0 version: OpenCL 1.2 AMD-APP (1124.2) [2013-06-10 14:37:52] Platform 0 devices: 1 [2013-06-10 14:37:52] 0 Cypress [2013-06-10 14:37:52] GPU 0 iAdapterIndex 0 strUDID PCI_VEN_1002&DEV_689E&SUBSYS_E140174B&REV_00_4&EEFFDB8&0&0008A iBusNumber 1 iDeviceNumber 0 iFunctionNumber 0 iVendorID 1002 strAdapterName ATI Radeon HD 5800 Series [2013-06-10 14:37:53] GPU 0 ATI Radeon HD 5800 Series hardware monitoring enabled [2013-06-10 14:37:53] Setting GPU 0 engine clock to 973 [2013-06-10 14:37:53] Setting GPU 0 memory clock to 600 [2013-06-10 14:37:53] USB scan devices: checking for ICA devices [2013-06-10 14:37:53] ICA looking for ICA 067b:2303 but found 8086:1c2d instead [2013-06-10 14:37:53] ICA looking for AMU 10c4:ea60 but found 8086:1c2d instead [2013-06-10 14:37:53] ICA looking for BLT 0403:6001 but found 8086:1c2d instead [2013-06-10 14:37:53] ICA looking for LLT 0403:6001 but found 8086:1c2d instead [2013-06-10 14:37:53] ICA looking for CMR 0403:8350 but found 8086:1c2d instead [2013-06-10 14:37:53] ICA looking for CMR 0403:6014 but found 8086:1c2d instead [2013-06-10 14:37:53] ICA looking for ICA 067b:2303 but found 8086:1c26 instead [2013-06-10 14:37:53] ICA looking for AMU 10c4:ea60 but found 8086:1c26 instead [2013-06-10 14:37:53] ICA looking for BLT 0403:6001 but found 8086:1c26 instead [2013-06-10 14:37:53] ICA looking for LLT 0403:6001 but found 8086:1c26 instead [2013-06-10 14:37:53] ICA looking for CMR 0403:8350 but found 8086:1c26 instead [2013-06-10 14:37:53] ICA looking for CMR 0403:6014 but found 8086:1c26 instead [2013-06-10 14:37:53] ICA looking for ICA 067b:2303 but found 046d:c312 instead [2013-06-10 14:37:53] ICA looking for AMU 10c4:ea60 but found 046d:c312 instead [2013-06-10 14:37:53] ICA looking for BLT 0403:6001 but found 046d:c312 instead [2013-06-10 14:37:53] ICA looking for LLT 0403:6001 but found 046d:c312 instead [2013-06-10 14:37:53] ICA looking for CMR 0403:8350 but found 046d:c312 instead [2013-06-10 14:37:53] ICA looking for CMR 0403:6014 but found 046d:c312 instead [2013-06-10 14:37:53] ICA looking for ICA 067b:2303 but found 046d:c52f instead [2013-06-10 14:37:53] ICA looking for AMU 10c4:ea60 but found 046d:c52f instead [2013-06-10 14:37:53] ICA looking for BLT 0403:6001 but found 046d:c52f instead [2013-06-10 14:37:53] ICA looking for LLT 0403:6001 but found 046d:c52f instead [2013-06-10 14:37:53] ICA looking for CMR 0403:8350 but found 046d:c52f instead [2013-06-10 14:37:53] ICA looking for CMR 0403:6014 but found 046d:c52f instead [2013-06-10 14:37:53] ICA looking for ICA 067b:2303 but found 04b4:6560 instead [2013-06-10 14:37:53] ICA looking for AMU 10c4:ea60 but found 04b4:6560 instead [2013-06-10 14:37:53] ICA looking for BLT 0403:6001 but found 04b4:6560 instead [2013-06-10 14:37:53] ICA looking for LLT 0403:6001 but found 04b4:6560 instead [2013-06-10 14:37:53] ICA looking for CMR 0403:8350 but found 04b4:6560 instead [2013-06-10 14:37:53] ICA looking for CMR 0403:6014 but found 04b4:6560 instead [2013-06-10 14:37:53] ICA looking for ICA 067b:2303 but found 058f:6387 instead [2013-06-10 14:37:53] ICA looking for AMU 10c4:ea60 but found 058f:6387 instead [2013-06-10 14:37:53] ICA looking for BLT 0403:6001 but found 058f:6387 instead [2013-06-10 14:37:53] ICA looking for LLT 0403:6001 but found 058f:6387 instead [2013-06-10 14:37:53] ICA looking for CMR 0403:8350 but found 058f:6387 instead [2013-06-10 14:37:53] ICA looking for CMR 0403:6014 but found 058f:6387 instead [2013-06-10 14:37:53] ICA looking for ICA 067b:2303 but found 8087:0024 instead [2013-06-10 14:37:53] ICA looking for AMU 10c4:ea60 but found 8087:0024 instead [2013-06-10 14:37:53] ICA looking for BLT 0403:6001 but found 8087:0024 instead [2013-06-10 14:37:53] ICA looking for LLT 0403:6001 but found 8087:0024 instead [2013-06-10 14:37:53] ICA looking for CMR 0403:8350 but found 8087:0024 instead [2013-06-10 14:37:53] ICA looking for CMR 0403:6014 but found 8087:0024 instead [2013-06-10 14:37:53] ICA looking for ICA 067b:2303 but found 8087:0024 instead [2013-06-10 14:37:53] ICA looking for AMU 10c4:ea60 but found 8087:0024 instead [2013-06-10 14:37:53] ICA looking for BLT 0403:6001 but found 8087:0024 instead [2013-06-10 14:37:53] ICA looking for LLT 0403:6001 but found 8087:0024 instead [2013-06-10 14:37:53] ICA looking for CMR 0403:8350 but found 8087:0024 instead [2013-06-10 14:37:53] ICA looking for CMR 0403:6014 but found 8087:0024 instead [2013-06-10 14:37:53] USB scan devices: checking for BAS devices [2013-06-10 14:37:53] BAS looking for BAS 0403:6014 but found 8086:1c2d instead [2013-06-10 14:37:53] BAS looking for BAS 0403:6014 but found 8086:1c26 instead [2013-06-10 14:37:53] BAS looking for BAS 0403:6014 but found 046d:c312 instead [2013-06-10 14:37:53] BAS looking for BAS 0403:6014 but found 046d:c52f instead [2013-06-10 14:37:53] BAS looking for BAS 0403:6014 but found 04b4:6560 instead [2013-06-10 14:37:53] BAS looking for BAS 0403:6014 but found 058f:6387 instead [2013-06-10 14:37:53] BAS looking for BAS 0403:6014 but found 8087:0024 instead [2013-06-10 14:37:53] BAS looking for BAS 0403:6014 but found 8087:0024 instead [2013-06-10 14:37:53] USB scan devices: checking for BFL devices [2013-06-10 14:37:53] BFL looking for BFL 0403:6014 but found 8086:1c2d instead [2013-06-10 14:37:53] BFL looking for BFL 0403:6014 but found 8086:1c26 instead [2013-06-10 14:37:53] BFL looking for BFL 0403:6014 but found 046d:c312 instead [2013-06-10 14:37:53] BFL looking for BFL 0403:6014 but found 046d:c52f instead [2013-06-10 14:37:53] BFL looking for BFL 0403:6014 but found 04b4:6560 instead [2013-06-10 14:37:53] BFL looking for BFL 0403:6014 but found 058f:6387 instead [2013-06-10 14:37:53] BFL looking for BFL 0403:6014 but found 8087:0024 instead [2013-06-10 14:37:53] BFL looking for BFL 0403:6014 but found 8087:0024 instead [2013-06-10 14:37:53] USB scan devices: checking for MMQ devices [2013-06-10 14:37:53] MMQ looking for MMQ 1fc9:0003 but found 8086:1c2d instead [2013-06-10 14:37:53] MMQ looking for MMQ 1fc9:0003 but found 8086:1c26 instead [2013-06-10 14:37:53] MMQ looking for MMQ 1fc9:0003 but found 046d:c312 instead [2013-06-10 14:37:53] MMQ looking for MMQ 1fc9:0003 but found 046d:c52f instead [2013-06-10 14:37:53] MMQ looking for MMQ 1fc9:0003 but found 04b4:6560 instead [2013-06-10 14:37:53] MMQ looking for MMQ 1fc9:0003 but found 058f:6387 instead [2013-06-10 14:37:53] MMQ looking for MMQ 1fc9:0003 but found 8087:0024 instead [2013-06-10 14:37:53] MMQ looking for MMQ 1fc9:0003 but found 8087:0024 instead [2013-06-10 14:37:53] Not a ZTEX device 8086:1c2d [2013-06-10 14:37:53] Not a ZTEX device 8086:1c26 [2013-06-10 14:37:53] Not a ZTEX device 046d:c312 [2013-06-10 14:37:53] Not a ZTEX device 046d:c52f [2013-06-10 14:37:53] Not a ZTEX device 04b4:6560 [2013-06-10 14:37:53] Not a ZTEX device 058f:6387 [2013-06-10 14:37:53] Not a ZTEX device 8087:0024 [2013-06-10 14:37:53] Not a ZTEX device 8087:0024 [2013-06-10 14:37:53] Probing for an alive pool [2013-06-10 14:37:53] Popping work to stage thread [2013-06-10 14:37:53] Testing pool http://mint.bitminter.com:8332 [2013-06-10 14:37:53] Testing pool http://pool.50btc.com:8332 [2013-06-10 14:37:53] Testing pool http://pool-ru.50btc.com:8332 [2013-06-10 14:37:53] Testing pool http://mint.bitminter.com:8332 [2013-06-10 14:37:53] Testing pool http://stratum.bitcoin.cz:3333 [2013-06-10 14:37:53] Testing pool http://stratum.btcguild.com:3333 [2013-06-10 14:37:53] Testing pool http://pit.deepbit.net:8332 [2013-06-10 14:37:53] Probing for GBT support [2013-06-10 14:37:53] Probing for GBT support [2013-06-10 14:37:53] Probing for GBT support [2013-06-10 14:37:53] Probing for GBT support [2013-06-10 14:37:53] Probing for GBT support [2013-06-10 14:37:53] Probing for GBT support [2013-06-10 14:37:53] Probing for GBT support [2013-06-10 14:37:53] No GBT coinbase + append support found, using getwork protocol [2013-06-10 14:37:53] No GBT coinbase + append support found, using getwork protocol [2013-06-10 14:37:53] Testing pool 1 stratum stratum+tcp://50btc.com:3333 [2013-06-10 14:37:53] HTTP request failed: Empty reply from server [2013-06-10 14:37:53] No GBT coinbase + append support found, using getwork protocol [2013-06-10 14:37:54] Testing pool 2 stratum stratum+tcp://178.33.43.149:3333 [2013-06-10 14:37:54] Failed to get sessionid in initiate_stratum [2013-06-10 14:37:54] Switching pool 1 http://pool.50btc.com:8332 to stratum+tcp://50btc.com:3333 [2013-06-10 14:37:54] HTTP request failed: Empty reply from server [2013-06-10 14:37:54] No GBT coinbase + append support found, using getwork protocol [2013-06-10 14:37:54] Failed to get sessionid in initiate_stratum [2013-06-10 14:37:54] Switching pool 2 http://pool-ru.50btc.com:8332 to stratum+tcp://178.33.43.149:3333 [2013-06-10 14:37:54] Failed to get sessionid in initiate_stratum [2013-06-10 14:37:54] JSON-RPC call failed: { "code": -1, "message": "error" } [2013-06-10 14:37:54] No GBT coinbase + append support found, using getwork protocol [2013-06-10 14:37:54] HTTP request failed: Empty reply from server [2013-06-10 14:37:54] HTTP request failed: Empty reply from server [2013-06-10 14:37:54] Failed to get sessionid in initiate_stratum [2013-06-10 14:37:54] GBT coinbase + append support found, switching to GBT protocol [2013-06-10 14:37:54] GBT coinbase + append support found, switching to GBT protocol [2013-06-10 14:37:54] Stratum authorisation success for pool 1 [2013-06-10 14:37:54] Switching to pool 1 http://pool.50btc.com:8332 - first alive pool [2013-06-10 14:37:54] Pool 1 http://pool.50btc.com:8332 alive [2013-06-10 14:37:54] Failed to get sessionid in initiate_stratum [2013-06-10 14:37:54] Stratum authorisation success for pool 2 [2013-06-10 14:37:55] Pool 2 http://pool-ru.50btc.com:8332 alive [2013-06-10 14:37:55] Pool 4 stratum session id: ae6812eb4cd7735a302a8a9dd95cf71f [2013-06-10 14:37:55] Successfully retrieved and deciphered work from pool 6 http://pit.deepbit.net:8332 [2013-06-10 14:37:55] Pushing pooltest work to base pool [2013-06-10 14:37:55] Network diff set to 15.6M [2013-06-10 14:37:55] Pool 6 http://pit.deepbit.net:8332 alive [2013-06-10 14:37:55] New block: 000c3b869069aad9... diff 15.6M [2013-06-10 14:37:55] Pushing work to getwork queue [2013-06-10 14:37:55] Popping work to stage thread [2013-06-10 14:37:55] JSON-RPC decode failed: (unknown reason) [2013-06-10 14:37:55] Failed to resume stratum, trying afresh [2013-06-10 14:37:55] Testing pool 3 stratum stratum+tcp://eu1.bitminter.com:3333 [2013-06-10 14:37:55] Pushing ping to thread 0 [2013-06-10 14:37:55] Init GPU thread 0 GPU 0 virtual GPU 0 [2013-06-10 14:37:55] CL Platform vendor: Advanced Micro Devices, Inc. [2013-06-10 14:37:55] JSON-RPC decode failed: (unknown reason) [2013-06-10 14:37:55] CL Platform name: AMD Accelerated Parallel Processing [2013-06-10 14:37:55] Failed to resume stratum, trying afresh [2013-06-10 14:37:55] CL Platform version: OpenCL 1.2 AMD-APP (1124.2) [2013-06-10 14:37:55] List of devices: [2013-06-10 14:37:55] 0 Cypress [2013-06-10 14:37:55] Selected 0: Cypress [2013-06-10 14:37:55] Testing pool 0 stratum stratum+tcp://eu1.bitminter.com:3333 [2013-06-10 14:37:55] Preferred vector width reported 4 [2013-06-10 14:37:55] Max work group size reported 256 [2013-06-10 14:37:55] Max mem alloc size is 536870912 [2013-06-10 14:37:55] No binary found, generating from source [2013-06-10 14:37:55] Setting worksize to 128 [2013-06-10 14:37:55] Patched source to suit 2 vectors [2013-06-10 14:37:55] cl_amd_media_ops found, setting BITALIGN [2013-06-10 14:37:55] BFI_INT patch requiring device found, patched source with BFI_INT [2013-06-10 14:37:55] CompilerOptions: -D WORKSIZE=128 -D VECTORS2 -D WORKVEC=256 -D BITALIGN -D BFI_INT [2013-06-10 14:37:55] Failed to get sessionid in initiate_stratum [2013-06-10 14:37:55] Switching pool 3 http://mint.bitminter.com:8332 to stratum+tcp://eu1.bitminter.com:3333 [2013-06-10 14:37:55] Failed to get sessionid in initiate_stratum [2013-06-10 14:37:55] Switching pool 0 http://mint.bitminter.com:8332 to stratum+tcp://eu1.bitminter.com:3333 [2013-06-10 14:37:55] Failed to get sessionid in initiate_stratum [2013-06-10 14:37:55] Pool 5 difficulty set to 1.000000 [2013-06-10 14:37:55] Failed to get sessionid in initiate_stratum [2013-06-10 14:37:55] Pool 3 difficulty set to 1.000000 [2013-06-10 14:37:55] Stratum authorisation success for pool 3 [2013-06-10 14:37:55] Pool 3 http://mint.bitminter.com:8332 alive [2013-06-10 14:37:55] Failed to get sessionid in initiate_stratum [2013-06-10 14:37:55] Pool 0 difficulty set to 1.000000 [2013-06-10 14:37:55] Stratum authorisation success for pool 0 [2013-06-10 14:37:55] Pool 0 http://mint.bitminter.com:8332 alive [2013-06-10 14:37:55] Switching to pool 0 http://mint.bitminter.com:8332 [2013-06-10 14:37:55] Stratum authorisation success for pool 5 [2013-06-10 14:37:55] Pool 5 http://stratum.btcguild.com:3333 alive [2013-06-10 14:37:56] Closing socket for stratum pool 2 [2013-06-10 14:37:56] Pool 4 stratum session id: ae6812eb4cd7735a302a8a9dd95cf71f [2013-06-10 14:37:56] Closing socket for stratum pool 3 [2013-06-10 14:37:56] Closing socket for stratum pool 5 [2013-06-10 14:37:57] Stratum authorisation success for pool 4 [2013-06-10 14:37:57] Pool 4 http://stratum.bitcoin.cz:3333 alive [2013-06-10 14:37:57] Binary size for gpu 0 found in binary slot 0: 825208 [2013-06-10 14:37:57] At 0523bd6a (4290042414 rem. bytes), to begin patching
|
|
|
|
energywave
Newbie
Offline
Activity: 19
Merit: 0
|
|
June 10, 2013, 03:08:00 PM |
|
I'm experiencing a very odd and blocking problem: was mining with CGMINER 3.1.0 on Radeon HD 5750, never had problem, with SHA256 nor Scrypt, all was fine. At some point I tried CGMINER 3.2.0 and it crashed at start (could only see one line "Started CGMINER 3.2.0" and then crashed). The odd thing is that from that point over even all other versions of CGMINER do the same!!! I cannot anymore use CGMINER! I've tried with 3.1.1 (that I'm succesfully using on another PC): crash. 3.1.0 that was working well before: crash. Today I tried even 3.2.1: crash. I did a Dr. Mingw debug for you, hoping to understand what the hell is happening. cgminer.exe caused an Access Violation at location 004312d2 in module cgminer.exe Reading from location 072ff1d3.
Registers: eax=76709102 ebx=0445fd14 ecx=00000000 edx=00000000 esi=0445fc80 edi=00000000 eip=772de1a4 esp=0445fb58 ebp=0445fcd8 iopl=0 nv up ei pl nz na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202
Call stack: 772DE1A4 ntdll.dll:772DE1A4 ZwWaitForMultipleObjects 76AE6AEB KERNEL32.DLL:76AE6AEB WaitForMultipleObjects 0045A362 cgminer.exe:0045A362 0045ACD7 cgminer.exe:0045ACD7 Registers: eax=00000000 ebx=7fffffff ecx=00000000 edx=00000000 esi=ffffffff edi=0097c6d8 eip=772ddc34 esp=04d5f998 ebp=04d5f9d8 iopl=0 nv up ei pl nz na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202
Call stack: 772DDC34 ntdll.dll:772DDC34 NtWaitForSingleObject 71F78599 mswsock.dll:71F78599 Tcpip4_WSHGetWildcardSockaddr 75140CCF WS2_32.dll:75140CCF select 0041C6B8 cgminer.exe:0041C6B8 socket_full util.c:1057 0041C6FD cgminer.exe:0041C6FD sock_full util.c:1069 0040F6B0 cgminer.exe:0040F6B0 stratum_rthread cgminer.c:4962 00459F25 cgminer.exe:00459F25 7670906A msvcrt.dll:7670906A _ui64tow 76709147 msvcrt.dll:76709147 iswalnum 76AE8543 KERNEL32.DLL:76AE8543 BaseThreadInitThunk 7730BF39 ntdll.dll:7730BF39 RtlInitializeExceptionChain 7730BF0C ntdll.dll:7730BF0C RtlInitializeExceptionChain XXXXXXXXXXXXXXXXXXXXXX Registers: eax=072ff1cf ebx=02008668 ecx=ffb8e50d edx=00000008 esi=01ff2e68 edi=02007c6a eip=004312d2 esp=0028f4e0 ebp=0028f548 iopl=0 nv up ei pl nz na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202
Call stack: 004312D2 cgminer.exe:004312D2 patch_opcodes ocl.c:178 004333EF cgminer.exe:004333EF initCl ocl.c:738 00430218 cgminer.exe:00430218 opencl_thread_prepare driver-opencl.c:1332 00419410 cgminer.exe:00419410 main cgminer.c:7691 004010B9 cgminer.exe:004010B9 __mingw_CRTStartup crt1.c:244 00401284 cgminer.exe:00401284 WinMainCRTStartup crt1.c:274 76AE8543 KERNEL32.DLL:76AE8543 BaseThreadInitThunk 7730BF39 ntdll.dll:7730BF39 RtlInitializeExceptionChain 7730BF0C ntdll.dll:7730BF0C RtlInitializeExceptionChain Registers: eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=00000002 edi=0097afe0 eip=772df6b4 esp=048dfdec ebp=048dff84 iopl=0 nv up ei pl nz na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202
Call stack: 772DF6B4 ntdll.dll:772DF6B4 ZwWaitForWorkViaWorkerFactory 76AE8543 KERNEL32.DLL:76AE8543 BaseThreadInitThunk 7730BF39 ntdll.dll:7730BF39 RtlInitializeExceptionChain 7730BF0C ntdll.dll:7730BF0C RtlInitializeExceptionChain Registers: eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=0469fe6c edi=00001cb4 eip=772ddc34 esp=0469fe28 ebp=0469fe90 iopl=0 nv up ei pl nz na po nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000206
Call stack: 772DDC34 ntdll.dll:772DDC34 NtWaitForSingleObject 753A10B4 KERNELBASE.dll:753A10B4 WaitForSingleObject 0FB90B1B amdocl.dll:0FB90B1B clGetSamplerInfo 0FB872A7 amdocl.dll:0FB872A7 clGetSamplerInfo 0FB87456 amdocl.dll:0FB87456 clGetSamplerInfo 0FB84362 amdocl.dll:0FB84362 clGetSamplerInfo 0FB96FD6 amdocl.dll:0FB96FD6 clGetSamplerInfo 76AE8543 KERNEL32.DLL:76AE8543 BaseThreadInitThunk 7730BF39 ntdll.dll:7730BF39 RtlInitializeExceptionChain 7730BF0C ntdll.dll:7730BF0C RtlInitializeExceptionChain Registers: eax=00000000 ebx=04b1f8a4 ecx=00000000 edx=00000000 esi=04b1f810 edi=00000000 eip=772de1a4 esp=04b1f6e8 ebp=04b1f868 iopl=0 nv up ei pl nz na po nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000206
Call stack: 772DE1A4 ntdll.dll:772DE1A4 ZwWaitForMultipleObjects 76AE6AEB KERNEL32.DLL:76AE6AEB WaitForMultipleObjects 0045A362 cgminer.exe:0045A362 0045ACD7 cgminer.exe:0045ACD7 753AEE71 KERNELBASE.dll:753AEE71 CreateEventExW 753AEE8C KERNELBASE.dll:753AEE8C CreateEventExW 753B3BFE KERNELBASE.dll:753B3BFE CreateEventExA 00458630 cgminer.exe:00458630 0041BD00 cgminer.exe:0041BD00 tq_pop util.c:769 0040F9D0 cgminer.exe:0040F9D0 stratum_sthread cgminer.c:5053 00459F25 cgminer.exe:00459F25 7670906A msvcrt.dll:7670906A _ui64tow 76709147 msvcrt.dll:76709147 iswalnum 76AE8543 KERNEL32.DLL:76AE8543 BaseThreadInitThunk 7730BF39 ntdll.dll:7730BF39 RtlInitializeExceptionChain 7730BF0C ntdll.dll:7730BF0C RtlInitializeExceptionChain Registers: eax=76709102 ebx=6b619070 ecx=00000000 edx=00000000 esi=029afe90 edi=00000000 eip=772de1a4 esp=029afd68 ebp=029afee8 iopl=0 nv up ei pl nz na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202
Call stack: 772DE1A4 ntdll.dll:772DE1A4 ZwWaitForMultipleObjects 76AE6AEB KERNEL32.DLL:76AE6AEB WaitForMultipleObjects 6B608229 libusb-1.0.dll:6B608229 windows_clock_gettime_threaded 76709147 msvcrt.dll:76709147 iswalnum 76AE8543 KERNEL32.DLL:76AE8543 BaseThreadInitThunk 7730BF39 ntdll.dll:7730BF39 RtlInitializeExceptionChain 7730BF0C ntdll.dll:7730BF0C RtlInitializeExceptionChain
I hope that someone can lead me to the solution.... I'm now using bitminter java client, but I want a scrypt miner and I like so much CGMINER...! Thank you in advance to who will reply!
|
|
|
|
mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
June 10, 2013, 03:30:39 PM |
|
I'm experiencing a very odd and blocking problem: was mining with CGMINER 3.1.0 on Radeon HD 5750, never had problem, with SHA256 nor Scrypt, all was fine. At some point I tried CGMINER 3.2.0 and it crashed at start (could only see one line "Started CGMINER 3.2.0" and then crashed). The odd thing is that from that point over even all other versions of CGMINER do the same!!! I cannot anymore use CGMINER! I've tried with 3.1.1 (that I'm succesfully using on another PC): crash. 3.1.0 that was working well before: crash. Today I tried even 3.2.1: crash. I did a Dr. Mingw debug for you, hoping to understand what the hell is happening.
sounds like a task is still running, or you need to reboot? M
|
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me!
|
|
|
af_newbie
Legendary
Offline
Activity: 2702
Merit: 1468
|
|
June 10, 2013, 03:35:40 PM |
|
I'm experiencing a very odd and blocking problem: was mining with CGMINER 3.1.0 on Radeon HD 5750, never had problem, with SHA256 nor Scrypt, all was fine. At some point I tried CGMINER 3.2.0 and it crashed at start (could only see one line "Started CGMINER 3.2.0" and then crashed). The odd thing is that from that point over even all other versions of CGMINER do the same!!! I cannot anymore use CGMINER! I've tried with 3.1.1 (that I'm succesfully using on another PC): crash. 3.1.0 that was working well before: crash. Today I tried even 3.2.1: crash. I did a Dr. Mingw debug for you, hoping to understand what the hell is happening. cgminer.exe caused an Access Violation at location 004312d2 in module cgminer.exe Reading from location 072ff1d3.
Registers: eax=76709102 ebx=0445fd14 ecx=00000000 edx=00000000 esi=0445fc80 edi=00000000 eip=772de1a4 esp=0445fb58 ebp=0445fcd8 iopl=0 nv up ei pl nz na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202
Call stack: 772DE1A4 ntdll.dll:772DE1A4 ZwWaitForMultipleObjects 76AE6AEB KERNEL32.DLL:76AE6AEB WaitForMultipleObjects 0045A362 cgminer.exe:0045A362 0045ACD7 cgminer.exe:0045ACD7 Registers: eax=00000000 ebx=7fffffff ecx=00000000 edx=00000000 esi=ffffffff edi=0097c6d8 eip=772ddc34 esp=04d5f998 ebp=04d5f9d8 iopl=0 nv up ei pl nz na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202
Call stack: 772DDC34 ntdll.dll:772DDC34 NtWaitForSingleObject 71F78599 mswsock.dll:71F78599 Tcpip4_WSHGetWildcardSockaddr 75140CCF WS2_32.dll:75140CCF select 0041C6B8 cgminer.exe:0041C6B8 socket_full util.c:1057 0041C6FD cgminer.exe:0041C6FD sock_full util.c:1069 0040F6B0 cgminer.exe:0040F6B0 stratum_rthread cgminer.c:4962 00459F25 cgminer.exe:00459F25 7670906A msvcrt.dll:7670906A _ui64tow 76709147 msvcrt.dll:76709147 iswalnum 76AE8543 KERNEL32.DLL:76AE8543 BaseThreadInitThunk 7730BF39 ntdll.dll:7730BF39 RtlInitializeExceptionChain 7730BF0C ntdll.dll:7730BF0C RtlInitializeExceptionChain XXXXXXXXXXXXXXXXXXXXXX Registers: eax=072ff1cf ebx=02008668 ecx=ffb8e50d edx=00000008 esi=01ff2e68 edi=02007c6a eip=004312d2 esp=0028f4e0 ebp=0028f548 iopl=0 nv up ei pl nz na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202
Call stack: 004312D2 cgminer.exe:004312D2 patch_opcodes ocl.c:178 004333EF cgminer.exe:004333EF initCl ocl.c:738 00430218 cgminer.exe:00430218 opencl_thread_prepare driver-opencl.c:1332 00419410 cgminer.exe:00419410 main cgminer.c:7691 004010B9 cgminer.exe:004010B9 __mingw_CRTStartup crt1.c:244 00401284 cgminer.exe:00401284 WinMainCRTStartup crt1.c:274 76AE8543 KERNEL32.DLL:76AE8543 BaseThreadInitThunk 7730BF39 ntdll.dll:7730BF39 RtlInitializeExceptionChain 7730BF0C ntdll.dll:7730BF0C RtlInitializeExceptionChain Registers: eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=00000002 edi=0097afe0 eip=772df6b4 esp=048dfdec ebp=048dff84 iopl=0 nv up ei pl nz na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202
Call stack: 772DF6B4 ntdll.dll:772DF6B4 ZwWaitForWorkViaWorkerFactory 76AE8543 KERNEL32.DLL:76AE8543 BaseThreadInitThunk 7730BF39 ntdll.dll:7730BF39 RtlInitializeExceptionChain 7730BF0C ntdll.dll:7730BF0C RtlInitializeExceptionChain Registers: eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=0469fe6c edi=00001cb4 eip=772ddc34 esp=0469fe28 ebp=0469fe90 iopl=0 nv up ei pl nz na po nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000206
Call stack: 772DDC34 ntdll.dll:772DDC34 NtWaitForSingleObject 753A10B4 KERNELBASE.dll:753A10B4 WaitForSingleObject 0FB90B1B amdocl.dll:0FB90B1B clGetSamplerInfo 0FB872A7 amdocl.dll:0FB872A7 clGetSamplerInfo 0FB87456 amdocl.dll:0FB87456 clGetSamplerInfo 0FB84362 amdocl.dll:0FB84362 clGetSamplerInfo 0FB96FD6 amdocl.dll:0FB96FD6 clGetSamplerInfo 76AE8543 KERNEL32.DLL:76AE8543 BaseThreadInitThunk 7730BF39 ntdll.dll:7730BF39 RtlInitializeExceptionChain 7730BF0C ntdll.dll:7730BF0C RtlInitializeExceptionChain Registers: eax=00000000 ebx=04b1f8a4 ecx=00000000 edx=00000000 esi=04b1f810 edi=00000000 eip=772de1a4 esp=04b1f6e8 ebp=04b1f868 iopl=0 nv up ei pl nz na po nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000206
Call stack: 772DE1A4 ntdll.dll:772DE1A4 ZwWaitForMultipleObjects 76AE6AEB KERNEL32.DLL:76AE6AEB WaitForMultipleObjects 0045A362 cgminer.exe:0045A362 0045ACD7 cgminer.exe:0045ACD7 753AEE71 KERNELBASE.dll:753AEE71 CreateEventExW 753AEE8C KERNELBASE.dll:753AEE8C CreateEventExW 753B3BFE KERNELBASE.dll:753B3BFE CreateEventExA 00458630 cgminer.exe:00458630 0041BD00 cgminer.exe:0041BD00 tq_pop util.c:769 0040F9D0 cgminer.exe:0040F9D0 stratum_sthread cgminer.c:5053 00459F25 cgminer.exe:00459F25 7670906A msvcrt.dll:7670906A _ui64tow 76709147 msvcrt.dll:76709147 iswalnum 76AE8543 KERNEL32.DLL:76AE8543 BaseThreadInitThunk 7730BF39 ntdll.dll:7730BF39 RtlInitializeExceptionChain 7730BF0C ntdll.dll:7730BF0C RtlInitializeExceptionChain Registers: eax=76709102 ebx=6b619070 ecx=00000000 edx=00000000 esi=029afe90 edi=00000000 eip=772de1a4 esp=029afd68 ebp=029afee8 iopl=0 nv up ei pl nz na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202
Call stack: 772DE1A4 ntdll.dll:772DE1A4 ZwWaitForMultipleObjects 76AE6AEB KERNEL32.DLL:76AE6AEB WaitForMultipleObjects 6B608229 libusb-1.0.dll:6B608229 windows_clock_gettime_threaded 76709147 msvcrt.dll:76709147 iswalnum 76AE8543 KERNEL32.DLL:76AE8543 BaseThreadInitThunk 7730BF39 ntdll.dll:7730BF39 RtlInitializeExceptionChain 7730BF0C ntdll.dll:7730BF0C RtlInitializeExceptionChain
I hope that someone can lead me to the solution.... I'm now using bitminter java client, but I want a scrypt miner and I like so much CGMINER...! Thank you in advance to who will reply! Did you delete bin files? Reset the drivers to USB/COM? If nothing works, re-compile and remove all the fpga stuff.
|
|
|
|
energywave
Newbie
Offline
Activity: 19
Merit: 0
|
|
June 10, 2013, 03:57:10 PM |
|
thank you for answering me sounds like a task is still running, or you need to reboot? A task is still running? I don't understand, however I've rebooted several times without positive effects. Last try was to install catalyst 13.6 beta2 (I was on 13.5 beta that worked flawlessy, before to try CGMINER 3.2.0) Did you delete bin files? Reset the drivers to USB/COM? If nothing works, re-compile and remove all the fpga stuff. At first try I've copied CGMINER 3.2.0 files inside my old 3.1.0 CGMINER folder to update files (yes, all files + folders). That was the first crash, then I prepared a separate folder for every CGMINER version to be sure that no old file was messing up something. All my tried after first crash are from clean, just extracted folders. Reset drivers to USB/COM: what is that? I'm mining with just GPU, no FPGA nor ASIC. Recompile removing FPGA stuff... Uhm... that's will be my last last last resource.... Do you believe something about FPGA/ASIC is involved? If so why even returning to older 3.1.0 that was working is still crashing my system? For instance Bitminter java client is mining flawlessy. Damn, what a strange problem...
|
|
|
|
af_newbie
Legendary
Offline
Activity: 2702
Merit: 1468
|
|
June 10, 2013, 04:03:30 PM |
|
thank you for answering me sounds like a task is still running, or you need to reboot? A task is still running? I don't understand, however I've rebooted several times without positive effects. Last try was to install catalyst 13.6 beta2 (I was on 13.5 beta that worked flawlessy, before to try CGMINER 3.2.0) Did you delete bin files? Reset the drivers to USB/COM? If nothing works, re-compile and remove all the fpga stuff. At first try I've copied CGMINER 3.2.0 files inside my old 3.1.0 CGMINER folder to update files (yes, all files + folders). That was the first crash, then I prepared a separate folder for every CGMINER version to be sure that no old file was messing up something. All my tried after first crash are from clean, just extracted folders. Reset drivers to USB/COM: what is that? I'm mining with just GPU, no FPGA nor ASIC. Recompile removing FPGA stuff... Uhm... that's will be my last last last resource.... Do you believe something about FPGA/ASIC is involved? If so why even returning to older 3.1.0 that was working is still crashing my system? For instance Bitminter java client is mining flawlessy. Damn, what a strange problem... Call stack: 772DE1A4 ntdll.dll:772DE1A4 ZwWaitForMultipleObjects 76AE6AEB KERNEL32.DLL:76AE6AEB WaitForMultipleObjects 6B608229 libusb-1.0.dll:6B608229 windows_clock_gettime_threaded76709147 msvcrt.dll:76709147 iswalnum 76AE8543 KERNEL32.DLL:76AE8543 BaseThreadInitThunk 7730BF39 ntdll.dll:7730BF39 RtlInitializeExceptionChain 7730BF0C ntdll.dll:7730BF0C RtlInitializeExceptionChain I would recompile and remove FPGA code, if I were you.
|
|
|
|
Tamis
|
|
June 10, 2013, 04:47:50 PM |
|
Hi guys ! I really hope someone will be able to help me with this problem. I just added a HD 5870 (ATI) to my computer that already has a gtx-680 (nvidia). Having read that in windows 7 you can install both cards without a problem I was happy to see instalation was not a problem. The latest beta catalyst drivers (AMD Catalyst™ 13.6 Beta2) instaled without a problem and both card are recognized by windows. I did not install any SDK since it was not necessary with the 13.6 beta2 with my HD 5850 that runs in another computer. I though I could launch cgminer with default command line and the babies do their work, but I get an error message in cgminer :/ command line to launch cgminer : cgminer.exe -o http://stratum.bitcoin.cz:3333 -u user -p pass I get the following errors : and once I press enter : I searched for an answer on the forum and the web and the only solution I found involves disabling the nvidia card, connecting the screen to the amd card and launching the miner then enabling the nvidia card and switch the screen again. I have not tested this yet but it is not very practical. There is also a similar post on this forum but no answer was given : https://bitcointalk.org/index.php?topic=174091.0I can do a cgminer -n dump if needed ! I hope someone can help me through this problem. Tamis
|
|
|
|
Zanatos666
Sr. Member
Offline
Activity: 280
Merit: 250
Sometimes man, just sometimes.....
|
|
June 10, 2013, 04:56:03 PM |
|
Hi guys ! I really hope someone will be able to help me with this problem. I just added a HD 5870 (ATI) to my computer that already has a gtx-680 (nvidia). Having read that in windows 7 you can install both cards without a problem I was happy to see instalation was not a problem. The latest beta catalyst drivers (AMD Catalyst™ 13.6 Beta2) instaled without a problem and both card are recognized by windows. I did not install any SDK since it was not necessary with the 13.6 beta2 with my HD 5850 that runs in another computer. I though I could launch cgminer with default command line and the babies do their work, but I get an error message in cgminer :/ command line to launch cgminer : cgminer.exe -o http://stratum.bitcoin.cz:3333 -u user -p pass I get the following errors : and once I press enter : I searched for an answer on the forum and the web and the only solution I found involves disabling the nvidia card, connecting the screen to the amd card and launching the miner then enabling the nvidia card and switch the screen again. I have not tested this yet but it is not very practical. There is also a similar post on this forum but no answer was given : https://bitcointalk.org/index.php?topic=174091.0I can do a cgminer -n dump if needed ! I hope someone can help me through this problem. Tamis I dont know if this would work, but what about getting/making a dummy plug for your AMD card, and in your configuration in CGMiner, disabling the GPU number that corresponds to your Nvidia card? This way CGMiner shouldnt try and use it, and the dummy plug will make your system think your AMD card is plugged into a monitor.
|
Squiggly letters, written really fast, with a couple of dots for good measure.
|
|
|
energywave
Newbie
Offline
Activity: 19
Merit: 0
|
|
June 10, 2013, 04:57:50 PM |
|
I would recompile and remove FPGA code, if I were you.
Ok, thank you for the hint, I have to learn what I need to compile CGMINER. That can be instructive so I'll try. Thank you for poining me at libusb, I didn't note that.
|
|
|
|
Tamis
|
|
June 10, 2013, 05:23:05 PM |
|
I dont know if this would work, but what about getting/making a dummy plug for your AMD card, and in your configuration in CGMiner, disabling the GPU number that corresponds to your Nvidia card? This way CGMiner shouldnt try and use it, and the dummy plug will make your system think your AMD card is plugged into a monitor.
I should have said that my AMD card has a hdmi to vga adaptater connected. Those work as dummy plug no ?
|
|
|
|
Zanatos666
Sr. Member
Offline
Activity: 280
Merit: 250
Sometimes man, just sometimes.....
|
|
June 10, 2013, 06:08:30 PM |
|
I dont know if this would work, but what about getting/making a dummy plug for your AMD card, and in your configuration in CGMiner, disabling the GPU number that corresponds to your Nvidia card? This way CGMiner shouldnt try and use it, and the dummy plug will make your system think your AMD card is plugged into a monitor.
I should have said that my AMD card has a hdmi to vga adaptater connected. Those work as dummy plug no ? Could not tell you. I know when I had my 5870 running on Windows before switching to BAMT, I didnt need dummy plugs, the drivers worked just fine with it. Maybe try scaling back your drivers to something older in the 11.x or 12.x, getting rid of the connect on you 5870 altogether, and seeing what results that yields.
|
Squiggly letters, written really fast, with a couple of dots for good measure.
|
|
|
pirate1
Member
Offline
Activity: 75
Merit: 10
|
|
June 10, 2013, 08:58:20 PM |
|
Ok, I have a noob question. I am running a BitForce Single (FPGA), and two 6870 graphics cards mining Bitcoins. I have been using cgminer-2.10.5. It has been working fine. However, I am getting ready to receive my new BitForce Single (ASIC) and updating in preparation. When I try to use cgminer-3.2.1 I get the following message:
[2013-06-10 16:26:47] Started cgminer 3.2.1 [2013-06-10 16:26:47] USB init, open device failed, err -12, you need to install a Windows USB driver for - CMR device 2:1 [2013-06-10 16:26:47] Icarus detect (2:1) failed to initialise (incorrect device?) [2013-06-10 16:26:47] USB init, open device failed, err -12, you need to install a Windows USB driver for - BAS device 2:1 [2013-06-10 16:26:47] BitForceSC detect (2:1) failed to initialise (incorrect device?) [2013-06-10 16:26:47] USB init, open device failed, err -12, you need to install a Windows USB driver for - BFL device 2:1 [2013-06-10 16:26:47] BitForce detect (2:1) failed to initialise (incorrect device?)
I can still use cgminer-2.10.5 with no problem. I don't understand what I need to do or why one version works but not the other. I do not know where to look for or how to install the drivers. I have the latest updates. As I said, a noob question, but I still don't understand what I need to do. I know it is probably something simple and straightforward but I would appreciate some help.
|
As long as I wake up breathing it's all a bonus. Sometimes not much of a bonus but still a bonus.
|
|
|
Zanatos666
Sr. Member
Offline
Activity: 280
Merit: 250
Sometimes man, just sometimes.....
|
|
June 10, 2013, 09:10:54 PM |
|
Ok, I have a noob question. I am running a BitForce Single (FPGA), and two 6870 graphics cards mining Bitcoins. I have been using cgminer-2.10.5. It has been working fine. However, I am getting ready to receive my new BitForce Single (ASIC) and updating in preparation. When I try to use cgminer-3.2.1 I get the following message:
[2013-06-10 16:26:47] Started cgminer 3.2.1 [2013-06-10 16:26:47] USB init, open device failed, err -12, you need to install a Windows USB driver for - CMR device 2:1 [2013-06-10 16:26:47] Icarus detect (2:1) failed to initialise (incorrect device?) [2013-06-10 16:26:47] USB init, open device failed, err -12, you need to install a Windows USB driver for - BAS device 2:1 [2013-06-10 16:26:47] BitForceSC detect (2:1) failed to initialise (incorrect device?) [2013-06-10 16:26:47] USB init, open device failed, err -12, you need to install a Windows USB driver for - BFL device 2:1 [2013-06-10 16:26:47] BitForce detect (2:1) failed to initialise (incorrect device?)
I can still use cgminer-2.10.5 with no problem. I don't understand what I need to do or why one version works but not the other. I do not know where to look for or how to install the drivers. I have the latest updates. As I said, a noob question, but I still don't understand what I need to do. I know it is probably something simple and straightforward but I would appreciate some help.
Have you tried downloading the USB driver from BFL's website?
|
Squiggly letters, written really fast, with a couple of dots for good measure.
|
|
|
freshzive
|
|
June 10, 2013, 09:27:43 PM |
|
I'm running cgminer3.1.1 with 7 USB Block Erupters (Ubuntu 12.04 x64). I am seeing an abnormally high amount of rejects (~10%), see screenshot. I thought this might be pool specific, but I've tried 3 pools now and it seems consistent across all of them. The rejects come in big chunks, suddenly I'll get a run of 20+. They are generally "stale work" or some other similar error. Is there something I can do to fix this? I tried updating to 3.2.1m but it seems my USB3 hub doesn't work well with the new version, so I had to downgrade. I guess I may just have to get a new hub and use the new version?
|
|
|
|
atomicchaos
|
|
June 10, 2013, 10:22:18 PM |
|
I am solo mining LTC on my rigs, and have them pointing to a wallet on my LAN. When I added a failover pool (Coinotron), it picks up updates from that pool, and all new blocks come across as: "Stratum from Pool 1 Detected New Block" Instead of the expected solo: "New Block Detected"
I also get "Stratum Connection to Pool 1 Interrupted" and "Pool 1 Difficulty Changed to xxx" messages frequently.
It doesn't appear to impact me as I still find my solo blocks, but I'm wondering if I need to change back to just solo with no failover, so it doesn't keep wandering over to my failover pool to see what is going on there. Is this normal behavior? Does it take away any performance by checking both my local wallet and the pool? Thanks in advance for any advice!
|
BTC:113mFe2e3oRkZQ5GeqKhoHbGtVw16unnw2
|
|
|
-ck (OP)
Legendary
Offline
Activity: 4242
Merit: 1644
Ruu \o/
|
|
June 10, 2013, 10:44:55 PM |
|
I am solo mining LTC on my rigs, and have them pointing to a wallet on my LAN. When I added a failover pool (Coinotron), it picks up updates from that pool, and all new blocks come across as: "Stratum from Pool 1 Detected New Block" Instead of the expected solo: "New Block Detected"
I also get "Stratum Connection to Pool 1 Interrupted" and "Pool 1 Difficulty Changed to xxx" messages frequently.
It doesn't appear to impact me as I still find my solo blocks, but I'm wondering if I need to change back to just solo with no failover, so it doesn't keep wandering over to my failover pool to see what is going on there. Is this normal behavior? Does it take away any performance by checking both my local wallet and the pool? Thanks in advance for any advice!
This is intentional and advantageous for solo miners.
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
pirate1
Member
Offline
Activity: 75
Merit: 10
|
|
June 10, 2013, 11:29:15 PM |
|
Zanatos, I did download from the BFL site. I didn't understand how to install it but I checked versions and it is the same version I have installed. Cgminer-2.10.5 is working fine so I don't understand why the new one is not working for me.
|
As long as I wake up breathing it's all a bonus. Sometimes not much of a bonus but still a bonus.
|
|
|
-ck (OP)
Legendary
Offline
Activity: 4242
Merit: 1644
Ruu \o/
|
|
June 10, 2013, 11:30:57 PM |
|
Zanatos, I did download from the BFL site. I didn't understand how to install it but I checked versions and it is the same version I have installed. Cgminer-2.10.5 is working fine so I don't understand why the new one is not working for me.
Read the readme THAT COMES WITH THE VERSION YOU HAVE. It clearly says when you're starting that it needs a WinUSB driver, but you have the FTDI driver installed.
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
atomicchaos
|
|
June 11, 2013, 12:35:54 AM |
|
I am solo mining LTC on my rigs, and have them pointing to a wallet on my LAN. When I added a failover pool (Coinotron), it picks up updates from that pool, and all new blocks come across as: "Stratum from Pool 1 Detected New Block" Instead of the expected solo: "New Block Detected"
I also get "Stratum Connection to Pool 1 Interrupted" and "Pool 1 Difficulty Changed to xxx" messages frequently.
It doesn't appear to impact me as I still find my solo blocks, but I'm wondering if I need to change back to just solo with no failover, so it doesn't keep wandering over to my failover pool to see what is going on there. Is this normal behavior? Does it take away any performance by checking both my local wallet and the pool? Thanks in advance for any advice!
This is intentional and advantageous for solo miners. Thank you very much for the confirmation. I believe from what I read Stratum is much more dependable and makes sure that you are on the correct block and in sync with the chain. I wanted to make sure that it wasn't degrading anything by watching the pool info at the same time it solo mines. I assume if I removed the Stratum from the failover it would test if there was any degradation, I just didn't experiment. I greatly appreciate you answering my question.
|
BTC:113mFe2e3oRkZQ5GeqKhoHbGtVw16unnw2
|
|
|
|