X6500 Custom FPGA Miner

[fizzisist]

To everyone with software issues: I have been traveling for the past week but am returning home today. I'll look into each of those issues as soon as possible (on the plane if there's wifi). Until then, please post as much info as you can (OS, etc). Thanks!

[1713867235]

1713867235

[1713867235]

1713867235

[1713867235]

1713867235

[fizzisist]

Shad, could you try the latest from github? There may have been a fix for your problem in the last couple weeks (after the v0.1 release).

[thirdlight]

I'm seeing:

Code:

...
_d2xx.Error: (4, 'IO error')

This seems to be due to a flaky usb hub. 

Now getting:

Code:

(FPGA0) Golden nonce found
IO Error!
(FPGA0) rejected 72ba42c7L
(FGPA0) Connecting...
(FGPA0) accepted 72ba42c7L

Any thoughts?

[Qoheleth]

I'm having some trouble as well.

Running program.py gives this error:

Code:

Traceback (most recent call last):
  File "program.py", line 23, in <module>
    from ft232r import FT232R, FT232R_PortList
  File "/home/[redacted]/x6500-miner/ft232r.py", line 22, in <module>
    import d2xx
  File "/usr/lib/python2.7/site-packages/d2xx/__init__.py", line 24, in <module>
    from _d2xx import *
ImportError: /usr/lib/python2.7/site-packages/d2xx/_d2xx.so: undefined symbol: FT_CyclePort

I ran a quick nm command on the libftd2xx.so I downloaded from the site you indicated, and sure enough, there's no such symbol in the library.

I'm on 32-bit Linux, if it matters.

Edit: Bar that; solution found. Turns out there's four functions whose metadata you commented out in the modified python libraries, but you forgot to comment out the functions themselves. So it tried to link to them, and.... bang!

[Qoheleth]

New problem.

I've got both my X6500 boards up and "running", but while one of them (-d 1) is returning golden nonces every few jobs, the other one has been running for ~10 minutes without a single golden nonce.

Is this expected? What could the problem be?

Edit: Had a problem with my jury-rigged power supplies and had to reload -d 1, and when I came back it was spinning its wheels too.

[fizzisist]

Now getting:

Code:

(FPGA0) Golden nonce found
IO Error!
(FPGA0) rejected 72ba42c7L
(FGPA0) Connecting...
(FGPA0) accepted 72ba42c7L

Any thoughts?

I suspect that that IO Error was a connection error from the pool. Since it retried the submission after reconnecting, it shouldn't have counted that as rejected. I believe that behavior was fixed a few commits back in Github. Are you using v0.1? I decided to release a v0.11 today to try to bring everybody to the same page. This version and updated documentation can be found here. Sorry about all the trouble with that!

I was hoping to release after long-polling was added, but I think it's a good idea to get this out now, because of all these little fixes that have been added over the weeks. This version has been incredibly stable while I've been out of town for a week. I haven't once had to ssh in and restart a miner or anything like that. You can see the stability here: http://eligius.st/~artefact2/5/1FPGAxkfHskMq9fg2gbAWhPrnqwXydbX93

Also, this status line is pretty awesome:

Code:

273.35 MH/s | 0: 18082/1664/19 8.4% | 1: 18107/1665/19 8.4% | 1w23h39m | AHxxxxxx

[fizzisist]

I'm having some trouble as well.

Running program.py gives this error:

Code:

Traceback (most recent call last):
  File "program.py", line 23, in <module>
    from ft232r import FT232R, FT232R_PortList
  File "/home/[redacted]/x6500-miner/ft232r.py", line 22, in <module>
    import d2xx
  File "/usr/lib/python2.7/site-packages/d2xx/__init__.py", line 24, in <module>
    from _d2xx import *
ImportError: /usr/lib/python2.7/site-packages/d2xx/_d2xx.so: undefined symbol: FT_CyclePort

I ran a quick nm command on the libftd2xx.so I downloaded from the site you indicated, and sure enough, there's no such symbol in the library.

I'm on 32-bit Linux, if it matters.

Edit: Bar that; solution found. Turns out there's four functions whose metadata you commented out in the modified python libraries, but you forgot to comment out the functions themselves. So it tried to link to them, and.... bang!

Nice detective work! That's exactly the kind of modification I had to make to get it to work, and I'm not sure why you still had to make those changes. I'll look at my modified library again and update it so that this doesn't happen to others. Thanks, and sorry for the problems!

[fizzisist]

New problem.

I've got both my X6500 boards up and "running", but while one of them (-d 1) is returning golden nonces every few jobs, the other one has been running for ~10 minutes without a single golden nonce.

Is this expected? What could the problem be?

Edit: Had a problem with my jury-rigged power supplies and had to reload -d 1, and when I came back it was spinning its wheels too.

We need to find a solution to this kind of problem. I believe what happened was the power was removed momentarily from the FPGA. When that happens, it loses it's configuration and goes back to being an unprogrammed FPGA. The mining software doesn't know that it's unprogrammed so just keeps asking it for nonces. Of course, none ever come. We'll work on a fix to this (easy to add a bit that says, "I'm programmed" or something).

Until then, if anyone gets strange problems like this, the first thing to try is restarting mine.py. The next thing is to rerun program.py. Rerunning program.py is essentially the same as rebooting the FPGA, so it should clear up any strangeness.

[sadpandatech]

Are there any plans to add a small eprom to future boards in order to save the configuration to the boards until we purposely wish to change it?

[Qoheleth]

New problem.

I've got both my X6500 boards up and "running", but while one of them (-d 1) is returning golden nonces every few jobs, the other one has been running for ~10 minutes without a single golden nonce.

Is this expected? What could the problem be?

Edit: Had a problem with my jury-rigged power supplies and had to reload -d 1, and when I came back it was spinning its wheels too.

We need to find a solution to this kind of problem. I believe what happened was the power was removed momentarily from the FPGA. When that happens, it loses it's configuration and goes back to being an unprogrammed FPGA. The mining software doesn't know that it's unprogrammed so just keeps asking it for nonces. Of course, none ever come. We'll work on a fix to this (easy to add a bit that says, "I'm programmed" or something).

Until then, if anyone gets strange problems like this, the first thing to try is restarting mine.py. The next thing is to rerun program.py. Rerunning program.py is essentially the same as rebooting the FPGA, so it should clear up any strangeness.

Hmm. I suppose that'd explain it - like I said, my solutions to powering the boards are pretty seriously jury-rigged right now, so I'm not surprised that they'd cut out momentarily. I'll see if I can't get that part of the system to be more stable when I get home tonight.

[thirdlight]

Now using v 0.11, thanks!

Seeing frequent Errno 10053, and very occasional Errno 10054.

[fizzisist]

Seeing frequent Errno 10053, and very occasional Errno 10054.

Not sure what's going on there... I'm guessing those are socket errors, which would show up as "IOError" in the log. Is that what you see? Do you have some strange network config (behind a proxy, etc.)? I've never seen those errors myself.

What's the status on the Mac miner?

So far not tested yet. I was putting a little more focus on the ARM miner, but haven't had success yet. I'll try Mac soon.

I got it to run on my Mac today! I posted some instructions at fpgamining.com/software, but your testing and feedback on that will be much appreciated!

[thirdlight]

behind a proxy, etc.?

Yes, I use "Flexible Mining Proxy". Going direct does get rid of those errors.

But.. it won't connect to BTC Guild (which does work thru the proxy). Are there "good" pools & "bad" pools for this software? My experience is:

• Eclipse: works
• Guild: fails to connect
• p2pool: shares are "invalid"

Maybe the LP support will fix it?

[fizzisist]

I decided to put up a list of useful accessories for mining with your X6500, in hopes that it will save others a lot of time in searching around the web for these things.

