|
Title: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 06, 2012, 04:10:15 PM The Modular Python Bitcoin Miner is a very flexible mining software written in Python, aiming to unify the frontend of FPGA-based mining hardware. Features
Supported devices
Screenshots https://i.imgur.com/jBi2a.png?1 (https://i.imgur.com/jBi2a.png) News
Documentation / Howtos
Download / Source code
IRC channel
Donations
[/list] Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 06, 2012, 04:10:37 PM <placeholder>
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: shad on February 06, 2012, 06:27:52 PM so without the D2xx-drivers we could get this thing running on OpenWRT?
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 06, 2012, 06:42:53 PM so without the D2xx-drivers we could get this thing running on OpenWRT? That depends on:
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: O_Shovah on February 06, 2012, 08:01:02 PM Is there a more detailed description for setting the scripts up avaidable ?
I tried running it on my linux maschine but i keep getting errors for a common file. I guess my Pm to you dindn't reach you. Seems to be unreliable lately. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: thirdlight on February 06, 2012, 08:36:05 PM I'm using windows xp & getting
Code: 2012-02-06 20:23:21.406000: Traceback (most recent call last): The terminal window is blank. Am I missing something? Thanks Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: torusJKL on February 06, 2012, 08:49:52 PM Looks great.
Thanks for sharing. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 06, 2012, 08:59:11 PM I'm using windows xp & getting That sounds like you're using Python <2.7 to me. Only 2.7 and 3.x is supported.Code: 2012-02-06 20:23:21.406000: Traceback (most recent call last): @O_Shovah: I've responded to your PM now... Looks like common.py is missing for some reason? (I have no idea why...) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: kronosvl on February 06, 2012, 09:40:27 PM Sub'd same here, specially openWRT oportunityTitle: Re: Modular Python Bitcoin Miner - Official Thread Post by: thirdlight on February 06, 2012, 09:47:54 PM That sounds like you're using Python <2.7 to me. Only 2.7 and 3.x is supported. Yes, 2.6.7 as standard for X6500.I tried 2.7, log has: Code: 2012-02-06 21:45:41.750000: Exception in thread X6500 hotplug controller_main: How do I get usb module? Thanks Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 06, 2012, 09:59:57 PM That sounds like you're using Python <2.7 to me. Only 2.7 and 3.x is supported. Yes, 2.6.7 as standard for X6500.I tried 2.7, log has: Code: 2012-02-06 21:45:41.750000: Exception in thread X6500 hotplug controller_main: How do I get usb module? Thanks http://sourceforge.net/projects/pyusb/files/PyUSB%201.0/1.0.0-alpha-2/pyusb-1.0.0a2.zip/download you can just unpack the "usb" directory from that zip file into the mpbm directory, or install it system-wide using setup.py Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: bitcowok on February 07, 2012, 02:48:53 AM Hi.
Looking really good! Couple problems with v0.0.4alpha that I can see: 1) curses line characters are all messed up in my locale (en_AU.UTF-8) (let me know if you want a screenshot) 2) I'm getting "Invalid long polling URL for Slushies: http://api.bitcoin.cz:8410" Thanks for this work, i'm loving the idea of one program to run ALL the FPGA's. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coblee on February 07, 2012, 04:27:10 AM I'm getting this error:
Code: 2012-02-06 20:25:26.472938: X6500 board AH00WOWD: No backend available Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: LazarusLong on February 07, 2012, 08:27:54 AM I was working on a port with libftdi to replace the d2xx lib - it did not work, some bits in the data streams differ.
Great work! I really need this stuff on openwrt... ;D Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: thirdlight on February 07, 2012, 08:37:58 AM you can just unpack the "usb" directory from that zip file ... Thanks, TheSeven. I bet you underestimated the level of hand-holding some users need! Now getting: Code: 2012-02-07 08:34:53.468000: Caught exception: No backend available Not getting quite as far as coblee, as no board serial detected? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coblee on February 07, 2012, 09:25:38 AM Well, I put the serial in the config.py myself:
Code: # Single X6500 worker Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 07, 2012, 12:07:40 PM Hi. Looking really good! Couple problems with v0.0.4alpha that I can see: 1) curses line characters are all messed up in my locale (en_AU.UTF-8) (let me know if you want a screenshot) 2) I'm getting "Invalid long polling URL for Slushies: http://api.bitcoin.cz:8410" Thanks for this work, i'm loving the idea of one program to run ALL the FPGA's. 1) might be curses not properly detecting your terminal type. Running it inside a screen session sometimes helps with this. If you're using PuTTY as a terminal, make sure to set its charset to UTF-8. 2) MPBM probably expects a trailing slash here... I'll fix that later today. I'm getting this error: Code: 2012-02-06 20:25:26.472938: X6500 board AH00WOWD: No backend available you can just unpack the "usb" directory from that zip file ... Thanks, TheSeven. I bet you underestimated the level of hand-holding some users need! Now getting: Code: 2012-02-07 08:34:53.468000: Caught exception: No backend available Not getting quite as far as coblee, as no board serial detected? Sounds like you don't have libusb installed or a weird version of it. Well, I put the serial in the config.py myself: Code: # Single X6500 worker If that works, autodetecting should have worked as well. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 07, 2012, 12:25:01 PM 2) I'm getting "Invalid long polling URL for Slushies: http://api.bitcoin.cz:8410" Fixed :) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 07, 2012, 12:41:33 PM I'm using windows xp & getting Code: 2012-02-06 20:23:21.406000: Traceback (most recent call last): MPBM should now be compatible with Python 2.6 as well. Thanks to LazarusLong for providing the patch :) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: thirdlight on February 07, 2012, 04:58:53 PM I've had mpbm working using "useftd2xx":"true" and python 2.6.7.
It saw all the boards, but couldn't "open" all of them. Seemed to be getting shares, pool reported widely varying hashrate. The terminal window has a message about "window too small" so no stats to relay. Froze around an hour later, no reason in the log. I like that it manages (or tries to) all the boards at once - much neater than multiple windows. I will persevere. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: thirdlight on February 07, 2012, 06:16:07 PM So I've found & installed libusb-win32. This has stopped the other X6500 software from working.
mpbm programs all boards, but then: Code: 2012-02-07 18:04:08.375000: X6500 board AH00WOW1: Error while booting board: Traceback (most recent call last): ??? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 07, 2012, 06:26:07 PM I've had mpbm working using "useftd2xx":"true" and python 2.6.7. It saw all the boards, but couldn't "open" all of them. Seemed to be getting shares, pool reported widely varying hashrate. The terminal window has a message about "window too small" so no stats to relay. Froze around an hour later, no reason in the log. I like that it manages (or tries to) all the boards at once - much neater than multiple windows. I will persevere. ftd2xx has a couple of issues, especially that boards can get stuck if a miner software doesn't terminate cleanly. Most likely the reason for some of your boards to not be recognized correctly. Window too small means exactly what it says, those rather huge stats tables need like 150 chars of width. What were the last log messages before it froze? So I've found & installed libusb-win32. This has stopped the other X6500 software from working. mpbm programs all boards, but then: Code: 2012-02-07 18:04:08.375000: X6500 board AH00WOW1: Error while booting board: Traceback (most recent call last): ??? Damn, I overlooked that one during a rework. Has been fixed this very moment. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: thirdlight on February 07, 2012, 07:26:14 PM Damn, I overlooked that one during a rework. Has been fixed this very moment. Pulled, programs & mines on all boards except one:Code: 2012-02-07 19:12:04.062000: X6500 board AH00WLON: 99.2% complete [30 kB/s] [0s remaining] After 10 mins or so, it's finally succeded! +1 that it keeps on trying! Found out how to increase the window size (presumably everyone else knows to make a shortcut to the .bat file and change the size in the layout tab of the shortcut's properties). Wow. Lots of stats! So pleased this is working, as I can't go back... Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 07, 2012, 07:45:47 PM Damn, I overlooked that one during a rework. Has been fixed this very moment. Pulled, programs & mines on all boards except one:Code: 2012-02-07 19:12:04.062000: X6500 board AH00WLON: 99.2% complete [30 kB/s] [0s remaining] After 10 mins or so, it's finally succeded! +1 that it keeps on trying! Found out how to increase the window size (presumably everyone else knows to make a shortcut to the .bat file and change the size in the layout tab of the shortcut's properties). Wow. Lots of stats! So pleased this is working, as I can't go back... I think I know what was going and I'll have a look into avoiding that... Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: shad on February 07, 2012, 07:47:59 PM i am running it on an Buffalo WRZ-HP-AG300H-EU, it uses around 40MB-Ram openwrt+miner
(i didn't get it running on my linksys wrt54gl because of to few diskspace) installation on OpenWRT Quote opkg update opkg install phyton opkg install libncurses opkg install libncursesw opkg install libusb rmmod ftdi_sio python miner.py bitstream was already installed, will try installing bitstream over openwrt later Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: thirdlight on February 07, 2012, 08:14:05 PM i am running it on an Buffalo WRZ-HP-AG300H-EU That's fantastic!Also, I'm mining with fpga's on p2pool. Perfect! Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: shad on February 07, 2012, 08:44:58 PM i am running it on an Buffalo WRZ-HP-AG300H-EU That's fantastic!Also, I'm mining with fpga's on p2pool. Perfect! i think i have to choose between running on ARM or mining on P2Pool Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 07, 2012, 08:45:27 PM Also, I'm mining with fpga's on p2pool. Perfect! Please be aware that the x6500 has relatively long long poll latencies due to its architecture, which will probably result in extremely high (around 20-50%) stale rates on the (very fast) p2pool network. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: thirdlight on February 07, 2012, 09:01:36 PM i think i have to choose between running on ARM or mining on P2Pool Is that because p2pool won't run on ARM? My fpga controller pc isn't strong enough for p2pool, so I've got it on a vps.extremely high (around 20-50%) stale rates Yes, showing 20% on factory settings currently.Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: shad on February 07, 2012, 09:07:39 PM i think i have to choose between running on ARM or mining on P2Pool Is that because p2pool won't run on ARM? My fpga controller pc isn't strong enough for p2pool, so I've got it on a vps.p2pool will run on arm, but you need a bitcoin-server okay, i think you could be able to compile the bitcoin-server for ARM, you also have to hold the blockchain on the device, maybe with an usb-stick, but when i mined with my celeron 900Mhz on P2Pool, i had connection loses between p2pool and bitcoin because of high system load, i don't think this will run nice on my router Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: bitcowok on February 08, 2012, 03:36:29 AM 1) might be curses not properly detecting your terminal type. Running it inside a screen session sometimes helps with this. If you're using PuTTY as a terminal, make sure to set its charset to UTF-8. 2) MPBM probably expects a trailing slash here... I'll fix that later today. Your fix to (2) is worked, thanks. Its now mining like a champ. Re UTF-8 issues: my first problem was i am using xterm, which needs to be started in utf-8 mode like this: xterm -u8 If i run MPBM within xterm -u8, i get nice pretty graphics. Now when I try to run it within screen (within that xterm -u8), I now get strange characters. (even using screen -U , which forces UTF-8) As a test, running this should result a capital O with circumflex. Code: perl -le 'print "\x{d4}"'And what i'm seeing without screen, and within: http://jabawok.net/uploads/problems/utf-8-screen-problem.png Heres my locale: Code: $ locale so I'm stumped. I'm running it outside of screen for the time being, and its working beautifully, but if anyone has any clues to fix the utf-8 problem i'm having with screen, I'd love to hear them. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coblee on February 08, 2012, 08:24:28 AM I finally got this working by installing libusb (and it does break the x6500 default miner)
This miner is fantastic! It has all the stats that I can think of in a nice layout... color coded as well! Anyone working on an Icarus worker? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 08, 2012, 02:14:11 PM Anyone working on an Icarus worker? I might do that if someone can offer me access to a board for testing. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: freshzive on February 08, 2012, 04:36:59 PM Anyone have this working on a Mac? Before I try setting it up for my x6500 miners, wanted to make sure someone had already tested.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coblee on February 08, 2012, 05:06:07 PM Anyone have this working on a Mac? Before I try setting it up for my x6500 miners, wanted to make sure someone had already tested. Yes, it's working on my Mac. I needed to install these 2: http://sourceforge.net/projects/pyusb/files/PyUSB%201.0/1.0.0-alpha-2/pyusb-1.0.0a2.zip/download http://sourceforge.net/projects/libusb/files/libusb-1.0/libusb-1.0.8/ Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coblee on February 08, 2012, 06:59:04 PM Anyone working on an Icarus worker? I might do that if someone can offer me access to a board for testing. I might be able to do that. What kind of access do you need? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 08, 2012, 11:01:21 PM Anyone working on an Icarus worker? I might do that if someone can offer me access to a board for testing. I might be able to do that. What kind of access do you need? Just ssh into a box that's connected to a board (and the appropriate permissions to access the board's device node) should be sufficient. I'll probably also need some python modules to be installed (the python curses bindings and pyserial), ideally both python 2.7 and 3.x. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 09, 2012, 12:17:28 AM Experimental Icarus board support has been added, thanks a lot to O_Shovah for letting me test it on his board :)
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: ngzhang on February 09, 2012, 11:10:53 AM Experimental Icarus board support has been added, thanks a lot to O_Shovah for letting me test it on his board :) Offering some bitcoins might encourage you to not be lazy :) ;D is there any implementation guide for Icarus? ??? Code: # # Icarus worker Code: C:\project\TheSeven-Modular-Python-Bitcoin-Miner-aef8b23\TheSeven-Modular-Python-Bitcoin-Miner-aef8b23>c:\python27\python.exe miner.py :-[ Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 09, 2012, 02:13:00 PM Code: C:\project\TheSeven-Modular-Python-Bitcoin-Miner-aef8b23\TheSeven-Modular-Python-Bitcoin-Miner-aef8b23>c:\python27\python.exe miner.py :-[ add Code: import worker.theseven.icarus Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: ngzhang on February 09, 2012, 04:10:29 PM i must say, it works and have a very high efficiency.
but the form is a bit strange on my machine. :-[ http://i.minus.com/iHWHV1UdMiZYW.jpg python 2.7.2 and curses 2.2 (AMD64) ??? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: freshzive on February 09, 2012, 04:25:29 PM So does the hotplug not work with multiple x6500s? Or am I doing something wrong? I have 5, it seems like they all connect, but they never start hashing and I keep getting lots of Errno 19 where they disconnect.
https://i.imgur.com/e1eR9.png Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: freshzive on February 09, 2012, 04:30:59 PM Yeah, weird. When I specify them each by serial # it works perfectly.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: thirdlight on February 09, 2012, 04:31:55 PM So does the hotplug not work with multiple x6500s? I have it working with multiple X6500s - on windows, though.Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: freshzive on February 09, 2012, 04:34:51 PM So does the hotplug not work with multiple x6500s? I have it working with multiple X6500s - on windows, though.Yeah, maybe it's my Mac? Also, specifying the serial # in the config does nothing. When using the single x6500 miner, it automatically connects to device 0. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 09, 2012, 05:50:30 PM Are you sure that there's a bitstream running on the FPGAs? If they just get validation job timeouts after 3 minutes that might just be an FPGA that wasn't booted. MPBM won't upload bitstreams unless you instruct it to in the config file.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: freshzive on February 09, 2012, 06:59:29 PM Very sure. I programmed them using the x6500 software. I have all 5 up and running using 5 instances of your software with single x6500....but the hotplug won't work for whatever reason. Any suggestions?
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coblee on February 09, 2012, 07:01:18 PM Very sure. I programmed them using the x6500 software. I have all 5 up and running using 5 instances of your software with single x6500....but the hotplug won't work for whatever reason. Any suggestions? I never got the hotplug working on my Mac either. I got the same error message. So I gave up and just specified the serial and that's been working fine. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 09, 2012, 08:13:09 PM Very sure. I programmed them using the x6500 software. I have all 5 up and running using 5 instances of your software with single x6500....but the hotplug won't work for whatever reason. Any suggestions? No idea how hotplug cannot work if single workers do, that's really weird. They both enumerate all devices on the bus, just that the single worker skips everything where the serial doesn't match, and that hotplug spawns a single worker for every serial that it finds on the bus.But you should be able to just copy the worker definition in the config file for all 5 boards instead of running 5 MPBM instances. That's basically what hotplug would do anyway. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coblee on February 09, 2012, 08:17:59 PM Very sure. I programmed them using the x6500 software. I have all 5 up and running using 5 instances of your software with single x6500....but the hotplug won't work for whatever reason. Any suggestions? No idea how hotplug cannot work if single workers do, that's really weird. They both enumerate all devices on the bus, just that the single worker skips everything where the serial doesn't match, and that hotplug spawns a single worker for every serial that it finds on the bus.But you should be able to just copy the worker definition in the config file for all 5 boards instead of running 5 MPBM instances. That's basically what hotplug would do anyway. I have 2 x6500 workers in a single instance of MPBM on my Mac. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: freshzive on February 09, 2012, 09:02:36 PM Weird, specifying them by serial # doesn't seem to work on my Mac. No matter what serial # I put, it seems to connect to device #0 first. The second instance then connects to device #1, and so on.
Coblee can I see what your config file looks like? Would love to only have 1 instance running. Thanks for all the help :) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coblee on February 09, 2012, 11:31:20 PM Here's the relevant part:
Code: # Single X6500 worker Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coblee on February 09, 2012, 11:33:14 PM When using the icarus worker, if I stop the miner and restart it, the icarus worker will fail to start with this message:
Code: Icarus board on /dev/tty.usbserial: Timeout waiting for validation job to finish It seems like I have to disconnect and reconnect them in order for it to work again. Any ideas? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: freshzive on February 10, 2012, 06:06:02 AM So what's the proper way to specifiy a backup pool? I set my primary pool to a priority of '1000' and the backup to '1', yet my backup pool seems to be getting lots of shares still for some reason...
Thanks for the help coblee, got it running successfully with all 5 x6500s in one instance :) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: finway on February 10, 2012, 07:56:09 AM Mark.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 10, 2012, 08:55:55 AM So what's the proper way to specifiy a backup pool? I set my primary pool to a priority of '1000' and the backup to '1', yet my backup pool seems to be getting lots of shares still for some reason... If your main pool behaves normally this should only happen shortly after starting the miner (or if the backup pool is incredibly lucky).Thanks for the help coblee, got it running successfully with all 5 x6500s in one instance :) I might have to adjust some of the bias values in the default configuration to improve the startup behavior, in order to not confuse people... You might want to try something like these: Code: getworkbias = -3000 If you want it to just distribute hashrate accordingly to the priority/hashrate settings and completely ignore the pool's behavior, use this: Code: getworkbias = -3000 Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: nbtcminer on February 10, 2012, 01:55:00 PM For those with Win x64, where are you getting libusb from?
I'm basically stuck at the x6500 driver; no backend available Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 10, 2012, 02:04:06 PM For those with Win x64, where are you getting libusb from? In theory, building a WinUSB driver for the FTDI should work, libusb can nowadays use WinUSB as a backend.I'm basically stuck at the x6500 driver; no backend available I haven't got around to building such a driver yet though. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on February 10, 2012, 03:49:29 PM Wohoo..got it working. Just a note for those on Win 7 x64. First download and install curses mython module from here:
http://www.lfd.uci.edu/~gohlke/pythonlibs/#curses On a different note, what percent stale shares are you folks seeing? Edit: Whoops, replied to wrong thread. But still relevant. I meant to reply to the Icarus thread. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on February 10, 2012, 04:00:34 PM In regards to this:
"priority": 30, \ I take it the higher the number the higher the priority. And if so what is a recommended priority setting. I'm testing with BTC Guild for example, and I just kept the stock config's 30 level priority. This might be too high?? Could this explain failed job requests? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 10, 2012, 04:45:23 PM The priority values just define how hashrate will be distributed between the pools in the long term. If one pool has two times the priority of another one, it will get twice the hashrate compared to the other one on average. The absolute values don't matter, just the relative differences do. Assuming you have one pool with priority 1000 and another one with 2000 that's the same as if the first one had priority 1 and the second one 2.
This should not make job requests fail, but if a pool has issues, these values do influence MPBM's failover behavior. It is recommended to have at least two pools with similar priority levels (let's say no more than a factor of 2 or 3 apart from each other), otherwise MPBM might try to fetch work from your primary pool too agressively during an outage, causing the work buffer to run empty before it attempts to fetch work from another pool. This is especially important if you use the bias values I have posted above to make it distribute hashrate more evenly, the default values should be a bit more tolerant here (by "punishing" pools a lot harder for failed requests or stales). I'd recommend setting up two (or more) pools with the same priority for load balancing and failover, and if you want to, additionally the demo pool entries (at a lower priority) if you want to donate some hashrate. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on February 10, 2012, 05:01:14 PM Excellent reply. Thanks. I intend to setup more than one, but first I'm waiting for Mr. ngzhang to deliver another fpga board. Right now I have 1 Icarus board mining with your miner. I must admit I'm a big sucker for colored terminals and I find watching the miner's output the equivalent of "seeing into the matrix"
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: nbtcminer on February 10, 2012, 05:41:21 PM Here the steps I've taken so far:
I'm running: Windows 7 64-bit I have: - Python 2.6.7 (32-bit) installed ( - curses-2.2.win32-py2.6.exe (From: http://www.lfd.uci.edu/~gohlke/pythonlibs/#curses) - USB module copied into MPBM folder (http://sourceforge.net/projects/pyusb/files/PyUSB%201.0/1.0.0-alpha-2/pyusb-1.0.0a2.zip/download) - Copied the default_config.py and renamed it to config.py - Setup the serial number for my X6500 and my pool information in the config.py I'm at the point where I need to get libusb (from what I gather) installed. I previous had the FTDI D2XX driver (64bit) installed. Do I need to have the 32-bit drivers installed? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 10, 2012, 06:17:57 PM Here the steps I've taken so far: I'm running: Windows 7 64-bit I have: - Python 2.6.7 (32-bit) installed ( - curses-2.2.win32-py2.6.exe (From: http://www.lfd.uci.edu/~gohlke/pythonlibs/#curses) - USB module copied into MPBM folder (http://sourceforge.net/projects/pyusb/files/PyUSB%201.0/1.0.0-alpha-2/pyusb-1.0.0a2.zip/download) - Copied the default_config.py and renamed it to config.py - Setup the serial number for my X6500 and my pool information in the config.py I'm at the point where I need to get libusb (from what I gather) installed. I previous had the FTDI D2XX driver (64bit) installed. Do I need to have the 32-bit drivers installed? You can only install 64bit drivers on a 64bit OS, and Win7 x64 has mandantory driver signing. You have 4 options:
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: nbtcminer on February 10, 2012, 06:22:37 PM @TheSeven:
Thanks for the quick reply! I might try building my own WinUSB driver inf file (but we'll see how that goes). For now I think the easiest thing to do is to just use the D2XX driver (I want to test your miner over the weekend). Edit: If I wanted to add the FTDI D2xx line would it in: config.py (under the workers section) or \workers\fpgaming\x6500.py Thanks in advance for the help! Cheers! You can only install 64bit drivers on a 64bit OS, and Win7 x64 has mandantory driver signing. You have 4 options:
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 10, 2012, 06:46:49 PM In config.py, like this:
Code: { \See x6500.py for more available config options to be put there. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: nbtcminer on February 10, 2012, 11:36:30 PM @Theseven:
Awesome! I've got it up and running with the D2XX drivers and things look ok so far! However I'm an error that i used to get with the old X6500 as well: Code: Error while requesting job from "pool" timed out Any idea on that one? In config.py, like this: Code: { \See x6500.py for more available config options to be put there. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: freshzive on February 11, 2012, 03:22:02 AM So what's the proper way to specifiy a backup pool? I set my primary pool to a priority of '1000' and the backup to '1', yet my backup pool seems to be getting lots of shares still for some reason... If your main pool behaves normally this should only happen shortly after starting the miner (or if the backup pool is incredibly lucky).Thanks for the help coblee, got it running successfully with all 5 x6500s in one instance :) I might have to adjust some of the bias values in the default configuration to improve the startup behavior, in order to not confuse people... You might want to try something like these: Code: getworkbias = -3000 So I tried this, and it actually seemed to be sending MORE shares to my backup pool than it had previously (this was with priority set to 20 for main and 1 for backup). With the default settings and priorities of 1000 (main) and 1 (backup), it was sending about 100Mh/s of 2000Mh/s total to my backup pool over the course of ~24 hours. Any other ideas? Thanks. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 11, 2012, 04:29:38 AM @Theseven: Awesome! I've got it up and running with the D2XX drivers and things look ok so far! However I'm an error that i used to get with the old X6500 as well: Code: Error while requesting job from "pool" timed out Any idea on that one? Sounds like your pool is having issues (or you didn't configure it correctly)? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 11, 2012, 04:31:30 AM So I tried this, and it actually seemed to be sending MORE shares to my backup pool than it had previously (this was with priority set to 20 for main and 1 for backup). With the default settings and priorities of 1000 (main) and 1 (backup), it was sending about 100Mh/s of 2000Mh/s total to my backup pool over the course of ~24 hours. Any other ideas? Thanks. Interesting. It shouldn't be doing that unless your main pool is having severe trouble. Can you send me a screenshot of the full statistics and your config file (with passwords removed if neccessary)? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: cypherdoc on February 11, 2012, 03:06:18 PM To op,
will there ever be a version of this great software for non coders? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: freshzive on February 11, 2012, 04:10:24 PM Sent you a BTC for development of this great software :)
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on February 11, 2012, 04:16:25 PM http://img836.imageshack.us/img836/2045/mpbm1.png (http://imageshack.us/photo/my-images/836/mpbm1.png/)
Uploaded with ImageShack.us (http://imageshack.us) TheSeven, I'm wondering if you can tell me if the "failed job requests" , "Share upload retries" and "Efficiency" stats are within normal ranges. I know the failed job requests and share upload retries varies from person to person, but shouldn't the efficiency be higher? For a while it was at 98%. What does the efficiency level refer to? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: nbtcminer on February 11, 2012, 04:30:55 PM @Theseven:
It's BTCGuild, since they swapped servers yesterday things have been a bit weird. Cheers, nbtcminer Sounds like your pool is having issues (or you didn't configure it correctly)? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on February 11, 2012, 04:36:02 PM It seems it's sporadic. It sometimes goes pretty bad..checkout all the red lol:
http://img29.imageshack.us/img29/4593/mpbm2.png (http://imageshack.us/photo/my-images/29/mpbm2.png/) Uploaded with ImageShack.us (http://imageshack.us) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 11, 2012, 05:45:37 PM TheSeven, I'm wondering if you can tell me if the "failed job requests" , "Share upload retries" and "Efficiency" stats are within normal ranges. I know the failed job requests and share upload retries varies from person to person, but shouldn't the efficiency be higher? For a while it was at 98%. What does the efficiency level refer to? The failed job request, upload retries and stale share values are looking like there's connectivity trouble. Either a very slow (or rather high-latency) internet connection, a DDoS affecting the pool, or something similar. The efficiency value is basically your luck minus invalids/stales, it should usually be around 85-110% after some time (it needs some minutes to stabilize). However in your case something seems to have gone wrong with hashrate measurement at some point (look at your average hashrate), which will of course screw up the efficiency calculations. If you account for that, your effective efficiency is around 98%, which is pretty much normal. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 11, 2012, 05:53:56 PM To op, will there ever be a version of this great software for non coders? Well, you don't really require coding skills to use this software. Currently it isn't really documented well yet (this project was launched just days ago), and some general programming experience will of course make the installation and configuration easier, because programmers will usually grasp the general concepts of how this kind of thing works faster. However, if you look at the configuration file with some common sense, you'll probably recognize some patterns, how the definitions in there look like, which should enable you to adapt them to fit your needs. It really isn't all that complicated. Just ask for help if you don't understand something. I'm planning to remove the MPBM configuration file one day, and add a web interface instead through which it can be configured. This will require some major changes and thus take quite some time. Let's see how much spare time I'll have during the next months... Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 11, 2012, 05:55:25 PM Sent you a BTC for development of this great software :) Thanks a lot, I really appreciate that :)Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on February 11, 2012, 06:33:17 PM TheSeven, I'm wondering if you can tell me if the "failed job requests" , "Share upload retries" and "Efficiency" stats are within normal ranges. I know the failed job requests and share upload retries varies from person to person, but shouldn't the efficiency be higher? For a while it was at 98%. What does the efficiency level refer to? The failed job request, upload retries and stale share values are looking like there's connectivity trouble. Either a very slow (or rather high-latency) internet connection, a DDoS affecting the pool, or something similar. The efficiency value is basically your luck minus invalids/stales, it should usually be around 85-110% after some time (it needs some minutes to stabilize). However in your case something seems to have gone wrong with hashrate measurement at some point (look at your average hashrate), which will of course screw up the efficiency calculations. If you account for that, your effective efficiency is around 98%, which is pretty much normal. I think it was the pool as it has now stabilized. The efficiency is slowly climbing back up too. Average hashrate is also dropping to a more realistic figure. As for latency it's kind of funny cause I chose to use BTC Guild specifically due to the low ping and low number of hops from me to their server. I'll keep an eye on it and see how it goes. Props to you for coding a neat miner. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coblee on February 12, 2012, 11:26:40 AM I have 2 Icarus boards and after mining for a while, the stats start to look weird:
Code: Worker │Accepted│Accepted│Stale shares│Invalid shares│Current│ Average │Temperature│Effi- │ Current The accepted shares are about the same, but the 2nd board is shwoing a wrong average mhash/s and efficiency. In the logs I do notice a that the 2nd board had timed out a few times. TheSeven, any ideas? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: O_Shovah on February 12, 2012, 02:08:05 PM Has anybody suceded in running a Icarus board and a x6500 in parallel ?
It seems im missing something in the config. It only recognices and starts the x6500. The Icarus remains unseen. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on February 12, 2012, 03:10:23 PM Has anybody suceded in running a Icarus board and a x6500 in parallel ? It seems im missing something in the config. It only recognices and starts the x6500. The Icarus remains unseen. Do you have this in the list of modules to be loaded section: import worker.theseven.icarus and then in the list of workers section, this: # Icarus worker { \ # Worker module "type": worker.theseven.icarus.IcarusWorker, \ # Worker module parameters, in this case serial port name (default: /dev/ttyS0) "port": "COM3", \ }, \ Just remember to change the port variable to your particular one (ie COMx, or /dev/ttyUSBx) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 12, 2012, 03:27:07 PM I have 2 Icarus boards and after mining for a while, the stats start to look weird: Looks like something goes wrong with the total MHash counter for that worker. No idea what though, I've had a quick look at that code and can't spot any obvious reason for this. I also can't reproduce it by deliberately causing communication problems with the board. Code: Worker │Accepted│Accepted│Stale shares│Invalid shares│Current│ Average │Temperature│Effi- │ Current The accepted shares are about the same, but the 2nd board is shwoing a wrong average mhash/s and efficiency. In the logs I do notice a that the 2nd board had timed out a few times. TheSeven, any ideas? Has anybody suceded in running a Icarus board and a x6500 in parallel ? This is a bit tricky because the Icarus board requires the ftdi_sio kernel module, which conflicts with the x6500.It seems im missing something in the config. It only recognices and starts the x6500. The Icarus remains unseen. The following might be worth a try:
EDIT: It seems like the Icarus board isn't based on FTDI, but on some other USB to serial converter, which means that it doesn't need the ftdi_sio kernel module either (but possibly some other one, which doesn't hurt x6500 though). Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: nbtcminer on February 15, 2012, 09:21:58 PM Interesting note:
Found a method for installing Libusb on Windows but haven't had a change to test it yet. It seems like someone make this work around for iPhones but it may work for MPBM purposes: http://www.limesn0w.org/how-to-install-libusb-on-windows-7-vista-64-bit/ I'll give it a try tomorrow and let y'all know how it goes. Cheers, nbtcminer Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coblee on February 15, 2012, 09:26:58 PM I have 2 Icarus boards and after mining for a while, the stats start to look weird: Looks like something goes wrong with the total MHash counter for that worker. No idea what though, I've had a quick look at that code and can't spot any obvious reason for this. I also can't reproduce it by deliberately causing communication problems with the board. Code: Worker │Accepted│Accepted│Stale shares│Invalid shares│Current│ Average │Temperature│Effi- │ Current The accepted shares are about the same, but the 2nd board is shwoing a wrong average mhash/s and efficiency. In the logs I do notice a that the 2nd board had timed out a few times. TheSeven, any ideas? This keeps happening to me. Let me know how I can help you fix this. I am running the latest code. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on February 16, 2012, 11:30:21 PM Hmm, maybe this can be addressed in the next version of the miner, but it seems after connection/get work issues the miner reports ridiculous hash rates and low efficiency levels. Right now it says my average is 4244 MHs with 9.0% efficiency - I wish!! (I'm running a single Icarus board)
Maybe it should reset it's average/stats after a series of connection problems? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on February 17, 2012, 08:25:05 AM wtf..how come efficiency is showing as being negative!! looool. I'm pushing an average of -3716 MHs.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 19, 2012, 12:16:43 PM wtf..how come efficiency is showing as being negative!! looool. I'm pushing an average of -3716 MHs. I bet this is a race condition of some kind in the Icarus worker module. However I fail to spot/reproduce it. :P Feel free to have a look at the code yourself, it isn't all that complex. An additional pair of eyes can't hurt :) Anyway, I'm preparing for a new major version which will overhaul a lot of things (so it might take a while until it's finished), but as this module will probably completely rewritten during the process, I hope that this bug will just be gone afterwards... Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on February 19, 2012, 02:04:03 PM wtf..how come efficiency is showing as being negative!! looool. I'm pushing an average of -3716 MHs. I bet this is a race condition of some kind in the Icarus worker module. However I fail to spot/reproduce it. :P Feel free to have a look at the code yourself, it isn't all that complex. An additional pair of eyes can't hurt :) Anyway, I'm preparing for a new major version which will overhaul a lot of things (so it might take a while until it's finished), but as this module will probably completely rewritten during the process, I hope that this bug will just be gone afterwards... As far as I can tell it only happens when the pool I'm mining on has major connection issues or is down. Either it's not really that big of a deal - a quick restart of the miner fixes it. But I'm glad to hear you're rewriting the module/miner. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: thirdlight on February 19, 2012, 02:15:15 PM I'm preparing for a new major version Can you add uptime to the top line? So stable, like to see the weeks ticking by!Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: ngzhang on February 19, 2012, 05:41:14 PM Code: Modular Python Bitcoin Miner v0.0.4alpha running 6 boards. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: O_Shovah on February 19, 2012, 09:36:11 PM I finally got both the Icarus board and the x6500 board working on my "Gumstix" ARM computer.
Afther some dirty kernel hacking i got the modules to appear finally. I will measure the power and create "How to" for Gumstix boards this week. Manys thanks to TheSeven for his tips and patience on me and my ARM problems. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: ngzhang on February 20, 2012, 06:38:30 PM I finally got both the Icarus board and the x6500 board working on my "Gumstix" ARM computer. Afther some dirty kernel hacking i got the modules to appear finally. I will measure the power and create "How to" for Gumstix boards this week. Manys thanks to TheSeven for his tips and patience on me and my ARM problems. hi, i think you need a free icarus. please PM me your address. Code: Modular Python Bitcoin Miner v0.0.4alpha Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: O_Shovah on February 20, 2012, 07:38:18 PM I finally got both the Icarus board and the x6500 board working on my "Gumstix" ARM computer. Afther some dirty kernel hacking i got the modules to appear finally. I will measure the power and create "How to" for Gumstix boards this week. Manys thanks to TheSeven for his tips and patience on me and my ARM problems. hi, i think you need a free icarus. please PM me your address. Did you mean TheSeven or me ??? *confused* I will post a guide to your thread too. It gives a host computer with a almost full flavoured Linux using only 4 W. :) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 20, 2012, 09:44:16 PM I finally got both the Icarus board and the x6500 board working on my "Gumstix" ARM computer. Sorry about not being able to help you during the weekend, I was kinda busy with non-bitcoin stuff. Seems like you managed to get it running nevertheless?Afther some dirty kernel hacking i got the modules to appear finally. I will measure the power and create "How to" for Gumstix boards this week. Manys thanks to TheSeven for his tips and patience on me and my ARM problems. Which distro did you base this on? I know Ubuntu on the Pandaboard works like a charm (I'm using that over here), but I'm not sure about Gumstix. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: O_Shovah on February 20, 2012, 10:19:53 PM I finally got both the Icarus board and the x6500 board working on my "Gumstix" ARM computer. Sorry about not being able to help you during the weekend, I was kinda busy with non-bitcoin stuff. Seems like you managed to get it running nevertheless?Afther some dirty kernel hacking i got the modules to appear finally. I will measure the power and create "How to" for Gumstix boards this week. Manys thanks to TheSeven for his tips and patience on me and my ARM problems. Which distro did you base this on? I know Ubuntu on the Pandaboard works like a charm (I'm using that over here), but I'm not sure about Gumstix. Its a Ubuntu distru. A 10.04 "natty" to be precise. Its the same i tried using your client eralier.The charm was to compile a customised modified kernel for the board wich now seems to feature all modules intended for a regular ubuntu. I found a book (540pages) " The linux kernel " :D That helped a lot. I may hand it to you if i'm sure it works properly. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: ngzhang on February 21, 2012, 02:10:55 AM I finally got both the Icarus board and the x6500 board working on my "Gumstix" ARM computer. Afther some dirty kernel hacking i got the modules to appear finally. I will measure the power and create "How to" for Gumstix boards this week. Manys thanks to TheSeven for his tips and patience on me and my ARM problems. hi, i think you need a free icarus. please PM me your address. Did you mean TheSeven or me ??? *confused* I will post a guide to your thread too. It gives a host computer with a almost full flavoured Linux using only 4 W. :) ahhhhh, i mean TheSeven. i made a mistake. :-[ Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: ngzhang on February 21, 2012, 03:16:01 PM Code: Modular Python Bitcoin Miner v0.0.4alpha Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 21, 2012, 04:12:06 PM Code: Modular Python Bitcoin Miner v0.0.4alpha Can it really handle that much hashing power? Seems like the fetchers can keep up with it, but how does that setup behave shortly after long polls? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: ngzhang on February 21, 2012, 06:32:06 PM Code: Modular Python Bitcoin Miner v0.0.4alpha Can it really handle that much hashing power? Seems like the fetchers can keep up with it, but how does that setup behave shortly after long polls? i must say, even there are some stales. but the program is very stable. and here are some data, i think you may be interested in. Code: 2012-02-22 13:51:25.376000: Mining deepbit.net:c0379cbe273aa46c307ad85e69353eb75f57aa1ab1e2d7b9ff3fc23965235d25:b0c7fb034f44821d1a0c309c on Icarus board on COM39 Code: 2012-02-22 13:19:11.144000: ABCPool.co long poll failed: '' Code: 2012-02-22 08:00:36.322000: Error while uploading share a1541d8f (difficulty 1.76645) to deepbit.net (pit.deepbit.net:8332): timed out Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 22, 2012, 05:57:52 PM Hm, looks like deepbit is a bit swamped with requests after a long poll and can't respond to all of those 128 work requests it got from MPBM within 2 seconds. You basically ended up with like 3 seconds of wasted work after the long poll, which seems fine to me for such a huge army of workers.
If the FPGA design supports nonce ranges one day, it might be worth looking into splitting up work across multiple boards while the work fetchers are struggling to keep up after an LP. Another possibility would be adding an option that keeps multiple LP connections to the pools, so that there's more work to be put in the queue when the LP responses come in. I'll probably add support for that in the v0.1.x series. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: ngzhang on February 23, 2012, 03:43:00 AM Hm, looks like deepbit is a bit swamped with requests after a long poll and can't respond to all of those 128 work requests it got from MPBM within 2 seconds. You basically ended up with like 3 seconds of wasted work after the long poll, which seems fine to me for such a huge army of workers. If the FPGA design supports nonce ranges one day, it might be worth looking into splitting up work across multiple boards while the work fetchers are struggling to keep up after an LP. Another possibility would be adding an option that keeps multiple LP connections to the pools, so that there's more work to be put in the queue when the LP responses come in. I'll probably add support for that in the v0.1.x series. is it possible to support nonce ranges by miner software? i mean split the work by the miner, and transparent for the FPGAs. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 23, 2012, 04:12:08 PM Hm, looks like deepbit is a bit swamped with requests after a long poll and can't respond to all of those 128 work requests it got from MPBM within 2 seconds. You basically ended up with like 3 seconds of wasted work after the long poll, which seems fine to me for such a huge army of workers. If the FPGA design supports nonce ranges one day, it might be worth looking into splitting up work across multiple boards while the work fetchers are struggling to keep up after an LP. Another possibility would be adding an option that keeps multiple LP connections to the pools, so that there's more work to be put in the queue when the LP responses come in. I'll probably add support for that in the v0.1.x series. is it possible to support nonce ranges by miner software? i mean split the work by the miner, and transparent for the FPGAs. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: cypherdoc on February 23, 2012, 06:37:24 PM do any of you guys understand how BitForce is apparently outperforming your design boards? its a mystery to me.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: shad on February 23, 2012, 07:53:19 PM i think the use some high performance fpga's
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: bitcowok on February 24, 2012, 12:35:57 AM Define "outperforming". Bitforce boards currently use roughly double the power per megahash that spartan-6 boards get.
for example: 1 x bitforce = 80W @832MH 2 x x6500 = 40W @800MH Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: cypherdoc on February 24, 2012, 12:41:21 AM Define "outperforming". Bitforce boards currently use roughly double the power per megahash that spartan-6 boards get. for example: 1 x bitforce = 80W @832MH 2 x x6500 = 40W @800MH understood but you neglected to add at roughly the same price; the Mh/s is also slightly more than double. do we know for sure that the chips for the Bitforce are older generation? and does that matter in the end? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: ngzhang on February 24, 2012, 05:02:23 AM do any of you guys understand how BitForce is apparently outperforming your design boards? its a mystery to me. think about this first: why do not massive sale this alien's stuff? all of us know it will be sell well. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: ngzhang on February 24, 2012, 05:09:10 AM Hm, looks like deepbit is a bit swamped with requests after a long poll and can't respond to all of those 128 work requests it got from MPBM within 2 seconds. You basically ended up with like 3 seconds of wasted work after the long poll, which seems fine to me for such a huge army of workers. If the FPGA design supports nonce ranges one day, it might be worth looking into splitting up work across multiple boards while the work fetchers are struggling to keep up after an LP. Another possibility would be adding an option that keeps multiple LP connections to the pools, so that there's more work to be put in the queue when the LP responses come in. I'll probably add support for that in the v0.1.x series. is it possible to support nonce ranges by miner software? i mean split the work by the miner, and transparent for the FPGAs. understood. so how many bit in the nonce range is enough? now you know is 32bit wide. (11s@400MH/s) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 24, 2012, 06:45:10 PM Hm, looks like deepbit is a bit swamped with requests after a long poll and can't respond to all of those 128 work requests it got from MPBM within 2 seconds. You basically ended up with like 3 seconds of wasted work after the long poll, which seems fine to me for such a huge army of workers. If the FPGA design supports nonce ranges one day, it might be worth looking into splitting up work across multiple boards while the work fetchers are struggling to keep up after an LP. Another possibility would be adding an option that keeps multiple LP connections to the pools, so that there's more work to be put in the queue when the LP responses come in. I'll probably add support for that in the v0.1.x series. is it possible to support nonce ranges by miner software? i mean split the work by the miner, and transparent for the FPGAs. understood. so how many bit in the nonce range is enough? now you know is 32bit wide. (11s@400MH/s) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on February 29, 2012, 02:45:18 AM Total Python noob here.
I received 5 Icarus boards yesterday and I am trying to get MPBM to work (I have RG7Miner working fine with Icarus and 1 ZTEX board with the ZTEX Java Miner). I am on Windows 7 32bit. That's what I did so far. - Downloaded and installed Python 3.2 (python-3.2.2.msi). - Extracted TheSeven-Modular-Python-Bitcoin-Miner-4b06f62.zip to C:\mpbm - Edited config file and enabled Icarus and added my pool (I have only one entry in there now for my worker with COM3, would I just duplicate the entries for each worker?) - Installed curses-2.2.win32-py3.2.exe - Installed pyserial-2.5.win32.exe - I am not sure if I need JSON-RPC, so I downloaded joshmarshall-jsonrpclib-e3a3cde.zip and put it into the Python/Lib folder. Do I need to install a libusb or something? When I try to start the miner I get the following: Code: C:\mpbm>python miner.py Some coins are waiting for the one helping me to make this to work ;) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on February 29, 2012, 05:32:08 AM Did you install the PL303 driver? here: http://www.prolific.com.tw/eng/downloads.asp?id=31
Also you made sure you install the python modules such as serial,jsonrpc,curses. All available in ngzhang's github package: https://github.com/ngzhang/Icarus git it now :p Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on February 29, 2012, 07:31:59 AM Did you install the PL303 driver? here: http://www.prolific.com.tw/eng/downloads.asp?id=31 Also you made sure you install the python modules such as serial,jsonrpc,curses. All available in ngzhang's github package: https://github.com/ngzhang/Icarus git it now :p Thanks, we have success! I had the PL303 driver, but I somehow missed that the modules where available on ngzhang's github. Just putting the serial directory in the Lib folder didn't work, installing pyserial-2.5 also didn't work. I had to get pyserial-2.6.tar.gz and run 'python setup.py install' on it to get it to work (before that I had all sorts of errors, including syntax errors). Might be because I am using Python 3.2.2. Post your bitcoin address and I'll send you some coins :) I'll post a screenshot after a few hours. Right now I don't know what to make of all those numbers. So far I have this: Code: Modular Python Bitcoin Miner v0.0.4alpha Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on February 29, 2012, 08:31:18 AM Did you install the PL303 driver? here: http://www.prolific.com.tw/eng/downloads.asp?id=31 Also you made sure you install the python modules such as serial,jsonrpc,curses. All available in ngzhang's github package: https://github.com/ngzhang/Icarus git it now :p Thanks, we have success! I had the PL303 driver, but I somehow missed that the modules where available on ngzhang's github. Just putting the serial directory in the Lib folder didn't work, installing pyserial-2.5 also didn't work. I had to get pyserial-2.6.tar.gz and run 'python setup.py install' on it to get it to work (before that I had all sorts of errors, including syntax errors). Might be because I am using Python 3.2.2. Post your bitcoin address and I'll send you some coins :) I'll post a screenshot after a few hours. Right now I don't know what to make of all those numbers. So far I have this: Code: Modular Python Bitcoin Miner v0.0.4alpha Congrats. And thanks for the tip :) btc address is: 12c8Yd8P1YpTRdRDMwnvqLbTqEcymnvC67 As far as python 3.2 for sure you had to do that because you were using 3.2. Ngzhang recommends 2.7 AFAIK - that's what I'm using at the moment. Those numbers are good so far, but you need a longer running time to gain some useful data. Keep an eye for a high percentage of invalid shares. A higher number of invalid shares typically indicates overheating. I don't think you should have a problem with the stock Icarus cooling solution unless you run the board in a cramped hot area, or a very hot geographical location. Another tip for you, try using a pool that has the lowest latency/ping time from your location. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on February 29, 2012, 10:31:38 AM Quote from: allinvain Congrats. And thanks for the tip :) btc address is: 12c8Yd8P1YpTRdRDMwnvqLbTqEcymnvC67 Coins sent. Quote from: allinvain Another tip for you, try using a pool that has the lowest latency/ping time from your location. It's been running for about 2.5 hours and I have about 300 errors regarding my pool (slushes - bitcoin.cz) in my log. Ping is about 300ms from here. Most others are not much better to be honest (btcguild is). Here is an error only log file. Most are time outs, but if you scroll down you'll also see others. http://pastebin.com/5mrssXkj Edit: I changed getworktimeout to 4 seconds, this seems to have solved the time out errors for now. But do I waste a lot of time this way? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on February 29, 2012, 03:57:29 PM Edit: I changed getworktimeout to 4 seconds, this seems to have solved the time out errors for now. But do I waste a lot of time this way? It shouldn't waste time directly, it only increases the risk of the work buffer not filling fast enough, especially after long polls, if a pool misbehaves. 4 seconds should still be fine though, I use 2 seconds here because that's what pools manage to meet in >99% of the cases for me.You should probably add a backup pool though, so that your boards won't run idle if slush has problems. Generally I'd recommend using 2 or 3 pools at the same priority, i.e. balancing your hashing power across them equally. If one of them is acting up, MPBM will automatically move some hashing power away from it, towards a better working pool. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on February 29, 2012, 04:14:04 PM Quote from: allinvain Congrats. And thanks for the tip :) btc address is: 12c8Yd8P1YpTRdRDMwnvqLbTqEcymnvC67 Coins sent. Quote from: allinvain Another tip for you, try using a pool that has the lowest latency/ping time from your location. It's been running for about 2.5 hours and I have about 300 errors regarding my pool (slushes - bitcoin.cz) in my log. Ping is about 300ms from here. Most others are not much better to be honest (btcguild is). Here is an error only log file. Most are time outs, but if you scroll down you'll also see others. http://pastebin.com/5mrssXkj Edit: I changed getworktimeout to 4 seconds, this seems to have solved the time out errors for now. But do I waste a lot of time this way? Thanks antirack! :) Hmm, 300ms is pretty bad. How much better is btcguild? For me btcguild is the lowest latency pool. Slush is in the 120ms mark. There is no local pool or regional pool where you're located? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: ngzhang on March 01, 2012, 10:33:31 AM i usually get 800-1200ms here. ;D
300ms? extremely fast :P Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on March 01, 2012, 02:25:27 PM i usually get 800-1200ms here. ;D 300ms? extremely fast :P Whoa. I am extremely surprised. That is some pretty bad latency there ngzhang. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: Wandering Albatross on March 01, 2012, 07:00:50 PM Quote from: ngzhang i usually get 800-1200ms here. ;D You may want to try p2pool. I couldn't tell you if it will help you or not. If you check the p2pool thread someone might be able to tell you more. I am guessing you're in Asia or maybe you're on a sat link. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: nelisky on March 03, 2012, 12:17:49 PM https://github.com/nelisky/Modular-Python-Bitcoin-Miner/tree/ztex This is a very crude first attempt, many things are still missing, the devices need to be preflashed and the bitstreams must match the firmware. Only one device is supported (it does filter by serial, but then uses only the first device found) and the freq change algorithm from the error rate is much, much simpler than ztex's, and I only implemented the low speed FPGA config so far. Next step would be multiple device suport but as I only have one currently I'm not going to blindly implement that. I might add to the code base to support more of ztex's original java source goodies ported to python, like the high speed config, but I'll be happy to pass that anyone else wanting to lend a hand. Have fun (I'm mining on p2pool with my single ztex using this code right now). Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on March 03, 2012, 04:37:03 PM Awesome nelisky! Thanks for your contribution. Even though I do not have a ztex board I can definitely appreciate your working on support for it.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coretechs on March 04, 2012, 02:33:02 PM I just set up MPBM yesterday and have to say I was impressed. I will definitely be using this software in the future. Donation sent, thanks!
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: nelisky on March 04, 2012, 11:52:10 PM I have updated https://github.com/nelisky/Modular-Python-Bitcoin-Miner/tree/ztex with high speed FPGA configuration (which appears to be just as slow from my tests) and multi device hotplug support, though I only tested with my single board. Anyone having multiple ztex boards and wanting to experiment with MPBM, please give this a try and let me know.
I also created a pull request to get this into TheSeven's repo: https://github.com/TheSeven/Modular-Python-Bitcoin-Miner/pull/5 Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: O_Shovah on March 05, 2012, 07:21:42 AM I have finally gotten my ARM board + icarus + x6500 board running with bitcoin-qt p2pool and MPBM.
I am currently getting somewhere around 13% stales. How are your experiences regarding optimised values to improve efficiency on p2pool using MPBM ? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: shad on March 05, 2012, 12:51:29 PM I have finally gotten my ARM board + icarus + x6500 board running with bitcoin-qt p2pool and MPBM. I am currently getting somewhere around 13% stales. How are your experiences regarding optimised values to improve efficiency on p2pool using MPBM ? do you run bitcoin-qt on your arm device? what OS are you using? Openwrt? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: O_Shovah on March 05, 2012, 03:06:20 PM I am using a modified Ubuntu 11.04 natty.
I recompiled both bitcoind and bitcoin-qt for the plattform. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: julz on March 05, 2012, 06:52:22 PM I just got this running with Icarus on Windows 7.. nice!
Bitcoin donated. Is there a proper way to shut down MPBM? I've just been killing the command window as things like ctrl-c ctrl-z don't seem to have any effect. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 05, 2012, 11:07:39 PM I just got this running with Icarus on Windows 7.. nice! Thank you!Bitcoin donated. Is there a proper way to shut down MPBM? I've just been killing the command window as things like ctrl-c ctrl-z don't seem to have any effect. Hm, usually Ctrl+C should kill it. If it doesn't, there's probably something that locks up while attempting to shut things down. The Icarus worker module is currently kind of a 5 minute hack to make it work somehow, so it might suffer from that kind of thing. This will be improved in the upcoming major release.Just killing the miner should be fine, it doesn't do any real cleanup anyway (yet). Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on March 06, 2012, 01:03:44 AM I just got this running with Icarus on Windows 7.. nice! Thank you!Bitcoin donated. Is there a proper way to shut down MPBM? I've just been killing the command window as things like ctrl-c ctrl-z don't seem to have any effect. Hm, usually Ctrl+C should kill it. If it doesn't, there's probably something that locks up while attempting to shut things down. The Icarus worker module is currently kind of a 5 minute hack to make it work somehow, so it might suffer from that kind of thing. This will be improved in the upcoming major release.Just killing the miner should be fine, it doesn't do any real cleanup anyway (yet). Ctrl-C doesn't work on my Windows 7/Icarus setup neither. Ctrl-Break works. I now also have 3 ZTEX boards, but I will be traveling for the next 10 days so I can't try it using the new code in MPBM. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: O_Shovah on March 06, 2012, 07:49:33 AM I am using a modified Ubuntu 11.04 natty. Have you done a writeup on this anywhere?I recompiled both bitcoind and bitcoin-qt for the plattform. I will create thread for Bitcoin on ARM devices as soon as i find the time. Maybe this weekend. I will post descriptions downloadable system images, build instructions.... For the "Gumstix" ARM , the panda board , and maybe for a rasberry pi if i get one. So you will have to be a little patient. I would appreciate anybody else who has created systems on ARM devices to post his system there. And again: what are your experience values with MPBM and p2pool ( stales,rates, ..) And wich values do you adjust to improve performance. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 06, 2012, 03:06:43 PM And again: Should be between 10% and 20% stales if p2pool performs well (which my installation clearly doesn't, due to a sluggish bitcoind).what are your experience values with MPBM and p2pool ( stales,rates, ..) And wich values do you adjust to improve performance. And you can't really adjust any values to improve that, maybe increase the polling frequency if it's a x6500/ztex board. The only thing you could do about it would be latency optimizing the code, which will break the modular approach (and multi-worker/multi-pool capabilities). Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 07, 2012, 09:34:11 PM I've uploaded an MPBM v0.1.x prototype to the testing branch of the git repository.
It's working sufficiently to fetch work from the demo work sources somehow, so people can start porting worker interfaces. The SimpleRS232Worker module has already been ported, and might serve as kind of a porting guide. Please not that this is not ready for production use yet. At the moment it supports neither long polling nor any other getwork extensions, and it's likely that there's still quite a lot of bugs. There also is no UI for the statistics yet (but the statistics should be collected in the background). Tasks left to be done before the beta release:
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: Turbor on March 08, 2012, 07:46:47 PM Finally working :D no curses, no miner... donation sent !
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 08, 2012, 09:06:36 PM Finally working :D no curses, no miner... donation sent ! Are you sure that you prefer CursesUI over WebUI+StderrLogger with ANSI coding enabled?Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: Turbor on March 08, 2012, 09:13:18 PM Finally working :D no curses, no miner... donation sent ! Are you sure that you prefer CursesUI over WebUI+StderrLogger with ANSI coding enabled?:o i'm a carpenter, no idea what you talk about :D Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: Turbor on March 10, 2012, 05:41:29 PM Runs stable at 0.1% rejects. No more sleep mode. Only thing that's not working after some time is the average MH/s rate and the efficiency. It says 600+ MH for one board. Restart helps.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 17, 2012, 11:21:15 PM I'd like to invite everyone who's willing to take a small risk of deadlocks and other annoyances, to check out the testing branch of MPBM.
It isn't quite ready for production use that's unattended over months yet, but it has at least survived a week of testing on my own low-hashrate board. It would be especially interesting for me to collect testing results from bigger FPGA rigs (>2GH/s, or even >10GH/s), but please only do that if you can react quickly in case of failure, to prevent wasting valuable hashing time. Please note that latencies seem to be too high to work reasonably well with P2Pool. This seems to be the price you have to pay for flexibility. We'll see if that can be improved. One of the most important new features is the web based user interface, which allows to configure the miner on the fly, and removes the need for a configuration file. If you want to check it out, do this:
Btw. the correct way to shut down MPBM is just hitting ctrl+c on the console. Known issues:
If you hit some issues, or just want to provide some feedback, feel free to post here or contact me at #mpbm on irc.freenode.net (http://webchat.freenode.net?channels=mpbm). In case you should hit a deadlock, please obtain a thread state dump from the debug menu on WebUI and pastebin that. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coblee on March 19, 2012, 12:18:26 AM I can't seem to get my X6500 workers to work.
2012-03-18 17:17:44.525 [100] X6500 worker - AH00WI18: Proxy: Exception caught: Traceback (most recent call last): File "/Users/charlie/Modular-Python-Bitcoin-Miner-testing/modules/fpgamining/x6500/boardproxy.py", line 77, in run else: self.device = FT232R(FT232R_PyUSB(self.serial, self.takeover)) File "/Users/charlie/Modular-Python-Bitcoin-Miner-testing/modules/fpgamining/x6500/util/ft232r.py", line 314, 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-03-18 17:17:44.528 [100] X6500 worker - AH00WI18: Traceback (most recent call last): File "/Users/charlie/Modular-Python-Bitcoin-Miner-testing/modules/fpgamining/x6500/x6500worker.py", line 211, in main elif data[0] == "dying": raise Exception("Proxy died!") Exception: Proxy died! Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 19, 2012, 02:00:49 AM USBError: [Errno None] Unknown error Now that's the kind of libusb errors that I like most. What OS is that? Mac? Does this affect only the testing branch or both? Does it work with the D2XX driver? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coblee on March 19, 2012, 03:30:01 AM USBError: [Errno None] Unknown error Now that's the kind of libusb errors that I like most. What OS is that? Mac? Does this affect only the testing branch or both? Does it work with the D2XX driver? OS is Mac. Only affects testing branch. Haven't tried D2XX drivers. Will try that later. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 19, 2012, 08:51:32 PM I'm running it both with 2.7 and 3.2, everything >=2.6 should work.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: Raize on March 20, 2012, 05:34:41 AM Never used Python in my life. Anyone willing to give me a step-by-step on exactly how to do this? I've got Python 2.7 installed and I downloaded default_config.py and miner.py. I have literally no idea what is safe to edit. I use P2Pool. I've made the necessary edits and nothing seem to be working. CGminer also doesn't work, and nor does RG7Miner under Java. I'm starting to think I've gotten a bad Icarus device.
Bounty of 2 Bitcoin to whoever provides a successful step-by-step. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: Turbor on March 20, 2012, 11:42:55 AM Never used Python in my life. Anyone willing to give me a step-by-step on exactly how to do this? I've got Python 2.7 installed and I downloaded default_config.py and miner.py. I have literally no idea what is safe to edit. I use P2Pool. I've made the necessary edits and nothing seem to be working. CGminer also doesn't work, and nor does RG7Miner under Java. I'm starting to think I've gotten a bad Icarus device. Bounty of 2 Bitcoin to whoever provides a successful step-by-step. What OS ? Windows ? I spent some hours to get my board running. You need some important files to make it work. It's very unlike that the board is bad. Can help you this evening (european time) if your on IRC. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: Turbor on March 20, 2012, 06:26:13 PM Hey Raize here a little write-up for Windows.
Download and install the USB to Serial driver: http://www.prolific.com.tw/support/files/%5CIO%20Cable%5CPL-2303%5CDrivers%20-%20Generic%5CWindows%5Callinone%5CPL2303_Prolific_DriverInstaller_v1.5.0.zip (http://www.prolific.com.tw/support/files/%5CIO%20Cable%5CPL-2303%5CDrivers%20-%20Generic%5CWindows%5Callinone%5CPL2303_Prolific_DriverInstaller_v1.5.0.zip) Install Python: http://www.python.org/getit/ (http://www.python.org/getit/) Get the python libs from Zhang (need them to run the board) and put them into the python27/Lib folder: https://github.com/ngzhang/Icarus/tree/0945ce06be6ed85fc2623ef36aa15c70ae82e56f/Downloads/python_Libs (https://github.com/ngzhang/Icarus/tree/0945ce06be6ed85fc2623ef36aa15c70ae82e56f/Downloads/python_Libs) For .exe curses go to http://www.lfd.uci.edu/~gohlke/pythonlibs/#curses (http://www.lfd.uci.edu/~gohlke/pythonlibs/#curses), scroll down to curses and install the one you need for your Windows version ! Download MPBM, unzip in a location of your choice: https://github.com/TheSeven/Modular-Python-Bitcoin-Miner/zipball/master Here is my default_config.py file: Code: # Modular Python Bitcoin Miner demonstration configuration file Once edited for your needs, start the miner with the command prompt, something like below if you installed the software to user: C:\Users\Samxxx Xxxxxx>miner.py If the board is well, it "should" fire up. If you have questions, feel free to ask. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 20, 2012, 09:44:14 PM New feature on testing branch: ZTEX board support
Even though ztex himself still does not seem to want to cooperate, a user of MPBM was kind enough to let me test things on a couple ZTEX boards. For now, the dynamic overclocking behavior is 100% cloned from BTCMiner to avoid warranty issues. Feel free to check things out! :) Anyone with a BFL board around who wants to help adding the last missing FPGA board interface module? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: bitcowok on March 21, 2012, 12:33:23 AM Anyone with a BFL board around who wants to help adding the last missing FPGA board interface module? As soon as mine arrives, i'll set you up with ssh access, if you still need it. It was ordered in jan, so i'm hoping in the next month or so. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: O_Shovah on March 21, 2012, 12:02:11 PM My BFL box has been working for some days now hooked up to cgminer.
If theres anyone interested , maybe you TheSeven or anybody else i will create a ssh access for him to develop a module. I would very much appreciate this. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: Raize on March 22, 2012, 03:36:41 AM Hey Raize here a little write-up for Windows. Thanks for the help. Do you have a wallet address? Also, Icarus with this miner does not seem to work with P2Pool: (EDIT: Actually I get this with every pool I mine on) https://i.imgur.com/9Og8g.png Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 22, 2012, 09:24:16 AM This behavior means that the board just doesn't respond for some reason. Is it powered up? What do the LEDs say? (You should see some go out when you start MPBM and then start flashing from time to time. If they don't, there's a communication issue.)
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: Turbor on March 22, 2012, 05:54:42 PM Thanks for the help. Do you have a wallet address? Also, Icarus with this miner does not seem to work with P2Pool: (EDIT: Actually I get this with every pool I mine on) https://i.imgur.com/9Og8g.png Hello Raize This one was for free. The miner runs fine, but there seems to be an issue with the boards. Are you sure about the port numbers ? You can check it with the hardware manager (Connections (COM & LPT). If you connect them to a different port the number will change and you can see the driver working in the task bar of windows. When finished it says something like device x on port y ready (don't remember :D). Also check if the libs from Zhang are extracted and in the right place. Perhaps you can send us the code of your conf file. Edit: You can donate to TheSeven if you got it up and running ! He deserves it. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: Glasswalker on March 22, 2012, 06:31:27 PM On testing build I'm getting some odd behavior. I'm mining with Icarus (12 of them right now) against GPUMax with Slush as backup (for one I tried P2Pool and it failed miserably, timeouts like crazy, and random stalls, among other things)
Anyway, the problem I'm getting is half my miners seem to be doing no work. As in after 12 hours of mining, 6 of them have done 4000+ accepted shares, and the other 6 have done 5. (seems to be random which ones). Any thoughts of things to look at first? where to start digging? Thanks! Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: Raize on March 23, 2012, 12:33:07 AM Okay, I'll throw him 2 BTC. I ended up having to switch the miners off and disconnect then back on and reconnect and it all worked fine. (In case anyone is wondering)
EDIT: There is one address in TheSeven's signature and one in the first post, which one should I send to? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 23, 2012, 01:45:40 AM Okay, I'll throw him 2 BTC. I ended up having to switch the miners off and disconnect then back on and reconnect and it all worked fine. (In case anyone is wondering) EDIT: There is one address in TheSeven's signature and one in the first post, which one should I send to? Just chose an arbitrary one. They all go to the same wallet, I just use different addresses to track where people actually look for one :) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 23, 2012, 01:48:01 AM New feature on testing branch: Butterfly Labs BitFORCE Single support
Thanks to O_Shovah for letting me develop and test this on his one :) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on March 23, 2012, 01:51:34 AM Just curious to know if you have any idea when the new MPBM will come out of testing and at least into main branch.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 23, 2012, 02:27:20 AM When enough people have tested it for stability, some more documentation (quick start gudes for various platforms / boards) has been written, and I've ironed out some remaining bugs, e.g. occasional bursts of unneccsary work requests to pools.
I think it might happen rather soon, but it all depends on whether other people are willing to help with testing and possibly documenting. I'd be especially interested in testing results from large clusters, to see whether MPBM scales well enough with the current work distribution system. I'd prefer that kind of testing to be done on BFL or Icarus boards for various reasons. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: BR0KK on March 23, 2012, 11:53:28 AM Hi, I'm trying to get this running under OSX LION.
The Miner starts but i get these errors: http://www.abload.de/thumb/bildschirmfoto2012-03mv5bb.png (http://www.abload.de/image.php?img=bildschirmfoto2012-03mv5bb.png) Seems that under OSX mpbm isn't able to load some modules? Is there an easy way to fix this (remember --> windows guy :D) or do i have to switch to linux / Windows? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 23, 2012, 02:21:15 PM You'll need to install the PySerial library (http://pyserial.sourceforge.net/ (http://pyserial.sourceforge.net/)), if you want to use SimpleRS232, Icarus or BFL boards.
You'll need to install the PyUSB library (http://sourceforge.net/apps/trac/pyusb/ (http://sourceforge.net/apps/trac/pyusb/)), if you want to use ZTEX boards. You'll need to install the PyUSB library (http://sourceforge.net/apps/trac/pyusb/ (http://sourceforge.net/apps/trac/pyusb/), recommended), or, alternatively (but not recommended), the PyD2XX library (http://bleyer.org/pyusb/ (http://bleyer.org/pyusb/), often wrongly called PyUSB as well), if you want to use X6500 boards. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: BR0KK on March 24, 2012, 01:08:49 AM I installed pyusb and libusb (a while ago not shire which one i installed. Might be the Twain Sane one -- could be to old?). MPBM seems to load the Modules but i can't get it to run with on of my boards.
I get these errors: Code: 2012-03-24 01:42:09.936 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 147, in main if not self.serial: raise Exception("Device serial number not set!") Exception: Device serial number not set! 2012-03-24 01:42:10.937 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 147, in main if not self.serial: raise Exception("Device serial number not set!") Exception: Device serial number not set! 2012-03-24 01:42:11.939 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 147, in main if not self.serial: raise Exception("Device serial number not set!") Exception: Device serial number not set! 2012-03-24 01:42:12.940 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 147, in main if not self.serial: raise Exception("Device serial number not set!") Exception: Device serial number not set! 2012-03-24 01:42:13.942 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 147, in main if not self.serial: raise Exception("Device serial number not set!") Exception: Device serial number not set! 2012-03-24 01:42:14.943 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 147, in main if not self.serial: raise Exception("Device serial number not set!") Exception: Device serial number not set! 2012-03-24 01:42:16.048 [100] Untitled ZTEX worker: Proxy: Exception caught: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/boardproxy.py", line 75, in run self.device = ZtexDevice(self, self.serial, self.takeover, self.firmware) File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/driver.py", line 49, in __init__ for bus in usb.busses(): File "/Library/Python/2.7/site-packages/usb/legacy.py", line 333, in busses return (Bus(),) File "/Library/Python/2.7/site-packages/usb/legacy.py", line 329, in __init__ self.devices = [Device(d) for d in core.find(find_all=True)] File "/Library/Python/2.7/site-packages/usb/core.py", line 851, in find return [d for d in device_iter(k, v)] File "/Library/Python/2.7/site-packages/usb/core.py", line 821, in device_iter for dev in backend.enumerate_devices(): File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 390, in enumerate_devices _check(_lib.usb_find_busses()) File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 384, in _check raise USBError(errmsg, ret) USBError: [Errno None] libusb/darwin.c usb_setup_iterator: IOServiceGetMatchingServices: unknown error 2012-03-24 01:42:16.049 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 170, in main elif data[0] == "dying": raise Exception("Proxy died!") Exception: Proxy died! 2012-03-24 01:42:17.057 [100] Untitled ZTEX worker: Proxy: Exception caught: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/boardproxy.py", line 75, in run self.device = ZtexDevice(self, self.serial, self.takeover, self.firmware) File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/driver.py", line 49, in __init__ for bus in usb.busses(): File "/Library/Python/2.7/site-packages/usb/legacy.py", line 333, in busses return (Bus(),) File "/Library/Python/2.7/site-packages/usb/legacy.py", line 329, in __init__ self.devices = [Device(d) for d in core.find(find_all=True)] File "/Library/Python/2.7/site-packages/usb/core.py", line 851, in find return [d for d in device_iter(k, v)] File "/Library/Python/2.7/site-packages/usb/core.py", line 821, in device_iter for dev in backend.enumerate_devices(): File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 390, in enumerate_devices _check(_lib.usb_find_busses()) File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 384, in _check raise USBError(errmsg, ret) USBError: [Errno None] libusb/darwin.c usb_setup_iterator: IOServiceGetMatchingServices: unknown error 2012-03-24 01:42:17.059 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 170, in main elif data[0] == "dying": raise Exception("Proxy died!") Exception: Proxy died! 2012-03-24 01:42:18.069 [100] Untitled ZTEX worker: Proxy: Exception caught: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/boardproxy.py", line 75, in run self.device = ZtexDevice(self, self.serial, self.takeover, self.firmware) File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/driver.py", line 49, in __init__ for bus in usb.busses(): File "/Library/Python/2.7/site-packages/usb/legacy.py", line 333, in busses return (Bus(),) File "/Library/Python/2.7/site-packages/usb/legacy.py", line 329, in __init__ self.devices = [Device(d) for d in core.find(find_all=True)] File "/Library/Python/2.7/site-packages/usb/core.py", line 851, in find return [d for d in device_iter(k, v)] File "/Library/Python/2.7/site-packages/usb/core.py", line 821, in device_iter for dev in backend.enumerate_devices(): File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 390, in enumerate_devices _check(_lib.usb_find_busses()) File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 384, in _check raise USBError(errmsg, ret) USBError: [Errno None] libusb/darwin.c usb_setup_iterator: IOServiceGetMatchingServices: unknown error 2012-03-24 01:42:18.071 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 170, in main elif data[0] == "dying": raise Exception("Proxy died!") Exception: Proxy died! 2012-03-24 01:42:19.083 [100] Untitled ZTEX worker: Proxy: Exception caught: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/boardproxy.py", line 75, in run self.device = ZtexDevice(self, self.serial, self.takeover, self.firmware) File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/driver.py", line 49, in __init__ for bus in usb.busses(): File "/Library/Python/2.7/site-packages/usb/legacy.py", line 333, in busses return (Bus(),) File "/Library/Python/2.7/site-packages/usb/legacy.py", line 329, in __init__ self.devices = [Device(d) for d in core.find(find_all=True)] File "/Library/Python/2.7/site-packages/usb/core.py", line 851, in find return [d for d in device_iter(k, v)] File "/Library/Python/2.7/site-packages/usb/core.py", line 821, in device_iter for dev in backend.enumerate_devices(): File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 390, in enumerate_devices _check(_lib.usb_find_busses()) File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 384, in _check raise USBError(errmsg, ret) USBError: [Errno None] libusb/darwin.c usb_setup_iterator: IOServiceGetMatchingServices: unknown error 2012-03-24 01:42:19.084 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 170, in main elif data[0] == "dying": raise Exception("Proxy died!") Exception: Proxy died! 2012-03-24 01:42:20.096 [100] Untitled ZTEX worker: Proxy: Exception caught: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/boardproxy.py", line 75, in run self.device = ZtexDevice(self, self.serial, self.takeover, self.firmware) File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/driver.py", line 49, in __init__ for bus in usb.busses(): File "/Library/Python/2.7/site-packages/usb/legacy.py", line 333, in busses return (Bus(),) File "/Library/Python/2.7/site-packages/usb/legacy.py", line 329, in __init__ self.devices = [Device(d) for d in core.find(find_all=True)] File "/Library/Python/2.7/site-packages/usb/core.py", line 851, in find return [d for d in device_iter(k, v)] File "/Library/Python/2.7/site-packages/usb/core.py", line 821, in device_iter for dev in backend.enumerate_devices(): File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 390, in enumerate_devices _check(_lib.usb_find_busses()) File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 384, in _check raise USBError(errmsg, ret) USBError: [Errno None] libusb/darwin.c usb_setup_iterator: IOServiceGetMatchingServices: unknown error 2012-03-24 01:42:20.098 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 170, in main elif data[0] == "dying": raise Exception("Proxy died!") Exception: Proxy died! 2012-03-24 01:42:21.111 [100] Untitled ZTEX worker: Proxy: Exception caught: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/boardproxy.py", line 75, in run self.device = ZtexDevice(self, self.serial, self.takeover, self.firmware) File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/driver.py", line 49, in __init__ for bus in usb.busses(): File "/Library/Python/2.7/site-packages/usb/legacy.py", line 333, in busses return (Bus(),) File "/Library/Python/2.7/site-packages/usb/legacy.py", line 329, in __init__ self.devices = [Device(d) for d in core.find(find_all=True)] File "/Library/Python/2.7/site-packages/usb/core.py", line 851, in find return [d for d in device_iter(k, v)] File "/Library/Python/2.7/site-packages/usb/core.py", line 821, in device_iter for dev in backend.enumerate_devices(): File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 390, in enumerate_devices _check(_lib.usb_find_busses()) File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 384, in _check raise USBError(errmsg, ret) USBError: [Errno None] libusb/darwin.c usb_setup_iterator: IOServiceGetMatchingServices: unknown error 2012-03-24 01:42:21.112 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 170, in main elif data[0] == "dying": raise Exception("Proxy died!") Exception: Proxy died! 2012-03-24 01:42:23.432 [500] Eligius (donation): Got 120 jobs 2012-03-24 01:42:23.656 [500] BTCGuild (donation): Got 1 jobs 2012-03-24 01:42:51.122 [100] Untitled ZTEX worker: Proxy: Exception caught: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/boardproxy.py", line 75, in run self.device = ZtexDevice(self, self.serial, self.takeover, self.firmware) File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/driver.py", line 49, in __init__ for bus in usb.busses(): File "/Library/Python/2.7/site-packages/usb/legacy.py", line 333, in busses return (Bus(),) File "/Library/Python/2.7/site-packages/usb/legacy.py", line 329, in __init__ self.devices = [Device(d) for d in core.find(find_all=True)] File "/Library/Python/2.7/site-packages/usb/core.py", line 851, in find return [d for d in device_iter(k, v)] File "/Library/Python/2.7/site-packages/usb/core.py", line 821, in device_iter for dev in backend.enumerate_devices(): File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 390, in enumerate_devices _check(_lib.usb_find_busses()) File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 384, in _check raise USBError(errmsg, ret) USBError: [Errno None] libusb/darwin.c usb_setup_iterator: IOServiceGetMatchingServices: unknown error 2012-03-24 01:42:51.123 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 170, in main elif data[0] == "dying": raise Exception("Proxy died!") Exception: Proxy died! 2012-03-24 01:43:21.135 [100] Untitled ZTEX worker: Proxy: Exception caught: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/boardproxy.py", line 75, in run self.device = ZtexDevice(self, self.serial, self.takeover, self.firmware) File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/driver.py", line 49, in __init__ for bus in usb.busses(): File "/Library/Python/2.7/site-packages/usb/legacy.py", line 333, in busses return (Bus(),) File "/Library/Python/2.7/site-packages/usb/legacy.py", line 329, in __init__ self.devices = [Device(d) for d in core.find(find_all=True)] File "/Library/Python/2.7/site-packages/usb/core.py", line 851, in find return [d for d in device_iter(k, v)] File "/Library/Python/2.7/site-packages/usb/core.py", line 821, in device_iter for dev in backend.enumerate_devices(): File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 390, in enumerate_devices _check(_lib.usb_find_busses()) File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 384, in _check raise USBError(errmsg, ret) USBError: [Errno None] libusb/darwin.c usb_setup_iterator: IOServiceGetMatchingServices: unknown error 2012-03-24 01:43:21.136 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 170, in main elif data[0] == "dying": raise Exception("Proxy died!") Exception: Proxy died! hmmm im not shure if MAC is the right computer for this kind of stuff. i just switched to it, so i have literally no skills in installing things that are complex :( (don't ask if i do with linux :P). Isn't there a how to aviable describing how MPBM works (Just a basic tutorial: like setting up workers etc)? I'll try to set it up under windows tomorrow. Thx for the help :) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on March 24, 2012, 02:07:10 AM I have tested this according to your instructions and it worked without problems in my 3 Ztex (+5 Icarus) setup). It recognized the Ztex boards automatically, while I had to add my Icarus COM ports manually (as expected I guess). I only had 5 minutes so I didn't set up my own blockchains (pools), but everything worked as expected. Once I have more time I will test a bit more and give you feedback in your thread, I have only been using the old version of MPBM so far. One thing I noticed, using Firefox the display on the top left (menu) was messed up. With Chrome it worked fine. Could be one of my Firefox add-ons though. Yes, I haven't found a way to autodetect Icarus boards yet, their protocol doesn't really make that easy. It's kinda fire and forget. What do you mean with "old version"? The old version (master branch) doesn't have ztex board support (except for nelisky's branch, but I'm not sure if that one even works yet, haven't tested it). The web user interface is the new (testing) branch. The firefox issues are known, seems like it has a problem with sizing of scrollable divs. Need to look into that when I find time to do that. This is from the ztex thread. With "old version" I meant the master branch that works in the console. I used it to run my 5 Icarus and for my 3 ztex I used the BTCMiner in another console. I now switched to the testing branch on Windows 7 with Python 3.2 and so far it works fine. I have created my own worker sources and noticed it is not possible to assign workers to worker sources, or maybe I just didn't figure out how it works. In my pools I usually setup two workers, one for icarus one for ztex. The login would usually be username.ztex or username.icarus on the pools. This way I can also monitor their performance separately in the pools, and via mobile app on the phone for instance. Would this be something that could be done? What is the idea behind having Blockchains? Now there is only one, the Bitcoin blockchain. And all you can do is set the name and a timeout. Autodetect Icarus: on windows it seems you can use HARDWARE\\DEVICEMAP\\SERIALCOMM to check for the serial ports, then send some test data to the ones with "Prolific" to see if they are indeed Icarus boards. http://eli.thegreenplace.net/2009/07/31/listing-all-serial-ports-on-windows-with-python/ Edit: Here is code that seems to work with other OS too, but it's from 2007: http://bitpim.svn.sourceforge.net/viewvc/bitpim/trunk/bitpim/src/comscan.py?view=markup Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 24, 2012, 10:37:19 AM I installed pyusb and libusb (a while ago not shire which one i installed. Might be the Twain Sane one -- could be to old?). MPBM seems to load the Modules but i can't get it to run with on of my boards. I get these errors: Code: 2012-03-24 01:42:09.936 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 147, in main if not self.serial: raise Exception("Device serial number not set!") Exception: Device serial number not set! 2012-03-24 01:42:10.937 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 147, in main if not self.serial: raise Exception("Device serial number not set!") Exception: Device serial number not set! 2012-03-24 01:42:11.939 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 147, in main if not self.serial: raise Exception("Device serial number not set!") Exception: Device serial number not set! 2012-03-24 01:42:12.940 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 147, in main if not self.serial: raise Exception("Device serial number not set!") Exception: Device serial number not set! 2012-03-24 01:42:13.942 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 147, in main if not self.serial: raise Exception("Device serial number not set!") Exception: Device serial number not set! 2012-03-24 01:42:14.943 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 147, in main if not self.serial: raise Exception("Device serial number not set!") Exception: Device serial number not set! 2012-03-24 01:42:16.048 [100] Untitled ZTEX worker: Proxy: Exception caught: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/boardproxy.py", line 75, in run self.device = ZtexDevice(self, self.serial, self.takeover, self.firmware) File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/driver.py", line 49, in __init__ for bus in usb.busses(): File "/Library/Python/2.7/site-packages/usb/legacy.py", line 333, in busses return (Bus(),) File "/Library/Python/2.7/site-packages/usb/legacy.py", line 329, in __init__ self.devices = [Device(d) for d in core.find(find_all=True)] File "/Library/Python/2.7/site-packages/usb/core.py", line 851, in find return [d for d in device_iter(k, v)] File "/Library/Python/2.7/site-packages/usb/core.py", line 821, in device_iter for dev in backend.enumerate_devices(): File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 390, in enumerate_devices _check(_lib.usb_find_busses()) File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 384, in _check raise USBError(errmsg, ret) USBError: [Errno None] libusb/darwin.c usb_setup_iterator: IOServiceGetMatchingServices: unknown error 2012-03-24 01:42:16.049 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 170, in main elif data[0] == "dying": raise Exception("Proxy died!") Exception: Proxy died! 2012-03-24 01:42:17.057 [100] Untitled ZTEX worker: Proxy: Exception caught: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/boardproxy.py", line 75, in run self.device = ZtexDevice(self, self.serial, self.takeover, self.firmware) File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/driver.py", line 49, in __init__ for bus in usb.busses(): File "/Library/Python/2.7/site-packages/usb/legacy.py", line 333, in busses return (Bus(),) File "/Library/Python/2.7/site-packages/usb/legacy.py", line 329, in __init__ self.devices = [Device(d) for d in core.find(find_all=True)] File "/Library/Python/2.7/site-packages/usb/core.py", line 851, in find return [d for d in device_iter(k, v)] File "/Library/Python/2.7/site-packages/usb/core.py", line 821, in device_iter for dev in backend.enumerate_devices(): File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 390, in enumerate_devices _check(_lib.usb_find_busses()) File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 384, in _check raise USBError(errmsg, ret) USBError: [Errno None] libusb/darwin.c usb_setup_iterator: IOServiceGetMatchingServices: unknown error 2012-03-24 01:42:17.059 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 170, in main elif data[0] == "dying": raise Exception("Proxy died!") Exception: Proxy died! 2012-03-24 01:42:18.069 [100] Untitled ZTEX worker: Proxy: Exception caught: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/boardproxy.py", line 75, in run self.device = ZtexDevice(self, self.serial, self.takeover, self.firmware) File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/driver.py", line 49, in __init__ for bus in usb.busses(): File "/Library/Python/2.7/site-packages/usb/legacy.py", line 333, in busses return (Bus(),) File "/Library/Python/2.7/site-packages/usb/legacy.py", line 329, in __init__ self.devices = [Device(d) for d in core.find(find_all=True)] File "/Library/Python/2.7/site-packages/usb/core.py", line 851, in find return [d for d in device_iter(k, v)] File "/Library/Python/2.7/site-packages/usb/core.py", line 821, in device_iter for dev in backend.enumerate_devices(): File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 390, in enumerate_devices _check(_lib.usb_find_busses()) File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 384, in _check raise USBError(errmsg, ret) USBError: [Errno None] libusb/darwin.c usb_setup_iterator: IOServiceGetMatchingServices: unknown error 2012-03-24 01:42:18.071 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 170, in main elif data[0] == "dying": raise Exception("Proxy died!") Exception: Proxy died! 2012-03-24 01:42:19.083 [100] Untitled ZTEX worker: Proxy: Exception caught: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/boardproxy.py", line 75, in run self.device = ZtexDevice(self, self.serial, self.takeover, self.firmware) File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/driver.py", line 49, in __init__ for bus in usb.busses(): File "/Library/Python/2.7/site-packages/usb/legacy.py", line 333, in busses return (Bus(),) File "/Library/Python/2.7/site-packages/usb/legacy.py", line 329, in __init__ self.devices = [Device(d) for d in core.find(find_all=True)] File "/Library/Python/2.7/site-packages/usb/core.py", line 851, in find return [d for d in device_iter(k, v)] File "/Library/Python/2.7/site-packages/usb/core.py", line 821, in device_iter for dev in backend.enumerate_devices(): File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 390, in enumerate_devices _check(_lib.usb_find_busses()) File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 384, in _check raise USBError(errmsg, ret) USBError: [Errno None] libusb/darwin.c usb_setup_iterator: IOServiceGetMatchingServices: unknown error 2012-03-24 01:42:19.084 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 170, in main elif data[0] == "dying": raise Exception("Proxy died!") Exception: Proxy died! 2012-03-24 01:42:20.096 [100] Untitled ZTEX worker: Proxy: Exception caught: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/boardproxy.py", line 75, in run self.device = ZtexDevice(self, self.serial, self.takeover, self.firmware) File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/driver.py", line 49, in __init__ for bus in usb.busses(): File "/Library/Python/2.7/site-packages/usb/legacy.py", line 333, in busses return (Bus(),) File "/Library/Python/2.7/site-packages/usb/legacy.py", line 329, in __init__ self.devices = [Device(d) for d in core.find(find_all=True)] File "/Library/Python/2.7/site-packages/usb/core.py", line 851, in find return [d for d in device_iter(k, v)] File "/Library/Python/2.7/site-packages/usb/core.py", line 821, in device_iter for dev in backend.enumerate_devices(): File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 390, in enumerate_devices _check(_lib.usb_find_busses()) File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 384, in _check raise USBError(errmsg, ret) USBError: [Errno None] libusb/darwin.c usb_setup_iterator: IOServiceGetMatchingServices: unknown error 2012-03-24 01:42:20.098 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 170, in main elif data[0] == "dying": raise Exception("Proxy died!") Exception: Proxy died! 2012-03-24 01:42:21.111 [100] Untitled ZTEX worker: Proxy: Exception caught: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/boardproxy.py", line 75, in run self.device = ZtexDevice(self, self.serial, self.takeover, self.firmware) File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/driver.py", line 49, in __init__ for bus in usb.busses(): File "/Library/Python/2.7/site-packages/usb/legacy.py", line 333, in busses return (Bus(),) File "/Library/Python/2.7/site-packages/usb/legacy.py", line 329, in __init__ self.devices = [Device(d) for d in core.find(find_all=True)] File "/Library/Python/2.7/site-packages/usb/core.py", line 851, in find return [d for d in device_iter(k, v)] File "/Library/Python/2.7/site-packages/usb/core.py", line 821, in device_iter for dev in backend.enumerate_devices(): File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 390, in enumerate_devices _check(_lib.usb_find_busses()) File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 384, in _check raise USBError(errmsg, ret) USBError: [Errno None] libusb/darwin.c usb_setup_iterator: IOServiceGetMatchingServices: unknown error 2012-03-24 01:42:21.112 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 170, in main elif data[0] == "dying": raise Exception("Proxy died!") Exception: Proxy died! 2012-03-24 01:42:23.432 [500] Eligius (donation): Got 120 jobs 2012-03-24 01:42:23.656 [500] BTCGuild (donation): Got 1 jobs 2012-03-24 01:42:51.122 [100] Untitled ZTEX worker: Proxy: Exception caught: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/boardproxy.py", line 75, in run self.device = ZtexDevice(self, self.serial, self.takeover, self.firmware) File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/driver.py", line 49, in __init__ for bus in usb.busses(): File "/Library/Python/2.7/site-packages/usb/legacy.py", line 333, in busses return (Bus(),) File "/Library/Python/2.7/site-packages/usb/legacy.py", line 329, in __init__ self.devices = [Device(d) for d in core.find(find_all=True)] File "/Library/Python/2.7/site-packages/usb/core.py", line 851, in find return [d for d in device_iter(k, v)] File "/Library/Python/2.7/site-packages/usb/core.py", line 821, in device_iter for dev in backend.enumerate_devices(): File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 390, in enumerate_devices _check(_lib.usb_find_busses()) File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 384, in _check raise USBError(errmsg, ret) USBError: [Errno None] libusb/darwin.c usb_setup_iterator: IOServiceGetMatchingServices: unknown error 2012-03-24 01:42:51.123 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 170, in main elif data[0] == "dying": raise Exception("Proxy died!") Exception: Proxy died! 2012-03-24 01:43:21.135 [100] Untitled ZTEX worker: Proxy: Exception caught: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/boardproxy.py", line 75, in run self.device = ZtexDevice(self, self.serial, self.takeover, self.firmware) File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/driver.py", line 49, in __init__ for bus in usb.busses(): File "/Library/Python/2.7/site-packages/usb/legacy.py", line 333, in busses return (Bus(),) File "/Library/Python/2.7/site-packages/usb/legacy.py", line 329, in __init__ self.devices = [Device(d) for d in core.find(find_all=True)] File "/Library/Python/2.7/site-packages/usb/core.py", line 851, in find return [d for d in device_iter(k, v)] File "/Library/Python/2.7/site-packages/usb/core.py", line 821, in device_iter for dev in backend.enumerate_devices(): File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 390, in enumerate_devices _check(_lib.usb_find_busses()) File "/Library/Python/2.7/site-packages/usb/backend/libusb01.py", line 384, in _check raise USBError(errmsg, ret) USBError: [Errno None] libusb/darwin.c usb_setup_iterator: IOServiceGetMatchingServices: unknown error 2012-03-24 01:43:21.136 [100] Untitled ZTEX worker: Traceback (most recent call last): File "/Users/BR0KK/Modular-Python-Bitcoin-Miner/modules/theseven/ztex/ztexworker.py", line 170, in main elif data[0] == "dying": raise Exception("Proxy died!") Exception: Proxy died! hmmm im not shure if MAC is the right computer for this kind of stuff. i just switched to it, so i have literally no skills in installing things that are complex :( (don't ask if i do with linux :P). Isn't there a how to aviable describing how MPBM works (Just a basic tutorial: like setting up workers etc)? I'll try to set it up under windows tomorrow. Thx for the help :) Looks like you instantiated a single ZTEX board worker and didn't configure the board number. You should probably just use the ZTEX hotplug worker instead, which autodetects which boards are present. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 24, 2012, 10:47:01 AM I have tested this according to your instructions and it worked without problems in my 3 Ztex (+5 Icarus) setup). It recognized the Ztex boards automatically, while I had to add my Icarus COM ports manually (as expected I guess). I only had 5 minutes so I didn't set up my own blockchains (pools), but everything worked as expected. Once I have more time I will test a bit more and give you feedback in your thread, I have only been using the old version of MPBM so far. One thing I noticed, using Firefox the display on the top left (menu) was messed up. With Chrome it worked fine. Could be one of my Firefox add-ons though. Yes, I haven't found a way to autodetect Icarus boards yet, their protocol doesn't really make that easy. It's kinda fire and forget. What do you mean with "old version"? The old version (master branch) doesn't have ztex board support (except for nelisky's branch, but I'm not sure if that one even works yet, haven't tested it). The web user interface is the new (testing) branch. The firefox issues are known, seems like it has a problem with sizing of scrollable divs. Need to look into that when I find time to do that. This is from the ztex thread. With "old version" I meant the master branch that works in the console. I used it to run my 5 Icarus and for my 3 ztex I used the BTCMiner in another console. I now switched to the testing branch on Windows 7 with Python 3.2 and so far it works fine. I have created my own worker sources and noticed it is not possible to assign workers to worker sources, or maybe I just didn't figure out how it works. In my pools I usually setup two workers, one for icarus one for ztex. The login would usually be username.ztex or username.icarus on the pools. This way I can also monitor their performance separately in the pools, and via mobile app on the phone for instance. Would this be something that could be done? What is the idea behind having Blockchains? Now there is only one, the Bitcoin blockchain. And all you can do is set the name and a timeout. Autodetect Icarus: on windows it seems you can use HARDWARE\\DEVICEMAP\\SERIALCOMM to check for the serial ports, then send some test data to the ones with "Prolific" to see if they are indeed Icarus boards. http://eli.thegreenplace.net/2009/07/31/listing-all-serial-ports-on-windows-with-python/ Edit: Here is code that seems to work with other OS too, but it's from 2007: http://bitpim.svn.sourceforge.net/viewvc/bitpim/trunk/bitpim/src/comscan.py?view=markup Finding the PL2303s is not really an issue, but I the Icarus protocol doesn't allow for any quick and easy probing whether it's actually an Icarus board. You would have to open the port, send some work, wait for the board to find a nonce and check if it's valid. This means that the probing would take quite some time because you don't get an immediate response, and you would have to send lots of data, which might badly confuse the device if it turns out to not be an Icarus at all. I'd rather not risk breaking some other devices that happen to be connected to the same host that way. PL2303s are just too common. Blockchains are used for long poll aggregation, to reduce stales. If one pool inside a blockchain reports a new block, MPBM discards the jobs that are in the queue from all other pools of that blockchain as well, even if those pools haven't realized that a new block was found yet. This means that P2Pool needs to be in a separate blockchain, but all regular bitcoin mining pools should share one. It currently is not possible to map workers to work sources, because this would make work buffering even more complex, would be error prone, and probably increase latencies enough to produce some more stales. What would this be good for at all? What should a worker do if its assigned work source just doesn't manage to produce work at that very moment? Sit there and idle instead of taking jobs from other sources that are waiting in the queue? You can measure a worker's behavior far more accurately inside MPBM than any pool can. There are JSON APIs for that as well, if you want to hook up something external. MPBM currently does not archive these statistics yet, but that's a feature that might be added at some point (and I'd really appreciate it if other developers could help out with that). Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on March 24, 2012, 01:53:20 PM I created a logger via the Frontend with the default settings. It creates the file mpbm.log but it has a file size of 0, and nothing is ever logged to it.
I shut down MPBM, deleted the file, and started MPBM again, but still the same. New file, no logs written to it. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 24, 2012, 02:31:50 PM I created a logger via the Frontend with the default settings. It creates the file mpbm.log but it has a file size of 0, and nothing is ever logged to it. I shut down MPBM, deleted the file, and started MPBM again, but still the same. New file, no logs written to it. What did you set the log level to? 500 should be the default, and 300-1000 is a reasonable range, depending on what you actually want to be logged. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on March 24, 2012, 03:42:27 PM I had it set to the default 500 before, but now it's at 300 and still not logging anything. Is the number in square brackets [300] the log level in the output?
I have some showing up with 350, 400 or also 500 - but nothing is written to the log. At this moment I'd like to log everything, so that I can review the logs after a while and look for errors etc. Code: 2012-03-24 23:40:26.037 [500] Eclipse: Got 60 jobs Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 24, 2012, 03:49:13 PM I had it set to the default 500 before, but now it's at 300 and still not logging anything. Is the number in square brackets [300] the log level in the output? I have some showing up with 350, 400 or also 500 - but nothing is written to the log. At this moment I'd like to log everything, so that I can review the logs after a while and look for errors etc. Yes, the number in square brackets is the log level. The console shows loglevel <= 500 messages by default. If you want even more verbose logging, go for loglevel 1000. The log file is not flushed immediately, so python might buffer some kilobytes internally. Is there still no content after shutting down the miner with ctrl+c? This works perfectly fine for me (on linux though). Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on March 24, 2012, 03:52:01 PM Still nothing after shutting down with Ctrl-C. I have also deleted the file just to make sure it's not locked or something. It is recreated, but with 0kb and again nothing after Ctrl-C. I'll let it run over night and see if there is anything logged by tomorrow. But it was running for hours with logging enabled and log level 500, so it should have already logged something during the past few hours.
Good night. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on March 25, 2012, 02:34:54 AM Still no log. I also tried python run-mpbm.py > my.log, but this also results in a 0 kb file. That's very strange. Since it was git which created my directories, I copied the whole MPBM folder to another location and replaced all permissions with my own 'Full' permissions, this didn't make a difference. I am really puzzled, but I guess it's not really a bug in your code if piping the command doesn't work either.
What worked, in the same command prompt (run as Administrator) is "dir > my.log" or creating a new file with "edit my.log" and writing something to it. Maybe it's python which doesn't have permission somehow? Anyway, this is VERY low priority but I just thought I'd report back. Now I just found this: Code: 2012-03-25 10:35:10.694000 [100]: Core: Could not start frontend Untitled log file logger: Traceback (most recent call last): Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 25, 2012, 10:52:44 AM Still no log. I also tried python run-mpbm.py > my.log, but this also results in a 0 kb file. That's very strange. Since it was git which created my directories, I copied the whole MPBM folder to another location and replaced all permissions with my own 'Full' permissions, this didn't make a difference. I am really puzzled, but I guess it's not really a bug in your code if piping the command doesn't work either. What worked, in the same command prompt (run as Administrator) is "dir > my.log" or creating a new file with "edit my.log" and writing something to it. Maybe it's python which doesn't have permission somehow? It logs to stderr, not stdout, which explains why piping it that way doesn't work. Anyway, this is VERY low priority but I just thought I'd report back. Now I just found this: Code: 2012-03-25 10:35:10.694000 [100]: Core: Could not start frontend Untitled log file logger: Traceback (most recent call last): I think you just caught it! Need to fix that. This would explain why it only works on Python 2.x, which I'm currently running on. Fix will be pushed in a minute. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on March 25, 2012, 01:13:05 PM How do I get the fixed code without overwriting my config or other files?
git clone git://github.com/TheSeven/Modular-Python-Bitcoin-Miner.git -b testing Or something else? By the way, the ZTEX hotplug manager points to the X6500 firmware file. modules/fpgamining/x6500/firmware/x6500.bit The file doesn't actually exist if I am not wrong and I assume I am currently mining with the bit stream that was already programmed into my ztex boards before. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 25, 2012, 08:35:28 PM How do I get the fixed code without overwriting my config or other files? git clone git://github.com/TheSeven/Modular-Python-Bitcoin-Miner.git -b testing Or something else? git pull By the way, the ZTEX hotplug manager points to the X6500 firmware file. modules/fpgamining/x6500/firmware/x6500.bit The file doesn't actually exist if I am not wrong and I assume I am currently mining with the bit stream that was already programmed into my ztex boards before. I just fixed the default value for that. That setting should point to the directory where the bit files are, which are needed to boot the FPGA if it was power cycled. As long as it's running those files won't be touched. Also, no MCU firmware will ever be programmed to the board, just an FPGA bitstream (that matches the currently installed MCU firmware) if neccessary. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 26, 2012, 12:30:09 AM I've just released MPBM v0.1.0beta
Please test it, and report any issues that you encounter, so that I can take care of them. We should probably have some place for howtos, especially explaining how to install required drivers on windows. In order to run MPBM on ztex/x6500 boards, you'll need a libusb driver, which I haven't packaged yet. I've made some packages for windows users who haven't got Python installed, see the first post. Can somebody who doesn't have the neccessary stuff installed on his system yet please try these out? If I test them locally, I never know if they're really self-contained or if something just picked up a library that was present on my system anyway. Just extract both zip files to the same directory and run mpbm.exe. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coretechs on March 26, 2012, 03:31:38 AM Just upgraded the instance I was using for my X6500s. I added the workers and pool to my config but I'm getting the following error for each board:
Code: 2012-03-25 23:28:17.791608 [100]: X6500 worker 4: Proxy: Exception caught: Traceback (most recent call last): Also I am unable to kill the process with ctrl-c, it just keeps getting jobs. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: bitcowok on March 26, 2012, 05:31:51 AM same for me, a whole heap of "Proxy died!".
I dont get the "no module named usb" error (i have pyusb-1.0.0_alpha1 installed with my distro's package management) running using: Code: python run-mpbm.py --detect-workers --detect-frontends last few lines of output (theres pages...): Code: 2012-03-26 13:26:06.749902 [500]: X6500 board AH00WOWJ: Proxy: FPGA 1: Spartan 6 LX150 - Firmware: rev 0, build 0 I'm assuming a bitstream file is missing. (which is correct, i'm managing bitstreams myself) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 26, 2012, 08:57:44 AM Just upgraded the instance I was using for my X6500s. I added the workers and pool to my config but I'm getting the following error for each board: Code: 2012-03-25 23:28:17.791608 [100]: X6500 worker 4: Proxy: Exception caught: Traceback (most recent call last): Also I am unable to kill the process with ctrl-c, it just keeps getting jobs. Did you upgrade from v0.0.4 to v0.1.0beta, or just from v0.1.0alpha (testing branch) to v0.1.0 beta? Did you previously use the D2XX driver or PyUSB? Have you installed PyUSB correctly for the Python version you're running MPBM on? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 26, 2012, 08:59:13 AM same for me, a whole heap of "Proxy died!". I dont get the "no module named usb" error (i have pyusb-1.0.0_alpha1 installed with my distro's package management) running using: Code: python run-mpbm.py --detect-workers --detect-frontends last few lines of output (theres pages...): Code: 2012-03-26 13:26:06.749902 [500]: X6500 board AH00WOWJ: Proxy: FPGA 1: Spartan 6 LX150 - Firmware: rev 0, build 0 I'm assuming a bitstream file is missing. (which is correct, i'm managing bitstreams myself) Your assumption is correct. Just put the right bitstream there, or disable bitstream upload at all (which means you have to boot the boards manually). Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on March 26, 2012, 10:52:07 AM Pulled the latest version and works without problems. Logging to the log file now also works. I can stop the miner with Ctrl-C.
Here are a couple of errors I am getting, but everything seems to work fine though. Code: 2012-03-26 18:45:18.245000 [100]: Ztex board 04A3469722: Proxy: Exception caught: Traceback (most recent call last): Code: 2012-03-26 18:48:46.573000 [200]: ABCPool long poll failed: Traceback (most recent call last): Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: BR0KK on March 26, 2012, 11:28:49 AM Hi, tried to use the windows-runtime-v0.1.0beta on my windows 7 x86 FPGA Miner. I'm unable to run the mpbm.exe on my computer.
Displaying that error message (it's German): http://www.abload.de/thumb/bildschirmfoto2012-03pk2wv.png (http://www.abload.de/image.php?img=bildschirmfoto2012-03pk2wv.png) It says that the Version of this Program is not compatible with my Windows System (Windows 7 x86 w. latest Drivers and System updates) and that i should look if my computer is x86 or x64. (That could all be part of the "MAC OSX Lion + Parallels + VM" Problem so it is not important that this works :)) On my experimental GPU Miner (Windows 7 x64) the program seems to be ok but I'm also unable to start it. When i try to start the mpbm.exe (via cmd) it displays an error: http://www.abload.de/thumb/bildschirmfoto2012-03tlu28.png (http://www.abload.de/image.php?img=bildschirmfoto2012-03tlu28.png) Are there any basic instructions how to run that program? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 26, 2012, 01:03:38 PM Hi, tried to use the windows-runtime-v0.1.0beta on my windows 7 x86 FPGA Miner. I'm unable to run the mpbm.exe on my computer. Displaying that error message (it's German): http://www.abload.de/thumb/bildschirmfoto2012-03pk2wv.png (http://www.abload.de/image.php?img=bildschirmfoto2012-03pk2wv.png) It says that the Version of this Program is not compatible with my Windows System (Windows 7 x86 w. latest Drivers and System updates) and that i should look if my computer is x86 or x64. (That could all be part of the "MAC OSX Lion + Parallels + VM" Problem so it is not important that this works :)) I just realized that I actually compiled this for 64bit. On my experimental GPU Miner (Windows 7 x64) the program seems to be ok but I'm also unable to start it. When i try to start the mpbm.exe (via cmd) it displays an error: http://www.abload.de/thumb/bildschirmfoto2012-03tlu28.png (http://www.abload.de/image.php?img=bildschirmfoto2012-03tlu28.png) Are there any basic instructions how to run that program? You need to merge the contents of those two zip files, not put them in separate folders. Then it'll magically work, and you can access it at http://localhost:8832 (user: admin, password: mpbm) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 26, 2012, 01:06:50 PM Pulled the latest version and works without problems. Logging to the log file now also works. I can stop the miner with Ctrl-C. Here are a couple of errors I am getting, but everything seems to work fine though. Code: 2012-03-26 18:45:18.245000 [100]: Ztex board 04A3469722: Proxy: Exception caught: Traceback (most recent call last): This part looks like two workers are fighting for some boards, or the hotplug worker has detected boards that are currently being controlled by some other software. I need to know some more details about your configuration to figure out what exactly is going on. Code: 2012-03-26 18:48:46.573000 [200]: ABCPool long poll failed: Traceback (most recent call last): That's just a dropped long poll connection from the pool (due to them restarting something?), nothing to worry about. MPBM will just reconnect it. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on March 26, 2012, 01:37:48 PM I have these longpoll errors frequently with ABCPool, so unless they are having issues at this moment I suspect there is something wrong. I didn't see it happen with the alpha version, but I don't have a log file to check.
I don't have any other miner working in the background. I just power cycled my ztex boards and reprogrammed them, still the same. It only happens in the beginning a couple of times, but strangely not for all the boards. I just restarted MPBM and it happened 4 times in total, 3 time with with my board *C7 and only 1 time with my board *22. Not at all with my 3rd board *E9. Edit: the ABCPool longpoll error also happens on the alpha version. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coretechs on March 26, 2012, 04:07:16 PM Just upgraded the instance I was using for my X6500s. I added the workers and pool to my config but I'm getting the following error for each board: Code: 2012-03-25 23:28:17.791608 [100]: X6500 worker 4: Proxy: Exception caught: Traceback (most recent call last): Also I am unable to kill the process with ctrl-c, it just keeps getting jobs. Did you upgrade from v0.0.4 to v0.1.0beta, or just from v0.1.0alpha (testing branch) to v0.1.0 beta? Did you previously use the D2XX driver or PyUSB? Have you installed PyUSB correctly for the Python version you're running MPBM on? I upgraded from 0.0.4 by doing a git pull. I have the D2XX driver installed (older version as recommended, though I did try a later one to rule that out) and had configured PyUSB in the past based on the guide on fpgamining.com. When creating the workers in the new version, it automatically saves them using PyUSB even if I try to specify D2XX on the worker config. I assume I have some configuration issue I went back to 0.0.4 and it loads with no problems and the boards function as expected. BTW this is running on Mint 11 (ubuntu) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 26, 2012, 05:44:10 PM I upgraded from 0.0.4 by doing a git pull. I have the D2XX driver installed (older version as recommended, though I did try a later one to rule that out) and had configured PyUSB in the past based on the guide on fpgamining.com. When creating the workers in the new version, it automatically saves them using PyUSB even if I try to specify D2XX on the worker config. I assume I have some configuration issue I went back to 0.0.4 and it loads with no problems and the boards function as expected. BTW this is running on Mint 11 (ubuntu) OK, I'll fix that. However it looks like this is purely a display issue, the workers should actually accept that setting, just show the wrong one when reading it back. This means that it should actually mine correctly... does it? BTW I'd strongly recommend switching to PyUSB. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: BR0KK on March 26, 2012, 10:11:40 PM It's finally running but I'm having difficulties running more than one board. My FPGA Miner VM goes right into Bluescreen Of Death when more than one board is connected while starting mpbm.
http://www.abload.de/thumb/bildschirmfoto2012-03euktq.png (http://www.abload.de/image.php?img=bildschirmfoto2012-03euktq.png)http://www.abload.de/thumb/bildschirmfoto2012-03s1kp8.png (http://www.abload.de/image.php?img=bildschirmfoto2012-03s1kp8.png) Could this be because all the boards use the same serial number? (While flashing them with BTCMiner for cluster mode all the boards get the same number assigned to them. Not shure how to change that back?) I leave the donations on while I'm testing this miner btw. :) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 26, 2012, 10:17:43 PM urgh... ztex, WHAT THE HELL!? what's the point of a serial number!?
MPBM won't like that at all. As far as I can tell the hotplug worker will ignore all but one which have the same serial. Instantiating multiple of them manually will make all hell break loose, effectively ending up in that bluescreen (by triggering a windows or libusb bug apparently). You'll probably have to assign them different serial numbers again. Ask ztex for instructions, I have no clue. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on March 26, 2012, 11:06:01 PM It's finally running but I'm having difficulties running more than one board. My FPGA Miner VM goes right into Bluescreen Of Death when more than one board is connected while starting mpbm. http://www.abload.de/thumb/bildschirmfoto2012-03euktq.png (http://www.abload.de/image.php?img=bildschirmfoto2012-03euktq.png)http://www.abload.de/thumb/bildschirmfoto2012-03s1kp8.png (http://www.abload.de/image.php?img=bildschirmfoto2012-03s1kp8.png) Could this be because all the boards use the same serial number? (While flashing them with BTCMiner for cluster mode all the boards get the same number assigned to them. Not shure how to change that back?) I leave the donations on while I'm testing this miner btw. :) What is the exact command you use the program them for cluster mode? (and you only need to do it once in their lifetime if I am not wrong) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: BR0KK on March 26, 2012, 11:37:09 PM Quote Programming one device: java -cp ZtexBTCMiner-120208.jar BTCMiner -m p -f ztex_ufm1_15d2.ihx -s 01-02-01 Reprogramming that specific device: java -cp ZtexBTCMiner-120208.jar BTCMiner -m p -ps 01-02-01 -f ztex_ufm1_15d2.ihx Reprogramming all devices that had been programmed with the firmware .....: java -cp ZtexBTCMiner-120208.jar BTCMiner -m p -pt ztex_ufm1_15d2 -f ztex_ufm1_15d2.ihx Somewhere between these steps it must have happened...... -s is the serial number of a device (it could be anything even a name) I took one of the boards serial numbers when I tried to run this for the first time:) <--- had no clue what I was doing then..... When I run BTCminer with the option -I i get this printout: http://www.abload.de/thumb/unbenannt01105.png (http://www.abload.de/image.php?img=unbenannt01105.png) See .... Every board uses the same Serial number ..... I might ask Ztex how to change that. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on March 26, 2012, 11:41:35 PM Quote Programming one device: java -cp ZtexBTCMiner-120208.jar BTCMiner -m p -f ztex_ufm1_15d2.ihx -s 01-02-01 Reprogramming that specific device: java -cp ZtexBTCMiner-120208.jar BTCMiner -m p -ps 01-02-01 -f ztex_ufm1_15d2.ihx Reprogramming all devices that had been programmed with the firmware .....: java -cp ZtexBTCMiner-120208.jar BTCMiner -m p -pt ztex_ufm1_15d2 -f ztex_ufm1_15d2.ihx Somewhere between these steps it must have happened...... -s is the serial number of a device (it could be anything even a name) I took one of the boards serial numbers when I tried to run this for the first time:) <--- had no clue what I was doing then..... When I run BTCminer with the option -I i get this printout: Pic is comming soon;) You could always just copy and paste the output, no pic needed. Can't you just unplug all your devices but one, then program with a new serial number? Rinse and repeat for all your boards. Problem fixed. I am not very experienced with the programming mode, so I can't think of any other solution for now. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: BR0KK on March 26, 2012, 11:51:27 PM I'm on an iPhone right now. Pics are easier to make :D
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: bitcowok on March 27, 2012, 06:03:16 AM I'm assuming a bitstream file is missing. (which is correct, i'm managing bitstreams myself) Your assumption is correct. Just put the right bitstream there, or disable bitstream upload at all (which means you have to boot the boards manually).Any clues as to disabling bitstream upload? (or how to configure anything at all?) I see a "config" directory with a default.cfg which seems to be a binary format (what the?) the old version had a config.py or similar which was nicely commented. I see no such file with this release, unless i'm missing something obvious. I'm fairly sure i've read the whole thread, and of course first post still says documentation "coming soon...". perhaps a wiki is in order? Thanks -bitcowok Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 27, 2012, 12:50:59 PM I'm assuming a bitstream file is missing. (which is correct, i'm managing bitstreams myself) Your assumption is correct. Just put the right bitstream there, or disable bitstream upload at all (which means you have to boot the boards manually).Any clues as to disabling bitstream upload? (or how to configure anything at all?) I see a "config" directory with a default.cfg which seems to be a binary format (what the?) the old version had a config.py or similar which was nicely commented. I see no such file with this release, unless i'm missing something obvious. There is no such thing any more. The new configuration store is a Python pickle, so that it is easily machine read/write/editable. Configuration is now done through user interface modules, currently only WebUI supports that: http://localhost:8832 (user: admin, password: mpbm) I'm fairly sure i've read the whole thread, and of course first post still says documentation "coming soon...". perhaps a wiki is in order? Thanks -bitcowok Yes, a wiki sounds like a plan. Maybe put it into http://wiki.btcfpga.com (http://wiki.btcfpga.com)? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: O_Shovah on March 27, 2012, 08:25:52 PM Hello everybody,
As promised i release some images and data of my FPGA family at its daily work. The setup (please excuse the messy workbench) http://img26.imageshack.us/img26/7428/miningsetup.png (http://imageshack.us/photo/my-images/26/miningsetup.png/) [From left to right: ARM board "Gumstix" (the first i developed on), Icarus(rev0),120mmfan ,x6500(rev2),120mmfan,Pandaboard ES(revB2),Bitforce single(1.0)] And the mining data thanks to TheSeven http://img41.imageshack.us/img41/6237/webuiscreenshot.png (http://imageshack.us/photo/my-images/41/webuiscreenshot.png/) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: macbook-air on March 27, 2012, 10:45:34 PM MPBM's support of fallback pools is the best. Any idea to make it support phatk2 video card mining?
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 27, 2012, 10:49:07 PM MPBM's support of fallback pools is the best. Any idea to make it support phatk2 video card mining? Well, in theory you should be able to rip the relevant parts of code out of poclbm or some other python gpu miner, and implant it into MPBM as a worker module. I'd figure that this should probably be an out of process worker module like ztex/x6500, to prevent GIL congestion and have some isolation to prevent a buggy GPU driver from taking down the whole MPBM instance.Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: hashking on March 28, 2012, 02:50:12 AM I just recieved 3 x6500 boards and 2 of them work fine but one of them I keep getting
X6500 A4014OEH: Error while booting board: Traceback (most recent call last): 2012-03-26 16:29:52.619000: File "worker\fpgamining\x6500.pyc", line 194, in main 2012-03-26 16:29:52.619000: File "worker\fpgamining\util\fpga.pyc", line 83, in detect 2012-03-26 16:29:52.619000: File "worker\fpgamining\util\jtag.pyc", line 90, in detect 2012-03-26 16:29:52.619000: File "worker\fpgamining\util\jtag.pyc", line 331, in _readIdcodes 2012-03-26 16:29:52.619000: File "worker\fpgamining\util\jtag.pyc", line 166, in read_dr 2012-03-26 16:29:52.619000: File "worker\fpgamining\util\jtag.pyc", line 163, in shift_dr 2012-03-26 16:29:52.619000: File "worker\fpgamining\util\jtag.pyc", line 170, in read_tdo 2012-03-26 16:29:52.619000: File "worker\fpgamining\util\ft232r.pyc", line 203, in read_data 2012-03-26 16:29:52.619000: File "worker\fpgamining\util\ft232r.pyc", line 163, in write 2012-03-26 16:29:52.619000: File "worker\fpgamining\util\ft232r.pyc", line 410, in write 2012-03-26 16:29:52.619000: File "usb\legacy.pyc", line 148, in bulkWrite 2012-03-26 16:29:52.619000: File "usb\core.pyc", line 619, in write 2012-03-26 16:29:52.619000: File "usb\backend\libusb01.pyc", line 474, in bulk_write 2012-03-26 16:29:52.619000: File "usb\backend\libusb01.pyc", line 556, in __write 2012-03-26 16:29:52.619000: File "usb\backend\libusb01.pyc", line 384, in _check 2012-03-26 16:29:52.619000: USBError: [Errno None] libusb0-dll:err [_usb_reap_async] timeout error 2012-03-26 16:29:52.619000: 2012-03-26 16:29:52.619000: My other two work fine. I am using Windows 7 64 bit. Downloaded the software off of fpgamining.com. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 28, 2012, 03:29:59 AM I just recieved 3 x6500 boards and 2 of them work fine but one of them I keep getting X6500 A4014OEH: Error while booting board: Traceback (most recent call last): 2012-03-26 16:29:52.619000: File "worker\fpgamining\x6500.pyc", line 194, in main 2012-03-26 16:29:52.619000: File "worker\fpgamining\util\fpga.pyc", line 83, in detect 2012-03-26 16:29:52.619000: File "worker\fpgamining\util\jtag.pyc", line 90, in detect 2012-03-26 16:29:52.619000: File "worker\fpgamining\util\jtag.pyc", line 331, in _readIdcodes 2012-03-26 16:29:52.619000: File "worker\fpgamining\util\jtag.pyc", line 166, in read_dr 2012-03-26 16:29:52.619000: File "worker\fpgamining\util\jtag.pyc", line 163, in shift_dr 2012-03-26 16:29:52.619000: File "worker\fpgamining\util\jtag.pyc", line 170, in read_tdo 2012-03-26 16:29:52.619000: File "worker\fpgamining\util\ft232r.pyc", line 203, in read_data 2012-03-26 16:29:52.619000: File "worker\fpgamining\util\ft232r.pyc", line 163, in write 2012-03-26 16:29:52.619000: File "worker\fpgamining\util\ft232r.pyc", line 410, in write 2012-03-26 16:29:52.619000: File "usb\legacy.pyc", line 148, in bulkWrite 2012-03-26 16:29:52.619000: File "usb\core.pyc", line 619, in write 2012-03-26 16:29:52.619000: File "usb\backend\libusb01.pyc", line 474, in bulk_write 2012-03-26 16:29:52.619000: File "usb\backend\libusb01.pyc", line 556, in __write 2012-03-26 16:29:52.619000: File "usb\backend\libusb01.pyc", line 384, in _check 2012-03-26 16:29:52.619000: USBError: [Errno None] libusb0-dll:err [_usb_reap_async] timeout error 2012-03-26 16:29:52.619000: 2012-03-26 16:29:52.619000: My other two work fine. I am using Windows 7 64 bit. Downloaded the software off of fpgamining.com. Hm, USB communication trouble... Wild guess: Bad cable? Might also be all kinds of other shit though. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: hashking on March 28, 2012, 03:32:28 AM I switched the cable with one of the good ones and its the same thing. The other 2 work great. Once it gets going then I get this.
X6500 A4014OEL: Discovering FPGA 0... 2012-03-27 22:33:25.213000: X6500 A4014OEL: Error while booting board: Traceback (most recent call last): 2012-03-27 22:33:25.213000: File "worker\fpgamining\x6500.pyc", line 194, in main 2012-03-27 22:33:25.213000: File "worker\fpgamining\util\fpga.pyc", line 83, in detect 2012-03-27 22:33:25.213000: File "worker\fpgamining\util\jtag.pyc", line 88, in detect 2012-03-27 22:33:25.213000: NoDevicesDetected X6500 A4014OEL: Reading FPGA temperatures failed: list index out of range Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 28, 2012, 03:34:35 AM I've made some packages for windows users who haven't got Python installed, see the first post. Can somebody who doesn't have the neccessary stuff installed on his system yet please try these out? If I test them locally, I never know if they're really self-contained or if something just picked up a library that was present on my system anyway. Just extract both zip files to the same directory and run mpbm.exe. http://img38.imageshack.us/img38/576/mpbmw.jpg (http://imageshack.us/photo/my-images/38/mpbmw.jpg/) Interesting... I need to check why this is happening tomorrow. Temporary workaround: Move that dll file into c:\windows\system32 (on 32bit windows) or c:\windows\syswow64 (on 64bit windows). Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: hashking on March 28, 2012, 03:37:43 AM Is this a bad board?
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on March 28, 2012, 03:50:29 AM Is this a bad board? If your other two boards work, and switching around the cables, changing the socket on the USB hub, switching around power supply etc doesn't work, then that would be my guess. I'd mail to support@fpgamining.com and see if they have any other ideas what the problem might be. I haven't personally used the X6500 yet, but it may just be something stupid. I forgot to switch my Icarus boards ON since I was used to Ztex boards which don't have a on/off switch. You plug them in and they start mining (if the software is already running). This reminds me, I should test if Ztex hotplug really works with MPBM (edit: working very well). Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on March 28, 2012, 04:07:31 AM I've had my Icarus + Ztex combo up and running with MPBM for 1D 12h now.
I'd like to understand some of the numbers. For instance, why are cancelled jobs on the Ztex boards 11.50%, 14.58% and 13.61% vs. only between 1.11% and 1.16% on my Icarus boards? The 'GHashes total' on the Icarus seems lower per FPGA (ie. Ztex 28290 vs. Icarus 25045) than on the Ztex, but then the jobs per hour seems higher (Ztex 240-250 Icarus 308-318). Do any other numbers seem off in the screenshot? I realize that Slush has a lot of upload errors. The timeout is 5 now (default), would increasing that possibly solve that problem? 5 seems already very long to me. http://image.bayimg.com/lannpaadj.jpg Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on March 28, 2012, 12:01:01 PM So far the only thing that shows up in my log file (log level 300) with 'long poll' or 'longpoll' is those error messages. How can I actually confirm that long polling is working? Canceled Jobs = long polling works?
Code: 2012-03-26 23:23:20.042000 [200]: ABCPool long poll failed: Traceback (most recent call last): I have two other pools (slush + eclipse) but as said nothing that confirms any long polling in my log file. And long polling with ABCPool works with Ztex BTCMiner. I'd like to see a message in the logs when a long poll is received. Is that possible? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 28, 2012, 01:52:02 PM There are two libusb implementations, both called the same thing but incompatible with each other. This actually shouldn't matter for MPBM. PyUSB (which MPBM relies on) supports both libusb versions, and something called openusb, which I think is apple's own libusb equivalent. So you might possibly get away without any libusb at all. Gotta run now... Antirack, I'll explain the stats to you later today. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 28, 2012, 02:28:39 PM So far the only thing that shows up in my log file (log level 300) with 'long poll' or 'longpoll' is those error messages. How can I actually confirm that long polling is working? Canceled Jobs = long polling works? Canceled jobs do not necessarily mean that long polling actually works, because MPBM tries to detect new blocks by other means as well. Code: 2012-03-26 23:23:20.042000 [200]: ABCPool long poll failed: Traceback (most recent call last): I have two other pools (slush + eclipse) but as said nothing that confirms any long polling in my log file. And long polling with ABCPool works with Ztex BTCMiner. This message does not mean that long polling does not work at all. It just means that a long poll connection died without getting a response. MPBM will automatically reconnect it, so if you only get that message occasionally, this is probably just a sign of a slightly unstable pool, connection issues (bad router? have seen this before...) or just someone restarting something on the pool side. I'd like to see a message in the logs when a long poll is received. Is that possible? If you increase the loglevel to 500, you should occasionally see these messages: Code: <Pool name>: Got <job number> jobs from long poll response Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 28, 2012, 02:56:50 PM I've had my Icarus + Ztex combo up and running with MPBM for 1D 12h now. I'd like to understand some of the numbers. For instance, why are cancelled jobs on the Ztex boards 11.50%, 14.58% and 13.61% vs. only between 1.11% and 1.16% on my Icarus boards? A Ztex board takes about twice as long to process a job than an Icarus. This means that the probability that a job is hit by a long poll is twice as high. The actual probability for a job to be canceled on an Icarus should be around 1.3% on average, twice that on Ztex. So your Icarus numbers look perfectly fine to me. The reason that your Ztex boards show higher numbers is a bit more complicated: MPBM fetches new work as soon as the number of jobs in the queue that expire in more than 10 seconds goes below some threshold. However, if jobs are received in bursts due to X-Roll-NTime, it's rather likely that all jobs in the queue have the same expiry time, and that this is somewhere between 10 (fetcher threshold) and 15 (Ztex board job processing time) seconds in the future. Because of this, there are no jobs with a remaining life of >15 seconds in the queue, and the Ztex board is forced to work on a job that it can't possibly finish in time. As soon as the remaining jobs cross the 10 second boundary, MPBM will fetch new jobs, and as soon as the remaining life of the accepted job hits zero, the board will behave as if a long poll came in, cancel its current job and get a new one (with longer life). To account for network latencies, a safety margin of about 5 seconds is subtracted from the expiry time reported by the pool before inserting the jobs into the queue. TL;DR: This is caused by MPBMs inner workings, and nothing to worry about. The 'GHashes total' on the Icarus seems lower per FPGA (ie. Ztex 28290 vs. Icarus 25045) than on the Ztex, but then the jobs per hour seems higher (Ztex 240-250 Icarus 308-318). This is partially caused by the effect I described above, and partially by the fact that MPBM pushes new work to the boards about 1 second before the board actually exhausts the noncerange of the previous job, because none of the boards that we have today support real queueing of jobs (which means we need to do this to prevent the board from idling briefly between jobs). This absolute time value doesn't depend on the hashrate, and thus offsets the number of jobs against the number of gigahashes. Do any other numbers seem off in the screenshot? I realize that Slush has a lot of upload errors. The timeout is 5 now (default), would increasing that possibly solve that problem? 5 seems already very long to me. 5 Seconds should be plenty. If a pool fails to respond within this timeframe, I'd avoid that pool. I wouldn't increase that timeout, because that would decrease MPBM's aggressiveness to deliver a share, thereby possibly causing more stales, especially if the timeout was not caused by the pool software being overloaded, but rather by network packet loss (retrying is likely to be faster than waiting for the protocol layer to detect the packet loss, trigger retransmissions, and finally get a response). However it seems like stales are still within a reasonable margin on this instance, so I wouldn't care too much about those retries. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: BR0KK on March 30, 2012, 10:59:41 PM Somehow i'm unable to get it running.... Ztex told me how to revert my "serial number problem" and every board has back its unique one. When i start mpbm (the windows packaged) on my VM the hot plug worker recognizes the 5 Boards. But they are in some kind of constant reconnection loop. The don't start mining since they are kicked out of the work immediately when the connect to it.
even one board doesn't function with it (and it did before)? Some Screens (I'm on an iPad so I'm only able to make screenshots): http://www.abload.de/thumb/bildschirmfoto2012-03hx5c4.png (http://www.abload.de/image.php?img=bildschirmfoto2012-03hx5c4.png)http://www.abload.de/thumb/bildschirmfoto2012-038x07u.png (http://www.abload.de/image.php?img=bildschirmfoto2012-038x07u.png) It could be som VM related problems .... so its not neccecary that this works:) I'm only curious whats the cause of this is? Ill hook them to my gnu miner if i have some time tomorrow. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 30, 2012, 11:52:31 PM Somehow i'm unable to get it running.... Ztex told me how to revert my "serial number problem" and every board has back its unique one. When i start mpbm (the windows packaged) on my VM the hot plug worker recognizes the 5 Boards. But they are in some kind of constant reconnection loop. The don't start mining since they are kicked out of the work immediately when the connect to it. even one board doesn't function with it (and it did before)? Some Screens (I'm on an iPad so I'm only able to make screenshots): http://www.abload.de/thumb/bildschirmfoto2012-03hx5c4.png http://www.abload.de/thumb/bildschirmfoto2012-038x07u.png It could be som VM related problems .... so its not neccecary that this works:) I'm only curious whats the cause of this is? Ill hook them to my gnu miner if i have some time tomorrow. That's the result of a typo in the ztex bitstream upload code. Apparently nobody has ever tested this before, and I can't do it myself because I don't have a board and ztex doesn't want to cooperate with me. I have pushed a fix for that particular bug to the testing branch, however I'm not sure if this was the only problem with that code. There's likely more to it, if this indeed was never tested before. If you haven't done that yet, you'll probably need to extract the bitstream files from BTCMiner and put them into the directory that you specified as the firmware path for that worker. As a workaround, you can let another miner software upload the bitstream for now, and then switch to MPBM. This will be neccessary after every power cycle of the boards. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on March 31, 2012, 12:38:21 AM BR0KK, before starting MPBM, fire up BTCMiner via command line and wait till all the boards are configured and it starts mining.
Then press Control-C to exit. Now start MPBM. This should fix the problem. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 31, 2012, 12:55:05 AM BR0KK, before starting MPBM, fire up BTCMiner via command line and wait till all the boards are configured and it starts mining. Then press Control-C to exit. Now start MPBM. This should fix the problem. Well, it's a workaround. A fix would be if I'd finally get a board from ztex to test this kind of stuff properly. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on March 31, 2012, 01:50:30 AM I just pulled the latest code and tried it with the .bit file in the MPBM directory and the path (not filename, since the fn is set automatically it seems) set in the hotplug manager. Got this error (in addition to the "Can not open the specified device, possibly because it is already in use"):
Code: 2012-03-31 09:46:20.445000 [100]: File "C:\Modular-Python-Bitcoin-Miner\modules\theseven\ztex\boardproxy.py", line 75, in run Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: BR0KK on March 31, 2012, 11:56:02 AM The Seven where do you come from? Not from Germany or somewhere near that?
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 31, 2012, 12:04:01 PM The Seven where do you come from? Not from Germany or somewhere near that? From exactly that :)Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: BR0KK on March 31, 2012, 12:43:59 PM Hm Ztex won't give u one for free for this ..... Would at least remote access to one help u?
May be Somerset of us Ztex owners could provide a board for testing? Kickstarter ? Also mein VM Miner leuft 24/7 Und ich have Zugriff via teamviewer darauf. Wenns hilft kann ich dich drauf lassen? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on March 31, 2012, 04:04:31 PM Hm Ztex won't give u one for free for this ..... Would at least remote access to one help u? I still don't quite understand why he doesn't give me a free one for this, because he once stated he would offer free boards to mining software developers, but apparently he has changed his mind and tries to even prevent third party software support these days. And yes, remote access would help, but I'll probably need some kind of a "board power cycling agent" at the other end of the tunnel to test the bitstream upload part. May be Somerset of us Ztex owners could provide a board for testing? Kickstarter ? Someone actually tried to raise a non-negligible bounty for cgminer ztex support, but as of now I don't know of any efforts to do that for MPBM. cgminer is just much more popular. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: BR0KK on March 31, 2012, 10:54:16 PM Quote And yes, remote access would help, but I'll probably need some kind of a "board power cycling agent" at the other end of the tunnel to test the bitstream upload part. Remote Access its easy to give but the remote shutdown isn't. I currently do not own an IP - switchable power plug (IP Steckdose). Maybe i can find something the next time i'm at saturn or mediamarkt?. Couldn't be that expensive? My Setup is somewhat complicated (Mac --> Parallels 7 --> Windows 7). I hope that won't have an effect on your programing? (I only have a windows VM, but i could install a Linux for that?). Doing it directly on the mac isn't possible because mac osx LION does have some wierd problems with teamviewer 7 beta (all the other versions i've tried are not working properly to) and i literally lack any experience with UNIX or linux at all. Tell me where u are from with a pm. Maybe we can work something out :) I'm trying to get a new board soon (or more if i could raise the money)...... Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on March 31, 2012, 11:37:59 PM The BountyChest effort to get a ztex board for Con in Australia fr cgminer development didn't go anywhere. They are going to "refund" the people at one point as far as I know from mjt (bountychest dev).
If I didn't understand this wrong, with ztex's discount program you would have to buy your ztex board, then write the software, and then once done he would decide how much credit you get in form of a refund to your bank account. http://www.ztex.de/os_discount_program.e.html You will get the money refunded (via bank wire transfer to a European EUR account or via Paypal) after the project is published and rated. You'd also have to publish it on his wiki etc and link back to ztex on the MPBM website/thread to qualify. And the way his discount program sounds, a "simple" miner (which effectively duplicates functionality that's already there with his own open source project) wouldn't score very high on his 15% to >50% discount table IMHO. I have to be absolutely honest here, if I would only have ztex boards I would probably never have tried MPBM. Now that I am using it, I see a couple of great and unique features (ie the way it handles work sources/blockchains). But I can also understand ztex for discouraging third party miner use, he has to cover his ass for the 2 years warranty and if somebody fries the FPGA chips it will be very costly to replace the boards. The main advantage (to me) in having a third party miner would actually be to get it to work on platforms with a very low resource/power footprint. But I don't know enough about Python to say if that would be possible. I always liked xiangfu's approach of running his cgminer with 40+ Icarus in a mini dlink router that's not much bigger than a pack of cigarettes. This won't happen with Java. But would this be possible with python for instance? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on March 31, 2012, 11:48:23 PM Remote Access its easy to give but the remote shutdown isn't. I currently do not own an IP - switchable power plug (IP Steckdose). Maybe i can find something the next time i'm at saturn or mediamarkt?. Couldn't be that expensive? BROKK, Remote Power Switch made in Germany (retail price Euro 399.00, I had a few of their 8 port a few years ago in a server cabinet): http://www.ebay.de/itm/Leunig-Remote-Power-Switch-4G-/160772462474?pt=DE_Computer_Peripherie_Netzwerk&hash=item256ec9178a This one is also cool (but probably dodgy and low quality). Control your power socket with a SIM card via a mobile phone. http://www.ebay.de/itm/New-Fashion-Cellphone-Phone-PDA-GSM-RC-Remote-Control-Socket-Power-Switch-DD-/150764040585?pt=LH_DefaultDomain_77&hash=item231a3cb189 It's kind of universal, but it doesn't show what kind of male plugs it has on the back, so you may need to use a travel adapter to make the setup even more dodgy and the risk of burning down your house even higher. PS: Although I am not from Germany and actually far far away, I am another native German speaker ;) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: BR0KK on March 31, 2012, 11:57:32 PM there is something similar from allnet (or other companies) thats far cheaper than this :) (i can't afford to pay 600€ for one purpose, if i had that money i could buy two and send one to TheSeven; but I'm out of money since i invested in 5 Ztex Boards last month).
Had one at my old workplace and its was controllable via Browser IP. I remember it costs a blot 60 -100€ or even less. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on April 01, 2012, 12:01:15 AM I checked their price list. New price Euro 399. The one on eBay costs Euro 150 and is 4 port. But I get your point. Probably overdoing it for a home setup with a few FPGA boards. If you control servers you need something robust, that's why they are still in business even with those prices.
(The allnet thing is 8A max, the Leunig one 16A continues and 120A tops). Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: fizzisist on April 01, 2012, 12:23:29 AM Another option might be the low tech version: hang out on IRC with TheSeven and he can initiate a power cycle by typing:
Code: Hey BR0KK, can you power cycle the board for me? :P Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on April 01, 2012, 12:30:25 AM Another option might be the low tech version: hang out on IRC with TheSeven and he can initiate a power cycle by typing: Code: Hey BR0KK, can you power cycle the board for me? :P Buying new tech toys is way more fun! Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on April 01, 2012, 01:18:50 AM The BountyChest effort to get a ztex board for Con in Australia fr cgminer development didn't go anywhere. They are going to "refund" the people at one point as far as I know from mjt (bountychest dev). If I didn't understand this wrong, with ztex's discount program you would have to buy your ztex board, then write the software, and then once done he would decide how much credit you get in form of a refund to your bank account. http://www.ztex.de/os_discount_program.e.html You will get the money refunded (via bank wire transfer to a European EUR account or via Paypal) after the project is published and rated. You'd also have to publish it on his wiki etc and link back to ztex on the MPBM website/thread to qualify. And the way his discount program sounds, a "simple" miner (which effectively duplicates functionality that's already there with his own open source project) wouldn't score very high on his 15% to >50% discount table IMHO. He mentioned up to 100% for mining software on his forum thread at some point. I have to be absolutely honest here, if I would only have ztex boards I would probably never have tried MPBM. Now that I am using it, I see a couple of great and unique features (ie the way it handles work sources/blockchains). But I can also understand ztex for discouraging third party miner use, he has to cover his ass for the 2 years warranty and if somebody fries the FPGA chips it will be very costly to replace the boards. This is why MPBM 100% replicates ztex's clocking behavior. The main advantage (to me) in having a third party miner would actually be to get it to work on platforms with a very low resource/power footprint. But I don't know enough about Python to say if that would be possible. I always liked xiangfu's approach of running his cgminer with 40+ Icarus in a mini dlink router that's not much bigger than a pack of cigarettes. This won't happen with Java. But would this be possible with python for instance? That's very well possible, but not with ztex boards, those cause too much host CPU usage due to offloading the error rate measurement and clock adjustment to the host. With Icarus or BFL boards MPBM should easily handle two figure board numbers on ARM platforms. It might need quite a bit of RAM, but not all that much CPU. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: BR0KK on April 01, 2012, 11:14:43 AM Quote Quote from: fizzisist on Today at 12:23:29 AM Another option might be the low tech version: hang out on IRC with TheSeven and he can initiate a power cycle by typing: Code: Hey BR0KK, can you power cycle the board for me? Buying new tech toys is way more fun! Defently possible and yes buing new hardware is my hobby :D Since im not home all day we have to work sonething out. Maybe in the evenings ? I work at a restaurant atm. so it could get late ..... If i get a new job in some weeks that shouldnt be a problem anymore. Quote That's very well possible, but not with ztex boards, those cause too much host CPU usage due to offloading the error rate measurement and clock adjustment to the host. With Icarus or BFL boards MPBM should easily handle two figure board numbers on ARM platforms. It might need quite a bit of RAM, but not all that much CPU. I ordered a rasberry pi for the ztex boards yesterday. I will try to run the Ztex boards with it.... hope to get this thing soon. For 30€ its worth a try ;) Did you try it? Is it impossible to run this boards with an arm powered device? What are the sideffects? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: O_Shovah on April 01, 2012, 11:57:59 AM I am running mpbm, p2pool and the bitcoin clients on ARM boards for some time now very sucessfull.
There is the Gumstix, the Panda board and other. I just dint get a rasberry yet. I will offer a system for it too as soon as i get one. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: antirack on April 01, 2012, 12:17:14 PM I am running mpbm, p2pool and the bitcoin clients on ARM boards for some time now very sucessfull. There is the Gumstix, the Panda board and other. I just dint get a rasberry yet. I will offer a system for it too as soon as i get one. How many FPGA boards do you have connected, which ones, and how about CPU load etc? If you'd build a bigger cluster, what would you use? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: O_Shovah on April 01, 2012, 02:04:10 PM Highly depends on if you use p2pool or a pool.
I had 7 boards connected at maximum. This resultet in ~ 55% CPU for the Gumstix and ~12 % on the Panda. Running a p2pool server seems limited to the Pandaboard but is also highly influenced by SD card I/O performance. It then uses something like 40% CPU. The Gumstix uses 4W maximum on the wall and could be plugged on top of a modular board. (Measueres something like 50 by 20 mm) But the panda board is easier to develop for and uses 7,5 W. In additionis has a dual core so paralelising threads is easier. Therefore i would recommend The panda baord for bigger setups with USB connectors and the Gumstix for modular board approaches. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on April 01, 2012, 09:35:23 PM 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 Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: hashking on April 03, 2012, 06:02:06 AM I have the version .4a for windows. How can I install the new version..
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on April 03, 2012, 07:25:59 AM
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: BR0KK on April 03, 2012, 06: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 :)
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on April 03, 2012, 06:42:00 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. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: BR0KK on April 03, 2012, 07:23:04 PM Uhh Licensing; thats complicated....Hope that you can arrange something with Ztex. If u need Accesss to a board sometimes just ask :)
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: hashking on April 04, 2012, 01:53:52 AM Which pools is this program optimized for?
Title: Re: Modular Python Bitcoin Miner - Official Thread - HELP! Post by: Garr255 on April 05, 2012, 01:35:07 AM 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 Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on April 05, 2012, 02:39:07 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. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: freshzive on April 06, 2012, 04:35:42 AM Is this version working properly with p2pool (using x6500s)? Just wanted to make sure before I upgrade from that pesky v0.0.4alpha
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on April 06, 2012, 05:35:13 AM TheSeven, any ideas when we can expect a non beta release?
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on April 06, 2012, 11:53:44 AM 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. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on April 06, 2012, 11:58:23 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. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: freshzive on April 06, 2012, 03:40:57 PM Any idea what causes this? It seems to crash python.
Code: 2012-04-06 08:40:00.470180 [100]: Core: Starting up... Edit: It actually starts up, but all of my x6500s show this: Code: X6500 board AH00WOVX: Proxy: Exception caught: Traceback (most recent call last): 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 Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on April 06, 2012, 06:04:11 PM Any idea what causes this? It seems to crash python. Code: 2012-04-06 08:40:00.470180 [100]: Core: Starting up... Edit: It actually starts up, but all of my x6500s show this: Code: X6500 board AH00WOVX: Proxy: Exception caught: Traceback (most recent call last): 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? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: hashking on April 07, 2012, 01:05:25 PM Anyone using the program to work with GPUMAX. I can't get mine to connect. What are your settings for source?
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on April 07, 2012, 08:42:04 PM 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. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: Garr255 on April 07, 2012, 10:28:15 PM 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. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coblee on April 09, 2012, 03:20:02 AM 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. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coretechs on April 09, 2012, 03:46:19 AM 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): 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. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: Garr255 on April 09, 2012, 04:40:19 AM Try the testing branch. It seems to fix that error.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: fizzisist on April 09, 2012, 04:53:52 AM 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. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coblee on April 09, 2012, 05:48:15 AM 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): Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: Garr255 on April 09, 2012, 06:23:28 AM Make a new directory and do a
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. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: hashking on April 09, 2012, 08:19:30 PM 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. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: fizzisist on April 09, 2012, 08:58:12 PM 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. 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. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: hashking on April 09, 2012, 09:03:07 PM 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. 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. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on April 09, 2012, 09:38:43 PM 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. 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. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coblee on April 10, 2012, 12:29:18 AM Using the testing branch, I get this error on my Mac:
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 Any ideas? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coretechs on April 10, 2012, 05:01:10 AM 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 Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on April 10, 2012, 10:30:16 AM Using the testing branch, I get this error on my Mac: 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 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. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on April 10, 2012, 10:32:34 AM 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. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coblee on April 10, 2012, 03:51:55 PM Using the testing branch, I get this error on my Mac: 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 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] Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on April 10, 2012, 06:23:59 PM Hm, that looks like a Python or OpenUSB/LibUSB/PyUSB bug. You might want to try a different Python/PyUSB version.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coblee on April 10, 2012, 06:27:37 PM 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. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coblee on April 11, 2012, 03:25:24 AM 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. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on April 11, 2012, 11:04:31 AM 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 :) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: freshzive on April 12, 2012, 05:06:00 AM 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. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coblee on April 12, 2012, 05:33:09 AM 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. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: hashking on April 12, 2012, 06:22:34 PM It seems like Im getting a very high rate of rejects on gpumax. Over 10%. Is this normal.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on April 12, 2012, 07:51:36 PM It seems like Im getting a very high rate of rejects on gpumax. Over 10%. Is this normal. It definitely isn't. There were some GPUMAX issues that have been fixed in the past, but it looks like we missed some :/ However, as the GPUMAX guys refuse to send me an invite since months, I can't really do anything about that. >:( Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: LoWang on April 13, 2012, 03:30:27 PM 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. Hello Coblee I wrote you several times in the offical LTC thread, then I PM you but you still don't respond. I wrote you private message on #litecoin IRC but you ignored it. Are you that busy or is there some other reason why you ignore me? Thank you Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coblee on April 13, 2012, 04:13:45 PM 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. Hello Coblee I wrote you several times in the offical LTC thread, then I PM you but you still don't respond. I wrote you private message on #litecoin IRC but you ignored it. Are you that busy or is there some other reason why you ignore me? Thank you Sorry for ignoring you, I will send you PM. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: hashking on April 14, 2012, 02:12:29 PM It seems like Im getting a very high rate of rejects on gpumax. Over 10%. Is this normal. It definitely isn't. There were some GPUMAX issues that have been fixed in the past, but it looks like we missed some :/ However, as the GPUMAX guys refuse to send me an invite since months, I can't really do anything about that. >:( I can let you borrow my gpumax account so you can fix the issues with it. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: Garr255 on April 15, 2012, 07:51:09 AM I already offered, he seems convinced to convince the gpumax guys to give him one of his own :P
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: hashking on April 15, 2012, 04:28:13 PM This would be a very important item to fix for this miner. Would a bounty to fix this speed up things.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: BR0KK on April 16, 2012, 10:03:48 AM Im preparing to get one of the newly announced Ztex 1.15y Quad Spartan Boards. If i have it in my hands you could have a look at it when u like (for implementing support into MPBM) As i described i could offer u Remote Access to all of my Boards via Teamviewer etc :)
€: Got one yesterday and its hashing nicely since then :P Could you get anything new about Ztex and your licensing problem? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: hashking on May 02, 2012, 02:32:12 AM Here is the error I keep getting with GPUMAX. Can you please fix this. Thanks.
2012-05-01 21:30:15.310 [200] GPUMAX: Error while fetching job: Traceback (most recent call last): File "C:\Users\Desktop\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\core\actualworksource.py", line 155, in get_job jobs = self._get_job() File "C:\Users\Desktop\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\theseven\bcjsonrpc\bcjsonrpcworksource.py", line 120, in _get_job conn.request("POST", self.settings.path, req, headers) File "c:\Program Files (x86)\Python32\lib\http\client.py", line 964, in request File "c:\Program Files (x86)\Python32\lib\http\client.py", line 1002, in _send_request File "c:\Program Files (x86)\Python32\lib\http\client.py", line 960, in endheaders File "c:\Program Files (x86)\Python32\lib\http\client.py", line 805, in _send_output File "c:\Program Files (x86)\Python32\lib\http\client.py", line 743, in send File "c:\Program Files (x86)\Python32\lib\http\client.py", line 721, in connect File "c:\Program Files (x86)\Python32\lib\socket.py", line 386, in create_connection socket.gaierror: [Errno 11004] getaddrinfo failed Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on May 02, 2012, 08:26:44 AM Here is the error I keep getting with GPUMAX. Can you please fix this. Thanks. 2012-05-01 21:30:15.310 [200] GPUMAX: Error while fetching job: Traceback (most recent call last): File "C:\Users\Desktop\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\core\actualworksource.py", line 155, in get_job jobs = self._get_job() File "C:\Users\Desktop\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\theseven\bcjsonrpc\bcjsonrpcworksource.py", line 120, in _get_job conn.request("POST", self.settings.path, req, headers) File "c:\Program Files (x86)\Python32\lib\http\client.py", line 964, in request File "c:\Program Files (x86)\Python32\lib\http\client.py", line 1002, in _send_request File "c:\Program Files (x86)\Python32\lib\http\client.py", line 960, in endheaders File "c:\Program Files (x86)\Python32\lib\http\client.py", line 805, in _send_output File "c:\Program Files (x86)\Python32\lib\http\client.py", line 743, in send File "c:\Program Files (x86)\Python32\lib\http\client.py", line 721, in connect File "c:\Program Files (x86)\Python32\lib\socket.py", line 386, in create_connection socket.gaierror: [Errno 11004] getaddrinfo failed This looks like a GPUMAX-side or configuration problem that I can't do anything about. It basically means that the DNS name that the work source is using could not be resolved. Judging from the GPUMAX thread it has been pretty much dead recently, with most IP addresses locked out, so could it be just that? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: nbtcminer on May 04, 2012, 09:12:54 PM Can anyone help me out with some reqs / initial setup instructions on how to get a BFL single to work with MPBM 0.1.0? Thanks in advance for the help!
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on May 04, 2012, 11:13:45 PM Can anyone help me out with some reqs / initial setup instructions on how to get a BFL single to work with MPBM 0.1.0? Thanks in advance for the help! Which operating system? On Linux it's mostly "plug the BFLs, unzip MPBM, start it, configure the pools etc.". Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: nbtcminer on May 05, 2012, 11:04:52 AM Can anyone help me out with some reqs / initial setup instructions on how to get a BFL single to work with MPBM 0.1.0? Thanks in advance for the help! Which operating system? On Linux it's mostly "plug the BFLs, unzip MPBM, start it, configure the pools etc.". Sorry forgot to add that important part in; Windows 7 Pro X64 Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on May 05, 2012, 01:40:52 PM Install the FTDI drivers (just like for any other BFL miner software), and then either:
1. install python and pyserial, clone mpbm git 2. use prebuilt package from the first post of this thread (a bit outdated right now) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: shad on May 11, 2012, 08:54:09 PM mpbm latest testing from github running on openwrt Attitude Adjustment (r30753)
i think python and pyusb are the only packages needed Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: macbook-air on May 12, 2012, 12:09:07 PM I've just got my BFL Single, but MPBM reports frequent "Bad ZDX response", and the mining speed is only around 500 MH/s. cgminer also does have a similar problem. Code: 2012-05-12 20:00:17.670746 [ 0]: Modular Python Bitcoin Miner v0.1.0beta, Copyright (C) 2012 Michael Sparmann (TheSeven) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on May 12, 2012, 01:57:09 PM Looks like it occasionally misses a ZFX command. Could be either a bug in the usb-serial driver, or a firmware bug on the BFL itself, or faulty hardware.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: shad on May 12, 2012, 08:35:50 PM anyone got an idea how i get infos like average mhash/sec into mrtg?
any output interfaces? didn't look really, hoping that anyone did it before :D Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on May 13, 2012, 02:50:25 AM anyone got an idea how i get infos like average mhash/sec into mrtg? any output interfaces? didn't look really, hoping that anyone did it before :D There is a munin plugin for MPBM (http://pastie.org/3903092), using its JSON API. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coblee on May 14, 2012, 05:16:32 PM i am running it on an Buffalo WRZ-HP-AG300H-EU, it uses around 40MB-Ram openwrt+miner (i didn't get it running on my linksys wrt54gl because of to few diskspace) installation on OpenWRT Quote opkg update opkg install phyton opkg install libncurses opkg install libncursesw opkg install libusb rmmod ftdi_sio python miner.py bitstream was already installed, will try installing bitstream over openwrt later I just installed OpenWRT (on a TP-Link MR3020) and got the latest MPBM to run. Here are a few other packages I needed: Code: opkg install pyusb The miners will come up as /dev/ttyUSB# Run 'ls /dev/ttyUSB*' and you will see them. Mine are /dev/ttyUSB0, /dev/ttyUSB1, /dev/ttyUSB2, /dev/ttyUSB3 And this is what you put in the PORT field when you configure a worker in MPBM Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: Garr255 on May 14, 2012, 07:34:50 PM Thanks coblee. I'm glad that router is working for you.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on May 15, 2012, 01:35:10 AM Is anyone else having an issue with the latest git mpbm version whereby the web management interface freezes after some time. The only solution is to close the browser and restart. This happens with Chrome. With Firefox the web interface looks all messed up - overlapping text..etc.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: fizzisist on May 15, 2012, 02:29:56 AM Is anyone else having an issue with the latest git mpbm version whereby the web management interface freezes after some time. The only solution is to close the browser and restart. This happens with Chrome. With Firefox the web interface looks all messed up - overlapping text..etc. Are you leaving the browser window open all day? I think something happens when the scrollback on the log gets too long. Reducing the log level should help with that (Settings button on the top right corner). I like 300 or 400 personally, but I also just close the MPBM window when I'm not actively using it anyway. I'm sure TheSeven has a better explanation for it, but that's what I do to avoid the problem at least. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on May 15, 2012, 02:57:17 AM Is anyone else having an issue with the latest git mpbm version whereby the web management interface freezes after some time. The only solution is to close the browser and restart. This happens with Chrome. With Firefox the web interface looks all messed up - overlapping text..etc. Are you leaving the browser window open all day? I think something happens when the scrollback on the log gets too long. Reducing the log level should help with that (Settings button on the top right corner). I like 300 or 400 personally, but I also just close the MPBM window when I'm not actively using it anyway. I'm sure TheSeven has a better explanation for it, but that's what I do to avoid the problem at least. Yes that's what I was doing. I've had the log level set to the default 500. I dialed it down to 300 now. I like to keep the window open just to keep an eye on the invalid shares percentage and overall hashrate. But I guess it's not absolutely necessary that I keep it open 24/7. Is there any docs anywhere that explains the differences between the various log levels. I see that 300 displays only accepted shares unlike 500 which displays a lot more detail. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: fizzisist on May 15, 2012, 03:28:31 AM Is anyone else having an issue with the latest git mpbm version whereby the web management interface freezes after some time. The only solution is to close the browser and restart. This happens with Chrome. With Firefox the web interface looks all messed up - overlapping text..etc. Are you leaving the browser window open all day? I think something happens when the scrollback on the log gets too long. Reducing the log level should help with that (Settings button on the top right corner). I like 300 or 400 personally, but I also just close the MPBM window when I'm not actively using it anyway. I'm sure TheSeven has a better explanation for it, but that's what I do to avoid the problem at least. Yes that's what I was doing. I've had the log level set to the default 500. I dialed it down to 300 now. I like to keep the window open just to keep an eye on the invalid shares percentage and overall hashrate. But I guess it's not absolutely necessary that I keep it open 24/7. Is there any docs anywhere that explains the differences between the various log levels. I see that 300 displays only accepted shares unlike 500 which displays a lot more detail. A munin plugin or some simplified interface that only shows the stats you want ("bonks" showed me one he wrote that I like quite a bit) might be a better way to accomplish this. Even cooler would be if a talented web designer wrote an overhaul of the WebUI to make it super snazzy. :) This could be color coding for important stats, the option to turn off columns or move columns around, and a fix for that Firefox compatibility problem. Log levels can be figured out by looking at the log messages themselves. For example: Code: 2012-05-14 20:18:59.212 [200] X6500 board AH01A6D7 FPGA0 sent K-not-zero share 68dc3054 The [200] in the bracket shows the minimum log level that this message would be displayed for. Once again, I'm sure TheSeven has a better explanation. :) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on May 15, 2012, 04:23:50 AM Thanks for your help fizzisist :)
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: hashking on May 15, 2012, 10:06:55 PM Does the overclocker firmware raise the clocks by itself? I know it lowers them if the board gets to hot.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: fizzisist on May 15, 2012, 10:27:38 PM Does the overclocker firmware raise the clocks by itself? I know it lowers them if the board gets to hot. Yeah, it should raise them as well, but I believe this is done pretty conservatively. I recommend setting the starting clock to 200 MHz and the maximum clock to 250 MHz and letting it run for a few hours to stabilize. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: hashking on May 15, 2012, 10:35:35 PM Does the overclocker firmware raise the clocks by itself? I know it lowers them if the board gets to hot. Yeah, it should raise them as well, but I believe this is done pretty conservatively. I recommend setting the starting clock to 200 MHz and the maximum clock to 250 MHz and letting it run for a few hours to stabilize. What is considered a safe temperature for this board. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on May 15, 2012, 10:45:20 PM Just as a side note lowering the log level to 350 did the trick for me - ie the web interface no longer crashes..3 days and still going (before it would crash after after day or less)
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: fizzisist on May 15, 2012, 11:07:00 PM Does the overclocker firmware raise the clocks by itself? I know it lowers them if the board gets to hot. Yeah, it should raise them as well, but I believe this is done pretty conservatively. I recommend setting the starting clock to 200 MHz and the maximum clock to 250 MHz and letting it run for a few hours to stabilize. What is considered a high temperature for this board. MPBM has default values of 45 C for "warning" and 55 C for "critical." I would say these are good values, but if you are running a more power consuming bitstream later (like eldentyrell's forthcoming one), you might want to lower these values, since the offset between the PCB temp and the FPGA die will be a little higher. For now, aim to keep it under 45, and under 40 is even better. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: freshzive on May 23, 2012, 02:39:41 AM So I got my ubuntu 12.04 setup working nicely with MPBM. The new (rev3?) units load up flawlessly. However, when loading older units, I get this error just after the firmware finishes uploading and it tries to wake up the FPGAs:
Code: 2012-05-22 19:38:08.719 [100] AH00WOVL: Traceback (most recent call last): Obviously the older revs didn't have temp sensors, so I'm not sure what to do about this? Guessing there's some easy fix that I'm not thinking of. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on May 23, 2012, 03:58:05 AM That's a regression on the testing branch as of about 3 days ago, which managed to slip through my testing.
Run "git reset --hard 21575deb675015e20e0ec68958e595e49c6988db" to go back to a working revision for now until I fix this later today. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: O_Shovah on May 24, 2012, 10:55:09 AM Hello
Its me again ;) Two little issues i ran into again. First my x6500: Code: self.core.event(350, self.children[0], "temperature", fpga0 * 1000, "%f \xc2\xb0C" % fpga0, worker = self.children[0]) Second the Butterfly auto manager: If i hook up two Butterfly boxes to the miner they react in a strange way. They start some kind of flic flacing the work between the two boards so one is doing nothing while the other is on full. A few seconds later its the other way around I just get them to work if manually define workers for each of them. Any ideas ? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: fizzisist on May 24, 2012, 06:13:56 PM Hello Its me again ;) Two little issues i ran into again. First my x6500: Code: self.core.event(350, self.children[0], "temperature", fpga0 * 1000, "%f \xc2\xb0C" % fpga0, worker = self.children[0]) This looks like the same problem that freshzive ran into. See: That's a regression on the testing branch as of about 3 days ago, which managed to slip through my testing. Run "git reset --hard 21575deb675015e20e0ec68958e595e49c6988db" to go back to a working revision for now until I fix this later today. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on May 25, 2012, 02:18:07 AM I don't know if anyone else is having this issue but one of my singles is showing odd performance metrics. The Accepted Shared, Cancelled Shares, Accepted jobs, etc are all heavily disproportionate when compared to the first one. This is BFL Single 2 that is doing this. I've attached a screenshot.
Any help is greatly appreciated! Maybe I need to tune the pool settings a bit? I'm mining with btc guild. As you can see the first single is doing ok. I've downclocked the second single as it was throttling but the slightly lower speed (825 mhs) does not explain the odd performance - or at least it should not. http://img546.imageshack.us/img546/3718/screenshot2sn.png Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on May 25, 2012, 02:55:36 AM Update:
Hmm, well I flashed the formerly throttling unit back up to the stock 832 firmware and the previous issue with rejected jobs and shares disappeared..it seems running these things at differing hashrates (asynchronously) is not such a good idea. This could be an issue with the mining software, but I don't know for sure at this point. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on May 25, 2012, 08:49:35 AM I think it's highly unlikely that there is an issue with multiple BFLs running at different speeds. I'd rather suspect that the "slower" BFL's firmware just doesn't work properly.
If you want to nail this issue down, can you please try running only the "slower" single (with the slower firmware) for some hours and give me the ghashes total, accepted jobs and accepted shares numbers? Or you could also try running both of them with the slower firmware to check if both go nuts in that case :) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on May 26, 2012, 06:42:09 PM I think it's highly unlikely that there is an issue with multiple BFLs running at different speeds. I'd rather suspect that the "slower" BFL's firmware just doesn't work properly. If you want to nail this issue down, can you please try running only the "slower" single (with the slower firmware) for some hours and give me the ghashes total, accepted jobs and accepted shares numbers? Or you could also try running both of them with the slower firmware to check if both go nuts in that case :) Sure, I'll do that next week as I'm moving the cooler running single to a different location. Then I'll be able to run the hotter (the one that I had to originally downclock) single all by itself using the 825 firmware. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: O_Shovah on May 28, 2012, 11:38:08 AM I think it's highly unlikely that there is an issue with multiple BFLs running at different speeds. I'd rather suspect that the "slower" BFL's firmware just doesn't work properly. If you want to nail this issue down, can you please try running only the "slower" single (with the slower firmware) for some hours and give me the ghashes total, accepted jobs and accepted shares numbers? Or you could also try running both of them with the slower firmware to check if both go nuts in that case :) Sure, I'll do that next week as I'm moving the cooler running single to a different location. Then I'll be able to run the hotter (the one that I had to originally downclock) single all by itself using the 825 firmware. Could you give me the two temperatures of you singles and the room temperature. I would like to have some comparison. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on May 28, 2012, 12:58:18 PM Room temp 27C
Single 1: 47.50 Single 2: 51.20 Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: O_Shovah on June 06, 2012, 09:27:13 PM So maybe a picture of my current (nonpermanent) setup of watercooled FPGA boards wich are manged by MPBM
http://img515.imageshack.us/img515/7880/setupc.png (http://imageshack.us/photo/my-images/515/setupc.png/) .... 2,4 Gh/s .. @ 200 W ... nom nom nom And thanks a lot to TheSeven for all the bugfixing he is doing for me as i seem to come around with bugs and errors most frequently ;) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: gr0bi42 on June 08, 2012, 08:35:00 AM So maybe a picture of my current (nonpermanent) setup of watercooled FPGA boards wich are manged by MPBM http://img515.imageshack.us/img515/7880/setupc.png (http://imageshack.us/photo/my-images/515/setupc.png/) .... 2,4 Gh/s .. @ 200 W ... nom nom nom And thanks a lot to TheSeven for all the bugfixing he is doing for me as i seem to come around with bugs and errors most frequently ;) What kind of CPU-board is this? Looks not like an Rasberry-PI. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: O_Shovah on June 08, 2012, 09:05:24 AM Its a Pandaboard ES running Ubuntu ARM and my ports of bitcoin-qt/bitcoind and mpbm.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: Zeronic on June 13, 2012, 06:33:46 PM Has anyone been able to setup MPBM via VMware, I know VM sometime doesn't see some USB devices. Windows 7 x64 Host with a Linux VM.
Also what Linux distro would allow me to startup in text mode and then startx in to a GUI (make it easy for me to setup MPBM then leave it low resource mode). I like this with some of the older version of Red Hat, but not seen any others that allow for this. Thanks in Advance. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: freshzive on June 13, 2012, 08:02:59 PM Does MPBM performance deteriorate over time? Or is that the x6500s?
I notice that when I start MPBM (w/ 6 x6500s), performance is in the 2300-2400Mhash range (as reported by my pool). After about a week of running, it seems to have slowly dropped to around 2000-2100Mhash. MPBM looks fine and all my miners are still submitting shares, so it just seems there is a slight deterioration in performance over time. This is in Ubuntu 12.04. Restarting Ubuntu and loading MPBM (firmware on miners is also reloaded) seems to restore the original, faster hashrate. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: TheSeven on June 13, 2012, 09:20:16 PM Does MPBM performance deteriorate over time? Or is that the x6500s? I notice that when I start MPBM (w/ 6 x6500s), performance is in the 2300-2400Mhash range (as reported by my pool). After about a week of running, it seems to have slowly dropped to around 2000-2100Mhash. MPBM looks fine and all my miners are still submitting shares, so it just seems there is a slight deterioration in performance over time. This is in Ubuntu 12.04. Restarting Ubuntu and loading MPBM (firmware on miners is also reloaded) seems to restore the original, faster hashrate. Which bitstream are you using? Are there any signs of a memory leak, i.e. increasing memory usage over time? Are there situations where it shows shitloads of "got <count> jobs from <work source>" on the console? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: rjk on June 13, 2012, 09:25:07 PM I notice that when I start MPBM (w/ 6 x6500s), performance is in the 2300-2400Mhash range (as reported by my pool). It's most likely that the pool is being overly optimistic at the beginning.Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: hashking on June 14, 2012, 03:51:56 PM Can anyone help me with a step by step instruction on how to get a bfl to work with this miner on windows.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: hashking on June 16, 2012, 12:38:12 AM I guess no one has used any BFL singles with this miner on windows.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: cablepair on June 16, 2012, 02:28:41 AM Only REV1 BFL Singles work with MPBM
a worker module for the REV3 has been on do list but TheSeven just hasnt gotten around to it yet. So unless you have all BFL REV1 singles they will not work with MPBM however all versions of the ModMiner Quad will. :) If you need help getting either one working with MPBM please dont hesitate to ask Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: coretechs on June 16, 2012, 05:10:33 AM Only REV1 BFL Singles work with MPBM a worker module for the REV3 has been on do list but TheSeven just hasnt gotten around to it yet. So unless you have all BFL REV1 singles they will not work with MPBM That isn't true. I have rev.3 singles and they have worked just fine with MPBM since the first time I plugged them in. I am running linux though, so if you are referring to a Windows-specific problem you may want to be more explicit with your statement. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: O_Shovah on June 16, 2012, 12:05:51 PM I guess no one has used any BFL singles with this miner on windows. I can do a testing on it today if you realy prefere windows. Otherwise i would strongly recommend you to use ubuntu or another debian flavour of linux wich mpbm was originally written for. In that case i may give you a detailed stepguide. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: ebereon on June 17, 2012, 11:45:27 AM Currently trying to use the Icarus side of the Cairnsmore1 board (57600 baud rate and SW6 1 off, 2,3,4 on) and getting the following error: "could not open port /dev/ttyUSB0: [Error 3] The system cannot find the path specified." First person to fix gets 5 btc. (I've tried USB0-6) On Windows or Linux? You say /dev/ttyUSBx... I assume you're using linux. When you plug in the unit you see the /dev/ttyUSBx (it should be 4 ttyUSB's) coming up (dmesg)? If yes try the icarus miner with baudrate 56000 (SW6 1234 on) and the standard 115200 (SW6 1 off, 234 on) on every ttyUSB for the unit. Only 2 of them are the fpga's. You have to power off the unit to take the switches work! I'm sure you already did "¯/sbin/modprobe -q ftdi-sio product=0x8350 vendor=0x0403¯" ?! sry for my bad english ;P My cairnsmore with mpbm on Windows7 32bit: http://content.wuala.com/contents/ebereon/Shared/bitcoin/mpbm_cairnsmore1.JPG?dl=1 Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: ebereon on June 17, 2012, 06:08:27 PM On windows you need to use "\\.\COMxx" not "/dev/ttyUSBx" ...
If you look in the device manager and you put the unit in, you should see COM20 - 23. So only 2 of em are the right ones. On my win7 it was COM21 and COM23. But other people have COM22 and COM23. You have to test this. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: ebereon on June 17, 2012, 06:33:46 PM 1KWGtSxo5b52Adk3Pvw14E3o9kp96JZJm2
:D Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: ebereon on June 19, 2012, 08:46:36 AM You just earned yourself 5 btc my friend. What's your address? Received! Thank you! ;D Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: mu50stang on June 20, 2012, 12:34:24 AM Does anyone know how to use the modminer with this software.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: MykelSilver on June 24, 2012, 12:12:55 PM Hi,
Is there any example configuration for solo mining with MPBM? I have now configured MPBM for pooled mining, but I cannot figure out how to mine solo with MPBM. Anyone? Thanks in advance. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: shad on June 25, 2012, 05:59:38 PM you have to direct mpbm to your local bitcoin client i guess?
shouldn't be different to using a pool Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: MykelSilver on June 25, 2012, 06:08:29 PM Is it really that simple? Thanks a lot!
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: MykelSilver on June 27, 2012, 05:13:20 PM you have to direct mpbm to your local bitcoin client i guess? shouldn't be different to using a pool I have tried your suggestion but I keep gettting this error: Local: Error while fetching job: Traceback (most recent call last): File "C:\Users\MykelSilver\Desktop\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\core\actualworksource.py", line 155, in get_job jobs = self._get_job() File "C:\Users\MykelSilver\Desktop\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\theseven\bcjsonrpc\bcjsonrpcworksource.py", line 120, in _get_job conn.request("POST", self.settings.path, req, headers) File "c:\Program Files (x86)\Python32\lib\http\client.py", line 964, in request File "c:\Program Files (x86)\Python32\lib\http\client.py", line 1002, in _send_request File "c:\Program Files (x86)\Python32\lib\http\client.py", line 960, in endheaders File "c:\Program Files (x86)\Python32\lib\http\client.py", line 805, in _send_output File "c:\Program Files (x86)\Python32\lib\http\client.py", line 743, in send File "c:\Program Files (x86)\Python32\lib\http\client.py", line 721, in connect File "c:\Program Files (x86)\Python32\lib\socket.py", line 386, in create_connection socket.gaierror: [Errno 11004] getaddrinfo failed I have configured my work source to connect to localhost:8332 Of course the bitcoin daemon is running. Unfortunately there is no documentation of its configuration file. Anyone has any luck with the configuration of the bitcoin deamon? Thanks in advance Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: shad on June 28, 2012, 10:26:42 AM #server=1 tells Bitcoin to accept JSON-RPC commands.
#server=1 # You must set rpcuser and rpcpassword to secure the JSON-RPC api #rpcuser=Ulysseys #rpcpassword=YourSuperGreatPasswordNumber_385593 did you set those? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: MykelSilver on June 28, 2012, 04:35:23 PM #server=1 tells Bitcoin to accept JSON-RPC commands. #server=1 # You must set rpcuser and rpcpassword to secure the JSON-RPC api #rpcuser=Ulysseys #rpcpassword=YourSuperGreatPasswordNumber_385593 did you set those? The MPBM webUI runs on Windows. I running the bitcoin daemon on linux I installed them in my home folder There are two files: -rwxr-xr-x. 1 mykelsilver mykelsilver 4,2M 8 mei 19:34 bitcoind -rwxr-xr-x. 1 mykelsilver mykelsilver 9,3M 8 mei 19:34 bitcoin-qt I cannot see any configuration file in ~/.bitcoin. This folder contains only the following files: drwx------. 3 mykelsilver mykelsilver 4,0K 27 jun 21:23 . drwx------. 107 mykelsilver mykelsilver 4,0K 25 jun 18:25 .. -rw-------. 1 mykelsilver mykelsilver 5,8M 27 jun 21:23 addr.dat -rw-------. 1 mykelsilver mykelsilver 1,9G 27 jun 21:10 blk0001.dat -rw-------. 1 mykelsilver mykelsilver 645M 27 jun 21:10 blkindex.dat drwx------. 2 mykelsilver mykelsilver 12K 27 jun 21:23 database -rw-------. 1 mykelsilver mykelsilver 0 3 mrt 08:26 db.log -rw-------. 1 mykelsilver mykelsilver 1,7M 27 jun 21:23 debug.log -rw-------. 1 mykelsilver mykelsilver 0 3 mrt 08:26 .lock -rw-------. 1 mykelsilver mykelsilver 88K 27 jun 21:10 wallet.dat -rw-rw-r--. 1 mykelsilver mykelsilver 46K 29 apr 18:29 wallet.dat.pgp [mykelsilver@fedora .bitcoin]$ In the configuration of my client I cannot set any username or password. In my previous post I connected through the wrong ipaddress. Now I connect to the ipaddress of the linux server It is to complex to explain all the details. Never mind. It is not possible to solo mine with MPBM for me. Anyway thanks for your patience and time. Regards, Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: MykelSilver on June 28, 2012, 04:50:10 PM Wow I works now. I had to create the bitcoin.conf file manually :D
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: freshzive on July 05, 2012, 06:18:55 AM are there any specific settings I should use with P2Pool to reduce DOA and stale %?
what do others get for stale % using P2pool with MPBM? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: binspac on July 13, 2012, 08:36:52 AM How can I get this working for BFL Singles?
My worker dropdown only shows options for the x6500. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: bonks on July 13, 2012, 08:59:25 AM How can I get this working for BFL Singles? My worker dropdown only shows options for the x6500. Git pull the latest code. I could not get the bfl manager to work so I use the individual workers. Make sure to set the path to the appropriate /dev/ttyUSB# Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: binspac on July 13, 2012, 09:22:45 AM How can I get this working for BFL Singles? My worker dropdown only shows options for the x6500. Git pull the latest code. I could not get the bfl manager to work so I use the individual workers. Make sure to set the path to the appropriate /dev/ttyUSB# I did Git it. It appears that it fails to load because I don't have pyusb or pyserial and opkg says they do not exist. This is odd because they do exist: http://www.angstrom-distribution.org/repo/?pkgname=python-pyusb http://www.angstrom-distribution.org/repo/?pkgname=python-pyserial Edit: OK, I got them installed by downloading them manually now all I need is the ftdi-sio driver but I have to save that for tomorrow. If anyone can help with the driver that would be awesome, my OS (Angstrom) didn't come with it. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: shad on July 13, 2012, 02:43:29 PM did you make "opkg update" before?
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: binspac on July 14, 2012, 07:00:22 AM Got the ftdi_sio driver and did:
Code: modprobe ftdi_sio vendor=0x0403 product=6014 But when I plug in my device it doesn't create /dev/ttyUSB0. Here is my dmesg output when plugging it in: http://pastebin.com/8hbhVxzL Can anyone help? System: WM8650 Netbook OS: Angstrom Device: BFL Single Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: teaserX on July 21, 2012, 04:34:13 PM I'm trying to make some adjustments to my MPBM webui. Can't find there right place in the code to adjust the height of the viewport for the statistics gadget. Pointing me to the right file is probably all I need. thx in advance.
EDIT: For future reference the post below is spot on. Thx. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: ebereon on July 21, 2012, 04:57:24 PM I'm trying to make some adjustments to my MPBM webui. Can't find there right place in the code to adjust the height of the viewport for the statistics gadget. Pointing me to the right file is probably all I need. thx in advance. mpbm\modules\theseven\webui\wwwroot\static\statsgadget\statsgadget.js I hope it helps. eb Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: ssateneth on July 22, 2012, 01:03:29 AM Your screenshot links to a thumbnail. Please fix to regular screenshot?
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: LazyOtto on July 22, 2012, 07:11:13 AM On OS X, using python3 and the BFL 768 firmware (merely haven't tested at other speeds yet) I had to change the following two lines in bflsingleworker.py to be successful:
starting about line 224 from: if response[:12] != "NONCE-FOUND:" or response[-1:] != "\n": to: if response[:12] != b"NONCE-FOUND:": and from: if len(nonces) != 8 and nonces[8] != b",": to: if len(nonces) != 8 and nonces[8] != 0x2c: Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: LazyOtto on July 22, 2012, 08:51:59 AM Same patch is working with the 800MH/s BFL firmware.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: binspac on July 23, 2012, 03:16:58 AM Got the ftdi_sio driver and did: Code: modprobe ftdi_sio vendor=0x0403 product=6014 But when I plug in my device it doesn't create /dev/ttyUSB0. Here is my dmesg output when plugging it in: http://pastebin.com/8hbhVxzL Can anyone help? System: WM8650 Netbook OS: Angstrom Device: BFL Single 5btc reward for someone to get this working for me, would really like to move these loud, hot, suckers elsewhere Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: O_Shovah on July 23, 2012, 10:19:28 AM Got the ftdi_sio driver and did: Code: modprobe ftdi_sio vendor=0x0403 product=6014 But when I plug in my device it doesn't create /dev/ttyUSB0. Here is my dmesg output when plugging it in: http://pastebin.com/8hbhVxzL Can anyone help? System: WM8650 Netbook OS: Angstrom Device: BFL Single 5btc reward for someone to get this working for me, would really like to move these loud, hot, suckers elsewhere I know Angström to be a little tricky here. I am using ubuntu 12.04 and have used all ubuntu distributions from 9.04 upwards. I will try to dig some free time tonight, so i may have a look at your problem. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: binspac on July 24, 2012, 12:13:21 AM The WM8650 has an ARM processor and the OS has to run from an SD card. I might buy a bigger SD card (mine is only 2GB) so I can use Debian instead of Angstrom.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: MykelSilver on August 18, 2012, 10:15:31 PM Mining using MPBM configured for a mining pool (like ozcoin / deepbit) runs fine.
I still run into trouble using MPBM configured for solo mining :-( I am currently using MPBM.EXE under windows My bitcoind is running under linux (other machine) I have created the bitcoin.conf with the rpcuser and rpcpassword supplied I run the bitcoind with bitcoin -server in a terminal When I create a new worker in MPBM with the ip adress of the machine where bitcoind runs and port 8332 and supply the rpcuser and rpcpassword, MPBM is not able to fetch jobs from bitcoind... What am I doing wrong? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: davecoin on August 28, 2012, 03:16:42 PM What is the best way to set a backup pool using mpbm? For instance, if mtred goes down, is there a way to have the program switch to another pool? I am familiar with this feature on cgminer, but I am new to mpbm.
Thanks, Dave Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: LazyOtto on August 28, 2012, 03:23:04 PM I never found a good way (one which satisfied me) to have mpbm do an actual hot/backup configuration.
However, it does an excellent job of equally sharing work among two to many work-sources. So, my suggestion, pick two pools which you find both to be satisfactory and split your shares between them. Or, Ozcoin and EclipseMC both have multiple independent servers which you can point work-sources at and then all the shares get credited to the same account. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: davecoin on August 28, 2012, 03:44:04 PM That's a good idea, thanks.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: davecoin on August 28, 2012, 04:01:02 PM Should this be of any concern?
"Discarding 120 jobs from long poll response because work buffer is full" Thanks, Dave Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: LazyOtto on August 28, 2012, 04:30:54 PM I don't think so. Just watch for a while to ensure you are getting as many shares accepted per minute as you expect. In my case, I'm getting almost exactly, or perhaps slightly better, results as I was getting with cgminer.
However, a tip, if you want to leave the monitor web page up for long periods you'll need to change the log level to something like 200 in two places. Both for the web output and for the stdout output. If you don't do that it will develop a problem (bad) in a half day to a couple of days of continuous running. -- Hmmm, just went to increase the log level for web output to verify that I also was getting those messages (I 'think' I was) and see that there is no longer a log level setting for the web gui. So, that problem may have been resolved. I'm using a version pulled straight from the git repository since I wanted to take a look at some of the work in progress. Depending on where you got your distribution there could be some minor variances. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: hashking on August 28, 2012, 09:56:15 PM Is there any newer version then this out for windows mpbm-v0.1.0beta.zip. I'm seeing alot of this lately with any pool I use and wonder if its a software issue.
50 BTC.COM: Error while fetching job: Traceback (most recent call last): File "C:\Users\\Desktop\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\core\actualworksource.py", line 155, in get_job jobs = self._get_job() File "C:\Users\\Desktop\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\theseven\bcjsonrpc\bcjsonrpcworksource.py", line 120, in _get_job conn.request("POST", self.settings.path, req, headers) File "c:\Program Files (x86)\Python32\lib\http\client.py", line 964, in request File "c:\Program Files (x86)\Python32\lib\http\client.py", line 1002, in _send_request File "c:\Program Files (x86)\Python32\lib\http\client.py", line 960, in endheaders File "c:\Program Files (x86)\Python32\lib\http\client.py", line 805, in _send_output File "c:\Program Files (x86)\Python32\lib\http\client.py", line 743, in send File "c:\Program Files (x86)\Python32\lib\http\client.py", line 721, in connect File "c:\Program Files (x86)\Python32\lib\socket.py", line 404, in create_connection File "c:\Program Files (x86)\Python32\lib\socket.py", line 395, in create_connection socket.timeout: timed out Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: LazyOtto on August 29, 2012, 07:18:30 AM How to use json to get data from MPBM.
It would have saved me quite a few hours if an example of this type had been available, so, here it is for anyone else who might be looking. The 'magic' involved is having to set the headers on the request in order to receive a non-null response. E.g., curl <url> -d "1" -H "DNT: 1" -H "If-Modified-Since:Sat, 1 Jan 2000 00:00:00 GMT" -H "Content-Type:application/json" You can find examples of required <url> in the Python example below. This gives a quick test to ensure the web-server / mpbm is working before you get bogged down in "why is urllib3 throwing that exception?". :) (BTW, "requests" is a third party library. Free to use it seems. You can find it if you need it.) -- #!/usr/bin/env python # -*- coding: utf-8 -*- # Path hack. import sys import os sys.path.insert(0, os.path.abspath('..')) import json import unittest import pickle import tempfile from pprint import pprint import datetime import time import requests from requests.compat import str, StringIO from requests import HTTPError from requests import get, post, head, put from requests.auth import HTTPBasicAuth, HTTPDigestAuth from requests.exceptions import InvalidURL # curl <url> -d "1" -H "DNT: 1" -H "If-Modified-Since:Sat, 1 Jan 2000 00:00:00 GMT" -H "Content-Type:application/json" def getDataFromMPBM(): auth = HTTPBasicAuth('admin', 'mpbm') headers = {'content-type' : 'application/json', 'DNT' : '1', 'If-Modified-Since' : 'Sat, 1 Jan 2000 00:00:00 GMT' } workerURL = 'http://host.domain.com:8832/api/statsgadget/getworkerstats' blockchainURL = 'http://host.domain.com:8832/api/statsgadget/getblockchainstats' worksourceURL = 'http://host.domain.com:8832/api/statsgadget/getworksourcestats' allURL = 'http://host.domain.com:8832/api/statsgadget/getallstats' r = requests.post(workerURL, auth=auth, data='1', headers=headers, prefetch=True) #print(json.dumps( r.json, sort_keys = True, indent = 4 ) ) workerResponse = json.loads( r.text ) #pprint( workerResponse ) return workerResponse tempHigh = 0.0 tempLow = 100.0 while( True ): workerResponse = getDataFromMPBM() startTime = datetime.datetime.fromtimestamp( workerResponse[ 'starttime' ] ) dataTime = datetime.datetime.fromtimestamp( workerResponse[ 'timestamp' ] ) upTime = dataTime - startTime tempNow = workerResponse['workers'][0]['temperature'] if tempNow < tempLow : tempLow = tempNow if tempNow > tempHigh : tempHigh = tempNow #print( upTime ) print( '{0:.1f} \tHigh: {2:.1f} \tLow: {3:.1f} \t{1}'.format( tempNow, dataTime, tempHigh, tempLow ) ) time.sleep( 9.991 ) exit() Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: fizzisist on August 29, 2012, 08:25:11 AM How to use json to get data from MPBM. It would have saved me quite a few hours if an example of this type had been available, so, here it is for anyone else who might be looking. Thanks for this, Otto. Actually, there is one example of grabbing data from the API in the munin plugin here (https://bitcointalk.org/index.php?topic=62823.msg897409#msg897409). TheSeven, might be good to add links to both of these in the OP? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: steveme on August 29, 2012, 07:47:57 PM Hi all,
I'm running mpbm 0.1.0 beta on Ubuntu 12.04 with Python 2.7.3 but when viewing it locally using Firefox or remotely using Firefox or IE it is displayed with the menu ('frontends', 'workers', 'work sources', etc) 'behind' a table displaying the donation pools, the only way I can interact with those options is to switch to 'no style' in 'view' -> 'page style' in FF I'm assuming it's a missing python package - any ideas?? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: LazyOtto on August 29, 2012, 09:02:03 PM It is actually a known problem that it doesn't work with Firefox.
Not a missing python package issue. Wouldn't know about IE, haven't used it for years. Works fine with Safari from OS X. You might try that or Opera. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: moparguy528 on August 29, 2012, 11:29:52 PM Is there any newer version then this out for windows mpbm-v0.1.0beta.zip. I'm seeing alot of this lately with any pool I use and wonder if its a software issue. 50 BTC.COM: Error while fetching job: Traceback (most recent call last): File "C:\Users\\Desktop\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\core\actualworksource.py", line 155, in get_job jobs = self._get_job() File "C:\Users\\Desktop\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\theseven\bcjsonrpc\bcjsonrpcworksource.py", line 120, in _get_job conn.request("POST", self.settings.path, req, headers) File "c:\Program Files (x86)\Python32\lib\http\client.py", line 964, in request File "c:\Program Files (x86)\Python32\lib\http\client.py", line 1002, in _send_request File "c:\Program Files (x86)\Python32\lib\http\client.py", line 960, in endheaders File "c:\Program Files (x86)\Python32\lib\http\client.py", line 805, in _send_output File "c:\Program Files (x86)\Python32\lib\http\client.py", line 743, in send File "c:\Program Files (x86)\Python32\lib\http\client.py", line 721, in connect File "c:\Program Files (x86)\Python32\lib\socket.py", line 404, in create_connection File "c:\Program Files (x86)\Python32\lib\socket.py", line 395, in create_connection socket.timeout: timed out I am seeing something similar using the latest version in Ubuntu 12.04. Doesn't matter which pool. Once this happens a few times sometimes I lose all connections to the pool. I have to restart. It seems to get worse the more x6500 units hook up to it. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: davecoin on August 30, 2012, 04:23:55 AM Hi all, I'm running mpbm 0.1.0 beta on Ubuntu 12.04 with Python 2.7.3 but when viewing it locally using Firefox or remotely using Firefox or IE it is displayed with the menu ('frontends', 'workers', 'work sources', etc) 'behind' a table displaying the donation pools, the only way I can interact with those options is to switch to 'no style' in 'view' -> 'page style' in FF I'm assuming it's a missing python package - any ideas?? I had the same issue. Try the chromium browser. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: Dexter770221 on August 30, 2012, 06:26:06 PM I'm looking, and looking and can't find how to use this software on Windows... Any help?
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: O_Shovah on August 31, 2012, 07:31:03 AM I'm looking, and looking and can't find how to use this software on Windows... Any help? You have been acting according to http://fpgamining.com/documentation/software/mpbm-windows (http://fpgamining.com/documentation/software/mpbm-windows) ?This is a guide by fizzist. If that does not work some info on your system (software) might be intresting. While Windows 7 is mostly problemless Windows XP is very nasty here. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: shad on September 23, 2012, 06:56:03 PM Status update on my miner:
1.) i always wrote that i am mining on ARM, thats not true :) sorry for that i checked cpuinfo and it's an "MIPS 24Kc V7.4" with 128MB-RAM with one X6500 OS: Openwrt RAM-Usage:56MB 2) MPBM stop working today (after i added an additional pool and made some config changes) with some "OS error can't handl memory allocation or something" i am on version 0.1.0 (beta), yeah its at this version since a long time, commit "7690b2e" (Apr 27, 2012) it did run stable for 2 Month 16 Day This Miner-Software is great! 3) there are only 2 blockchains => Bitcoin and P2Pool, i guess nobody is mining namecoin or others without merged mining so i am thinking about an "workers source"-option called "new block doesn't effect other worker sources" made a git pull yesterday and my problem is gone :) nice work just my 0.5BTC ;) Title: MPBM AJAX memory leak? Post by: Bogart on October 01, 2012, 02:37:47 PM Hi, I hope this is a good place for bug reporting.
I have been using MPBM for a few days now, cloned from github on 26-September. Over the weekend I left it running, and left the Safari window open with the WebUI running. When I returned today, it was running real chunky, and Safari was using several gigs of memory. Upon closing the MPBM tab, the memory was freed and things returned to normal. I think the AJAX code is leaking memory. Here is a screenshot of the Activity window after it has been running for a few minutes: https://i.imgur.com/GbdbN.png I think either the getallstats responses, or /api/log/stream (or both) are continuing to accumulate in browser memory for as long as the tab remains open. Sorry I didn't capture the Activity window before closing the tab earlier. Let me know if I can do anything more to help debug this. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: 99Percent on October 11, 2012, 03:25:55 AM I regret to report that after several months of using a very early version of mpbm (v0.0.4alpha) I can no longer get the miner to work with my x6500 and BTCGuild using today's git version (v0.1.0beta)
I have set up everything to the best of my knowledge but I get right of the bat: Code: 2012-10-10 21:57:45.146 [0] Core: Modular Python Bitcoin Miner v0.1.0beta, Copyright (C) 2012 Michael Sparmann (TheSeven) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: 99Percent on October 11, 2012, 04:32:25 AM Never mind. I was entering the wrong user_worker and password.
Perhaps a less cryptic message is in order here. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on October 21, 2012, 05:06:52 PM Does anyone know why using both BFL singles and Icarus FPGA miners with MPBM does not work? Is there some special trick that has to be done? Oddly even when I go to add a worker the bfl single worker does not even show up even though it appears the appropriate modules are there in the modules directory. I tried even the latest github build, no go. Eventually I gave up and used bfgminer for the singles and mpbm for the icarus boards.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: purelithium on December 17, 2012, 11:33:17 PM How do I use this with the ModMiner Quad? I currently use BFGMiner, but I prefer the webinterface of MPBM. It works great with my X6500s, now I want to add in my MMQ.
How do I do this? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: allinvain on December 26, 2012, 09:33:20 AM Is this project still being worked on or has it been abandoned? Any chance of updating the software to support the stratum mining protocol and any of the recent advancements in bitcoin mining - perhaps even support for ASIC miners? (granted being ASIC ready means supporting a mining protocol like stratum or getblocktemplate - luke's idea)
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: shad on December 26, 2012, 11:16:54 AM i guess you have to use the stratum-proxy, which is impossible for me on my router :( but it should work fine on a pc or a raspberry
but i am pretty sure it will support ASIC last update was 17 days ago Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: freshzive on February 06, 2013, 06:12:33 AM just did a git pull and noticed stratum support. seems to work fine with my set of x6500s. cheers!
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: fpgaminer on February 12, 2013, 11:52:04 PM If anyone has trouble using MPBM's Stratum Work Source with the BitMinter pool, I made the following patch against the latest version of MPBM:
http://pastie.org/6112329 (http://pastie.org/6112329) I have the patched code running well with the Stratum sources of Slush, BitMinter, and Ozcoin. On my Raspberry Pi and X6500! Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: bbulker on March 04, 2013, 03:55:20 AM Is it supposed to look like this, lol? Help!
https://i.imgur.com/3IMgOVOt.png (https://i.imgur.com/3IMgOVO.png) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: gyverlb on March 04, 2013, 10:32:48 AM Is it supposed to look like this, lol? Help! Try Chrome/Chromium (this is how it looks like on Firefox).https://i.imgur.com/3IMgOVOt.png (https://i.imgur.com/3IMgOVO.png) Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: bbulker on March 04, 2013, 10:57:23 AM Is it supposed to look like this, lol? Help! Try Chrome/Chromium (this is how it looks like on Firefox).https://i.imgur.com/3IMgOVOt.png (https://i.imgur.com/3IMgOVO.png) I refuse to install Chrome (AKA Google Botnet) since it's a massive security hole and records everything you type into the URL bar. Opera is my main browser due to the tight securty options but the console log never shows up in it. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: gyverlb on March 04, 2013, 11:34:47 AM I refuse to install Chrome (AKA Google Botnet) since it's a massive security hole and records everything you type into the URL bar. Aren't all browser recording what you type to make it easier to find later? I can understand Chrome being a privacy problem being closed-source and configured to send back information to Google by default but I'm not sure how it is a security problem and why Chromium would be a problem at all given that you can check for yourself that it doesn't have any back-door or send data back to Google (which isn't possible with Opera unless you disassemble it). Anyway, Opera is switching to WebKit (already used by Safari and all Chromium derivatives) so you may just opt to wait. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: shad on March 06, 2013, 07:33:21 PM Is it supposed to look like this, lol? Help! Try Chrome/Chromium (this is how it looks like on Firefox).https://i.imgur.com/3IMgOVOt.png (https://i.imgur.com/3IMgOVO.png) I refuse to install Chrome (AKA Google Botnet) since it's a massive security hole and records everything you type into the URL bar. Opera is my main browser due to the tight securty options but the console log never shows up in it. or try safari it works too i use it only for that, and only because its preinstalled on osx Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: shad on March 13, 2013, 11:05:54 PM anyone else having trouble with stratum?
worked fine for some hours now it is finding share but no accept or reject message, not counted on the pool Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: Bicknellski on March 26, 2013, 03:50:04 PM Quote 2013-03-27 00:25:24.747 [100] Untitled X6500 worker: 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\\mpbm-v0.1.0beta\modules\fpgamining\x6500\util\ft232r.py", line 349, in __init__ raise Exception("Can not open the specified device") Exception: Can not open the specified device 2013-03-27 00:25:24.748 [100] Untitled X6500 worker: Traceback (most recent call last): File "C:\Users.....\Users.....X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\\mpbm-v0.1.0beta\modules\fpgamining\x6500\x6500worker.py", line 211, in main elif data[0] == "dying": raise Exception("Proxy died!") Exception: Proxy died! Resolved it... just needed BETTER USB cables.... ARGGGGG! Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: ziomik on April 01, 2013, 05:53:44 PM anyone else having trouble with stratum? worked fine for some hours now it is finding share but no accept or reject message, not counted on the pool same problem, works for hours and then BOOM error red Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: tolan77 on April 04, 2013, 07:11:25 PM Quote 2013-03-27 00:25:24.747 [100] Untitled X6500 worker: 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\\mpbm-v0.1.0beta\modules\fpgamining\x6500\util\ft232r.py", line 349, in __init__ raise Exception("Can not open the specified device") Exception: Can not open the specified device 2013-03-27 00:25:24.748 [100] Untitled X6500 worker: Traceback (most recent call last): File "C:\Users.....\Users.....X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\\mpbm-v0.1.0beta\modules\fpgamining\x6500\x6500worker.py", line 211, in main elif data[0] == "dying": raise Exception("Proxy died!") Exception: Proxy died! Resolved it... just needed BETTER USB cables.... ARGGGGG! Caught exception: Traceback (most recent call last): File "C:\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\x6500hotplug.py", line 287, in main for serial, child in self.childmap.items(): RuntimeError: dictionary changed size during iteration Which cables did you end up trying? Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: n4l3hp on April 05, 2013, 01:33:12 PM http://i45.tinypic.com/a2w652.jpg
Using bfgminer 2.10.5 for 2 weeks now without issues. Was using MPBM before because the x6500s had SICK/DEAD issues with older versions of bfgminer. OCL 0 & 1 = 6870s (underclocked to 775/300) OCL 2 = 5850 (overclocked to 960/300) OCL 3 = 5670 (overclocked to 1000/300) BFL = 864 firmware XBS 0 - 3 = x6500 rev 3 Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: paszczakojad on May 07, 2013, 08:34:48 PM Hi,
I connected MPBM through RS232 to a custom board running at 400 MH/s (Kintex 325) and I'm getting 9% cancelled shares. Is that acceptable value? Does that mean that I loose 9% of my computing power? I'm wondering if it's better to connect two such boards to two RS232 ports or design a new dual-FPGA board that shares work between two FPGAs - in the first case the canceled rate should remain the same and in the second case it should be halved. But does that matter? Or is there any other way to fix that problem? P. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: rethaw on May 30, 2013, 11:53:58 PM Using MPBM to mine with ASICMINER's USB miners (https://bitcointalk.org/index.php?topic=212085.0;topicseen). It is doubling the Current MH/s, but the effective is accurate over time.
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: LazyOtto on June 03, 2013, 08:13:57 PM Using MPBM to mine with ASICMINER's USB miners (https://bitcointalk.org/index.php?topic=212085.0;topicseen). It is doubling the Current MH/s, but the effective is accurate over time. I can report the same thing. On OS X.Initially tried it on Raspbian where I have a BFL FPGA and a couple of CM1s. But it *seems* like the combination of BE USB and CM1 causes a catastrophic failure with MPBM on Raspbian. "Catastrophic" as in mining stops, ssh stops and the machine no longer responds to a ping. Sadly, no residue which I can find left in any log, either. Currently MPBM on Raspbian is running two CM1s and MPBM on OS X is running a BFL Single (FPGA) and a BE USB. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: Mike270 on June 11, 2013, 06:18:25 AM Hi, I just started using MPBM for the first time, and what shall I say.... WOW I love it :-)
Easy to set up work sources, Easy to switch on & off & distribute hash power... Using it with my new Cairnsmore1 devices (running on dynamic clocking hashvoodoo bitstream). Applied fpgaminer's stratum fix to get it to work with various stratum pools that didn't work without the patch. Also, Hash rates are about 5-10% higher than I can achieve with bfgminer on the boards. (~217,5MH/s/ single FPGA with MPBM) Plus: Accurate Hash rates :-) So now I'm having some questions, hoping that you'd help me here: - I also have some ModMiner Quads that are running very stable and fine with cgminer, but now that I saw MPBM I'd really like to integrate them. At a first test, MPBM wants to send a bitstream to them, but doesn't find it since non is included. When I google for the file name MPBM expects, I cannot find anything. What bitstream would I need for them? Can I just use the same Hashvoodoo bitstream that I use for Cairnsmore1 and rename it to the file name MPBM expects? - The stats displayed are over the whole running time of MPBM - Is there a way to reset them to see the effects of Priority changes better(without restarting MPBM)? - Is there some tutorial/README on how the Priority settings / Hashrate settings work? Some work sources, like for example bitminter getwork seem to flood the processing that almost all hash power goes there, even when I have other pools at same priority or at same hashrate settings. So far I could not notice any effect of setting the hashrate for a work source. Basically all I can do right now is doing something like define a primary pool at prio 1000000, a backup pool at prio 1000 and a backup backup pool at prio 1 , but anything more elaborated was not as successful as I hoped it to be. What I really would like to achive is: Have for example a work source group "bitcoin", a work source group "freicoin", .... and within each work source group I have a mix of multiple primary/secondary pools. Then I could on the fly define a target hashrate for each worksource group that could be easily adjusted. But so far no luck :-( Thanks a lot for any help! Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: frankenmint on July 08, 2013, 10:31:45 AM For some reason I cannot connect to any stratum servers? Getwork works fine but not stratum. Do I need to install a stratum server?
Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: LazyOtto on July 08, 2013, 04:51:17 PM For some reason I cannot connect to any stratum servers? Getwork works fine but not stratum. Do I need to install a stratum server? For some pools a patch needs to be applied. Search this thread.Personally, I'm just using a proxy. Title: Re: Modular Python Bitcoin Miner - Official Thread Post by: Tsunamirain on October 31, 2013, 04:19:40 PM Theseven pm sent :)
|
