Modular Python Bitcoin Miner - Official Thread

[fizzisist]

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])
bash: Syntaxfehler beim unerwarteten Wort `350,'
schwing@R2079-W5:~$ TypeError: unsupported operand type(s) for *: 'NoneType' and 'int'

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.

[1714878973]

1714878973

[1714878973]

1714878973

[1714878973]

1714878973

[1714878973]

1714878973

[allinvain]

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.

[allinvain]

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.

[TheSeven]

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

[allinvain]

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.

[O_Shovah]

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.

[allinvain]

Room temp 27C

Single 1: 47.50
Single 2: 51.20

[O_Shovah]

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

[gr0bi42]

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

What kind of CPU-board is this? Looks not like an Rasberry-PI.

[O_Shovah]

Its a Pandaboard ES running Ubuntu ARM and my ports of bitcoin-qt/bitcoind  and mpbm.

[Zeronic]

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.

[freshzive]

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.

[TheSeven]

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?

[rjk]

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.

[hashking]

Can anyone help me with a step by step instruction on how to get a bfl to work with this miner on windows.

[hashking]

I guess no one has used any BFL singles with this miner on windows.

[cablepair]

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

[coretechs]

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.

[O_Shovah]

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.

[ebereon]

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: