Title: T17 soc init failed Post by: WesleyHA on November 01, 2021, 01:19:45 PM Hello guys,
I recently bought a batch of T17, but with almost all of them i got the same unexplainable error, 2021-11-01 13:05:27 driver-btm-api.c:663:init_freq_mode: This is scan-user version 2021-11-01 13:05:27 driver-btm-api.c:2028:bitmain_soc_init: opt_multi_version = 1 2021-11-01 13:05:27 driver-btm-api.c:2029:bitmain_soc_init: opt_bitmain_ab = 1 2021-11-01 13:05:27 driver-btm-api.c:2030:bitmain_soc_init: opt_bitmain_work_mode = 2 2021-11-01 13:05:27 driver-btm-api.c:2031:bitmain_soc_init: Miner compile time: Thu Apr 23 16:29:07 CST 2020 type: Antminer T17 2021-11-01 13:05:27 driver-btm-api.c:2032:bitmain_soc_init: commit version: 1c5be6f 2020-04-20 16:18:14, build by: lol 2020-04-23 16:35:04 2021-11-01 13:05:27 driver-btm-api.c:1844:show_sn: no SN got, please write SN to /nvdata/sn 2021-11-01 13:05:27 driver-btm-api.c:1167:miner_device_init: Detect 256MB control board of XILINX 2021-11-01 13:05:27 driver-btm-api.c:1115:init_fan_parameter: fan_eft : 0 fan_pwm : 0 2021-11-01 13:05:27 thread.c:885:create_read_nonce_reg_thread: create thread 2021-11-01 13:05:33 driver-btm-api.c:1099:init_miner_version: miner ID : 80344dca7910481c 2021-11-01 13:05:33 driver-btm-api.c:1105:init_miner_version: FPGA Version = 0xB013 2021-11-01 13:05:33 driver-btm-api.c:1897:bitmain_board_init: ERROR: None of the chains exist 2021-11-01 13:05:33 driver-btm-api.c:205:set_miner_status: ERROR_SOC_INIT 2021-11-01 13:05:33 driver-btm-api.c:146:stop_mining: stop mining: soc init failed! 2021-11-01 13:05:33 thread.c:930:cancel_read_nonce_reg_thread: cancel thread 2021-11-01 13:05:33 driver-btm-api.c:131:killall_hashboard: ****power off hashboard**** 2021-11-01 13:05:33 power_api.c:46:power_off: init gpio907 I've swapped hashboards, controlboards, flashed stock firmware and vnish. with an SD and in the interface. but nothing seems to work. Does anyone know more about this topic? Thanks for your time, Wesley Title: Re: T17 soc init failed Post by: WesleyHA on November 02, 2021, 01:51:10 PM For the people still reading this, switching to vnish and using asicboost nicehash pools solved the problem for me.
Title: Re: T17 soc init failed Post by: Andrew1981 on March 17, 2022, 03:39:03 PM When your antminer T17 is reading 'soc connect failed , kill all hashboard. It is usually because one or more of your heat sink is lose but has not fallen off yet. So you need to detach the lose heat sink and use super glue to fix it properly. If my suggestion helps you and you want to donate bitcoins to me, please send it to this address:
36Erg6tTtLjeRcc812KVF96Y4W4ZiqH7pn Title: Re: T17 soc init failed Post by: BitMaxz on March 17, 2022, 04:00:56 PM So you need to detach the lost heat sink and use super glue to fix it properly. There is no super glue that you can use to reattached the ASIC heatsink I'm sure it will burn and lose right away after ASIC chips get hot. You need a proper glue or adhesive that can withstand high temperature like arctic silver. Title: Re: T17 soc init failed Post by: thierry4wd on March 17, 2022, 05:23:36 PM When your antminer T17 is reading 'soc connect failed , kill all hashboard. It is usually because one or more of your heat sink is lose but has not fallen off yet. So you need to detach the lose heat sink and use super glue to fix it properly. If my suggestion helps you and you want to donate bitcoins to me, please send it to this address: 36Erg6tTtLjeRcc812KVF96Y4W4ZiqH7pn NO , this message " 2021-11-01 13:05:33 driver-btm-api.c:205:set_miner_status: ERROR_SOC_INIT " group all problem, temp sensor, bad chip, bad pool, pool dead... I see : " 2021-11-01 13:05:33 driver-btm-api.c:1897:bitmain_board_init: ERROR: None of the chains exist " ... SO ! need check ALL the ribon cable ! or maybe psu . Title: Re: T17 soc init failed Post by: tornado_blade on April 06, 2022, 09:13:01 PM Hi,
you need Code Editor to read t17 hashboard from one of them and write to others to match them together, this error mean your hashboards from different device or repaired and hash boards didn't match together. |