Topic: Modular Python Bitcoin Miner - Official Thread - page 7. (Read 74189 times)
It seems like Im getting a very high rate of rejects on gpumax. Over 10%. Is this normal.
Hm, that looks like a Python or OpenUSB/LibUSB/PyUSB bug. You might want to try a different Python/PyUSB version.
Ok, just FYI. This worked with the previous version of MPBM. So the new web-based version is doing something different.
I tried both pyusb-1.0.0-a0 and pyusb-1.0.0a2 and neither worked. I switched back to v0.0.4 and my x6500 boards are working again. Any ideas?
Honestly, I like v0.0.4 better. It's much easier to spot if anything is wrong with my miners. The latest has a lot of stats, but most of them don't mean much to me. So it makes it harder for me to find the important ones like hashrate and stales. You should consider make it adjustable so I could hide the stats I don't care about.
No matter what I do, I can't get this to work correctly on a mac. Tried different versions of python/pyUSB/libusb, but nothing. 0.4 runs beautifully out of the box, guess I'll stick with that for now.
Yes, I'm on a Mac too. And I've reverted back to 0.0.4. TheSeven, let me know if there's anything we can do to help get this fixed for the Mac.
Hm, that looks like a Python or OpenUSB/LibUSB/PyUSB bug. You might want to try a different Python/PyUSB version.
Ok, just FYI. This worked with the previous version of MPBM. So the new web-based version is doing something different.
I tried both pyusb-1.0.0-a0 and pyusb-1.0.0a2 and neither worked. I switched back to v0.0.4 and my x6500 boards are working again. Any ideas?
Honestly, I like v0.0.4 better. It's much easier to spot if anything is wrong with my miners. The latest has a lot of stats, but most of them don't mean much to me. So it makes it harder for me to find the important ones like hashrate and stales. You should consider make it adjustable so I could hide the stats I don't care about.
No matter what I do, I can't get this to work correctly on a mac. Tried different versions of python/pyUSB/libusb, but nothing. 0.4 runs beautifully out of the box, guess I'll stick with that for now.
Hm, that looks like a Python or OpenUSB/LibUSB/PyUSB bug. You might want to try a different Python/PyUSB version.
Ok, just FYI. This worked with the previous version of MPBM. So the new web-based version is doing something different.
I tried both pyusb-1.0.0-a0 and pyusb-1.0.0a2 and neither worked. I switched back to v0.0.4 and my x6500 boards are working again. Any ideas?
Honestly, I like v0.0.4 better. It's much easier to spot if anything is wrong with my miners. The latest has a lot of stats, but most of them don't mean much to me. So it makes it harder for me to find the important ones like hashrate and stales. You should consider make it adjustable so I could hide the stats I don't care about.
If it works with v0.0.4 this points towards an issue with forking. In v0.0.x everything was running in a single process, since v0.1.x the computationally intensive parts of some worker modules (x6500 and ztex) have been moved to out-of-process board proxys, which are created by forking the main process. This was neccessary to allow MPBM to use multiple processor cores for bigger clusters.
I know that the UI needs some improvement, however I'm pretty busy these days and thus focus on a stable backend for now. Feel free to submit a patch
Hm, that looks like a Python or OpenUSB/LibUSB/PyUSB bug. You might want to try a different Python/PyUSB version.
Ok, just FYI. This worked with the previous version of MPBM. So the new web-based version is doing something different.
I tried both pyusb-1.0.0-a0 and pyusb-1.0.0a2 and neither worked. I switched back to v0.0.4 and my x6500 boards are working again. Any ideas?
Honestly, I like v0.0.4 better. It's much easier to spot if anything is wrong with my miners. The latest has a lot of stats, but most of them don't mean much to me. So it makes it harder for me to find the important ones like hashrate and stales. You should consider make it adjustable so I could hide the stats I don't care about.
Hm, that looks like a Python or OpenUSB/LibUSB/PyUSB bug. You might want to try a different Python/PyUSB version.
Ok, just FYI. This worked with the previous version of MPBM. So the new web-based version is doing something different.
Hm, that looks like a Python or OpenUSB/LibUSB/PyUSB bug. You might want to try a different Python/PyUSB version.
Using the testing branch, I get this error on my Mac:
Any ideas?
Quote
2012-04-09 17:26:20.918 [100] X6500 worker - AH00WI18: Traceback (most recent call last):
File "/Users/charlie/Modular-Python-Bitcoin-Miner/modules/fpgamining/x6500/x6500worker.py", line 208, in main
data = self.rxconn.recv()
EOFError
File "/Users/charlie/Modular-Python-Bitcoin-Miner/modules/fpgamining/x6500/x6500worker.py", line 208, in main
data = self.rxconn.recv()
EOFError
Any ideas?
The real error message is probably a couple of lines above that.
This one just means that the board proxy connection closed unexpectedly. The proxy should have reported an error before dying.
No other error in log, but my Mac did throw up this dialog with an error in Python:
Code:
Process: Python [65198]
Path: /Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
Identifier: Python
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: Python [38184]
Date/Time: 2012-04-10 08:49:41.592 -0700
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6
Interval Since Last Report: 605434 sec
Crashes Since Last Report: 75
Per-App Crashes Since Last Report: 74
Anonymous UUID: DCA0F194-0D4B-4F5C-A3E3-45B04B466E1A
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008
Crashed Thread: 1
Application Specific Information:
*** multi-threaded process forked ***
Thread 0:
0 libSystem.B.dylib 0x00007fff85022a6a __semwait_signal + 10
1 libSystem.B.dylib 0x00007fff850228f9 nanosleep + 148
2 libSystem.B.dylib 0x00007fff85022863 usleep + 57
3 libusb-1.0.dylib 0x00000001015f1b5a darwin_init + 170
4 libusb-1.0.dylib 0x00000001015ec8a5 libusb_init + 133
5 _ctypes.so 0x0000000102790574 ffi_call_unix64 + 76
6 _ctypes.so 0x00000001027910e9 ffi_call + 537
7 _ctypes.so 0x000000010278b50f _ctypes_callproc + 895
8 _ctypes.so 0x000000010278345f PyCFuncPtr_call + 303
9 org.python.python 0x000000010000c5e2 PyObject_Call + 98
10 org.python.python 0x00000001000be5f3 PyEval_EvalFrameEx + 11587
11 org.python.python 0x00000001000c2d29 PyEval_EvalCodeEx + 2137
12 org.python.python 0x000000010003da80 function_call + 176
13 org.python.python 0x000000010000c5e2 PyObject_Call + 98
14 org.python.python 0x000000010001ebcb instancemethod_call + 363
15 org.python.python 0x000000010000c5e2 PyObject_Call + 98
16 org.python.python 0x0000000100077a68 slot_tp_init + 88
17 org.python.python 0x0000000100074e65 type_call + 245
18 org.python.python 0x000000010000c5e2 PyObject_Call + 98
19 org.python.python 0x00000001000be5f3 PyEval_EvalFrameEx + 11587
20 org.python.python 0x00000001000c1ebe PyEval_EvalFrameEx + 26126
21 org.python.python 0x00000001000c2d29 PyEval_EvalCodeEx + 2137
22 org.python.python 0x00000001000c0b6a PyEval_EvalFrameEx + 21178
23 org.python.python 0x00000001000c2d29 PyEval_EvalCodeEx + 2137
24 org.python.python 0x000000010003da80 function_call + 176
25 org.python.python 0x000000010000c5e2 PyObject_Call + 98
26 org.python.python 0x000000010001ebcb instancemethod_call + 363
27 org.python.python 0x000000010000c5e2 PyObject_Call + 98
28 org.python.python 0x0000000100077a68 slot_tp_init + 88
29 org.python.python 0x0000000100074e65 type_call + 245
30 org.python.python 0x000000010000c5e2 PyObject_Call + 98
31 org.python.python 0x00000001000be5f3 PyEval_EvalFrameEx + 11587
32 org.python.python 0x00000001000c1ebe PyEval_EvalFrameEx + 26126
33 org.python.python 0x00000001000c2d29 PyEval_EvalCodeEx + 2137
34 org.python.python 0x000000010003da80 function_call + 176
35 org.python.python 0x000000010000c5e2 PyObject_Call + 98
36 org.python.python 0x000000010001ebcb instancemethod_call + 363
37 org.python.python 0x000000010000c5e2 PyObject_Call + 98
38 org.python.python 0x00000001000ba5f7 PyEval_CallObjectWithKeywords + 87
39 org.python.python 0x0000000100021e5e PyInstance_New + 126
40 org.python.python 0x000000010000c5e2 PyObject_Call + 98
41 org.python.python 0x00000001000be5f3 PyEval_EvalFrameEx + 11587
42 org.python.python 0x00000001000c1ebe PyEval_EvalFrameEx + 26126
43 org.python.python 0x00000001000c1ebe PyEval_EvalFrameEx + 26126
44 org.python.python 0x00000001000c2d29 PyEval_EvalCodeEx + 2137
45 org.python.python 0x000000010003da80 function_call + 176
46 org.python.python 0x000000010000c5e2 PyObject_Call + 98
47 org.python.python 0x000000010001ebcb instancemethod_call + 363
48 org.python.python 0x000000010000c5e2 PyObject_Call + 98
49 org.python.python 0x0000000100077a68 slot_tp_init + 88
50 org.python.python 0x0000000100074e65 type_call + 245
51 org.python.python 0x000000010000c5e2 PyObject_Call + 98
52 org.python.python 0x00000001000be5f3 PyEval_EvalFrameEx + 11587
53 org.python.python 0x00000001000c1ebe PyEval_EvalFrameEx + 26126
54 org.python.python 0x00000001000c2d29 PyEval_EvalCodeEx + 2137
55 org.python.python 0x000000010003da80 function_call + 176
56 org.python.python 0x000000010000c5e2 PyObject_Call + 98
57 org.python.python 0x00000001000bd53c PyEval_EvalFrameEx + 7308
58 org.python.python 0x00000001000c1ebe PyEval_EvalFrameEx + 26126
59 org.python.python 0x00000001000c1ebe PyEval_EvalFrameEx + 26126
60 org.python.python 0x00000001000c2d29 PyEval_EvalCodeEx + 2137
61 org.python.python 0x000000010003da80 function_call + 176
62 org.python.python 0x000000010000c5e2 PyObject_Call + 98
63 org.python.python 0x000000010001ebcb instancemethod_call + 363
64 org.python.python 0x000000010000c5e2 PyObject_Call + 98
65 org.python.python 0x00000001000ba5f7 PyEval_CallObjectWithKeywords + 87
66 org.python.python 0x0000000100100a63 t_bootstrap + 67
67 libSystem.B.dylib 0x00007fff85020fd6 _pthread_start + 331
68 libSystem.B.dylib 0x00007fff85020e89 thread_start + 13
Thread 1 Crashed:
0 com.apple.CoreFoundation 0x00007fff81b37fb7 CFRunLoopAddSource + 71
1 libusb-1.0.dylib 0x00000001015f1be8 event_thread_main + 120
2 libSystem.B.dylib 0x00007fff85020fd6 _pthread_start + 331
3 libSystem.B.dylib 0x00007fff85020e89 thread_start + 13
Thread 1 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000075 rbx: 0x00007fff703ec390 rcx: 0x00007fff84ffa272 rdx: 0x0000000000000000
rdi: 0x0000000000000002 rsi: 0x00007fff81c2a868 rbp: 0x0000000106b80ed0 rsp: 0x0000000106b80e90
r8: 0x0000000106b80eaf r9: 0x0000000000000001 r10: 0x00007fff84ffa272 r11: 0x0000000000000202
r12: 0x00000001099cc350 r13: 0x00007fff703ec390 r14: 0x0000000000000000 r15: 0x0000000109e15820
rip: 0x00007fff81b37fb7 rfl: 0x0000000000010246 cr2: 0x0000000000000008
Binary Images:
0x100000000 - 0x100000fff +org.python.python 2.7.2 (2.7.2) <639E72E4-F205-C034-8E34-E59DE9C46369> /Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
0x100003000 - 0x10016cfef +org.python.python 2.7.2, (c) 2004-2011 Python Software Foundation. (2.7.2) <49D18B1A-C92D-E32E-A7C1-086D0B14BD76> /Library/Frameworks/Python.framework/Versions/2.7/Python
0x1002ec000 - 0x1002eefff +time.so ??? (???) <77136671-9973-6EFB-9A2D-127664836672> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/time.so
0x1002f4000 - 0x1002f7ff7 +strop.so ??? (???)/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/strop.so
0x1002fc000 - 0x1002fdff7 +_functools.so ??? (???) <755EA750-0AF2-4887-4C25-703D7366BB37> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_functools.so
0x1004f0000 - 0x1004f4ff7 +operator.so ??? (???)/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/operator.so
0x10053b000 - 0x10053dfff +_locale.so ??? (???) <7F398010-BCF7-FF58-065C-85B45DF4FC03> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_locale.so
0x100541000 - 0x100545fff +_struct.so ??? (???) <8FFF4DE5-5CF1-5DFD-ADE0-5AAD633838BF> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_struct.so
0x10054c000 - 0x10054ffef +binascii.so ??? (???) <89F159C8-99E7-6BB0-4829-3C441378FF07> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/binascii.so
0x100553000 - 0x100554fff +cStringIO.so ??? (???) <364F2486-CB7C-0DA0-C419-F3BCE469B261> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/cStringIO.so
0x100559000 - 0x100567fff +datetime.so ??? (???) <710107D4-44E6-D559-D71B-2D59CCC8966E> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/datetime.so
0x1005b3000 - 0x1005b7fff +_collections.so ??? (???) <101CE794-99F9-CF85-B3DF-B2ACA887CEDB> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_collections.so
0x1005bd000 - 0x1005c4ff7 +itertools.so ??? (???) <87448276-955A-B859-0CCB-35A9834894A7> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/itertools.so
0x1005cf000 - 0x1005cffff +_bisect.so ??? (???) <0872429A-9467-F3F6-BA8E-CCF6C9AD4FB5> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_bisect.so
0x1005d2000 - 0x1005d3ff7 +_heapq.so ??? (???) <22FEED03-4F6C-2499-DC3B-952791344ABD> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_heapq.so
0x100617000 - 0x10061afff +_multiprocessing.so ??? (???) <88934565-4DA9-F2F8-A0A4-66E3A8879267> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_multiprocessing.so
0x10061f000 - 0x10062eff7 +cPickle.so ??? (???) <190F516F-97F6-7258-29D3-F8B23CF04C50> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/cPickle.so
0x100636000 - 0x100637fff +_hashlib.so ??? (???) <609B0E50-C9BD-9B88-9177-FFBAFED033ED> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_hashlib.so
0x10073b000 - 0x100740fff +_json.so ??? (???) <70ACC7E0-56A9-2B65-7370-A11C4B06A13C> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_json.so
0x100745000 - 0x10074afff +array.so ??? (???) <88248C2B-CFF2-71B4-2511-09B994E36CE9> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/array.so
0x100751000 - 0x100758fff +_socket.so ??? (???) <47EC3750-BA57-53BB-8088-8CB89C10AC16> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_socket.so
0x100762000 - 0x100766ff7 +_ssl.so ??? (???) <4936BA04-9ACD-2DAF-56C1-E5F51CBB2BA0> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_ssl.so
0x1007ac000 - 0x1007b1fef +math.so ??? (???)/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/math.so
0x1007b8000 - 0x1007b9fff +_random.so ??? (???) <54585B5D-1999-A6CC-9CEB-34F759F0438F> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_random.so
0x1007bc000 - 0x1007bdff7 +fcntl.so ??? (???)/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/fcntl.so
0x101100000 - 0x101101fff +termios.so ??? (???) <43FCCF9A-C66E-DE5B-0F7D-1028A41F9263> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/termios.so
0x101106000 - 0x101109fff +select.so ??? (???)/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/select.so
0x10110f000 - 0x101124fff +_io.so ??? (???) <7A9EA5F2-75D9-F13A-7FDB-AD6841880B07> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_io.so
0x10113b000 - 0x10113bfff +grp.so ??? (???) <9133BC7F-65D3-5CFB-ACCC-8F1F9478FF2E> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/grp.so
0x10117e000 - 0x10117efff +_scproxy.so ??? (???) <89155F35-5A65-8AF1-BC1B-5208151D0B68> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_scproxy.so
0x1011c1000 - 0x1011c7fff +_d2xx.so ??? (???) <2FFBED77-5D30-989A-078F-5CCC3625F613> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/d2xx/_d2xx.so
0x1011cc000 - 0x1011e8ff7 +libftd2xx.1.0.4.dylib 1.0.4 (compatibility 0.1.0) <1A36F49C-F006-F267-F680-2C1E6354C852> /usr/local/lib/libftd2xx.1.0.4.dylib
0x101500000 - 0x101594fff +unicodedata.so ??? (???)/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/unicodedata.so
0x1015eb000 - 0x1015f4ff7 +libusb-1.0.dylib ??? (???) <6715990C-3A0B-43AA-E976-2231B3569F67> /usr/local/lib/libusb-1.0.dylib
0x102780000 - 0x102796fff +_ctypes.so ??? (???)/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_ctypes.so
0x7fff5fc00000 - 0x7fff5fc3bdef dyld 132.1 (???) <472D950D-70F8-B810-A959-9184C2AA6C74> /usr/lib/dyld
0x7fff80750000 - 0x7fff80754ff7 libmathCommon.A.dylib 315.0.0 (compatibility 1.0.0) <95718673-FEEE-B6ED-B127-BCDBDB60D4E5> /usr/lib/system/libmathCommon.A.dylib
0x7fff80773000 - 0x7fff807b0ff7 libssl.0.9.8.dylib 0.9.8 (compatibility 0.9.8)/usr/lib/libssl.0.9.8.dylib
0x7fff80893000 - 0x7fff809b2fe7 libcrypto.0.9.8.dylib 0.9.8 (compatibility 0.9.8) <14115D29-432B-CF02-6B24-A60CC533A09E> /usr/lib/libcrypto.0.9.8.dylib
0x7fff81078000 - 0x7fff8112eff7 libobjc.A.dylib 227.0.0 (compatibility 1.0.0) <03140531-3B2D-1EBA-DA7F-E12CC8F63969> /usr/lib/libobjc.A.dylib
0x7fff81b02000 - 0x7fff81c79fe7 com.apple.CoreFoundation 6.6.6 (550.44)/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff83170000 - 0x7fff83181ff7 libz.1.dylib 1.2.3 (compatibility 1.0.0)/usr/lib/libz.1.dylib
0x7fff84f86000 - 0x7fff84fe6fe7 com.apple.framework.IOKit 2.0 (???) <4F071EF0-8260-01E9-C641-830E582FA416> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x7fff84fe7000 - 0x7fff851a8fef libSystem.B.dylib 125.2.11 (compatibility 1.0.0) <9AB4F1D1-89DC-0E8A-DC8E-A4FE4D69DB69> /usr/lib/libSystem.B.dylib
0x7fff8591e000 - 0x7fff8595ffff com.apple.SystemConfiguration 1.10.8 (1.10.2) <78D48D27-A9C4-62CA-2803-D0BBED82855A> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
0x7fff85a1a000 - 0x7fff85a97fef libstdc++.6.dylib 7.9.0 (compatibility 7.0.0) <35ECA411-2C08-FD7D-11B1-1B7A04921A5C> /usr/lib/libstdc++.6.dylib
0x7fff8637c000 - 0x7fff8637dff7 com.apple.TrustEvaluationAgent 1.1 (1) <74800EE8-C14C-18C9-C208-20BBDB982D40> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent
0x7fff88235000 - 0x7fff88281fff libauto.dylib ??? (???)/usr/lib/libauto.dylib
0x7fff882cc000 - 0x7fff882daff7 libkxld.dylib ??? (???) <8145A534-95CC-9F3C-B78B-AC9898F38C6F> /usr/lib/system/libkxld.dylib
0x7fff89145000 - 0x7fff89303fff libicucore.A.dylib 40.0.0 (compatibility 1.0.0) <4274FC73-A257-3A56-4293-5968F3428854> /usr/lib/libicucore.A.dylib
0x7fffffe00000 - 0x7fffffe01fff libSystem.B.dylib ??? (???) <9AB4F1D1-89DC-0E8A-DC8E-A4FE4D69DB69> /usr/lib/libSystem.B.dylib
Model: iMac11,3, BootROM IM112.0057.B00, 4 processors, Intel Core i7, 2.93 GHz, 12 GB, SMC 1.59f2
Graphics: ATI Radeon HD 5750, ATI Radeon HD 5750, PCIe, 1024 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x8F), Atheros 9280: 2.1.14.6
Bluetooth: Version 2.4.5f3, 2 service, 19 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: OPTIARC DVD RW AD-5680H
Serial ATA Device: APPLE SSD TS256B, 233.76 GB
USB Device: Hub, 0x0424 (SMSC), 0x2514, 0xfa100000 / 2
USB Device: Internal Memory Card Reader, 0x05ac (Apple Inc.), 0x8403, 0xfa120000 / 4
USB Device: USB 2.0 Hub [MTT], 0x1a40 (TERMINUS TECHNOLOGY INC.), 0x0201, 0xfa130000 / 6
USB Device: FT232R USB UART, 0x0403 (Future Technology Devices International Limited), 0x6001, 0xfa136000 / 12
USB Device: FT232R USB UART, 0x0403 (Future Technology Devices International Limited), 0x6001, 0xfa135000 / 11
USB Device: USB 2.0 Hub, 0x1a40 (TERMINUS TECHNOLOGY INC.), 0x0101, 0xfa137000 / 10
USB Device: USB-Serial Controller D, 0x067b (Prolific Technology, Inc.), 0x2303, 0xfa132000 / 9
USB Device: USB-Serial Controller D, 0x067b (Prolific Technology, Inc.), 0x2303, 0xfa131000 / 8
USB Device: Keyboard Hub, 0x05ac (Apple Inc.), 0x1006, 0xfa140000 / 5
USB Device: Apple Keyboard, 0x05ac (Apple Inc.), 0x0220, 0xfa142000 / 13
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 3
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8215, 0xfa111000 / 7
USB Device: Hub, 0x0424 (SMSC), 0x2514, 0xfd100000 / 2
USB Device: iPhone, 0x05ac (Apple Inc.), 0x1297, 0xfd140000 / 5
USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0xfd120000 / 3
USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8502, 0xfd110000 / 4
Try the testing branch. It seems to fix that error.
Switching to the test branch fixed the int/iterate error. Running perfectly now, thanks.
On a separate note I wanted to mention an observation and see if anyone else is noticing the same behavior. It seems that mixing different flavor FPGAs in a single instance of MPBM has will cause more frequent invalids across all FPGAs for both version 0.0.4a and 0.1.0b. If I separate the x6500s from Icarus units and run each in it's own instance of MPBM, I get significantly fewer invalids. I know ngzhang had mentioned that Icarus had some minor protocol bugs that account for some invalids, but the x6500s really seem to highlight the problem. If I run them alone, I can run the 200mhz bitstream for 24+ hours with 0 invalids, but if I add some Icarus units to the same config, the x6500s start throwing intermittent invalids ( %0.3-%0.8 ) and the Icarus units seem to throw a greater amount. Has anyone noticed similar behavior?
I haven't yet tried running 2 instances of version 0.1.0b and I wanted to ask where to specify the log/monitoring port for a second instance. I didn't see any reference to the port in the config file.
I have no explanation for that kind of behavior. A couple more stales maybe, but invalids just don't make sense. I'm tempted to blame variance...
To run multiple v0.1.x instances, start up one instance and move its WebUI to a different port number in its frontend settings. Then start another one, etc.
Using the testing branch, I get this error on my Mac:
Any ideas?
Quote
2012-04-09 17:26:20.918 [100] X6500 worker - AH00WI18: Traceback (most recent call last):
File "/Users/charlie/Modular-Python-Bitcoin-Miner/modules/fpgamining/x6500/x6500worker.py", line 208, in main
data = self.rxconn.recv()
EOFError
File "/Users/charlie/Modular-Python-Bitcoin-Miner/modules/fpgamining/x6500/x6500worker.py", line 208, in main
data = self.rxconn.recv()
EOFError
Any ideas?
The real error message is probably a couple of lines above that.
This one just means that the board proxy connection closed unexpectedly. The proxy should have reported an error before dying.
Try the testing branch. It seems to fix that error.
Switching to the test branch fixed the int/iterate error. Running perfectly now, thanks.
On a separate note I wanted to mention an observation and see if anyone else is noticing the same behavior. It seems that mixing different flavor FPGAs in a single instance of MPBM has will cause more frequent invalids across all FPGAs for both version 0.0.4a and 0.1.0b. If I separate the x6500s from Icarus units and run each in it's own instance of MPBM, I get significantly fewer invalids. I know ngzhang had mentioned that Icarus had some minor protocol bugs that account for some invalids, but the x6500s really seem to highlight the problem. If I run them alone, I can run the 200mhz bitstream for 24+ hours with 0 invalids, but if I add some Icarus units to the same config, the x6500s start throwing intermittent invalids ( %0.3-%0.8 ) and the Icarus units seem to throw a greater amount. Has anyone noticed similar behavior?
I haven't yet tried running 2 instances of version 0.1.0b
Using the testing branch, I get this error on my Mac:
Any ideas?
Quote
2012-04-09 17:26:20.918 [100] X6500 worker - AH00WI18: Traceback (most recent call last):
File "/Users/charlie/Modular-Python-Bitcoin-Miner/modules/fpgamining/x6500/x6500worker.py", line 208, in main
data = self.rxconn.recv()
EOFError
File "/Users/charlie/Modular-Python-Bitcoin-Miner/modules/fpgamining/x6500/x6500worker.py", line 208, in main
data = self.rxconn.recv()
EOFError
Any ideas?
X6500 board A40146TT: Proxy: Exception caught: Traceback (most recent call last):
File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\boardproxy.py", line 77, in run
else: self.device = FT232R(FT232R_PyUSB(self.serial, self.takeover))
File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\util\ft232r.py", line 346, in __init__
raise Exception("Can not open the specified device, possibly because it is already in use")
Exception: Can not open the specified device, possibly because it is already in use
2012-04-09 15:16:51.118 [100] X6500 board A40146TT: Traceback (most recent call last):
File "C:\Users\Desktop\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\x6500worker.py", line 211, in main
elif data[0] == "dying": raise Exception("Proxy died!")
Exception: Proxy died!
I get this error on two of my boards. The rest work fine. Not sure why.
File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\boardproxy.py", line 77, in run
else: self.device = FT232R(FT232R_PyUSB(self.serial, self.takeover))
File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\util\ft232r.py", line 346, in __init__
raise Exception("Can not open the specified device, possibly because it is already in use")
Exception: Can not open the specified device, possibly because it is already in use
2012-04-09 15:16:51.118 [100] X6500 board A40146TT: Traceback (most recent call last):
File "C:\Users\Desktop\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\x6500worker.py", line 211, in main
elif data[0] == "dying": raise Exception("Proxy died!")
Exception: Proxy died!
I get this error on two of my boards. The rest work fine. Not sure why.
This might also be a remnant of a previously running MPBM instance that didn't shut down all board proxys properly (e.g. because they were uploading a bitstream when MPBM was shutting down). You might want to look for stray python processes and kill them.
X6500 board A40146TT: Proxy: Exception caught: Traceback (most recent call last):
File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\boardproxy.py", line 77, in run
else: self.device = FT232R(FT232R_PyUSB(self.serial, self.takeover))
File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\util\ft232r.py", line 346, in __init__
raise Exception("Can not open the specified device, possibly because it is already in use")
Exception: Can not open the specified device, possibly because it is already in use
2012-04-09 15:16:51.118 [100] X6500 board A40146TT: Traceback (most recent call last):
File "C:\Users\Desktop\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\x6500worker.py", line 211, in main
elif data[0] == "dying": raise Exception("Proxy died!")
Exception: Proxy died!
I get this error on two of my boards. The rest work fine. Not sure why.
File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\boardproxy.py", line 77, in run
else: self.device = FT232R(FT232R_PyUSB(self.serial, self.takeover))
File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\util\ft232r.py", line 346, in __init__
raise Exception("Can not open the specified device, possibly because it is already in use")
Exception: Can not open the specified device, possibly because it is already in use
2012-04-09 15:16:51.118 [100] X6500 board A40146TT: Traceback (most recent call last):
File "C:\Users\Desktop\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\x6500worker.py", line 211, in main
elif data[0] == "dying": raise Exception("Proxy died!")
Exception: Proxy died!
I get this error on two of my boards. The rest work fine. Not sure why.
I think this is the error you get when the USB interface was not properly closed by MPBM. Try checking "Reset board if it appears to be in use" under the worker config, then right click the worker and click Restart Worker.
All my boards all work fine on 0.4a. I will try this. Thanks.
X6500 board A40146TT: Proxy: Exception caught: Traceback (most recent call last):
File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\boardproxy.py", line 77, in run
else: self.device = FT232R(FT232R_PyUSB(self.serial, self.takeover))
File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\util\ft232r.py", line 346, in __init__
raise Exception("Can not open the specified device, possibly because it is already in use")
Exception: Can not open the specified device, possibly because it is already in use
2012-04-09 15:16:51.118 [100] X6500 board A40146TT: Traceback (most recent call last):
File "C:\Users\Desktop\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\x6500worker.py", line 211, in main
elif data[0] == "dying": raise Exception("Proxy died!")
Exception: Proxy died!
I get this error on two of my boards. The rest work fine. Not sure why.
File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\boardproxy.py", line 77, in run
else: self.device = FT232R(FT232R_PyUSB(self.serial, self.takeover))
File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\util\ft232r.py", line 346, in __init__
raise Exception("Can not open the specified device, possibly because it is already in use")
Exception: Can not open the specified device, possibly because it is already in use
2012-04-09 15:16:51.118 [100] X6500 board A40146TT: Traceback (most recent call last):
File "C:\Users\Desktop\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\x6500worker.py", line 211, in main
elif data[0] == "dying": raise Exception("Proxy died!")
Exception: Proxy died!
I get this error on two of my boards. The rest work fine. Not sure why.
I think this is the error you get when the USB interface was not properly closed by MPBM. Try checking "Reset board if it appears to be in use" under the worker config, then right click the worker and click Restart Worker.
X6500 board A40146TT: Proxy: Exception caught: Traceback (most recent call last):
File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\boardproxy.py", line 77, in run
else: self.device = FT232R(FT232R_PyUSB(self.serial, self.takeover))
File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\util\ft232r.py", line 346, in __init__
raise Exception("Can not open the specified device, possibly because it is already in use")
Exception: Can not open the specified device, possibly because it is already in use
2012-04-09 15:16:51.118 [100] X6500 board A40146TT: Traceback (most recent call last):
File "C:\Users\Desktop\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\x6500worker.py", line 211, in main
elif data[0] == "dying": raise Exception("Proxy died!")
Exception: Proxy died!
I get this error on two of my boards. The rest work fine. Not sure why.
File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\boardproxy.py", line 77, in run
else: self.device = FT232R(FT232R_PyUSB(self.serial, self.takeover))
File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\util\ft232r.py", line 346, in __init__
raise Exception("Can not open the specified device, possibly because it is already in use")
Exception: Can not open the specified device, possibly because it is already in use
2012-04-09 15:16:51.118 [100] X6500 board A40146TT: Traceback (most recent call last):
File "C:\Users\Desktop\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\x6500worker.py", line 211, in main
elif data[0] == "dying": raise Exception("Proxy died!")
Exception: Proxy died!
I get this error on two of my boards. The rest work fine. Not sure why.
Make a new directory and do a
Then try running it from there. Remember to copy over a bitstream and your config.
Code:
git clone -b testing https://github.com/TheSeven/Modular-Python-Bitcoin-Miner.git
Then try running it from there. Remember to copy over a bitstream and your config.
Try the testing branch. It seems to fix that error.
Yes, I'm not sure about the details of the error, but the testing branch has a fix for this bug already. If you're running from a git clone, just run
Code:
git checkout testing
then restart MPBM.
I hope that fixes coblee and coretechs' problems! I'm sure TheSeven can explain the problem tomorrow, but he's asleep right now.
After getting the testing branch
Code:
git checkout origin/testing
Code:
X6500 worker - AH00WI18: Traceback (most recent call last):
File "/Users/charlie/Modular-Python-Bitcoin-Miner/modules/fpgamining/x6500/x6500worker.py", line 208, in main
data = self.rxconn.recv()
EOFError
Try the testing branch. It seems to fix that error.
Yes, I'm not sure about the details of the error, but the testing branch has a fix for this bug already. If you're running from a git clone, just run
Code:
git checkout testing
then restart MPBM.
I hope that fixes coblee and coretechs' problems! I'm sure TheSeven can explain the problem tomorrow, but he's asleep right now.
Try the testing branch. It seems to fix that error.
Jump to: