|
That looks pretty good HotSwap.
Thanks !
|
|
|
|
I do have a couple of miners that show that they are hashing, but they show no work units accepted or sent in CGminer.
Moved them from one computer to another (Linux to Windows), and they do the same thing, show hashing but no work units accepted.
Do you guys think they need to be reflashed or something? They do show some amount of hardware errors, seem like above normal compared to the others.
Pretty weird.
What are the temps  Have you checked the power cables are plugged all the way in,no undue stress on them pulling them just a little loose,your PSU is able to supply enough power 60 watts per is what I use to judge by  They appear to be hashing, showing about 5.3 Gh/s, the temps are the same as the ones that show accepted work units (about 40ish). But, these 2 do not show accepted work units, just the same amount after HW: 128309, in CGminer. I'm assuming those are hardware errors. It shows zero WU: and zero A: the other ones are show A: 937989 and HW: 85. I have two of these that do not show anything but a zero WU: 0, whereas the other ones show WU: 75.9 , and stuff like that. How the hell do I post a stinking picture? Anyway, I think these two are bad. They've never done anything, I'm guessing WU: means work units? My jalepeno has a rating of WU: 72.9, and the other klondikes are like 77.2 or thereabouts. Is there a way to somehow fix them or reflash them?? They seem to be hashing, just not really accepting work units. I moved them from one machine to another (Linux to Windows, and back again), tried different USB ports, but it's always the same symptom. Tried it with different power supplies, different cables, different PCI-E power slot, always the same thing. The little LED at the bottom is flashing every once in a while...weird. Seems kind of high failure rate for 2 out of 16 units. That's more than 10%.... |
|
|
|
|
I bought an ASSRock mobo earlier this year.
The first one was DOA, the second one was DOA, and the third one would post hung up all the time while booting 2 different operating systems.
Needless to say, I got my money back after sending the 3rd one back, then I bought an ASUS that has been flawless.
|
|
|
|
|
I do have a couple of miners that show that they are hashing, but they show no work units accepted or sent in CGminer.
Moved them from one computer to another (Linux to Windows), and they do the same thing, show hashing but no work units accepted.
Do you guys think they need to be reflashed or something? They do show some amount of hardware errors, seem like above normal compared to the others.
Pretty weird.
|
|
|
|
|
Great service and experience.
The network was slow yesterday, but they even sent me the $$ before full confirmation of the BTC I sent them.
No problems whatsoever.
|
|
|
|
|
Interesting.
I'll do a test transaction and see how it works out.
|
|
|
|
|
I had not even seen that one...lol
Pretty funny !
|
|
|
|
Even if you disonnect during programming you can never brick it with pickit3. Might be possible to brick them with usb boot loader tho, if the bootloader is part of the data being overwritten in the programming process. In that case, it would require a pickit3 reprogramming to unbrick it. So if you have a number of miners, I'd go get a pickit3 on ebay and get those miners hashing asap  worry bout firmware later I ordered a PickIt3 just for kicks, but the miners work pretty well out of the box. In other words, the PickIt3 is not necessary at this time. It might be in the future. The miners work fine. If you have to restart them up, you have to unplug them, and I at least hotplug them 2 at a time into CGminer, those 2 start hashing and once they get up to max Gh/s, at 325 Mhz, I hotplug 2 more, and so on. It seems that CGminer gets confused sometimes, or it may be a driver issue, even with the changed parameters in CGminer recompile. Sometimes, one KLN will get stuck at 0.00 Gh/s for a while, and it needs to be re-plugged in. But overall, they work fine. They do suck down power though. Take about 55 watts each at 325 Mhz. I have 10 running + a BFL single, and that whole setup + 2 fans sucks down 712 Watts at about 86-90 Gh/s. (off a killawatt meter). The computer is not included in that figure. I have the window totally open, and it's been below freezing outside. The room is still nice and toasty with the miners next to the window. |
|
|
|
Well hold onto it, id be running the shit out of it if I was you. 1THs can bring some coins in for another month easy!
oh it's running. it would be blasphemous to hold onto it and not use, I think. LOL I meant forget about selling it! Just wait, make some coins now and when all the let down Hashfast and Cointerra peeps get BFL'd you can bang that off for 7300.00 then!!! BFL'd ... now that's verb. BFLed = to be lied to, cheated, duped, and no product delivered for one year, while using your money for personal gain. That's like, worse than a ponzi scheme.  |
|
|
|
Hey Guys, I'm having trouble getting my K16s to even start up. I'm using a standard ATX PSU (Corsair CX430) it should be a case of plugging it in and getting it running shouldn't it? Am I missing something really obvious here?
I find it hard to believe that everyone of my miners doesn't work, so I must be setting up my PSU wrong, which I didn't think was even possible.
Find the green wire on the 24pin ATX connector and use a paperclip (bare metal) and connect it to the black wire next to it to turn on your PSU. Also, I found that 5 Klondike16's won't draw enough power at idle to make some powersupplies stay on (All non-haswell compatible PSU's for example) so adding a small load like hooking up an old harddrive to the PSU makes it stay on. Just thought I'd mention it if anybody has troubles with and old psu. Cheers Hook up 2 or 3 of them with a molex connector, so the fan is on, and then put a couple of more fans on the power supply. Power supplies need a minimum load to stay on. |
|
|
|
|
Pretty soon, all of these ASIC companies are going to go out of business, because nobody in their right mind will pay for overpriced ASICs that will never ROI.
Nothing really wrong with not ROIing, as long as you support the network. But it's not worth paying through the nose for.
|
|
|
|
|
Mine are still mining.
I figure, why go through the hassle of trying to sell them, and when BTC hits $500, they will actually be profitable.
Just keep mining, be happy.
|
|
|
|
|
5nm ASICS aren't going to happen before Intel or IBM actually make the technology mature.
As for BFL, why would you keep pi$$ing away money at them, when they've consistently not delivered on time, lied to their customers, and showed to be completely incompetent in terms of engineering and delivering a product on time?
I consider my Jalepenos that have not shipped yet sunk costs also, but I'm not going to be continually sinking money into something that's already sunk.
I figure when they get here, I'll just add their hash rate to the ScaryCluster, and be done with it.
|
|
|
|
Just out of curiosity, what USB hubs are you guys using? My Ankers for some strange reason do not work anymore, on either windows or linux. Must be some sort of weird usb 3.0 bug in those hubs, or some weird cgminer issue.
Finally got use out of my Mondohub 28 port ! Where possible, try using USB 2 ports vs USB 3 ports, I've found. Yep, my Ankers are totally worthless. I just got a Belkin 2.0 7-port powered hub (2.0 amps max) from Best Buy, and it did the trick. On another note, one of my Klondikes must have had it's fan connector disconnected by me brushing up against it while I was connecting another one, and it sat there, heated up, and SPOOGED a huge wad of creamy thermal compound all over the table and my hand... Who would have thought that with the price of BTC going up, some K16 would have spilled a load... At least, I hope it was just thermal compound... |
|
|
|
|
solved the problem thanks to zipju. Check out the klondike org under the raspberri pi. YOu have to recompile and change the variables about line 58 to this:
#define REPLY_WAIT_TIME 25
#define CMD_REPLY_RETRIES 4
The default values are 100 and 8 respectively.
I did it and recompiled on Linux. Unfortunately, I have no clue how to do that on windows.
Less errors.
|
|
|
|
Thank you for the suggestion Zipiju, I had thought that only applied to raspberry-pi, but I tried it, and it did help quite a bit, on Linux, where I can compile it easily. On my windows machine, it's another story, but it seems to be working ok. It seems if you add too may K16 too fast, cgminer gets confused. Best to add them one at a time, while keeping cgminer waiting on hotplug. At least, that works for me. |
|
|
|
For whatever reason, my klondikes say KLN2 went idle before work was sent over and over again. No idea what is going on, using CGminer 3.7.2 |
|
|
|
|
Well, I finally connected everything up with new Belkin usb 2.0 7-port hubs, because the Anker 3.0 hubs were not recognizing the K16's, and now I'm getting another error"
KLN2:0 went idle before work was sent
KLN3:0 went idle before work was sent
.
.
So only 1 out of 6 KLN is actually hashing, the rest just sit there at zero hash rate. WTF ! They were working before, and now nothing.
Having the same problem on windows as on Linux. What is up with this??
Using cgminer 3.7.2 on linux, and same on windows...crazy stuff. On windows this appears to happen when the zadig driver does not load properly. But now it's happening on my Linux box too (Linux mint 14) with custom compiled cgminer.
Anybody got any ideas?
|
|
|
|
Xian, I happen to have 18 myself. What is your solution for powering them? I didn't plan ahead for my shipment all that well, so I currently have 12 attached to a standalone 1000W ATX PSU; the other 6 are leeching off of a different PC's spare PCI-E cables (in a different room altogether). I'd like to consolidate them if I can.
Using a Corsair TX 850 to power 10 of them, and using the PCIE cables off a RaidMax 1000W that is powering the host CPU to drive the other 8 K16's. Just out of curiosity, what USB hubs are you guys using? My Ankers for some strange reason do not work anymore, on either windows or linux. Must be some sort of weird usb 3.0 bug in those hubs, or some weird cgminer issue. My klondikes do not like USB 3.0 at all. I can only run mine off the built in USB ports on the computers (either the windows7 or the linux box). They just are not recognized off the Anker 3.0 hubs. I keep thinking its either a bug in CGminer 3.6ish and above, because they do not work with the block erupters anymore either, but used to work fine with CGminer 3.5.0... I have an ancient Dlink hub that works fine (weird), but it only has 4 slots. Totally friggin strange ! |
|
|
|
I have a USB driver question (not a complaint). Have you changed any USB driver components between 3.6.4 and 3.7.2? Because all of a sudden, I cannot for the life of me get CGminer 3.7.2 to work with my USB block erupters at all, while going thru Anker USB hubs (I have two hubs, none of them wants to work with CGminer 3.7.2). If I reboot, and start up CGminer 3.6.4, same machine, different CGminers in different directories, 3.6.4 works fine. I start up 3.7.2, no AMUs get recognized thru the hub. The only way they get recognized by CGminer 3.7.2 is if I plug them into the computer's usb ports directly. The Anker hubs are USB 3.0 hubs, so it seems like there is some kind of issue when going from USB 2.0 to USB 3.0., either with CGminer or the Anker hubs. This is a pure Linux Mint 14 machine, AMD processor, with the each version of CGminer compiled using --enable-icarus --enable-klondike --no-gpu --disable-opencl I don't remember what the flags were for each compile (I think I have them written down somewhere), but the earlier version had a different set...I'm guessing that's important? (I think I loaded libtool, libncurses-dev yasm curl , for the 3.6.4 compilation, but not for the 3.7.2 compilation). The 3.7.2 compile I just did cd cgminer chmod +x ./autogen.sh ./autogen.sh ./configure --enable-icarus --enable-klondike --no-gpu --disable-opencl make Version 3.6.4 used to also recognized Klondikes going thru the Anker hub, but it does not anymore under 3.7.2. Both icarus and klondikes work fine when plugged directly into the usb ports under 3.6.4. Weird, isn't it?  Any thoughts would be greatly appreciated. Thank you for all your work on this. |
|
|
|
|
Show Posts
