Antminer S17+ Hashboards working solo but not together?

Hey everyone, I’m in need of some help or ideas here. So, I’ve tested the hashboards separately and in pairs, and they work fine. But when I hook up all three at once, they just won’t function. It's really puzzling. Here are the last few lines from the Kernel log: 2022-05-16 17:17:45 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.113780 2022-05-16 17:17:46 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.143219 2022-05-16 17:17:47 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.242385 2022-05-16 17:17:47 power_api.c:53:_get_avg_voltage: average_voltage = 21.166461 2022-05-16 17:17:47 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.17, check voltage passed. 2022-05-16 17:17:47 uart.c:72:set_baud: set fpga_baud to 115200 2022-05-16 17:17:59 driver-btm-api.c:1096:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0 2022-05-16 17:18:10 driver-btm-api.c:1096:check_asic_number_with_power_on: Chain[1]: find 65 asic, times 0 2022-05-16 17:18:21 driver-btm-api.c:1096:check_asic_number_with_power_on: Chain[2]: find 65 asic, times 0 2022-05-16 17:18:29 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003 2022-05-16 17:18:29 driver-btm-api.c:397:set_order_clock: chain[0]: set order clock, stragegy 3 2022-05-16 17:18:29 driver-btm-api.c:397:set_order_clock: chain[1]: set order clock, stragegy 3 2022-05-16 17:18:29 driver-btm-api.c:397:set_order_clock: chain[2]: set order clock, stragegy 3 2022-05-16 17:18:30 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34 2022-05-16 17:18:30 driver-btm-api.c:1854:check_clock_counter: freq 50 clock_counter_li

Stock Bitmain firmware stores the chip tuning information along with the voltage it was tuned to run at in an eeprom on each hashboard. If the voltages are different between the boards, the firmware will not run. You can either buy a tool that will let you program the eeprom, or run aftermarket firmware like Brains or Vnish, both of which ignore all the data stored in the hashboard.

Does it seem that the two or all hashboard are replacements? You can't just able to run them without dumping the EEPROM from the original hashboard and flashing it to that replacement hashboard. You need a tool called Hashboard code editor to fix this issue read more about this below - https://www.zeusbtc.com/MinerDetails.asp?ID=236