I'm using a pi with minepeon with 3.6.6 compiled from scratch and everything has been working fine at 350mhz with four of them on a powered usb2 hub.
I did have to shut down PSU, reboot Peon, turn on PSU, to get them to come up the first time.
Topic: Liquid Synergy Designs Inc. -ASIC mining hardware - page 40. (Read 423279 times)
I think it's 3.7.0, 3.6.6 works fine for me.
My pi has been running rock solid with six block erupters over the last couple of months. I tried removing all of the hubs and just plugging two K16's straight in to the pi. I then tried known good versions of cgminer that I built and ran with my block erupters without any problems. It's been running for months without a single crash until the K16's started hashing. I just got done testing it with:
3.5.1
3.6.6
3.7.0
Anyone have some tips on what else I can try? I'm running Raspbian Wheezy. It must be something going on with the pi itself. I'm going to start doing an internet search to see if I can pull up some kind of error log to see why the system is going down. I'm a linux noob. heh..
Thanks!
Chad
I think it's 3.7.0, 3.6.6 works fine for me.
They are definitely not playing nice on my pi right now...It just crashed on a fresh 3.7.0 build of cgminer and I'm running out of ideas. Going to start swapping USB ports and hubs around, but this set up has been running six block errupters for two months and until today I have never had it crash. Might try moving the errupters to another computer and see if that settles it down.
Chad
Chad
I had been running the git master, somewhere between 3.6.6 and 3.7.0.
I just built 3.7.0, and so far so good. I did still modify driver-klondike.c to increase KLN_KILLWORK_TEMP to 65.5.
BTW, a Pi just does not make a good miner host in my experience. While it works in some cases, it fails badly under any kind of non-moderate CPU load (USB dies, which includes the on-board ethernet). Mine kept failing like that with just 3 K16s attached. I'm guessing the klondike driver hits the CPU hard enough sometimes to cause that kind of failure mode.
I'm currently mining using a Foxconn nt330i with an Atom CPU. Works much better.
Soon I'll have an Odroid-U2 in my hands to try. Should have plenty of power with its quad-core ARM chip.
A BeagleBone Black works OK too, but I don't care for its flavor of linux.
I just built 3.7.0, and so far so good. I did still modify driver-klondike.c to increase KLN_KILLWORK_TEMP to 65.5.
BTW, a Pi just does not make a good miner host in my experience. While it works in some cases, it fails badly under any kind of non-moderate CPU load (USB dies, which includes the on-board ethernet). Mine kept failing like that with just 3 K16s attached. I'm guessing the klondike driver hits the CPU hard enough sometimes to cause that kind of failure mode.
I'm currently mining using a Foxconn nt330i with an Atom CPU. Works much better.
Soon I'll have an Odroid-U2 in my hands to try. Should have plenty of power with its quad-core ARM chip.
A BeagleBone Black works OK too, but I don't care for its flavor of linux.
Er...
Code:
[2013-11-04 20:52:19] Started cgminer 3.7.0
[2013-11-04 20:52:21] Klondike (2:5) detect read failed (0:-7)
[2013-11-04 20:52:22] Klondike (2:5) detect read failed (0:-7)
[2013-11-04 20:52:24] Klondike (2:4) detect read failed (0:-7)
[2013-11-04 20:52:25] Klondike (2:4) detect read failed (0:-7)
[2013-11-04 20:52:28] Klondike (2:3) detect read failed (0:-7)
[2013-11-04 20:52:29] Klondike (2:3) detect read failed (0:-7)
[2013-11-04 20:52:31] Klondike (2:2) detect read failed (0:-7)
[2013-11-04 20:52:32] Klondike (2:2) detect read failed (0:-7)Segmentation fault (core dumped)
I spoke too soon about no problems. My raspberry pi has started crashing now. I reverted back to a couple of older versions of cgminer that ran for more than a month error free and they crashed too. I've got 3.7.0 building right now. Hopefully that will fix me up. What version is everyone else running? I've got six block erupter running with the K16's. Maybe they aren't playing nice with each other.
Chad
I am using a RasPI with a powered 7-port USB hub and 4 klondike miners attached.Chad
I have not had my RasPI crash. Using CGM 3.6.6, raspbian wheezy 7/26/13.
I have 2 USB hubs one is a Dlink the other is Rosewill.
The RasPi does not like the Dlink hub. The RasPi hangs during boot about 50% of the time when the Dlink attached.
I spoke too soon about no problems. My raspberry pi has started crashing now. I reverted back to a couple of older versions of cgminer that ran for more than a month error free and they crashed too. I've got 3.7.0 building right now. Hopefully that will fix me up. What version is everyone else running? I've got six block erupter running with the K16's. Maybe they aren't playing nice with each other.
Chad
Chad
I requested that my K16's be shipped as is on Thursday October 31st. They just showed up in the mail a couple of hours ago and have been hashing away at an average of 5.5 gigahashes at 350mhz for the last fifteen minutes. Zero hardware errors so far and temps are hovering around 52C. One of my big questions that never got answered was if the units being shipped had been flashed already with the known good firmware. I bought the pickit3 programer too, but it appears the K16's are ready to go right out of the box. EXCELLENT PACKAGING!!
Chad
If the I2C code gets done then you might want to use your pickit3 to update.Chad
I am sure that SB loads the best FW available before shipping out units.
He's probable up late at night to make this happen.
I requested that my K16's be shipped as is on Thursday October 31st. They just showed up in the mail a couple of hours ago and have been hashing away at an average of 5.5 gigahashes at 350mhz for the last fifteen minutes. Zero hardware errors so far and temps are hovering around 52C. One of my big questions that never got answered was if the units being shipped had been flashed already with the known good firmware. I bought the pickit3 programer too, but it appears the K16's are ready to go right out of the box. EXCELLENT PACKAGING!!
Chad
Chad
The only way he could refund based on BTC paid would be if he only converted 75% of BTC to USD, which would be silly. So if you paid $100 for assembly and get 25% back you'll get $25, or about 0.12 BTC.
BTC payments were instantly converted to dollars by BitPay so SB could pay suppliers in dollars.
I can almost guarantee refunds are going to be processed in dollars, then converted to BTC (with unfavorable results for us). The exchange rate was miserably low when I paid, because like others I was trying to meet the deadline SB had laid out. And I'll likely be punished for that...
I can almost guarantee refunds are going to be processed in dollars, then converted to BTC (with unfavorable results for us). The exchange rate was miserably low when I paid, because like others I was trying to meet the deadline SB had laid out. And I'll likely be punished for that...
That will almost certainly cause a shitstorm. He's already talking about keeping 75% of our assembly costs. Throw in a screw job on the exchange rate, and my assembly funds would be just plain gone.
Hell, do enough voodoo with the exchange rate, and we could all end up owing SB money! ROFL!
This just keeps on getting better and better, eh?
It's _almost_ like this was a high risk investment--I sure wish someone told me that before I consciously sent a stranger on the Internet money! Oh well, maybe I'll learn my lesson one day, and take the wins with the losses....
[edit; grammar is hard]
BTC payments were instantly converted to dollars by BitPay so SB could pay suppliers in dollars.
I can almost guarantee refunds are going to be processed in dollars, then converted to BTC (with unfavorable results for us). The exchange rate was miserably low when I paid, because like others I was trying to meet the deadline SB had laid out. And I'll likely be punished for that...
I can almost guarantee refunds are going to be processed in dollars, then converted to BTC (with unfavorable results for us). The exchange rate was miserably low when I paid, because like others I was trying to meet the deadline SB had laid out. And I'll likely be punished for that...
That will almost certainly cause a shitstorm.
You took the words right out of my mouth...
BTC payments were instantly converted to dollars by BitPay so SB could pay suppliers in dollars.
I can almost guarantee refunds are going to be processed in dollars, then converted to BTC (with unfavorable results for us). The exchange rate was miserably low when I paid, because like others I was trying to meet the deadline SB had laid out. And I'll likely be punished for that...
I can almost guarantee refunds are going to be processed in dollars, then converted to BTC (with unfavorable results for us). The exchange rate was miserably low when I paid, because like others I was trying to meet the deadline SB had laid out. And I'll likely be punished for that...
That will almost certainly cause a shitstorm. He's already talking about keeping 75% of our assembly costs. Throw in a screw job on the exchange rate, and my assembly funds would be just plain gone.
Hell, do enough voodoo with the exchange rate, and we could all end up owing SB money! ROFL!
This just keeps on getting better and better, eh?
I requested shipment Sat afternoon and got a tracking number Sun evening. He also answered a few questions.
I sent my request to ship my order on Saturday evening, CST and received my tracking number promptly this morning. Thanks for your dedication and effort, Steamboat!
BTC payments were instantly converted to dollars by BitPay so SB could pay suppliers in dollars.
I can almost guarantee refunds are going to be processed in dollars, then converted to BTC (with unfavorable results for us). The exchange rate was miserably low when I paid, because like others I was trying to meet the deadline SB had laid out. And I'll likely be punished for that...
I can almost guarantee refunds are going to be processed in dollars, then converted to BTC (with unfavorable results for us). The exchange rate was miserably low when I paid, because like others I was trying to meet the deadline SB had laid out. And I'll likely be punished for that...
Yeah, I agree, so now that we've gotten the chips, and refunded the other chips and stuff and we're finished with yifu, how bout we go beat that dog (yifu) to a pulp? I mean, with lawyers and law in hand etc etc... 
He should be held responsible in some way
He should be held responsible in some way
To me it doesn't matter if the purchase was denominated in Turkey Feathers. I paid in BTC, therefore I expect to be refunded in BTC.
The way I remember paying for assembly was this: We were given less then 1 week to procure BTC for assembly. I bought at what was then a high price, and paid a premium for the service to get BTC in time to order. THEN SB extended the payment deadline. So yeah, I paid in BTC. Hard gotten BTC at that.
Everyone here knows the price of BTC is volatile. That's one reason I've been so anxious to get refunded. I've expected all along to get refunded in THE SAME CURRENCY I PAID.
If SB wanted to avoid getting screwed on the exchange rate on the refunds, maybe he should have issued them when BTC were still closer to $140. U.S.
For me the unequivocal bottom line for BTC transactions that they are just that - BTC transactions. You can't come back later and say sorry, those prices were USD, we just HAPPENED to collect them as BTC!
(Yes, if BTC prices drop like a rock, I'll STILL feel the same. Believe me, it's happened before.)
BTW that wording about not being punished is kinda funny cuz it sorta feels like I'm already being punished...
I don't remember what the value was exactly, but say you paid $130 for everything and BTC was $100 at the time, you paid 1.3 BTC, right? Now that BTC is $220, you can expect 0.59 BTC back for your $130.
In BTC, that is what is called losing value.
In BTC, that is what is called losing value.
I am hoping it falls somewhere in between, not exactly full refund in BTCs, but more than we paid in terms of dollars.
I suspect SB and Co made margin on the equipment purchases that they kept in the form of BTCs from our payment. To refund us in $ face values of the equipment they purchased without compensation for holding the margin (in BTCs) at current market valuation wouldn't be the best business practice. We should share in that risk factor IMO and I hope that's part of the reason why it's taking a long time for them to refund us. Assuming they made 10% on the assembly/hosting fees, then they're looking at .1 BTC per $100 of customer spend (assuming my memory of BTC conversion is accurate at the time of the assembly/hosting payment deadline)
In today's BTCs, that's a $13, or 130%, appreciation per $100 of customer spend in 4-months without supplying a hosted product. More than enough to refund all of the customers who never received assembly/hosting and 3% remaining to keep for themselves as a handling "fee"
Jump to: