 Show Posts
|
|
Pages: [1] 2 3 4 5 »
|
KnC Titan users: We suggest you to use #xnsub AND #skipcbcheck parameters to get stable mining on NiceHash or WestHash, example: stratum+tcp://stratum.nicehash.com/#xnsub#skipcbcheck With those settings you'll be able to get a stable 350 Mh/s average speed with fw 1.95 overclocking at 325MHs. Proof:  btw: average NiceHash/WestHash Scrypt profitability is aprox. 25% more then direct Litecoin mining. How do you enter the port number? stratum+tcp://stratum.nicehash.com/#xnsub#skipcbcheck:3333 does not work. |
|
|
|
|
I was wondering about the high Granitecoin profitability. The pool seems to be pulling a 50 satoshi valuation out of somewhere - maybe bittrex, where Granitecoin was apparently delisted. Granitecoin is listen on Bleutrade, where the highest bid is 4 satoshis.
EDIT: Conspiracycoin seems to have a similar situation.
|
|
|
|
|
I tried Coinking for a few days, and I have some feedback.
FTC is listed as a scrypt coin, even though it switched to neoscrypt ages ago.
LTC profitability calculation seems erroneus giving about half of true value. As a result LTC is hardly mined at all, while other scrypt multipools mostly mine LTC.
SHA256 coins less profitable than Bitcoin seem to be mined too. Bitcoin hashing power should be forwarded to some larger no fee pool like other multipools do.
Automatic exhange seems not to work on some some coins.
|
|
|
|
|
Guess what the mailman brought today? Four titan Y-cables from KnC.
|
|
|
|
Has Knc Cloud shut down? "KncMiner" stopped finding blocks. What the hell is going on?
Maybe something to do with the class action lawsuit? Did they run with the money to some Central American or Caribbean state to avoid responsibility for the Titan(ic) disaster?  |
|
|
|
This update solved a lot of problems!  |
|
|
|
It seems as if this problem is widespread. Do you think KnC has manufactured numerous cubes and shipped 3 winners and 1 loser to each of their customers?
I have only one cube out of four capable of occasionally reaching 75 MH/s. Mine was shipped the first day of shipping I believe. Maybe they knowingly shipped defective cubes to meet September deadline, and started shipping good cubes later, putting only one bad cube in each shipment hoping that people wouldn't complain. |
|
|
|
I just realized that KnC originally promised 250/MH/s. Mathematically this is equal to 250 s/MH. 250 seconds to produce one Megahash is equal to 4 kH/s. Not sure if the Raspberry Pi alone can reach this hashing speed  |
|
|
|
What is their rationale claiming that a connector rated for max 13 amps is enough to draw over 200 watts at 12 volts? I know my Ohm's law, and I can multiply 12 volts times 13 amps, which comes out to 156 watts. One cube draws over 20 amps I think. The heat generated is proportional to the square of the current. 20^2 / 13^2 = 2.37, which means 137% more heat than the connector is rated for.  |
|
|
|
Is there a Swedish authority that can force recall of a dangerous product? |
|
|
|
|
What a titanic mess. The original micro SD card that came with the miner got corrupted beyond being able to be written any more. Let's see how long the spare I had lasts. So far it got corrupted only once, but was able to be rewritten.
|
|
|
|
|
Did any Kncminer products ever have the CE conformity marking? Titan doesn't, right?
|
|
|
|
Problems:
a) quota feature broken
b) low hash rate
c) unreliability
d) 5-7 second flushes of old work
e) doesn't work well on coin switching pools
f) doesn't work well on faster block time/low network hashrate coins
g) lots of bfgminer errors
h) reports of I2C and SPI bus issues
i) reports of dead dies
j) reports of DC/DC problems
k) reports of good cubes degrading over time
l) apparent slow progress of firmware development/fixes
m) reports of higher than advertised power consumption
n) reluctance of KNC to accept problems
o) slow production/delivery rate
p) concerns for safety due to alleged fire hazard
q) report of ee design problem -> no resistive termination of control cable bus
r) report of ee design problem -> one PCI-e connector
s) report of ee design problem -> rPI
t) difficulty of access to web admin interface due to performance issues of rPI
u) reports of yield problem with Asics
v) list of problems is getting bigger every day
x) SD card corruption. |
|
|
|
|
Is the multipool stuck on megacoin. The pool seems to think that the difficulty is 112, when it is actually over 300, and no litecoin payouts are given for found blocks.
|
|
|
|
|
Raspberry pi performance should not be the issue, since Bitfury made miners with hundreds of gigahashes using raspberry controller. Software can be causing low performance though.
|
|
|
|
|
[2014-09-28 05:53:22] KnC spi xfer: ioctl error on SPI device: Message too long
Segmentation fault
Occasionally getting this right before miner stops.
|
|
|
|
Which pool you used?
The evil one... Getting over 12 GH/s of rejects on ghash ltc+doge pool... How many Titans are you mining with ? Just one. Then you must mean MHs not GHs. Nope. It is producing gigahashes of rejects.  |
|
|
|
|
Where can we obtain those PCI-e 2-to-1 Y power cables? Preferrably in Europe. Looks like 1 to 2 are more common. Or sell me yours for bitcoins.
|
|
|
|
Which pool you used?
The evil one... Getting over 12 GH/s of rejects on ghash ltc+doge pool... How many Titans are you mining with ? Just one. |
|
|
|
Which pool you used?
The evil one... Getting over 12 GH/s of rejects on ghash ltc+doge pool... |
|
|
|
|
