ASICminer will just rub their hands together and say "lets party" from Dec well into the new year.
Then this comes into play: We would like to state that If any of our competitors continues to add large amounts of hashing power to the network during December, January or February. We will continue to release our devices as competitively priced as we can to protect our customers share of the network.
|
|
|
|
Just received this update? Talking about March 2014? HUH? I thought these were to ship this year October? What's going on? So there will be three entire months other companies will be shipping miners and KNC will not be? That doesn't make sense. They need to understand they are also in competition with other mining companies. Not just themselves, right? I don't get it. You mean I could be waiting the entire winter months after paying months ago??? Damn, sounds like BFL all over again, no?
KnCMiner Network Protection Statement
At KnCMiner we are aware of the service we are providing to our customers. We are also aware that we need our customers to have a return on their devices in order to purchase form us again. With the scale of the supply chains, agreements and factories we have access to, we need to be cautious we don’t ship too many devices and therefore reduce the return to our customers. So with that in mind our plan is to do as follows:
We will ship no devices in December 2013, January 2014 or February 2014. Meaning that once we have taken the difficulty up at the end of November we will not release any more hashing power for 3 months. We will then release our new generation of devices, which will begin shipping in March 2014. These devices will also have a much higher GH/$ rating than any of our current offerings.
We would like to state that If any of our competitors continues to add large amounts of hashing power to the network during December, January or February. We will continue to release our devices as competitively priced as we can to protect our customers share of the network.
Thanks
KnCMiner Team
What they basically say, is that they plan to be finished with all batch 1 deliveries by the end of November. Interesting. Not BFL: they are talking about the next wave, after they are done delivering all the currently ordered devices. |
|
|
|
Saturn is listed as drawing max 500W. Do you think a 600W Corsair that I have lying around would be enough or should I go for a bigger PSU?
If your 600w PSU is 80Plus Silver, it can handle 510w. If it's 80Plus Bronze, 492w. I've read that non-80Plus PSUs can be as low as 50-60% of declared capacity. Thanks, I think I'll go for a new 750W 80Plus Silver PSU (EDIT: when the time comes). However, reading up a bit here: http://en.wikipedia.org/wiki/80_PlusDoes not 600W 80Plus Silver PSU mean that it will deliver 600W to the device, but will draw 675W from the wall? |
|
|
|
|
I see. Thanks for the explanation.
|
|
|
|
Just noticed that after a few replies on different threads lately, my activity counter still stays at 154. Meta-warning: wonder if this question will change that.  EDIT: Nope, still 154. |
|
|
|
- specify an alternate reg and inductor allowing 3A power (not for USB 2.0 ports) There have been a number of questions regarding the (not for USB 2.0 ports) reference BKKCoins. Can you explain in a bit more detail, only if you have the time, about this reference? Pardon my ignorance I just want to make sure people are clear about the reference. A USB 2.0 port only needs to provide a max. of 500mA @ 5V. And sometimes they cannot do even that if all ports are drawing near max. Good USB hubs like the Anker ones provide enough juice that you may be able to draw more, but it's beyond spec. USB 3.0 hubs seem to be better as their spec has a max of 900mA. Some ports can provide more when operating as battery charger mode, but aren't required to when operating as data ports. And then you have issues regarding the RasPi not working with 3.0 hubs, and cgminer having problems on RasPi with running multiple devices at once. So there is many factors to determine what you can actually do, or get away with, beyond what "should" work. Some threads on this forum discuss these issues but I haven't kept abreast of the latest details. **** I've been running on RasPi for a couple days non-stop at 330MHz with around 0.6% errors, and no issues at all. I'll be boosting to 340 soon to see how that works. I'm waiting for the new boards to do a full-populate and test. I'll not solder the ASICs by hand this time so it will be all 16 at once in the oven. Will K1 stay within 0.5A specs of USB 2.0 or will it try to draw more from the port, especially when overclocked? Some (was it Bicknellski?) say that it should be possible to clock them up to do close to 450MHs. |
|
|
|
Far from vague. Pretty much details what concerns you need to have when sourcing 2.0 vs 3.0 USB hubs given the limits imposed typically by 2.0 specs. With vague, I meant if K1 would stay within USB 2.0 specs of 0.5A or if it would overdraw. |
|
|
|
Added to the list. What are the specs for its AC adapter? Couldn't find them anywhere. |
|
|
|
|
Finally we are moving:
Last price:$81.32
Daily change: -$9.65 (-10.61%)
Day's range:$78.92 - $91.00
Today's open:$90.96
24h volume15930 BTC
PS: The order book @ Bitstamp looks really one-sided!
|
|
|
|
cbuchner1, I stopped trying to build as I finally managed to download your pre-built archive from Mega.co.nz after trying 5 different machines what felt like 500 times. Could you release the prebuilt archive on some other file sharing service? Now, some results: Run on laptop with Quaddro FX 880M. Really nice. I can't compare to CgMiner as it always crashed on all my nVidia cards, but for comparison, poclbm doing SHA-256 managed to give max 12MHs on the same card: *** CudaMiner for nVidia GPUs by Christian Buchner ***
This is version 2013-07-13 (alpha)
based on pooler-cpuminer 2.3.2 (c) 2010 Jeff Garzik, 2012 pooler
Cuda additions Copyright 2013 Christian Buchner
My donation address: LKS1WDKGED647msBQfLBHV3Ls8sveGncnm
[2013-07-18 10:36:45] 1 miner threads started, using 'scrypt' algorithm.
[2013-07-18 10:36:45] Starting Stratum on stratum+tcp://stratum.give-me-ltc.com:3333
[2013-07-18 10:36:50] GPU #0: Quadro FX 880M with compute capability 1.2
[2013-07-18 10:36:50] GPU #0: interactive: 1, tex-cache: 0 , single-alloc: 0
[2013-07-18 10:36:50] GPU #0: Performing auto-tuning (Patience...)
[2013-07-18 10:37:08] GPU #0: 15.67 khash/s with configuration 12x6
[2013-07-18 10:37:08] GPU #0: using launch configuration 12x6
[2013-07-18 10:37:28] accepted: 1/1 (100.00%), 15.29 khash/s (yay!!!)
[2013-07-18 10:37:41] accepted: 2/2 (100.00%), 15.24 khash/s (yay!!!)
[2013-07-18 10:37:52] accepted: 3/3 (100.00%), 15.26 khash/s (yay!!!)
Ctrl-C
[2013-07-18 10:38:31] workio thread dead, waiting for workers...
[2013-07-18 10:38:31] worker threads all shut down, exiting.
--texture-cache 1 reduced the speed to 9.79kh/s (9.79 khash/s with configuration S6x5) --texture-cache 2 reduced the speed to 9.90kh/s (9.90 khash/s with configuration 12x5) A small bug report. I added -t 8 argument just for fun and got the followign. Maybe better error handling is in order? *** CudaMiner for nVidia GPUs by Christian Buchner ***
This is version 2013-07-13 (alpha)
based on pooler-cpuminer 2.3.2 (c) 2010 Jeff Garzik, 2012 pooler
Cuda additions Copyright 2013 Christian Buchner
My donation address: LKS1WDKGED647msBQfLBHV3Ls8sveGncnm
[2013-07-18 10:39:05] Starting Stratum on stratum+tcp://stratum.give-me-ltc.com:3333
[2013-07-18 10:39:05] 8 miner threads started, using 'scrypt' algorithm.
[2013-07-18 10:39:06] GPU #2: ÙTÐ☻ with compute capability 56620564.257475133
[2013-07-18 10:39:06] GPU #1: øSÐ☻ with compute capability 53605140.257475133
[2013-07-18 10:39:06] GPU #5: {TÐ☻ with compute capability 62911316.257475133
[2013-07-18 10:39:06] GPU #2: interactive: 1, tex-cache: 0 , single-alloc: 0
[2013-07-18 10:39:06] GPU #1: interactive: 1, tex-cache: 0 , single-alloc: 0
[2013-07-18 10:39:06] GPU #7: ♂TÐ☻ with compute capability 66581652.257475133
[2013-07-18 10:39:06] GPU #4: {ÿ║☻ with compute capability 61667220.257475133
[2013-07-18 10:39:06] GPU #0: Quadro FX 880M with compute capability 1.2
[2013-07-18 10:39:06] GPU #5: interactive: 1, tex-cache: 0 , single-alloc: 0
[2013-07-18 10:39:06] GPU #6: +SÐ☻ with compute capability 64352468.257475133
[2013-07-18 10:39:06] GPU #7: interactive: 1, tex-cache: 0 , single-alloc: 0
[2013-07-18 10:39:06] GPU #4: interactive: 1, tex-cache: 0 , single-alloc: 0
[2013-07-18 10:39:06] GPU #0: interactive: 1, tex-cache: 0 , single-alloc: 0
[2013-07-18 10:39:06] GPU #6: interactive: 1, tex-cache: 0 , single-alloc: 0
[2013-07-18 10:39:06] GPU #3: Ùÿ║☻ with compute capability 58782612.257475133
[2013-07-18 10:39:06] GPU #3: interactive: 1, tex-cache: 0 , single-alloc: 0
[2013-07-18 10:39:06] GPU #2: Performing auto-tuning (Patience...)
[2013-07-18 10:39:06] GPU #2: 0.00 khash/s with configuration 0x0
[2013-07-18 10:39:06] GPU #2: using launch configuration 0x0
[2013-07-18 10:39:06] GPU #1: Performing auto-tuning (Patience...)
[2013-07-18 10:39:06] GPU #1: 0.00 khash/s with configuration 0x0
[2013-07-18 10:39:06] GPU #1: using launch configuration 0x0
[2013-07-18 10:39:06] GPU #5: Performing auto-tuning (Patience...)
[2013-07-18 10:39:06] GPU #5: 0.00 khash/s with configuration 0x0
[2013-07-18 10:39:06] GPU #5: using launch configuration 0x0
[2013-07-18 10:39:06] GPU #7: Performing auto-tuning (Patience...)
[2013-07-18 10:39:06] GPU #7: 0.00 khash/s with configuration 0x0
[2013-07-18 10:39:06] GPU #7: using launch configuration 0x0
[2013-07-18 10:39:06] GPU #4: Performing auto-tuning (Patience...)
[2013-07-18 10:39:06] GPU #4: 0.00 khash/s with configuration 0x0
[2013-07-18 10:39:06] GPU #4: using launch configuration 0x0
[2013-07-18 10:39:06] GPU #3: Performing auto-tuning (Patience...)
[2013-07-18 10:39:06] GPU #3: 0.00 khash/s with configuration 0x0
[2013-07-18 10:39:06] GPU #3: using launch configuration 0x0
[2013-07-18 10:39:06] GPU #6: Performing auto-tuning (Patience...)
[2013-07-18 10:39:06] GPU #6: 0.00 khash/s with configuration 0x0
[2013-07-18 10:39:06] GPU #6: using launch configuration 0x0
I'll report my GeForce 560Ti experience later (with different overclocking settings) |
|
|
|
|
Saturn is listed as drawing max 500W. Do you think a 600W Corsair that I have lying around would be enough or should I go for a bigger PSU?
|
|
|
|
|
Bicknellski, I saw your note on the hub thread. Are these K1's going to require USB 3.0 hubs? I already ordered 3 D-Link USB 2.0 hubs, but I can still cancel my order and buy something else, so a prompt reply would be appreciated.
|
|
|
|
|
I am with Bitstamp, if only because of SEPA.
And the sideways pressure-cooking trend continues:
Last price:$90.39
Daily change: -$1.16 (-1.27%)
Day's range:$89.20 - $92.37
Today's open:$91.61
24h volume9218 BTC
|
|
|
|
A shame these hubs come with a 3.0A PSU. They work fine with the Raspi though, and that's quite something. Can somebody recommend a nice 3.5A or 4.0A PSU?
I keep tabs in the hubs here: https://bitcointalk.org/index.php?topic=253749.0Not sure if any of the ones listed there would work with Raspberry, though. |
|
|
|
Thank you. EDIT: Build problems. Building on cygwin: $ ./autogen.sh
configure.ac:116: error: possibly undefined macro: AC_MSG_ERROR
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
This one runs ok:
$ ./autogen.sh m4_pattern_allow
$ ./configure
gives:
......
checking for json_loads in -ljansson... no
checking for pthread_create in -lpthread... yes
./configure: line 6032: syntax error near unexpected token `,'
./configure: line 6032: `LIBCURL_CHECK_CONFIG(, 7.15.2, ,'
Before that I've successfully run ./configure && make && make install on curl-7.29.0
Now, deleted all files an started afresh without running autogen.sh.
./configure finished fine, but the new hiccup is in make:
EDIT: Seems I didn't have nVidia GPU Computing Tooltik installed. It should have been linked to from OP
https://developer.nvidia.com/cuda-downloads?sid=311699
Still compile problems, though:
nvcc -g -O2 -arch=compute_10 --maxrregcount=124 --ptxas-options=-v -I./compat/jansson -o salsa_kernel.o -c salsa_kernel.cu
nvcc : fatal error : Cannot find compiler 'cl.exe' in PATH
Makefile:922: recipe for target `salsa_kernel.o' failed
make[2]: *** [salsa_kernel.o] Error 127
make[2]: Leaving directory `/d/CudaMiner-master'
[/s] EDIT: this is getting tedious. I've added path to cl.exe Luckily I still had Visual Studio 2008 installed as cl.exe from VS2012 was not accepted. Now to the next hurdle: nvcc -g -O2 -arch=compute_10 --maxrregcount=124 --ptxas-options=-v -I./compat/jansson -o salsa_kernel.o -c salsa_kernel.cu
salsa_kernel.cu
salsa_kernel.cu(16) : fatal error C1083: Cannot open include file: 'sys/time.h': No such file or directory
Makefile:922: recipe for target `salsa_kernel.o' failed
make[2]: *** [salsa_kernel.o] Error 2
make[2]: Leaving directory `/d/CudaMiner-master'
Makefile:472: recipe for target `all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/d/CudaMiner-master'
Makefile:276: recipe for target `all' failed
make: *** [all] Error 2
Still asking: Any alternative venues for building this on Windows? Maybe there are precompiled binaries, the way pooler distributes his cpuminer for Windows? Also, could you provide Windows compile instructions in either OP or in README.txt?! |
|
|
|
|
Added your find to the table, right after Anker. I used Amazon price with a footnote, pointing to your review. By the way, Amazon states that the hub has 5A adapter.
|
|
|
|
|
How are they going to be cooled? Will you have a small VGA memory-style heatsink attached?
|
|
|
|
Nice setup. Which hub is that? D-Link DUB-H7? |
|
|
|
|
Show Posts
