Pages:
Author

Topic: T17/S17 malfunction: cases, solutions, remedies, RMA history - page 3. (Read 6919 times)

newbie
Activity: 20
Merit: 0
Hello guys, just had a small rig of gpus since 2018.  Have a opportunity to buy a couple of s17 for great price. But doing some research I seen they have a fire hazard, heatsink problems, weak psu, and faulty fans. my buddy said stay away.

If i decided to get them and wanted to overclock them what can I do to reduce risk? Get new power supply, new fan, new heatsink? I have background in computers from the 90s, i put together and taken apart many pc, cpus, heatsinks, fixed or upgraded everything at one time or another over the years.

Also for overclocking i was wondering what firmwares are legit? (ascii.to (the moon))?  I like to hear good and bad from actual users to make informed decision.
 
Thanks guys.
sr. member
Activity: 446
Merit: 347
Yes, without any problem, just swap original fan by slower fan, i make 8000trs fan, and run good !!! (underclock to, on 35 th)
newbie
Activity: 20
Merit: 25
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.
hero member
Activity: 544
Merit: 589

It's a gamble. I think the quality control just wasn't good enough for all these 17 series miners to get a reliably good product, but it seems like some batches were fine, others were horrible. I have 10 S17s that came directly from Bitmain in one batch and haven't had a single one go down. Been running for nearly 2 years. Got 7 s17 pros in another batch from Malaysia and had issues with 3 out of 7 in under a year.

So could go either way. With used miners, if they've been solidly running with no issues they may be good and the original owners were the ones that took the risk. Or it could be every single miner they are selling had issues and it's just a matter of time before they start failing.

I'd just go into it assuming 25% of the hashboards will die. Make sure the #s make sense with that assumption. Consolidate working hashboards into fully working miners and either sell the bad boards for parts or see if you can find a repair shop.

newbie
Activity: 14
Merit: 0
Sooo bringing in $50k worth of T17's 42Th/s is starting to look/sound like a bad idea....

Am I in for a world of pain? - No, I haven't bought them yet.
legendary
Activity: 2170
Merit: 6279
be constructive or S.T.F.U
Whoah, so running a big farm like that easily becomes your full time job if you can also do repairing yourself

I think the type of mining gears running at the farm will determine whether this becomes feasible or not, if the farm is full of 17 series gears, well, then probably a dozen technicians can do that full-time, if it's other robust gears, the amount of work needed could be extremely low.

If I charged enough to make it worth my time I'd be even more expensive than the overpriced services already listed...

Makes sense.

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.

If the chips are burnt then they are burnt, the kernel log won't show 30 asics at times and 0 in the others, however, if it's just a bad solder connection then it's pretty normal for the hash board to show 30 asics and then maybe 24 and then 0, I personally managed to fix a few hash boards by freezing them in the freezer, the freezing did something to that solder joint and fixed it, so ya, it's pretty normal for that to happen.
newbie
Activity: 20
Merit: 25
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.
hero member
Activity: 544
Merit: 589
I'd imagine so. I don't run a big farm but nearly all this dead gear I have I bought from a large farm that shut down last year. They had full-time technicians to repair miners but when they shut down they had piles of dead gear that the technicians either didn't get to or couldn't repair.
legendary
Activity: 2422
Merit: 1706
Electrical engineer. Mining since 2014.
Whoah, so running a big farm like that easily becomes your full time job if you can also do repairing yourself
hero member
Activity: 544
Merit: 589
Thanks, but I have no interest in repairing miners as a service. If I charged enough to make it worth my time I'd be even more expensive than the overpriced services already listed...

Still have >100 dead hashboards of my own to repair anyway which will probably take me more than a year to get through.
legendary
Activity: 2170
Merit: 6279
be constructive or S.T.F.U
Welcome back man, you went missing for quite a while, by the way, if you are interested, I could add your name here > https://bitcointalksearch.org/topic/where-to-fix-your-asic-miners-5297994, you are the most experienced member in fixing these hash boards, trusted and can probably do better than most of those overpriced services listed, check it out and let me know.




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.

It's more like a bad chip connection than just a loose heatsink, in fact, if the heatsink isn't shorting anything, the miner will still run for a very short while before showing "Over-Temp", but getting the temp sensors errors is probably because of a dead/burnt chip or a bad connection between one of the chip and PCB.

This problem could also be caused by a bad PSU, do you have another PSU to test with?
hero member
Activity: 544
Merit: 589
...

I wouldn't really recommend trying to fix yourself. Removing/replacing heatsinks and chips on these hashboards is not easy, and without lots of practice, you'd probably just create more issues.

You can search back through this thread to find some potential remedies that may get the board up at least temporarily. Changing the temperature and/or orientation of the miner can sometimes close broken solder joints or open shorts caused by excess solder on the board. In my experience, these are the most likely causes.

Best option is to find an experienced repair shop.
newbie
Activity: 20
Merit: 25
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:
Code:
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

When no asics found on board 1:

Code:
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.

Code:
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.
newbie
Activity: 10
Merit: 2
yeh, I'm a mining newbie and I haven't though about the problems associate with the miners S17.

The turn off to buy the S19 was the price, they are selling for 15K and the S17 for 5k ... so for me was a no brainer LOL

maybe I sell it as soon I get them.
legendary
Activity: 2170
Merit: 6279
be constructive or S.T.F.U
OMG, I have order and pay for a used S17+ from alibaba, I'm already scared what gonna append....


Buy first and then do your research, way to go, my friend. Cheesy

Quote
Any thoughts how to prevent the heat sinks from falling?

Try to keep them cool that will help.

Quote
Maybe laying the miner sideways instead upward? 

some folks reported some tiny percentage of success by placing them horizontally, I'd say it's a fraction of an effect but well, why not? just make sure you place the chips up, the larger heatsink needs to face up.
newbie
Activity: 10
Merit: 2
OMG, I have order and pay for a used S17+ from alibaba, I'm already scared what gonna append....

Any thoughts how to prevent the heat sinks from falling?
Any solutions for this problem?

Maybe laying the miner sideways instead upward? 
hero member
Activity: 544
Merit: 589
My experience repairing these so far has shown that the faulty miners typically have multiple issues, and all the issues don't always present themselves. I run miners several days after a repair to make sure they are stable, and nearly 100% of the time they fail again, normally in different ways, within a few days. So not surprised to see a lot of reports of "repaired" miners arriving broken.
newbie
Activity: 16
Merit: 15
Haha, same at my side. I sent 5 dead S17 to Bitmain during October and now, more than half year later they sent me 1 working and two dead units. I'll repair them by myself.
member
Activity: 61
Merit: 29
[...]

I just wanted to give you a status update.

After I sent my defective miner to Bitmain on October 29th, a replacement device was sent to me from Hong Kong today. That was fast!!! I hope the device works longer.

I have already bought the M30 + and M30 ++, they have been running without any problems so far and I am satisfied with them. From Bitmain, I will keep my distance first, have had too many defective devices (S17 +).
hero member
Activity: 544
Merit: 589
Dear Mr. wndsnb, can you tell me from which country

I'm from east coast USA, but I can't promise quick responses.... I'm pretty busy these days. I respond when I can find time....
Pages:
Jump to: