Bitcoin Forum
May 25, 2024, 09:35:34 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 [230] 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 ... 406 »
4581  Bitcoin / Mining support / Re: S17 Pro Firmware Booster on: February 19, 2020, 09:47:32 PM
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

Quote
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

Quote
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.
4582  Alternate cryptocurrencies / Mining (Altcoins) / Re: Please Identify this miner for me on: February 19, 2020, 09:01:11 PM
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!
4583  Bitcoin / Mining support / Re: S17 Pro Firmware Booster on: February 19, 2020, 08:12:30 PM
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.
4584  Local / العربية (Arabic) / Re: شراء فيزا كارد افتراضية بالبتكوين on: February 19, 2020, 05:37:56 PM
شكرا لك اخي ميكي على الشرح المميز وعلى مشاركة هذه التجربة معنا
Quote
القيم المتاحة هي : 5$,10$,25$,50$
أعتقد أن سعرها ليس غالي والجميل فيها أن تقبل الدفع بالبيتكوين
يعني البطاقة التي سعرها 5$ تعادل حوالي 0.0005$ وهو مبلغ بسيط

اريد توضيح نقطة اخرى وهي ان قيمة البطاقة اقل بقليل من المبلغ الذي يتم دفعه، فمثلا بطاقة 50$ تدفع 52.23$ لتحصل عليها.

مما يعني ان عمولة الموقع اكثر من 4% فيجب تجنب استخدامها الا عند الحاجة، والافضل هوا شراء ال gift cards للمواقع التي تتعامل بها لان سعرها اقل ، يعني مثلا amazon gift يمكن الحصول عليها بدفع 80-90% من قيمتها فقط.
4585  Bitcoin / Development & Technical Discussion / Re: 51% Attack on: February 19, 2020, 01:37:33 AM
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.

Quote
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.


Quote
First, how do you get that 4,285,714 s9?
Money!

Quote
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.


Quote
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?

Quote
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".

4586  Local / العربية (Arabic) / Re: شراء فيزا كارد افتراضية بالبتكوين on: February 19, 2020, 01:17:00 AM
ملاحظة: عدل الصورة التي بها بيانات البطاقة في حال لا يزال فيها رصيد خاصة CVV. الارقام يمكن استنتاجها عند التركيز على الصورة.

أجل أخي خالد لقد فعلت ذالك هذا جاء إلى ذهني  Grinمن خلال التركيز في الصورة أكثر تستطيع تخمين الرقم الصحيح و إحدى هذه الأرقام سبعة لذا يجب الإنتباه أكثر من الأخ مايكي حتى لا نسمع ما لا نحبه. و أشكر الأخ أيضا على الشرح المفيد بحيث يمكن إستغلال الخدمة للحصول على كارد فيزا إفتراضية و توضيفه لتسوق أو دفع تمويل . خصوصا إذا كان المستخدم لا يتوفر على حساب بنكي أو البلد لا يدعم الخدمة.


من يسطتيع استنتاج او تخمين الارقام حلال عليه ماتبقى من رصيد في البطاقة , وله ايضا جائزة 30$ بتكوين يتم تحويلها مباشرة الى محفظته  Roll Eyes على اي حال شكرا على الملاحظة اخ خالد واخ Ulven
4587  Other / Meta / Re: A reply of yours, quoted below, was deleted by a Bitcoin Forum moderator. on: February 19, 2020, 12:07:52 AM
Recently, Mickeywith suggested in Chipmixer that it is impossible to change boards
Quote
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  Huh.

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

Quote
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.
4588  Local / التعدين / Re: المفيد المختصر في شرح الوحش المنتظر on: February 18, 2020, 11:50:09 PM
موضوع اكثر من رائع بكل صراحة, المشكلة الوحيدة هوا انك لم تقم بربط ثقنية الكوانتوم بالتعدين ( بحكم ان الموضوع موجود في قسم التعدين) في الواقع الموضوع يحتاج لربط بالبتكوين بالمجمل, يوجد ورقة بحث اكثر من رائعة اتمنى ان تقرائها 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 الخاص به.

يوجد مبالغة كبيرة في مدى خطورة الكوانتوم على التشفير بصفة عامة, مايجهله الكثرين ان هده الثقنية هي في الاصل خطر على انظمة الدول العظمى واستخبارتها وامنها القوي, لذلك قبل وصول هده الثقنية للعلن ستكون تلك الحكومات قد قامت باستخدام اجهزة كوانتوم نفسها لانشاء لوغورتمات تشفير تفوق قدرة الكوانتوم لفكها, تمام كما حصل مع اجهزة الحاسوب التي نسخدمها الان, في الماضي كان التشفير بالورقة والقلم, وبمجرد انتشار تقنية الحاسوب قامو باستخدامه لانشاء تشفيرات لاتزال حتى الان مصتعصية, نفس الشي سيحدث مع الكوانتوم ولا داعي للقلك من وجهة نظري المتواضعة.

شكرا جدا على هدا الموضوع الاكثر من رائع
4589  Local / العربية (Arabic) / شراء فيزا كارد افتراضية بالبتكوين on: February 18, 2020, 11:06:21 PM
تحديث مهم بتاريخ 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.
4590  Bitcoin / Mining support / Re: Antminer S9 SE 17TH on: February 18, 2020, 09:49:03 PM
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.
4591  Bitcoin / Mining speculation / Re: Bitmain Points ( A new feature, What is it) ? on: February 18, 2020, 09:26:15 PM
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".
4592  Bitcoin / Mining support / Re: S9K temperature related network failure - logs on: February 18, 2020, 04:25:24 AM
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  Cheesy

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.
4593  Bitcoin / Mining speculation / Re: Bitmain Points ( A new feature, What is it) ? on: February 18, 2020, 03:53:02 AM
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.
4594  Bitcoin / Mining support / Re: Antminer S9 SE 17TH on: February 18, 2020, 02:58:08 AM
Continuation (exceeded maximum length)

Code:
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.
4595  Bitcoin / Mining support / Re: Antminer S9 SE 17TH on: February 18, 2020, 02:52:21 AM
Below is the kernel log of one of my S9E 16Th version

Code:

Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
  Normal zone: 480 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 198656K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 30720K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xcf800000 - 0xff800000   ( 768 MB)
    lowmem  : 0xc0000000 - 0xcf000000   ( 240 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc090c424   (9234 kB)
      .init : 0xc0a00000 - 0xc0b00000   (1024 kB)
      .data : 0xc0b00000 - 0xc0b39fe0   ( 232 kB)
       .bss : 0xc0b39fe0 - 0xc0b71c28   ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 17680K (cc9bc000 - cdb00000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Broadcom BCM5241 e000b000.etherne:00: attached PHY driver [Broadcom BCM5241] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
  No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 16/7, WL threshold: 4096, image sequence number: 416762856
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): recovery needed
UBIFS (ubi0:0): recovery completed
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 84A07273-7DB4-4D10-BFAD-008C5D5B6CDF, small LPT model
ubi1: attaching mtd5
ubi1: scanning is finished
ubi1: attached mtd5 (name "reserve1", size 128 MiB)
ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi1: good PEBs: 1020, bad PEBs: 4, corrupted PEBs: 0
ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi1: max/mean erase counter: 725/194, WL threshold: 4096, image sequence number: 1746335632
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): recovery needed
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 92A8FA43-575C-4006-B303-EDE1C509283D, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb34000
*base_vir_addr = 0xab00d
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
 [1970-01-01 00:00:53.733] httpListenThread start ret=0
 [1970-01-01 00:01:23.733] start listen on 6060 ...
 [1970-01-01 00:05:54.563] setStartTimePoint total_tv_start_sys=355 total_tv_end_sys=356

1970-01-01 00:00:53 driver-btm-soc.c:6490:bitmain_soc_init: This is Antminer S9 SE scan user version
1970-01-01 00:00:53 driver-btm-soc.c:6496:bitmain_soc_init: special mode: disabled
1970-01-01 00:00:53 driver-btm-soc.c:6503:bitmain_soc_init: This is high performance mode
1970-01-01 00:00:53 driver-btm-soc.c:6508:bitmain_soc_init: last commit version: a70ae17 commit time: 2019-07-10 21:53:39 build: 2019-07-11 11:18:49
1970-01-01 00:00:53 driver-btm-soc.c:6529:bitmain_soc_init: Detect 256MB control board of XILINX
1970-01-01 00:00:53 driver-btm-soc.c:6532:bitmain_soc_init: Miner compile time: Thu Jul 11 11:11:08 CST 2019 type: Antminer S9 SE
1970-01-01 00:00:53 driver-btm-soc.c:838:check_chain: get_hash_on_plug is 0x7
1970-01-01 00:00:53 driver-btm-soc.c:850:check_chain: !! chain[0]is exist
1970-01-01 00:00:53 driver-btm-soc.c:850:check_chain: !! chain[1]is exist
1970-01-01 00:00:53 driver-btm-soc.c:850:check_chain: !! chain[2]is exist
         00 01 02 03 04 05 06 07   08 09 0A 0B 0C 0D 0E 0F
00000000 7e ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000010 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000020 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000030 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000040 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000050 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000060 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000070 ff ff ff ff ff ff ff ff   ff 01 02 1f fc 28 fc ff
00000080 ff ff ff ff ff ff ff a5   57 57 57 57 57 57 57 57
00000090 54 52 52 57 57 54 57 57   57 57 57 57 57 57 57 57
000000a0 57 57 57 57 54 52 52 54   57 57 57 57 57 57 57 57
000000b0 57 57 57 57 57 57 57 57   54 52 52 54 57 57 57 57
000000c0 57 57 57 57 00 ff ff ff   ff ff ff ff ff ff ff ff
000000d0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000e0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000f0 ff ff ff ff 00 15 00 00   60 ff ff ff 39 10 87 4a
         00 01 02 03 04 05 06 07   08 09 0A 0B 0C 0D 0E 0F
00000000 7e ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000010 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000020 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000030 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000040 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000050 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000060 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000070 ff ff ff ff ff ff ff ff   ff 01 02 1f fc 28 fc ff
00000080 ff ff ff ff ff ff ff a5   57 57 57 57 57 57 54 4c
00000090 54 52 4c 54 54 57 57 52   57 57 57 57 57 57 57 57
000000a0 57 57 54 54 52 4c 4c 52   54 54 57 57 57 57 57 57
000000b0 52 57 57 57 57 54 57 57   54 4c 4c 52 54 54 57 57
000000c0 57 57 57 57 00 ff ff ff   ff ff ff ff ff ff ff ff
000000d0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000e0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000f0 ff ff ff ff a9 14 00 00   60 ff ff ff 39 10 c9 cc
         00 01 02 03 04 05 06 07   08 09 0A 0B 0C 0D 0E 0F
00000000 7e ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000010 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000020 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000030 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000040 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000050 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000060 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000070 ff ff ff ff ff ff ff ff   ff 01 02 1f fc 28 fd ff
00000080 ff ff ff ff ff ff ff a5   58 58 58 58 58 58 58 58
00000090 58 55 55 58 58 58 58 58   58 58 58 58 58 58 58 58
000000a0 58 58 58 58 58 55 55 58   58 58 58 58 58 58 58 58
000000b0 58 58 58 58 58 58 58 58   58 55 55 58 58 58 58 58
000000c0 58 58 58 58 00 ff ff ff   ff ff ff ff ff ff ff ff
000000d0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000e0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000f0 ff ff ff ff 5e 15 00 00   60 ff ff ff 39 10 a3 23

read chain[0] hardware info:
major type: 0
minor type: 4
chip level: 1
bom version: 0x10
pcb version: 0x39
fixture 8pattern result: L0

read chain[1] hardware info:
major type: 0
minor type: 4
chip level: 1
bom version: 0x10
pcb version: 0x39
fixture 8pattern result: L0

read chain[2] hardware info:
major type: 0
minor type: 4
chip level: 1
bom version: 0x10
pcb version: 0x39
fixture 8pattern result: L0

sweep config for eco mode:
sweep_start_voltage: 8.60
max_aging_voltage:   8.90
sweep_min_freq:      300M
sweep_max_freq:      380M

sweep config for hpf mode:
sweep_start_voltage: 9.30
max_aging_voltage:   9.60
sweep_min_freq:      415M
sweep_max_freq:      465M
1970-01-01 00:01:05 driver-btm-soc.c:838:check_chain: get_hash_on_plug is 0x7
1970-01-01 00:01:05 driver-btm-soc.c:850:check_chain: !! chain[0]is exist
1970-01-01 00:01:05 driver-btm-soc.c:850:check_chain: !! chain[1]is exist
1970-01-01 00:01:05 driver-btm-soc.c:850:check_chain: !! chain[2]is exist
1970-01-01 00:01:05 driver-btm-soc.c:5935:get_freq_result_from_eeprom: orginal chip freq:
chain 0 freq:
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

chain 1 freq:
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

chain 2 freq:
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

1970-01-01 00:01:05 driver-btm-soc.c:6618:bitmain_soc_init: reset all...
1970-01-01 00:01:07 driver-btm-soc.c:6626:bitmain_soc_init: miner ID : 807875c81540885c
1970-01-01 00:01:07 driver-btm-soc.c:6329:init_miner_version: FPGA Version = 0xB00D
1970-01-01 00:01:26 dspic33ep16gs202.c:486:get_pic_software_version_all_chain: chain[0] PIC software version: 177
1970-01-01 00:01:27 dspic33ep16gs202.c:486:get_pic_software_version_all_chain: chain[1] PIC software version: 177
1970-01-01 00:01:28 dspic33ep16gs202.c:486:get_pic_software_version_all_chain: chain[2] PIC software version: 177
1970-01-01 00:01:28 power.c:183:power_init: power init ...
1970-01-01 00:01:28 driver-btm-soc.c:5048:get_working_voltage_from_eeprom: get working vol [ 9.60] from chain[0] eeprom
1970-01-01 00:01:28 power.c:230:set_working_voltage_by_chain: chain[0] working_voltage = 9.600000
1970-01-01 00:01:28 driver-btm-soc.c:5048:get_working_voltage_from_eeprom: get working vol [ 9.60] from chain[1] eeprom
1970-01-01 00:01:28 power.c:230:set_working_voltage_by_chain: chain[1] working_voltage = 9.600000
1970-01-01 00:01:28 driver-btm-soc.c:5048:get_working_voltage_from_eeprom: get working vol [ 9.60] from chain[2] eeprom
1970-01-01 00:01:28 power.c:230:set_working_voltage_by_chain: chain[2] working_voltage = 9.600000
1970-01-01 00:01:28 driver-btm-soc.c:5724:update_highest_voltage: chain 0 hpf working voltage 9.30
1970-01-01 00:01:28 driver-btm-soc.c:5724:update_highest_voltage: chain 1 hpf working voltage 9.30
1970-01-01 00:01:28 driver-btm-soc.c:5724:update_highest_voltage: chain 2 hpf working voltage 9.30
1970-01-01 00:01:28 driver-btm-soc.c:5733:update_highest_voltage: open core at max voltage 10.04
1970-01-01 00:01:28 power.c:779:set_iic_power_to_highest_voltage_by_chain: chain[0] setting to hightest voltage: 10.04 ...
1970-01-01 00:01:28 power.c:705:set_iic_power_by_voltage: now setting voltage to : 10.044000
1970-01-01 00:01:29 power.c:779:set_iic_power_to_highest_voltage_by_chain: chain[1] setting to hightest voltage: 10.04 ...
1970-01-01 00:01:31 power.c:705:set_iic_power_by_voltage: now setting voltage to : 10.044000
1970-01-01 00:01:31 power.c:779:set_iic_power_to_highest_voltage_by_chain: chain[2] setting to hightest voltage: 10.04 ...
1970-01-01 00:01:32 power.c:705:set_iic_power_by_voltage: now setting voltage to : 10.044000
1970-01-01 00:01:32 driver-btm-soc.c:1186:get_eeprom_total_hash_rate: chain[0] hash rate = 5376
1970-01-01 00:01:32 driver-btm-soc.c:1186:get_eeprom_total_hash_rate: chain[1] hash rate = 5289
1970-01-01 00:01:32 driver-btm-soc.c:1186:get_eeprom_total_hash_rate: chain[2] hash rate = 5470
1970-01-01 00:01:32 driver-btm-soc.c:1190:get_eeprom_total_hash_rate: total rate = 16135
1970-01-01 00:01:32 driver-btm-soc.c:1198:get_ideal_hash_rate: get ideal hash rate 16000
1970-01-01 00:01:32 eeprom.c:665:travel_eeprom_store: chain[0] data in eeprom is:
magic number: 0x7e
freq data per ASIC:
IC[000]:1275 IC[001]:1275 IC[002]:1275 IC[003]:1275 IC[004]:1275 IC[005]:1275 IC[006]:1275 IC[007]:1275 IC[008]:1275 IC[009]:1275
IC[010]:1275 IC[011]:1275 IC[012]:1275 IC[013]:1275 IC[014]:1275 IC[015]:1275 IC[016]:1275 IC[017]:1275 IC[018]:1275 IC[019]:1275
IC[020]:1275 IC[021]:1275 IC[022]:1275 IC[023]:1275 IC[024]:1275 IC[025]:1275 IC[026]:1275 IC[027]:1275 IC[028]:1275 IC[029]:1275
IC[030]:1275 IC[031]:1275 IC[032]:1275 IC[033]:1275 IC[034]:1275 IC[035]:1275 IC[036]:1275 IC[037]:1275 IC[038]:1275 IC[039]:1275
IC[040]:1275 IC[041]:1275 IC[042]:1275 IC[043]:1275 IC[044]:1275 IC[045]:1275 IC[046]:1275 IC[047]:1275 IC[048]:1275 IC[049]:1275
IC[050]:1275 IC[051]:1275 IC[052]:1275 IC[053]:1275 IC[054]:1275 IC[055]:1275 IC[056]:1275 IC[057]:1275 IC[058]:1275 IC[059]:1275
voltage: 11.10 V
hash rate: -0001 GH/s

freq data per ASIC in mode2:
IC[000]:435 IC[001]:435 IC[002]:435 IC[003]:435 IC[004]:435 IC[005]:435 IC[006]:435 IC[007]:435 IC[008]:420 IC[009]:410
IC[010]:410 IC[011]:435 IC[012]:435 IC[013]:420 IC[014]:435 IC[015]:435 IC[016]:435 IC[017]:435 IC[018]:435 IC[019]:435
IC[020]:435 IC[021]:435 IC[022]:435 IC[023]:435 IC[024]:435 IC[025]:435 IC[026]:435 IC[027]:435 IC[028]:420 IC[029]:410
IC[030]:410 IC[031]:420 IC[032]:435 IC[033]:435 IC[034]:435 IC[035]:435 IC[036]:435 IC[037]:435 IC[038]:435 IC[039]:435
IC[040]:435 IC[041]:435 IC[042]:435 IC[043]:435 IC[044]:435 IC[045]:435 IC[046]:435 IC[047]:435 IC[048]:420 IC[049]:410
IC[050]:410 IC[051]:420 IC[052]:435 IC[053]:435 IC[054]:435 IC[055]:435 IC[056]:435 IC[057]:435 IC[058]:435 IC[059]:435
voltage in mode2: 9.30 V
hash rate in mode2: 05376 GH/s

1970-01-01 00:01:32 eeprom.c:665:travel_eeprom_store: chain[1] data in eeprom is:
magic number: 0x7e
freq data per ASIC:
IC[000]:1275 IC[001]:1275 IC[002]:1275 IC[003]:1275 IC[004]:1275 IC[005]:1275 IC[006]:1275 IC[007]:1275 IC[008]:1275 IC[009]:1275
IC[010]:1275 IC[011]:1275 IC[012]:1275 IC[013]:1275 IC[014]:1275 IC[015]:1275 IC[016]:1275 IC[017]:1275 IC[018]:1275 IC[019]:1275
IC[020]:1275 IC[021]:1275 IC[022]:1275 IC[023]:1275 IC[024]:1275 IC[025]:1275 IC[026]:1275 IC[027]:1275 IC[028]:1275 IC[029]:1275
IC[030]:1275 IC[031]:1275 IC[032]:1275 IC[033]:1275 IC[034]:1275 IC[035]:1275 IC[036]:1275 IC[037]:1275 IC[038]:1275 IC[039]:1275
IC[040]:1275 IC[041]:1275 IC[042]:1275 IC[043]:1275 IC[044]:1275 IC[045]:1275 IC[046]:1275 IC[047]:1275 IC[048]:1275 IC[049]:1275
IC[050]:1275 IC[051]:1275 IC[052]:1275 IC[053]:1275 IC[054]:1275 IC[055]:1275 IC[056]:1275 IC[057]:1275 IC[058]:1275 IC[059]:1275
voltage: 11.10 V
hash rate: -0001 GH/s

freq data per ASIC in mode2:
IC[000]:435 IC[001]:435 IC[002]:435 IC[003]:435 IC[004]:435 IC[005]:435 IC[006]:420 IC[007]:380 IC[008]:420 IC[009]:410
IC[010]:380 IC[011]:420 IC[012]:420 IC[013]:435 IC[014]:435 IC[015]:410 IC[016]:435 IC[017]:435 IC[018]:435 IC[019]:435
IC[020]:435 IC[021]:435 IC[022]:435 IC[023]:435 IC[024]:435 IC[025]:435 IC[026]:420 IC[027]:420 IC[028]:410 IC[029]:380
IC[030]:380 IC[031]:410 IC[032]:420 IC[033]:420 IC[034]:435 IC[035]:435 IC[036]:435 IC[037]:435 IC[038]:435 IC[039]:435
IC[040]:410 IC[041]:435 IC[042]:435 IC[043]:435 IC[044]:435 IC[045]:420 IC[046]:435 IC[047]:435 IC[048]:420 IC[049]:380
IC[050]:380 IC[051]:410 IC[052]:420 IC[053]:420 IC[054]:435 IC[055]:435 IC[056]:435 IC[057]:435 IC[058]:435 IC[059]:435
voltage in mode2: 9.30 V
hash rate in mode2: 05289 GH/s

1970-01-01 00:01:32 eeprom.c:665:travel_eeprom_store: chain[2] data in eeprom is:
magic number: 0x7e
freq data per ASIC:
IC[000]:1275 IC[001]:1275 IC[002]:1275 IC[003]:1275 IC[004]:1275 IC[005]:1275 IC[006]:1275 IC[007]:1275 IC[008]:1275 IC[009]:1275
IC[010]:1275 IC[011]:1275 IC[012]:1275 IC[013]:1275 IC[014]:1275 IC[015]:1275 IC[016]:1275 IC[017]:1275 IC[018]:1275 IC[019]:1275
IC[020]:1275 IC[021]:1275 IC[022]:1275 IC[023]:1275 IC[024]:1275 IC[025]:1275 IC[026]:1275 IC[027]:1275 IC[028]:1275 IC[029]:1275
IC[030]:1275 IC[031]:1275 IC[032]:1275 IC[033]:1275 IC[034]:1275 IC[035]:1275 IC[036]:1275 IC[037]:1275 IC[038]:1275 IC[039]:1275
IC[040]:1275 IC[041]:1275 IC[042]:1275 IC[043]:1275 IC[044]:1275 IC[045]:1275 IC[046]:1275 IC[047]:1275 IC[048]:1275 IC[049]:1275
IC[050]:1275 IC[051]:1275 IC[052]:1275 IC[053]:1275 IC[054]:1275 IC[055]:1275 IC[056]:1275 IC[057]:1275 IC[058]:1275 IC[059]:1275
voltage: 11.10 V
hash rate: -0001 GH/s

freq data per ASIC in mode2:
IC[000]:440 IC[001]:440 IC[002]:440 IC[003]:440 IC[004]:440 IC[005]:440 IC[006]:440 IC[007]:440 IC[008]:440 IC[009]:425
IC[010]:425 IC[011]:440 IC[012]:440 IC[013]:440 IC[014]:440 IC[015]:440 IC[016]:440 IC[017]:440 IC[018]:440 IC[019]:440
IC[020]:440 IC[021]:440 IC[022]:440 IC[023]:440 IC[024]:440 IC[025]:440 IC[026]:440 IC[027]:440 IC[028]:440 IC[029]:425
IC[030]:425 IC[031]:440 IC[032]:440 IC[033]:440 IC[034]:440 IC[035]:440 IC[036]:440 IC[037]:440 IC[038]:440 IC[039]:440
IC[040]:440 IC[041]:440 IC[042]:440 IC[043]:440 IC[044]:440 IC[045]:440 IC[046]:440 IC[047]:440 IC[048]:440 IC[049]:425
IC[050]:425 IC[051]:440 IC[052]:440 IC[053]:440 IC[054]:440 IC[055]:440 IC[056]:440 IC[057]:440 IC[058]:440 IC[059]:440
voltage in mode2: 9.30 V
hash rate in mode2: 05470 GH/s

1970-01-01 00:01:32 driver-btm-soc.c:6669:bitmain_soc_init: fan_eft : 1  fan_pwm : 90
1970-01-01 00:01:32 driver-btm-soc.c:6358:bring_up_chain:

bring up chain 0
1970-01-01 00:01:33 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000ffff
1970-01-01 00:02:04 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
1970-01-01 00:02:06 driver-btm-soc.c:3991:check_asic_num: without pre_open_core chain 0, find asic num = 60
1970-01-01 00:02:09 driver-btm-soc.c:4804:set_freq_by_chain: chain[0] set freq:100.00
1970-01-01 00:02:10 driver-btm-soc.c:3917:pre_open_core_one_chain: for chain 0
1970-01-01 00:02:10 driver-btm-soc.c:4078:set_clock_delay_control: core_data = 0x06
1970-01-01 00:02:10 temperature.c:604:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
1970-01-01 00:02:10 temperature.c:513:is_tempsensor_data_correct: Bad,temp_info.type = 0
1970-01-01 00:02:10 temperature.c:741:calibration_sensor_offset: chain[0] temp info is bad, reload from eeprom..
sensor type = 1,sensor num = 2
sensor pos: 31  40  0  0  0  0
sensor offset: -4  -4  0  0  0  0
1970-01-01 00:02:10 temperature.c:791:calibration_sensor_offset: Chain[0] chip[31] middle temp offset=-4, typeID=55
1970-01-01 00:02:11 temperature.c:791:calibration_sensor_offset: Chain[0] chip[40] middle temp offset=-4, typeID=55
1970-01-01 00:02:11 driver-btm-soc.c:6358:bring_up_chain:

