لم أستطع زيادة فقرة أخرى حول التعدين لأني على ما يبدو قد تجاوزت الحدود المسموحة من البيانات حاولت بما تبقى ربط الموضوع قليلا. لا أعلم إن كان يمكن تصنبف الموضوع تحت قسم التعدين لأن المواضيع المشابهة بالأنجليزية تندرج تحت القسم التقني. الأمر راجع إليك في قبول المشاركة من عدمها. المفيد المختصر في شرح الوحش المنتظرلقد تم قبولك موضوعك نظرا لانه متعلق بالتعدين بطريقة او باخرى. بالتوفيق لك تمت ارشفة جميع المواضيع في حوالي الساعة 20 Feb 2020 23:25:36 UTC لامانع من تعديل مواضيعكم كما ترون, ولكن اتمنى من الاعضاء الذين سيقومون بالتصويت ان يدخلو على المواضيع من خلال الروابط الموجودة في هدا الموضوع (المنشور الاصلي وليس المشاركات) سيتم قبول جميع الاصوات من الاعضاء الذين يمتلكون رتبة Member فما فوق ( يحق لي استبعاد الاصوات التي تاتي من اعضاء برتبة اقل من Full Member في حال كان هناك دليل على امتلاك العضو اكثر من حساب واستخدام الحسابين للتصويت). اتمنى من جميع الاعضاء التصويت حتى الذين شاركو (طبعا لايمكن التصويت لنفسك). نظرا لغياب بعض الاخوة هده الفترة, قررت اضافة مدة زمينة كافية للتصويت بحيث ان التصويت يبد الان وينتهي بتاريخ 1-3-2020 , اتمنى من الجميع التصويت, وبالتوفيق للجميع. |
|
|
|
I think the main reason Apple will lose money because of the decrease in demand for its products rather than the production itself, China is a major market and once they stop buying, Apple's value drops, look at crude oil prices, they dropped from $68 to $52 in no time, simply because China is the largest buyer for Crude oil, Apple's revenue in China was about 45 billion dollars last year alone, that's a big hit for them. As far as mining is concerned, I don't know about other companies, but Bitmain seems to be operating normally, I get replies to my emails normally, they shipped the s17+ control board faster than I thought, the slow in production and the long waiting periods might have been caused by the virus, but it has been this way since the last year-end, maybe not as bad as today, but most certainly nothing too strange. Bitmain should ship S17+ and T17+ next month, let's see how they do. Next Difficulty Change: between -0.2224% and -0.1906%
Previous Retarget: February 11, 2020 at 8:59 AM
Next Retarget (earliest): Tuesday at 9:53 AM (in 5d 7h 34m 42s)
Next Retarget (latest): Tuesday at 10:02 AM (in 5d 7h 43m 41s)
Projected Epoch Length: between 14d 0h 53m 32s and 14d 1h 2m 31s Price fell hard $10,170 to $9,290 in less than an hour, currently back at $9599. |
|
|
|
Bump for theymos  |
|
|
|
بكل تأكيد هدا التصرف غير اخلاقي ابدا, هل انت متأكد من انك تتحدث عن نفس الموقع ؟ على العموم لديهم حساب على المنتدى وموضوع خاص بالخدمة https://bitcointalk.org/index.php?topic=5182163.0 يمكنك مواجهته بتصرفه الغير اخلاقي في موضوعه, ربما لم يلاحظ ايميلك وقام شخص اخر بتحديره عبر المنتدى؟ |
|
|
|
على حد علمي هذه الخاصية لا تعمل مع العملات البديلة
في الواقع تقريبا 99% من كلامي في هدا المنتدى مخصص للبتكوين واحيانا انسى اصلا ان هناك عملات اخرى  . على العموم الموضوع يعتمد على تصميم العملة, فمثلا عملة ايثيريوم لا تقوم بتحويل القيمة بناء على UXTOs بحيث انه لا يمكنك انشاء عنوان جديد لكل عملية. مايحدث بطريقة مبسطة هوا الاتي: لديك 1 بتكوين في عنوانك tttt وتريد ارسال 0.5 بتكوين لصديقك على عنوانه ffff تقوم المحفظة بانشاء عنوان جديد nnnn وفي نفس ال transaction تقوم بارسال 0.5 بتكوين ل ffff و 0.5 لعنوانك الجديد nnnn , مما يعني انه بمجرد ان يصبح المفتاح العام لعنوانك tttt معروف, يكون رصيده قد اصبح 0, في الواقع هدا ليس "قرار" لان المحفظة مجبرة على ارسال ماهو موجود في tttt ولكن بدلا من ترسله 0.5 الى ffff والنص التاني الى tttt (نفس العنوان) تقوم بارساله الى العنوان الجديد nnnn ( الشرح يطول ولكن يكفي فهم النقطة كما هي). انا لا اعرف ان كانت محافظ الاثيريوم لديها بدائل لحل هده المشكلة , ولكن اعتقد ان الحل بسيط, بدلا من وجود Transaction واحد يمكن ان تتم العملية على التوالي بحيث تقوم بارسال المبلغ الى عنوان المستلم, وبعدها تقوم باجراء تحويل تاني منفصل لعنوان اخر, سيكون هناك فرق زمني في الارسال يمكن استغالاله لسرقة ماهو متبقي من في العنوان الاول, ولكن لا يمكنني التفكير في اي طريقة اخرى, ولكن انا شخص هاوي وافكاري محدودة وبكل تأكيد ان تلك العملات لديها البدائل والحلول, الموضوع يحتاج لبحث اكثر وبصراحة انا لست مهتما كتيرا بالعملات البديلة. |
|
|
|
Last I checked awesomeminer is also a vnish re-brand. At least the S9 version they advertised was.
You are right about this one, in fact, Patric from awesome miner himself confirmed that Of the 2% mining fee we are actually getting half of it. So we do benefit from customers that go for the Awesome Miner firmware. This is also the reason why we can provide product support for it and also integrate it well with Awesome Miner. Users of other Vnish firmware do get most of the features as well, so your point is valid that we do give away features to a larger user base. Some features like setting Mining Profiles via Awesome Miner is exclusive to our brand of the firmware. We could make more feature exclusive, but we are also trying to be nice to our customers and respect what decisions they make.
The dev fees on Vnish website are as follows Dev fee 1.6-1.9% only for S9/T9, 2.6- 2.9% for S17/T17 awesomeminer's fees for S9 is 2% or 3% (without consuming awesomeminer license), for S17/T17 the fee is 3%, so that's anywhere from 0.1% to 0.4% more for awesomeminer, if you use awesomeminer to monitor say, 100 miners, then you have to pay 700$ for the software, so one should do the math and see if the difference in fees is worth the license and the features that awesomeminer provide which Vnish doesn't. If it makes no economic sense, one might want to stick to Vnish, I personally use awesomeminer and I count on it big time to manage my gears, so I wouldn't mind paying a little extra, but that is just me, everyone should run the numbers. |
|
|
|
Phill, I have to agree to PassThePopcorn on this one, this without a doubt is Innosilicon Equihash A9++ ZMaster. Pay attention to the images below for comparsion. a9++  S9 Dual  There are a few difference in the way they look, but the most obvious one is the white sticker with the blue writing right next to the ethernet port, bitmain always use a sticker with a black background and white writing, only Inno uses white and blue. What is strange about the image that tmfp posted is in fact Jay Locke's image with his face hidden, Jay Locke is the founder of what's accused of being a Ponzi/MLM, called "goldmine369" and it's also based in UK!  I have no further information neither have I dug any deeper, but there is what looks like a solid scam accusation against the guy in the picture, you can read further here and here. This is nothing but a warning to tmfp to rethink his choices, I am not accusing goldmine369/Jay Locke for anything without having a rock solid proof.
The math: A9++ Zmaster is an Equihash based miner, it does not mine bitcoin, so you should not worry about bitcoin halving, the gear makes about 6$ a day after power at 10 cents Kwh , but keep in mind that is somehow a fresh alogthirm, the improvemt of the coming gears will differently kill the current once, it's nothing like Sha256 miners where we at 7nm already, and improvements are very little. I wouldn't advice anyone to buy these gears, but that's just me! |
|
|
|
There are probably a dozen out there, the only two that I would trust would be taserz aka Asic.to's firmware and awesomeminer firmware. Could there be any better than those two? well maybe, but the amount of fake and scam firmware we see every day stop me from vouching for any firmware which I have not tried/trust the developers behind it. Having said that, you should always be careful when attempting to overclock/boost your miner, you could easily toast it, stick to "auto-tuning" and/or refer to other user's outputs and what voltage and frequency they suggest. |
|
|
|
شكرا لك اخي ميكي على الشرح المميز وعلى مشاركة هذه التجربة معنا القيم المتاحة هي : 5$,10$,25$,50$ أعتقد أن سعرها ليس غالي والجميل فيها أن تقبل الدفع بالبيتكوين يعني البطاقة التي سعرها 5$ تعادل حوالي 0.0005$ وهو مبلغ بسيط اريد توضيح نقطة اخرى وهي ان قيمة البطاقة اقل بقليل من المبلغ الذي يتم دفعه، فمثلا بطاقة 50$ تدفع 52.23$ لتحصل عليها. مما يعني ان عمولة الموقع اكثر من 4% فيجب تجنب استخدامها الا عند الحاجة، والافضل هوا شراء ال gift cards للمواقع التي تتعامل بها لان سعرها اقل ، يعني مثلا amazon gift يمكن الحصول عليها بدفع 80-90% من قيمتها فقط. |
|
|
|
China is really coughing to death and I don't see anything going to hell!
How? with 2,000 deaths of coronavirus? more than that die from car accidents every month in the U.S alone, but even with that "$34 billion were wiped out of apple alone", oil prices feel from $68 to $52 as china imports the most crude oil in the world, everything has been affected by the small and silent half cough of china, china is a "global supply chain", look around your house and you will see china in every corner, if the virus is not contained and cured soon enough, things will get pretty ugly all over the globe. Let me break this down for you:
GDP PPP per capita: GDP per capita is not the same as GDP (PPP), you seem to have gotten things mixed up a bit, the example you used is PPP per capita which is pretty dependant on the population size, that's why you see Qatar is placed first but 51th in GDP (PPP). you should probably browse this website http://statisticstimes.com/index.php to get a better understanding of the differences, although this is really going off-topic. First, how do you get that 4,285,714 s9?
Money! And this is when economic strat to play their role, bitmain doesn't have that many chips and they need to also put an order on TSMC for that and if TSMC is busy, could it still be done? If its this huge order and must be done quickly just how much not are only prices going to spike, not even mentioning bribing a lot of guys to keep quiet? The king can have 10 countries and 1000 companies work for him to collect all the miners he needs, money buys everything, he can even buy mining farms in China or any other place. Could this be done in secrecy? No way!
So until you manage to manufacture that many miners build the infrastructure, ship and install them there is a lot of time to take some measures, and code is pretty faster than a cargo ship.
There is no need to keep this a secret, the King's country can simply say they are going to support bitcoin mining by holding a large mining farm if people find out, a dozen of mining gears get moved around, does anyone know where did the last million S9s go to and who bought them?? anyone who has both power and money can potentially and easily accumulate all the hashrate they need, in fact, the Chinese president now does "technically" have control over all the mining farms in China and can perform the attack if he wants, but you are suggesting that he probably wouldn't, therefore there is no risk? And anyway, there is nothing we could really do if someone is bent on spending billions or tens of billions attacking it!
There must be, it's to be or not to be, in 2041 BTC has to be worth nearly half a million dollars for the chain to be as secured against 51% as is today, if it's worth only 100k then it will be 80% less secure than it is now. I do believe in the role of economy, more people and businesses owning bitcoin gives it more value and more security as whoever uses it should at some point "invest" a portion of what they have to secure the network, I don't discard that role, but there is nothing wrong with planning for a technical-based solution rather than completely counting on the assumption that "nobody will perform a 51% because it's expensive or difficult". |
|
|
|
ملاحظة: عدل الصورة التي بها بيانات البطاقة في حال لا يزال فيها رصيد خاصة CVV. الارقام يمكن استنتاجها عند التركيز على الصورة.
أجل أخي خالد لقد فعلت ذالك هذا جاء إلى ذهني  من خلال التركيز في الصورة أكثر تستطيع تخمين الرقم الصحيح و إحدى هذه الأرقام سبعة لذا يجب الإنتباه أكثر من الأخ مايكي حتى لا نسمع ما لا نحبه. و أشكر الأخ أيضا على الشرح المفيد بحيث يمكن إستغلال الخدمة للحصول على كارد فيزا إفتراضية و توضيفه لتسوق أو دفع تمويل . خصوصا إذا كان المستخدم لا يتوفر على حساب بنكي أو البلد لا يدعم الخدمة. من يسطتيع استنتاج او تخمين الارقام حلال عليه ماتبقى من رصيد في البطاقة , وله ايضا جائزة 30$ بتكوين يتم تحويلها مباشرة الى محفظته  على اي حال شكرا على الملاحظة اخ خالد واخ Ulven |
|
|
|
Recently, Mickeywith suggested in Chipmixer that it is impossible to change boards
As you can see Mickeywith suggested that it will be impossible for someone to start posting in the mining without noticing and I wanted to prove him wrong because You misspelled my username twice  . Anyway, I would like to see you quote the post where I wrote "it is impossible to change boards" or "will be impossible for someone to start posting in the mining without noticing". I don't think you are making that up, I would love to believe that it's simply a misunderstanding due to linguistic barriers, I have literally said It is either you are good at something or you are not, you cannot force yourself to post in boards you are not comfortable with just to be accepted if you know what mining is and enjoy it, but for some reason, you have not been posting there, and out of a sudden for whatever reason, you start to be active in the mining board, that is completely fine, as long as you have the knowledge needed as well as the desire to actually post there. If you don't have both, it will be so obvious that you are in for financial gains, the mining board was just an example, I was not accusing you or anyone else of skewing, it was an advice to everyone who is willing to actually post in boards they know nothing about just to get accepted in X signature campaign. If I learn Chinese and start to post there regardless of the fact that I have probably never posted there, I see nothing wrong with that, but if I use google translation to post in Chinese Local Board just to get accepted in Jihan Wu's signature campaign then that is terrible. You really shouldn't even try to prove me wrong, because I was not challenging you, I was only trying to help you! Having said that, I don't agree to the deletion of your posts, as far as I see, they are mining-related and are not off-topic (unless I am missing something), however, anyone who knows the mining board knows that frodocooper is pretty strict, probably the most strict moderator around, I myself get some of my posts deleted, I do get angry sometimes, but if I ' hypothetically' was the one who decides on keeping or removing him from the mining board, I will most certainly keep him as a moderator, he does a tremendous amount of quality work to the mining board, a few mistakes here and there do not wipe the efforts he puts and the work he does. |
|
|
|
موضوع اكثر من رائع بكل صراحة, المشكلة الوحيدة هوا انك لم تقم بربط ثقنية الكوانتوم بالتعدين ( بحكم ان الموضوع موجود في قسم التعدين) في الواقع الموضوع يحتاج لربط بالبتكوين بالمجمل, يوجد ورقة بحث اكثر من رائعة اتمنى ان تقرائها https://arxiv.org/ftp/arxiv/papers/1711/1711.04235.pdf وان تستفيد منها لاضافة نوع من العلاقة مابين البتكوين , تعدين البتكوين والكوانتوم. ملخص ماجاء في البحث هوا -الكوانتوم كومبيوتر بطبيعته ليس منافس قوي لاجهزة تعدين ASIC لاسباب ثقنية فهوا ليس مصمم لمثل هده المسائل -الخطر الحقيقي يمكن في قوة الكوانتوم في استخدام Shor's algorithm كما قمت حضرتك بشرحه لفك elliptic curve digital signature algorithm (ECDSA) المستعملة في تشفير المفتاح العام والخاص ( Public key and private key encryption ) والبتكوين نوعا ما "محصنة" من مثل هدا الهجوم لان ال Public Key لايمكنك معرفته من معرفة ال Address الا بعد القيام بعملية ارسال من العنوان, وهدا السبب الذي يجعل معظم المحافظ تقوم باعطائك عنوان جديد فور استخدامك للعنوان الاول وتقوم بنقل ماتبقى من العنوان الاول للعنوان جديد في نفس الوقت الذي تقوم فيه بارسال ماتريد انت ارساله, مما يعني انه وبمجرد ان تصبح ال Public Key الخاصة بك معروفة ويمكنك مهاجمتها سيتكون رصيدك من البتكوين قد ثم نقله لعنوان جديد احد يعرف ال Public Key الخاص به. يوجد مبالغة كبيرة في مدى خطورة الكوانتوم على التشفير بصفة عامة, مايجهله الكثرين ان هده الثقنية هي في الاصل خطر على انظمة الدول العظمى واستخبارتها وامنها القوي, لذلك قبل وصول هده الثقنية للعلن ستكون تلك الحكومات قد قامت باستخدام اجهزة كوانتوم نفسها لانشاء لوغورتمات تشفير تفوق قدرة الكوانتوم لفكها, تمام كما حصل مع اجهزة الحاسوب التي نسخدمها الان, في الماضي كان التشفير بالورقة والقلم, وبمجرد انتشار تقنية الحاسوب قامو باستخدامه لانشاء تشفيرات لاتزال حتى الان مصتعصية, نفس الشي سيحدث مع الكوانتوم ولا داعي للقلك من وجهة نظري المتواضعة. شكرا جدا على هدا الموضوع الاكثر من رائع |
|
|
|
تحديث مهم بتاريخ 10-7-2021 لقد قمت بالاستفسار من كونزبيي و لقد أكدو أنهم ان يقومو بتعبئة المخزون من الان فصاعدا (بسبب المشاكل التي واجهها الكثير من المستخدمين) لذلك، أعتقد أنه سوف يكون من الجيد ان قمت بغلق الموضوع أو تعديله على الأقل.
بناء على هده المعلومة من الاخ اوميقا سوف اقوم باغلاق الموضوع. تحديث مهم بتاريخ 4-12-2020: ملاحظة بسيطة بالنسبة للاخوة الذين مازالو يستخدمون هذه البطاقات... https://www.trustpilot.com/review/www.prepaiddigitalsolutions.comكما ترون في الرابط أعلاه، لقد ظهرت في الاونة الاخيرة الكثير من الشكاوي حول الموقع الذي يقوم باصدار البطاقات لذلك أرجو من الجميع توخي الحذر و عدم شراء بطاقات ذات فئة كبيرة الا في حال تأكدك من أن الموقع سوف يقبل البطاقة. لقد قام الموقع باضافة ال KYC... يعني أنه بمجرد وصول مجموع قيمة مشترياتك الى 15,000 أورو، سوف يتوجب عليك اثبات هويتك. بعد الاطلاع على تعليق الاخ OmegaStarScream عن شراء البطاقات الافتراضية من موقع www.coinsbee.com قررت تجربته. اولا نقوم بالدخول على رابط الشراء https://www.coinsbee.com/en/shop , قمت باضافة فلتر للنتائج حتى تظهر لي البطاقات بالدولار الامريكي فقط كما هوا موضع في الصورة  القيم المتاحة بالدولار: : 5, 10 , 200 ( فيزا كارد) القيم المتاحة باليورو: 5, 10 , 100 ( ماسترد كارد) تقوم باختيار ماتريده بالضغط على Add to cart وتم تختار Go to shopping cart  تقوم بعدها بمراجعتك مشترياتك وتقوم بالظغط على Checkout للذهاب لواجهة الدفع حيث يطلب منك كتابة الايميل الذي ستتستلم عليه الكود, بعد كتابة الايميل والموافقة على الشروط تقوم بالظغط على Buy Now  تظهر لك خيارات الدفع المتاحة, وانا قمت بالدفع عن طريق شبكة البرق الخاصة بالبتكوين Bitcoin Lightening Network باستخدام محفظة BlueWallet , تقوم بكتابة ايمليلك مجددا وتظغط على pay تقوم بنسخ رقم الفاتورة او باستعمال كاميرة الموبايل يمكنك قراءة ال QR code والقيام بالدفع, ويكون الاستلام فوري عند استخدامك لي شبكة البرق على عكس استخدام اي طريقة اخرى سيطلك ايميل من Coingate وهي بوابة الدفع التي يستخدمها موقع Coinsbee  وبعدها يصلك ايميل من موقع Coinsbee نفسه يحتوي على "كود" بناء على ماجاء في الموقع العملية قد تأخد من 5 الى 15 دقيقة في العادة , بناء على تجربي اخدت 4 دقائق ملاحظة مهمة: الايميل وصلني على Spam ربما يحدث معك نفس الشي  قم بنسخ الكود وادخل على هدا الرابط https://www.prepaiddigitalsolutions.com/ كما هوا مبين في الشرح من موقع Coinsbee  عند كتابة الكود ستظهر لك قائمة لكتابة اسمك , بلدك, عنوانك, رقم الهاتف, والايميل. ومن ثم يتم اصدار بطاقة افتراضية لك بهدا الشكل  للاطلاع على رصيدك او تغير بياناتك لاحقا يمكنك تكرار نفس العملية بالدخول على www.prepaiddigitalsolutions.com ومن ثم تدخل الكود وبدل ان تظهر لك قائمة تطلب بياناتك مجددا ستظهر لك بيانات بطاقاتك مثل ماوجد في اخر صورة. قمت بتجربة البطاقة الافتراضية لشراء Domain وتمث العملية بنجاح ! طبعا للاسف هده البطاقة لاتعمل في كل المواقع فمثلا الاعلانات الممولة على فيسبوك لاتقبل الدفع بالببطاقات الافتراضية, اتذكر ايضا ان موقع اخر رفض مثل هده البطاقة ولكن نسيت اسم الموقع, لذلك يجب عليك التأكد ان الموقع الذي تريد الشراء منه لا يرفض الابطاقات الافتراضية, اعتقد ان اغلب المواقع لاتمنع استخدام البطاقات الافتراضية. BlueWallet: يمكن القراءة عنها اكثر وفهم كيفية استعمالها بعد قراءة هدا الموضوع للاخ yhiaali3. |
|
|
|
having a mix of s9s I have to say if you can get s9i they are the best. I have one at stock and it does 15th
I think you don't have S9j then, because based on my own experience and almost everyone else whom i asked, the J series seem to have the finest chips among all it's other S9 rivals, i have not personally checked the power consumption but i heard they do slightly better too. Having said that, the difference is really very minor between the S9i and the S9j , it gets wider when compared to the normal S9 and ofcourse a lot better when compared to the S9k, the latter is the worst gear bitmain has ever made. |
|
|
|
Odd...
So if everyone is close to 1 point per 100$ spent, why am I closer to 0.5 per 100$ spent.
I will contact them to ask about that, and I'll try to extract all the info about those points from their customer support.
Your points are pretty confusing to be honest, i asked one of the resllers whom i trust, he got about 800 points for an order of $80,000 , so pretty much close to 0.01 points per dollar, or 1 point to $100. I guess maybe you have some orders placed on the 29th itself, that day might not count towards the final points as it says "after 29". |
|
|
|
Well, if all recommendation doesn't work I think the issue still under their firmware which is a common issue on s9k miner. Read this " WANRNING! Do Not Buy Antminer S9k" Well, if only he read the topic before purchasing  The stock firmware has a lot of issues in regards to reading the temperature of the chips, it has "supposedly" fixed in the later version/s, however, these S9ks suck by default, my S9ks keep losing a board every now and then, sometimes they reboot a few times a day for really no obvious reason, I have actually got to the point where I don't bother with them anymore, I have talked to Taserz and Patrick (Awesome Miner) about a firmware for the S9k, hoping that their firmware will fix these issues, but the of them did not promise me anything yet. if you are certain the problem you have is temperature related, you can simply do one of the following or both. 1-Set all fans to 90%. 2-Turn the other S9s off to reduce the room temperature. if the problem goes away, then you need to improve your ventilation system, if it does not, then try to return them to Bitmain while you still can. |
|
|
|
EDIT: Oh yeah, I forgot to mention that I have 28 points and since Oct 29.2019. I have spent around 4700 USD (w/o shipping) on their website.
I have been trying to crack this point system, or at least how are they calculated, so far no luck, I got 67 points and total purchase since Oct 30.2019 is $6372 without shipping and $6845 with shipping, I have used coupons on all of those orders. 67 points for 6372 = 0.01 points for every dollar yours is 28 / 4700 = 0.0059 points for every dollar That way of calculation does not make any sense, I will try to collect more data in order to come with a better understanding of how were those points distributed, would appreciate other people's inputs, the larger the sample the more accurate the results, I hope it has nothing to do with the type of gear you bought because that will be a lot more difficult to figure out. |
|
|
|
Continuation (exceeded maximum length) reopen chain 1, current pwm 90
2020-02-17 18:32:52 power.c:779:set_iic_power_to_highest_voltage_by_chain: chain[1] setting to hightest voltage: 10.04 ...
2020-02-17 18:32:52 power.c:705:set_iic_power_by_voltage: now setting voltage to : 10.044000
2020-02-17 18:32:52 asic.c:1176:set_baud_by_chain: chain 1 set baud=26
2020-02-17 18:32:53 driver-btm-soc.c:6358:bring_up_chain:
bring up chain 1
2020-02-17 18:32:53 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffa
2020-02-17 18:32:54 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-02-17 18:32:55 driver-btm-soc.c:3991:check_asic_num: without pre_open_core chain 1, find asic num = 60
2020-02-17 18:32:58 driver-btm-soc.c:4804:set_freq_by_chain: chain[1] set freq:100.00
2020-02-17 18:32:59 driver-btm-soc.c:3917:pre_open_core_one_chain: for chain 1
2020-02-17 18:32:59 driver-btm-soc.c:4078:set_clock_delay_control: core_data = 0x06
2020-02-17 18:32:59 temperature.c:604:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
2020-02-17 18:32:59 temperature.c:791:calibration_sensor_offset: Chain[1] chip[31] middle temp offset=-4, typeID=55
2020-02-17 18:33:00 temperature.c:791:calibration_sensor_offset: Chain[1] chip[40] middle temp offset=-4, typeID=55
2020-02-17 18:33:00 asic.c:1176:set_baud_by_chain: chain 1 set baud=1
2020-02-17 18:33:00 asic.c:1269:set_asic_ticket_mask: set ticket mask 63
2020-02-17 18:33:00 driver-btm-soc.c:4148:open_core_bm1393: Start Open Core!!
2020-02-17 18:33:03 driver-btm-soc.c:4215:open_core_bm1393: End Open Core!!
2020-02-17 18:33:03 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 125
2020-02-17 18:33:04 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 150
2020-02-17 18:33:05 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 175
2020-02-17 18:33:06 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 200
2020-02-17 18:33:07 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 225
2020-02-17 18:33:08 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 250
2020-02-17 18:33:09 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 275
2020-02-17 18:33:10 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 300
2020-02-17 18:33:11 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 325
2020-02-17 18:33:12 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 350
2020-02-17 18:33:13 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 375
2020-02-17 18:33:14 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 380
2020-02-17 18:33:15 driver-btm-soc.c:5365:increase_freq_by_eeprom_slowly_by_chain: max = 435 ,min = 380
2020-02-17 18:33:15 driver-btm-soc.c:5371:increase_freq_by_eeprom_slowly_by_chain: chain[1] increaseing the diff freq ...
2020-02-17 18:33:26 driver-btm-soc.c:5400:increase_freq_by_eeprom_slowly_by_chain: chain 1 final freq setting:
435 435 435 435 435 435 420 380 420 410
380 420 420 435 435 410 435 435 435 435
435 435 435 435 435 435 420 420 410 380
380 410 420 420 435 435 435 435 435 435
410 435 435 435 435 420 435 435 420 380
380 410 420 420 435 435 435 435 435 435
2020-02-17 18:33:26 driver-btm-soc.c:5100:set_timeout: freq 440 final timeout=297
2020-02-17 18:33:27 driver-btm-soc.c:6987:re_open_core_by_chain: reopen chain 1 finished, chain 1 chip temp 45 - 60
2020-02-17 18:33:27 driver-btm-soc.c:6988:re_open_core_by_chain: all chain chip temp 42 - 69
2020-02-17 18:33:27 driver-btm-soc.c:7004:re_open_core_by_chain: re_open_core done!
2020-02-17 18:33:57 driver-btm-soc.c:6960:re_open_core_by_chain:
reopen chain 2, current pwm 90
2020-02-17 18:34:00 power.c:779:set_iic_power_to_highest_voltage_by_chain: chain[2] setting to hightest voltage: 10.04 ...
2020-02-17 18:34:02 power.c:705:set_iic_power_by_voltage: now setting voltage to : 10.044000
2020-02-17 18:34:02 asic.c:1176:set_baud_by_chain: chain 2 set baud=26
2020-02-17 18:34:02 driver-btm-soc.c:6358:bring_up_chain:
bring up chain 2
2020-02-17 18:34:02 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-02-17 18:34:03 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-02-17 18:34:05 driver-btm-soc.c:3991:check_asic_num: without pre_open_core chain 2, find asic num = 60
2020-02-17 18:34:08 driver-btm-soc.c:4804:set_freq_by_chain: chain[2] set freq:100.00
2020-02-17 18:34:09 driver-btm-soc.c:3917:pre_open_core_one_chain: for chain 2
2020-02-17 18:34:09 driver-btm-soc.c:4078:set_clock_delay_control: core_data = 0x06
2020-02-17 18:34:09 temperature.c:604:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
2020-02-17 18:34:09 temperature.c:791:calibration_sensor_offset: Chain[2] chip[31] middle temp offset=-4, typeID=55
2020-02-17 18:34:10 temperature.c:791:calibration_sensor_offset: Chain[2] chip[40] middle temp offset=-3, typeID=55
2020-02-17 18:34:10 asic.c:1176:set_baud_by_chain: chain 2 set baud=1
2020-02-17 18:34:10 asic.c:1269:set_asic_ticket_mask: set ticket mask 63
2020-02-17 18:34:10 driver-btm-soc.c:4148:open_core_bm1393: Start Open Core!!
2020-02-17 18:34:12 driver-btm-soc.c:4215:open_core_bm1393: End Open Core!!
2020-02-17 18:34:12 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 125
2020-02-17 18:34:13 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 150
2020-02-17 18:34:14 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 175
2020-02-17 18:34:15 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 200
2020-02-17 18:34:16 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 225
2020-02-17 18:34:17 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 250
2020-02-17 18:34:19 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 275
2020-02-17 18:34:20 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 300
2020-02-17 18:34:21 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 325
2020-02-17 18:34:22 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 350
2020-02-17 18:34:23 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 375
2020-02-17 18:34:24 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 400
2020-02-17 18:34:25 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 425
2020-02-17 18:34:26 driver-btm-soc.c:5365:increase_freq_by_eeprom_slowly_by_chain: max = 440 ,min = 425
2020-02-17 18:34:26 driver-btm-soc.c:5371:increase_freq_by_eeprom_slowly_by_chain: chain[2] increaseing the diff freq ...
2020-02-17 18:34:29 driver-btm-soc.c:5400:increase_freq_by_eeprom_slowly_by_chain: chain 2 final freq setting:
440 440 440 440 440 440 440 440 440 425
425 440 440 440 440 440 440 440 440 440
440 440 440 440 440 440 440 440 440 425
425 440 440 440 440 440 440 440 440 440
440 440 440 440 440 440 440 440 440 425
425 440 440 440 440 440 440 440 440 440
2020-02-17 18:34:29 driver-btm-soc.c:5100:set_timeout: freq 440 final timeout=297
2020-02-17 18:34:30 driver-btm-soc.c:6987:re_open_core_by_chain: reopen chain 2 finished, chain 2 chip temp 41 - 54
2020-02-17 18:34:30 driver-btm-soc.c:6988:re_open_core_by_chain: all chain chip temp 41 - 71
2020-02-17 18:34:30 driver-btm-soc.c:7004:re_open_core_by_chain: re_open_core done!
2020-02-17 18:35:00 power.c:269:set_higher_voltage_by_chain: chain[0] higher_voltage = 9.700001
2020-02-17 18:35:00 power.c:269:set_higher_voltage_by_chain: chain[1] higher_voltage = 9.700001
2020-02-17 18:35:00 power.c:269:set_higher_voltage_by_chain: chain[2] higher_voltage = 9.700001
2020-02-17 18:35:00 power.c:1253:slowly_set_iic_power_voltage_t11: parallel set all chain to working voltage:
now setting chain[0]-volt[10.04]-data[014] chain[1]-volt[10.04]-data[014] chain[2]-volt[10.04]-data[014]
now setting chain[0]-volt[09.99]-data[015] chain[1]-volt[09.99]-data[015] chain[2]-volt[09.99]-data[015]
now setting chain[0]-volt[09.94]-data[016] chain[1]-volt[09.94]-data[016] chain[2]-volt[09.94]-data[016]
now setting chain[0]-volt[09.89]-data[017] chain[1]-volt[09.89]-data[017] chain[2]-volt[09.89]-data[017]
now setting chain[0]-volt[09.85]-data[018] chain[1]-volt[09.85]-data[018] chain[2]-volt[09.85]-data[018]
now setting chain[0]-volt[09.76]-data[020] chain[1]-volt[09.76]-data[020] chain[2]-volt[09.76]-data[020]
now setting chain[0]-volt[09.72]-data[021] chain[1]-volt[09.72]-data[021] chain[2]-volt[09.72]-data[021]
2020-02-17 18:35:17 power.c:1273:slowly_set_iic_power_voltage_t11: parallel set all chain to working voltage end!
now setting chain[0]-volt[09.72]-data[021] chain[1]-volt[09.72]-data[021] chain[2]-volt[09.72]-data[021]
2020-02-17 18:35:17 hash_rate.c:58:clear_queue: reset calc...
2020-02-17 18:35:17 driver-btm-soc.c:3786:check_system_work: low temperature re_open_core [1] times,DONE!
2020-02-17 18:40:21 driver-btm-soc.c:3711:check_system_work: bring_up_pcb_temp = 18, low_bringup_pcb_temp_threshhold = 28
2020-02-17 18:40:21 driver-btm-soc.c:3712:check_system_work: detecting at 20 minutes
2020-02-17 18:40:21 driver-btm-soc.c:3713:check_system_work: target hash rate = 15840, 5mins avg hash rate = 15663
2020-02-17 18:40:21 driver-btm-soc.c:3734:check_system_work: low temp bing up:[Yes]
2020-02-17 18:40:21 driver-btm-soc.c:3735:check_system_work: low temp running:[No]
2020-02-17 18:40:21 driver-btm-soc.c:3738:check_system_work: Temp Low! Entering Low Environment Handler...
2020-02-17 18:40:21 driver-btm-soc.c:3026:get_compensation_voltage: last_testpatten_lowest_pcb_temp = 20
2020-02-17 18:40:21 driver-btm-soc.c:3027:get_compensation_voltage: max_delta_vol = 0.10
2020-02-17 18:40:21 driver-btm-soc.c:3173:get_compensation_voltage: add extra 0.1V for low temp handler!
2020-02-17 18:40:21 driver-btm-soc.c:3190:get_compensation_voltage: chain[0] working vol = 9.60, add vol = 0.20...
2020-02-17 18:40:21 driver-btm-soc.c:3190:get_compensation_voltage: chain[1] working vol = 9.60, add vol = 0.20...
2020-02-17 18:40:21 driver-btm-soc.c:3190:get_compensation_voltage: chain[2] working vol = 9.60, add vol = 0.20...
2020-02-17 18:40:21 driver-btm-soc.c:6960:re_open_core_by_chain:
reopen chain 0, current pwm 90
2020-02-17 18:40:23 power.c:779:set_iic_power_to_highest_voltage_by_chain: chain[0] setting to hightest voltage: 10.04 ...
2020-02-17 18:40:24 power.c:705:set_iic_power_by_voltage: now setting voltage to : 10.044000
2020-02-17 18:40:24 asic.c:1176:set_baud_by_chain: chain 0 set baud=26
2020-02-17 18:40:24 driver-btm-soc.c:6358:bring_up_chain:
bring up chain 0
2020-02-17 18:40:24 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff9
2020-02-17 18:40:25 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-02-17 18:40:27 driver-btm-soc.c:3991:check_asic_num: without pre_open_core chain 0, find asic num = 60
2020-02-17 18:40:30 driver-btm-soc.c:4804:set_freq_by_chain: chain[0] set freq:100.00
2020-02-17 18:40:31 driver-btm-soc.c:3917:pre_open_core_one_chain: for chain 0
2020-02-17 18:40:31 driver-btm-soc.c:4078:set_clock_delay_control: core_data = 0x06
2020-02-17 18:40:31 temperature.c:604:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
2020-02-17 18:40:31 temperature.c:791:calibration_sensor_offset: Chain[0] chip[31] middle temp offset=-4, typeID=55
2020-02-17 18:40:32 temperature.c:791:calibration_sensor_offset: Chain[0] chip[40] middle temp offset=-4, typeID=55
2020-02-17 18:40:32 asic.c:1176:set_baud_by_chain: chain 0 set baud=1
2020-02-17 18:40:32 asic.c:1269:set_asic_ticket_mask: set ticket mask 63
2020-02-17 18:40:32 driver-btm-soc.c:4148:open_core_bm1393: Start Open Core!!
2020-02-17 18:40:34 driver-btm-soc.c:4215:open_core_bm1393: End Open Core!!
2020-02-17 18:40:34 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 125
2020-02-17 18:40:35 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 150
2020-02-17 18:40:36 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 175
2020-02-17 18:40:37 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 200
2020-02-17 18:40:38 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 225
2020-02-17 18:40:39 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 250
2020-02-17 18:40:41 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 275
2020-02-17 18:40:42 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 300
2020-02-17 18:40:43 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 325
2020-02-17 18:40:44 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 350
2020-02-17 18:40:45 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 375
2020-02-17 18:40:46 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 400
2020-02-17 18:40:47 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 410
2020-02-17 18:40:48 driver-btm-soc.c:5365:increase_freq_by_eeprom_slowly_by_chain: max = 435 ,min = 410
2020-02-17 18:40:48 driver-btm-soc.c:5371:increase_freq_by_eeprom_slowly_by_chain: chain[0] increaseing the diff freq ...
2020-02-17 18:40:51 driver-btm-soc.c:5400:increase_freq_by_eeprom_slowly_by_chain: chain 0 final freq setting:
435 435 435 435 435 435 435 435 420 410
410 435 435 420 435 435 435 435 435 435
435 435 435 435 435 435 435 435 420 410
410 420 435 435 435 435 435 435 435 435
435 435 435 435 435 435 435 435 420 410
410 420 435 435 435 435 435 435 435 435
2020-02-17 18:40:51 driver-btm-soc.c:5100:set_timeout: freq 440 final timeout=297
2020-02-17 18:40:52 driver-btm-soc.c:6987:re_open_core_by_chain: reopen chain 0 finished, chain 0 chip temp 42 - 61
2020-02-17 18:40:52 driver-btm-soc.c:6988:re_open_core_by_chain: all chain chip temp 42 - 65
2020-02-17 18:40:52 driver-btm-soc.c:7004:re_open_core_by_chain: re_open_core done!
2020-02-17 18:41:22 driver-btm-soc.c:6960:re_open_core_by_chain:
reopen chain 1, current pwm 90
2020-02-17 18:41:25 power.c:779:set_iic_power_to_highest_voltage_by_chain: chain[1] setting to hightest voltage: 10.04 ...
2020-02-17 18:41:26 power.c:705:set_iic_power_by_voltage: now setting voltage to : 10.044000
2020-02-17 18:41:26 asic.c:1176:set_baud_by_chain: chain 1 set baud=26
2020-02-17 18:41:26 driver-btm-soc.c:6358:bring_up_chain:
bring up chain 1
2020-02-17 18:41:26 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffa
2020-02-17 18:41:27 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-02-17 18:41:29 driver-btm-soc.c:3991:check_asic_num: without pre_open_core chain 1, find asic num = 60
2020-02-17 18:41:32 driver-btm-soc.c:4804:set_freq_by_chain: chain[1] set freq:100.00
2020-02-17 18:41:33 driver-btm-soc.c:3917:pre_open_core_one_chain: for chain 1
2020-02-17 18:41:33 driver-btm-soc.c:4078:set_clock_delay_control: core_data = 0x06
2020-02-17 18:41:33 temperature.c:604:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
2020-02-17 18:41:33 temperature.c:791:calibration_sensor_offset: Chain[1] chip[31] middle temp offset=-4, typeID=55
2020-02-17 18:41:34 temperature.c:791:calibration_sensor_offset: Chain[1] chip[40] middle temp offset=-4, typeID=55
2020-02-17 18:41:34 asic.c:1176:set_baud_by_chain: chain 1 set baud=1
2020-02-17 18:41:34 asic.c:1269:set_asic_ticket_mask: set ticket mask 63
2020-02-17 18:41:34 driver-btm-soc.c:4148:open_core_bm1393: Start Open Core!!
2020-02-17 18:41:36 driver-btm-soc.c:4215:open_core_bm1393: End Open Core!!
2020-02-17 18:41:36 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 125
2020-02-17 18:41:37 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 150
2020-02-17 18:41:38 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 175
2020-02-17 18:41:39 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 200
2020-02-17 18:41:40 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 225
2020-02-17 18:41:42 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 250
2020-02-17 18:41:43 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 275
2020-02-17 18:41:44 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 300
2020-02-17 18:41:45 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 325
2020-02-17 18:41:46 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 350
2020-02-17 18:41:47 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 375
2020-02-17 18:41:48 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 380
2020-02-17 18:41:49 driver-btm-soc.c:5365:increase_freq_by_eeprom_slowly_by_chain: max = 435 ,min = 380
2020-02-17 18:41:49 driver-btm-soc.c:5371:increase_freq_by_eeprom_slowly_by_chain: chain[1] increaseing the diff freq ...
2020-02-17 18:41:59 driver-btm-soc.c:5400:increase_freq_by_eeprom_slowly_by_chain: chain 1 final freq setting:
435 435 435 435 435 435 420 380 420 410
380 420 420 435 435 410 435 435 435 435
435 435 435 435 435 435 420 420 410 380
380 410 420 420 435 435 435 435 435 435
410 435 435 435 435 420 435 435 420 380
380 410 420 420 435 435 435 435 435 435
2020-02-17 18:42:00 driver-btm-soc.c:5100:set_timeout: freq 440 final timeout=297
2020-02-17 18:42:01 driver-btm-soc.c:6987:re_open_core_by_chain: reopen chain 1 finished, chain 1 chip temp 46 - 61
2020-02-17 18:42:01 driver-btm-soc.c:6988:re_open_core_by_chain: all chain chip temp 43 - 70
2020-02-17 18:42:01 driver-btm-soc.c:7004:re_open_core_by_chain: re_open_core done!
2020-02-17 18:42:31 driver-btm-soc.c:6960:re_open_core_by_chain:
reopen chain 2, current pwm 90
2020-02-17 18:42:33 power.c:779:set_iic_power_to_highest_voltage_by_chain: chain[2] setting to hightest voltage: 10.04 ...
2020-02-17 18:42:34 power.c:705:set_iic_power_by_voltage: now setting voltage to : 10.044000
2020-02-17 18:42:34 asic.c:1176:set_baud_by_chain: chain 2 set baud=26
2020-02-17 18:42:34 driver-btm-soc.c:6358:bring_up_chain:
bring up chain 2
2020-02-17 18:42:34 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-02-17 18:42:35 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-02-17 18:42:37 driver-btm-soc.c:3991:check_asic_num: without pre_open_core chain 2, find asic num = 60
2020-02-17 18:42:40 driver-btm-soc.c:4804:set_freq_by_chain: chain[2] set freq:100.00
2020-02-17 18:42:41 driver-btm-soc.c:3917:pre_open_core_one_chain: for chain 2
2020-02-17 18:42:41 driver-btm-soc.c:4078:set_clock_delay_control: core_data = 0x06
2020-02-17 18:42:41 temperature.c:604:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
2020-02-17 18:42:41 temperature.c:791:calibration_sensor_offset: Chain[2] chip[31] middle temp offset=-4, typeID=55
2020-02-17 18:42:42 temperature.c:791:calibration_sensor_offset: Chain[2] chip[40] middle temp offset=-3, typeID=55
2020-02-17 18:42:42 asic.c:1176:set_baud_by_chain: chain 2 set baud=1
2020-02-17 18:42:42 asic.c:1269:set_asic_ticket_mask: set ticket mask 63
2020-02-17 18:42:42 driver-btm-soc.c:4148:open_core_bm1393: Start Open Core!!
2020-02-17 18:42:44 driver-btm-soc.c:4215:open_core_bm1393: End Open Core!!
2020-02-17 18:42:44 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 125
2020-02-17 18:42:46 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 150
2020-02-17 18:42:47 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 175
2020-02-17 18:42:48 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 200
2020-02-17 18:42:49 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 225
2020-02-17 18:42:50 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 250
2020-02-17 18:42:51 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 275
2020-02-17 18:42:52 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 300
2020-02-17 18:42:53 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 325
2020-02-17 18:42:54 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 350
2020-02-17 18:42:55 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 375
2020-02-17 18:42:56 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 400
2020-02-17 18:42:57 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 425
2020-02-17 18:42:58 driver-btm-soc.c:5365:increase_freq_by_eeprom_slowly_by_chain: max = 440 ,min = 425
2020-02-17 18:42:58 driver-btm-soc.c:5371:increase_freq_by_eeprom_slowly_by_chain: chain[2] increaseing the diff freq ...
2020-02-17 18:43:02 driver-btm-soc.c:5400:increase_freq_by_eeprom_slowly_by_chain: chain 2 final freq setting:
440 440 440 440 440 440 440 440 440 425
425 440 440 440 440 440 440 440 440 440
440 440 440 440 440 440 440 440 440 425
425 440 440 440 440 440 440 440 440 440
440 440 440 440 440 440 440 440 440 425
425 440 440 440 440 440 440 440 440 440
2020-02-17 18:43:02 driver-btm-soc.c:5100:set_timeout: freq 440 final timeout=297
2020-02-17 18:43:03 driver-btm-soc.c:6987:re_open_core_by_chain: reopen chain 2 finished, chain 2 chip temp 41 - 55
2020-02-17 18:43:03 driver-btm-soc.c:6988:re_open_core_by_chain: all chain chip temp 41 - 71
2020-02-17 18:43:03 driver-btm-soc.c:7004:re_open_core_by_chain: re_open_core done!
2020-02-17 18:43:33 power.c:269:set_higher_voltage_by_chain: chain[0] higher_voltage = 9.800000
2020-02-17 18:43:33 power.c:269:set_higher_voltage_by_chain: chain[1] higher_voltage = 9.800000
2020-02-17 18:43:33 power.c:269:set_higher_voltage_by_chain: chain[2] higher_voltage = 9.800000
2020-02-17 18:43:33 power.c:1253:slowly_set_iic_power_voltage_t11: parallel set all chain to working voltage:
now setting chain[0]-volt[10.04]-data[014] chain[1]-volt[10.04]-data[014] chain[2]-volt[10.04]-data[014]
now setting chain[0]-volt[09.99]-data[015] chain[1]-volt[09.99]-data[015] chain[2]-volt[09.99]-data[015]
now setting chain[0]-volt[09.94]-data[016] chain[1]-volt[09.94]-data[016] chain[2]-volt[09.94]-data[016]
now setting chain[0]-volt[09.89]-data[017] chain[1]-volt[09.89]-data[017] chain[2]-volt[09.89]-data[017]
now setting chain[0]-volt[09.85]-data[018] chain[1]-volt[09.85]-data[018] chain[2]-volt[09.85]-data[018]
now setting chain[0]-volt[09.80]-data[019] chain[1]-volt[09.80]-data[019] chain[2]-volt[09.80]-data[019]
2020-02-17 18:43:47 power.c:1273:slowly_set_iic_power_voltage_t11: parallel set all chain to working voltage end!
now setting chain[0]-volt[09.80]-data[019] chain[1]-volt[09.80]-data[019] chain[2]-volt[09.80]-data[019]
2020-02-17 18:43:47 hash_rate.c:58:clear_queue: reset calc...
2020-02-17 18:43:47 driver-btm-soc.c:3786:check_system_work: low temperature re_open_core [2] times,DONE!
2020-02-17 19:14:14 driver-btm-soc.c:3498:check_system_work: The avg rate is 16380 in 30 mins, PCB temperature between 17 ~ 48
2020-02-17 19:44:41 driver-btm-soc.c:3498:check_system_work: The avg rate is 16096 in 30 mins, PCB temperature between 20 ~ 45
2020-02-17 20:15:09 driver-btm-soc.c:3498:check_system_work: The avg rate is 16140 in 30 mins, PCB temperature between 19 ~ 45
2020-02-17 20:45:36 driver-btm-soc.c:3498:check_system_work: The avg rate is 16200 in 30 mins, PCB temperature between 19 ~ 45
2020-02-17 21:16:04 driver-btm-soc.c:3498:check_system_work: The avg rate is 16251 in 30 mins, PCB temperature between 17 ~ 44
2020-02-17 21:46:31 driver-btm-soc.c:3498:check_system_work: The avg rate is 16199 in 30 mins, PCB temperature between 16 ~ 42
2020-02-17 21:48:04 driver-btm-soc.c:7153:send_job: Version num 1
2020-02-17 21:48:04 util.c:2178:process_version_mask: Pool 0 Version num is 2
2020-02-17 21:48:04 util.c:2178:process_version_mask: Pool 0 Version num is 2
2020-02-17 21:48:11 driver-btm-soc.c:7153:send_job: Version num 2
2020-02-17 22:16:59 driver-btm-soc.c:3498:check_system_work: The avg rate is 16188 in 30 mins, PCB temperature between 16 ~ 41
2020-02-17 22:47:27 driver-btm-soc.c:3498:check_system_work: The avg rate is 16185 in 30 mins, PCB temperature between 15 ~ 41
2020-02-17 23:17:55 driver-btm-soc.c:3498:check_system_work: The avg rate is 16291 in 30 mins, PCB temperature between 16 ~ 41
2020-02-17 23:48:22 driver-btm-soc.c:3498:check_system_work: The avg rate is 16275 in 30 mins, PCB temperature between 16 ~ 41
2020-02-18 00:18:50 driver-btm-soc.c:3498:check_system_work: The avg rate is 16312 in 30 mins, PCB temperature between 16 ~ 41
2020-02-18 00:49:18 driver-btm-soc.c:3498:check_system_work: The avg rate is 16200 in 30 mins, PCB temperature between 15 ~ 41
2020-02-18 01:19:46 driver-btm-soc.c:3498:check_system_work: The avg rate is 16146 in 30 mins, PCB temperature between 15 ~ 39
2020-02-18 01:50:13 driver-btm-soc.c:3498:check_system_work: The avg rate is 16108 in 30 mins, PCB temperature between 15 ~ 39
2020-02-18 02:20:41 driver-btm-soc.c:3498:check_system_work: The avg rate is 16171 in 30 mins, PCB temperature between 15 ~ 39 For the miner that shows only 2 hash boards, there is a 90% chance that board number 2 is bad, a 10% chance the PSU / data cable (from the control board to hash board) is bad. The simplest way to troubleshoot this is by swapping the PSU with a working one, and the same thing for the ribbon cable, if no luck then you have to actually unplug/remove hash board number 2 which is the middle board, the miner will most likely run just fine when you do that, of course with only 2/3 of the total hash rate you would expect. as for your other concern, the S9Es are much better than the S9k, but they are not even close to being half stable and robust as the S9/S9j/S9i, they take forever to boot and start hashing at a stable rate, don't compare them to your old S9s, those days are over. |
|
|
|
|
Show Posts
