Pages:
Author

Topic: X6500 Custom FPGA Miner - page 16. (Read 220101 times)

newbie
Activity: 36
Merit: 0
April 18, 2012, 06:06:55 PM
Any word on when we will see more available for order? Cant wait to get my hands on some.
hero member
Activity: 504
Merit: 500
FPGA Mining LLC
April 18, 2012, 11:35:05 AM
There may be other ways to work around it... feel free to share them.  Smiley

Add a native serial port driver to MPBM, to completely remove the need for ftdi_sio.
Not exactly trivial, but shouldn't be all that hard either. It's on my todo list for May/June Smiley
donator
Activity: 362
Merit: 250
April 18, 2012, 10:17:17 AM
That could be it. freshzive, if you're on linux, take a look at the Linux guide for a way to blacklist that module so you don't have to bother with it again.

Let us know if you're still having the problem!

Keep in mind that if you are running other FPGAs you may want to skip the blacklist in step 4, otherwise they may not be assigned a ttyUSB port.  On my system I run rmmod ftdi_sio prior to starting MPBM.  I load the x6500 bitstreams and get them mining first, then plug in other devices that require ftdi_sio.  There may be other ways to work around it... feel free to share them.  Smiley
sr. member
Activity: 447
Merit: 250
April 18, 2012, 09:38:17 AM
Yeah, and the old mine.py works fine with it as well...strange!

Maybe ftdi_sio got loaded accidentally? x6500-miner tries to remove that automatically, MPBM doesn't.

That could be it. freshzive, if you're on linux, take a look at the Linux guide for a way to blacklist that module so you don't have to bother with it again.

Let us know if you're still having the problem!

Hmmm, on a Mac not linux. I tried to remove and it doesn't seem to exist:

sudo kextunload /System/Library/Extensions/FTDIUSBSerialDriver.kext
Can't open CFBundle for /System/Library/Extensions/FTDIUSBSerialDriver.kext.
Can't create /System/Library/Extensions/FTDIUSBSerialDriver.kext.

Why would it get loaded on the new x6500 but no the old ones? Those are still chugging along fine in MPBM.
hero member
Activity: 720
Merit: 528
April 18, 2012, 06:07:11 AM
Yeah, and the old mine.py works fine with it as well...strange!

Maybe ftdi_sio got loaded accidentally? x6500-miner tries to remove that automatically, MPBM doesn't.

That could be it. freshzive, if you're on linux, take a look at the Linux guide for a way to blacklist that module so you don't have to bother with it again.

