Modular Python Bitcoin Miner - Official Thread - page 8.

coretechs

donator

Activity: 362

Merit: 250

I'm still having issues with 0.1.0beta on linux (fresh install, ubuntu 64-bit) as well. I was able to get it to the point where it loads the firmware on all the boards, but as soon as it hits 100% and completes it throws the following error and restarts the firmware load:

Code:

2012-04-08 23:40:17.763066 [100]: X6500 board AH00WOWB: Proxy: Exception caught: Traceback (most recent call last):
  File "/home/xxxxx/Modular-Python-Bitcoin-Miner/modules/fpgamining/x6500/boardproxy.py", line 123, in run
    if self.error: raise self.error
TypeError: 'int' object is not iterable
2012-04-08 23:40:17.765450 [100]: X6500 board AH00WOWB: Traceback (most recent call last):
  File "/home/xxxxx/Modular-Python-Bitcoin-Miner/modules/fpgamining/x6500/x6500worker.py", line 212, in main
    elif data[0] == "dying": raise Exception("Proxy died!")
Exception: Proxy died!

I have no problems running the same version with the x6500s on windows. I've tried using the worker and the hotplug worker using the linux install steps on fpgamining.com with no luck. All the boards detect and load the firmware, then error and repeat.

coblee

donator

Activity: 1654

Merit: 1351

Creator of Litecoin. Cryptocurrency enthusiast.

I just got latest code and everything stopped working. I couldn't get either my x6500 or my Icarus working. I'm getting the proxy died error for x6500 and "device reports readiness to read but returned no data (device disconnected?)" on my Icarus.

This is quite frustrating. Anyway I can switch back to the previous version?

I'm running this on my Mac. Python 2.7.2.

Garr255

legendary

Activity: 938

Merit: 1000

What's a GPU?

Quote from: hashking on April 07, 2012, 08:05:25 AM

Anyone using the program to work with GPUMAX. I can't get mine to connect. What are your settings for source?

I haven't tried it yet, but when I do I'll post back here.

TheSeven

hero member

Activity: 504

Merit: 500

FPGA Mining LLC

Quote from: hashking on April 07, 2012, 08:05:25 AM

Anyone using the program to work with GPUMAX. I can't get mine to connect. What are your settings for source?

I didn't get a GPUMAX invite yet, so I can't tell you the exact configuration, but other people said it's pretty much straightforward.

hashking

sr. member

Activity: 308

Merit: 250

Anyone using the program to work with GPUMAX. I can't get mine to connect. What are your settings for source?

TheSeven

hero member

Activity: 504

Merit: 500

FPGA Mining LLC

Quote from: freshzive on April 06, 2012, 10:40:57 AM

Any idea what causes this? It seems to crash python.

Code:

2012-04-06 08:40:00.470180 [100]: Core: Starting up...
2012-04-06 08:40:00.490875 [200]: Core: Startup completed
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.

Edit: It actually starts up, but all of my x6500s show this:

Code:

X6500 board AH00WOVX: Proxy: Exception caught: Traceback (most recent call last):
  File "/Users/christian/modular/modules/fpgamining/x6500/boardproxy.py", line 77, in run
    else: self.device = FT232R(FT232R_PyUSB(self.serial, self.takeover))
  File "/Users/christian/modular/modules/fpgamining/x6500/util/ft232r.py", line 315, in __init__
    for bus in usb.busses():
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/legacy.py", line 333, in busses
    return (Bus(),)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/legacy.py", line 329, in __init__
    self.devices = [Device(d) for d in core.find(find_all=True)]
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/core.py", line 851, in find
    return [d for d in device_iter(k, v)]
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/core.py", line 821, in device_iter
    for dev in backend.enumerate_devices():
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/backend/libusb10.py", line 457, in enumerate_devices
    return _DevIterator()
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/backend/libusb10.py", line 445, in __init__
    byref(self.dev_list))
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/backend/libusb10.py", line 403, in _check
    raise USBError(_str_error[ret], ret, _libusb_errno[ret])
USBError: [Errno None] Unknown error
2012-04-06 08:45:34.453529 [100]: X6500 board AH00WOVX: Traceback (most recent call last):
  File "/Users/christian/modular/modules/fpgamining/x6500/x6500worker.py", line 212, in main
    elif data[0] == "dying": raise Exception("Proxy died!")
Exception: Proxy died!

I take it the ztex200mhz file doesn't work? I tried loading firmware using program.py and still get these errors on all devices. This is on Mac OS X with Python 2.7.2

Now that's very odd. Haven't seen something like this before.
Which python/pyusb/libusb version is showing that behavior?

freshzive

sr. member

Activity: 447

Merit: 250

Any idea what causes this? It seems to crash python.

Code:

2012-04-06 08:40:00.470180 [100]: Core: Starting up...
2012-04-06 08:40:00.490875 [200]: Core: Startup completed
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.

Edit: It actually starts up, but all of my x6500s show this:

Code:

X6500 board AH00WOVX: Proxy: Exception caught: Traceback (most recent call last):
  File "/Users/christian/modular/modules/fpgamining/x6500/boardproxy.py", line 77, in run
    else: self.device = FT232R(FT232R_PyUSB(self.serial, self.takeover))
  File "/Users/christian/modular/modules/fpgamining/x6500/util/ft232r.py", line 315, in __init__
    for bus in usb.busses():
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/legacy.py", line 333, in busses
    return (Bus(),)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/legacy.py", line 329, in __init__
    self.devices = [Device(d) for d in core.find(find_all=True)]
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/core.py", line 851, in find
    return [d for d in device_iter(k, v)]
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/core.py", line 821, in device_iter
    for dev in backend.enumerate_devices():
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/backend/libusb10.py", line 457, in enumerate_devices
    return _DevIterator()
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/backend/libusb10.py", line 445, in __init__
    byref(self.dev_list))
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/backend/libusb10.py", line 403, in _check
    raise USBError(_str_error[ret], ret, _libusb_errno[ret])