bring up chain 1
1970-01-01 00:02:12 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
1970-01-01 00:02:44 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
1970-01-01 00:02:45 driver-btm-soc.c:3991:check_asic_num: without pre_open_core chain 1, find asic num = 60
1970-01-01 00:02:48 driver-btm-soc.c:4804:set_freq_by_chain: chain[1] set freq:100.00
1970-01-01 00:02:49 driver-btm-soc.c:3917:pre_open_core_one_chain: for chain 1
1970-01-01 00:02:49 driver-btm-soc.c:4078:set_clock_delay_control: core_data = 0x06
1970-01-01 00:02:49 temperature.c:604:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
1970-01-01 00:02:49 temperature.c:513:is_tempsensor_data_correct: Bad,temp_info.type = 0
1970-01-01 00:02:49 temperature.c:741:calibration_sensor_offset: chain[1] temp info is bad, reload from eeprom..
sensor type = 1,sensor num = 2
sensor pos: 31  40  0  0  0  0
sensor offset: -4  -4  0  0  0  0
1970-01-01 00:02:49 temperature.c:791:calibration_sensor_offset: Chain[1] chip[31] middle temp offset=-4, typeID=55
1970-01-01 00:02:50 temperature.c:791:calibration_sensor_offset: Chain[1] chip[40] middle temp offset=-4, typeID=55
1970-01-01 00:02:50 driver-btm-soc.c:6358:bring_up_chain:

