|
1022
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Quad XC6SLX150 Board - Initial Price £400/$640/520€
|
on: July 30, 2012, 04:52:43 PM
|
New Results with makomk 160.bit running smooth so far in cgminer 2.6.0.
Its getting there!
ICA 0: | 357.4/358.3Mh/s | A:194 R:0 HW:0 U: 4.50/m
ICA 1: | 361.1/355.3Mh/s | A:205 R:0 HW:0 U: 4.75/m
Nice! Out of interest, did you have trouble getting the board to pass cgminer's validation? I'm hoping I found the cause of that problem and fixed it, but... makomk, I've just flashed 5 of my boards with controller rev. 1.3, one of them, serial nr 62-0104 keeps failing cgminer validation, the other four are working nicely. spiccioli. EDIT: a full reset (removing power), it seems SW1 switch 1 OFF is not the same, seems to have solved my issue, now all 5 boards are hashing. |
|
|
|
|
1024
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Quad XC6SLX150 Board - Initial Price £400/$640/520€
|
on: July 28, 2012, 07:37:21 PM
|
Third time I ask this but as my question is buried under pages of people testing new bitstreams and yohan didn't seem to notice it...
Is there any way to flash a controller bitstream from a Linux computer or any plan to allow it ? I don't know if compiling spiprog is possible, if a specific version or patch is needed to make it work (Windows users are advised to download their SPIprog.exe from Enterpoint for example). So I don't even know if hacking my way through a random spiprog source compilation would not make my boards pricey door stops.
@yohan, please advise.
I too want to know the answer of this. +1 spiccioli |
|
|
|
|
1025
|
Bitcoin / Hardware / Re: Bounty: a bitstream for better utilizing the Cairnsmore1 143-243btc
|
on: July 28, 2012, 08:40:00 AM
|
Zefir's escrow status added to bounty terms post.
Thank you for the support. And thanks to all contributors so far, we just entered the three-digit range (113BTC as of writing). Keep it rolling! 2 BTC bounty sent....as small time operator thats a big % for me...comon CM1 owners...1 BTC per board will not send you bankrupt Sent my 10BTC a couple of days ago. spiccioli |
|
|
|
|
1026
|
Bitcoin / Hardware / Re: Algorithmically placed FPGA miner: 255MH/s/chip, supports all known boards
|
on: July 26, 2012, 07:26:51 AM
|
With lots and lots of $9 JTAG cables.  Inspector, do you need some kind of jtag hub? I mean, on one side we have the jtag connector, but on the other side? spiccioli USB typically. Back in the old days, they used to hook up JTAG controllers to the parallel printer port... <wanders off into the distance, muttering about the old days when JTAG ports were still hooked up to LPT1: and a gallon of gasoline cost less than a buck> Thanks for clarifying, I've never used a jtag port  spiccioli |
|
|
|
|
1028
|
Bitcoin / Mining / Re: LargeCoin is scared of BFL
|
on: July 25, 2012, 08:17:06 PM
|
Well, I might make note of something that makes a difference - they say 1Th/s, not 1.5.
Additionally, that 1 Th/s is with multiple chips in a box, and the number is unspecified. My understanding of full-custom ASIC processes is that chips are cheap to make, once the NRE is recovered. Like, REALLY cheap.
So I do believe it is possible, but I also am of the opinion that they are staking an awful lot on the outcome.
The number of chips is not particularly relevant. What matters is the hashing power to wattage ratio. Unless you want to spend $5-10M in NRE, you're going with a structured ASIC process. eASIC and Alterra HardCopy are the only options here. Chips will be capable of 2GHash/s each, approximately. So, assuming BFL is using a structured ASIC process to keep NRE less than millions, they'd need 500 ASICs to generate a terahash. Unit costs are small if you produce 10,000s of ASICs; however, when your production is in the hundreds or low thousands, you're looking at $100s per unit. That terahash box has a cost base of $500K, by our estimation. 50K using 500 chips per box at 100 USD per chip. spiccioli |
|
|
|
|
1029
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Quad XC6SLX150 Board - Initial Price £400/$640/520€
|
on: July 25, 2012, 06:28:33 AM
|
Today I was able to get the Enterpoint cairnsmore to work with the tricone mining software without needing an isolated stand-alone cable, just the FTDI link. The code is still early in function, and still suffers from some JTAG errors likely due to noise / reflections on the lines which will need better error handling. I only performed several tests, but was easily able to get stable function with three rings at 100Mhz. (150 Mh/s).
I will keep you guys updated, I should have more time to work on it on Tuesday.
Here's some brief logs from submitted shares, it's fairly garbled from the ascii formatting for the colors.
Hi chrisp, so you wrote the java interface for the cairnsmore board? spiccioli |
|
|
|
|
1030
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Quad XC6SLX150 Board - Initial Price £400/$640/520€
|
on: July 23, 2012, 12:20:25 PM
|
Okay now I'm convinced there's something seriously wrong with my two Cairnsmore1 boards.
After trying again today to get them working at full speed, I was flashing Rev 1.2 onto both of my boards using SPIProg.exe, I turned the power off to the boards, then turned it back on. I noticed that one of my boards had different LEDs lit to the other board, even though they were using the exact same documented DIP switch settings
norulezapply, this is a bug of revision 1.2, sometimes when starting up you get blue/red leds light up. If you flash revision 1.3 this problem is fixed. spiccioli. Hmm. The reason I was trying 1.2 was because I'm not getting stable or full hashrates with 1.3. If it is just a bug with 1.2, how come the same thing is not happening with my 2nd board when I flash it with 1.2? :S norulezapply, I don't know, see this and following messages from yohan https://bitcointalk.org/index.php?topic=78239.msg1023229;topicseen#msg1023229spiccioli. |
|
|
|
|
1031
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Quad XC6SLX150 Board - Initial Price £400/$640/520€
|
on: July 23, 2012, 07:28:41 AM
|
Okay now I'm convinced there's something seriously wrong with my two Cairnsmore1 boards.
After trying again today to get them working at full speed, I was flashing Rev 1.2 onto both of my boards using SPIProg.exe, I turned the power off to the boards, then turned it back on. I noticed that one of my boards had different LEDs lit to the other board, even though they were using the exact same documented DIP switch settings
norulezapply, this is a bug of revision 1.2, sometimes when starting up you get blue/red leds light up. If you flash revision 1.3 this problem is fixed. spiccioli. |
|
|
|
|
1032
|
Bitcoin / Bitcoin Discussion / Re: [POLL] Multi-sig or scalability--which is more pressing?
|
on: July 22, 2012, 07:34:27 AM
|
Multisig support was already (re)enabled in the protocol with the last release. Scalability is not on the backburner at all. Right now there's a ton of work going into it: - Myself and Stefan are upgrading the Satoshi client to use LevelDB, which eliminates IO as a bottleneck on hard disk based nodes. This should make blocks and transactions propagate a lot faster across the network, which in turn should mean mining pools find it profitable to include SatoshiDice transactions again.
- sipa and Matt have been experimenting with different ways of doing pruning, which means you can have a full node that doesn't store the entire block chain. Sipa also has refactored some of the core TX verification code in a way that'll make it easier to multi-thread in future.
- Jeff has been doing some initial work and design proposals for connection filtering, which is needed to make bandwidth usage for lightweight clients linear in wallet activity rather than system activity
- Just generally a bunch of us are working on bitcoinj, which is a lightweight (SPV) implementation of Bitcoin which scales with wallet activity rather than system activity. Eventually nearly all users will be using SPV clients, meaning they won't have to download or process the whole block chain. We can already run Bitcoin on mobile phones, which is a big achievement, but there's still plenty of work left to do.
- Gavin has been finding ways to make hard-forking changes much smoother and easier in future, which will be important when we reach the 1MB limit.
If anything I'd say right now most development effort, at least from "core" developers, is going into scalability. Mike, I always wanted to ask this question: is there a reason for not separating the client from the DB management and use a real SQL engine like MySQL or PostgreSQL to host the blockchain? spiccioli |
|
|
|
|
1033
|
Bitcoin / Hardware / Re: Algorithmically placed FPGA miner: 255MH/s/chip, supports all known boards
|
on: July 21, 2012, 12:31:58 PM
|
Is anyone using that bitstream on Ztex Singles? Would like to know if it is somehow usable
H:357/114,114,128 X:272 C:180,180,185 E:0/0,0,0 T:5m personal best, so far at least. You have all my envy spiccioli |
|
|
|
|
1034
|
Bitcoin / Hardware / Re: Bounty: a bitstream for better utilizing the Cairnsmore1
|
on: July 21, 2012, 12:29:53 PM
|
Once things get started, they are getting momentum  Yohan's announcement to me sounds like Glasswalker successfully took a major hurdle and might finalize what he is working on soon. I am still committed to support the bounty, but do we need to clarify that the winner can't be Enterpoint or someone already being paid for his work by Enterpoint? Or do you think it would be ok to pay the bounty on top of the payment as additional incentive to hurry up? Given that we're using our boards at half their speed (or even less) I'd say I'm willing to send Glasswalker my bounty if he is the one behid Yohan's announcement if he can give us a solution and he is willing to support it for as long as it takes to have a stable bitstream/miner program. spiccioli. |
|
|
|
|
1035
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Quad XC6SLX150 Board - Initial Price £400/$640/520€
|
on: July 21, 2012, 07:15:49 AM
|
This is dmesg output.
...
I have to say, that doesn't look like a bitstream problem. It looks very much like there's some problem with the USB hub that you're connecting the boards to - it's dropping off the bus, failing to enumerate at USB 2.0 speeds, and eventually falling back to USB 1.1. Try a different hub or connecting them directly? Well that's certainly a good suggestion - but of course, spiccioli, note that they will get different USB numbers so be sure to compare the old and new correctly i.e. plug a few directly into the computer and compare to the ones in the hubs - but unplug them, then first take a listing of 'ls /dev/ttyUSB*' then plug them in and compare to what it was before - the new numbers not present in the previous listing (which can be higher or in the middle of the old numbers) are of course the direct connected ones. Also, certain old linux kernels have a problem with sending/receiving > 64 bytes over Serial+USB and literally chop off a byte at 64 Seeing the number 64 in there reminded me of that - but I don't know the kernel numbers. makomk, kano I don't think I have the old kernel issue, uname -a
Linux t5570 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
It could be a usb hub issue, I'll buy a new hub soon, just to see if it makes some difference. I can't connect them directly, though, since my HP thin client 5570 which I'm using as host pc can handle a maximum of three units since the boards require powered ports which it has not. spiccioli |
|
|
|
|
1038
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Quad XC6SLX150 Board - Initial Price £400/$640/520€
|
on: July 20, 2012, 03:30:16 PM
|
Double failure  after one week, this afternoon I found cgminer version 2.4.3 - Started: [2012-07-13 07:26:50]
--------------------------------------------------------------------------------
(5s):0.0 (avg):7341.2 Mh/s | Q:1462192 A:535635 R:580 HW:0 E:37% U:50.2/m
TQ: 20 ST: 21 SS: 18 DW: 19736 NB: 1148 LW: 1731 GF: 982 RF: 11
Connected to http://pool.abcpool.co with LP as user ......
Block: 0000014fd06b0138ceffc572e94b9597... Started: [17:10:25]
--------------------------------------------------------------------------------
[P]ool management [S]ettings [D]isplay options [Q]uit
ICA 0: | OFF /366.7Mh/s | A:27822 R:34 HW:0 U: 2.61/m
ICA 1: | OFF /366.9Mh/s | A:25564 R:25 HW:0 U: 2.40/m
ICA 2: | OFF /367.0Mh/s | A:27594 R:33 HW:0 U: 2.59/m
ICA 3: | OFF /366.9Mh/s | A:26397 R:31 HW:0 U: 2.47/m
ICA 4: | OFF /366.9Mh/s | A:27691 R:23 HW:0 U: 2.59/m
ICA 5: | OFF /366.9Mh/s | A:27226 R:23 HW:0 U: 2.55/m
ICA 6: | OFF /366.6Mh/s | A:27374 R:24 HW:0 U: 2.56/m
ICA 7: | OFF /366.4Mh/s | A:19404 R:25 HW:0 U: 1.82/m
ICA 8: | 380.0/367.3Mh/s | A:27337 R:34 HW:0 U: 2.56/m
ICA 9: | 380.0/367.2Mh/s | A:23528 R:27 HW:0 U: 2.20/m
ICA 10: | 380.0/367.3Mh/s | A:27353 R:32 HW:0 U: 2.56/m
ICA 11: | 380.0/367.1Mh/s | A:27529 R:23 HW:0 U: 2.58/m
ICA 12: | 380.0/367.3Mh/s | A:27557 R:32 HW:0 U: 2.58/m
ICA 13: | 380.0/367.3Mh/s | A:27555 R:32 HW:0 U: 2.58/m
ICA 14: | 380.0/367.1Mh/s | A:27685 R:32 HW:0 U: 2.59/m
ICA 15: | 380.0/367.2Mh/s | A:27517 R:26 HW:0 U: 2.58/m
ICA 16: | 380.0/367.3Mh/s | A:27500 R:28 HW:0 U: 2.58/m
ICA 17: | 380.0/367.3Mh/s | A:27658 R:33 HW:0 U: 2.59/m
ICA 18: | 380.0/367.2Mh/s | A:27792 R:30 HW:0 U: 2.60/m
ICA 19: | 380.0/367.3Mh/s | A:27552 R:33 HW:0 U: 2.58/m
--------------------------------------------------------------------------------
[2012-07-20 16:17:02] ICA 4 failure, disabling!
[2012-07-20 16:17:02] ICA 5 failure, disabling!
[2012-07-20 16:17:02] ICA 6 failure, disabling!
[2012-07-20 16:17:02] ICA 7 failure, disabling!
[2012-07-20 16:36:52] LONGPOLL from pool 0 detected new block
[2012-07-20 16:38:25] LONGPOLL from pool 0 detected new block
[2012-07-20 16:40:08] LONGPOLL from pool 0 detected new block
[2012-07-20 16:43:18] LONGPOLL from pool 0 detected new block
[2012-07-20 16:45:26] LONGPOLL from pool 0 detected new block
[2012-07-20 16:55:44] LONGPOLL from pool 0 detected new block
half of my boards disconnected and reconnected as new usb ports, cgminer stopped sending more work to my pool even if it is still working as it detects long polls. This is dmesg output. [636683.527463] usb 1-3: USB disconnect, device number 2
[636683.527480] usb 1-3.1: USB disconnect, device number 4
[636683.527969] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[636683.528056] ftdi_sio 1-3.1:1.0: device disconnected
[636683.531516] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1
[636683.531571] ftdi_sio 1-3.1:1.1: device disconnected
[636683.537769] ftdi_sio ttyUSB2: FTDI USB Serial Device converter now disconnected from ttyUSB2
[636683.537810] ftdi_sio 1-3.1:1.2: device disconnected
[636683.541175] ftdi_sio ttyUSB3: FTDI USB Serial Device converter now disconnected from ttyUSB3
[636683.541216] ftdi_sio 1-3.1:1.3: device disconnected
[636683.541585] usb 1-3.2: USB disconnect, device number 5
[636683.541957] ftdi_sio ttyUSB4: FTDI USB Serial Device converter now disconnected from ttyUSB4
[636683.542003] ftdi_sio 1-3.2:1.0: device disconnected
[636683.543191] ftdi_sio ttyUSB5: FTDI USB Serial Device converter now disconnected from ttyUSB5
[636683.543241] ftdi_sio 1-3.2:1.1: device disconnected
[636683.546774] ftdi_sio ttyUSB6: FTDI USB Serial Device converter now disconnected from ttyUSB6
[636683.546815] ftdi_sio 1-3.2:1.2: device disconnected
[636683.549974] ftdi_sio ttyUSB7: FTDI USB Serial Device converter now disconnected from ttyUSB7
[636683.550008] ftdi_sio 1-3.2:1.3: device disconnected
[636683.550311] usb 1-3.3: USB disconnect, device number 6
[636683.550616] ftdi_sio ttyUSB8: FTDI USB Serial Device converter now disconnected from ttyUSB8
[636683.550655] ftdi_sio 1-3.3:1.0: device disconnected
[636683.552739] ftdi_sio ttyUSB9: FTDI USB Serial Device converter now disconnected from ttyUSB9
[636683.552782] ftdi_sio 1-3.3:1.1: device disconnected
[636683.556542] ftdi_sio ttyUSB10: FTDI USB Serial Device converter now disconnected from ttyUSB10
[636683.556577] ftdi_sio 1-3.3:1.2: device disconnected
[636683.559003] ftdi_sio ttyUSB11: FTDI USB Serial Device converter now disconnected from ttyUSB11
[636683.559037] ftdi_sio 1-3.3:1.3: device disconnected
[636683.559342] usb 1-3.4: USB disconnect, device number 7
[636683.559647] ftdi_sio ttyUSB12: FTDI USB Serial Device converter now disconnected from ttyUSB12
[636683.559688] ftdi_sio 1-3.4:1.0: device disconnected
[636683.562317] ftdi_sio ttyUSB13: FTDI USB Serial Device converter now disconnected from ttyUSB13
[636683.562362] ftdi_sio 1-3.4:1.1: device disconnected
[636683.565950] ftdi_sio ttyUSB14: FTDI USB Serial Device converter now disconnected from ttyUSB14
[636683.565985] ftdi_sio 1-3.4:1.2: device disconnected
[636683.569579] ftdi_sio ttyUSB15: FTDI USB Serial Device converter now disconnected from ttyUSB15
[636683.569614] ftdi_sio 1-3.4:1.3: device disconnected
[636683.808058] usb 1-3: new high-speed USB device number 15 using ehci_hcd
[636698.920070] usb 1-3: device descriptor read/64, error -110
[636714.136074] usb 1-3: device descriptor read/64, error -110
[636714.352074] usb 1-3: new high-speed USB device number 16 using ehci_hcd
[636729.464051] usb 1-3: device descriptor read/64, error -110
[636744.680055] usb 1-3: device descriptor read/64, error -110
[636744.896057] usb 1-3: new high-speed USB device number 17 using ehci_hcd
[636755.304068] usb 1-3: device not accepting address 17, error -110
[636755.416075] usb 1-3: new high-speed USB device number 18 using ehci_hcd
[636765.824088] usb 1-3: device not accepting address 18, error -110
[636765.824235] hub 1-0:1.0: unable to enumerate USB device on port 3
[636766.080066] usb 3-1: new full-speed USB device number 2 using uhci_hcd
[636766.225103] usb 3-1: not running at top speed; connect to a high speed hub
[636766.250260] hub 3-1:1.0: USB hub found
[636766.252447] hub 3-1:1.0: 4 ports detected
[636766.537118] usb 3-1.1: new full-speed USB device number 3 using uhci_hcd
[636766.639088] usb 3-1.1: not running at top speed; connect to a high speed hub
[636766.675515] ftdi_sio 3-1.1:1.0: FTDI USB Serial Device converter detected
[636766.675636] usb 3-1.1: Detected FT4232H
[636766.675648] usb 3-1.1: Number of endpoints 2
[636766.675660] usb 3-1.1: Endpoint 1 MaxPacketSize 64
[636766.675672] usb 3-1.1: Endpoint 2 MaxPacketSize 64
[636766.675684] usb 3-1.1: Setting MaxPacketSize 64
[636766.677277] usb 3-1.1: FTDI USB Serial Device converter now attached to ttyUSB0
[636766.681010] ftdi_sio 3-1.1:1.1: FTDI USB Serial Device converter detected
[636766.681143] usb 3-1.1: Detected FT4232H
[636766.681155] usb 3-1.1: Number of endpoints 2
[636766.681167] usb 3-1.1: Endpoint 1 MaxPacketSize 64
[636766.681179] usb 3-1.1: Endpoint 2 MaxPacketSize 64
[636766.681191] usb 3-1.1: Setting MaxPacketSize 64
[636766.683866] usb 3-1.1: FTDI USB Serial Device converter now attached to ttyUSB1
[636766.687509] ftdi_sio 3-1.1:1.2: FTDI USB Serial Device converter detected
[636766.687627] usb 3-1.1: Detected FT4232H
[636766.687639] usb 3-1.1: Number of endpoints 2
[636766.687651] usb 3-1.1: Endpoint 1 MaxPacketSize 64
[636766.687663] usb 3-1.1: Endpoint 2 MaxPacketSize 64
[636766.687675] usb 3-1.1: Setting MaxPacketSize 64
[636766.689301] usb 3-1.1: FTDI USB Serial Device converter now attached to ttyUSB4
[636766.692684] ftdi_sio 3-1.1:1.3: FTDI USB Serial Device converter detected
[636766.692783] usb 3-1.1: Detected FT4232H
[636766.692793] usb 3-1.1: Number of endpoints 2
[636766.692803] usb 3-1.1: Endpoint 1 MaxPacketSize 64
[636766.692812] usb 3-1.1: Endpoint 2 MaxPacketSize 64
[636766.692821] usb 3-1.1: Setting MaxPacketSize 64
[636766.694253] usb 3-1.1: FTDI USB Serial Device converter now attached to ttyUSB5
[636766.769118] usb 3-1.2: new full-speed USB device number 4 using uhci_hcd
[636766.872093] usb 3-1.2: not running at top speed; connect to a high speed hub
[636766.910520] ftdi_sio 3-1.2:1.0: FTDI USB Serial Device converter detected
[636766.910646] usb 3-1.2: Detected FT4232H
[636766.910658] usb 3-1.2: Number of endpoints 2
[636766.910670] usb 3-1.2: Endpoint 1 MaxPacketSize 64
[636766.910682] usb 3-1.2: Endpoint 2 MaxPacketSize 64
[636766.910693] usb 3-1.2: Setting MaxPacketSize 64
[636766.913543] usb 3-1.2: FTDI USB Serial Device converter now attached to ttyUSB8
[636766.916687] ftdi_sio 3-1.2:1.1: FTDI USB Serial Device converter detected
[636766.916811] usb 3-1.2: Detected FT4232H
[636766.916823] usb 3-1.2: Number of endpoints 2
[636766.916835] usb 3-1.2: Endpoint 1 MaxPacketSize 64
[636766.916847] usb 3-1.2: Endpoint 2 MaxPacketSize 64
[636766.916858] usb 3-1.2: Setting MaxPacketSize 64
[636766.918279] usb 3-1.2: FTDI USB Serial Device converter now attached to ttyUSB9
[636766.921514] ftdi_sio 3-1.2:1.2: FTDI USB Serial Device converter detected
[636766.921634] usb 3-1.2: Detected FT4232H
[636766.921646] usb 3-1.2: Number of endpoints 2
[636766.921658] usb 3-1.2: Endpoint 1 MaxPacketSize 64
[636766.921670] usb 3-1.2: Endpoint 2 MaxPacketSize 64
[636766.921681] usb 3-1.2: Setting MaxPacketSize 64
[636766.923932] usb 3-1.2: FTDI USB Serial Device converter now attached to ttyUSB12
[636766.927514] ftdi_sio 3-1.2:1.3: FTDI USB Serial Device converter detected
[636766.927637] usb 3-1.2: Detected FT4232H
[636766.927649] usb 3-1.2: Number of endpoints 2
[636766.927661] usb 3-1.2: Endpoint 1 MaxPacketSize 64
[636766.927673] usb 3-1.2: Endpoint 2 MaxPacketSize 64
[636766.927684] usb 3-1.2: Setting MaxPacketSize 64
[636766.929279] usb 3-1.2: FTDI USB Serial Device converter now attached to ttyUSB13
[636767.005107] usb 3-1.3: new full-speed USB device number 5 using uhci_hcd
[636767.107088] usb 3-1.3: not running at top speed; connect to a high speed hub
[636767.145527] ftdi_sio 3-1.3:1.0: FTDI USB Serial Device converter detected
[636767.145649] usb 3-1.3: Detected FT4232H
[636767.145662] usb 3-1.3: Number of endpoints 2
[636767.145674] usb 3-1.3: Endpoint 1 MaxPacketSize 64
[636767.145686] usb 3-1.3: Endpoint 2 MaxPacketSize 64
[636767.145697] usb 3-1.3: Setting MaxPacketSize 64
[636767.147857] usb 3-1.3: FTDI USB Serial Device converter now attached to ttyUSB40
[636767.151504] ftdi_sio 3-1.3:1.1: FTDI USB Serial Device converter detected
[636767.151635] usb 3-1.3: Detected FT4232H
[636767.151647] usb 3-1.3: Number of endpoints 2
[636767.151659] usb 3-1.3: Endpoint 1 MaxPacketSize 64
[636767.151671] usb 3-1.3: Endpoint 2 MaxPacketSize 64
[636767.151682] usb 3-1.3: Setting MaxPacketSize 64
[636767.153281] usb 3-1.3: FTDI USB Serial Device converter now attached to ttyUSB41
[636767.156697] ftdi_sio 3-1.3:1.2: FTDI USB Serial Device converter detected
[636767.156820] usb 3-1.3: Detected FT4232H
[636767.156831] usb 3-1.3: Number of endpoints 2
[636767.156843] usb 3-1.3: Endpoint 1 MaxPacketSize 64
[636767.156855] usb 3-1.3: Endpoint 2 MaxPacketSize 64
[636767.156866] usb 3-1.3: Setting MaxPacketSize 64
[636767.159105] usb 3-1.3: FTDI USB Serial Device converter now attached to ttyUSB42
[636767.162427] ftdi_sio 3-1.3:1.3: FTDI USB Serial Device converter detected
[636767.162534] usb 3-1.3: Detected FT4232H
[636767.162543] usb 3-1.3: Number of endpoints 2
[636767.162553] usb 3-1.3: Endpoint 1 MaxPacketSize 64
[636767.162563] usb 3-1.3: Endpoint 2 MaxPacketSize 64
[636767.162572] usb 3-1.3: Setting MaxPacketSize 64
[636767.164807] usb 3-1.3: FTDI USB Serial Device converter now attached to ttyUSB43
spiccioli |
|
|
|
|
1039
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Quad XC6SLX150 Board - Initial Price £400/$640/520€
|
on: July 20, 2012, 09:42:35 AM
|
Can you share how you managed to get it stable for that long, since many are not yet.
What settings and that do you use in CGminer?
Hi Lethos, nothing fancy, I just start cgminer telling it what ttyUSB?? port (I'm on linux) to use, I'm not using the icarus-timing option. spiccioli Think that might be a keypoint to stability issues, I have noticed a lot with the worst problems with stability use windows. Guess I really need to get my arse into gear and get cgminer working on linux. Lethos, I think there are problems with usb drivers on windows, Yohan found out that inserting a usb key sometimes makes one or more boards to disappear. In my case, though, the stuck FPGA does not hash anymore, its A: value hasn't been changing for two days now, but there are no signs that the usb connections is gone, since the other FPGA on the same boards is still hashing nicely. So either the controlling FPGA "lost" that single FPGA or bitstream inside that FPGA locked up for some reason. Anyway, you can look here for a 32 bit cgminer 2.4.3 compiled for linux with just icarus support available (this is the one I'm using), you need to trust my build though. https://bitcointalk.org/index.php?topic=78239.msg993287;topicseen#msg993287 spiccioli |
|
|
|
|
1040
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Quad XC6SLX150 Board - Initial Price £400/$640/520€
|
on: July 20, 2012, 08:16:46 AM
|
Can you share how you managed to get it stable for that long, since many are not yet.
What settings and that do you use in CGminer?
Hi Lethos, nothing fancy, I just start cgminer telling it what ttyUSB?? port (I'm on linux) to use, I'm not using the icarus-timing option. spiccioli Yeah those MH/s values are wrong of course (--icarus-timing fixes that) The correct MH/s for U: 2.60/m would be 186MH/s i.e. ignore the MH/s numbers on your screen. the --icarus-timing (assuming 2.60/186 is correct) would be ~5.376 But to be sure you would use something like --icarus-timing 5.376=200Of course you can get close to the correct value instead of 5.376 using --icarus-timing short kano, I've found that cgminer 2.4.3 works as well without using --icarus-timing at all, I'm just throwing away a bigger part of each getwork and I don't see the correct hashing speed (which is not an issue for me). By the way, the used bitstream should be hashing at 190MH/s but there are boards with higher U: and other boards with a lower one, so a single --icarus-timing option would be correct just for some boards. spiccioli. |
|
|
|
|
Show Posts
