Liquid Synergy Designs Inc. -ASIC mining hardware

[randoint]

Posted this in the Klondike thread, no response yet, try my luck here. Sounds like some problems could be related or similar

I hope someone has an answer to these questions:

Currently I run 14 KLN units. There seems to be 2 issues that I run into.

First is the KLN: went idle before work was sent error:

As far as the resources on the Klondike page http://projectklondike.org/, the reason is known, however, as I run a windows 8 environment there isn't really an easy way for me to recompile the drivers. Is there any other solutions to reduce these errors? Future cgminer updates will address this?


The next issue that I seem to keep running into is stability/performance of the units:

Unless I power up the units a certain way, I tend to get a lot of zombie KLN units, or units that are plugged in, however, does not hash at all (zero hash rate, zero work units). Upon system startup and powering of the KLN units, usually all units hash. Eventually one or couple of units will stop hashing at all after a certain period of time (the unit that goes idle is random, physically speaking). As I have 14 units, cgminer should show the units as KLN0-KLN13. The units that go bad will eventually keep trying to redetect itself, and the ID of the unit will keep climbing in cgminer (eg: from KLN13 to KLN253).

Is it possible that this issue be a possibility of USB overload? I have 3 units connected to USB ports in the back pane, 5 units connected to one USB hub, and 6 units connected to another USB hub. Temperatures are under 50c

Thanks for any assistance or knowledge on these matters Smiley


edit:
Nov 19
-Tried cgminers different versions 3.50+ to latest, no success.
-Only 1 miner was not hashing in the above USB configurations. Plug only 5 USBs in each of the 2 hubs; remainder plugged into the back pane of computer. Currently everything hashes, except two units are hashing at half the rate expected. Using cgminer 3.70.
-1 of the half rate hashers completely stopped hashing after 30 mins.

[chadtn]

What clock speed are you running them at?  If I go over 352 mhz  mine start hashing at half speed.

Chad

[Unacceptable]

I too have found 3.7.0 to be the most stable version....weird  

As for this error:went idle before work was sent.I see no drop in hashrate at my pool,it seems to have no effect at all,So I ignore it  

When I start my rig,I unplug all but 1 miner,then plug each miner in waiting about 10 seconds or so between each.

I can get my rig of 6 miners to run for about 3 days max.Most of the time I do a full reboot of my PC,but I do get lucky & get away with only a reboot of CGminer about 30% of the time.

[randoint]

I agree, 3.7.0 is probably the best one right now for stablity. Currently everything is clocked at 350, there isn't anything unusual about temperatures either.

This is exactly what happens after about 30 mins of running:

https://i.imgur.com/vE8Yi2I.png

[chadtn]

I agree, 3.7.0 is probably the best one right now for stablity. Currently everything is clocked at 350, there isn't anything unusual about temperatures either.

Just as an experiment try turning the half hashers down to 300 mhz and see if that makes a difference.  Mine run anywhere from 42C to 48C and still drop to half rate if I go over 352 mhz.  Zipiju thinks it is most likely a power issue with the components on my boards.  He said that each bank of chips has it's own hardware to regulate power.  If the K16 hashes at half rate it is likely that it is only functioning on one bank of chips.

Just something to try...if you get a good average 4.5 gigahashes at 300 mhz that is the likely culprit.  If they work fine at 300 you can start bumping it up 1 mhz at a time until you find the point that a bank drops out or hardware errors start going nuts.

My two K16's have been running 24/7 flawlessly at 352 mhz on a Raspberry Pi for more than a week now.  Other than when I was initially setting them up and messing around with everything the only time they have stopped hashing was for about ten seconds to upgrade from cgminer 3.8.1 to 3.8.2.

Good luck!

Chad

[kano]

if you make sure the API is on
--api-enable
Then in the cgminer folder:
java API stats
or to remove the unwanted data:
java API stats | grep -v STA | egrep " Chip|KLN"
That shows for each chip the number of valid nonces and the number of invalid nonces returned.

e.g.

Code:

   [ID] => KLN0
   [Nonces / Chip 0] => 0007300 0007262 0007155 0007320 0007193 0007138 0007236 0007394 0007335 0007236 0007131 0007330 0007166 0007221 0007184 0007279
   [Errors / Chip 0] => 0000000 0000000 0000000 0000000 0000000 0000000 0000000 0000000 0000002 0000001 0000000 0000000 0000000 0000001 0000001 0000001
   [ID] => KLN1
   [Nonces / Chip 0] => 0007240 0007302 0007099 0007197 0007234 0007401 0007343 0007208 0007265 0007266 0007303 0007202 0007253 0007256 0007400 0007299
   [Errors / Chip 0] => 0000000 0000000 0000000 0000001 0000000 0000001 0000000 0000000 0000000 0000000 0000000 0000000 0000000 0000000 0000000 0000000

[bitcoinanon]

I was reading through this thread to find an answer to my problem, but it was taking too long so I thought i would just ask.
I have compiled cgminer on my laptop running Ubuntu and hooked up my klondike's but when i run cgminer it tells me that it does not find any devices. I didn't think I needed the sdk download since I am not gpu mining. Is there something else that I am missing? Or do I need to download ADL_SDK for my comp to recognize the klondikes?

[cp1]

I was reading through this thread to find an answer to my problem, but it was taking too long so I thought i would just ask.
I have compiled cgminer on my laptop running Ubuntu and hooked up my klondike's but when i run cgminer it tells me that it does not find any devices. I didn't think I needed the sdk download since I am not gpu mining. Is there something else that I am missing? Or do I need to download ADL_SDK for my comp to recognize the klondikes?

Make sure you have plugdev permissions on that user.  You can try running with sudo to see if this is your problem.

[ionstorm]

Can these be hotplugged to the PCI-E connectors or should I shut down PSU?  Ive noticed I get approximately the same hashrate between 340mhz-360mhz, anyone else experience this?  Also I was wondering if it is safe to run a 25gh/s butterfly labs miner with 5 klondikes on a Silverstone ST60F-ES PSU?  I calculated 480w, 60wx5(klondikes) and 180w for the Little Single 25gh.  I'm not quite sure exactly what wattage the 25gh/s runs at i've only seen one person post the power specs of that unit.  I'ts been running 48hours stable with them all connected but do I need to worry about blowing the PSU?

[rammy2k2]

any news for us, the customers who paid for a such a long delayed product?

[Unacceptable]

I was reading through this thread to find an answer to my problem, but it was taking too long so I thought i would just ask.
I have compiled cgminer on my laptop running Ubuntu and hooked up my klondike's but when i run cgminer it tells me that it does not find any devices. I didn't think I needed the sdk download since I am not gpu mining. Is there something else that I am missing? Or do I need to download ADL_SDK for my comp to recognize the klondikes?

1.Update the package index: # sudo apt-get update
2.Install libudev-dev deb package: # sudo apt-get install libudev-dev
have to go to http://pkgs.org/download/libudev-dev & download libudev-dev_204-5_amd64.deb.

[Unacceptable]

Can these be hotplugged to the PCI-E connectors or should I shut down PSU?  Ive noticed I get approximately the same hashrate between 340mhz-360mhz, anyone else experience this?  Also I was wondering if it is safe to run a 25gh/s butterfly labs miner with 5 klondikes on a Silverstone ST60F-ES PSU?  I calculated 480w, 60wx5(klondikes) and 180w for the Little Single 25gh.  I'm not quite sure exactly what wattage the 25gh/s runs at i've only seen one person post the power specs of that unit.  I'ts been running 48hours stable with them all connected but do I need to worry about blowing the PSU?

That is a single rail PSU with 12 volt @42 amps=580 watts.

You need a larger PSU ASAP !!!!! 

[bitcoinanon]

my Klondike 16's are hashing away. THanks again Steamboat and liquidsynergy and project klondike.

[ScaryHash]

So at this point I have 4 Klondikes that are not working right.

2 of them accept ZERO work units, and produce nothing but errors, instead of accepted shares.

2 more are hashing at about 2.1 to 2.5 Gh/s at 350 mhz, so that means that only one bank is working.

I have not attempted to flash either one of them, but I did get a PickIT3 just in case off Ebay about a week ago.

So my option is either to flash those, and risk bricking them??

Or sending them back to Steamboat??

I thought I paid for the fully assembled and tested option. Has there actually been any testing before shipping these things out??

4 out of 16 not working right is not what I would call "fully tested".

If I attempt to flash them, and somehow they get bricked (I am relatively competent with electronics stuff), then all Steamboat has to do is claim it's my fault?

Is there a repair/exchange service with the assembly house, Steamboat??

I thought we were paying "top dollar" for "quality US assembly services". Do these things come with a warranty from the assembly house?

[chadtn]

Have you tried running them at 300 mhz.  I believe they were originally advertised as 4.5 gigahash miners.  That would technically make anything higher an unsupported overclock.

BTW...mine were shipped with the latest firmware already loaded.  I bought the programmer too, but didn't need it.

Chad

[cardcomm]

Has anyone here actually had contact with Steamboat recently? I know some members of this forums were visiting and helping with assembly.

I'd really like to get some insight from SOMEONE that has any idea whats going on with the assembly refunds and hosting?

If SB has abandoned this thread as it seems he might have, we need to band together and take some sort of action. I want my assembly (or even my shipping) and I know people want their hosted miners working for them.

If there is someone out there that knows FOR CERTAIN that progress is being made, please let us know what. And also pass along to Steve the obvious to need for him the address this himself.

This is beyond absurd - Steamboat hasn't even logged in to this forum since November 12, 2013, 11:55:52 AM.

I fear we've been well and truly fucked, laddies!

[mjmvisser]

BKKCoins is OK! He was in a motorcycle accident and is lucky to be alive: https://bitcointalk.org/index.php?topic=190731.msg3649002#msg3649002

As for all of you clamouring for Steamboat's blood: give it a rest, already. Did you not read the GIANT BOLD DISCLAIMER warning prospective buyers that this project carries a high level of risk and has many factors outside of Steamboat's control?

[nightengale]

I think being too busy to consider processing refunds is something that is within SB's control.

[nightengale]

Addendum: I also think communicating or not communicating with customers is something that is probably within his control as well.

Your patience is touching, but misplaced.

[Unacceptable]

Steamboat IS working on an update & info on the hosting.Not sure when,but he is gonna do it soon .

I saw him tonite,he said the update is being compiled as of this moment  

He's not going anywhere,just trying to figure the best solution for everyone!!!!!