bring up chain 2
1970-01-01 00:02:51 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
1970-01-01 00:03:23 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
1970-01-01 00:03:24 driver-btm-soc.c:3991:check_asic_num: without pre_open_core chain 2, find asic num = 60
1970-01-01 00:03:27 driver-btm-soc.c:4804:set_freq_by_chain: chain[2] set freq:100.00
1970-01-01 00:03:28 driver-btm-soc.c:3917:pre_open_core_one_chain: for chain 2
1970-01-01 00:03:28 driver-btm-soc.c:4078:set_clock_delay_control: core_data = 0x06
1970-01-01 00:03:28 temperature.c:604:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
1970-01-01 00:03:28 temperature.c:513:is_tempsensor_data_correct: Bad,temp_info.type = 0
1970-01-01 00:03:28 temperature.c:741:calibration_sensor_offset: chain[2] temp info is bad, reload from eeprom..
sensor type = 1,sensor num = 2
sensor pos: 31  40  0  0  0  0
sensor offset: -4  -3  0  0  0  0
1970-01-01 00:03:29 temperature.c:791:calibration_sensor_offset: Chain[2] chip[31] middle temp offset=-4, typeID=55
1970-01-01 00:03:29 temperature.c:791:calibration_sensor_offset: Chain[2] chip[40] middle temp offset=-3, typeID=55
1970-01-01 00:03:29 asic.c:1153:set_baud: set baud=1
1970-01-01 00:03:30 asic.c:1269:set_asic_ticket_mask: set ticket mask 63
1970-01-01 00:03:31 temperature.c:1933:detect_startup_environment_temperature: Environment temperature: [12]
1970-01-01 00:03:31 driver-btm-soc.c:4148:open_core_bm1393: Start Open Core!!
1970-01-01 00:03:37 driver-btm-soc.c:4215:open_core_bm1393: End Open Core!!
1970-01-01 00:03:37 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 125
1970-01-01 00:03:38 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 150
1970-01-01 00:03:39 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 175
1970-01-01 00:03:40 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 200
1970-01-01 00:03:41 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 225
1970-01-01 00:03:42 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 250
1970-01-01 00:03:43 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 275
1970-01-01 00:03:44 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 300
1970-01-01 00:03:45 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 325
1970-01-01 00:03:46 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 350
1970-01-01 00:03:47 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 375
1970-01-01 00:03:48 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 400
1970-01-01 00:03:49 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 410
1970-01-01 00:03:50 driver-btm-soc.c:5365:increase_freq_by_eeprom_slowly_by_chain: max = 435 ,min = 410
1970-01-01 00:03:50 driver-btm-soc.c:5371:increase_freq_by_eeprom_slowly_by_chain: chain[0] increaseing the diff freq ...
1970-01-01 00:03:54 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
1970-01-01 00:03:54 power.c:1303:slowly_set_working_power_t11: set chain 0 to working voltage:
now setting chain[0]-volt[10.04]-data[014]
now setting chain[0]-volt[09.99]-data[015]
now setting chain[0]-volt[09.94]-data[016]
now setting chain[0]-volt[09.89]-data[017]
now setting chain[0]-volt[09.85]-data[018]
now setting chain[0]-volt[09.76]-data[020]
now setting chain[0]-volt[09.68]-data[022]
now setting chain[0]-volt[09.65]-data[023]
now setting chain[0]-volt[09.61]-data[024]
1970-01-01 00:04:20 power.c:1318:slowly_set_working_power_t11: done!
1970-01-01 00:04:20 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 125
1970-01-01 00:04:21 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 150
1970-01-01 00:04:22 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 175
1970-01-01 00:04:23 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 200
1970-01-01 00:04:24 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 225
1970-01-01 00:04:25 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 250
1970-01-01 00:04:26 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 275
1970-01-01 00:04:27 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 300
1970-01-01 00:04:28 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 325
1970-01-01 00:04:29 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 350
1970-01-01 00:04:30 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 375
1970-01-01 00:04:31 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 380
1970-01-01 00:04:32 driver-btm-soc.c:5365:increase_freq_by_eeprom_slowly_by_chain: max = 435 ,min = 380
1970-01-01 00:04:32 driver-btm-soc.c:5371:increase_freq_by_eeprom_slowly_by_chain: chain[1] increaseing the diff freq ...
1970-01-01 00:04:43 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
1970-01-01 00:04:43 power.c:1303:slowly_set_working_power_t11: set chain 1 to working voltage:
now setting chain[1]-volt[10.04]-data[014]
now setting 1970-01-01 00:04:48 dspic33ep16gs202.c:276:dsPIC33EP16GS202_set_pic_voltage: ERROR! failed on Chain[1] after 3 times try!
chain[1]-volt[09.99]-data[015]
now setting chain[1]-volt[09.94]-data[016]
now setting chain[1]-volt[09.89]-data[017]
now setting chain[1]-volt[09.85]-data[018]
now setting chain[1]-volt[09.76]-data[020]
now setting chain[1]-volt[09.68]-data[022]
now setting chain[1]-volt[09.65]-data[023]
now setting chain[1]-volt[09.61]-data[024]
1970-01-01 00:05:10 power.c:1318:slowly_set_working_power_t11: done!
1970-01-01 00:05:10 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 125
1970-01-01 00:05:11 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 150
1970-01-01 00:05:12 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 175
1970-01-01 00:05:13 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 200
1970-01-01 00:05:14 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 225
1970-01-01 00:05:15 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 250
1970-01-01 00:05:16 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 275
1970-01-01 00:05:17 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 300
1970-01-01 00:05:18 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 325
1970-01-01 00:05:19 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 350
1970-01-01 00:05:21 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 375
1970-01-01 00:05:22 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 400
1970-01-01 00:05:23 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 425
1970-01-01 00:05:24 driver-btm-soc.c:5365:increase_freq_by_eeprom_slowly_by_chain: max = 440 ,min = 425
1970-01-01 00:05:24 driver-btm-soc.c:5371:increase_freq_by_eeprom_slowly_by_chain: chain[2] increaseing the diff freq ...
1970-01-01 00:05:27 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
1970-01-01 00:05:27 power.c:1303:slowly_set_working_power_t11: set chain 2 to working voltage:
now setting chain[2]-volt[10.04]-data[014]
now setting chain[2]-volt[09.99]-data[015]
now setting chain[2]-volt[09.94]-data[016]
now setting chain[2]-volt[09.89]-data[017]
now setting 1970-01-01 00:05:41 dspic33ep16gs202.c:276:dsPIC33EP16GS202_set_pic_voltage: ERROR! failed on Chain[2] after 3 times try!
chain[2]-volt[09.85]-data[018]
now setting chain[2]-volt[09.76]-data[020]
now setting chain[2]-volt[09.68]-data[022]
now setting chain[2]-volt[09.65]-data[023]
now setting 1970-01-01 00:05:53 dspic33ep16gs202.c:276:dsPIC33EP16GS202_set_pic_voltage: ERROR! failed on Chain[2] after 3 times try!
chain[2]-volt[09.61]-data[024]
1970-01-01 00:05:54 power.c:1318:slowly_set_working_power_t11: done!
1970-01-01 00:05:54 driver-btm-soc.c:5100:set_timeout: freq 440 final timeout=297
1970-01-01 00:05:54 driver-btm-soc.c:2918:low_temp_process_parm_init: chip miner_type = [4]
1970-01-01 00:05:54 driver-btm-soc.c:2918:low_temp_process_parm_init: chip miner_type = [4]
1970-01-01 00:05:54 driver-btm-soc.c:2918:low_temp_process_parm_init: chip miner_type = [4]
1970-01-01 00:05:54 driver-btm-soc.c:3357:check_system_work: check system thread start...
1970-01-01 00:05:54 driver-btm-soc.c:3374:check_system_work: low_bringup_pcb_temp_threshhold = 28
1970-01-01 00:05:54 driver-btm-soc.c:3375:check_system_work: recovery_working_vol_low_temp = 30, recovery_working_vol_high_temp = 35
1970-01-01 00:05:54 driver-btm-soc.c:3376:check_system_work: delta_voltage = 0.10
1970-01-01 00:05:54 driver-btm-soc.c:6771:bitmain_soc_init: Init done!
1970-01-01 00:05:54 driver-btm-soc.c:7478:bitmain_soc_prepare: bitmain soc init success.
1970-01-01 00:05:55 temperature.c:1402:read_temp_func: bring_up_pcb_temp = 18
1970-01-01 00:05:55 util.c:2178:process_version_mask: Pool 0 Version num is 2
1970-01-01 00:05:55 util.c:2178:process_version_mask: Pool 0 Version num is 2
1970-01-01 00:05:55 driver-btm-soc.c:7153:send_job: Version num 2
1970-01-01 00:06:15 driver-btm-soc.c:3529:check_system_work: set reopen algorith parameters...
1970-01-01 00:10:59 eeprom.c:913:eeprom_get_inbalance_info: error: chain[0] inbalance num is 255, more than MAX_OFFSET 4
1970-01-01 00:10:59 driver-btm-soc.c:2498:is_domain_imbalance: eeprom info not correct! ret = 0, len = 0
1970-01-01 00:10:59 eeprom.c:913:eeprom_get_inbalance_info: error: chain[1] inbalance num is 255, more than MAX_OFFSET 4
1970-01-01 00:10:59 driver-btm-soc.c:2498:is_domain_imbalance: eeprom info not correct! ret = 0, len = 0
1970-01-01 00:10:59 eeprom.c:913:eeprom_get_inbalance_info: error: chain[2] inbalance num is 255, more than MAX_OFFSET 4
1970-01-01 00:10:59 driver-btm-soc.c:2498:is_domain_imbalance: eeprom info not correct! ret = 0, len = 0
1970-01-01 00:10:59 driver-btm-soc.c:2511:is_domain_imbalance: dumping inbalance domain info...
0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0 
0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0 
2020-02-17 18:29:28 temperature.c:1225:process_status_value: Fatal Error: network connection lost!
2020-02-17 18:29:42 log.c:101:_log_update_name: _log_update_name
2020-02-17 18:29:42 log.c:101:_log_update_name: _log_update_name
2020-02-17 18:31:46 driver-btm-soc.c:3711:check_system_work: bring_up_pcb_temp = 18, low_bringup_pcb_temp_threshhold = 28
2020-02-17 18:31:46 driver-btm-soc.c:3712:check_system_work: detecting at 15 minutes
2020-02-17 18:31:46 driver-btm-soc.c:3713:check_system_work: target hash rate = 15840, 5mins avg hash rate = 15587

2020-02-17 18:31:46 driver-btm-soc.c:3734:check_system_work: low temp bing up:[Yes]
2020-02-17 18:31:46 driver-btm-soc.c:3735:check_system_work: low temp running:[No]

2020-02-17 18:31:46 driver-btm-soc.c:3738:check_system_work: Temp Low! Entering Low Environment Handler...
2020-02-17 18:31:46 driver-btm-soc.c:3018:get_compensation_voltage: chip miner_type = [4]
2020-02-17 18:31:46 driver-btm-soc.c:3018:get_compensation_voltage: chip miner_type = [4]
2020-02-17 18:31:46 driver-btm-soc.c:3018:get_compensation_voltage: chip miner_type = [4]
2020-02-17 18:31:46 driver-btm-soc.c:3026:get_compensation_voltage: last_testpatten_lowest_pcb_temp = 20
2020-02-17 18:31:46 driver-btm-soc.c:3027:get_compensation_voltage: max_delta_vol =  0.10
2020-02-17 18:31:46 driver-btm-soc.c:3190:get_compensation_voltage: chain[0] working vol =  9.60, add vol =  0.10...
2020-02-17 18:31:46 driver-btm-soc.c:3190:get_compensation_voltage: chain[1] working vol =  9.60, add vol =  0.10...
2020-02-17 18:31:46 driver-btm-soc.c:3190:get_compensation_voltage: chain[2] working vol =  9.60, add vol =  0.10...
2020-02-17 18:31:46 driver-btm-soc.c:6960:re_open_core_by_chain:

reopen chain 0, current pwm 90
2020-02-17 18:31:48 power.c:779:set_iic_power_to_highest_voltage_by_chain: chain[0] setting to hightest voltage: 10.04 ...
2020-02-17 18:31:50 power.c:705:set_iic_power_by_voltage: now setting voltage to : 10.044000
2020-02-17 18:31:50 asic.c:1176:set_baud_by_chain: chain 0 set baud=26
2020-02-17 18:31:50 driver-btm-soc.c:6358:bring_up_chain:

bring up chain 0
2020-02-17 18:31:50 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff9
2020-02-17 18:31:51 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-02-17 18:31:53 driver-btm-soc.c:3991:check_asic_num: without pre_open_core chain 0, find asic num = 60
2020-02-17 18:31:56 driver-btm-soc.c:4804:set_freq_by_chain: chain[0] set freq:100.00
2020-02-17 18:31:57 driver-btm-soc.c:3917:pre_open_core_one_chain: for chain 0
2020-02-17 18:31:57 driver-btm-soc.c:4078:set_clock_delay_control: core_data = 0x06
2020-02-17 18:31:57 temperature.c:604:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
2020-02-17 18:31:57 temperature.c:791:calibration_sensor_offset: Chain[0] chip[31] middle temp offset=-4, typeID=55
2020-02-17 18:31:58 temperature.c:791:calibration_sensor_offset: Chain[0] chip[40] middle temp offset=-4, typeID=55
2020-02-17 18:31:58 asic.c:1176:set_baud_by_chain: chain 0 set baud=1
2020-02-17 18:31:58 asic.c:1269:set_asic_ticket_mask: set ticket mask 63
2020-02-17 18:31:58 driver-btm-soc.c:4148:open_core_bm1393: Start Open Core!!
2020-02-17 18:32:00 driver-btm-soc.c:4215:open_core_bm1393: End Open Core!!
2020-02-17 18:32:01 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 125
2020-02-17 18:32:02 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 150
2020-02-17 18:32:03 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 175
2020-02-17 18:32:04 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 200
2020-02-17 18:32:05 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 225
2020-02-17 18:32:06 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 250
2020-02-17 18:32:07 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 275
2020-02-17 18:32:08 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 300
2020-02-17 18:32:09 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 325
2020-02-17 18:32:10 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 350
2020-02-17 18:32:11 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 375
2020-02-17 18:32:12 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 400
2020-02-17 18:32:13 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 410
2020-02-17 18:32:14 driver-btm-soc.c:5365:increase_freq_by_eeprom_slowly_by_chain: max = 435 ,min = 410
2020-02-17 18:32:14 driver-btm-soc.c:5371:increase_freq_by_eeprom_slowly_by_chain: chain[0] increaseing the diff freq ...
2020-02-17 18:32:18 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:32:18 driver-btm-soc.c:5100:set_timeout: freq 440 final timeout=297
2020-02-17 18:32:19 driver-btm-soc.c:6987:re_open_core_by_chain: reopen chain 0 finished, chain 0 chip temp 41 - 60
2020-02-17 18:32:19 driver-btm-soc.c:6988:re_open_core_by_chain: all chain chip temp 41 - 63
2020-02-17 18:32:19 driver-btm-soc.c:7004:re_open_core_by_chain: re_open_core done!
2020-02-17 18:32:49 driver-btm-soc.c:6960:re_open_core_by_chain:

4596  Local / العربية (Arabic) / Re: موقع لحجز الطيران والفنادق on: February 18, 2020, 01:39:02 AM
بخصوص ال Virtual credit cards فأنا أنصح بموقع Coinsbee. بعد شراء البطاقة, سوف يتوجب عليك اعطاء

سوف اقوم بتحديث مشاركتي ووضع شرح مفصل لاحقا.

اتفق من هيوج, موضوع مخصص سكيون افضل , حسب ماقرات في الموقع الذي قمت بنشره هوا انهم يعطوك prepaid Visa Gift Card , والمشكلة مع هده البطاقات انها لا يتم قبولها في كل المواقع, لقد قمت بتجربة prepaid Visa Gift Card  كنت قد اشتريتها من امازون, وتم رفضها من بعض المواقع, اتذكر ان تم قبولها في موقع aliexpress ورفضها في اعلان ممول على Facebook تم رفضها ايضا من موقع اخر نسيت اسمه لان الموضوع مر عليه فترة.

لا ادري ان كانت البطاقات الافتراضية التي يعطيها هدا الموقع تختلف عن تلك الموجودة في امازون ام لا, على العموم انا جدا مهتم بقراءة الموضوع عند كتابته.
4597  Bitcoin / Development & Technical Discussion / Re: 51% Attack on: February 18, 2020, 01:11:19 AM
Gdp means nothing...sspecially when it is :

I find it amusing how you take a measurement scale that is well known and considered and say it means nothing, GDP PPP is not less important than nominal GDP,

Quote
GDP comparisons using PPP are arguably more useful than those using nominal GDP when assessing a nation's domestic market because PPP takes into account the relative cost of local goods, services and inflation rates of the country, rather than using international market exchange rates which may distort the real differences in per capita income.
https://en.wikipedia.org/wiki/List_of_countries_by_GDP_(PPP)


Quote
In 2007 US coughed twice., it sent the entire global economy to its deathbed.

Using GDP PPP china surpasses the U.S using the Nominal GDP China is not far from the U.S, taking share in world exports china has a much larger share, I don't understand why are you underestimating the economic strength of China. If China coughs twice it will also send the entire global economy to hell.

Quote
As others have said also, I stand by my opinion, why would be something that technical?
Raid coinbase with a SWAT team and from 3 billion in equipment you can do it with 10 million worth of it.  Wink

We are kind of going off-topic here ( a lot of economics) but I have a better argument to put us back on track, the U.S does not ban Bitcoin, they don't have a problem with it, China performs a 51%:Smiley

or both China and the U.S have no problem with Bitcoin but UAE, Saudi, Iran does, or even any other prince/king decides to play with 2-5 Billion Dollars (because he can)

Current hashrate is about 120 million TH , half that is 60  million TH that is 4,285,714 Antminer S9 or 4285714*80$ = $342,857,120 , or 1,090,909 T17+ (55th) *1000$ = $1,090,909,090 (slightly higher than 1 billion) and just about 2,000 megawatts worth of power, I am pretty sure a king or prince can spare 1 billion + maybe half a billion for infrastructure and 2,000 megawatt worth of electricity.

Attacking bitcoin for economic profit does not make sense, but attacking it for fun, experimental purposes or protecting one's economy makes a lot of sense, the above calculation is just an estimate, of course, if someone decides to buy that many gears they will cause gears prices to rise, but to what extent? another billion dollars? two? that much money is still pretty affordable to many countries and individuals around the globe, after the halving a huge chunk of that hash rate will leave the network for good and if the price does not moon, the attack will be a lot cheaper.

I find it really naive to think that X person won't do something in one way because Z person can do it in another way, ignoring the possibility of something happening is a terrible idea, IMO anything that has the slightest chance of happening must be discussed seriously and not ignored.
4598  Local / العربية (Arabic) / Re: بعض من روبوتات التداول الآلي on: February 17, 2020, 01:10:48 AM
( أن أستأجر مبرمج يعمل عمل حر بأن يصمم لي روبوت قائم على إستراتيجيتي الخاصة المبتكرة أو المقتبسة على مقاييسي الخاصة .. و هكذا أضمن أن لا يتم التلاعب في حال كان وارداً حدوث هذا الشيء و بالتالي أمان محفظتي أو حساباتي الشخصية ..

فكرة اكثر من رائعة ولكن كيف لك ان تظمن ان الشخص التي تقوم بالتعاقد معه والدفع له لكي يقوم بتصميم البوت الخاص بك بأن لا يقوم بسرقته او بيع نفس الكود لاشخاص اخرين دون علمك؟ لا اعتقد انه من السهل ايجاد حل لهده المشكلة والامر يتطلب من المستتمر بان يكون لديه خبرة كافية في مجال البرمجة ليجعل المبرمج يكتب له الكود بدون اي يعلم ماذا يكون وماذا يعمل, لايجد الوثوق في ان المصمم او المبرمج لن يقوم بسرقة مايعتقده "مجهوداته" حتى لو تقاضى اتعابه عليها مسبقا.
4599  Local / العربية (Arabic) / Re: بعض من روبوتات التداول الآلي on: February 16, 2020, 10:27:26 PM
يعني حسبما أعرف حتى تستخدم الربوت يجب ان تعطيه صلاحيات للوصول لكل حساباتك المختلفة في المنصات وهذا الموضوع يعتبر خطير جدا وغير آمن لأنه لو تعرض الربوت للاختراق مثلا أو كان الربوتوت نفسه غير موثوق فسوف يتم اختراق كامل حساباتك.

معظم المنصات ان لم يكن جميعها سواء كانت متخصصة بالكريبتو او الفوركس او البورصة تمنحك نوعان من الصلاحيات فيما يتعلق بالبوتات الخاصة بالتداول, ومعظها يكون الخيار الافتراضي فيها (تداول فقط) بحيث انه لايمكن باي حال من الاحوال للبوت ان يقوم بسحب اموالك الا ان سمحت له انت بذلك وهده الخاصية يستخدمها بعض الناس لاسباب قد يطول شرحها, ولكن يكفي ان تعرف ان استخدام البوت لايعرض اموالك للخسارة بطريقة سرقة الاموال في معظم الاحوال.

ولكن وبالرغم من هدا فان البوتات وخوصوصا في الكريبتو تعرضك للخسارة الغير مباشرة والتي تأتي من استخدام اموالك في عمليات ال pump and dump حيت ان مصمم البوت يقوم باستخدام حسابات الضحايا لشراء عملة ذات ماركت كاب منخفض بعد ان يكون قد اشتراها هوا بارخص الاثمان, ويبدا في رفع سعرها تدريجا عن طريق شراءها باستخدام البوت ومن ثم يبيع الكميات التي اشتراها للبوت ويخرج بمكسب كبير ويسبب خسارة للباقين.

طبعا هدا لايعني باي حال من الاحوال ان التداول باستخدام البوت غير مجدي , ولكن من وجهة نظري الاطريقة الوحيدة التي قد يكون فيها البوت ناجح هي عند تصميمه ليتماشى مع استراجيتك انت, اما البوتات التي يتم بيعها في العلن فمعضمها تخسر الاموال على المدى الطويل ولا انصح باستخدامها.

4600  Bitcoin / Development & Technical Discussion / Re: 51% Attack on: February 16, 2020, 08:16:35 PM
You're underestimating the power of the US and its influence, and this comes from an EU citizen, not some 2nd amendment freak.

I am not sure if I am underestimating their power or you are overestimating it, the U.S has been slapping sanctions on Russia, North Korea, Iran, China, Syria, well you name it, and the results are not as bad, the earth has not stopped spinning.



The projected results are even worse



But what do I know? I might be really "underestimating the power of the US"

Quote
Let's cut China out of the picture because you know that if the US sees BTC as a threat the Chinese would have gone with the ban already.

BTC could be more like a threat to the U.S dollar, this does not mean it has to be at the same level of threat to any other economy.

Quote
And since we're at 51% scenario, imagine how this "ban" or whatever it is called would affect the chain security...
We would be lucky if we would drop only to 1k in the first phase.

So you really think if the U.S bans bitcoin mining for an example, the rest of the world will do the same? Also, I would like to hear your comment about how would the U.S government go about banning bitcoin anyway, does their constitution give the government enough rights to do that?

Quote
How can you be prepared for this? Grin

First of all by admitting that a 51% attack on BTC is very possible, and is IMO the most powerful way to fight bitcoin, way more effective than simply trying to ban it.

As far as being technically prepared for such an attack, well I might be the worst person to be asked  Grin, but some interesting idea's like "the delayed block submission penalty." or "Komodo’s Delayed Proof of Work".

Other methods like increasing confirmations required by merchants and individuals, perhaps someone might make an automated system that sensors the migration of a large enough portion of hashrate (assuming the hash power that is used to perform the 51% has already been on the main blockchain),  community consensus to change the mining algothroim to a GPU-Only algthorim so if the attack happens it won't last long.

I don't know, those are off the top of my head, I am sure more intelligent people like yourself have better ways to prepare for such an attack rather than thinking that it simply won't happen:Smiley
Pages: « 1 ... 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 [230] 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 ... 406 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!