Let us know if you're still having the problem!
hero member
Activity: 720
Merit: 528
April 18, 2012, 06:04:42 AM
Just a photo of the latest progress on my rig (4 x x6500's so far). TIP: if you live in Australia, order these individually otherwise customs will slug you if it's worth over A$1000 (even if you paid in bitcoins).  These are the new rev3 boards with old style heatsinks, attached with arctic alumina thermal adhesive. The new boards are very slightly too big for my original design, but with a bit of shoving and wiggling, they fit fine.



Heres the rest of the build photos, if interested: http://jabawok.net/gallery/v/random/201201-x6500-30x-enclosure/

The boards are all running at 200Mhz (1.6Gh/s total), the fans are @ 7V and total power consumption at the AC is 95W

Temperature at 25C ambient is 36C on lower heatsink and 42C on upper heatsink. I'm not getting any invalids, if I start getting them when the ambient temperature is higher, i'll increase fan voltage a bit (which costs a few watts).

@fizzisist: if you have any blue heatsinks left, save them for me! What was your supplier for those blue heatsinks? On the rev3 boards sold with heatsnk/fan, how high do the standoffs need to be to stack the boards and allow adequate airflow? I can work with it, but I think i wont be able to fit 30 boards in my enclosure any more with the new heatsink/fan: blowing air down rather than across is not really optimal for stacking.

Awesomeness! Glad you were able to get the rev3 to fit.

I have a whole box of those heatsinks with your name on it. Wink We bought them from Digikey, but you're welcome to them at a nice discount.

The new heatsinks are about 2 inches tall with the fans. You need another 1/2 inch or so at least if you want to stack them and leave the fans on. But, you can remove the fans (4 screws) and supply airflow from the side, just like you're doing now. The height of the heatsink then is a little under 1.5 inch. I've been using 2 inch standoffs between boards, but you could get by with less, maybe 1 3/4 inch.
newbie
Activity: 48
Merit: 0
April 17, 2012, 08:38:22 PM
Just a photo of the latest progress on my rig (4 x x6500's so far). TIP: if you live in Australia, order these individually otherwise customs will slug you if it's worth over A$1000 (even if you paid in bitcoins).  These are the new rev3 boards with old style heatsinks, attached with arctic alumina thermal adhesive. The new boards are very slightly too big for my original design, but with a bit of shoving and wiggling, they fit fine.



Heres the rest of the build photos, if interested: http://jabawok.net/gallery/v/random/201201-x6500-30x-enclosure/

The boards are all running at 200Mhz (1.6Gh/s total), the fans are @ 7V and total power consumption at the AC is 95W

Temperature at 25C ambient is 36C on lower heatsink and 42C on upper heatsink. I'm not getting any invalids, if I start getting them when the ambient temperature is higher, i'll increase fan voltage a bit (which costs a few watts).

@fizzisist: if you have any blue heatsinks left, save them for me! What was your supplier for those blue heatsinks? On the rev3 boards sold with heatsnk/fan, how high do the standoffs need to be to stack the boards and allow adequate airflow? I can work with it, but I think i wont be able to fit 30 boards in my enclosure any more with the new heatsink/fan: blowing air down rather than across is not really optimal for stacking.
hero member
Activity: 504
Merit: 500
FPGA Mining LLC
April 17, 2012, 12:04:07 PM
Yeah, and the old mine.py works fine with it as well...strange!

Maybe ftdi_sio got loaded accidentally? x6500-miner tries to remove that automatically, MPBM doesn't.
sr. member
Activity: 447
Merit: 250
April 17, 2012, 10:42:24 AM
Yeah, and the old mine.py works fine with it as well...strange!
sr. member
Activity: 447
Merit: 250
April 17, 2012, 10:36:51 AM
So does program.py not work to program the new rev of boards? I get this error on both

Code:
2012-04-16 21:45:07 | Device 3 opened (A4014PHJ)
Traceback (most recent call last):
  File "program.py", line 91, in
    fpga.detect()
  File "/Users/christian/x6500-6/fpga.py", line 82, in detect
    with self.ft232r.lock: self.jtag.detect()
  File "/Users/christian/x6500-6/jtag.py", line 81, in detect
    raise NoDevicesDetected

Shows up in listDevices.py fine though?

It should... Have you tried MPBM? NoDevicesDetected means no FPGAs were detected, which usually happens when you don't have power on the board. Can you double check your power supply?

Yeah, you were right. I was able to upload the firmware, but now I'm having issues connecting in MPBM 0.4.

I get the error:

2012-04-17 08:35:58.714317: X6500 board A4014PHJ: Can not open the specified device

Ztex200 is definitely loaded on the board, so I'm not sure what's up? All of my old rev work fine with this version.
hero member
Activity: 720
Merit: 528
April 17, 2012, 01:50:39 AM
So does program.py not work to program the new rev of boards? I get this error on both

Code:
2012-04-16 21:45:07 | Device 3 opened (A4014PHJ)
Traceback (most recent call last):
  File "program.py", line 91, in
    fpga.detect()
  File "/Users/christian/x6500-6/fpga.py", line 82, in detect
    with self.ft232r.lock: self.jtag.detect()
  File "/Users/christian/x6500-6/jtag.py", line 81, in detect
    raise NoDevicesDetected

Shows up in listDevices.py fine though?

It should... Have you tried MPBM? NoDevicesDetected means no FPGAs were detected, which usually happens when you don't have power on the board. Can you double check your power supply?
sr. member
Activity: 447
Merit: 250
April 16, 2012, 11:46:06 PM
So does program.py not work to program the new rev of boards? I get this error on both

Code:
2012-04-16 21:45:07 | Device 3 opened (A4014PHJ)
Traceback (most recent call last):
  File "program.py", line 91, in
    fpga.detect()
  File "/Users/christian/x6500-6/fpga.py", line 82, in detect
    with self.ft232r.lock: self.jtag.detect()
  File "/Users/christian/x6500-6/jtag.py", line 81, in detect
    raise NoDevicesDetected

Shows up in listDevices.py fine though?
legendary
Activity: 1012
Merit: 1000
April 10, 2012, 04:58:56 PM
Wow I'm a 'tard.  Forgot to update bitstream from default.  Thanks for the quick response guys.
hero member
Activity: 504
Merit: 500
FPGA Mining LLC
April 10, 2012, 01:26:24 PM
Which bitstream are you using?
Can you post a screenshot of the worker configuration?
Can you paste the full MPBM log, from startup until the first couple of shares were found?
sr. member
Activity: 249
Merit: 250
April 10, 2012, 11:38:42 AM
Have tried rebooting the board several times....



 Huh

@ Pipesnake:
A couple of questions for you:

1.) Which rev of the x6500 are you using?
2.) Which bitstream / firmware are you using?
3.) Have you tried 0.4 of MPBM or only 1.0 MPBM?
legendary
Activity: 1012
Merit: 1000
April 10, 2012, 11:04:29 AM
Have tried rebooting the board several times....



 Huh
sr. member
Activity: 249
Merit: 250
April 10, 2012, 10:19:14 AM
BTW I've been testing and playing around with my X6500 Rev 3.0 and I got to say: this thing is solid! I'm using the Zalman "flower" coolers and so far getting a fairly consistent hash power from my unit! Pics to come later once I've gotten it all settled!


-n
hero member
Activity: 720
Merit: 528
April 10, 2012, 04:43:34 AM
Have a board stuck at 50mh/s per core.  Any ideas as to why?

Using the new overclocker firmware? That is the starting frequency if you don't send the FPGA any commands to set the clock. I'm guessing an MPBM bug that caused that command to not go out. Can you restart the worker in MPBM? You might not even need to upload the firmware again, although that couldn't hurt.

If you're on a fixed-clock firmware, like ztexmerge, then I don't know what's going on. First thing to try is reprogramming it. If you've done that already, then I'm pretty stumped.
legendary
Activity: 1012
Merit: 1000
April 10, 2012, 04:18:06 AM
Have a board stuck at 50mh/s per core.  Any ideas as to why?
legendary
Activity: 938
Merit: 1000
What's a GPU?
April 09, 2012, 09:32:47 PM
That just cycles power, unloading the firmware from the fpga. Ticking the box mentioned above will give you the same result most of the time.
Pages:
Jump to: