Field Programmable Gate Array (FPGA) – BitcoinWiki

Bitcoin mentioned around Reddit: [Serious] what kind of mining hardware should one invest in with about 1k of available funds for a passive income stream?? should one use usb(s), ASIC(s), FPGA(a), or GPU(S) in this age of the game wi /r/AskReddit

Bitcoin mentioned around Reddit: [Serious] what kind of mining hardware should one invest in with about 1k of available funds for a passive income stream?? should one use usb(s), ASIC(s), FPGA(a), or GPU(S) in this age of the game wi /AskReddit submitted by BitcoinAllBot to BitcoinAll [link] [comments]

I earned about 4000% more btc with my android tablet than with a $250 ASIC mini rig setup using GekkoScience Newpac USB miners!

Requirements:
1.) Android Device with access to Google Play Store. *I haven't tried yet but you may be able to use tis on Android TV devces as well by sideloading. If anyone has success before I try, let me know! -Note, I did this with a Samsung Galaxy Tab S6 so its a newer more powerful device. If your android is older, your profts will most likely be less than what I earned but to give a projected range I also tested on my Raspberry Pi 4 running a custom LineageOS rom that doesn't allow the OS to make full use of the Pi's specs and I still got 500 h/s on that with Cloud boost, so about 60% of what my Tab 6 with MUCH Higher Specs does.
**Hey guys. Before I get started i just wanted to be clear about one thing. Yes I have seen those scammy posts sharing "miracle" boosts and fixes. I have a hard time believing stuff online anymore. But this is honestly real. Ill attach photos and explain the whole story and process below. Thanks for taking the time to read and feel free to share any thoughts, concerns, tips, etc*
So last week I finally got started with my first mini rig type mining build. I started getting into crypto about a year ago and it has taken me a long time to even grasp half of the projects out there but its been fun thus far! Anyways my rig was 2 GekkoScience Newpac USB miners, a Moonlander USB miner to pair with an FPGA i already had mining, a 10 port 60W 3.0 USB hub and 2 usb fans. The Newpacs actually are hashing at a combined 280 g/s which is actually better than their reported max hash rate when overclocked. Pleasant surpise and they are simple!! I just wanted to get a moonlander because my fpga already mines on Odocrypt for DGB and I just wanted to experience Scrypt mining and help build the DGB project. The Newpacs are mining BTC though.
After I got everything up and running i checked my payout daily average after 1 week. I averaged .01 a day TOTAL between all three miners with them all perforing ABOVE SPEC!!! I had done research so i knew I wouldnt earn much. More than anything i just wanted to learn. But still. I was kinda surprised in a negative way. Yesterday I actually earned less than .01 Frustrated I went back to scouring the web for new ideas. About a year ago, when II was starting, I saw an app on my iphone called CryptoBrowser that claimed to mine btc on your phone without actually using phone resources using a method of cloud mining. I tried it for a week and quit because I earned like .03 after a ton of use and seemed scammy. Plus my iphone actually would get very hot when doing this so I quit using it as it seemed like a possible scam with all the cryptonight browser mining hacks and malware out there.
Anyways I was on my Galaxy Tab S6 and saw that CryptoBrowser released a "PRO" edition for 3.99 on Google Play. I bought it for Sh*ts and giggles and booted it up. It came with what they called "Cloud Boost" Essentially this is a button you press and it multiplys the estimated hashrate that it gives you device by the number shown on the boost button. (With the purchase of PRO you get one free x10 boost. You can purchase additional boosts to use with other android devices but those are actually pretty pricy. Another x10 boost was like $25 if i remember correctly).
I played with it for about an hour to see if it actually worked like it said it would this time. To my surprise, as i was browsing, my device didnt increase in temperature AT ALL!!!!! I checked my tast manager to confirm and it was indeed true, my memory and usage barely went up. it was giving me an estimated range of 80-105 on the hashrate. Once i pushed the x10 boost button, that went to 800-1150 h/s. I switched my screen to not go to sleep, plugged it to the charge and let it run on the browser page, hashing. When you push the boost button, it runs for 3 hours at the boosted speeds. After that it goes back to normal but if you press the button again, it boosts everything again. There is no limit to how many times you use it. After checking what I earned after 24 hours, I HAD MADE .40 in BTC!!!!! I JUST EARNED OVER 4000% MORE THAN MY $280 MINING RIG EARNED ME!!!! I was blown away. Maybe this was a fluke? I did it again next day. Every 3 hours or so I would push the button again but thats all. Sure enough, .35 that day. Also, it realy BTC. I requested a payout and although it took like 12 hours for them to send me an email stating they had just sent it, I actually did recieve the state amount of BTC within 24 hours in my personal wallet. The fees to send are SUPER LOW!. Like .01
Below I will list the steps I took, along with an explanation of thier "Mining" process on Androids. Reminder, this ONLY WORKS ON ANDROIDS. Also DO NOT use cryptobrowser on a physcal laptop or desktop. I ran it on an old laptop for three days last year and it fried it. It does actually use your hardware on those platforms to mine and it is not efficnet at all as I suspect they prob steal over half of your power for themselves using the REAL RandomX protocol via browser mining which is EXTREMELY INEFFICIENT DONT TRY IT!!
-----How To Do This Yourself:
Cryptotab Browser states the program works on Android devices by estimating what it thinks the hashrate would be for your device specs and siimulates what you would mine in a remote server however you still earn that estimated coin amount. It is not a SHA-256 process or coin that they say is mining, rather it is XMR and they swap that and pay it out to you in BTC Bitcoin. However I know damn well my Tab S6 doesnt hash 80-105 h/s on RandomX because I have done it with a moodified XMRig module i ported to Android. I got 5 h/s a sec if I was getting any hashes at all. But thats besides the point as I still was making money.
Now, when you press that cloud boost button it immediately boosts that hash rate it estimates by the number on the cloud boost. As stated above, you can purchase more boosts and gift them or use them on extra android devices that you may have. Again, they are pricey so I'm not doing that plus it would just mean that I have another device that I have to leave on and open. The boosts come in x2, x4, x6, x8 and x10 variants. Again, they have unlimited uses.
Here is the link to grab yourself CryptoBrowser Pro from CryptoTab. This IS A REFERRAL LINK! This is where I benefit from doing tis tutorial. Like i said, I want to be transparent as this is not a scam but I'm also not doing this out of the love of my heart. Their referral system works in that people that use the donwload the app using your link are your stage 1 referrals. Anytime they are mining, you earn a 15% bonus. So say they mine $.30 one day. You would get paid out an additional $.045 in your own balance (it does not come out of the referred user balance fyi so no worries). Then lets say that referred miner also gets their own referrals. I would get a 10% bonus on whatever THOSE people mine. This goes on and on for like 8 tiers. Each tier the bonus percntage essential halves. So again, I stand to benefit from this but it also is stupid to not make this visible as its WAY CHEAPER, EASIER AND MORE PROFITABLE TO GET BTC USING THIS METHOD THAN IT IS USING ASICS!! THIS EARNS ALMOST AS MUCH BTC AS AN ANTMINER S7 DOES RUNNING 24/7 ONLY WITHOUT THE HUGE ELLECTRICTY BILL AND COSTS!!!!)
Thats it. Again, if you have concerns, let me know or if you have suggestions, other tips, etc... mention those as well!!!
https://cryptotabbrowser.com/8557319
Links to Picture Proof http://imgur.com/gallery/P13bEsB
submitted by Afraid_Balance to earnbitcoin [link] [comments]

استخراج بیت کوین با FPGA چگونه انجام می شود

استخراج بیت کوین با FPGA چگونه انجام می شود؟ در حال حاضر، تجهیزات ماینینگ که به آنها ماینرهای ارز دیجیتال گفته می شود براساس پردازنده ‌های FPGA کار می کنند. این پردازشگرها می‌توانند از طریق درگاه USB به رایانه های شخصی متصل گردند. استخراج بیت کوین با FPGA، از روش های کارآ برای ماینینگ ارز دیجیتال BTC می باشد که با کاربرد نرم افزار بر روی این پردازشگرهای خاص انجام می گردد.....ادامه این مطلب در لینک پیوست شده در وب سایت بیت پارس.
submitted by bitpars to u/bitpars [link] [comments]

Continued censorship involving Ethereum's proposed fork to progPOW.

Our friends at Ethereum are subject to continued manipulation into forking their coin to progPOW. I decided to post this in /btc because it is the last bastion of free speech in the crypto community.
Today, after drawing attention to the sketchy history of progPOW's original proponent, my post was subjected to massive vote manipulation, and eventually deleted.
I have long suspected that progPOW favors NVIDIA miners, given the deep connections that progPOW's development team has to NVIDIA. Today, the progPOW team freely admitted that AMD miners will suffer a larger hashrate decrease compared to NVIDIA miners, so I created a poll:
Ethereum developers want to fork to ETH to progPOW [1], a proof-of-work algorithm that gives AMD GPUs a stronger hashrate penalty compared to NVIDIA [2][3]. Should Ethereum use ProgPOW for Proof-of-Work? Cast your vote with Ethereum [4].
Sources:
Below is my post that was deleted, in its entirety.
If you are curious about the CSW/Coingeek connection, scroll down.
Previous Posts
Criticism and Soft Power
I have received criticism for my posts mostly due to what people call "character attacks." I have two things to say about that:
  1. I have never engaged in any character attacks. In all cases, the character has made their modus operandi known by themselves, and I have simply shined a light on it. I don't need call people "mentally unstable gentlemen" [--source, Ohgodagirl Twitter] to get my point across.
  2. Algorithm change discussions must include economic and political introspection as well as a discussion of the proposed change's technical details. As I have stated before, progPOW would not exist without the people responsible for creating it. We must look at these people's history, character, prior accomplishments, and industry connections. The discussion must exist outside the scope of the proposed change, not inside of it.
Example: When people criticize my posts for "not looking at the technical details", they are making a mistake. If someone asked "which should we kill more often: baby seals or baby kittens?", we don't all immediately start discussing the optimal relation of kittens-per-second to seals-per-second that can be killed. No, our first reaction is "what the fuck, why should we kill anything?"
Onward
Customer complaints from people who bought cloud contracts from Kristy's previous company:
Coingeek Connection
Previously, I had promised to provide information regarding the CSW/Coingeek and Core Scientific connection.
When I was president of ImageShack.com (2003-2011), someone wanted to buy our company. When this happens, the buyer and seller usually write a purchase agreement similar to the business in which they are involved. This is done to ensure that the purchase is executed. In ImageShack's case, the buyer bought $500,000 worth of advertising from us. The logic was that ImageShack would be acquired, so they actually would pay themselves. If they didn't buy ImageShack, they would owe us $500,000.
Given the partnership between Core Scientific (Kristy's employer) and "Squire Mining" (effectively, Coingeek), I would not be surprised if Coingeek and Core Scientific made such an agreement, as well. In their case, it would likely be a hosting agreement. Since Coingeek has many ASICs, and Core Scientific is a large mining facility, I would not be surprised if those Coingeek ASICs are hosted by Core Scientific.
Individuals close to these parties can verify those claims, but I cannot share the proof at this time without revealing the identity of my sources.
Chatlog Dumps
Today, I also provide public comments from chatlog dumps showcasing Kristy Leigh Anne Minehan's deep connection to NVIDIA:
01/28/2018 - 22:34<@OhGodAGirl> Yo. ystarnaud/sling00: **I'll be meeting NV next week**. I think it's next week. The 4th! Anyway; if you have NVIDIA fixes you need for EthOS or something you want special attention on, PM me. 02/05/2018 - 06:47<@OhGodAGirl> Also I got a USB shaped like a NVIDIA GTX. It's the best thing ever. 02/05/2018 - 06:50<@OhGodAGirl> https://usercontent.irccloud-cdn.com/file/ffwT8M2j/IMG_2726.JPG 02/05/2018 - 06:50<@OhGodAGirl> Look at this adorable little shit. 
"Ah, but there's a catch. These USB drives are extremely rare—Nvidia only cranked out a couple thousand of these drives and will be giving them away to press and "influencers" at E3, along with 1,080 registered GeForce Experience members who are opted in to receive communications from Nvidia."
04/22/2018 - 20:17<@sling00> OhGodAGirl: what does ohgodanethlargement do 04/22/2018 - 20:17< cYnIxX3> https://youtu.be/2mj1nCfFvlI?t=2m16s 04/22/2018 - 20:19< cYnIxX3> sling00, about 10-25mh improvement to 1080 gpus. 04/22/2018 - 20:19< __virus__> about 40-50% improvement afaik 04/22/2018 - 20:21< OhGodAGirl> But...it's not under because NVIDIA asked me not to. 04/21/2018 - 16:51< OhGodAGirl> I have a ton of private tools for Mineority 04/21/2018 - 16:51< OhGodAGirl> Right now our Equihash kernel has a 25% advantage over Claymore. 04/21/2018 - 16:52< PL3> 25% on amds? 04/21/2018 - 16:52< OhGodAGirl> NVIDIA ;) 04/21/2018 - 16:52< PL3> you have claymore nvidia equi miner? 04/21/2018 - 16:52< OhGodAGirl> We're a NV only company. For now. 04/29/2018 - 00:53< OhGodAGirl> So uh, NVIDIA showed ETHlargement at an executive meeting 04/29/2018 - 00:53< OhGodAGirl> They thought it was hillarious 04/29/2018 - 00:53< acv_> that is awesome. 04/29/2018 - 01:22< OhGodAGirl> So many dicks on Youtube though 04/29/2018 - 01:22< OhGodAGirl> "RA RA IT'S A SCAM" 04/29/2018 - 01:22< OhGodAGirl> "RA RA IT WILL STEAL ALL YOUR PRIVKEYS" 04/29/2018 - 01:22< OhGodAGirl> "RA RA NO ONE IS EVER NICE IN THIS WORLD' 04/29/2018 - 01:22< OhGodAGirl> Well dammit I'm a nice person. =( 
submitted by ugtarmas to btc [link] [comments]

Best $100-$300 FPGA development board in 2018?

Hello, I’ve been trying to decide on a FPGA development board, and have only been able to find posts and Reddit threads from 4-5 years ago. So I wanted to start a new thread and ask about the best “mid-range” FGPA development board in 2018. (Price range $100-$300.)
I started with this Quora answer about FPGA boards, from 2013. The Altera DE1 sounded good. Then I looked through the Terasic DE boards.
Then I found this Reddit thread from 2014, asking about the DE1-SoC vs the Cyclone V GX Starter Kit: https://www.reddit.com/FPGA/comments/1xsk6w/cyclone_v_gx_starter_kit_vs_de1soc_board/‬ (I was also leaning towards the DE1-SoC.)
Anyway, I thought I better ask here, because there are probably some new things to be aware of in 2018.
I’m completely new to FPGAs and VHDL, but I have experience with electronics/microcontrollers/programming. My goal is to start with some basic soft-core processors. I want to get some C / Rust programs compiling and running on my own CPU designs. I also want to play around with different instruction sets, and maybe start experimenting with asynchronous circuits (e.g. clock-less CPUs)
Also I don’t know if this is possible, but I’d like to experiment with ternary computing, or work with analog signals instead of purely digital logic. EDIT: I just realized that you would call those FPAAs, i.e. “analog” instead of “gate”. Would be cool if there was a dev board that also had an FPAA, but no problem if not.
EDIT 2: I also realized why "analog signals on an FPGA" doesn't make any sense, because of how LUTs work. They emulate boolean logic with a lookup table, and the table can only store 0s and 1s. So there's no way to emulate a transistor in an intermediate state. I'll just have play around with some transistors on a breadboard.
UPDATE: I've put together a table with some of the best options:
Board Maker Chip LUTs Price SoC? Features
icoBoard Lattice iCE40-HX8K 7,680 $100 Sort of A very simple FPGA development board that plugs into a Raspberry Pi, so you have a "backup" hard-core CPU that can control networking, etc. Supports a huge range of pmod accessories. You can write a program/circuit so that the Raspberry Pi CPU and the FPGA work together, similar to a SoC. Proprietary bitstream is fully reverse engineered and supported by Project IceStorm, and there is an open-source toolchain that can compile your hardware design to bitstream. Has everything you need to start experimenting with FPGAs.
iCE40-HX8K Breakout Board Lattice iCE40-HX8K-CT256 7,680 $49 No 8 LEDs, 8 switches. Very similar to icoBoard, but no Raspberry Pi or pmod accessories.
iCE40 UltraPlus Lattice iCE40 UltraPlus FPGA 5280 $99 No Chip specs. 4 switchable FPGAs, and a rechargeable battery. Bluetooth module, LCD Display (240 x 240 RGB), RGB LED, microphones, audio output, compass, pressure, gyro, accelerometer.
Go Board Lattice ICE40 HX1K FPGA 1280 $65 No 4 LEDs, 4 buttons, Dual 7-Segment LED Display, VGA, 25 MHz on-board clock, 1 Mb Flash.
snickerdoodle Xilinx Zynq 7010 28K $95 Yes Xilinx Zynq 7-Series SoC - ARM Cortex-A9 processor, and Artix-7 FPGA. 125 IO pins. 1GB DDR2 RAM. Texas Instruments WiLink 8 wireless module for 802.11n Wi-Fi and Bluetooth 4.1. No LEDs or buttons, but easy to wire up your own on a breadboard. If you want to use a baseboard, you'll need a snickerdoodle black ($195) with the pins in the "down" orientation. (E.g. The "breakyBreaky breakout board" ($49) or piSmasher SBC ($195)). The snickerdoodle one only comes with pins in the "up" orientation and doesn't support any baseboards. But you can still plug the jumpers into the pins and wire up things on a breadboard.
numato Mimas A7 Xilinx Artix 7 52K $149 No 2Gb DDR3 RAM. Gigabit Ethernet. HDMI IN/OUT. 100MHz LVDS oscillator. 80 IOs. 7-segment display, LEDs, buttons. (Found in this Reddit thread.)
Ultra96 Xilinx Zynq UltraScale+ ZU3EG 154K $249 Yes Has one of the latest Xilinx SoCs. 2 GB (512M x32) LPDDR4 Memory. Wi-Fi / Bluetooth. Mini DisplayPort. 1x USB 3.0 type Micro-B, 2x USB 3.0 Type A. Audio I/O. Four user-controllable LEDs. No buttons and limited LEDs, but easy to wire up your own on a breadboard
Nexys A7-100T Xilinx Artix 7 15,850 $265 No . 128MiB DDR2 RAM. Ethernet port, PWM audio output, accelerometer, PDM microphone, microphone, etc. 16 switches, 16 LEDs. 7 segment displays. USB HID Host for mice, keyboards and memory sticks.
Zybo Z7-10 Xilinx Zynq 7010 17,600 $199 Yes Xilinx Zynq 7000 SoC (ARM Cortex-A9, 7-series FPGA.) 1 GB DDR3 RAM. A few switches, push buttons, and LEDs. USB and Ethernet. Audio in/out ports. HDMI source + sink with CEC. 8 Total Processor I/O, 40 Total FPGA I/O. Also a faster version for $299 (Zybo Z7-20).
Arty A7 Xilinx Artix 7 15K $119 No 256MB DDR3L. 10/100 Mbps Ethernet. A few switches, buttons, LEDs.
DE10-Standard (specs) Altera Cyclone V 110K $350 Yes Dual-core Cortex-A9 processor. Lots of buttons, LEDs, and other peripherals.
DE10-Nano Altera Cyclone V 110K $130 Yes Same as DE10-Standard, but not as many peripherals, buttons, LEDs, etc.

Winner:

icoBoard ($100). (Buy it here.)
The icoBoard plugs into a Raspberry Pi, so it's similar to having a SoC. The iCE40-HX8K chip comes with 7,680 LUTs (logic elements.) This means that after you learn the basics and create some simple circuits, you'll also have enough logic elements to run the VexRiscv soft-core CPU (the lightweight Murax SoC.)
The icoBoard also supports a huge range of pluggable pmod accessories:
You can pick whatever peripherals you're interested in, and buy some more in the future.
Every FPGA vendor keeps their bitstream format secret. (Here's a Hacker News discussion about it.) The iCE40-HX8K bitstream has been fully reverse engineered by Project IceStorm, and there is an open-source set of tools that can compile Verilog to iCE40 bitstream.
This means that you have the freedom to do some crazy experiments, like:
You don't really have the same freedom to explore these things with Xilinx or Altera FPGAs. (Especially asynchronous circuits.)

Links:

Second Place:

iCE40-HX8K Breakout Board ($49)

Third Place:

numato Mimas A7 ($149).
An excellent development board with a Xilinx Artix 7 FPGA, so you can play with a bigger / faster FPGA and run a full RISC-V soft-core with all the options enabled, and a much higher clock speed. (The iCE40 FPGAs are a bit slow and small.)
Note: I've changed my mind several times as I learned new things. Here's some of my previous thoughts.

What did I buy?

I ordered a iCE40-HX8K Breakout Board to try out the IceStorm open source tooling. (I would have ordered an icoBoard if I had found it earlier.) I also bought a numato Mimas A7 so that I could experiment with the Artix 7 FPGA and Xilinx software (Vivado Design Suite.)

Questions

What can I do with an FPGA? / How many LUTs do I need?

submitted by ndbroadbent to FPGA [link] [comments]

The original proponent of progPOW, Kristy Leigh Anne Minehan, appears to have scammed people with cloud contracts, criticism, and soft power, and chatlog dumps.

Previous Posts
Criticism and Soft Power
I have received criticism for my posts mostly due to what people call "character attacks." I have two things to say about that:
  1. I have never engaged in any character attacks. In all cases, the character has made their modus operandi known by themselves, and I have simply shined a light on it. I don't need call people "mentally unstable gentlemen" [--source, Ohgodagirl Twitter] to get my point across.
  2. Algorithm change discussions must include economic and political introspection as well as a discussion of the proposed change's technical details. As I have stated before, progPOW would not exist without the people responsible for creating it. We must look at these people's history, character, prior accomplishments, and industry connections. The discussion must exist outside the scope of the proposed change, not inside of it.
Example: When people criticize my posts for "not looking at the technical details", they are making a mistake. If someone asked "which should we kill more often: baby seals or baby kittens?", we don't all immediately start discussing the optimal relation of kittens-per-second to seals-per-second that can be killed. No, our first reaction is "what the fuck, why should we kill anything?"
Onward
Customer complaints from people who bought cloud contracts from Kristy's previous company:
Coingeek Connection
Previously, I had promised to provide information regarding the CSW/Coingeek and Core Scientific connection.
When I was president of ImageShack.com (2003-2011), someone wanted to buy our company. When this happens, the buyer and seller usually write a purchase agreement similar to the business in which they are involved. This is done to ensure that the purchase is executed. In ImageShack's case, the buyer bought $500,000 worth of advertising from us. The logic was that ImageShack would be acquired, so they actually would pay themselves. If they didn't buy ImageShack, they would owe us $500,000.
Given the partnership between Core Scientific (Kristy's employer) and "Squire Mining" (effectively, Coingeek), I would not be surprised if Coingeek and Core Scientific made such an agreement, as well. In their case, it would likely be a hosting agreement. Since Coingeek has many ASICs, and Core Scientific is a large mining facility, I would not be surprised if those Coingeek ASICs are hosted by Core Scientific.
Individuals close to these parties can verify those claims, but I cannot share the proof at this time without revealing the identity of my sources.
Chatlog Dumps
Today, I also provide public comments from chatlog dumps showcasing Kristy Leigh Anne Minehan's deep connection to NVIDIA:
01/28/2018 - 22:34<@OhGodAGirl> Yo. ystarnaud/sling00: **I'll be meeting NV next week**. I think it's next week. The 4th! Anyway; if you have NVIDIA fixes you need for EthOS or something you want special attention on, PM me. 02/05/2018 - 06:47<@OhGodAGirl> Also I got a USB shaped like a NVIDIA GTX. It's the best thing ever. 02/05/2018 - 06:50<@OhGodAGirl> https://usercontent.irccloud-cdn.com/file/ffwT8M2j/IMG_2726.JPG 02/05/2018 - 06:50<@OhGodAGirl> Look at this adorable little shit. 
"Ah, but there's a catch. These USB drives are extremely rare—Nvidia only cranked out a couple thousand of these drives and will be giving them away to press and "influencers" at E3, along with 1,080 registered GeForce Experience members who are opted in to receive communications from Nvidia."
04/22/2018 - 20:17<@sling00> OhGodAGirl: what does ohgodanethlargement do 04/22/2018 - 20:17< cYnIxX3> https://youtu.be/2mj1nCfFvlI?t=2m16s 04/22/2018 - 20:19< cYnIxX3> sling00, about 10-25mh improvement to 1080 gpus. 04/22/2018 - 20:19< __virus__> about 40-50% improvement afaik 04/22/2018 - 20:21< OhGodAGirl> But...it's not under because NVIDIA asked me not to. 04/21/2018 - 16:51< OhGodAGirl> I have a ton of private tools for Mineority 04/21/2018 - 16:51< OhGodAGirl> Right now our Equihash kernel has a 25% advantage over Claymore. 04/21/2018 - 16:52< PL3> 25% on amds? 04/21/2018 - 16:52< OhGodAGirl> NVIDIA ;) 04/21/2018 - 16:52< PL3> you have claymore nvidia equi miner? 04/21/2018 - 16:52< OhGodAGirl> We're a NV only company. For now. 04/29/2018 - 00:53< OhGodAGirl> So uh, NVIDIA showed ETHlargement at an executive meeting 04/29/2018 - 00:53< OhGodAGirl> They thought it was hillarious 04/29/2018 - 00:53< acv_> that is awesome. 04/29/2018 - 01:22< OhGodAGirl> So many dicks on Youtube though 04/29/2018 - 01:22< OhGodAGirl> "RA RA IT'S A SCAM" 04/29/2018 - 01:22< OhGodAGirl> "RA RA IT WILL STEAL ALL YOUR PRIVKEYS" 04/29/2018 - 01:22< OhGodAGirl> "RA RA NO ONE IS EVER NICE IN THIS WORLD' 04/29/2018 - 01:22< OhGodAGirl> Well dammit I'm a nice person. =( 
submitted by ugtarmas to ethereum [link] [comments]

Why is getting into FPGA's such a crappy experience?

I'm a hobbyist and this is my first venture into FPGA's. I understand how FPGA works in theory. It's just a bunch of combinational logic connected by clock-connected flip-flops, whose topology and combinational functions can be programmed with a high level language. I bought a Xilinx board from embeddedmicro.com and I'm going to work through their tutorials.
All I want to be able to do is specify a bunch of like registers and crap, and how to connect them with clocked flip-flops to do some really basic stuff like a simple CPU with 1-2 custom instructions or something. So why do I have to download a GIANT SIX GIGABYTE FILE TO DO THAT? What could this software possibly be doing that it needs to be that big?
In a sane world, all I'd need is a board and a simple compiler which just takes the high-level language and turns it into the topology file to upload to the board. But in the insanity in which I am currently living, I have to download some gigantic IDE that is going to be huge and probably slower than mining bitcoins on an NES. I don't know because IT'S STILL DOWNLOADING.
So to even get to the download, I had to log into the website, register, and give them a name and a physical address (and God forbid I should leave the "Company" field empty!). The Licensing crap on their website looks like you need an MBA to understand it. This company sells pieces of hardware, FFS! Why in Stallman's name can't they just make the software FOSS and let anyone download it instead of all this BS about WEBPACK this and annual upgrade that?
Xilinx, in case you haven't noticed, in order for anyone to actually use your software, THEY HAVE TO BUY A CHIP OR BOARD AND YOU CAN MAKE MONEY OFF YOUR CUSTOMERS THAT WAY. CHARGING FOR SOFTWARE OR HAVING A BYZANTINE PROCESS FOR GETTING A FREE LICENSE MAKES ZERO SENSE FOR A HARDWARE COMPANY.
Anyone know a place where you can just buy an FPGA board, plug it into a USB port, sudo apt-get install some FOSS compiler, type your Verilog or VHDL or whatever into emacs, run 2-5 commands and have a running design?
If such a place doesn't exist, some startup needs to disrupt this industry. If you make it easy for people to develop for your HW, those devs will be inclined buy your product just to make their lives easier.
submitted by white_nerdy to FPGA [link] [comments]

Bitcoin miner beginer wanting some help

I am certain these questions have all been asked before and answered somewhere on the internet. However after 4 hours of trawling through this subreddit and searching on Google I am still left with unanswered questions. I am looking to invest ~$300 in to a mining system and would love some advice.
I know some of these questions are very vague but I am interested in setting up a system which can ultimately begin turning a substantial profit. Help offered in the form of useful articles/links is greatly appreciated.
EDIT: More questions
submitted by Sgtstudmufin to BitcoinMining [link] [comments]

Butterfly Labs's Bitcoin miners - Worth it?

Hey there, quite new to the mining scene, working with x2 570GTX (1gb cache) which hash at around 110 Mhash/s and 120 Mhash/s
Recently I've come across this piece of hardware
https://products.butterflylabs.com/homepage/5-gh-s-bitcoin-miner.html
Has anyone else seen this, can anyone tell me a little bit more about it. Such as, is it legit? They've been taking orders but wont be shipping till the end of April when the product is finished. Will it really perform 5GH/s or is that an 'up to' estimate?
Any information will be appreciated
Also Discuss
submitted by Xooch to BitcoinMining [link] [comments]

The Concept of Bitcoin

The Concept of Bitcoin
https://preview.redd.it/5r9soz2ltq421.jpg?width=268&format=pjpg&auto=webp&s=6a89685f735b53ec1573eefe08c8646970de8124
What is Bitcoin?
Bitcoin is an experimental system of transfer and verification of property based on a network of peer to peer without any central authority.
The initial application and the main innovation of the Bitcoin network is a system of digital currency decentralized unit of account is bitcoin.
Bitcoin works with software and a protocol that allows participants to issue bitcoins and manage transactions in a collective and automatic way. As a free Protocol (open source), it also allows interoperability of software and services that use it. As a currency bitcoin is both a medium of payment and a store of value.
Bitcoin is designed to self-regulate. The limited inflation of the Bitcoin system is distributed homogeneously by computing the network power, and will be limited to 21 million divisible units up to the eighth decimal place. The functioning of the Exchange is secured by a general organization that everyone can examine, because everything is public: the basic protocols, cryptographic algorithms, programs making them operational, the data of accounts and discussions of the developers.
The possession of bitcoins is materialized by a sequence of numbers and letters that make up a virtual key allowing the expenditure of bitcoins associated with him on the registry. A person may hold several key compiled in a 'Bitcoin Wallet ', 'Keychain' web, software or hardware which allows access to the network in order to make transactions. Key to check the balance in bitcoins and public keys to receive payments. It contains also (often encrypted way) the private key associated with the public key. These private keys must remain secret, because their owner can spend bitcoins associated with them on the register. All support (keyrings) agrees to maintain the sequence of symbols constituting your keychain: paper, USB, memory stick, etc. With appropriate software, you can manage your assets on your computer or your phone.
Bitcoin on an account, to either a holder of bitcoins in has given you, for example in Exchange for property, either go through an Exchange platform that converts conventional currencies in bitcoins, is earned by participating in the operations of collective control of the currency.
The sources of Bitcoin codes have been released under an open source license MIT which allows to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the software, subject to insert a copyright notice into all copies.
Bitcoin creator, Satoshi Nakamoto
What is the Mining of bitcoin?
Technical details :
During mining, your computer performs cryptographic hashes (two successive SHA256) on what is called a header block. For each new hash, mining software uses a different random number that called Nuncio. According to the content of the block and the nonce value typically used to express the current target. This number is called the difficulty of mining. The difficulty of mining is calculated by comparing how much it is difficult to generate a block compared to the first created block. This means that a difficulty of 70000 is 70000 times more effort that it took to Satoshi Nakamoto to generate the first block. Where mining was much slower and poorly optimized.
The difficulty changes each 2016 blocks. The network tries to assign the difficulty in such a way that global computing power takes exactly 14 days to generate 2016 blocks. That's why the difficulty increases along with the power of the network.
Material :
In the beginning, mining with a processor (CPU) was the only way to undermine bitcoins. (GPU) graphics cards have possibly replaced the CPU due to their nature, which allowed an increase between 50 x to 100 x in computing power by using less electricity by megahash compared to a CPU.
Although any modern GPU can be used to make the mining, the brand AMD GPU architecture has proved to be far superior to nVidia to undermine bitcoins and the ATI Radeon HD 5870 card was the most economical for a time.
For a more complete list of graphics cards and their performance, see Wiki Bitcoin: comparison of mining equipment
In the same way that transition CPU to GPU, the world of mining has evolved into the use of the Field Programmable Gate Arrays (FPGA) as a mining platform. Although FPGAs did not offer an increase of 50 x to 100 x speed of calculation as the transition from CPU to GPU, they offered a better energy efficiency.
A typical HD/s 600 graphics card consumes about 400w of power, while a typical FPGA device can offer a rate of hash of 826 MH/s to 80w of power consumption, a gain of 5 x more calculations for the same energy power. Since energy efficiency is a key factor in the profitability of mining, it was an important step for the GPU to FPGA migration for many people.
The world of the mining of bitcoin is now migrating to the Application Specific Integrated Circuit (ASIC). An ASIC is a chip designed specifically to accomplish a single task. Unlike FPGAs, an ASIC is unable to be reprogrammed for other tasks. An ASIC designed to undermine bitcoins cannot and will not do anything else than to undermine bitcoins.
The stiffness of an ASIC allows us to offer an increase of 100 x computing power while reducing power consumption compared to all other technologies. For example, a classic device to offer 60 GH/s (1 hashes equals 1000 Megahash. 1GH/s = 1000 Mh/s) while consuming 60w of electricity. Compared to the GPU, it is an increase in computing power of 100 x and a reduction of power consumption by a factor of 7.
Unlike the generations of technologies that have preceded the ASIC, ASIC is the "end of the line" when we talk about important technology change. The CPUs have been replaced by the GPUs, themselves replaced by FPGAs that were replaced by ASICs.
There is nothing that can replace the ASICs now or in the immediate future. There will be technological refinements in ASIC products, and improvements in energy efficiency, but nothing that may match increased from 50 x to 100 x the computing power or a 7 x reduction in power consumption compared with the previous technology.
Which means that the energy efficiency of an ASIC device is the only important factor of all product ASIC, since the estimated lifetime of an ASIC device is superior to the entire history of the mining of bitcoin. It is conceivable that a purchased ASIC device today is still in operation in two years if the unit still offers a profitable enough economic to keep power consumption. The profitability of mining is also determined by the value of bitcoin but in all cases, more a device has a good energy efficiency, it is profitable.
Software :
There are two ways to make mining: by yourself or as part of a team (a pool). If you are mining for yourself, you must install the Bitcoin software and configure it to JSON-RPC (see: run Bitcoin). The other option is to join a pool. There are multiple available pools. With a pool, the profit generated by any block generated by a member of the team is split between all members of the team. The advantage of joining a team is to increase the frequency and stability of earnings (this is called reduce the variance) but gains will be lower. In the end, you will earn the same amount with the two approaches. Undermine solo allows you to receive earnings huge but very infrequent, while miner with a pool can offer you small stable and steady gains.
Once you have your software configured or that you have joined a pool, the next step is to configure the mining software. The software the most populare for ASIC/FPGA/GPU currently is CGminer or a derivative designed specifically for FPGAS and ASICs, BFGMiner.
If you want a quick overview of mining without install any software, try Bitcoin Plus, a Bitcoin minor running in your browser with your CPU. It is not profitable to make serious mining, but it is a good demonstration of the principle of the mining team.
submitted by Josephbitcoin to u/Josephbitcoin [link] [comments]

Antminer S9 no longer hashing?

Good morning folks,
I have an Antminer S9 that has performed flawlessly. After I moved it to a better location, I noticed that it no longer seems to be working. The green light is flashing, but it doesn't seem to be hashing to my pool (Nicehash).
I'm fairly new to Bitcoining mining and can't make sense of some of the information on my status screen. Before I jump into Bitmain support, I was wondering if anyone could clue me in as to what the problem might be.
https://s15.postimg.cc/i0n5qsyoInked_Capture_LI.jpg
I'll post my Kernal Log here.
Thank you in advance!!!
KERNAL LOG: [ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.14.0-xilinx-ge8a2f71-dirty ([email protected]) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #82 SMP PREEMPT Tue May 16 19:49:53 CST 2017
[ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Xilinx Zynq
[ 0.000000] cma: CMA: reserved 128 MiB at 27800000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] On node 0 totalpages: 258048
[ 0.000000] free_area_init_node: node 0, pgdat c0740a40, node_mem_map e6fd8000
[ 0.000000] Normal zone: 1520 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 194560 pages, LIFO batch:31
[ 0.000000] HighMem zone: 496 pages used for memmap
[ 0.000000] HighMem zone: 63488 pages, LIFO batch:15
[ 0.000000] PERCPU: Embedded 8 pages/cpu @e6fc0000 s9088 r8192 d15488 u32768
[ 0.000000] pcpu-alloc: s9088 r8192 d15488 u32768 alloc=8*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 256528
[ 0.000000] Kernel command line: noinitrd mem=1008M console=ttyPS0,115200 root=ubi0:rootfs ubi.mtd=1 rootfstype=ubifs rw rootwait
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 884148K/1032192K available (5032K kernel code, 283K rwdata, 1916K rodata, 204K init, 258K bss, 148044K reserved, 253952K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0xf0000000 - 0xff000000 ( 240 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xef800000 ( 760 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc06d1374 (6949 kB)
[ 0.000000] .init : 0xc06d2000 - 0xc0705380 ( 205 kB)
[ 0.000000] .data : 0xc0706000 - 0xc074cf78 ( 284 kB)
[ 0.000000] .bss : 0xc074cf84 - 0xc078d9fc ( 259 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Dump stacks of tasks blocking RCU-preempt GP.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] ps7-slcr mapped to f0004000
[ 0.000000] zynq_clock_init: clkc starts at f0004100
[ 0.000000] Zynq clock init
[ 0.000015] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[ 0.000308] ps7-ttc #0 at f0006000, irq=43
[ 0.000618] Console: colour dummy device 80x30
[ 0.000658] Calibrating delay loop... 1325.46 BogoMIPS (lpj=6627328)
[ 0.040207] pid_max: default: 32768 minimum: 301
[ 0.040436] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.040459] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.042612] CPU: Testing write buffer coherency: ok
[ 0.042974] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.043036] Setting up static identity map for 0x4c4b00 - 0x4c4b58
[ 0.043263] L310 cache controller enabled
[ 0.043282] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB
[ 0.121037] CPU1: Booted secondary processor
[ 0.210227] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.210357] Brought up 2 CPUs
[ 0.210376] SMP: Total of 2 processors activated.
[ 0.210385] CPU: All CPU(s) started in SVC mode.
[ 0.211051] devtmpfs: initialized
[ 0.213481] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 0.214724] regulator-dummy: no parameters
[ 0.223736] NET: Registered protocol family 16
[ 0.226067] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.228361] cpuidle: using governor ladder
[ 0.228374] cpuidle: using governor menu
[ 0.235908] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered
[ 0.237440] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[ 0.237453] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.237572] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xf0080000
[ 0.259435] bio: create slab at 0
[ 0.261172] vgaarb: loaded
[ 0.261915] SCSI subsystem initialized
[ 0.262814] usbcore: registered new interface driver usbfs
[ 0.262985] usbcore: registered new interface driver hub
[ 0.263217] usbcore: registered new device driver usb
[ 0.263743] media: Linux media interface: v0.10
[ 0.263902] Linux video capture interface: v2.00
[ 0.264150] pps_core: LinuxPPS API ver. 1 registered
[ 0.264162] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[[email protected]](mailto:[email protected])>
[ 0.264286] PTP clock support registered
[ 0.264656] EDAC MC: Ver: 3.0.0
[ 0.265719] Advanced Linux Sound Architecture Driver Initialized.
[ 0.268708] DMA-API: preallocated 4096 debug entries
[ 0.268724] DMA-API: debugging enabled by kernel config
[ 0.268820] Switched to clocksource arm_global_timer
[ 0.289596] NET: Registered protocol family 2
[ 0.290280] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.290375] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.290535] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.290612] TCP: reno registered
[ 0.290633] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 0.290689] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 0.290971] NET: Registered protocol family 1
[ 0.291346] RPC: Registered named UNIX socket transport module.
[ 0.291359] RPC: Registered udp transport module.
[ 0.291368] RPC: Registered tcp transport module.
[ 0.291376] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.291391] PCI: CLS 0 bytes, default 64
[ 0.291857] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[ 0.293945] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 0.295408] bounce pool size: 64 pages
[ 0.296323] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.296525] msgmni has been set to 1486
[ 0.297330] io scheduler noop registered
[ 0.297343] io scheduler deadline registered
[ 0.297385] io scheduler cfq registered (default)
[ 0.308358] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
[ 0.308380] dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.434378] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
[ 1.006815] console [ttyPS0] enabled
[ 1.011106] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to f0068000
[ 1.018731] [drm] Initialized drm 1.1.0 20060810
[ 1.036029] brd: module loaded
[ 1.045494] loop: module loaded
[ 1.055163] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[ 1.060985] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[ 1.068779] libphy: XEMACPS mii bus: probed
[ 1.073341] ------------- phy_id = 0x3625e62
[ 1.078112] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
[ 1.087072] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.093912] ehci-pci: EHCI PCI platform driver
[ 1.101155] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing?
[ 1.107952] usbcore: registered new interface driver usb-storage
[ 1.114850] mousedev: PS/2 mouse device common for all mice
[ 1.120975] i2c /dev entries driver
[ 1.127946] zynq-edac f8006000.ps7-ddrc: ecc not enabled
[ 1.133474] cpufreq_cpu0: failed to get cpu0 regulator: -19
[ 1.139426] Xilinx Zynq CpuIdle Driver started
[ 1.144261] sdhci: Secure Digital Host Controller Interface driver
[ 1.150384] sdhci: Copyright(c) Pierre Ossman
[ 1.154700] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.161601] mmc0: no vqmmc regulator found
[ 1.165614] mmc0: no vmmc regulator found
[ 1.208845] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[ 1.217539] usbcore: registered new interface driver usbhid
[ 1.223054] usbhid: USB HID core driver
[ 1.227806] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[ 1.234107] nand: Micron MT29F2G08ABAEAWP
[ 1.238074] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[ 1.244027] Bad block table found at page 131008, version 0x01
[ 1.250251] Bad block table found at page 130944, version 0x01
[ 1.256303] 3 ofpart partitions found on MTD device pl353-nand
[ 1.262080] Creating 3 MTD partitions on "pl353-nand":
[ 1.267174] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel"
[ 1.275230] 0x000002000000-0x00000b000000 : "angstram-rootfs"
[ 1.282582] 0x00000b000000-0x000010000000 : "upgrade-rootfs"
[ 1.291630] TCP: cubic registered
[ 1.294869] NET: Registered protocol family 17
[ 1.299597] Registering SWP/SWPB emulation handler
[ 1.305497] regulator-dummy: disabling
[ 1.309875] UBI: attaching mtd1 to ubi0
[ 1.836565] UBI: scanning is finished
[ 1.848221] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0
[ 1.855302] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 1.862063] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 1.868728] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[ 1.875605] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0
[ 1.881586] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[ 1.888693] UBI: max/mean erase counter: 4/1, WL threshold: 4096, image sequence number: 1134783803
[ 1.897736] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40
[ 1.906953] UBI: background thread "ubi_bgt0d" started, PID 1080
[ 1.906959] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 1.911038] ALSA device list:
[ 1.911042] No soundcards found.
[ 1.927420] UBIFS: background thread "ubifs_bgt0_0" started, PID 1082
[ 1.956473] UBIFS: recovery needed
[ 2.016970] UBIFS: recovery completed
[ 2.020709] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[ 2.026635] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 2.035771] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[ 2.045653] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 2.050693] UBIFS: media format: w4/r0 (latest is w4/r0), UUID B079DD56-06BB-4E31-8F5E-A6604F480DB2, small LPT model
[ 2.061987] VFS: Mounted root (ubifs filesystem) on device 0:11.
[ 2.069184] devtmpfs: mounted
[ 2.072297] Freeing unused kernel memory: 204K (c06d2000 - c0705000)
[ 2.920928] random: dd urandom read with 0 bits of entropy available
[ 3.318860]
[ 3.318860] bcm54xx_config_init
[ 3.928853]
[ 3.928853] bcm54xx_config_init
[ 7.929682] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[ 7.935787] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
[ 22.563181] In axi fpga driver!
[ 22.566260] request_mem_region OK!
[ 22.569676] AXI fpga dev virtual address is 0xf01fe000
[ 22.574751] *base_vir_addr = 0x8c510
[ 22.590723] In fpga mem driver!
[ 22.593791] request_mem_region OK!
[ 22.597361] fpga mem virtual address is 0xf3000000
[ 23.408156]
[ 23.408156] bcm54xx_config_init
[ 24.038071]
[ 24.038071] bcm54xx_config_init
[ 28.038487] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[ 28.044593] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
This is XILINX board. Totalram: 1039794176
Detect 1GB control board of XILINX
DETECT HW version=0008c510
miner ID : 8118b4c610358854
Miner Type = S9
AsicType = 1387
real AsicNum = 63
use critical mode to search freq...
get PLUG ON=0x000000e0
Find hashboard on Chain[5]
Find hashboard on Chain[6]
Find hashboard on Chain[7]
set_reset_allhashboard = 0x0000ffff
Check chain[5] PIC fw version=0x03
Check chain[6] PIC fw version=0x03
Check chain[7] PIC fw version=0x03
chain[5]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
has freq in PIC, will disable freq setting.
chain[5] has freq in PIC and will jump over...
Chain[5] has core num in PIC
Chain[5] ASIC[15] has core num=5
Check chain[5] PIC fw version=0x03
chain[6]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
has freq in PIC, will disable freq setting.
chain[6] has freq in PIC and will jump over...
Chain[6] has core num in PIC
Chain[6] ASIC[17] has core num=8
Check chain[6] PIC fw version=0x03
chain[7]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
has freq in PIC, will disable freq setting.
chain[7] has freq in PIC and will jump over...
Chain[7] has core num in PIC
Chain[7] ASIC[8] has core num=13
Chain[7] ASIC[9] has core num=11
Chain[7] ASIC[13] has core num=11
Chain[7] ASIC[19] has core num=14
Chain[7] ASIC[30] has core num=6
Chain[7] ASIC[32] has core num=1
Chain[7] ASIC[42] has core num=2
Chain[7] ASIC[55] has core num=1
Chain[7] ASIC[57] has core num=2
Check chain[7] PIC fw version=0x03
get PIC voltage=108 on chain[5], value=880
get PIC voltage=74 on chain[6], value=900
get PIC voltage=108 on chain[7], value=880
set_reset_allhashboard = 0x00000000
chain[5] temp offset record: 62,0,0,0,0,0,35,28
chain[5] temp chip I2C addr=0x98
chain[5] has no middle temp, use special fix mode.
chain[6] temp offset record: 62,0,0,0,0,0,35,28
chain[6] temp chip I2C addr=0x98
chain[6] has no middle temp, use special fix mode.
chain[7] temp offset record: 62,0,0,0,0,0,35,28
chain[7] temp chip I2C addr=0x98
chain[7] has no middle temp, use special fix mode.
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
CRC error counter=0
set command mode to VIL
--- check asic number
After Get ASIC NUM CRC error counter=0
set_baud=0
The min freq=700
set real timeout 52, need sleep=379392
After TEST CRC error counter=0
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
search freq for 1 times, completed chain = 3, total chain num = 3
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
restart Miner chance num=2
waiting for receive_func to exit!
waiting for pic heart to exit!
bmminer not found= 1643 root 0:00 grep bmminer
bmminer not found, restart bmminer ...
This is user mode for mining
Detect 1GB control board of XILINX
Miner Type = S9
Miner compile time: Fri Nov 17 17:57:49 CST 2017 type: Antminer S9set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
set_reset_allhashboard = 0x0000ffff
miner ID : 8118b4c610358854
set_reset_allhashboard = 0x0000ffff
Checking fans!get fan[2] speed=6120
get fan[2] speed=6120
get fan[2] speed=6120
get fan[2] speed=6120
get fan[2] speed=6120
get fan[2] speed=6120
get fan[5] speed=13440
get fan[2] speed=6120
get fan[5] speed=13440
get fan[2] speed=6120
get fan[5] speed=13440
chain[5]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
Chain[J6] has backup chain_voltage=880
Chain[J6] test patten OK temp=-126
Check chain[5] PIC fw version=0x03
chain[6]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
Chain[J7] has backup chain_voltage=900
Chain[J7] test patten OK temp=-120
Check chain[6] PIC fw version=0x03
chain[7]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
Chain[J8] has backup chain_voltage=880
Chain[J8] test patten OK temp=-125
Check chain[7] PIC fw version=0x03
Chain[J6] orignal chain_voltage_pic=108 value=880
Chain[J7] orignal chain_voltage_pic=74 value=900
Chain[J8] orignal chain_voltage_pic=108 value=880
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
Chain[J6] has 63 asic
Chain[J7] has 63 asic
Chain[J8] has 63 asic
Chain[J6] has core num in PIC
Chain[J6] ASIC[15] has core num=5
Chain[J7] has core num in PIC
Chain[J7] ASIC[17] has core num=8
Chain[J8] has core num in PIC
Chain[J8] ASIC[8] has core num=13
Chain[J8] ASIC[9] has core num=11
Chain[J8] ASIC[13] has core num=11
Chain[J8] ASIC[19] has core num=14
Chain[J8] ASIC[30] has core num=6
Chain[J8] ASIC[32] has core num=1
Chain[J8] ASIC[42] has core num=2
Chain[J8] ASIC[55] has core num=1
Chain[J8] ASIC[57] has core num=2
miner total rate=13999GH/s fixed rate=13500GH/s
read PIC voltage=940 on chain[5]
Chain:5 chipnum=63
Chain[J6] voltage added=0.2V
Chain:5 temp offset=0
Chain:5 base freq=487
Asic[ 0]:618
Asic[ 1]:631 Asic[ 2]:681 Asic[ 3]:618 Asic[ 4]:631 Asic[ 5]:681 Asic[ 6]:618 Asic[ 7]:631 Asic[ 8]:675
Asic[ 9]:618 Asic[10]:631 Asic[11]:681 Asic[12]:631 Asic[13]:637 Asic[14]:606 Asic[15]:487 Asic[16]:637
Asic[17]:675 Asic[18]:618 Asic[19]:637 Asic[20]:675 Asic[21]:631 Asic[22]:650 Asic[23]:687 Asic[24]:631
Asic[25]:537 Asic[26]:687 Asic[27]:631 Asic[28]:587 Asic[29]:687 Asic[30]:612 Asic[31]:650 Asic[32]:687
Asic[33]:631 Asic[34]:650 Asic[35]:687 Asic[36]:631 Asic[37]:662 Asic[38]:693 Asic[39]:631 Asic[40]:662
Asic[41]:662 Asic[42]:543 Asic[43]:668 Asic[44]:693 Asic[45]:568 Asic[46]:675 Asic[47]:700 Asic[48]:631
Asic[49]:568 Asic[50]:700 Asic[51]:631 Asic[52]:625 Asic[53]:700 Asic[54]:631 Asic[55]:675 Asic[56]:662
Asic[57]:631 Asic[58]:662 Asic[59]:687 Asic[60]:631 Asic[61]:681 Asic[62]:700
Chain:5 max freq=700
Chain:5 min freq=487
read PIC voltage=940 on chain[6]
Chain:6 chipnum=63
Chain[J7] voltage added=0.1V
Chain:6 temp offset=0
Chain:6 base freq=687
Asic[ 0]:650
Asic[ 1]:650 Asic[ 2]:650 Asic[ 3]:650 Asic[ 4]:650 Asic[ 5]:650 Asic[ 6]:650 Asic[ 7]:650 Asic[ 8]:650
Asic[ 9]:650 Asic[10]:650 Asic[11]:650 Asic[12]:650 Asic[13]:650 Asic[14]:650 Asic[15]:650 Asic[16]:650
Asic[17]:650 Asic[18]:650 Asic[19]:650 Asic[20]:650 Asic[21]:650 Asic[22]:650 Asic[23]:650 Asic[24]:650
Asic[25]:650 Asic[26]:656 Asic[27]:656 Asic[28]:656 Asic[29]:656 Asic[30]:656 Asic[31]:656 Asic[32]:656
Asic[33]:656 Asic[34]:656 Asic[35]:656 Asic[36]:656 Asic[37]:656 Asic[38]:656 Asic[39]:656 Asic[40]:656
Asic[41]:656 Asic[42]:656 Asic[43]:656 Asic[44]:656 Asic[45]:656 Asic[46]:656 Asic[47]:656 Asic[48]:656
Asic[49]:656 Asic[50]:656 Asic[51]:656 Asic[52]:656 Asic[53]:656 Asic[54]:656 Asic[55]:656 Asic[56]:656
Asic[57]:656 Asic[58]:656 Asic[59]:656 Asic[60]:656 Asic[61]:656 Asic[62]:656
Chain:6 max freq=656
Chain:6 min freq=650
read PIC voltage=940 on chain[7]
Chain:7 chipnum=63
Chain[J8] voltage added=0.2V
Chain:7 temp offset=0
Chain:7 base freq=637
Asic[ 0]:656
Asic[ 1]:656 Asic[ 2]:656 Asic[ 3]:656 Asic[ 4]:656 Asic[ 5]:656 Asic[ 6]:656 Asic[ 7]:656 Asic[ 8]:637
Asic[ 9]:637 Asic[10]:656 Asic[11]:656 Asic[12]:656 Asic[13]:637 Asic[14]:656 Asic[15]:662 Asic[16]:662
Asic[17]:662 Asic[18]:662 Asic[19]:637 Asic[20]:662 Asic[21]:662 Asic[22]:662 Asic[23]:662 Asic[24]:662
Asic[25]:662 Asic[26]:662 Asic[27]:662 Asic[28]:662 Asic[29]:662 Asic[30]:637 Asic[31]:662 Asic[32]:662
Asic[33]:662 Asic[34]:662 Asic[35]:662 Asic[36]:662 Asic[37]:662 Asic[38]:662 Asic[39]:662 Asic[40]:662
Asic[41]:662 Asic[42]:650 Asic[43]:662 Asic[44]:662 Asic[45]:662 Asic[46]:662 Asic[47]:662 Asic[48]:662
Asic[49]:662 Asic[50]:662 Asic[51]:662 Asic[52]:662 Asic[53]:662 Asic[54]:662 Asic[55]:650 Asic[56]:662
Asic[57]:650 Asic[58]:662 Asic[59]:662 Asic[60]:662 Asic[61]:662 Asic[62]:662
Chain:7 max freq=662
Chain:7 min freq=637
Miner fix freq ...
read PIC voltage=940 on chain[5]
Chain:5 chipnum=63
Chain[J6] voltage added=0.2V
Chain:5 temp offset=0
Chain:5 base freq=487
Asic[ 0]:618
Asic[ 1]:631 Asic[ 2]:650 Asic[ 3]:618 Asic[ 4]:631 Asic[ 5]:656 Asic[ 6]:618 Asic[ 7]:631 Asic[ 8]:656
Asic[ 9]:618 Asic[10]:631 Asic[11]:656 Asic[12]:631 Asic[13]:637 Asic[14]:606 Asic[15]:487 Asic[16]:637
Asic[17]:656 Asic[18]:618 Asic[19]:637 Asic[20]:656 Asic[21]:631 Asic[22]:650 Asic[23]:656 Asic[24]:631
Asic[25]:537 Asic[26]:656 Asic[27]:631 Asic[28]:587 Asic[29]:656 Asic[30]:612 Asic[31]:650 Asic[32]:656
Asic[33]:631 Asic[34]:650 Asic[35]:656 Asic[36]:631 Asic[37]:656 Asic[38]:656 Asic[39]:631 Asic[40]:656
Asic[41]:656 Asic[42]:543 Asic[43]:656 Asic[44]:656 Asic[45]:568 Asic[46]:656 Asic[47]:656 Asic[48]:631
Asic[49]:568 Asic[50]:656 Asic[51]:631 Asic[52]:625 Asic[53]:656 Asic[54]:631 Asic[55]:656 Asic[56]:656
Asic[57]:631 Asic[58]:656 Asic[59]:656 Asic[60]:631 Asic[61]:656 Asic[62]:656
Chain:5 max freq=656
Chain:5 min freq=487
read PIC voltage=940 on chain[6]
Chain:6 chipnum=63
Chain[J7] voltage added=0.1V
Chain:6 temp offset=0
Chain:6 base freq=687
Asic[ 0]:631
Asic[ 1]:631 Asic[ 2]:631 Asic[ 3]:631 Asic[ 4]:631 Asic[ 5]:631 Asic[ 6]:631 Asic[ 7]:631 Asic[ 8]:631
Asic[ 9]:631 Asic[10]:631 Asic[11]:631 Asic[12]:631 Asic[13]:631 Asic[14]:631 Asic[15]:631 Asic[16]:631
Asic[17]:631 Asic[18]:631 Asic[19]:631 Asic[20]:631 Asic[21]:631 Asic[22]:631 Asic[23]:631 Asic[24]:631
Asic[25]:631 Asic[26]:631 Asic[27]:631 Asic[28]:631 Asic[29]:631 Asic[30]:631 Asic[31]:631 Asic[32]:631
Asic[33]:631 Asic[34]:631 Asic[35]:637 Asic[36]:637 Asic[37]:637 Asic[38]:637 Asic[39]:637 Asic[40]:637
Asic[41]:637 Asic[42]:637 Asic[43]:637 Asic[44]:637 Asic[45]:637 Asic[46]:637 Asic[47]:637 Asic[48]:637
Asic[49]:637 Asic[50]:637 Asic[51]:637 Asic[52]:637 Asic[53]:637 Asic[54]:637 Asic[55]:637 Asic[56]:637
Asic[57]:637 Asic[58]:637 Asic[59]:637 Asic[60]:637 Asic[61]:637 Asic[62]:637
Chain:6 max freq=637
Chain:6 min freq=631
read PIC voltage=940 on chain[7]
Chain:7 chipnum=63
Chain[J8] voltage added=0.2V
Chain:7 temp offset=0
Chain:7 base freq=637
Asic[ 0]:637
Asic[ 1]:637 Asic[ 2]:637 Asic[ 3]:637 Asic[ 4]:637 Asic[ 5]:637 Asic[ 6]:637 Asic[ 7]:637 Asic[ 8]:637
Asic[ 9]:637 Asic[10]:637 Asic[11]:637 Asic[12]:637 Asic[13]:637 Asic[14]:637 Asic[15]:637 Asic[16]:637
Asic[17]:637 Asic[18]:637 Asic[19]:637 Asic[20]:637 Asic[21]:637 Asic[22]:637 Asic[23]:637 Asic[24]:637
Asic[25]:637 Asic[26]:637 Asic[27]:637 Asic[28]:637 Asic[29]:637 Asic[30]:637 Asic[31]:637 Asic[32]:637
Asic[33]:637 Asic[34]:637 Asic[35]:637 Asic[36]:637 Asic[37]:637 Asic[38]:637 Asic[39]:637 Asic[40]:637
Asic[41]:637 Asic[42]:637 Asic[43]:637 Asic[44]:637 Asic[45]:637 Asic[46]:637 Asic[47]:637 Asic[48]:637
Asic[49]:643 Asic[50]:643 Asic[51]:643 Asic[52]:643 Asic[53]:643 Asic[54]:643 Asic[55]:643 Asic[56]:643
Asic[57]:643 Asic[58]:643 Asic[59]:643 Asic[60]:643 Asic[61]:643 Asic[62]:643
Chain:7 max freq=643
Chain:7 min freq=637
max freq = 656
set baud=1
Chain[J6] PIC temp offset=62,0,0,0,0,0,35,28
chain[5] temp chip I2C addr=0x98
chain[5] has no middle temp, use special fix mode.
Chain[J6] chip[244] use PIC middle temp offset=0 typeID=55
New offset Chain[5] chip[244] local:26 remote:27 offset:29
Chain[J6] chip[244] get middle temp offset=29 typeID=55
Chain[J7] PIC temp offset=62,0,0,0,0,0,35,28
chain[6] temp chip I2C addr=0x98
chain[6] has no middle temp, use special fix mode.
Chain[J7] chip[244] use PIC middle temp offset=0 typeID=55
New offset Chain[6] chip[244] local:26 remote:27 offset:29
Chain[J7] chip[244] get middle temp offset=29 typeID=55
Chain[J8] PIC temp offset=62,0,0,0,0,0,35,28
chain[7] temp chip I2C addr=0x98
chain[7] has no middle temp, use special fix mode.
Chain[J8] chip[244] use PIC middle temp offset=0 typeID=55
New offset Chain[7] chip[244] local:26 remote:28 offset:28
Chain[J8] chip[244] get middle temp offset=28 typeID=55
miner rate=13501 voltage limit=900 on chain[5]
get PIC voltage=880 on chain[5], check: must be < 900
miner rate=13501 voltage limit=900 on chain[6]
get PIC voltage=900 on chain[6], check: must be < 900
miner rate=13501 voltage limit=900 on chain[7]
get PIC voltage=880 on chain[7], check: must be < 900
Chain[J6] set working voltage=880 [108]
Chain[J7] set working voltage=900 [74]
Chain[J8] set working voltage=880 [108]
do heat board 8xPatten for 1 times
start send works on chain[5]
start send works on chain[6]
start send works on chain[7]
get send work num :57456 on Chain[5]
get send work num :57456 on Chain[6]
get send work num :57456 on Chain[7]
wait recv nonce on chain[5]
wait recv nonce on chain[6]
wait recv nonce on chain[7]
get nonces on chain[5]
require nonce number:912
require validnonce number:57456
asic[00]=912 asic[01]=912 asic[02]=912 asic[03]=912 asic[04]=912 asic[05]=912 asic[06]=912 asic[07]=912
asic[08]=912 asic[09]=912 asic[10]=912 asic[11]=912 asic[12]=912 asic[13]=912 asic[14]=912 asic[15]=912
asic[16]=912 asic[17]=912 asic[18]=912 asic[19]=912 asic[20]=912 asic[21]=912 asic[22]=912 asic[23]=912
asic[24]=912 asic[25]=912 asic[26]=912 asic[27]=912 asic[28]=912 asic[29]=912 asic[30]=912 asic[31]=912
asic[32]=912 asic[33]=912 asic[34]=912 asic[35]=912 asic[36]=912 asic[37]=912 asic[38]=912 asic[39]=912
asic[40]=912 asic[41]=912 asic[42]=912 asic[43]=912 asic[44]=912 asic[45]=912 asic[46]=912 asic[47]=912
asic[48]=912 asic[49]=912 asic[50]=912 asic[51]=912 asic[52]=912 asic[53]=912 asic[54]=912 asic[55]=912
asic[56]=912 asic[57]=912 asic[58]=912 asic[59]=912 asic[60]=912 asic[61]=912 asic[62]=912
Below ASIC's core didn't receive all the nonce, they should receive 8 nonce each!
freq[00]=618 freq[01]=631 freq[02]=650 freq[03]=618 freq[04]=631 freq[05]=656 freq[06]=618 freq[07]=631
freq[08]=656 freq[09]=618 freq[10]=631 freq[11]=656 freq[12]=631 freq[13]=637 freq[14]=606 freq[15]=487
freq[16]=637 freq[17]=656 freq[18]=618 freq[19]=637 freq[20]=656 freq[21]=631 freq[22]=650 freq[23]=656
freq[24]=631 freq[25]=537 freq[26]=656 freq[27]=631 freq[28]=587 freq[29]=656 freq[30]=612 freq[31]=650
freq[32]=656 freq[33]=631 freq[34]=650 freq[35]=656 freq[36]=631 freq[37]=656 freq[38]=656 freq[39]=631
freq[40]=656 freq[41]=656 freq[42]=543 freq[43]=656 freq[44]=656 freq[45]=568 freq[46]=656 freq[47]=656
freq[48]=631 freq[49]=568 freq[50]=656 freq[51]=631 freq[52]=625 freq[53]=656 freq[54]=631 freq[55]=656
freq[56]=656 freq[57]=631 freq[58]=656 freq[59]=656 freq[60]=631 freq[61]=656 freq[62]=656
total valid nonce number:57456
total send work number:57456
require valid nonce number:57456
repeated_nonce_num:0
err_nonce_num:25912
last_nonce_num:14370
get nonces on chain[6]
require nonce number:912
require validnonce number:57456
asic[00]=912 asic[01]=912 asic[02]=912 asic[03]=912 asic[04]=912 asic[05]=912 asic[06]=912 asic[07]=912
asic[08]=912 asic[09]=912 asic[10]=912 asic[11]=912 asic[12]=912 asic[13]=912 asic[14]=912 asic[15]=912
asic[16]=912 asic[17]=912 asic[18]=912 asic[19]=912 asic[20]=912 asic[21]=912 asic[22]=912 asic[23]=912
asic[24]=912 asic[25]=912 asic[26]=912 asic[27]=912 asic[28]=912 asic[29]=912 asic[30]=912 asic[31]=912
asic[32]=912 asic[33]=912 asic[34]=912 asic[35]=912 asic[36]=912 asic[37]=912 asic[38]=912 asic[39]=912
asic[40]=912 asic[41]=912 asic[42]=912 asic[43]=912 asic[44]=912 asic[45]=912 asic[46]=912 asic[47]=912
asic[48]=912 asic[49]=912 asic[50]=912 asic[51]=912 asic[52]=912 asic[53]=912 asic[54]=912 asic[55]=912
asic[56]=912 asic[57]=912 asic[58]=912 asic[59]=912 asic[60]=912 asic[61]=912 asic[62]=912
Below ASIC's core didn't receive all the nonce, they should receive 8 nonce each!
freq[00]=631 freq[01]=631 freq[02]=631 freq[03]=631 freq[04]=631 freq[05]=631 freq[06]=631 freq[07]=631
freq[08]=631 freq[09]=631 freq[10]=631 freq[11]=631 freq[12]=631 freq[13]=631 freq[14]=631 freq[15]=631
freq[16]=631 freq[17]=631 freq[18]=631 freq[19]=631 freq[20]=631 freq[21]=631 freq[22]=631 freq[23]=631
freq[24]=631 freq[25]=631 freq[26]=631 freq[27]=631 freq[28]=631 freq[29]=631 freq[30]=631 freq[31]=631
freq[32]=631 freq[33]=631 freq[34]=631 freq[35]=637 freq[36]=637 freq[37]=637 freq[38]=637 freq[39]=637
freq[40]=637 freq[41]=637 freq[42]=637 freq[43]=637 freq[44]=637 freq[45]=637 freq[46]=637 freq[47]=637
freq[48]=637 freq[49]=637 freq[50]=637 freq[51]=637 freq[52]=637 freq[53]=637 freq[54]=637 freq[55]=637
freq[56]=637 freq[57]=637 freq[58]=637 freq[59]=637 freq[60]=637 freq[61]=637 freq[62]=637
total valid nonce number:57456
total send work number:57456
require valid nonce number:57456
repeated_nonce_num:0
err_nonce_num:25987
last_nonce_num:14368
get nonces on chain[7]
require nonce number:912
require validnonce number:57456
asic[00]=912 asic[01]=912 asic[02]=912 asic[03]=912 asic[04]=912 asic[05]=912 asic[06]=912 asic[07]=912
asic[08]=907 asic[09]=912 asic[10]=912 asic[11]=912 asic[12]=912 asic[13]=912 asic[14]=912 asic[15]=912
asic[16]=912 asic[17]=912 asic[18]=912 asic[19]=909 asic[20]=912 asic[21]=912 asic[22]=912 asic[23]=912
asic[24]=912 asic[25]=912 asic[26]=912 asic[27]=912 asic[28]=912 asic[29]=912 asic[30]=912 asic[31]=912
asic[32]=912 asic[33]=912 asic[34]=912 asic[35]=912 asic[36]=912 asic[37]=912 asic[38]=912 asic[39]=912
asic[40]=912 asic[41]=912 asic[42]=912 asic[43]=912 asic[44]=912 asic[45]=912 asic[46]=912 asic[47]=912
asic[48]=912 asic[49]=912 asic[50]=912 asic[51]=912 asic[52]=912 asic[53]=912 asic[54]=912 asic[55]=911
asic[56]=912 asic[57]=912 asic[58]=912 asic[59]=912 asic[60]=912 asic[61]=912 asic[62]=912
Below ASIC's core didn't receive all the nonce, they should receive 8 nonce each!
asic[08]=907
core[049]=7 core[053]=5 core[056]=7
asic[19]=909
core[064]=7 core[112]=6
asic[55]=911
core[007]=7
freq[00]=637 freq[01]=637 freq[02]=637 freq[03]=637 freq[04]=637 freq[05]=637 freq[06]=637 freq[07]=637
freq[08]=637 freq[09]=637 freq[10]=637 freq[11]=637 freq[12]=637 freq[13]=637 freq[14]=637 freq[15]=637
freq[16]=637 freq[17]=637 freq[18]=637 freq[19]=637 freq[20]=637 freq[21]=637 freq[22]=637 freq[23]=637
freq[24]=637 freq[25]=637 freq[26]=637 freq[27]=637 freq[28]=637 freq[29]=637 freq[30]=637 freq[31]=637
freq[32]=637 freq[33]=637 freq[34]=637 freq[35]=637 freq[36]=637 freq[37]=637 freq[38]=637 freq[39]=637
freq[40]=637 freq[41]=637 freq[42]=637 freq[43]=637 freq[44]=637 freq[45]=637 freq[46]=637 freq[47]=637
freq[48]=637 freq[49]=643 freq[50]=643 freq[51]=643 freq[52]=643 freq[53]=643 freq[54]=643 freq[55]=643
freq[56]=643 freq[57]=643 freq[58]=643 freq[59]=643 freq[60]=643 freq[61]=643 freq[62]=643
total valid nonce number:57447
total send work number:57456
require valid nonce number:57456
repeated_nonce_num:0
err_nonce_num:26183
last_nonce_num:35748
chain[5]: All chip cores are opened OK!
Test Patten on chain[5]: OK!
chain[6]: All chip cores are opened OK!
Test Patten on chain[6]: OK!
chain[7]: All chip cores are opened OK!
Test Patten on chain[7]: OK!
setStartTimePoint total_tv_start_sys=217 total_tv_end_sys=218
restartNum = 2 , auto-reinit enabled...
do read_temp_func once...
do check_asic_reg 0x08
get RT hashrate from Chain[5]: (asic index start from 1-63)
Asic[01]=72.5110 Asic[02]=68.6020 Asic[03]=74.4230 Asic[04]=74.6750 Asic[05]=71.4540 Asic[06]=77.5610 Asic[07]=74.7760 Asic[08]=74.3900
Asic[09]=77.7790 Asic[10]=76.7220 Asic[11]=73.8020 Asic[12]=68.5850 Asic[13]=76.1680 Asic[14]=72.4770 Asic[15]=73.0470 Asic[16]=57.8810
Asic[17]=74.4740 Asic[18]=76.4530 Asic[19]=67.8800 Asic[20]=70.1280 Asic[21]=73.7520 Asic[22]=74.6580 Asic[23]=73.6850 Asic[24]=78.5170
Asic[25]=73.6850 Asic[26]=63.6860 Asic[27]=80.9660 Asic[28]=73.9200 Asic[29]=68.9870 Asic[30]=75.6310 Asic[31]=74.9770 Asic[32]=69.4570
Asic[33]=74.6580 Asic[34]=79.8930 Asic[35]=76.6710 Asic[36]=74.3730 Asic[37]=66.6050 Asic[38]=76.7380 Asic[39]=71.4540 Asic[40]=69.3060
Asic[41]=72.5610 Asic[42]=73.8530 Asic[43]=58.9210 Asic[44]=75.3800 Asic[45]=73.1310 Asic[46]=68.4000 Asic[47]=77.6780 Asic[48]=73.1150
Asic[49]=69.2890 Asic[50]=62.8130 Asic[51]=74.2720 Asic[52]=73.1480 Asic[53]=67.4440 Asic[54]=72.4940 Asic[55]=68.1990 Asic[56]=72.4100
Asic[57]=75.3460 Asic[58]=66.1350 Asic[59]=72.9800 Asic[60]=78.1480 Asic[61]=72.3260 Asic[62]=72.5610 Asic[63]=77.7950
get RT hashrate from Chain[6]: (asic index start from 1-63)
Asic[01]=67.6620 Asic[02]=75.9840 Asic[03]=70.3300 Asic[04]=75.5640 Asic[05]=62.8470 Asic[06]=70.2790 Asic[07]=74.5240 Asic[08]=72.9130
Asic[09]=70.6320 Asic[10]=72.5610 Asic[11]=73.9370 Asic[12]=77.3420 Asic[13]=72.4440 Asic[14]=68.8030 Asic[15]=73.0810 Asic[16]=73.8360
Asic[17]=73.5510 Asic[18]=73.9700 Asic[19]=71.0340 Asic[20]=71.1680 Asic[21]=72.1580 Asic[22]=78.8190 Asic[23]=71.9230 Asic[24]=69.4570
Asic[25]=67.7630 Asic[26]=71.7220 Asic[27]=76.4030 Asic[28]=71.1180 Asic[29]=68.7360 Asic[30]=69.7090 Asic[31]=77.5610 Asic[32]=70.1790
Asic[33]=67.9140 Asic[34]=72.3930 Asic[35]=64.5920 Asic[36]=72.1920 Asic[37]=74.6080 Asic[38]=75.4470 Asic[39]=73.8700 Asic[40]=73.9370
Asic[41]=66.2860 Asic[42]=79.4230 Asic[43]=75.8160 Asic[44]=68.6350 Asic[45]=74.7920 Asic[46]=70.7990 Asic[47]=71.2360 Asic[48]=73.8700
Asic[49]=66.5380 Asic[50]=70.6150 Asic[51]=72.6280 Asic[52]=75.7490 Asic[53]=71.8400 Asic[54]=76.5370 Asic[55]=73.5340 Asic[56]=69.2390
Asic[57]=75.1280 Asic[58]=74.3230 Asic[59]=73.4330 Asic[60]=72.3430 Asic[61]=77.6780 Asic[62]=82.4600 Asic[63]=69.5240
get RT hashrate from Chain[7]: (asic index start from 1-63)
Asic[01]=73.5510 Asic[02]=75.9160 Asic[03]=80.1110 Asic[04]=76.9900 Asic[05]=76.1510 Asic[06]=73.5170 Asic[07]=74.9940 Asic[08]=73.1150
Asic[09]=70.6650 Asic[10]=70.6990 Asic[11]=72.4770 Asic[12]=70.1450 Asic[13]=74.3060 Asic[14]=71.8060 Asic[15]=74.7420 Asic[16]=75.6650
Asic[17]=76.8220 Asic[18]=69.5240 Asic[19]=72.0910 Asic[20]=75.2620 Asic[21]=72.0240 Asic[22]=73.2660 Asic[23]=76.2690 Asic[24]=69.9440
Asic[25]=67.7290 Asic[26]=71.7050 Asic[27]=74.6250 Asic[28]=78.2320 Asic[29]=69.8430 Asic[30]=68.4670 Asic[31]=71.5210 Asic[32]=68.9540
Asic[33]=74.6250 Asic[34]=71.8730 Asic[35]=74.4400 Asic[36]=74.8760 Asic[37]=73.9030 Asic[38]=72.9300 Asic[39]=69.6250 Asic[40]=74.9430
Asic[41]=72.7620 Asic[42]=69.4910 Asic[43]=67.4270 Asic[44]=71.4870 Asic[45]=74.4570 Asic[46]=66.6550 Asic[47]=67.5450 Asic[48]=75.4800
Asic[49]=72.2590 Asic[50]=72.9300 Asic[51]=75.6820 Asic[52]=71.9070 Asic[53]=67.9640 Asic[54]=67.8470 Asic[55]=74.3900 Asic[56]=71.0010
Asic[57]=75.8490 Asic[58]=74.9270 Asic[59]=72.3930 Asic[60]=74.3730 Asic[61]=75.5310 Asic[62]=73.8190 Asic[63]=72.4440
Check Chain[J6] ASIC RT error: (asic index start from 1-63)
Check Chain[J7] ASIC RT error: (asic index start from 1-63)
Check Chain[J8] ASIC RT error: (asic index start from 1-63)
Done check_asic_reg
do read temp on Chain[5]
Chain[5] Chip[62] TempTypeID=55 middle offset=29
Chain[5] Chip[62] local Temp=60
Chain[5] Chip[62] middle Temp=70
Special fix Chain[5] Chip[62] middle Temp = 75
Done read temp on Chain[5]
do read temp on Chain[6]
Chain[6] Chip[62] TempTypeID=55 middle offset=29
Chain[6] Chip[62] local Temp=60
Chain[6] Chip[62] middle Temp=72
Special fix Chain[6] Chip[62] middle Temp = 75
Done read temp on Chain[6]
do read temp on Chain[7]
Chain[7] Chip[62] TempTypeID=55 middle offset=28
Chain[7] Chip[62] local Temp=62
Chain[7] Chip[62] middle Temp=72
Special fix Chain[7] Chip[62] middle Temp = 77
Done read temp on Chain[7]
set FAN speed according to: temp_highest=62 temp_top1[PWM_T]=62 temp_top1[TEMP_POS_LOCAL]=62 temp_change=0 fix_fan_steps=0
FAN PWM: 74
read_temp_func Done!
CRC error counter=0
submitted by Timsierramist to BitcoinMining [link] [comments]

The $22,484.00 Butterfly Labs Mini Rig bitcoin miner is a huge, broken, unstable piece of shit.

(This was a rather controversial article posted on Buttcoin.org and became quite popular, even moving to the top of /bitcoin. It's since been mysteriously edited on the site [maybe by g-g-g-ghosts!] so it's being reposted here for posterity's sake. Some numbers may be off by now, but it was all accurate at the time of posting.)
Butterfly Labs has a long and horrible history with their mining rigs. They started taking pre-orders over a year ago, with a ship time sometime in late July. After numerous delays in production, shipping problems and general incompetence, the only thing they’ve managed to get out the door are some of their tiniest miners, the Jalapenos. And those mainly ended up in the hands of reviewers and blogs in order to keep pumping the Butterfly Labs hype train and securing millions of dollars of pre-orders still in limbo.Lucky BFL forums user Luke-JR however scored a sweet Mini Rig from Butterfly Labs (it’s just a coincidence he’s a driver developer for them I’m sure). This rig was originally promised to produce 1500 GH/s hashing power at 1500 watts for $30,000, but has since seen it’s hashing power slashed to a third of what was promised and it’s power consumption increased 75%, now just offer 500 GH/s at 2400 watts. They’ve promised to make good on pre-order buy sending out 3 rigs to match the initial hashing rate, so now it’s only 1500 GH/s at 6900 watts, a reduction in GH/Watt by a factor of 5.
So what does $22,484 buy you? Take a look!
Minirig is here! Today, my Minirig arrived.
http://i.imgur.com/Yp0WPvE.jpg
FedEx apparently dropped it somewhere along the way, and the weakest part of the case, the thin metal part around the back of the PSU, broke.
http://i.imgur.com/lFcOHxP.jpg
I’m not sure how sturdy the back side was supposed to be, but its two pieces aren’t quite together either.
http://i.imgur.com/AVttcOt.jpg
The power supplies (EVGA 1500W) also created havoc interfering with the neutral on the power line. This disrupted X10 communication significantly enough that the pool overflowed because the system controlling it was unable to turn off the pump. Workaround: This PSU supports 240V, so we rewired the outlet. 240V does not use neutral, so now all should be okay.
Edit: 240V workaround is only partial. Still having problems
But the good news is, it all seems to be working for the most part.
Next up, installing it in the window so the heat goes outside
A twenty two thousand dollar box of electronics that is broken out of the box, that required the guy to do a sketchy electrical workaround to get partially working, that he is going to install in a window… and he’s happy about it?
In case you didn’t notice it, the delivered unit is different than the picture on the website. They had to install 2 power supplies instead of 1 and had to modify the case to fit. Also, if you didn’t notice, the LCD/Phone thingy in the front has been replaced by … a piece of cardboard spray painted black. Wonderful.
You could maybe chalk this up to a careless Fedex postman, but when you’re shipping something that costs as much as a mid-sized sedan, how bought putting a little more effort into packing? Dell and HP can ship bigger and heavier servers across the world without this kind of problem.
The unit had to hit its huge power draw increase by putting dual EVGA consumer grade power supplies in the unit. We’re talking almost a 75 amp load (6*1500/120), disregarding power factor. He could very well overload the circuit panel and trip the main breaker for the house.
Let’s take a look inside this guy.
This is from an earlier version of the Minirig (note the single power supply) This is apparently from an earlier FPGA but it will give you a good glimpse at what kind of craftsmanship you can expect from a computer that is half the average household income in the United States.
Consumer grade PSU and cheap USB hubs glued to the inside case.
Electrical tape and random velcro glued to the insides
A closer look at the USB hubs. Plugs are hot glued to stay secured.
Electrical tape everywhere, splices and voided hardware are the theme.
You can view the entire album here.
Despite all that, this thing can still mine bitcoins and it should be profitable. Keep in ind that many people jumped in on the preorders a year ago when bitcoins were still hovering around $6.50 per. Meaning customers paid 1562 bitcoins for that particular piece of shit, which at today’s value is $156,200. Aston martin money. How long will it take them to make their money back (as apposed to just hanging on to them)? If the difficulty didn’t change, they would make 37 bitcoins a day and recoup the initial investment in 124 days. Difficulty is jumping pretty much 20% every 12 days or so, so in the next week before adjustment, they’ll make 259, the next 12 days 369, the next 12 days 312, then 256, then 213, etc.
So by day 127, they’ll be halfway to breaking even, but by day 151 they’ll be making less than 5 bitcoins a day, and even if difficulty stopped rising at that point(which it won’t), it would take another 435 days for a total of 586 days to break even. If difficulty kept rising at the same pace, by day 200 they’d be making 2.4 bitcoins per day, and it would take 1024 days to break even with no difficulty increase. Assuming 25 cents per kw/h, and $100 a bitcoin, it would cost 0.43 of a bitcoin per day in electricity which means the unit would no longer be profitable on a power usage basis by day 307, at which point it will have produced 2620 bitcoins.
Bear in mind this is only for the first few units, and that’s running 24/7 pumping out around 24,000 BTU, so yes, medical bills from heat stroke will be on top of that.
But Alas, the chips don’t run nearly as well as they’re supposed to, frequently running too hot and giving multiple hardware failures. Coindesk noted in one of the first ever runs of the Minirig by hosting provide gigavps that it was running much too hot and erroring out.
At the time of posting, gigavps warned that the unit would be repeatedly shut down while ckolivas, who was assisting, modified the machine’s software to optimise performance. After some tweaking, the device was said to have been left to run continuously for two hours, and was shown to have an average hash rate of 478.1 GH/s. As you can see in the table below, ASIC number four (of a total of eight hashing chips) ran significantly hotter (86 degrees) and consequently gave the highest hardware (HW) error rate.
http://i.imgur.com/q3iGrnb.jpg
So, what happens if you just decide you don’t want this, you don’t want to wait over a year to get a $22,000 broken piece of shit? Nothing, because BFL won’t let you cancel your preorder because they’re now “shipping”, i.e. they sent out one unit to their own company shill.
http://i.imgur.com/0p3Up03.jpg
Which is of course illegal regardless of what Butterfly Labs may say.
So in summary: Don’t buy anything from Butterfly Labs … ever.
submitted by borderpatrol to Buttcoin [link] [comments]

Antminer S9 not hashing?

Good morning folks,
I have an Antminer S9 that has performed flawlessly. After I moved it to a better location, I noticed that it no longer seems to be working. The green light is flashing, but it doesn't seem to be hashing to my pool (Nicehash).
I'm fairly new to Bitcoining mining and can't make sense of some of the information on my status screen. Before I jump into Bitmain support, I was wondering if anyone could clue me in as to what the problem might be.
https://s15.postimg.cc/i0n5qsyoInked_Capture_LI.jpg
I'll post my Kernal Log here.
Thank you in advance!!!
KERNAL LOG: [ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.14.0-xilinx-ge8a2f71-dirty ([email protected]) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #82 SMP PREEMPT Tue May 16 19:49:53 CST 2017
[ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Xilinx Zynq
[ 0.000000] cma: CMA: reserved 128 MiB at 27800000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] On node 0 totalpages: 258048
[ 0.000000] free_area_init_node: node 0, pgdat c0740a40, node_mem_map e6fd8000
[ 0.000000] Normal zone: 1520 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 194560 pages, LIFO batch:31
[ 0.000000] HighMem zone: 496 pages used for memmap
[ 0.000000] HighMem zone: 63488 pages, LIFO batch:15
[ 0.000000] PERCPU: Embedded 8 pages/cpu @e6fc0000 s9088 r8192 d15488 u32768
[ 0.000000] pcpu-alloc: s9088 r8192 d15488 u32768 alloc=8*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 256528
[ 0.000000] Kernel command line: noinitrd mem=1008M console=ttyPS0,115200 root=ubi0:rootfs ubi.mtd=1 rootfstype=ubifs rw rootwait
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 884148K/1032192K available (5032K kernel code, 283K rwdata, 1916K rodata, 204K init, 258K bss, 148044K reserved, 253952K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0xf0000000 - 0xff000000 ( 240 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xef800000 ( 760 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc06d1374 (6949 kB)
[ 0.000000] .init : 0xc06d2000 - 0xc0705380 ( 205 kB)
[ 0.000000] .data : 0xc0706000 - 0xc074cf78 ( 284 kB)
[ 0.000000] .bss : 0xc074cf84 - 0xc078d9fc ( 259 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Dump stacks of tasks blocking RCU-preempt GP.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] ps7-slcr mapped to f0004000
[ 0.000000] zynq_clock_init: clkc starts at f0004100
[ 0.000000] Zynq clock init
[ 0.000015] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[ 0.000308] ps7-ttc #0 at f0006000, irq=43
[ 0.000618] Console: colour dummy device 80x30
[ 0.000658] Calibrating delay loop... 1325.46 BogoMIPS (lpj=6627328)
[ 0.040207] pid_max: default: 32768 minimum: 301
[ 0.040436] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.040459] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.042612] CPU: Testing write buffer coherency: ok
[ 0.042974] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.043036] Setting up static identity map for 0x4c4b00 - 0x4c4b58
[ 0.043263] L310 cache controller enabled
[ 0.043282] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB
[ 0.121037] CPU1: Booted secondary processor
[ 0.210227] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.210357] Brought up 2 CPUs
[ 0.210376] SMP: Total of 2 processors activated.
[ 0.210385] CPU: All CPU(s) started in SVC mode.
[ 0.211051] devtmpfs: initialized
[ 0.213481] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 0.214724] regulator-dummy: no parameters
[ 0.223736] NET: Registered protocol family 16
[ 0.226067] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.228361] cpuidle: using governor ladder
[ 0.228374] cpuidle: using governor menu
[ 0.235908] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered
[ 0.237440] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[ 0.237453] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.237572] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xf0080000
[ 0.259435] bio: create slab at 0
[ 0.261172] vgaarb: loaded
[ 0.261915] SCSI subsystem initialized
[ 0.262814] usbcore: registered new interface driver usbfs
[ 0.262985] usbcore: registered new interface driver hub
[ 0.263217] usbcore: registered new device driver usb
[ 0.263743] media: Linux media interface: v0.10
[ 0.263902] Linux video capture interface: v2.00
[ 0.264150] pps_core: LinuxPPS API ver. 1 registered
[ 0.264162] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[[email protected]](mailto:[email protected])>
[ 0.264286] PTP clock support registered
[ 0.264656] EDAC MC: Ver: 3.0.0
[ 0.265719] Advanced Linux Sound Architecture Driver Initialized.
[ 0.268708] DMA-API: preallocated 4096 debug entries
[ 0.268724] DMA-API: debugging enabled by kernel config
[ 0.268820] Switched to clocksource arm_global_timer
[ 0.289596] NET: Registered protocol family 2
[ 0.290280] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.290375] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.290535] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.290612] TCP: reno registered
[ 0.290633] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 0.290689] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 0.290971] NET: Registered protocol family 1
[ 0.291346] RPC: Registered named UNIX socket transport module.
[ 0.291359] RPC: Registered udp transport module.
[ 0.291368] RPC: Registered tcp transport module.
[ 0.291376] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.291391] PCI: CLS 0 bytes, default 64
[ 0.291857] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[ 0.293945] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 0.295408] bounce pool size: 64 pages
[ 0.296323] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.296525] msgmni has been set to 1486
[ 0.297330] io scheduler noop registered
[ 0.297343] io scheduler deadline registered
[ 0.297385] io scheduler cfq registered (default)
[ 0.308358] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
[ 0.308380] dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.434378] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
[ 1.006815] console [ttyPS0] enabled
[ 1.011106] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to f0068000
[ 1.018731] [drm] Initialized drm 1.1.0 20060810
[ 1.036029] brd: module loaded
[ 1.045494] loop: module loaded
[ 1.055163] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[ 1.060985] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[ 1.068779] libphy: XEMACPS mii bus: probed
[ 1.073341] ------------- phy_id = 0x3625e62
[ 1.078112] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
[ 1.087072] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.093912] ehci-pci: EHCI PCI platform driver
[ 1.101155] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing?
[ 1.107952] usbcore: registered new interface driver usb-storage
[ 1.114850] mousedev: PS/2 mouse device common for all mice
[ 1.120975] i2c /dev entries driver
[ 1.127946] zynq-edac f8006000.ps7-ddrc: ecc not enabled
[ 1.133474] cpufreq_cpu0: failed to get cpu0 regulator: -19
[ 1.139426] Xilinx Zynq CpuIdle Driver started
[ 1.144261] sdhci: Secure Digital Host Controller Interface driver
[ 1.150384] sdhci: Copyright(c) Pierre Ossman
[ 1.154700] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.161601] mmc0: no vqmmc regulator found
[ 1.165614] mmc0: no vmmc regulator found
[ 1.208845] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[ 1.217539] usbcore: registered new interface driver usbhid
[ 1.223054] usbhid: USB HID core driver
[ 1.227806] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[ 1.234107] nand: Micron MT29F2G08ABAEAWP
[ 1.238074] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[ 1.244027] Bad block table found at page 131008, version 0x01
[ 1.250251] Bad block table found at page 130944, version 0x01
[ 1.256303] 3 ofpart partitions found on MTD device pl353-nand
[ 1.262080] Creating 3 MTD partitions on "pl353-nand":
[ 1.267174] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel"
[ 1.275230] 0x000002000000-0x00000b000000 : "angstram-rootfs"
[ 1.282582] 0x00000b000000-0x000010000000 : "upgrade-rootfs"
[ 1.291630] TCP: cubic registered
[ 1.294869] NET: Registered protocol family 17
[ 1.299597] Registering SWP/SWPB emulation handler
[ 1.305497] regulator-dummy: disabling
[ 1.309875] UBI: attaching mtd1 to ubi0
[ 1.836565] UBI: scanning is finished
[ 1.848221] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0
[ 1.855302] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 1.862063] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 1.868728] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[ 1.875605] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0
[ 1.881586] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[ 1.888693] UBI: max/mean erase counter: 4/1, WL threshold: 4096, image sequence number: 1134783803
[ 1.897736] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40
[ 1.906953] UBI: background thread "ubi_bgt0d" started, PID 1080
[ 1.906959] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 1.911038] ALSA device list:
[ 1.911042] No soundcards found.
[ 1.927420] UBIFS: background thread "ubifs_bgt0_0" started, PID 1082
[ 1.956473] UBIFS: recovery needed
[ 2.016970] UBIFS: recovery completed
[ 2.020709] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[ 2.026635] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 2.035771] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[ 2.045653] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 2.050693] UBIFS: media format: w4/r0 (latest is w4/r0), UUID B079DD56-06BB-4E31-8F5E-A6604F480DB2, small LPT model
[ 2.061987] VFS: Mounted root (ubifs filesystem) on device 0:11.
[ 2.069184] devtmpfs: mounted
[ 2.072297] Freeing unused kernel memory: 204K (c06d2000 - c0705000)
[ 2.920928] random: dd urandom read with 0 bits of entropy available
[ 3.318860]
[ 3.318860] bcm54xx_config_init
[ 3.928853]
[ 3.928853] bcm54xx_config_init
[ 7.929682] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[ 7.935787] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
[ 22.563181] In axi fpga driver!
[ 22.566260] request_mem_region OK!
[ 22.569676] AXI fpga dev virtual address is 0xf01fe000
[ 22.574751] *base_vir_addr = 0x8c510
[ 22.590723] In fpga mem driver!
[ 22.593791] request_mem_region OK!
[ 22.597361] fpga mem virtual address is 0xf3000000
[ 23.408156]
[ 23.408156] bcm54xx_config_init
[ 24.038071]
[ 24.038071] bcm54xx_config_init
[ 28.038487] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[ 28.044593] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
This is XILINX board. Totalram: 1039794176
Detect 1GB control board of XILINX
DETECT HW version=0008c510
miner ID : 8118b4c610358854
Miner Type = S9
AsicType = 1387
real AsicNum = 63
use critical mode to search freq...
get PLUG ON=0x000000e0
Find hashboard on Chain[5]
Find hashboard on Chain[6]
Find hashboard on Chain[7]
set_reset_allhashboard = 0x0000ffff
Check chain[5] PIC fw version=0x03
Check chain[6] PIC fw version=0x03
Check chain[7] PIC fw version=0x03
chain[5]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
has freq in PIC, will disable freq setting.
chain[5] has freq in PIC and will jump over...
Chain[5] has core num in PIC
Chain[5] ASIC[15] has core num=5
Check chain[5] PIC fw version=0x03
chain[6]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
has freq in PIC, will disable freq setting.
chain[6] has freq in PIC and will jump over...
Chain[6] has core num in PIC
Chain[6] ASIC[17] has core num=8
Check chain[6] PIC fw version=0x03
chain[7]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
has freq in PIC, will disable freq setting.
chain[7] has freq in PIC and will jump over...
Chain[7] has core num in PIC
Chain[7] ASIC[8] has core num=13
Chain[7] ASIC[9] has core num=11
Chain[7] ASIC[13] has core num=11
Chain[7] ASIC[19] has core num=14
Chain[7] ASIC[30] has core num=6
Chain[7] ASIC[32] has core num=1
Chain[7] ASIC[42] has core num=2
Chain[7] ASIC[55] has core num=1
Chain[7] ASIC[57] has core num=2
Check chain[7] PIC fw version=0x03
get PIC voltage=108 on chain[5], value=880
get PIC voltage=74 on chain[6], value=900
get PIC voltage=108 on chain[7], value=880
set_reset_allhashboard = 0x00000000
chain[5] temp offset record: 62,0,0,0,0,0,35,28
chain[5] temp chip I2C addr=0x98
chain[5] has no middle temp, use special fix mode.
chain[6] temp offset record: 62,0,0,0,0,0,35,28
chain[6] temp chip I2C addr=0x98
chain[6] has no middle temp, use special fix mode.
chain[7] temp offset record: 62,0,0,0,0,0,35,28
chain[7] temp chip I2C addr=0x98
chain[7] has no middle temp, use special fix mode.
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
CRC error counter=0
set command mode to VIL
--- check asic number
After Get ASIC NUM CRC error counter=0
set_baud=0
The min freq=700
set real timeout 52, need sleep=379392
After TEST CRC error counter=0
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
search freq for 1 times, completed chain = 3, total chain num = 3
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
restart Miner chance num=2
waiting for receive_func to exit!
waiting for pic heart to exit!
bmminer not found= 1643 root 0:00 grep bmminer
bmminer not found, restart bmminer ...
This is user mode for mining
Detect 1GB control board of XILINX
Miner Type = S9
Miner compile time: Fri Nov 17 17:57:49 CST 2017 type: Antminer S9set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
set_reset_allhashboard = 0x0000ffff
miner ID : 8118b4c610358854
set_reset_allhashboard = 0x0000ffff
Checking fans!get fan[2] speed=6120
get fan[2] speed=6120
get fan[2] speed=6120
get fan[2] speed=6120
get fan[2] speed=6120
get fan[2] speed=6120
get fan[5] speed=13440
get fan[2] speed=6120
get fan[5] speed=13440
get fan[2] speed=6120
get fan[5] speed=13440
chain[5]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
Chain[J6] has backup chain_voltage=880
Chain[J6] test patten OK temp=-126
Check chain[5] PIC fw version=0x03
chain[6]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
Chain[J7] has backup chain_voltage=900
Chain[J7] test patten OK temp=-120
Check chain[6] PIC fw version=0x03
chain[7]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
Chain[J8] has backup chain_voltage=880
Chain[J8] test patten OK temp=-125
Check chain[7] PIC fw version=0x03
Chain[J6] orignal chain_voltage_pic=108 value=880
Chain[J7] orignal chain_voltage_pic=74 value=900
Chain[J8] orignal chain_voltage_pic=108 value=880
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
Chain[J6] has 63 asic
Chain[J7] has 63 asic
Chain[J8] has 63 asic
Chain[J6] has core num in PIC
Chain[J6] ASIC[15] has core num=5
Chain[J7] has core num in PIC
Chain[J7] ASIC[17] has core num=8
Chain[J8] has core num in PIC
Chain[J8] ASIC[8] has core num=13
Chain[J8] ASIC[9] has core num=11
Chain[J8] ASIC[13] has core num=11
Chain[J8] ASIC[19] has core num=14
Chain[J8] ASIC[30] has core num=6
Chain[J8] ASIC[32] has core num=1
Chain[J8] ASIC[42] has core num=2
Chain[J8] ASIC[55] has core num=1
Chain[J8] ASIC[57] has core num=2
miner total rate=13999GH/s fixed rate=13500GH/s
read PIC voltage=940 on chain[5]
Chain:5 chipnum=63
Chain[J6] voltage added=0.2V
Chain:5 temp offset=0
Chain:5 base freq=487
Asic[ 0]:618
Asic[ 1]:631 Asic[ 2]:681 Asic[ 3]:618 Asic[ 4]:631 Asic[ 5]:681 Asic[ 6]:618 Asic[ 7]:631 Asic[ 8]:675
Asic[ 9]:618 Asic[10]:631 Asic[11]:681 Asic[12]:631 Asic[13]:637 Asic[14]:606 Asic[15]:487 Asic[16]:637
Asic[17]:675 Asic[18]:618 Asic[19]:637 Asic[20]:675 Asic[21]:631 Asic[22]:650 Asic[23]:687 Asic[24]:631
Asic[25]:537 Asic[26]:687 Asic[27]:631 Asic[28]:587 Asic[29]:687 Asic[30]:612 Asic[31]:650 Asic[32]:687
Asic[33]:631 Asic[34]:650 Asic[35]:687 Asic[36]:631 Asic[37]:662 Asic[38]:693 Asic[39]:631 Asic[40]:662
Asic[41]:662 Asic[42]:543 Asic[43]:668 Asic[44]:693 Asic[45]:568 Asic[46]:675 Asic[47]:700 Asic[48]:631
Asic[49]:568 Asic[50]:700 Asic[51]:631 Asic[52]:625 Asic[53]:700 Asic[54]:631 Asic[55]:675 Asic[56]:662
Asic[57]:631 Asic[58]:662 Asic[59]:687 Asic[60]:631 Asic[61]:681 Asic[62]:700
Chain:5 max freq=700
Chain:5 min freq=487
read PIC voltage=940 on chain[6]
Chain:6 chipnum=63
Chain[J7] voltage added=0.1V
Chain:6 temp offset=0
Chain:6 base freq=687
Asic[ 0]:650
Asic[ 1]:650 Asic[ 2]:650 Asic[ 3]:650 Asic[ 4]:650 Asic[ 5]:650 Asic[ 6]:650 Asic[ 7]:650 Asic[ 8]:650
Asic[ 9]:650 Asic[10]:650 Asic[11]:650 Asic[12]:650 Asic[13]:650 Asic[14]:650 Asic[15]:650 Asic[16]:650
Asic[17]:650 Asic[18]:650 Asic[19]:650 Asic[20]:650 Asic[21]:650 Asic[22]:650 Asic[23]:650 Asic[24]:650
Asic[25]:650 Asic[26]:656 Asic[27]:656 Asic[28]:656 Asic[29]:656 Asic[30]:656 Asic[31]:656 Asic[32]:656
Asic[33]:656 Asic[34]:656 Asic[35]:656 Asic[36]:656 Asic[37]:656 Asic[38]:656 Asic[39]:656 Asic[40]:656
Asic[41]:656 Asic[42]:656 Asic[43]:656 Asic[44]:656 Asic[45]:656 Asic[46]:656 Asic[47]:656 Asic[48]:656
Asic[49]:656 Asic[50]:656 Asic[51]:656 Asic[52]:656 Asic[53]:656 Asic[54]:656 Asic[55]:656 Asic[56]:656
Asic[57]:656 Asic[58]:656 Asic[59]:656 Asic[60]:656 Asic[61]:656 Asic[62]:656
Chain:6 max freq=656
Chain:6 min freq=650
read PIC voltage=940 on chain[7]
Chain:7 chipnum=63
Chain[J8] voltage added=0.2V
Chain:7 temp offset=0
Chain:7 base freq=637
Asic[ 0]:656
Asic[ 1]:656 Asic[ 2]:656 Asic[ 3]:656 Asic[ 4]:656 Asic[ 5]:656 Asic[ 6]:656 Asic[ 7]:656 Asic[ 8]:637
Asic[ 9]:637 Asic[10]:656 Asic[11]:656 Asic[12]:656 Asic[13]:637 Asic[14]:656 Asic[15]:662 Asic[16]:662
Asic[17]:662 Asic[18]:662 Asic[19]:637 Asic[20]:662 Asic[21]:662 Asic[22]:662 Asic[23]:662 Asic[24]:662
Asic[25]:662 Asic[26]:662 Asic[27]:662 Asic[28]:662 Asic[29]:662 Asic[30]:637 Asic[31]:662 Asic[32]:662
Asic[33]:662 Asic[34]:662 Asic[35]:662 Asic[36]:662 Asic[37]:662 Asic[38]:662 Asic[39]:662 Asic[40]:662
Asic[41]:662 Asic[42]:650 Asic[43]:662 Asic[44]:662 Asic[45]:662 Asic[46]:662 Asic[47]:662 Asic[48]:662
Asic[49]:662 Asic[50]:662 Asic[51]:662 Asic[52]:662 Asic[53]:662 Asic[54]:662 Asic[55]:650 Asic[56]:662
Asic[57]:650 Asic[58]:662 Asic[59]:662 Asic[60]:662 Asic[61]:662 Asic[62]:662
Chain:7 max freq=662
Chain:7 min freq=637
Miner fix freq ...
read PIC voltage=940 on chain[5]
Chain:5 chipnum=63
Chain[J6] voltage added=0.2V
Chain:5 temp offset=0
Chain:5 base freq=487
Asic[ 0]:618
Asic[ 1]:631 Asic[ 2]:650 Asic[ 3]:618 Asic[ 4]:631 Asic[ 5]:656 Asic[ 6]:618 Asic[ 7]:631 Asic[ 8]:656
Asic[ 9]:618 Asic[10]:631 Asic[11]:656 Asic[12]:631 Asic[13]:637 Asic[14]:606 Asic[15]:487 Asic[16]:637
Asic[17]:656 Asic[18]:618 Asic[19]:637 Asic[20]:656 Asic[21]:631 Asic[22]:650 Asic[23]:656 Asic[24]:631
Asic[25]:537 Asic[26]:656 Asic[27]:631 Asic[28]:587 Asic[29]:656 Asic[30]:612 Asic[31]:650 Asic[32]:656
Asic[33]:631 Asic[34]:650 Asic[35]:656 Asic[36]:631 Asic[37]:656 Asic[38]:656 Asic[39]:631 Asic[40]:656
Asic[41]:656 Asic[42]:543 Asic[43]:656 Asic[44]:656 Asic[45]:568 Asic[46]:656 Asic[47]:656 Asic[48]:631
Asic[49]:568 Asic[50]:656 Asic[51]:631 Asic[52]:625 Asic[53]:656 Asic[54]:631 Asic[55]:656 Asic[56]:656
Asic[57]:631 Asic[58]:656 Asic[59]:656 Asic[60]:631 Asic[61]:656 Asic[62]:656
Chain:5 max freq=656
Chain:5 min freq=487
read PIC voltage=940 on chain[6]
Chain:6 chipnum=63
Chain[J7] voltage added=0.1V
Chain:6 temp offset=0
Chain:6 base freq=687
Asic[ 0]:631
Asic[ 1]:631 Asic[ 2]:631 Asic[ 3]:631 Asic[ 4]:631 Asic[ 5]:631 Asic[ 6]:631 Asic[ 7]:631 Asic[ 8]:631
Asic[ 9]:631 Asic[10]:631 Asic[11]:631 Asic[12]:631 Asic[13]:631 Asic[14]:631 Asic[15]:631 Asic[16]:631
Asic[17]:631 Asic[18]:631 Asic[19]:631 Asic[20]:631 Asic[21]:631 Asic[22]:631 Asic[23]:631 Asic[24]:631
Asic[25]:631 Asic[26]:631 Asic[27]:631 Asic[28]:631 Asic[29]:631 Asic[30]:631 Asic[31]:631 Asic[32]:631
Asic[33]:631 Asic[34]:631 Asic[35]:637 Asic[36]:637 Asic[37]:637 Asic[38]:637 Asic[39]:637 Asic[40]:637
Asic[41]:637 Asic[42]:637 Asic[43]:637 Asic[44]:637 Asic[45]:637 Asic[46]:637 Asic[47]:637 Asic[48]:637
Asic[49]:637 Asic[50]:637 Asic[51]:637 Asic[52]:637 Asic[53]:637 Asic[54]:637 Asic[55]:637 Asic[56]:637
Asic[57]:637 Asic[58]:637 Asic[59]:637 Asic[60]:637 Asic[61]:637 Asic[62]:637
Chain:6 max freq=637
Chain:6 min freq=631
read PIC voltage=940 on chain[7]
Chain:7 chipnum=63
Chain[J8] voltage added=0.2V
Chain:7 temp offset=0
Chain:7 base freq=637
Asic[ 0]:637
Asic[ 1]:637 Asic[ 2]:637 Asic[ 3]:637 Asic[ 4]:637 Asic[ 5]:637 Asic[ 6]:637 Asic[ 7]:637 Asic[ 8]:637
Asic[ 9]:637 Asic[10]:637 Asic[11]:637 Asic[12]:637 Asic[13]:637 Asic[14]:637 Asic[15]:637 Asic[16]:637
Asic[17]:637 Asic[18]:637 Asic[19]:637 Asic[20]:637 Asic[21]:637 Asic[22]:637 Asic[23]:637 Asic[24]:637
Asic[25]:637 Asic[26]:637 Asic[27]:637 Asic[28]:637 Asic[29]:637 Asic[30]:637 Asic[31]:637 Asic[32]:637
Asic[33]:637 Asic[34]:637 Asic[35]:637 Asic[36]:637 Asic[37]:637 Asic[38]:637 Asic[39]:637 Asic[40]:637
Asic[41]:637 Asic[42]:637 Asic[43]:637 Asic[44]:637 Asic[45]:637 Asic[46]:637 Asic[47]:637 Asic[48]:637
Asic[49]:643 Asic[50]:643 Asic[51]:643 Asic[52]:643 Asic[53]:643 Asic[54]:643 Asic[55]:643 Asic[56]:643
Asic[57]:643 Asic[58]:643 Asic[59]:643 Asic[60]:643 Asic[61]:643 Asic[62]:643
Chain:7 max freq=643
Chain:7 min freq=637
max freq = 656
set baud=1
Chain[J6] PIC temp offset=62,0,0,0,0,0,35,28
chain[5] temp chip I2C addr=0x98
chain[5] has no middle temp, use special fix mode.
Chain[J6] chip[244] use PIC middle temp offset=0 typeID=55
New offset Chain[5] chip[244] local:26 remote:27 offset:29
Chain[J6] chip[244] get middle temp offset=29 typeID=55
Chain[J7] PIC temp offset=62,0,0,0,0,0,35,28
chain[6] temp chip I2C addr=0x98
chain[6] has no middle temp, use special fix mode.
Chain[J7] chip[244] use PIC middle temp offset=0 typeID=55
New offset Chain[6] chip[244] local:26 remote:27 offset:29
Chain[J7] chip[244] get middle temp offset=29 typeID=55
Chain[J8] PIC temp offset=62,0,0,0,0,0,35,28
chain[7] temp chip I2C addr=0x98
chain[7] has no middle temp, use special fix mode.
Chain[J8] chip[244] use PIC middle temp offset=0 typeID=55
New offset Chain[7] chip[244] local:26 remote:28 offset:28
Chain[J8] chip[244] get middle temp offset=28 typeID=55
miner rate=13501 voltage limit=900 on chain[5]
get PIC voltage=880 on chain[5], check: must be < 900
miner rate=13501 voltage limit=900 on chain[6]
get PIC voltage=900 on chain[6], check: must be < 900
miner rate=13501 voltage limit=900 on chain[7]
get PIC voltage=880 on chain[7], check: must be < 900
Chain[J6] set working voltage=880 [108]
Chain[J7] set working voltage=900 [74]
Chain[J8] set working voltage=880 [108]
do heat board 8xPatten for 1 times
start send works on chain[5]
start send works on chain[6]
start send works on chain[7]
get send work num :57456 on Chain[5]
get send work num :57456 on Chain[6]
get send work num :57456 on Chain[7]
wait recv nonce on chain[5]
wait recv nonce on chain[6]
wait recv nonce on chain[7]
get nonces on chain[5]
require nonce number:912
require validnonce number:57456
asic[00]=912 asic[01]=912 asic[02]=912 asic[03]=912 asic[04]=912 asic[05]=912 asic[06]=912 asic[07]=912
asic[08]=912 asic[09]=912 asic[10]=912 asic[11]=912 asic[12]=912 asic[13]=912 asic[14]=912 asic[15]=912
asic[16]=912 asic[17]=912 asic[18]=912 asic[19]=912 asic[20]=912 asic[21]=912 asic[22]=912 asic[23]=912
asic[24]=912 asic[25]=912 asic[26]=912 asic[27]=912 asic[28]=912 asic[29]=912 asic[30]=912 asic[31]=912
asic[32]=912 asic[33]=912 asic[34]=912 asic[35]=912 asic[36]=912 asic[37]=912 asic[38]=912 asic[39]=912
asic[40]=912 asic[41]=912 asic[42]=912 asic[43]=912 asic[44]=912 asic[45]=912 asic[46]=912 asic[47]=912
asic[48]=912 asic[49]=912 asic[50]=912 asic[51]=912 asic[52]=912 asic[53]=912 asic[54]=912 asic[55]=912
asic[56]=912 asic[57]=912 asic[58]=912 asic[59]=912 asic[60]=912 asic[61]=912 asic[62]=912
Below ASIC's core didn't receive all the nonce, they should receive 8 nonce each!
freq[00]=618 freq[01]=631 freq[02]=650 freq[03]=618 freq[04]=631 freq[05]=656 freq[06]=618 freq[07]=631
freq[08]=656 freq[09]=618 freq[10]=631 freq[11]=656 freq[12]=631 freq[13]=637 freq[14]=606 freq[15]=487
freq[16]=637 freq[17]=656 freq[18]=618 freq[19]=637 freq[20]=656 freq[21]=631 freq[22]=650 freq[23]=656
freq[24]=631 freq[25]=537 freq[26]=656 freq[27]=631 freq[28]=587 freq[29]=656 freq[30]=612 freq[31]=650
freq[32]=656 freq[33]=631 freq[34]=650 freq[35]=656 freq[36]=631 freq[37]=656 freq[38]=656 freq[39]=631
freq[40]=656 freq[41]=656 freq[42]=543 freq[43]=656 freq[44]=656 freq[45]=568 freq[46]=656 freq[47]=656
freq[48]=631 freq[49]=568 freq[50]=656 freq[51]=631 freq[52]=625 freq[53]=656 freq[54]=631 freq[55]=656
freq[56]=656 freq[57]=631 freq[58]=656 freq[59]=656 freq[60]=631 freq[61]=656 freq[62]=656
total valid nonce number:57456
total send work number:57456
require valid nonce number:57456
repeated_nonce_num:0
err_nonce_num:25912
last_nonce_num:14370
get nonces on chain[6]
require nonce number:912
require validnonce number:57456
asic[00]=912 asic[01]=912 asic[02]=912 asic[03]=912 asic[04]=912 asic[05]=912 asic[06]=912 asic[07]=912
asic[08]=912 asic[09]=912 asic[10]=912 asic[11]=912 asic[12]=912 asic[13]=912 asic[14]=912 asic[15]=912
asic[16]=912 asic[17]=912 asic[18]=912 asic[19]=912 asic[20]=912 asic[21]=912 asic[22]=912 asic[23]=912
asic[24]=912 asic[25]=912 asic[26]=912 asic[27]=912 asic[28]=912 asic[29]=912 asic[30]=912 asic[31]=912
asic[32]=912 asic[33]=912 asic[34]=912 asic[35]=912 asic[36]=912 asic[37]=912 asic[38]=912 asic[39]=912
asic[40]=912 asic[41]=912 asic[42]=912 asic[43]=912 asic[44]=912 asic[45]=912 asic[46]=912 asic[47]=912
asic[48]=912 asic[49]=912 asic[50]=912 asic[51]=912 asic[52]=912 asic[53]=912 asic[54]=912 asic[55]=912
asic[56]=912 asic[57]=912 asic[58]=912 asic[59]=912 asic[60]=912 asic[61]=912 asic[62]=912
Below ASIC's core didn't receive all the nonce, they should receive 8 nonce each!
freq[00]=631 freq[01]=631 freq[02]=631 freq[03]=631 freq[04]=631 freq[05]=631 freq[06]=631 freq[07]=631
freq[08]=631 freq[09]=631 freq[10]=631 freq[11]=631 freq[12]=631 freq[13]=631 freq[14]=631 freq[15]=631
freq[16]=631 freq[17]=631 freq[18]=631 freq[19]=631 freq[20]=631 freq[21]=631 freq[22]=631 freq[23]=631
freq[24]=631 freq[25]=631 freq[26]=631 freq[27]=631 freq[28]=631 freq[29]=631 freq[30]=631 freq[31]=631
freq[32]=631 freq[33]=631 freq[34]=631 freq[35]=637 freq[36]=637 freq[37]=637 freq[38]=637 freq[39]=637
freq[40]=637 freq[41]=637 freq[42]=637 freq[43]=637 freq[44]=637 freq[45]=637 freq[46]=637 freq[47]=637
freq[48]=637 freq[49]=637 freq[50]=637 freq[51]=637 freq[52]=637 freq[53]=637 freq[54]=637 freq[55]=637
freq[56]=637 freq[57]=637 freq[58]=637 freq[59]=637 freq[60]=637 freq[61]=637 freq[62]=637
total valid nonce number:57456
total send work number:57456
require valid nonce number:57456
repeated_nonce_num:0
err_nonce_num:25987
last_nonce_num:14368
get nonces on chain[7]
require nonce number:912
require validnonce number:57456
asic[00]=912 asic[01]=912 asic[02]=912 asic[03]=912 asic[04]=912 asic[05]=912 asic[06]=912 asic[07]=912
asic[08]=907 asic[09]=912 asic[10]=912 asic[11]=912 asic[12]=912 asic[13]=912 asic[14]=912 asic[15]=912
asic[16]=912 asic[17]=912 asic[18]=912 asic[19]=909 asic[20]=912 asic[21]=912 asic[22]=912 asic[23]=912
asic[24]=912 asic[25]=912 asic[26]=912 asic[27]=912 asic[28]=912 asic[29]=912 asic[30]=912 asic[31]=912
asic[32]=912 asic[33]=912 asic[34]=912 asic[35]=912 asic[36]=912 asic[37]=912 asic[38]=912 asic[39]=912
asic[40]=912 asic[41]=912 asic[42]=912 asic[43]=912 asic[44]=912 asic[45]=912 asic[46]=912 asic[47]=912
asic[48]=912 asic[49]=912 asic[50]=912 asic[51]=912 asic[52]=912 asic[53]=912 asic[54]=912 asic[55]=911
asic[56]=912 asic[57]=912 asic[58]=912 asic[59]=912 asic[60]=912 asic[61]=912 asic[62]=912
Below ASIC's core didn't receive all the nonce, they should receive 8 nonce each!
asic[08]=907
core[049]=7 core[053]=5 core[056]=7
asic[19]=909
core[064]=7 core[112]=6
asic[55]=911
core[007]=7
freq[00]=637 freq[01]=637 freq[02]=637 freq[03]=637 freq[04]=637 freq[05]=637 freq[06]=637 freq[07]=637
freq[08]=637 freq[09]=637 freq[10]=637 freq[11]=637 freq[12]=637 freq[13]=637 freq[14]=637 freq[15]=637
freq[16]=637 freq[17]=637 freq[18]=637 freq[19]=637 freq[20]=637 freq[21]=637 freq[22]=637 freq[23]=637
freq[24]=637 freq[25]=637 freq[26]=637 freq[27]=637 freq[28]=637 freq[29]=637 freq[30]=637 freq[31]=637
freq[32]=637 freq[33]=637 freq[34]=637 freq[35]=637 freq[36]=637 freq[37]=637 freq[38]=637 freq[39]=637
freq[40]=637 freq[41]=637 freq[42]=637 freq[43]=637 freq[44]=637 freq[45]=637 freq[46]=637 freq[47]=637
freq[48]=637 freq[49]=643 freq[50]=643 freq[51]=643 freq[52]=643 freq[53]=643 freq[54]=643 freq[55]=643
freq[56]=643 freq[57]=643 freq[58]=643 freq[59]=643 freq[60]=643 freq[61]=643 freq[62]=643
total valid nonce number:57447
total send work number:57456
require valid nonce number:57456
repeated_nonce_num:0
err_nonce_num:26183
last_nonce_num:35748
chain[5]: All chip cores are opened OK!
Test Patten on chain[5]: OK!
chain[6]: All chip cores are opened OK!
Test Patten on chain[6]: OK!
chain[7]: All chip cores are opened OK!
Test Patten on chain[7]: OK!
setStartTimePoint total_tv_start_sys=217 total_tv_end_sys=218
restartNum = 2 , auto-reinit enabled...
do read_temp_func once...
do check_asic_reg 0x08
get RT hashrate from Chain[5]: (asic index start from 1-63)
Asic[01]=72.5110 Asic[02]=68.6020 Asic[03]=74.4230 Asic[04]=74.6750 Asic[05]=71.4540 Asic[06]=77.5610 Asic[07]=74.7760 Asic[08]=74.3900
Asic[09]=77.7790 Asic[10]=76.7220 Asic[11]=73.8020 Asic[12]=68.5850 Asic[13]=76.1680 Asic[14]=72.4770 Asic[15]=73.0470 Asic[16]=57.8810
Asic[17]=74.4740 Asic[18]=76.4530 Asic[19]=67.8800 Asic[20]=70.1280 Asic[21]=73.7520 Asic[22]=74.6580 Asic[23]=73.6850 Asic[24]=78.5170
Asic[25]=73.6850 Asic[26]=63.6860 Asic[27]=80.9660 Asic[28]=73.9200 Asic[29]=68.9870 Asic[30]=75.6310 Asic[31]=74.9770 Asic[32]=69.4570
Asic[33]=74.6580 Asic[34]=79.8930 Asic[35]=76.6710 Asic[36]=74.3730 Asic[37]=66.6050 Asic[38]=76.7380 Asic[39]=71.4540 Asic[40]=69.3060
Asic[41]=72.5610 Asic[42]=73.8530 Asic[43]=58.9210 Asic[44]=75.3800 Asic[45]=73.1310 Asic[46]=68.4000 Asic[47]=77.6780 Asic[48]=73.1150
Asic[49]=69.2890 Asic[50]=62.8130 Asic[51]=74.2720 Asic[52]=73.1480 Asic[53]=67.4440 Asic[54]=72.4940 Asic[55]=68.1990 Asic[56]=72.4100
Asic[57]=75.3460 Asic[58]=66.1350 Asic[59]=72.9800 Asic[60]=78.1480 Asic[61]=72.3260 Asic[62]=72.5610 Asic[63]=77.7950
get RT hashrate from Chain[6]: (asic index start from 1-63)
Asic[01]=67.6620 Asic[02]=75.9840 Asic[03]=70.3300 Asic[04]=75.5640 Asic[05]=62.8470 Asic[06]=70.2790 Asic[07]=74.5240 Asic[08]=72.9130
Asic[09]=70.6320 Asic[10]=72.5610 Asic[11]=73.9370 Asic[12]=77.3420 Asic[13]=72.4440 Asic[14]=68.8030 Asic[15]=73.0810 Asic[16]=73.8360
Asic[17]=73.5510 Asic[18]=73.9700 Asic[19]=71.0340 Asic[20]=71.1680 Asic[21]=72.1580 Asic[22]=78.8190 Asic[23]=71.9230 Asic[24]=69.4570
Asic[25]=67.7630 Asic[26]=71.7220 Asic[27]=76.4030 Asic[28]=71.1180 Asic[29]=68.7360 Asic[30]=69.7090 Asic[31]=77.5610 Asic[32]=70.1790
Asic[33]=67.9140 Asic[34]=72.3930 Asic[35]=64.5920 Asic[36]=72.1920 Asic[37]=74.6080 Asic[38]=75.4470 Asic[39]=73.8700 Asic[40]=73.9370
Asic[41]=66.2860 Asic[42]=79.4230 Asic[43]=75.8160 Asic[44]=68.6350 Asic[45]=74.7920 Asic[46]=70.7990 Asic[47]=71.2360 Asic[48]=73.8700
Asic[49]=66.5380 Asic[50]=70.6150 Asic[51]=72.6280 Asic[52]=75.7490 Asic[53]=71.8400 Asic[54]=76.5370 Asic[55]=73.5340 Asic[56]=69.2390
Asic[57]=75.1280 Asic[58]=74.3230 Asic[59]=73.4330 Asic[60]=72.3430 Asic[61]=77.6780 Asic[62]=82.4600 Asic[63]=69.5240
get RT hashrate from Chain[7]: (asic index start from 1-63)
Asic[01]=73.5510 Asic[02]=75.9160 Asic[03]=80.1110 Asic[04]=76.9900 Asic[05]=76.1510 Asic[06]=73.5170 Asic[07]=74.9940 Asic[08]=73.1150
Asic[09]=70.6650 Asic[10]=70.6990 Asic[11]=72.4770 Asic[12]=70.1450 Asic[13]=74.3060 Asic[14]=71.8060 Asic[15]=74.7420 Asic[16]=75.6650
Asic[17]=76.8220 Asic[18]=69.5240 Asic[19]=72.0910 Asic[20]=75.2620 Asic[21]=72.0240 Asic[22]=73.2660 Asic[23]=76.2690 Asic[24]=69.9440
Asic[25]=67.7290 Asic[26]=71.7050 Asic[27]=74.6250 Asic[28]=78.2320 Asic[29]=69.8430 Asic[30]=68.4670 Asic[31]=71.5210 Asic[32]=68.9540
Asic[33]=74.6250 Asic[34]=71.8730 Asic[35]=74.4400 Asic[36]=74.8760 Asic[37]=73.9030 Asic[38]=72.9300 Asic[39]=69.6250 Asic[40]=74.9430
Asic[41]=72.7620 Asic[42]=69.4910 Asic[43]=67.4270 Asic[44]=71.4870 Asic[45]=74.4570 Asic[46]=66.6550 Asic[47]=67.5450 Asic[48]=75.4800
Asic[49]=72.2590 Asic[50]=72.9300 Asic[51]=75.6820 Asic[52]=71.9070 Asic[53]=67.9640 Asic[54]=67.8470 Asic[55]=74.3900 Asic[56]=71.0010
Asic[57]=75.8490 Asic[58]=74.9270 Asic[59]=72.3930 Asic[60]=74.3730 Asic[61]=75.5310 Asic[62]=73.8190 Asic[63]=72.4440
Check Chain[J6] ASIC RT error: (asic index start from 1-63)
Check Chain[J7] ASIC RT error: (asic index start from 1-63)
Check Chain[J8] ASIC RT error: (asic index start from 1-63)
Done check_asic_reg
do read temp on Chain[5]
Chain[5] Chip[62] TempTypeID=55 middle offset=29
Chain[5] Chip[62] local Temp=60
Chain[5] Chip[62] middle Temp=70
Special fix Chain[5] Chip[62] middle Temp = 75
Done read temp on Chain[5]
do read temp on Chain[6]
Chain[6] Chip[62] TempTypeID=55 middle offset=29
Chain[6] Chip[62] local Temp=60
Chain[6] Chip[62] middle Temp=72
Special fix Chain[6] Chip[62] middle Temp = 75
Done read temp on Chain[6]
do read temp on Chain[7]
Chain[7] Chip[62] TempTypeID=55 middle offset=28
Chain[7] Chip[62] local Temp=62
Chain[7] Chip[62] middle Temp=72
Special fix Chain[7] Chip[62] middle Temp = 77
Done read temp on Chain[7]
set FAN speed according to: temp_highest=62 temp_top1[PWM_T]=62 temp_top1[TEMP_POS_LOCAL]=62 temp_change=0 fix_fan_steps=0
FAN PWM: 74
read_temp_func Done!
CRC error counter=0
submitted by Timsierramist to BITMAIN [link] [comments]

Frequently Asked Question: What's an ASIC, FPGA?

So you're sick of just mining on your GPU, and not a fan of the electric bill after a month of mining? There has to be a better option out there than your loud GPU in your gaming computer. There is!
Shortly after GPUs became popular for bitcoin mining, enterprising folks started looking at other things they can re-purpose to mine bitcoins more efficiently. Around mid-year 2011, the first devices sprang up that are called FPGAs or Field Programmable Gate Arrays. These are nothing new to the hobbyist community, they've been around for a while for crackers and other security-conscious folks looking at ways to defeat cryptographic locks. Hey! I know something that uses cryptographic calculations to secure its network! BITCOINS! Yep, so some miners developed their own boards and slapped some FPGA chips on them (most commonly the Spartan-6), and wrote specific firmware and "bitstreams" to more efficiently calculate bitcoin hashes. The first generations were sort of slow, but still they had better efficiency than a GPU. Some of the latest generation included the Icarus boards, Cairnsmore, x6500, and ModMiner Quad.
In early 2012(i think my timeline is right), Butterfly Labs(BFL) was selling their own FPGA miner that hashed at 800 Mhash/s using 80 watts and only cost US$600 amazing! These grew very popular, but people could see that FPGAs still weren't the most efficient way to hash their shares. BFL then announced that they would be designing their own chips that would be orders of magnitude faster than anything ever seen. These would be the ASICs (or Application Specific Integrated Circuit)everyone is raving about. ASICs are--as the name implies--specifically designed for one thing, and one thing only. Bitcoins. This is all it can do, and can't really be repurposed like an FPGA to other applications. Who wouldn't want a US$150 "Jalapeno" that hashes at 3.5 GIGAhashes/s using only power from a USB port?? Crazy! So summer 2012, BFL says they will ship before Christmas. Various things happen and we now still don't have any confirmed ship dates from BFL.
A few other companies have sprouted up, ASICminer which I believe is developing their own chips to mine themselves, but in a responsible way as to not threaten the network with a sudden influx of hashing. bASIC was a fiasco that was developed by the creator of the ModMiner Quad(which is actually a fantastic miner, I own one, and love it.) where he took many preorders, promised lots of people amazing ASIC performance, but in early 2013 the stress of the whole endeavour got to him and he gave up, refunded money(I think it's still being refunded now, or maybe it's been cleared up already.)
Avalon is the only company we know has ASIC mining hardware in the wild. It is not certain exactly how many are out there, but they have been confirmed by independent sources. The Avalon units are expensive(75 BTC) and have been in limited production runs (or batches) of a few hundred units that were pre-sold out very quickly.
All of this info is gleaned from the Custom Hardware forum over at bitcointalk.org over the past year or so I've been involved in bitcoin. I may have some facts wrong, but this is the gist of the situation and hopefully gives you an insight on the state of the hardware war against bitcoin
Thanks for reading!
submitted by purelithium to BitcoinMining [link] [comments]

An idea to promote mining decentralization

When Bitcoin was first created, every full node was a miner. And every full node was using the CPU to find blocks. And most were successful at this because the difficulty was extremely low (compared to today). But as more and more people started using Bitcoin (and mining with their CPUs and GPUs), it became increasingly difficult and rare to find a block as a solo miner.
Mining pools changed all that. Rather than finding an entire block on rare occasions, mining pools allow the miner to combine his hash power with the hash power of others to find blocks, and get a percentage of the reward. The mining pools which charged the lowest fees and had the largest combined hash powers were the most popular and users/miners would flock to these pools in droves. This resulted in unprecedented centralization of Bitcoin mining into a handful of mining pools that we see today. This was not something that Satoshi expected, and it has been one of the leading causes for people to stop running full nodes. A full node cannot hope to compete with mining pools with petahashes of combined ASIC hashpower.
But there is one mining pool system that actually protects the decentralized nature of Bitcoin: P2Pool. This method for mining requires each miner to run their own full node, but rewards participating miners as if they were participating in a regular pool. This is a "Good Thing (TM)". But setting up P2Pool is complicated, and doesn't really offer any benefit over running a competing mining software and connecting to some larger pool.
What if we could make it easier to participate in P2Pool? I would propose that Bitcoin Core/XT/NameYourForkHere each update their built-in solo-mining code, to make every full node a functional member of P2Pool BY DEFAULT. Allow full node operators the ability to earn a tiny amount of Bitcoin just for operating a full node. Even a CPU miner can mine some tiny amount of BTC as a member of P2Pool, especially if P2Pool is the overwhelmingly dominate pool. And if Core/XT/NameYourFork also added support for GPU/FPGA/ASIC devices right into the client, so that your copy of Bitcoin-QT is just as capable of connecting to some USB connected 100TH ASIC rig as specialized mining software and has the potential to earn bitcoin in small amounts over time, folks might take that simplest and most decentralized approach, and just mine the old-fashioned way... With a full node.
submitted by ergofobe to bitcoinxt [link] [comments]

An idea to promote mining decentralization

When Bitcoin was first created, every full node was a miner. And every full node was using the CPU to find blocks. And most were successful at this because the difficulty was extremely low (compared to today). But as more and more people started using Bitcoin (and mining with their CPUs and GPUs), it became increasingly difficult and rare to find a block as a solo miner.
Mining pools changed all that. Rather than finding an entire block on rare occasions, mining pools allow the miner to combine his hash power with the hash power of others to find blocks, and get a percentage of the reward. The mining pools which charged the lowest fees and had the largest combined hash powers were the most popular and users/miners would flock to these pools in droves. This resulted in unprecedented centralization of Bitcoin mining into a handful of mining pools that we see today. This was not something that Satoshi expected, and it has been one of the leading causes for people to stop running full nodes. A full node cannot hope to compete with mining pools with petahashes of combined ASIC hashpower.
But there is one mining pool system that actually protects the decentralized nature of Bitcoin: P2Pool. This method for mining requires each miner to run their own full node, but rewards participating miners as if they were participating in a regular pool. This is a "Good Thing (TM)". But setting up P2Pool is complicated, and doesn't really offer any benefit over running a competing mining software and connecting to some larger pool.
What if we could make it easier to participate in P2Pool? I would propose that Bitcoin Core/XT/NameYourForkHere each update their built-in solo-mining code, to make every full node a functional member of P2Pool BY DEFAULT. Allow full node operators the ability to earn a tiny amount of Bitcoin just for operating a full node. Even a CPU miner can mine some tiny amount of BTC as a member of P2Pool, especially if P2Pool is the overwhelmingly dominate pool. And if Core/XT/NameYourFork also added support for GPU/FPGA/ASIC devices right into the client, so that your copy of Bitcoin-QT is just as capable of connecting to some USB connected 100TH ASIC rig as specialized mining software and has the potential to earn bitcoin in small amounts over time, folks might take that simplest and most decentralized approach, and just mine the old-fashioned way... With a full node.
submitted by ergofobe to bitcoin_uncensored [link] [comments]

An opinion on how Bitcoin is good for gaming [xpost r/truegaming]

A few days ago, I was a bit bored (read: procrastinating), and I ended up reading about Bitcoin. For those of you unfamiliar with the topic, the gist is this:
Bitcoin is a decentralized currency based entirely in cyberspace which is derived based on cryptographic hashes. The value is based on whatever value the market as a collective assigns to it, much like most modern currencies (USD, Euro, etc.). Transactions are enacted entirely over p2p systems, so it has useful applications ranging from legal online marketplace deals, to gray-area deals such as Wikileaks donations, to illicit activities on Silk Road, much like real world cash. New bitcoin units are 'mined' by using a computer to crack the encrypted provided by the p2p system.
Summarized from wikipedia and the official site
What applies to gaming is the mining of new coins. Originally users would let their cpu mine out the encryption blocks, but as the difficulty of mining increased, the users had to pool resources and work together. Eventually, someone realized that more efficient mining could be done using a computer's gpu as opposed to the cpu. The reason this was a big step has to do with the gpu's ability to much more effectively crunch the numbers of the encrypted block (for more information read the informative wiki page on it). As more users switched to this method, the difficulty increased to balance the new abilities. Avarice finds a way though, the more devoted users are employing devoted 'mining rigs' to increase profits. Some entrepreneurial souls have started producing and marketing advanced rigs for extreme mining (e.g. ztex and butterflylabs ).
This may not be good for the Bitcoin economy as a whole though, because it generates an upper echelon of powerusers who can afford the economic arms-race, and it may not be ultimately sustainable. BUT, this would be good for gaming because if the arms race continues we could see accelerated the development of gpu technology. This is all conjecture of course, but in my opinion, a Bitcoin bubble may be good for the community as a whole.
Conflict of Interest note: I am not affiliated with Bitcoin and do not personally invest in this currency.
Comment from thread:
You wrongly assume that bitcoins are even a factor in pushing hardware manufacturers to improve. It's not even a drop in the bucket compared to all other more relevant types of software that make use of graphics cards. -FromMars
Reply:
My view was that this niche allows smaller companies to come in and compete with the larger manufacturers (AMD/Nvidia) and bring new ideas to the table for efficient processing. I concede that high end applications will probably drive the gpu industry, but I posit that there is a chance for outside development ideas. -wessubba
submitted by wessubba to hardware [link] [comments]

An idea to promote mining decentralization

When Bitcoin was first created, every full node was a miner. And every full node was using the CPU to find blocks. And most were successful at this because the difficulty was extremely low (compared to today). But as more and more people started using Bitcoin (and mining with their CPUs and GPUs), it became increasingly difficult and rare to find a block as a solo miner.
Mining pools changed all that. Rather than finding an entire block on rare occasions, mining pools allow the miner to combine his hash power with the hash power of others to find blocks, and get a percentage of the reward. The mining pools which charged the lowest fees and had the largest combined hash powers were the most popular and users/miners would flock to these pools in droves. This resulted in unprecedented centralization of Bitcoin mining into a handful of mining pools that we see today. This was not something that Satoshi expected, and it has been one of the leading causes for people to stop running full nodes. A full node cannot hope to compete with mining pools with petahashes of combined ASIC hashpower.
But there is one mining pool system that actually protects the decentralized nature of Bitcoin: P2Pool. This method for mining requires each miner to run their own full node, but rewards participating miners as if they were participating in a regular pool. This is a "Good Thing (TM)". But setting up P2Pool is complicated, and doesn't really offer any benefit over running a competing mining software and connecting to some larger pool.
What if we could make it easier to participate in P2Pool? I would propose that Bitcoin Core/XT/NameYourForkHere each update their built-in solo-mining code, to make every full node a functional member of P2Pool BY DEFAULT. Allow full node operators the ability to earn a tiny amount of Bitcoin just for operating a full node. Even a CPU miner can mine some tiny amount of BTC as a member of P2Pool, especially if P2Pool is the overwhelmingly dominate pool. And if Core/XT/NameYourFork also added support for GPU/FPGA/ASIC devices right into the client, so that your copy of Bitcoin-QT is just as capable of connecting to some USB connected 100TH ASIC rig as specialized mining software and has the potential to earn bitcoin in small amounts over time, folks might take that simplest and most decentralized approach, and just mine the old-fashioned way... With a full node.
submitted by ergofobe to Bitcoin [link] [comments]

BitCoin Mining FPGA Card Finally!! Unboxing of a QUAD FPGA Bitcoin Mining System BitCoin Mining FPGA Card - YouTube Lancelot FPGA Bitcoin Miner Unboxing USB Bitcoin Miner - The Power of 1000's Computers - YouTube

GPUs, CPUs and other hardware not specifically designed for Bitcoin mining can be found in the Non-specialized_hardware_comparison. Notes: Mhash/s = millions hashes per second (double sha256 raw speed performance; may not be very energy efficient with some models) Mhash/J = millions hashes per joule (energy efficiency; 1 joule of energy is 1 watt during 1 second: 1 J = 1 W*s) W = watt (maximum ... Preisvorschlag senden - 4x GekkoScience Newpac 45-50GH/s Bitcoin USB Mining Set + Hub, 60W Netzteil. 2x Miner SHA256 ASIC USB Stick Block Erupter 333MH/s Mining Bitcoin BTC BCH. EUR 45,00 5T 11Std. Preisvorschlag senden - 2x Miner SHA256 ASIC USB Stick Block Erupter 333MH/s Mining Bitcoin BTC BCH. 6x TTBIT Scrypt Miner USB Hub Litecoin Mining Anlage kein Bitcoin Antminer. EUR 280,00 ... Die Bitcoin Mining Software überwacht diesen ständigen Input und Output der gesamten Miner, liefert Statistiken, die Geschwindigkeit des Miners, Hashrate, Temperatur und Lüftungsgeschwindigkeit. Welche Aufgaben übernimmt die Mining Software? Wallets. Eine der wichtigsten Dinge, um die man sich beim Mining kümmern sollte, sind abgesehen von der besten Hardware, das passende Wallet. Die ... Bitcoin mining software for ZTEX USB-FPGA Modules 1.15 . BTCMiner is an Open Source Bitcoin Miner for ZTEX USB-FPGA-Modules 1.15b and 1.15d and USB-FPGA-Modules 1.15x. The latter variant is optimized for cryptographic computations such as Bitcoin Mining and allows to build up FPGA clusters using standard components (USB cables and USB hubs). Ein nützliches Feature ist die Profit-Report-Funktion, da Sie mit dieser Funktion wissen, ob Ihr Mining profitabel ist oder nicht. Die neueste Version dieser Software ist Bitcoin Miner 1.27.0. BitMoose: Windows : Führen Sie Miners als Windows-Dienst aus. - BTCMiner: Windows : BTCMiner ist ein Open Source Bitcoin Miner für ZTEX USB-FPGA ...

[index] [29776] [19852] [26022] [10015] [824] [44149] [47425] [10029] [7970] [22482]

BitCoin Mining FPGA Card

SUBSCRIBE FOR MORE HOW MUCH - http://shorturl.at/arBHL GekkoScience NewPac USB Miner - https://bit.ly/2RIQgdX GekkoScience 8 Port USB Hub - https://bit.ly/2x... Safe USB version of the Gillian's Diamonds lamp. (With PCB file.) - Duration: 56:03. ... ELE 432- FPGA Bitcoin Miner - Duration: 4:08. Burak 14,472 views. 4:08. 8 x Xilinx VCU1525 FPGA Crypto ... Find this and more great products @ http://www.bitminingshop.com My friend purchased an FPGA Miner. Personally, I own a Butterfly Labs Single, if you do too ... Are USB Bitcoin Miners profitable right now? This video will show you all of the facts you need to know about usb bitcoin miners and how much money they actu... Lancelot FPGA Bitcoin Miner Unboxing Feel free to donate to keep more Tutorials coming: BTC:1Bv4XhVRZyNfBWuyFbqS8HwYwB3STJXdQA LTC:LWmXeH9Ur2xEbfoS8eiQJSxnra...

#