Bitbird
|
|
September 19, 2012, 07:20:54 AM |
|
Hey guys,
Just received my Quad XC6SLX150 Board. How should I do for setup it with my GPU and BLF single(x1) Linux minning rig? I use cgminer 2.7.5 and have no idea what's the next step after connected Quad XC6SLX150 to the minning rig. Most appreciate for any help!
|
|
|
|
Luke-Jr
Legendary
Offline
Activity: 2576
Merit: 1186
|
|
September 19, 2012, 07:38:14 AM |
|
Hey guys,
Just received my Quad XC6SLX150 Board. How should I do for setup it with my GPU and BLF single(x1) Linux minning rig? I use cgminer 2.7.5 and have no idea what's the next step after connected Quad XC6SLX150 to the minning rig. Most appreciate for any help!
https://en.bitcoin.it/wiki/CM1QuickstartRecommend upgrading to BFGMiner 2.8.0 tho
|
|
|
|
Bitbird
|
|
September 19, 2012, 05:20:51 PM |
|
@Luke-Jr Thanks! But how could I run BFGMiner on Linux? Can't find the file "bfgminer" in the /bfgminer-2.8.0 directory. Seem not the same as cgminer?
|
|
|
|
salty
|
|
September 19, 2012, 05:41:14 PM Last edit: September 19, 2012, 05:51:23 PM by salty |
|
Hey guys,
Just received my Quad XC6SLX150 Board. How should I do for setup it with my GPU and BLF single(x1) Linux minning rig? I use cgminer 2.7.5 and have no idea what's the next step after connected Quad XC6SLX150 to the minning rig. Most appreciate for any help!
Using cgminer 2.7.5 you need to get it to look for the cairnsmore on your com/serial ports when it starts using the option -S "/dev/tty.XXX" -S "/dev/tty.XXX" iirc. f.e. my cgminer startup command on windows has -S "\\.\COM22" -S "\\.\COM23" included. You'll need to find out what your cairnsmore's com ports are called, they're listed in /dev and (at least with the bitstream I'm using) there are 2 com ports per board.
|
|
|
|
tnkflx
|
|
September 19, 2012, 05:52:43 PM |
|
@Luke-Jr Thanks! But how could I run BFGMiner on Linux? Can't find the file "bfgminer" in the /bfgminer-2.8.0 directory. Seem not the same as cgminer?
What did you download? Binary, source?
|
| Operating electrum.be & us.electrum.be |
|
|
|
|
tnkflx
|
|
September 19, 2012, 06:14:13 PM |
|
Yeah, that's the source, need to compile that first: 1. Unzip (un-tbz2? ) and "cd bfgminer-2.8.0" 2. ./configure 3. make 4. ./bfgminer 5. ... 6. Profit!
|
| Operating electrum.be & us.electrum.be |
|
|
|
salty
|
|
September 19, 2012, 06:24:20 PM |
|
@salty Thanks! However, I got some messages say: Icarus Detect: Test failed at /dev/ttyUSB0: get 00000000, should: 000187a2 . . Is that definitely the right tty com port? Try some other ones maybe?
|
|
|
|
makomk
|
|
September 19, 2012, 07:42:38 PM |
|
@salty Thanks! However, I got some messages say: Icarus Detect: Test failed at /dev/ttyUSB0: get 00000000, should: 000187a2 . . That's almost certainly the wrong COM port. Try /dev/ttyUSB2 and /dev/ttyUSB3.
|
Quad XC6SLX150 Board: 860 MHash/s or so. SIGS ABOUT BUTTERFLY LABS ARE PAID ADS
|
|
|
salty
|
|
September 20, 2012, 12:54:25 AM |
|
@salty Thanks! However, I got some messages say: Icarus Detect: Test failed at /dev/ttyUSB0: get 00000000, should: 000187a2 . . That's almost certainly the wrong COM port. Try /dev/ttyUSB2 and /dev/ttyUSB3. One way to find out would be to get cgminer to scan them all, then check the log for a message like 'found Icarus on /dev/ttyUSB5' ie:- cgminer -S "/dev/ttyUSB0" -S "/dev/ttyUSB1" -S "/dev/ttyUSB2" -S "/dev/ttyUSB3" -S "/dev/ttyUSB4" -S "/dev/ttyUSB5" 2>mining.log In fact, if your com ports change between reboots, you could just let it check every time you start the miner.
|
|
|
|
Cranky4u
|
|
September 20, 2012, 05:47:08 AM |
|
|
|
|
|
Bitbird
|
|
September 20, 2012, 07:48:20 AM |
|
@tnkflx make: *** No targets specified and no makefile found. Stop. Strange..
|
|
|
|
Luke-Jr
Legendary
Offline
Activity: 2576
Merit: 1186
|
|
September 20, 2012, 08:01:10 AM |
|
@tnkflx make: *** No targets specified and no makefile found. Stop. Strange.. That's almost surely a result of some error in the previous steps. Can you pastebin the output from those?
|
|
|
|
Bitbird
|
|
September 20, 2012, 09:59:09 AM |
|
@salty @makomk cgminer -S "/dev/ttyUSB0" -S "/dev/ttyUSB1" -S "/dev/ttyUSB2" -S "/dev/ttyUSB3" -S "/dev/ttyUSB4" -S "/dev/ttyUSB5" 2>mining.log Already tried this but didn't work. Even when the list seems properly: ~ $ ls -l /dev/serial/by-id/ 總計 0 lrwxrwxrwx 1 root root 13 9月 20 15:37 usb-Butterfly_Labs_Inc._BitFORCE_SHA256-if00-port0 -> ../../ttyUSB4 lrwxrwxrwx 1 root root 13 9月 20 15:32 usb-FTDI_Cairnsmore1_FTVPMIN0-if00-port0 -> ../../ttyUSB0 lrwxrwxrwx 1 root root 13 9月 20 15:32 usb-FTDI_Cairnsmore1_FTVPMIN0-if01-port0 -> ../../ttyUSB1 lrwxrwxrwx 1 root root 13 9月 20 15:32 usb-FTDI_Cairnsmore1_FTVPMIN0-if02-port0 -> ../../ttyUSB2 lrwxrwxrwx 1 root root 13 9月 20 15:32 usb-FTDI_Cairnsmore1_FTVPMIN0-if03-port0 -> ../../ttyUSB3 update: I'll try on my another rig later.
|
|
|
|
Lethos
|
|
September 20, 2012, 10:18:30 AM |
|
@salty @makomk cgminer -S "/dev/ttyUSB0" -S "/dev/ttyUSB1" -S "/dev/ttyUSB2" -S "/dev/ttyUSB3" -S "/dev/ttyUSB4" -S "/dev/ttyUSB5" 2>mining.log Already tried this but didn't work. Even when the list seems properly: I've never used any " " to reference the usbports, so I assume that would be the problem. So it's more like: cgminer -S /dev/ttyUSB0 -S /dev/ttyUSB1 -S /dev/ttyUSB2 -S /dev/ttyUSB3 -S /dev/ttyUSB4 -S /dev/ttyUSB5 Also it depends on which bitstream you are using to what ports to reference. Make sure you have issued the modprobe command as well before hand. sudo modprobe ftdi-sio product=0x8350 vendor=0x0403 Mak's only uses 2, hashvoodoo uses all 4. If you need a simple guide on flashing new bitstreams; https://bitcointalk.org/index.php?topic=78239.msg1110647#msg1110647If you search through this thread, there is a ton of information, just a matter of searching for it.
|
|
|
|
|
kano
Legendary
Offline
Activity: 4620
Merit: 1851
Linux since 1997 RedHat 4
|
|
September 20, 2012, 12:38:28 PM |
|
Try this (old script I got from Xiangfu that I enhanced) on each of the linux USB ports that you expect to work like Icarus: https://raw.github.com/kanoi/cgminer/ztex/usbtest.py ./usbtest.py /dev/ttyUSB0 icarus It has a habit of clearing any USB problems if that is the cause. If that's not the cause, well then it wont help Also it's not very 'tidy' coz I don't like python I've needed it sometimes when I've moved an Icarus from windows to linux ( and I still don't know exactly how python fixes that - even after I wrote copious amounts of termios debug ... as you will see commented out in fpgautils.c ... the problem I get is actually when the port is opened ... and python somehow clears that problem) ... again ... if that's not the cause, well then it wont help.
|
|
|
|
makomk
|
|
September 20, 2012, 01:30:16 PM |
|
Interesting: Some bitstreams such as some current “220” bitstreams can use excessive power and hence generate heat that is impossible to extract from the FPGA packaging. This may damage FPGAs and our warranties will not support boards damaged by running “220” bitstreams or similar. The maximum recommended bitstream is currently “200”. If in doubt email bitcoin.support@enterpoint.co.uk for a list of approved bitstreams.
|
Quad XC6SLX150 Board: 860 MHash/s or so. SIGS ABOUT BUTTERFLY LABS ARE PAID ADS
|
|
|
Lethos
|
|
September 20, 2012, 01:36:57 PM |
|
Interesting: Some bitstreams such as some current “220” bitstreams can use excessive power and hence generate heat that is impossible to extract from the FPGA packaging. This may damage FPGAs and our warranties will not support boards damaged by running “220” bitstreams or similar. The maximum recommended bitstream is currently “200”. If in doubt email bitcoin.support@enterpoint.co.uk for a list of approved bitstreams. Yeah, that didn't add up to me either. I was always under the impression bitstreams can't effect it's "power" or "voltage", nor would it change automatically even if you pushed it hard via overclocking. The worst that happens is invalids or errors in the output.
|
|
|
|
tnkflx
|
|
September 20, 2012, 02:40:16 PM |
|
Interesting: Some bitstreams such as some current “220” bitstreams can use excessive power and hence generate heat that is impossible to extract from the FPGA packaging. This may damage FPGAs and our warranties will not support boards damaged by running “220” bitstreams or similar. The maximum recommended bitstream is currently “200”. If in doubt email bitcoin.support@enterpoint.co.uk for a list of approved bitstreams. Yohan, can you comment on this?
|
| Operating electrum.be & us.electrum.be |
|
|
|
|