Show Posts
|
|
Pages: [1] 2 3 4 5 »
|
|
These miners will go all the way 11T, out of the box at 800mhz (freq hard cap) No power or cooling upgrade required.
|
|
|
|
|
Phil has assisted countless miners with troubleshooting and various challenges over the years, including our team members and many customers. Excited to support him in his mission!
|
|
|
|
 - This post focuses on commercially available USB and Desktop style Bitcoin mining hardware.
- USB and smaller desktop sized miners are not novel. They were commercially available as early as 2011.
- A summary of speed & performance from 2011 to present.
- Exploration on what has driven the revival of owning and operating a USB or desktop device.
The Desktop Miner Renaissance – A brief history of desktop & USB miners
|
|
|
|
Saw this in person in Nashville last week and have to say that is just plain amazing! Solid metal and wood finish gives it a premium look. This is something many of us could use around the house. Happy to see mine4heat applications are evolving past space heating & water heating. Here's a video featuring the product.
|
|
|
|
I tried that procedure, but it may be obsolete now. Kept getting errors for various missing libraries. I guess we have to wait for kano to release the executables.
|
|
|
|
Just the stick and IglooPac Cooler in a Fancy box  Would highly recommend purchasing a smarthub along with Gekkoscience products. It can run 9 miners and makes everything plug and play.
|
|
|
|
|
Thanks for releasing the new linux cgminer Kano! We received our first batch of Compac A1s yesterday so looking forward to test. Will you also be releasing the windows version soon?
|
|
|
|
|
I'll second skot. Nano 3 does looks good on paper. On a purely $/Th perspective its very attractive. Yet it not easy to buy at the advertised price. The price you can buy one today is much higher. Also at only 140W max, its not much of a space heater.
Really weird that a publicly listed company with access to capital markets will crowdfund a product. Something doesn't add up.
We're still selling lots of Bitaxes, Urlachers and a new metal BitChimney coming this fall.
|
|
|
|
|
T21 stock firmware errors out on APW12, so you would need aftermarket firmware to run after swapping PSU from APW11 to APW12. For the fully assembled 'T21 transformer' we just ship with vnish on stock AMLOGIC control board. We have tested this build with both ePIC UMC and MARA UCB and it works with both, but they do add some additional cost to the build.
Both these CB options are nice since they have zero dev fees , so will likely pay themselves off over time. But if you're looking to save on upfront cost, you can just flash luxos or vnish on the stock AML CB and it works fine.
Now if your T21 came with a CV1835 control board, that changes the math, since there is very few firmware option available. In this case, your best bet is to just remove the stock CB and replace with epic or MARA.
|
|
|
|
|
Just shipped you a couple of complimentary T21 Transformer PSU covers. The bars aren't a shock risk but still pose short circuit risk.
|
|
|
|
|
Happy to see folks trying to get T21 to work on single phase. We've done this on a couple of test rigs and can't really tell a performance/efficiency difference between T21 and S21. Yet the T21 is considerably cheaper, and comes with a Bigger PSU. One issue I've encountered is that after you change the PSU and power bars, there doesn't seem to be an easy way to cover the power bars etc, since T21 does not come with a PSU cover piece.
|
|
|
|
|
Really excited about this product. It makes it much easier to setup and expand, standalone USB mining setups.
|
|
|
|
|
So, I'd like to post an update on this S19j Pro+ situation. We were initially skeptical of the soldered heatsinks that are very similar to those on Antminer S17 series. Call it a case of once bitten twice shy.
We've run many of these S19j Pro+ units in the mine through this summer, including some with substantial overclocking of upto 135T. The soldered heatsinks seems to be doing a much better job of heat dissipation and S19j Pro+ miners consistently ran about 5-10 deg C cooler than other S19 series miner in the mine. No, hashboard issues this summer either. While this is with just a few months of testing, I'd say its safe to assume that whatever issues Bitmain had with soldered heatsinks on S17 have now been fixed with S19j Pro+.
Someone mentioned it was improper chip tinning which caused issues with S17 series and not the soldering itself, so it's possible that Bitmain has improved its chip tinning process.
|
|
|
|
I saw the same issue when trying to run 8 Compac f with two R909s. This wasn't because of CPU overload, since CPU usage was only at 30% (12th gen core i5 with windows 10 PC). This computer can run 50+ compac f and upto 9 R909 without a problem. The devices run fine individually but the problem only occurs when running them together in the same cgminer window. I tried running two seperate cgminer instances on the same computer, one each for R909 and compac f and that seems to fix the unstable hashrate issues. I used --gekko-r909-detect & --gekko-compacf-detect to enable only one type of device in each cgminer window. I'm not sure why this works, but I'd suggest trying this out.
|
|
|
|
Just to close the loop on this issue with abnormal hashrate in LPM on JPro+, bitmain released an updated firmware a few days ago that fixes this issue. 
|
|
|
|
Well, in your green circle the 01 means one chip and the + means it's using ASIC Boost.
Most of this is explained in this thread and/or in Kano's support page.
Thanks for answering the green circle. I've looked through both kano's readme files and various gekkoscience threads but couldn't figure out what the other 3 that I've marked are. Would be great if someone can point me in the right direction. I'm compiling this information to make a neat infographic that explains everything on the gekko cgminer terminal for future users.
|
|
|
|
Can someone help me understand what the highlighted parts on this cgminer terminal mean? I read through the cgminer readme file, but I think these are device specific fields, so not listed there. 
|
|
|
|
|