USBError: [Errno None] Unknown error
2012-04-06 08:45:34.453529 [100]: X6500 board AH00WOVX: Traceback (most recent call last):
  File "/Users/christian/modular/modules/fpgamining/x6500/x6500worker.py", line 212, in main
    elif data[0] == "dying": raise Exception("Proxy died!")
Exception: Proxy died!

I take it the ztex200mhz file doesn't work? I tried loading firmware using program.py and still get these errors on all devices. This is on Mac OS X with Python 2.7.2

TheSeven

hero member

Activity: 504

Merit: 500

FPGA Mining LLC

Quote from: allinvain on April 06, 2012, 12:35:13 AM

TheSeven, any ideas when we can expect a non beta release?

When enough people have tested it and we can consider it bug-free. Oh, the UI also still needs some improvements (IE/firefox/opera compatibility, highlighting in the stats table to make that more readable, description tooltips for some elements, ...), and it should also be documented better.

There are currently some experimental fixes and improvements in the testing branch, which I'd like to apply to master soon. This version has been running for like a week here without any issues, however I might have broken compatibility with some python/pyusb version and board type combinations by accident, so some more people should test this.

BTW, a non-beta of 0.0.x was never released, and I'd say that 0.1.0beta should outperform that on most aspects.

TheSeven

hero member

Activity: 504

Merit: 500

FPGA Mining LLC

Quote from: freshzive on April 05, 2012, 11:35:42 PM

Is this version working properly with p2pool (using x6500s)? Just wanted to make sure before I upgrade from that pesky v0.0.4alpha

While x6500 generally isn't the board that's best-suited for p2pool (but it should work reasonably well, 1-2% DoA unless your host PC is overloaded), there should not be much difference between the MPBM versions left. While 0.0.x might have generally lower latencies due to less complexity, 0.1.x has added a couple of optimizations, which seem to more than outweigh that.

That said, I'm currently running MPBM 0.1.0beta on an Icarus and I'm getting like 0.8-0.9% DoA, ~5% stales total, so that's >100% efficiency, even though p2pool isn't running on the same host.

allinvain

legendary

Activity: 3080

Merit: 1080

TheSeven, any ideas when we can expect a non beta release?

freshzive

sr. member

Activity: 447

Merit: 250

Is this version working properly with p2pool (using x6500s)? Just wanted to make sure before I upgrade from that pesky v0.0.4alpha

TheSeven

hero member

Activity: 504

Merit: 500

FPGA Mining LLC

Quote from: hashking on April 03, 2012, 08:53:52 PM

Which pools is this program optimized for?

Well, basically anything except for pools that don't comply to the usual JSON-RPC protocol or do some other weird things like ozcoin.

Garr255

legendary

Activity: 938

Merit: 1000

What's a GPU?

Hey all,

I've been having a terrible time getting some x6500s running. I've tried everything under Ubuntu 10.10, XP, and 7. I spend a night on IRC with a few people but with no success. (Thanks for your effort anyway!)

My current error under a clean install of Ubuntu 10.10 with proper drivers, python-usb, etc installed:

http://pastebin.com/Mm0stxux

I really hope this gets resolved soon! Thanks.

Turns out it was a PSU activation method error (OK to ON instead of ON to ground). Derp.

-Garrett

hashking

sr. member

Activity: 308

Merit: 250

Which pools is this program optimized for?

BR0KK

hero member

Activity: 784

Merit: 500

Uhh Licensing; thats complicated....Hope that you can arrange something with Ztex. If u need Accesss to a board sometimes just ask

TheSeven

hero member

Activity: 504

Merit: 500

FPGA Mining LLC

Quote from: BR0KK on April 03, 2012, 01:29:44 PM

Hi im not home but in 3 Days we could arrange the Remote Access to all of my boards if you want

I don't think it will help much right now. I've identified at least one problem, which I can only really fix after sorting out licensing issues with ztex.

BR0KK

hero member

Activity: 784

Merit: 500

Hi im not home but in 3 Days we could arrange the Remote Access to all of my boards if you want

TheSeven

hero member

Activity: 504

Merit: 500

FPGA Mining LLC

Clone my git (testing branch if you want to try the latest greatest, risking that it might break from time to time)
With the boards you want it to use plugged, run run-mpbm.py, it should autodetect them unless they are Icarus boards
http://localhost:8832 (user: admin, password: mpbm)
Add your pools to the "User work sources" group
Right-click on them and assign them to the right blockchain

hashking

sr. member

Activity: 308

Merit: 250

I have the version .4a for windows. How can I install the new version..

TheSeven

hero member

Activity: 504

Merit: 500

FPGA Mining LLC

I had a closer look at the Ztex issues: Seems like there's some bitswapping that needs to be done so that the boards understand it.
This will however take ages if implemented in Python, so I'd prefer to distribute pre-swapped firmware files.
Sounds like I'll have to work out some licensing issues with Stefan...

For those keen on doing it themselves:
- Extract the bit file from the btcminer jar file
- There should be a couple 0xFFs in the first few hundred bytes.
- Reverse the bits of each byte starting from there, i.e. bit 0 swapped with bit 7, bit 1 swapped with bit 6, ...
- MPBM should accept the resulting firmware file

Topic: Modular Python Bitcoin Miner - Official Thread - page 8. (Read 74184 times)