 Show Posts
|
|
Pages: [1]
|
|
Is there any way to stop the miner from going 100% on all fans during start up? Limiting it to like 30-50 would drastically improve home mining conditions.
|
|
|
|
|
Do we have an estimate of how much hashrate is sold by "cloud mining" contracts?
Providers shouldn't care about profitability, because the costs of electricity are already paid for, and even if they do for no amount of profitability decrease, or electricity cost increase will they be allowed to turn them off, because of the contract. So, I guess almost every contract made in the last ~2 years, keeps miners running at an unprofitable rates, though mostly to the detriment of the users, not providers.
Could this be a factor in the next few months?
|
|
|
|
Meanwhile, finally a nice drop: Latest Block: 737276 (15 minutes ago)
Current Pace: 95.9803% (1437 / 1497.18 expected, 60.18 behind)
Previous Difficulty: 29794407589312.08
Current Difficulty: 31251101365711.12
Next Difficulty: between 29995723257407 and 30095444125863
Next Difficulty Change: between -4.0171% and -3.6980%
Previous Retarget: May 11, 2022 at 1:40 AM (+4.8892%)
Next Retarget (earliest): Wednesday at 2:35 PM (in 4d 3h 22m 50s)
Next Retarget (latest): Wednesday at 3:45 PM (in 4d 4h 32m 29s)
Projected Epoch Length: between 14d 12h 54m 40s and 14d 14h 4m 19s
|
|
|
|
I stumbled on this sheet while browsing another forum: https://docs.google.com/spreadsheets/d/11hd-Q6KdkNETiRBs_JYwxOEAEfiEM4YoYad__grb5lE/edit?usp=sharingBasically, this is an attempt to calculate the cost of mining 1 btc for Marathon and Riot (the infamous big players). The numbers were surprising to me, and I've noticed some errors, like the hashrate was not 225 EH on average in Q1, and a little more bitcoins were produced than 900*90 since, I guess, when hashrate is constantly growing we have more blocks generated than expected 2016 per 2 weeks. This lowers final numbers by 10-15% but still way too high IMO. The SEC filings are useful, but I'm not familiar enough with the terms to be able to verify them. Anyway, thought it would be useful to share it here. |
|
|
|
While this is an altcoin kind of stuff, but it does affect BTC regardless of how anyone thinks, BTC as it stands right now is a high-risk speculative asset, the average joe and his grandmother don't really know the technical differences between a solid ecosystem like BTC and a shitcoin like Luna, and thus "confidence" is gone, and it will take time to recover what has been broken.
What I find also true, is that during this bull run, the average joe and his grandma heard about bitcoin, and learned that it did actually proved to be a good investment. We are going full bear now, but given the following recession, inflation, war, energy crisis, and whatever else, the next bull run could be the perfect storm of these events which could lead to grandmas buying btc. |
|
|
|
|
Are there any electricity price changes at your countries? It seems to me energy prices are only scheduled to go up (way up). Adding ridiculously increasing hashrate into the equation, things aren't looking good for miners, even S19-tier. This, apart from having tremendous impact on mining, obviously has even greater impact on the world economy, and can quite possibly trigger a recession, much like the one in 2008 in magnitude, which basically is the reason bitcoin exists.
I gotta say, it would be interesting observing recession, this time with bitcoin around. Also seeing whether my at home mining equipment turn to junk or a goose with the golden eggs.
|
|
|
|
|
I must say I'm suprised with certain statements in this thread.
If we want to pretend that blockchains are trustless decentralized ledgers shouldn't we be against censorship/prevention of usage from a large group with common properties of users? (ie users from Russia)
One key point of the word trustless should be that we can allow even bad actors inside the system. Enemies in a war could be perceived as, at most, bad actors (Russian citizens are not Putin). But the system is equal for both sides of war, and outcomes inside the system shouldn't be determined by the morality/just cause or any other philosophical factor. If it is, we end up with trustless decentralized
When I heard the news that Flexpool banned all russian IPs, I was appalled. If I had something like that happen to me, I would be very disappointed in crypto. This sure isn't a way to make it a global standard.
Correct me if I'm wrong but I don't recall anyone tried to stop nazis from mining gold, flagging their gold or any other counter measure in a system of value that is gold, during WWII. No one stopped them, after the war, from moving their fortunes to Argentina, Spain etc.
Disclaimer: I'm not from Russia, and I'm against the war.
|
|
|
|
Right now Antminer S9 in decent condition is available locally. I have some, but considering getting more. I am saving up for a M30S or S17 running somewhere around 40 W/Th. Used S17 prices seems to hover around 55 USD per Th and Whatsminer about 80 USD (but warranty included).
I think its better to buy efficient gear, even with cheap electricity like yours. You will certainly be able to mine longer in case of price fall/diff growth and the equipment itself will hold value for longer time. When those s9 become unprofitable at 6c, not much people would find them useful (except someone with free electricity), which will eventually make them worthless. With an s17 however, you will be able to mine longer or sell it. |
|
|
|
This is my chart showing btc hashrate (in black, left side scale) and USD/KWh rev (different colors, right side scale) for common mining equipment:  Same chart, but showing BTC/KWh rev:  1. Its significantly more efficient to mine eth, in usd/kwh rev (data since 22th nov 2021): | min s19 | max s19 | | 0.2064791667 | 0.4282730586 | | min 3080 | max 3080 | | 0.5406816123 | 1.35386456 |
which shows between 2.6 - 3.2 times more efficient to mine with common gpu (nvidia 3080) than common asic (s19 pro). 2. The drop in rev is bigger for eth mining (data since 22th nov 2021): Ratio in usd/kwh| min s19 | max s19 | % drop | | 0.2064791667 | 0.4282730586 | 51.78796272 | | min 3080 | max 3080 | % drop | | 0.5406816123 | 1.35386456 | 60.06383294 |
And possibly more important ratio in btc/kwh| min s19 | max s19 | % drop | | 0.000006233333333 | 0.0000075178571436 | 17.08630245 | | min 3080 | max 3080 | % drop | | 0.00001585144928 | 0.00002356702899 | 32.73887309 |
If we add up pros and cons we get that mining eth is cheaper gear, more profitable, less noisy, more reliable. While mining btc is more stable rev. If I was a big player I would go eth all the way, but the problem we didn't mention is eth 2.0. I guess we can't know for sure when it will happen, but gpu mining rev is going down after this, no doubt. Yes, there are other coins to mine, but lets face it, none of it is even close to eth. One scenario of eth 2.0 aftermath could be: - gpu mining rev going down 5-10x - btc mining rev starting to tumble downwards much more than now, since now big players are going all in on btc - near apocalyptic sell off of gpus All this if prices stay relatively stable, or stable against each other. If eth 2.0 further delays for lets say a year, even the next halving will be near and comes in to play. Wild. |
|
|
|
Latest Block: 719484 (5 minutes ago)
Current Pace: 108.6480% (1789 / 1646.60 expected, 142.4 ahead)
Previous Difficulty: 24272331996979.97
Current Difficulty: 24371874614345.62
Next Difficulty: between 26457891734489 and 26487003856870
Next Difficulty Change: between +8.5591% and +8.6786%
Previous Retarget: January 8, 2022 at 8:40 AM (+0.4101%)
Next Retarget (earliest): Friday at 5:56 AM (in 1d 10h 49m 18s)
Next Retarget (latest): Friday at 6:16 AM (in 1d 11h 9m 39s)
Projected Epoch Length: between 12d 21h 15m 20s and 12d 21h 35m 40s
Seems like it aggressive hashrate growth has stopped because diff estimation is now consolidated around 8.6% for at least 24h now. |
|
|
|
I wanted to wait for at least a month before sharing some results from my chart, but I had to share this now... the correlation between the new A11 pro and BTC hashrate is almost perfect (yellow and black). The values of asics are revenue in usd per kwh.  |
|
|
|
|
First of all, thanks for the merit (even though I don't know its use), and thanks for the explanations. I will, hopefully, be a better forum user from now on.
Second, to be back on the topic, the idea came to my mind reading philipma's posts here a few months ago, and stayed with me ever since. Right now I think its the perfect moment for it to be the real factor of hashrate change, given the energy crisis.
I've created a google sheet which monitors such mining parameters over time, like a few popular ASICs and GPUs revenue in usd per kwh, along with BTC hashrate, and display them on a single chart. All this using some open APIs available and google's neat http capabilities. This way we could observe changes depending on mining efficiency, and over 2-3 months, some insights could appear.
I will share it when its ready, and if its allowed here. Any thoughts?
|
|
|
|
I believe it's a combination of both, your theory is valid tho and phill has pointed that out a while back, altcoins mining gears make a lot more money than BTC mining gears when power is the only factor, but this can't be the only reason, because even the manufacturers that are not known to be making altcoins mining gears and focused mainly on BTC gears aren't making enough gears.
It is both, the question is whichever is greater problem, but regardless, this means we will probably be looking at a very low change in diff in next year or so, IMHO. P.S. My post got deleted, I dont know why, I'm new here but I'm open for guidance on what I did wrong. |
|
|
|
Those chip temps on board #2 look pretty high compared to pcb temp and other boards... |
|
|
|
|
It seems that one of your hashboards has decent temperature, so possibly the other two could have heatsinks fallen off. Or the fans aren't blowing in the right direction.
|
|
|
|
|
On another note, I plan to underclock my T17 so it uses less power and makes less noise so it will be more acceptable for home mining. When I underlocked it and set power consumption to around 1200W (half of the original), I noticed that the PSU (APW9) is barely getting any heat but the fans are still pretty loud. Is there any way to slow down these small fans? Also, is there any heat sensor in the APW9? I don't wanna mess with it if it will make it unsafe, like fire hazard.
|
|
|
|
Best option is to find an experienced repair shop.
Thanks, I'll probably do that. This problem could also be caused by a bad PSU, do you have another PSU to test with?
No, unfortunately not. I guess it could be the soldier or a burnt chip, although, could there be a log of "find 30 asic" even with a burnt chip? Seems kinda contradictory. |
|
|
|
I have an issue with my T17, one just 1 hashboard. Sometimes i get 0 asic found sometimes it finds all 30. But in any case, I get the error for all temp sensors on the board. I think I've went through most of the posts here and it most likely resembles the issue I quoted below. As I could see, most likely its loose heatsink, but after my (inexperienced) inspection, none seems loose when tested with mild pressure. Can anyone point me to some diy fix (I have only solder, no heatgun) or just take it to the repair shop? Here are the logs: When finding all asics:2021-10-14 17:42:05 driver-btm-api.c:631:init_freq_mode: This is scan-user version
2021-10-14 17:42:05 driver-btm-api.c:1994:bitmain_soc_init: opt_multi_version = 1
2021-10-14 17:42:05 driver-btm-api.c:1995:bitmain_soc_init: opt_bitmain_ab = 1
2021-10-14 17:42:05 driver-btm-api.c:1996:bitmain_soc_init: opt_bitmain_work_mode = 0
2021-10-14 17:42:05 driver-btm-api.c:1997:bitmain_soc_init: Miner compile time: Tue Dec 24 16:13:07 CST 2019 type: Antminer T17
2021-10-14 17:42:05 driver-btm-api.c:1998:bitmain_soc_init: commit version: e93a09b 2019-12-24 16:03:45, build by: lol 2019-12-24 16:19:49
2021-10-14 17:42:05 driver-btm-api.c:1810:show_sn: no SN got, please write SN to /nvdata/sn
2021-10-14 17:42:05 driver-btm-api.c:1135:miner_device_init: Detect 256MB control board of XILINX
2021-10-14 17:42:05 driver-btm-api.c:1083:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2021-10-14 17:42:05 thread.c:789:create_read_nonce_reg_thread: create thread
2021-10-14 17:42:11 driver-btm-api.c:1067:init_miner_version: miner ID : 803c95042b104814
2021-10-14 17:42:11 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2021-10-14 17:42:13 eeprom.c:431:check_pattern_test_level: L1 board
2021-10-14 17:42:15 eeprom.c:431:check_pattern_test_level: L1 board
2021-10-14 17:42:16 eeprom.c:431:check_pattern_test_level: L1 board
2021-10-14 17:42:16 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2021-10-14 17:42:16 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2021-10-14 17:42:16 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2021-10-14 17:42:16 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2021-10-14 17:42:16 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2021-10-14 17:42:16 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2021-10-14 17:42:16 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2021-10-14 17:42:16 driver-btm-api.c:644:_set_project_type: project:2
2021-10-14 17:42:17 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2021-10-14 17:42:17 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2021-10-14 17:42:17 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2021-10-14 17:42:17 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2021-10-14 17:42:17 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2021-10-14 17:42:17 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2021-10-14 17:42:17 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2021-10-14 17:42:18 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2021-10-14 17:42:19 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2021-10-14 17:42:23 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2021-10-14 17:42:24 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2021-10-14 17:42:28 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2021-10-14 17:42:30 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2021-10-14 17:42:33 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2021-10-14 17:42:33 thread.c:784:create_pic_heart_beat_thread: create thread
2021-10-14 17:42:33 power_api.c:55:power_init: power init ...
2021-10-14 17:42:33 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2021-10-14 17:43:05 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2021-10-14 17:43:11 power_api.c:124:check_voltage_multi: retry time: 0
2021-10-14 17:43:13 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.677236
2021-10-14 17:43:14 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.120039
2021-10-14 17:43:16 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.917978
2021-10-14 17:43:16 power_api.c:97:get_average_voltage: aveage voltage is: 17.238418
2021-10-14 17:43:16 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2021-10-14 17:43:16 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2021-10-14 17:43:16 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2021-10-14 17:43:16 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2021-10-14 17:43:16 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2021-10-14 17:43:28 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2021-10-14 17:43:38 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2021-10-14 17:43:48 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2021-10-14 17:43:51 driver-btm-api.c:348:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2021-10-14 17:43:51 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2021-10-14 17:43:52 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2021-10-14 17:43:52 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2021-10-14 17:43:52 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2021-10-14 17:43:52 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2021-10-14 17:43:52 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2021-10-14 17:43:52 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2021-10-14 17:43:52 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2021-10-14 17:43:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2021-10-14 17:43:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2021-10-14 17:43:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2021-10-14 17:43:53 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2021-10-14 17:43:53 voltage[0] = 1690
2021-10-14 17:43:53 voltage[1] = 1690
2021-10-14 17:43:53 voltage[2] = 1690
2021-10-14 17:43:53 power_api.c:140:set_working_voltage: working_voltage = 16.900000
2021-10-14 17:43:54 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2021-10-14 17:43:55 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2021-10-14 17:43:57 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2021-10-14 17:43:57 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2021-10-14 17:43:57 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2021-10-14 17:43:57 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2021-10-14 17:43:57 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2021-10-14 17:43:59 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 21
2021-10-14 17:43:59 thread.c:804:create_check_miner_status_thread: create thread
2021-10-14 17:43:59 thread.c:794:create_set_miner_status_thread: create thread
2021-10-14 17:43:59 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2021-10-14 17:43:59 thread.c:779:create_temperature_monitor_thread: create thread
2021-10-14 17:43:59 freq_tuning.c:154:freq_tuning_get_max_freq: Max freq of tuning is 760
2021-10-14 17:43:59 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 17.80 ...
2021-10-14 17:44:33 power_api.c:124:check_voltage_multi: retry time: 0
2021-10-14 17:44:35 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.781328
2021-10-14 17:44:37 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.769082
2021-10-14 17:44:39 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.744590
2021-10-14 17:44:39 power_api.c:97:get_average_voltage: aveage voltage is: 17.765000
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 44 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 7, usr divider: 1
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 51 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 6, usr divider: 1
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 61 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 5, usr divider: 1
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 77 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 4, usr divider: 1
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 102 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 3, usr divider: 1
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 154 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 2, usr divider: 1
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 308 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 1, usr divider: 1
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 360 set refdiv: 2, fbdiv: 173, postdiv1: 6, postdiv2: 1, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 432 set refdiv: 2, fbdiv: 173, postdiv1: 5, postdiv2: 1, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 540 set refdiv: 2, fbdiv: 173, postdiv1: 4, postdiv2: 1, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 720 set refdiv: 2, fbdiv: 173, postdiv1: 3, postdiv2: 1, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 44 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 7, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 51 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 6, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 61 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 5, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 77 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 4, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 102 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 3, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 154 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 2, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 308 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 1, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 360 set refdiv: 2, fbdiv: 173, postdiv1: 6, postdiv2: 1, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 432 set refdiv: 2, fbdiv: 173, postdiv1: 5, postdiv2: 1, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 540 set refdiv: 2, fbdiv: 173, postdiv1: 4, postdiv2: 1, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 720 set refdiv: 2, fbdiv: 173, postdiv1: 3, postdiv2: 1, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 44 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 7, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 51 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 6, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 61 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 5, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 77 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 4, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 102 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 3, usr divider: 1
2021-10-14 17:44:42 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 154 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 2, usr divider: 1
2021-10-14 17:44:42 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 308 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 1, usr divider: 1
2021-10-14 17:44:42 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 360 set refdiv: 2, fbdiv: 173, postdiv1: 6, postdiv2: 1, usr divider: 1
2021-10-14 17:44:42 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 432 set refdiv: 2, fbdiv: 173, postdiv1: 5, postdiv2: 1, usr divider: 1
2021-10-14 17:44:42 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 540 set refdiv: 2, fbdiv: 173, postdiv1: 4, postdiv2: 1, usr divider: 1
2021-10-14 17:44:42 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 720 set refdiv: 2, fbdiv: 173, postdiv1: 3, postdiv2: 1, usr divider: 1
2021-10-14 17:44:42 driver-btm-api.c:612:set_timeout: freq 720 final timeout=163
2021-10-14 17:44:42 power_api.c:397:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 16.90 ...
2021-10-14 17:44:48 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 0
2021-10-14 17:45:01 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 1
2021-10-14 17:45:07 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 0
2021-10-14 17:45:17 power_api.c:124:check_voltage_multi: retry time: 0
2021-10-14 17:45:19 power_api.c:86:get_average_voltage: chain[0], voltage is: 16.783271
2021-10-14 17:45:20 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 1
2021-10-14 17:45:21 power_api.c:86:get_average_voltage: chain[1], voltage is: 16.771025
2021-10-14 17:45:22 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.979209
2021-10-14 17:45:22 power_api.c:97:get_average_voltage: aveage voltage is: 16.844502
2021-10-14 17:45:22 frequency.c:540:get_current_min_freq: current min freq 720
2021-10-14 17:45:22 driver-btm-api.c:1660:check_clock_counter: freq 720 clock_counter_limit 92
2021-10-14 17:45:27 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 0
2021-10-14 17:45:40 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 1
2021-10-14 17:45:47 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 0
2021-10-14 17:46:00 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 1
2021-10-14 17:46:04 register.c:1416:quick_dump_core_hash_clock_counter: bad clock counter. chain = 0, asic = 5, core = 0, found 0, clock counter 0x00000000
2021-10-14 17:46:04 driver-btm-api.c:2097:bitmain_soc_init: clock count check failed after retry, wait for hash rate protect later.
2021-10-14 17:46:04 thread.c:799:create_check_system_status_thread: create thread
2021-10-14 17:46:04 driver-btm-api.c:2113:bitmain_soc_init: Init done!
2021-10-14 17:46:04 driver-btm-api.c:201:set_miner_status: STATUS_INIT
2021-10-14 17:46:09 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2021-10-14 17:46:10 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 0
2021-10-14 17:46:14 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4
2021-10-14 17:46:24 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 1
2021-10-14 17:46:30 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 0
2021-10-14 17:46:43 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 1
2021-10-14 17:46:50 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 0
2021-10-14 17:47:03 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 1
2021-10-14 17:47:09 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 0
2021-10-14 17:47:23 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 1
2021-10-14 17:47:31 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 0
2021-10-14 17:47:44 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 1
2021-10-14 17:47:51 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 0
2021-10-14 17:48:04 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 1
2021-10-14 17:48:11 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 0
2021-10-14 17:48:24 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 1
2021-10-14 17:48:30 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 0
2021-10-14 17:48:43 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 1
2021-10-14 17:48:52 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 0
2021-10-14 17:49:05 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 1
2021-10-14 17:49:12 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 0
2021-10-14 17:49:25 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 1
2021-10-14 17:49:31 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 0
2021-10-14 17:49:44 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 1
2021-10-14 17:49:51 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 0
2021-10-14 17:50:04 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 1
2021-10-14 17:50:13 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 0
2021-10-14 17:50:26 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 1
2021-10-14 17:50:32 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 0
2021-10-14 17:50:46 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 1
2021-10-14 17:50:52 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 0
2021-10-14 17:51:05 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 1
2021-10-14 17:51:12 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 0
2021-10-14 17:51:13 thread.c:422:is_zero_nonce_happened: chain_nonce[0] = 0
2021-10-14 17:51:13 thread.c:422:is_zero_nonce_happened: chain_nonce[1] = 15697
2021-10-14 17:51:13 thread.c:422:is_zero_nonce_happened: chain_nonce[2] = 15686
2021-10-14 17:51:13 thread.c:539:check_system_work_thread: 0 nonce rate happened after retry, wait for hash rate protect later.
2021-10-14 17:51:25 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 1
2021-10-14 17:51:33 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 0 2021-10-14 17:24:48 driver-btm-api.c:631:init_freq_mode: This is scan-user version
2021-10-14 17:24:48 driver-btm-api.c:1994:bitmain_soc_init: opt_multi_version = 1
2021-10-14 17:24:48 driver-btm-api.c:1995:bitmain_soc_init: opt_bitmain_ab = 1
2021-10-14 17:24:48 driver-btm-api.c:1996:bitmain_soc_init: opt_bitmain_work_mode = 0
2021-10-14 17:24:48 driver-btm-api.c:1997:bitmain_soc_init: Miner compile time: Tue Dec 24 16:13:07 CST 2019 type: Antminer T17
2021-10-14 17:24:48 driver-btm-api.c:1998:bitmain_soc_init: commit version: e93a09b 2019-12-24 16:03:45, build by: lol 2019-12-24 16:19:49
2021-10-14 17:24:48 driver-btm-api.c:1810:show_sn: no SN got, please write SN to /nvdata/sn
2021-10-14 17:24:48 driver-btm-api.c:1135:miner_device_init: Detect 256MB control board of XILINX
2021-10-14 17:24:48 driver-btm-api.c:1083:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2021-10-14 17:24:48 thread.c:789:create_read_nonce_reg_thread: create thread
2021-10-14 17:24:54 driver-btm-api.c:1067:init_miner_version: miner ID : 803c95042b104814
2021-10-14 17:24:54 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2021-10-14 17:24:56 eeprom.c:431:check_pattern_test_level: L1 board
2021-10-14 17:24:58 eeprom.c:431:check_pattern_test_level: L1 board
2021-10-14 17:24:59 eeprom.c:431:check_pattern_test_level: L1 board
2021-10-14 17:24:59 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2021-10-14 17:24:59 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2021-10-14 17:24:59 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2021-10-14 17:24:59 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2021-10-14 17:24:59 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2021-10-14 17:24:59 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2021-10-14 17:24:59 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2021-10-14 17:24:59 driver-btm-api.c:644:_set_project_type: project:2
2021-10-14 17:24:59 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2021-10-14 17:24:59 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2021-10-14 17:24:59 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2021-10-14 17:24:59 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2021-10-14 17:24:59 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2021-10-14 17:24:59 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2021-10-14 17:24:59 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2021-10-14 17:24:59 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2021-10-14 17:25:01 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2021-10-14 17:25:05 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2021-10-14 17:25:06 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2021-10-14 17:25:10 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2021-10-14 17:25:12 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2021-10-14 17:25:15 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2021-10-14 17:25:15 thread.c:784:create_pic_heart_beat_thread: create thread
2021-10-14 17:25:15 power_api.c:55:power_init: power init ...
2021-10-14 17:25:15 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2021-10-14 17:25:47 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2021-10-14 17:25:53 power_api.c:124:check_voltage_multi: retry time: 0
2021-10-14 17:25:54 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.003701
2021-10-14 17:25:56 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.003701
2021-10-14 17:25:58 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963
2021-10-14 17:25:58 power_api.c:97:get_average_voltage: aveage voltage is: 16.991455
2021-10-14 17:25:58 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2021-10-14 17:25:58 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2021-10-14 17:25:58 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2021-10-14 17:25:58 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2021-10-14 17:25:58 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2021-10-14 17:26:09 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 0
2021-10-14 17:26:19 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 1
2021-10-14 17:26:29 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 2
2021-10-14 17:26:29 driver-btm-api.c:1037:check_asic_number: Chain 0 only find 0 asic, will power off hash board 0
2021-10-14 17:26:41 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2021-10-14 17:26:51 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2021-10-14 17:26:54 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2021-10-14 17:26:54 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2021-10-14 17:26:54 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2021-10-14 17:26:54 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2021-10-14 17:26:54 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2021-10-14 17:26:54 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2021-10-14 17:26:54 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2021-10-14 17:26:55 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2021-10-14 17:26:55 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2021-10-14 17:26:55 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2021-10-14 17:26:55 voltage[1] = 1690
2021-10-14 17:26:55 voltage[2] = 1690
2021-10-14 17:26:55 power_api.c:140:set_working_voltage: working_voltage = 16.900000
2021-10-14 17:26:56 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2021-10-14 17:26:57 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2021-10-14 17:26:57 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2021-10-14 17:26:57 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2021-10-14 17:26:57 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2021-10-14 17:26:59 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 25
2021-10-14 17:26:59 thread.c:804:create_check_miner_status_thread: create thread
2021-10-14 17:26:59 thread.c:794:create_set_miner_status_thread: create thread
2021-10-14 17:26:59 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2021-10-14 17:26:59 thread.c:779:create_temperature_monitor_thread: create thread
2021-10-14 17:26:59 freq_tuning.c:154:freq_tuning_get_max_freq: Max freq of tuning is 760
2021-10-14 17:26:59 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 17.80 ...
2021-10-14 17:27:30 power_api.c:124:check_voltage_multi: retry time: 0
2021-10-14 17:27:33 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.781328
2021-10-14 17:27:36 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.769082
2021-10-14 17:27:36 power_api.c:97:get_average_voltage: aveage voltage is: 17.775205
2021-10-14 17:27:36 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 44 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 7, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 51 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 6, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 61 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 5, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 77 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 4, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 102 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 3, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 154 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 2, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 308 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 1, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 360 set refdiv: 2, fbdiv: 173, postdiv1: 6, postdiv2: 1, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 432 set refdiv: 2, fbdiv: 173, postdiv1: 5, postdiv2: 1, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 540 set refdiv: 2, fbdiv: 173, postdiv1: 4, postdiv2: 1, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 720 set refdiv: 2, fbdiv: 173, postdiv1: 3, postdiv2: 1, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 44 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 7, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 51 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 6, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 61 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 5, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 77 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 4, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 102 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 3, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 154 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 2, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 308 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 1, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 360 set refdiv: 2, fbdiv: 173, postdiv1: 6, postdiv2: 1, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 432 set refdiv: 2, fbdiv: 173, postdiv1: 5, postdiv2: 1, usr divider: 1
2021-10-14 17:27:39 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 540 set refdiv: 2, fbdiv: 173, postdiv1: 4, postdiv2: 1, usr divider: 1
2021-10-14 17:27:39 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 720 set refdiv: 2, fbdiv: 173, postdiv1: 3, postdiv2: 1, usr divider: 1
2021-10-14 17:27:39 driver-btm-api.c:612:set_timeout: freq 720 final timeout=163
2021-10-14 17:27:39 power_api.c:397:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 16.90 ...
2021-10-14 17:27:58 thread.c:642:check_temperature: over max temp, pcb temp 59 (max 80), chip temp 106(max 103)
2021-10-14 17:27:58 driver-btm-api.c:201:set_miner_status: ERROR_TEMP_TOO_HIGH
2021-10-14 17:27:58 driver-btm-api.c:142:stop_mining: stop mining: over max temp
2021-10-14 17:27:58 thread.c:824:cancel_temperature_monitor_thread: cancel thread
2021-10-14 17:27:58 thread.c:834:cancel_read_nonce_reg_thread: cancel thread
2021-10-14 17:27:58 driver-btm-api.c:128:killall_hashboard: ****power off hashboard****
2021-10-14 17:28:09 power_api.c:124:check_voltage_multi: retry time: 0
2021-10-14 17:28:11 power_api.c:86:get_average_voltage: chain[1], voltage is: 16.948594
2021-10-14 17:28:13 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.205762
2021-10-14 17:28:13 power_api.c:97:get_average_voltage: aveage voltage is: 17.077178
2021-10-14 17:28:13 frequency.c:540:get_current_min_freq: current min freq 720
2021-10-14 17:28:13 driver-btm-api.c:1660:check_clock_counter: freq 720 clock_counter_limit 92
2021-10-14 17:28:16 register.c:1416:quick_dump_core_hash_clock_counter: bad clock counter. chain = 1, asic = 5, core = 0, found 0, clock counter 0x00000000
2021-10-14 17:28:16 driver-btm-api.c:2097:bitmain_soc_init: clock count check failed after retry, wait for hash rate protect later.
2021-10-14 17:28:16 thread.c:799:create_check_system_status_thread: create thread
2021-10-14 17:28:16 driver-btm-api.c:2113:bitmain_soc_init: Init done!
2021-10-14 17:28:16 driver-btm-api.c:201:set_miner_status: STATUS_INIT
2021-10-14 17:28:21 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2021-10-14 17:28:25 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4 I wouldnt want to use any permeneatny adhesive. Im looking to apply solder. What solder do you know I can use for this that can be taken off and on. Also I have a whole bunch of boards that have the same exact errors when I run the test fixture. All the asic are found but I still get a temp sensor error. 1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:53 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 14, reg = 1
...
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:54 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 10, reg = 1
...
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:55 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 54, reg = 1
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
...
1970-01-01 00:01:56 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 50, reg = 1
1970-01-01 00:01:56 single_board_test.c:1659:wait_warm_up: temper sensor bad
I have this same exact error for over 10 boards. Also the the error states chip 50, 54, 10, 14 as being bad chips but I get this same exact error on many boards. Cant all have the same exact chips with the same exact error. What could this be? My boards are in 100% perfect condition and all the sudden stopped working one day. Showed temp sensor errors and then stopped working completely. Running this test fixture is showing temo sensor is bad but that cant be either. Something is wrong and I dont know how to find the problem. Please advise. Thank you. |
|
|
|
These links are not working anymore. Does anyone know a safe source where I can find the firmware? |
|
|
|
I've spent some time looking into this coin. I like the concept, I like their website but it lacks many important features:
- No way to password encrypt your wallet
- Plots are linked to your wallet so if it gets compromised you have to redirect transactions
- It's unclear what security audits they did on their nodes. Are they susceptible to buffer overflow attacks or something else?
- The GUI itself is nice and modern, but lacks basic features like ability to stop/pause a plotting node (no resume). It also lacks any ability to predict plot time and any decent HT support. The CLI is basic, just like most cryptos but also lacks any of this.
The complexity has gone through the roof in just 1.5 months. Currently at 1.5 EiB and growing 10% every couple days. With 20 plots (2TB) it will take you 6 months to win anything. In a couple weeks that will be a couple years.
Plots themselves are very compute intensive. Not sure why they'd ever say this is green. A decent gaming system could do 10 plots/day. Unless you have a server with 32+ cores, enterprise NVMe SSD (or a huge parallel raid setup) you're not going to plot fast enough to catch-up with the increased complexity.
Now all of these are concerns and in some cases showstoppers for small-time miners. The real showstopper, however. The one that completely breaks this is that for whatever reason Bram and his cohort decided to premine 21 million coins. Whereas right now there is <500k coins out for CHIA miners to win. It's estimated over 25 years CHIA miners can win 21 million coins. These coins cost *nothing* for the chia corporation to create, yet they are going to instantaneously have these coins. Now their business whitepaper says they'll have a board that will decide when/if to sell the coins. 90 days notice will be given to everyone when it happens etc.... This is what the chia community says to justify this huge slice of chia pie given to the developers. This really doesn't fly well and beckons back to the early days of altcoins when developers would allocate 90% of the coins for themselves and a mere 10% for the community. Then instant dump when they get the chance. Chia can put this under the banner of a corporation if they want but it's astounding that they, and the chia miners themselves think this is even a close to fair idea.
So a 98% early premine, complexity pushing through the roof, and questionable miner support. This is an interesting coin to experiment with but I'd pass for now.
Yea, I liked the coin but when I saw 21 million premine I was like wtf?? I guess that 90% of the people getting onboard in the last few days don't know this. Nevertheless, I still think they will get a decent launch price and volume on EXs. The hype is real and currently it looks easier to buy chia for 20$ than to mine it. |
|
|
|
|