Cablesaurus.com
As long as you're ordering your X6500s from Cablesaurus, you might as well pick up some useful accessories there and not have to pay shipping to another supplier. We're trying to get as many accessories stocked by Cablesaurus.com as possible, but only have a few basics right now.

10 port USB hub:
http://cablesaurus.com/index.php?main_page=product_info&cPath=10&products_id=55

USB cable:
http://cablesaurus.com/index.php?main_page=product_info&cPath=10&products_id=54

Molex splitter:
http://cablesaurus.com/index.php?main_page=product_info&cPath=10&products_id=51

24-Pin ATX Power-On Dummy Plug:
http://cablesaurus.com/index.php?main_page=product_info&cPath=13&products_id=45

20-Pin ATX Power-On Dummy Plug:
http://cablesaurus.com/index.php?main_page=product_info&cPath=13&products_id=44


Elsewhere on the web:
Unfortunately, not everything that you might want is available from Cablesaurus.com yet. Here are some accessories that might be useful.

USB powered fan:
http://www.amazon.com/Thermaltake-Mobile-Fan-External-Cooling/dp/B00080G0BK

Fan with AC adapter (80mm):
http://www.buyextras.com/bxtulsi80x80.html

Fan with AC adapter (120mm):
http://www.buyextras.com/yalo120x25ul2.html

AC to Molex power supply (the current on the 5V rail is not enough to power an X6500, so you must use an adapter to bring the 12V line to the correct pin):
http://www.amazon.com/110v-4pin-molex-Power-Adapter/dp/B000MGG6SC

SATA to Molex adapter:
http://www.amazon.com/KingWin-Power-Adapter-Cable-SAC-05/dp/B001JE6WYY

Low-profile SATA to Molex:
http://www.amazon.com/Sata-LP4-Pin-Power-Adapter/dp/B000NPKGGU


I'll add to this list as I find more useful stuff.

[fizzisist]

behind a proxy, etc.?

Yes, I use "Flexible Mining Proxy". Going direct does get rid of those errors.

But.. it won't connect to BTC Guild (which does work thru the proxy). Are there "good" pools & "bad" pools for this software? My experience is:

• Eclipse: works
• Guild: fails to connect
• p2pool: shares are "invalid"

Maybe the LP support will fix it?

Hmm, I use the mining proxy regularly and never saw that error... I did have a problem early on where I would get empty responses from the proxy occasionally. I had to increase the KeepAliveTimeout in Apache's config to avoid this. Still, it should just retry when it encounters that instead of getting an error. Try increasing that setting to longer than the getwork interval (default 20 seconds) and see if it gets better.

As for the various pools, I haven't tested it with many others. The few I tried worked perfectly, but I need to do a careful study of a lot of them, along with recording the raw traffic to know what's really going on. Thanks for reporting what you've found!

[CA Coins]

Following to see how the software issues work out and what hash rates people are getting

[shad]

269.42 MH/s | 0: 3089/339/0 9.9% | 1: 2993/311/0 9.4% | 1d9h6m and sill running

stales rate is because of no LP, but i think LP is on the way

[sirky]

I am getting an error on my old XP box that says it cannot encode character \u2588

Anyone else get this.

And sorry if I missed something.

After it errors it seems like the FPGA gets a bit hotter too. It runs cool when it is running though.

[Qoheleth]

228.66 MH/s | 0: 2238/210/0 8.6% | 1: 2309/227/0 9.0% | 1d21m22s

Running the 133MHz bitstreams, not sure exactly why the rate is so low. Maybe just a run of bad luck.

[fizzisist]

I am getting an error on my old XP box that says it cannot encode character \u2588

Anyone else get this.

And sorry if I missed something.

After it errors it seems like the FPGA gets a bit hotter too. It runs cool when it is running though.

That error is probably because of that "sparkline" stuff in ConsoleLogger.py that I once thought was a great idea. I think that character is the largest one on the list of available characters, and I just removed it from the latest version in Github. Could you try it now to see if the problem is fixed for you? If it isn't we can completely comment out that section of the code and be done with it (unless you really want that sparkline in there).