Topic: Modular Python Bitcoin Miner - Official Thread - page 4. (Read 74196 times)
Is it really that simple? Thanks a lot!
you have to direct mpbm to your local bitcoin client i guess?
shouldn't be different to using a pool
shouldn't be different to using a pool
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.
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.
Does anyone know how to use the modminer with this software.
You just earned yourself 5 btc my friend. What's your address?
Received! Thank you!
1KWGtSxo5b52Adk3Pvw14E3o9kp96JZJm2
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.
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.
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)
"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:
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.
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
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.
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
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
I guess no one has used any BFL singles with this miner on windows.
Can anyone help me with a step by step instruction on how to get a bfl to work with this miner on windows.
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. 
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.
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
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.
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.
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.
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.
Its a Pandaboard ES running Ubuntu ARM and my ports of bitcoin-qt/bitcoind and mpbm.
So maybe a picture of my current (nonpermanent) setup of watercooled FPGA boards wich are manged by MPBM
.... 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
.... 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.
So maybe a picture of my current (nonpermanent) setup of watercooled FPGA boards wich are manged by MPBM
.... 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
.... 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
Jump to: