Error driver btm base c 2403 miner initialization failed - Исправление ошибок и поиск оптимальных решений проблем

Содержание

Topic: t17+ with framework asic.to (Read 415 times)
t17 ошибка в логах
Demiansikora
Valwhatsminer
Zoomy

Topic: t17+ with framework asic.to (Read 415 times)

You need to replace the PSU, there isn’t much of work arounds you can do fix this, your best option would be running a singel hash boards at pretty low settings until the new psu arrives, although if i were you i would shut it down and wait for the new psu to make sure i don’t harm more things.

One thing worth mentioning that lower/higher voltage than what bitmain specifies will kill the new psu as well, make sure your voltage is between 200-240v.

I think asic.to firmware won’t be able to do that and I think you can only set the frequency of chips but you can’t be able to disable the broken chip.

However, you can try to change the frequency of that chip under chip frequency settings.

Find that broken chip and set the freq to lowest.

thanks , 2chain work for 15 minutes without any problem and have this log on below.

after about 5 min this log happen, and miner continue mining without problem:

but after about 15 min this log showed : (do you know which part of power have problem with this comment «Malformed power»

You need to use APW9+ and not APW9, in other words any power supply that works on T17+ will work on S17e, T17e, S17+ and vice versa obviously, but T17, S17 and S17 pro use APW9 which won’t work on your miner.

APW9 > S17, T17, S17pro

APW9+ > S17e, T17e, S17+, T17+

so chain 1 alone shows

chain 2 alone shows

chain 3 alone shows

chain 3 and 1 showed both hashbaords asics but failed to start, what this suggests is exactly what I said in my previous post

Dear Mikeywith and BitMaxz

I tried all chain one by one and this is the results (freq 650,700 and voltage 18.5,19.5 (framework asic.to) :

chain 1 : work without problem

chain 2: work with this log and shut down

chain 3:work without problem :

but when connect two chain 1,3 that worked correctly in one mode :

That makes sense, he should try that as well.

It’s unlikely, this used to be the case in the old miners S11 and older IIRC, but since the S15 the control board will simply ignore the bad hash board and move on to the next one, it’s even better with Vnish firmware since even if the board needs tunning the other two will work while the bad one gets turned individually, so it’s unlikely that 1 board is causing the miner to shut-down.

However, it would be worth it to test the hash boards one by one not for the reason you mentioned but for the fact that his PSU could be bad but not totally broken and it may be able to run a single hash board but not 3 of them.

That was hard to troubleshoot but I think much better to flash it back first on the original Bitmain firmware to check if the miner is fine and to check if it’s actually a PSU issue.

If the miner is running fine with the original firmware there might be misconfigured on asic.to firmware that causes the issue you might need the help of taserz to tweak your miner.
Or your miner is broken and you are trying to fix the issue by using asic.to firmware?

Can you try to run the hashboard one by one?
The one hashboard might be broken that can prevent other hashboard to run properly.

The kernel log can be very tricky, but this single line suggests that your hash boards might be okay but the power supply isn’t feeding them enough power, in other words, your PSU is bad, do you have a spare PSU?

I did it but error is stable yet

According to your logs «Failed to receive chip replies» your hashboard might be overheating that could lead to miner autoshutdown for overheating protection.

The solution is already on the above post by mikeywith reducing the frequency might solve the issue. If not, try to increase the fan speed or set it fixed to the maximum.

You can also, try to downvolt and manually set it to the lower frequency just to get rid of this issue.

The guide is already on asic.to manual or download it from here https://asic.to/download/manual_english/

And check this part.

Enable the #3 for auto downscale if the HW errors still occur.

my t17+ have this log now..and after 15 min power off automatically and again miner work for 15 min . i don’t know whats the problem. please guide me . thanks

What do you mean by resetting it manually?

At which point do you get this output?

Anyway, to answer your question, you need to go

Miner Configuration > Chain Frequency settings

Notice that there are two «Chain Frequency settings» tabs, you want the second to the left, scroll down and set the voltage and frequency you want.

Before you do that I suggest you go to

Miner Configuration > Profile Setting

Go to Preset and chose a low-profile, let it run for about an hour and then see if that fix anything if not then simply disable the profile and go to Chain Frequency settings and set low-frequency on your chain 1 and 2 ( 0 seems to be fine showing 44 asics as it should).

Please note that your chances are slim to nothing, but it still worth the try.

I updated my asic t17+ 55 ths to framework of asic.to successfully .My miner status and log is on below. you know that we can change voltage and frequency of chain manually in asic.to framework. i want to know with change of voltage or frequency of chains , can i solve this chip issue? any recommend setting is exists for asic.to? thanks.

my asic is this status

and after reset it manually it change to it:

Источник

t17 ошибка в логах

Demiansikora

Знающий

[2021/09/30 07:33:38] INFO: Checking fans
[2021/09/30 07:33:39] INFO: fan[0] — OK
[2021/09/30 07:33:39] INFO: fan[1] — OK
[2021/09/30 07:33:39] INFO: fan[2] — OK
[2021/09/30 07:33:39] INFO: fan[3] — OK
[2021/09/30 07:33:45] INFO: Power ON
[2021/09/30 07:33:47] INFO: Starting FPGA queue
[2021/09/30 07:33:47] INFO: Initializing hash boards
[2021/09/30 07:33:47] INFO: chain[2] — Initializing
[2021/09/30 07:33:47] INFO: chain[1] — Initializing
[2021/09/30 07:33:47] INFO: chain[0] — Initializing
[2021/09/30 07:33:50] WARN: chain[2] — Failed to reset pic (attempt = 1), resp: 0x02 0x02
[2021/09/30 07:33:51] WARN: chain[2] — Failed to reset pic (attempt = 2), resp: 0x01 0x01
[2021/09/30 07:33:54] WARN: chain[2] — Failed to reset pic (attempt = 3), resp: 0x89 0x89
[2021/09/30 07:33:55] WARN: chain[2] — Failed to start pic app (attempt = 1), resp: 0x2d 0x2d
[2021/09/30 07:33:55] WARN: chain[2] — Failed to start pic app (attempt = 2), resp: 0x2d 0x2d
[2021/09/30 07:33:56] WARN: chain[2] — Failed to start pic app (attempt = 3), resp: 0x2d 0x2d
[2021/09/30 07:33:57] WARN: chain[2] — Failed to reset pic (attempt = 1), resp: 0x2d 0x2d
[2021/09/30 07:33:59] WARN: chain[2] — Failed to reset pic (attempt = 2), resp: 0x85 0x85
[2021/09/30 07:34:01] WARN: chain[2] — Failed to reset pic (attempt = 3), resp: 0x31 0x31
[2021/09/30 07:34:01] WARN: chain[2] — Failed to start pic app (attempt = 1), resp: 0x31 0x31
[2021/09/30 07:34:02] WARN: chain[2] — Failed to start pic app (attempt = 2), resp: 0x31 0x31
[2021/09/30 07:34:02] WARN: chain[2] — Failed to start pic app (attempt = 3), resp: 0x31 0x31
[2021/09/30 07:34:04] WARN: chain[2] — Failed to reset pic (attempt = 1), resp: 0x31 0x31
[2021/09/30 07:34:06] WARN: chain[2] — Failed to reset pic (attempt = 2), resp: 0x01 0x01
[2021/09/30 07:34:07] WARN: chain[2] — Failed to reset pic (attempt = 3), resp: 0x01 0x01
[2021/09/30 07:34:08] WARN: chain[2] — Failed to start pic app (attempt = 1), resp: 0x01 0x01
[2021/09/30 07:34:08] WARN: chain[2] — Failed to start pic app (attempt = 2), resp: 0x01 0x01
[2021/09/30 07:34:09] WARN: chain[2] — Failed to start pic app (attempt = 3), resp: 0x01 0x01
[2021/09/30 07:34:09] ERROR: driver-btm-chain.c:465 chain[2] — Failed to init pic controller
[2021/09/30 07:34:09] INFO: chain[2] — Shutting down the chain
[2021/09/30 07:34:09] ERROR: driver-btm-base.c:356 chain[2] — Initialization failed

кто знает что происходит со вторым чайником

Valwhatsminer

Новичок

кто знает что происходит со вторым чайником

Zoomy

Свой человек

кто знает что происходит со вторым чайником

Источник

Доброго времени суток!
Пришли асики с китая 3 шт Т17 42ТН. Естественно из них два оказалось раздолбано. В частности отлетели радиаторы и конденсаторы. Часть чипов видать сдохла в дороге. Попытался из двух собрать один. И тут понял, что у каждого асика свой набор хэш плат и собрать компот не получится т.к. EEPROM разный. Увёз в сервис. В сервисе ребята сказали что программатором сделают у всех шести плат одинаковый EEPROM а остальные на ремонт.
По итогу сейчас все платы выдают ERROR_EEPROM_INFO
В сервисе сказали, что со всех плат стерли EEPROM и они не знают что делать. Что надо доставать EEPROM с самой контрольки как то, но они не знают как. Поставил туда прошивку VNISH сейчас выдает:
[2022/03/03 11:20:51] INFO: Power ON
[2022/03/03 11:20:53] ERROR: src/power.c:161 Malformed power response
[2022/03/03 11:20:55] ERROR: src/power.c:161 Malformed power response
[2022/03/03 11:20:57] ERROR: src/power.c:161 Malformed power response
[2022/03/03 11:20:57] ERROR: src/power.c:319 Failed to send command to PSU
[2022/03/03 11:20:57] ERROR: driver-btm-base.c:795 Failed to set voltage to 17000 mV
[2022/03/03 11:20:57] ERROR: driver-btm-base.c:2139 Failed to set start-up voltage
[2022/03/03 11:20:57] INFO: Shutting down the miner
[2022/03/03 11:20:57] INFO: Power OFF
[2022/03/03 11:20:57] ERROR: driver-btm-base.c:2403 Miner initialization failed.
Открыл SSH подключился через WINSCP к контрольке
Спрашивал у Andrey_Doc. Он сказал искать в /nvdata/ но я такой файл или директорию не нашел.
Прошу помощи

Хорошо, вечером попробую, отпишусь

А на внише — поставь галочку в настройках «Disable chain break protection» и асе заработает.

поставил. Ошибка сохранилась

Залил экспериментальную прошивку. На платах выдает 0 вольт

лог Т17.txt

36,8 КБ · Просмотры: 4

Лог второго асика

лог Т17_2.txt

20 КБ · Просмотры: 2

Источник

@Splinter Приветствую, есть проблема с Т17 bad clock counter. chain = 1, asic = 7, core = 0, found 0, clock counter 0x00000000 что уже только не делал, чипы естесственно менял весь 3 домен 6ой чип, один фиг, при чём ошибка в точности повторяется, при этом плата запускается и майнит, ещё заметил что на третьем домене одно из питаний всех трёх чипов VDD2_1 на холодную 0,5в на всех остальных при этом примерно 0,8,когда плата чуть нагреется то и на третьем становится 0,8 может это быть связано с данной ошибкой? и скрин температуры при работе в морде приложил.

Спойлер

2022-04-28 13:01:29 driver-btm-api.c:631:init_freq_mode: This is scan-user version
2022-04-28 13:01:29 driver-btm-api.c:1994:bitmain_soc_init: opt_multi_version = 1
2022-04-28 13:01:29 driver-btm-api.c:1995:bitmain_soc_init: opt_bitmain_ab = 1
2022-04-28 13:01:29 driver-btm-api.c:1996:bitmain_soc_init: opt_bitmain_work_mode = 0
2022-04-28 13:01:29 driver-btm-api.c:1997:bitmain_soc_init: Miner compile time: Tue Dec 24 16:13:07 CST 2019 type: Antminer T17
2022-04-28 13:01:29 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
2022-04-28 13:01:29 driver-btm-api.c:1810:show_sn: no SN got, please write SN to /nvdata/sn
2022-04-28 13:01:29 driver-btm-api.c:1135:miner_device_init: Detect 256MB control board of XILINX
2022-04-28 13:01:29 driver-btm-api.c:1083:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2022-04-28 13:01:29 thread.c:789:create_read_nonce_reg_thread: create thread
2022-04-28 13:01:35 driver-btm-api.c:1067:init_miner_version: miner ID : 8030e4042b104814
2022-04-28 13:01:35 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2022-04-28 13:01:37 eeprom.c:431:check_pattern_test_level: L1 board
2022-04-28 13:01:39 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2022-04-28 13:01:39 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2022-04-28 13:01:39 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2022-04-28 13:01:39 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2022-04-28 13:01:39 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2022-04-28 13:01:39 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2022-04-28 13:01:39 driver-btm-api.c:644:_set_project_type: project:2
2022-04-28 13:01:39 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2022-04-28 13:01:39 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2022-04-28 13:01:39 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2022-04-28 13:01:39 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2022-04-28 13:01:39 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2022-04-28 13:01:42 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2022-04-28 13:01:43 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-04-28 13:01:47 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2022-04-28 13:01:49 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-04-28 13:01:52 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2022-04-28 13:01:52 thread.c:784:create_pic_heart_beat_thread: create thread
2022-04-28 13:01:52 power_api.c:55:power_init: power init …
2022-04-28 13:01:52 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2022-04-28 13:02:24 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 …
2022-04-28 13:02:26 power_api.c:124:check_voltage_multi: retry time: 0
2022-04-28 13:02:28 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.530283
2022-04-28 13:02:29 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.113916
2022-04-28 13:02:29 power_api.c:97:get_average_voltage: aveage voltage is: 17.322099
2022-04-28 13:02:29 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2022-04-28 13:02:29 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2022-04-28 13:02:29 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2022-04-28 13:02:29 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2022-04-28 13:02:39 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2022-04-28 13:02:49 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2022-04-28 13:02:52 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2022-04-28 13:02:52 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2022-04-28 13:02:52 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2022-04-28 13:02:52 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2022-04-28 13:02:52 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2022-04-28 13:02:52 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2022-04-28 13:02:52 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2022-04-28 13:02:55 register.c:1416:quick_dump_core_hash_clock_counter: bad clock counter. chain = 1, asic = 7, core = 0, found 0, clock counter 0x00000000
2022-04-28 13:02:55 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2022-04-28 13:02:55 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2022-04-28 13:02:55 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2022-04-28 13:02:55 driver-btm-api.c:1939:bitmain_board_init: clock counter status was not good. Try reset.
2022-04-28 13:03:05 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2022-04-28 13:03:15 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2022-04-28 13:03:18 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2022-04-28 13:03:18 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2022-04-28 13:03:18 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2022-04-28 13:03:18 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2022-04-28 13:03:18 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2022-04-28 13:03:18 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2022-04-28 13:03:18 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2022-04-28 13:03:21 register.c:1416:quick_dump_core_hash_clock_counter: bad clock counter. chain = 1, asic = 7, core = 0, found 0, clock counter 0x00000000
2022-04-28 13:03:21 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2022-04-28 13:03:21 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2022-04-28 13:03:21 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2022-04-28 13:03:21 driver-btm-api.c:1939:bitmain_board_init: clock counter status was not good. Try reset.
2022-04-28 13:03:31 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2022-04-28 13:03:41 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2022-04-28 13:03:43 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2022-04-28 13:03:44 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2022-04-28 13:03:44 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2022-04-28 13:03:44 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2022-04-28 13:03:44 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2022-04-28 13:03:44 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2022-04-28 13:03:44 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2022-04-28 13:03:47 register.c:1416:quick_dump_core_hash_clock_counter: bad clock counter. chain = 1, asic = 7, core = 0, found 0, clock counter 0x00000000
2022-04-28 13:03:47 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2022-04-28 13:03:47 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2022-04-28 13:03:47 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2022-04-28 13:03:47 driver-btm-api.c:1939:bitmain_board_init: clock counter status was not good. Try reset.
2022-04-28 13:03:47 voltage[1] = 1690
2022-04-28 13:03:47 voltage[2] = 1690
2022-04-28 13:03:47 power_api.c:140:set_working_voltage: working_voltage = 16.900000
2022-04-28 13:03:48 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2022-04-28 13:03:50 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2022-04-28 13:03:50 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2022-04-28 13:03:50 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2022-04-28 13:03:50 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2022-04-28 13:03:51 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 30
2022-04-28 13:03:51 thread.c:804:create_check_miner_status_thread: create thread
2022-04-28 13:03:51 thread.c:794:create_set_miner_status_thread: create thread
2022-04-28 13:03:51 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2022-04-28 13:03:51 thread.c:779:create_temperature_monitor_thread: create thread
2022-04-28 13:03:51 freq_tuning.c:154:freq_tuning_get_max_freq: Max freq of tuning is 760
2022-04-28 13:03:51 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 17.60 …
2022-04-28 13:04:20 power_api.c:124:check_voltage_multi: retry time: 0
2022-04-28 13:04:22 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.332402
2022-04-28 13:04:23 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.713974
2022-04-28 13:04:23 power_api.c:97:get_average_voltage: aveage voltage is: 18.023188
2022-04-28 13:04:23 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
2022-04-28 13:04:24 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
2022-04-28 13:04:24 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
2022-04-28 13:04:24 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
2022-04-28 13:04:24 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
2022-04-28 13:04:24 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
2022-04-28 13:04:24 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
2022-04-28 13:04:24 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
2022-04-28 13:04:24 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
2022-04-28 13:04:24 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
2022-04-28 13:04:24 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
2022-04-28 13:04:25 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 42 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 7, usr divider: 1
2022-04-28 13:04:25 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 50 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 6, usr divider: 1
2022-04-28 13:04:25 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 60 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 5, usr divider: 1
2022-04-28 13:04:25 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 75 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 4, usr divider: 1
2022-04-28 13:04:25 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 100 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 3, usr divider: 1
2022-04-28 13:04:25 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 150 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 2, usr divider: 1
2022-04-28 13:04:25 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 300 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 1, usr divider: 1
2022-04-28 13:04:25 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 350 set refdiv: 2, fbdiv: 168, postdiv1: 6, postdiv2: 1, usr divider: 1
2022-04-28 13:04:25 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 420 set refdiv: 2, fbdiv: 168, postdiv1: 5, postdiv2: 1, usr divider: 1
2022-04-28 13:04:26 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 525 set refdiv: 2, fbdiv: 168, postdiv1: 4, postdiv2: 1, usr divider: 1
2022-04-28 13:04:26 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 700 set refdiv: 2, fbdiv: 168, postdiv1: 3, postdiv2: 1, usr divider: 1
2022-04-28 13:04:26 driver-btm-api.c:612:set_timeout: freq 720 final timeout=163
2022-04-28 13:04:26 power_api.c:397:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 16.90 …
2022-04-28 13:04:50 power_api.c:124:check_voltage_multi: retry time: 0
2022-04-28 13:04:54 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.677236
2022-04-28 13:04:57 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.028193
2022-04-28 13:04:57 power_api.c:97:get_average_voltage: aveage voltage is: 17.352715
2022-04-28 13:04:57 frequency.c:540:get_current_min_freq: current min freq 700
2022-04-28 13:04:57 driver-btm-api.c:1660:check_clock_counter: freq 700 clock_counter_limit 89
2022-04-28 13:05:01 register.c:1416:quick_dump_core_hash_clock_counter:
2022-04-28 13:05:01 driver-btm-api.c:2097:bitmain_soc_init: clock count check failed after retry, wait for hash rate protect later.
2022-04-28 13:05:01 thread.c:799:create_check_system_status_thread: create thread
2022-04-28 13:05:01 driver-btm-api.c:2113:bitmain_soc_init: Init done!
2022-04-28 13:05:01 driver-btm-api.c:201:set_miner_status: STATUS_INIT
2022-04-28 13:05:06 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2022-04-28 13:05:11 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4
2022-04-28 13:10:10 thread.c:422:is_zero_nonce_happened: chain_nonce[1] = 14920
2022-04-28 13:10:10 thread.c:422:is_zero_nonce_happened: chain_nonce[2] = 15198
2022-04-28 13:10:10 thread.c:478:clear_zero_nonce_mark: 0 nonce protect succeed.

Источник

hello i have a antminer s17+ and its not working right it just keeps on resetting after it starts mining. here is the kernel log. and yes i know chain 1 isnt working but still the miner was hashing on the other 2 boards and now it just keeps resetting please help.

[2021/03/24 02:07:27] INFO: Detected 256 Mb of RAM

[2021/03/24 02:07:27] INFO: Switching to manual fan control (30 %)

[2021/03/24 02:07:27] INFO: Checking fans

[2021/03/24 02:07:28] INFO: fan[0] — OK

[2021/03/24 02:07:28] INFO: fan[1] — OK

[2021/03/24 02:07:28] INFO: fan[2] — OK

[2021/03/24 02:07:28] INFO: fan[3] — OK

[2021/03/24 02:07:34] INFO: Power ON

[2021/03/24 02:07:36] INFO: Starting FPGA queue

[2021/03/24 02:07:36] INFO: Initializing hash boards

[2021/03/24 02:07:36] INFO: chain[1] — Initializing

[2021/03/24 02:07:36] INFO: chain[0] — Initializing

[2021/03/24 02:07:49] INFO: chain[1] — 65 chips detected

[2021/03/24 02:07:51] INFO: chain[0] — 65 chips detected

[2021/03/24 02:07:58] INFO: Start-up temperature is 22 C (min -15 C)

[2021/03/24 02:07:58] INFO: Switching to manual fan control (100 %)

[2021/03/24 02:07:58] INFO: Changing voltage from 21000 to 20450 mV gradually

[2021/03/24 02:08:28] INFO: Raising freq from 50 to 565 Mhz gradually

[2021/03/24 02:08:39] INFO: Switching to automatic fan control (75 C)

[2021/03/24 02:08:39] INFO: Start mining!

[2021/03/24 02:08:57] INFO: Detected 256 Mb of RAM

[2021/03/24 02:08:57] INFO: Switching to manual fan control (30 %)

[2021/03/24 02:08:57] INFO: Checking fans

[2021/03/24 02:08:58] INFO: fan[0] — OK

[2021/03/24 02:08:58] INFO: fan[1] — OK

[2021/03/24 02:08:58] INFO: fan[2] — OK

[2021/03/24 02:08:58] INFO: fan[3] — OK

[2021/03/24 14:35:24] INFO: Detected 256 Mb of RAM

[2021/03/24 14:35:24] INFO: Switching to manual fan control (30 %)

[2021/03/24 14:35:24] INFO: Checking fans

[2021/03/24 14:35:29] INFO: fan[0] — OK

[2021/03/24 14:35:29] INFO: fan[1] — OK

[2021/03/24 14:35:29] INFO: fan[2] — OK

[2021/03/24 14:35:29] INFO: fan[3] — OK

[2021/03/24 14:35:35] INFO: Power ON

[2021/03/24 14:35:37] INFO: Starting FPGA queue

[2021/03/24 14:35:37] INFO: Initializing hash boards

[2021/03/24 14:35:37] INFO: chain[2] — Initializing

[2021/03/24 14:35:37] INFO: chain[1] — Initializing

[2021/03/24 14:35:37] INFO: chain[0] — Initializing

[2021/03/24 14:35:51] INFO: chain[2] — 65 chips detected

[2021/03/24 14:35:54] WARN: chain[1] — 64 of 65 chips detected

[2021/03/24 14:35:55] INFO: chain[0] — 65 chips detected

[2021/03/24 14:36:06] WARN: chain[1] — 64 of 65 chips detected

[2021/03/24 14:36:17] WARN: chain[1] — 64 of 65 chips detected

[2021/03/24 14:36:17] ERROR: driver-btm-chain.c:488 chain[1] — Failed to detect ASIC chips

[2021/03/24 14:36:17] INFO: chain[1] — Shutting down the chain

[2021/03/24 14:36:18] ERROR: driver-btm-base.c:361 chain[1] — Initialization failed

[2021/03/24 14:36:21] INFO: Start-up temperature is 21 C (min -15 C)

[2021/03/24 14:36:21] INFO: Switching to manual fan control (100 %)

[2021/03/24 14:36:21] INFO: Changing voltage from 21000 to 20450 mV gradually

[2021/03/24 14:36:51] INFO: Raising freq from 50 to 565 Mhz gradually

[2021/03/24 14:37:02] INFO: Switching to automatic fan control (75 C)

[2021/03/24 14:37:02] INFO: Start mining!

[2021/03/24 14:37:35] INFO: Detected 256 Mb of RAM

[2021/03/24 14:37:35] INFO: Switching to manual fan control (30 %)

[2021/03/24 14:37:35] INFO: Checking fans

[2021/03/24 14:37:36] INFO: fan[0] — OK

[2021/03/24 14:37:36] INFO: fan[1] — OK

[2021/03/24 14:37:36] INFO: fan[2] — OK

[2021/03/24 14:37:36] INFO: fan[3] — OK

[2021/03/24 14:37:42] INFO: Power ON

[2021/03/24 14:37:44] INFO: Starting FPGA queue

[2021/03/24 14:37:44] INFO: Initializing hash boards

[2021/03/24 14:37:44] INFO: chain[2] — Initializing

[2021/03/24 14:37:44] INFO: chain[1] — Initializing

[2021/03/24 14:37:44] INFO: chain[0] — Initializing

[2021/03/24 14:37:57] INFO: chain[2] — 65 chips detected

[2021/03/24 14:38:00] WARN: chain[1] — 64 of 65 chips detected

[2021/03/24 14:38:01] INFO: chain[0] — 65 chips detected

[2021/03/24 14:38:12] WARN: chain[1] — 64 of 65 chips detected

[2021/03/24 14:38:24] WARN: chain[1] — 64 of 65 chips detected

[2021/03/24 14:38:24] ERROR: driver-btm-chain.c:488 chain[1] — Failed to detect ASIC chips

[2021/03/24 14:38:24] INFO: chain[1] — Shutting down the chain

[2021/03/24 14:38:24] ERROR: driver-btm-base.c:361 chain[1] — Initialization failed

[2021/03/24 14:38:28] INFO: Start-up temperature is 24 C (min -15 C)

[2021/03/24 14:38:28] INFO: Switching to manual fan control (100 %)

[2021/03/24 14:38:28] INFO: Changing voltage from 21000 to 20450 mV gradually

[2021/03/24 14:38:58] INFO: Raising freq from 50 to 565 Mhz gradually

[2021/03/24 14:39:09] INFO: Switching to automatic fan control (75 C)

[2021/03/24 14:39:09] INFO: Start mining!

[2021/03/24 14:39:25] INFO: Detected 256 Mb of RAM

[2021/03/24 14:39:25] INFO: Switching to manual fan control (30 %)

[2021/03/24 14:39:25] INFO: Checking fans

[2021/03/24 14:39:26] INFO: fan[0] — OK

[2021/03/24 14:39:26] INFO: fan[1] — OK

[2021/03/24 14:39:26] INFO: fan[2] — OK

[2021/03/24 14:39:26] INFO: fan[3] — OK

[2021/03/24 14:39:32] INFO: Power ON

[2021/03/24 14:39:34] INFO: Starting FPGA queue

[2021/03/24 14:39:34] INFO: Initializing hash boards

[2021/03/24 14:39:34] INFO: chain[2] — Initializing

[2021/03/24 14:39:34] INFO: chain[1] — Initializing

[2021/03/24 14:39:34] INFO: chain[0] — Initializing

[2021/03/24 14:39:48] INFO: chain[2] — 65 chips detected

[2021/03/24 14:39:51] WARN: chain[1] — 64 of 65 chips detected

[2021/03/24 14:39:52] INFO: chain[0] — 65 chips detected

[2021/03/24 14:40:02] WARN: chain[1] — 64 of 65 chips detected

Источник

full member

Activity: 228

Merit: 101

NEM (XEM) Top Coin

Thanks mikeywith. I gave my power to technician to repair it. after fixed it , I’ll check and give u the results.

legendary

Activity: 1764

Merit: 4829

be constructive or S.T.F.U

One thing worth mentioning that lower/higher voltage than what bitmain specifies will kill the new psu as well, make sure your voltage is between 200-240v.

legendary

Activity: 2744

Merit: 2373

Bull market is coming?

I think asic.to firmware won’t be able to do that and I think you can only set the frequency of chips but you can’t be able to disable the broken chip.

However, you can try to change the frequency of that chip under chip frequency settings.

Find that broken chip and set the freq to lowest.

full member

Activity: 228

Merit: 101

NEM (XEM) Top Coin

Can i disable this

chip139x.c:1049

only in chain 1 and other chips work in this chain? because i use framework asic.to?

legendary

Activity: 3640

Merit: 5167

disconnect chain 1 as it looks to have a bad chip.

full member

Activity: 228

Merit: 101

NEM (XEM) Top Coin

thanks , 2chain work for 15 minutes without any problem and have this log on below.

[2020/08/26 16:11:56] INFO: fan[1] — OK
[2020/08/26 16:11:56] INFO: fan[2] — OK
[2020/08/26 16:11:56] INFO: fan[3] — OK
[2020/08/26 16:12:02] INFO: Power ON
[2020/08/26 16:12:04] INFO: Starting FPGA queue
[2020/08/26 16:12:04] INFO: Initializing hash boards
[2020/08/26 16:12:04] INFO: chain[2] — Initializing
[2020/08/26 16:12:04] INFO: chain[1] — Initializing
[2020/08/26 16:12:17] INFO: chain[2] — 44 chips detected
[2020/08/26 16:12:18] INFO: chain[1] — 44 chips detected
[2020/08/26 16:12:24] INFO: Start-up temperature is 27 C (min -15 C)
[2020/08/26 16:12:24] INFO: Switching to manual fan control (100 %)
[2020/08/26 16:12:24] INFO: Changing voltage from 19500 to 19000 mV gradually
[2020/08/26 16:12:51] INFO: Raising freq from 50 to 700 Mhz gradually
[2020/08/26 16:13:04] INFO: Switching to automatic fan control (75 C)
[2020/08/26 16:13:04] INFO: Start mining!
[2020/08/26 16:14:04] INFO: Changing voltage from 19000 to 18800 mV gradually
[2020/08/26 16:14:29] INFO: Changing voltage from 18800 to 18600 mV gradually
[2020/08/26 16:14:54] INFO: Changing voltage from 18600 to 18500 mV gradually
[2020/08/26 16:26:56] ERROR: src/chip139x.c:1049 chain[1] — Failed to receive chip replies
[2020/08/26 16:26:57] ERROR: src/chip139x.c:1049 chain[1] — Failed to receive chip replies
[2020/08/26 16:27:23] INFO: Detected 256 Mb of RAM
[2020/08/26 16:27:23] INFO: Switching to manual fan control (30 %)
[2020/08/26 16:27:23] INFO: Checking fans
[2020/08/26 16:27:24] INFO: fan[0] — OK
[2020/08/26 16:27:24] INFO: fan[1] — OK
[2020/08/26 16:27:24] INFO: fan[2] — OK
[2020/08/26 16:27:24] INFO: fan[3] — OK
[2020/08/26 16:27:30] INFO: Power ON
[2020/08/26 16:27:32] ERROR: src/power.c:161 Malformed power response
[2020/08/26 16:27:34] INFO: Starting FPGA queue
[2020/08/26 16:27:34] INFO: Initializing hash boards
[2020/08/26 16:27:34] INFO: chain[2] — Initializing
[2020/08/26 16:27:34] INFO: chain[1] — Initializing
[2020/08/26 16:27:45] ERROR: driver-btm-chain.c:687 chain[2] — Voltage is different, cur=801 mV tgt=19500 mV
[2020/08/26 16:27:45] ERROR: driver-btm-chain.c:471 chain[2] — Failed to set start up voltage
[2020/08/26 16:27:45] INFO: chain[2] — Shutting down the chain
[2020/08/26 16:27:45] ERROR: driver-btm-base.c:356 chain[2] — Initialization failed
[2020/08/26 16:27:46] ERROR: driver-btm-chain.c:687 chain[1] — Voltage is different, cur=874 mV tgt=19500 mV
[2020/08/26 16:27:46] ERROR: driver-btm-chain.c:471 chain[1] — Failed to set start up voltage
[2020/08/26 16:27:46] INFO: chain[1] — Shutting down the chain
[2020/08/26 16:27:46] ERROR: driver-btm-base.c:356 chain[1] — Initialization failed
[2020/08/26 16:27:46] ERROR: driver-btm-base.c:2154 Failed to initialize hash boards
[2020/08/26 16:27:46] INFO: Shutting down the miner
[2020/08/26 16:27:46] INFO: Stopping FPGA queue
[2020/08/26 16:27:46] INFO: chain[1] — Shutting down the chain
[2020/08/26 16:27:46] INFO: chain[2] — Shutting down the chain
[2020/08/26 16:27:46] INFO: Power OFF

after about 5 min this log happen, and miner continue mining without problem:

[2020/08/26 16:14:04] INFO: Changing voltage from 19000 to 18800 mV gradually
[2020/08/26 16:14:29] INFO: Changing voltage from 18800 to 18600 mV gradually
[2020/08/26 16:14:54] INFO: Changing voltage from 18600 to 18500 mV gradually

but after about 15 min this log showed : (do you know which part of power have problem with this comment «Malformed power»

[2020/08/26 16:26:56] ERROR: src/chip139x.c:1049 chain[1] — Failed to receive chip replies
[2020/08/26 16:26:57] ERROR: src/chip139x.c:1049 chain[1] — Failed to receive chip replies
[2020/08/26 16:27:32] ERROR: src/power.c:161 Malformed power response

legendary

Activity: 1764

Merit: 4829

be constructive or S.T.F.U

APW9 > S17, T17, S17pro

APW9+ > S17e, T17e, S17+, T17+

full member

Activity: 228

Merit: 101

NEM (XEM) Top Coin

Thanks for reply… can i use power miner t17 40th/s or other model power for t17+ 55 ths or exactly my power must be t17+55 and can’t be t17+58 or others ?

legendary

Activity: 1764

Merit: 4829

be constructive or S.T.F.U

so chain 1 alone shows

INFO: chain[1] — 44 chips detected

chain 2 alone shows

ERROR: driver-btm-base.c:2154 Failed to initialize hash boards

chain 3 alone shows

chain[3] — 44 chips detected

chain 3 and 1 showed both hashbaords asics but failed to start, what this suggests is exactly what I said in my previous post

The kernel log can be very tricky, but this single line suggests that your hash boards might be okay but the power supply isn’t feeding them enough power, in other words, your PSU is bad…

full member

Activity: 228

Merit: 101

NEM (XEM) Top Coin

Dear Mikeywith and BitMaxz

I tried all chain one by one and this is the results (freq 650,700 and voltage 18.5,19.5 (framework asic.to) :

chain 1 : work without problem

[2020/08/24 14:01:52] INFO: Detected 256 Mb of RAM
[2020/08/24 14:01:52] INFO: Switching to manual fan control (30 %)
[2020/08/24 14:01:52] INFO: Checking fans
[2020/08/24 14:01:53] INFO: fan[0] — OK
[2020/08/24 14:01:53] INFO: fan[1] — OK
[2020/08/24 14:01:53] INFO: fan[2] — OK
[2020/08/24 14:01:53] INFO: fan[3] — OK
[2020/08/24 14:01:59] INFO: Power ON
[2020/08/24 14:02:01] INFO: Starting FPGA queue
[2020/08/24 14:02:04] INFO: Initializing hash boards
[2020/08/24 14:02:05] INFO: chain[1] — Initializing
[2020/08/24 14:02:07] INFO: chain[1] — 44 chips detected
[2020/08/24 14:02:08] INFO: Start-up temperature is 25 C (min -15 C)
[2020/08/24 14:02:11] INFO: Switching to manual fan control (100 %)
[2020/08/24 14:02:13] INFO: Raising freq from 50 to 700 Mhz gradually
[2020/08/24 14:02:17] INFO: Switching to manual fan control (96 %)
[2020/08/24 14:02:19] INFO: Start mining!

chain 2: work with this log and shut down

[2020/08/24 14:21:13] INFO: Detected 256 Mb of RAM
[2020/08/24 14:21:13] INFO: Switching to manual fan control (30 %)
[2020/08/24 14:21:13] INFO: Checking fans
[2020/08/24 14:21:18] INFO: fan[0] — OK
[2020/08/24 14:21:18] INFO: fan[1] — OK
[2020/08/24 14:21:18] INFO: fan[2] — OK
[2020/08/24 14:21:18] INFO: fan[3] — OK
[2020/08/24 14:21:24] INFO: Power ON
[2020/08/24 14:21:26] INFO: Starting FPGA queue
[2020/08/24 14:21:26] INFO: Initializing hash boards
[2020/08/24 14:21:26] INFO: chain[2] — Initializing
[2020/08/24 14:21:37] ERROR: driver-btm-chain.c:687 chain[2] — Voltage is different, cur=608 mV tgt=19500 mV
[2020/08/24 14:21:37] ERROR: driver-btm-chain.c:471 chain[2] — Failed to set start up voltage
[2020/08/24 14:21:37] INFO: chain[2] — Shutting down the chain
[2020/08/24 14:21:37] ERROR: driver-btm-base.c:356 chain[2] — Initialization failed
[2020/08/24 14:21:37] ERROR: driver-btm-base.c:2154 Failed to initialize hash boards
[2020/08/24 14:21:37] INFO: Shutting down the miner
[2020/08/24 14:21:37] INFO: Stopping FPGA queue
[2020/08/24 14:21:37] INFO: chain[2] — Shutting down the chain

chain 3:work without problem :

[2020/08/24 15:06:37] INFO: Start mining!
[2020/08/24 15:16:49] INFO: Detected 256 Mb of RAM
[2020/08/24 15:16:49] INFO: Switching to manual fan control (30 %)
[2020/08/24 15:16:49] INFO: Checking fans
[2020/08/24 15:16:56] INFO: fan[0] — OK
[2020/08/24 15:16:56] INFO: fan[1] — OK
[2020/08/24 15:16:56] INFO: fan[2] — OK
[2020/08/24 15:16:56] INFO: fan[3] — OK
[2020/08/24 15:17:02] INFO: Power ON
[2020/08/24 15:17:04] INFO: Starting FPGA queue
[2020/08/24 15:17:04] INFO: Initializing hash boards
[2020/08/24 15:17:04] INFO: chain[1] — Initializing
[2020/08/24 15:17:16] INFO: chain[1] — 44 chips detected
[2020/08/24 15:17:22] INFO: Start-up temperature is 25 C (min -15 C)
[2020/08/24 15:17:22] INFO: Switching to manual fan control (100 %)
[2020/08/24 15:17:22] INFO: Raising freq from 50 to 700 Mhz gradually
[2020/08/24 15:17:35] INFO: Switching to manual fan control (96 %)
[2020/08/24 15:17:35] INFO: Start mining!

but when connect two chain 1,3 that worked correctly in one mode :

[2020/08/24 14:42:13] INFO: Detected 256 Mb of RAM
[2020/08/24 14:42:13] INFO: Switching to manual fan control (30 %)
[2020/08/24 14:42:13] INFO: Checking fans
[2020/08/24 14:42:14] INFO: fan[0] — OK
[2020/08/24 14:42:14] INFO: fan[1] — OK
[2020/08/24 14:42:14] INFO: fan[2] — OK
[2020/08/24 14:42:14] INFO: fan[3] — OK
[2020/08/24 14:42:20] INFO: Power ON
[2020/08/24 14:42:22] INFO: Starting FPGA queue
[2020/08/24 14:42:22] INFO: Initializing hash boards
[2020/08/24 14:42:22] INFO: chain[2] — Initializing
[2020/08/24 14:42:22] INFO: chain[1] — Initializing
[2020/08/24 14:42:35] INFO: chain[2] — 44 chips detected
[2020/08/24 14:42:36] INFO: chain[1] — 44 chips detected
[2020/08/24 14:42:42] INFO: Start-up temperature is 24 C (min -15 C)
[2020/08/24 14:42:42] INFO: Switching to manual fan control (100 %)
[2020/08/24 14:42:42] INFO: Changing voltage from 19500 to 18500 mV gradually
[2020/08/24 14:43:12] INFO: Raising freq from 50 to 650 Mhz gradually
[2020/08/24 14:43:25] INFO: Switching to manual fan control (96 %)
[2020/08/24 14:43:25] INFO: Start mining!
[2020/08/24 14:46:47] ERROR: src/chip139x.c:1049 chain[1] — Failed to receive chip replies
[2020/08/24 14:46:48] ERROR: src/chip139x.c:1049 chain[2] — Failed to receive chip replies
[2020/08/24 14:46:49] ERROR: src/chip139x.c:1049 chain[2] — Failed to receive chip replies
[2020/08/24 14:47:03] INFO: Detected 256 Mb of RAM
[2020/08/24 14:47:03] INFO: Switching to manual fan control (30 %)
[2020/08/24 14:47:03] INFO: Checking fans
[2020/08/24 14:47:04] INFO: fan[0] — OK
[2020/08/24 14:47:04] INFO: fan[1] — OK
[2020/08/24 14:47:04] INFO: fan[2] — OK
[2020/08/24 14:47:04] INFO: fan[3] — OK
[2020/08/24 14:47:10] INFO: Power ON
[2020/08/24 14:47:12] INFO: Starting FPGA queue
[2020/08/24 14:47:12] INFO: Initializing hash boards
[2020/08/24 14:47:12] INFO: chain[2] — Initializing
[2020/08/24 14:47:12] INFO: chain[1] — Initializing
[2020/08/24 14:47:23] ERROR: driver-btm-chain.c:687 chain[2] — Voltage is different, cur=874 mV tgt=19500 mV
[2020/08/24 14:47:23] ERROR: driver-btm-chain.c:471 chain[2] — Failed to set start up voltage
[2020/08/24 14:47:23] INFO: chain[2] — Shutting down the chain
[2020/08/24 14:47:23] ERROR: driver-btm-base.c:356 chain[2] — Initialization failed
[2020/08/24 14:47:24] ERROR: driver-btm-chain.c:687 chain[1] — Voltage is different, cur=946 mV tgt=19500 mV
[2020/08/24 14:47:24] ERROR: driver-btm-chain.c:471 chain[1] — Failed to set start up voltage
[2020/08/24 14:47:24] INFO: chain[1] — Shutting down the chain
[2020/08/24 14:47:24] ERROR: driver-btm-base.c:356 chain[1] — Initialization failed
[2020/08/24 14:47:24] ERROR: driver-btm-base.c:2154 Failed to initialize hash boards
[2020/08/24 14:47:24] INFO: Shutting down the miner

what do you think about this problem?

legendary

Activity: 1764

Merit: 4829

be constructive or S.T.F.U

That was hard to troubleshoot but I think much better to flash it back first on the original Bitmain firmware to check if the miner is fine and to check if it’s actually a PSU issue.

That makes sense, he should try that as well.

Can you try to run the hashboard one by one?
The one hashboard might be broken that can prevent other hashboard to run properly.

legendary

Activity: 2744

Merit: 2373

Bull market is coming?

That was hard to troubleshoot but I think much better to flash it back first on the original Bitmain firmware to check if the miner is fine and to check if it’s actually a PSU issue.

Can you try to run the hashboard one by one?
The one hashboard might be broken that can prevent other hashboard to run properly.

legendary

Activity: 1764

Merit: 4829

be constructive or S.T.F.U

[1970/01/01 00:20:11] ERROR: driver-btm-chain.c:967 chain[0] — Failed to read temp from all sensors!

This isn’t how he should do it, this is the auto-chip tune, he needs to go the next tab and set fixed frequency and voltage for each hashboard.

full member

Activity: 228

Merit: 101

NEM (XEM) Top Coin

I did it but error is stable yet

[2020/08/21 19:08:07] INFO: Detected 256 Mb of RAM
[2020/08/21 19:08:07] INFO: Switching to manual fan control (30 %)
[2020/08/21 19:08:07] INFO: Checking fans
[2020/08/21 19:08:08] INFO: fan[0] — OK
[2020/08/21 19:08:08] INFO: fan[1] — OK
[2020/08/21 19:08:08] INFO: fan[2] — OK
[2020/08/21 19:08:08] INFO: fan[3] — OK
[2020/08/21 19:08:14] INFO: Power ON
[2020/08/21 19:08:17] INFO: Starting FPGA queue
[2020/08/21 19:08:17] INFO: Initializing hash boards
[2020/08/21 19:08:17] INFO: chain[2] — Initializing
[2020/08/21 19:08:17] INFO: chain[1] — Initializing
[2020/08/21 19:08:17] INFO: chain[0] — Initializing
[2020/08/21 19:08:30] ERROR: src/chip139x.c:1049 chain[2] — Failed to receive chip replies
[2020/08/21 19:08:31] ERROR: src/chip139x.c:1049 chain[2] — Failed to receive chip replies
[2020/08/21 19:08:32] ERROR: src/chip139x.c:1049 chain[2] — Failed to receive chip replies
[2020/08/21 19:08:32] WARN: chain[2] — 0 of 44 chips detected
[2020/08/21 19:08:33] INFO: chain[1] — 44 chips detected
[2020/08/21 19:08:34] INFO: chain[0] — 44 chips detected
[2020/08/21 19:08:41] ERROR: src/chip139x.c:1049 chain[2] — Failed to receive chip replies
[2020/08/21 19:08:42] ERROR: src/chip139x.c:1049 chain[2] — Failed to receive chip replies
[2020/08/21 19:08:43] ERROR: src/chip139x.c:1049 chain[2] — Failed to receive chip replies
[2020/08/21 19:08:43] WARN: chain[2] — 0 of 44 chips detected
[2020/08/21 19:08:53] ERROR: src/chip139x.c:1049 chain[2] — Failed to receive chip replies
[2020/08/21 19:08:54] ERROR: src/chip139x.c:1049 chain[2] — Failed to receive chip replies
[2020/08/21 19:08:55] ERROR: src/chip139x.c:1049 chain[2] — Failed to receive chip replies
[2020/08/21 19:08:55] WARN: chain[2] — 0 of 44 chips detected
[2020/08/21 19:08:55] ERROR: driver-btm-chain.c:488 chain[2] — Failed to detect ASIC chips
[2020/08/21 19:08:55] INFO: chain[2] — Shutting down the chain
[2020/08/21 19:08:56] ERROR: driver-btm-base.c:356 chain[2] — Initialization failed
[2020/08/21 19:08:59] INFO: Start-up temperature is 31 C (min -15 C)
[2020/08/21 19:08:59] INFO: Switching to manual fan control (100 %)
[2020/08/21 19:08:59] INFO: Changing voltage from 19500 to 16000 mV gradually
[2020/08/21 19:09:45] INFO: Raising freq from 50 to 400 Mhz gradually
[2020/08/21 19:09:52] INFO: Switching to manual fan control (96 %)
[2020/08/21 19:09:52] INFO: Start mining!
[2020/08/21 19:10:52] INFO: Changing voltage from 16000 to 15800 mV gradually
[2020/08/21 19:11:18] INFO: Changing voltage from 15800 to 15600 mV gradually
[2020/08/21 19:11:44] INFO: Changing voltage from 15600 to 15400 mV gradually
[2020/08/21 19:12:09] ERROR: src/chip139x.c:1049 chain[0] — Failed to receive chip replies
[2020/08/21 19:12:10] ERROR: src/chip139x.c:1049 chain[0] — Failed to receive chip replies
[2020/08/21 19:12:11] ERROR: src/chip139x.c:1049 chain[1] — Failed to receive chip replies
[2020/08/21 19:12:12] ERROR: src/chip139x.c:1049 chain[1] — Failed to receive chip replies
[2020/08/21 19:12:14] ERROR: src/chip139x.c:1049 chain[0] — Failed to receive chip replies
[2020/08/21 19:12:15] ERROR: src/chip139x.c:1049 chain[0] — Failed to receive chip replies
[2020/08/21 19:12:16] ERROR: src/chip139x.c:1049 chain[1] — Failed to receive chip replies
[2020/08/21 19:12:17] ERROR: src/temp.c:217 chain[0] sen[3] — Lost, no updates for 10 sec
[2020/08/21 19:12:17] ERROR: src/temp.c:217 chain[1] sen[0] — Lost, no updates for 10 sec
[2020/08/21 19:12:17] ERROR: src/temp.c:217 chain[1] sen[1] — Lost, no updates for 10 sec
[2020/08/21 19:12:17] ERROR: src/chip139x.c:1049 chain[1] — Failed to receive chip replies
[2020/08/21 19:12:18] ERROR: src/temp.c:217 chain[0] sen[0] — Lost, no updates for 10 sec
[2020/08/21 19:12:18] ERROR: src/temp.c:217 chain[0] sen[1] — Lost, no updates for 10 sec
[2020/08/21 19:12:18] ERROR: src/temp.c:217 chain[0] sen[2] — Lost, no updates for 10 sec
[2020/08/21 19:12:18] ERROR: driver-btm-chain.c:967 chain[0] — Failed to read temp from all sensors!
[2020/08/21 19:12:18] INFO: chain[0] — Shutting down the chain
[2020/08/21 19:12:19] ERROR: src/chip139x.c:1049 chain[0] — Failed to receive chip replies
[2020/08/21 19:12:20] ERROR: src/temp.c:217 chain[1] sen[2] — Lost, no updates for 10 sec
[2020/08/21 19:12:20] ERROR: src/temp.c:217 chain[1] sen[3] — Lost, no updates for 10 sec
[2020/08/21 19:12:20] ERROR: driver-btm-chain.c:967 chain[1] — Failed to read temp from all sensors!
[2020/08/21 19:12:20] INFO: chain[1] — Shutting down the chain
[2020/08/21 19:12:20] ERROR: src/chip139x.c:1049 chain[0] — Failed to receive chip replies
[2020/08/21 19:12:21] ERROR: src/chip139x.c:1049 chain[1] — Failed to receive chip replies
[2020/08/21 19:12:22] ERROR: src/chip139x.c:1049 chain[1] — Failed to receive chip replies
[2020/08/21 19:12:23] ERROR: driver-btm-chain.c:687 chain[1] — Voltage is different, cur=1164 mV tgt=15400 mV
[2020/08/21 19:12:24] WARN: No working chains
[2020/08/21 19:12:24] INFO: Shutting down the miner
[2020/08/21 19:12:24] INFO: Stopping FPGA queue
[2020/08/21 19:12:24] INFO: chain[0] — Shutting down the chain
[2020/08/21 19:12:24] INFO: chain[1] — Shutting down the chain
[2020/08/21 19:12:24] INFO: chain[2] — Shutting down the chain
[2020/08/21 19:12:24] INFO: Power OFF

legendary

Activity: 2744

Merit: 2373

Bull market is coming?

According to your logs «Failed to receive chip replies» your hashboard might be overheating that could lead to miner autoshutdown for overheating protection.

The solution is already on the above post by mikeywith reducing the frequency might solve the issue. If not, try to increase the fan speed or set it fixed to the maximum.

You can also, try to downvolt and manually set it to the lower frequency just to get rid of this issue.

The guide is already on asic.to manual or download it from here https://asic.to/download/manual_english/

And check this part.

Enable the #3 for auto downscale if the HW errors still occur.

full member

Activity: 228

Merit: 101

NEM (XEM) Top Coin

Dear Mikeywith

my t17+ have this log now..and after 15 min power off automatically and again miner work for 15 min …i don’t know whats the problem…please guide me …thanks

[1970/01/01 00:05:10] INFO: Detected 256 Mb of RAM
[1970/01/01 00:05:10] INFO: Switching to manual fan control (30 %)
[1970/01/01 00:05:10] INFO: Checking fans
[1970/01/01 00:05:15] INFO: fan[0] — OK
[1970/01/01 00:05:15] INFO: fan[1] — OK
[1970/01/01 00:05:15] INFO: fan[2] — OK
[1970/01/01 00:05:15] INFO: fan[3] — OK
[1970/01/01 00:05:21] INFO: Power ON
[1970/01/01 00:05:23] INFO: Starting FPGA queue
[1970/01/01 00:05:23] INFO: Initializing hash boards
[1970/01/01 00:05:23] INFO: chain[2] — Initializing
[1970/01/01 00:05:23] INFO: chain[1] — Initializing
[1970/01/01 00:05:23] INFO: chain[0] — Initializing
[1970/01/01 00:05:36] ERROR: src/chip139x.c:1049 chain[2] — Failed to receive chip replies
[1970/01/01 00:05:37] ERROR: src/chip139x.c:1049 chain[2] — Failed to receive chip replies
[1970/01/01 00:05:38] ERROR: src/chip139x.c:1049 chain[2] — Failed to receive chip replies
[1970/01/01 00:05:38] WARN: chain[2] — 0 of 44 chips detected
[1970/01/01 00:05:39] INFO: chain[1] — 44 chips detected
[1970/01/01 00:05:40] INFO: chain[0] — 44 chips detected
[1970/01/01 00:05:48] ERROR: src/chip139x.c:1049 chain[2] — Failed to receive chip replies
[1970/01/01 00:05:49] ERROR: src/chip139x.c:1049 chain[2] — Failed to receive chip replies
[1970/01/01 00:05:50] ERROR: src/chip139x.c:1049 chain[2] — Failed to receive chip replies
[1970/01/01 00:05:50] WARN: chain[2] — 0 of 44 chips detected
[1970/01/01 00:05:59] ERROR: src/chip139x.c:1049 chain[2] — Failed to receive chip replies
[1970/01/01 00:06:00] ERROR: src/chip139x.c:1049 chain[2] — Failed to receive chip replies
[1970/01/01 00:06:01] ERROR: src/chip139x.c:1049 chain[2] — Failed to receive chip replies
[1970/01/01 00:06:01] WARN: chain[2] — 0 of 44 chips detected
[1970/01/01 00:06:01] ERROR: driver-btm-chain.c:488 chain[2] — Failed to detect ASIC chips
[1970/01/01 00:06:01] INFO: chain[2] — Shutting down the chain
[1970/01/01 00:06:02] ERROR: driver-btm-base.c:356 chain[2] — Initialization failed
[1970/01/01 00:06:05] INFO: Start-up temperature is 30 C (min -15 C)
[1970/01/01 00:06:05] INFO: Switching to manual fan control (100 %)
[1970/01/01 00:06:05] INFO: Changing voltage from 19500 to 18500 mV gradually
[1970/01/01 00:06:35] INFO: Raising freq from 50 to 650 Mhz gradually
[1970/01/01 00:06:48] INFO: Switching to manual fan control (96 %)
[1970/01/01 00:06:48] INFO: Start mining!
[1970/01/01 00:07:48] INFO: Changing voltage from 18500 to 18300 mV gradually
[1970/01/01 00:08:12] INFO: Changing voltage from 18300 to 18200 mV gradually
[1970/01/01 00:10:24] INFO: Changing voltage from 18200 to 18100 mV gradually
[1970/01/01 00:11:36] INFO: Changing voltage from 18100 to 18000 mV gradually
[1970/01/01 00:12:49] INFO: Changing voltage from 18000 to 17900 mV gradually
[1970/01/01 00:14:02] INFO: Changing voltage from 17900 to 17800 mV gradually
[1970/01/01 00:15:15] INFO: Changing voltage from 17800 to 17700 mV gradually
[1970/01/01 00:16:28] INFO: Changing voltage from 17700 to 17600 mV gradually
[1970/01/01 00:17:41] INFO: Changing voltage from 17600 to 17500 mV gradually
[1970/01/01 00:18:54] INFO: Changing voltage from 17500 to 17400 mV gradually
[1970/01/01 00:20:02] ERROR: src/chip139x.c:1049 chain[1] — Failed to receive chip replies
[1970/01/01 00:20:03] ERROR: src/chip139x.c:1049 chain[1] — Failed to receive chip replies
[1970/01/01 00:20:05] ERROR: src/chip139x.c:1049 chain[0] — Failed to receive chip replies
[1970/01/01 00:20:06] ERROR: src/chip139x.c:1049 chain[0] — Failed to receive chip replies
[1970/01/01 00:20:07] INFO: Changing voltage from 17400 to 17300 mV gradually
[1970/01/01 00:20:07] ERROR: src/chip139x.c:1049 chain[1] — Failed to receive chip replies
[1970/01/01 00:20:08] ERROR: src/chip139x.c:1049 chain[1] — Failed to receive chip replies
[1970/01/01 00:20:10] ERROR: src/temp.c:217 chain[1] sen[1] — Lost, no updates for 10 sec
[1970/01/01 00:20:10] ERROR: src/chip139x.c:1049 chain[0] — Failed to receive chip replies
[1970/01/01 00:20:11] ERROR: src/temp.c:217 chain[0] sen[0] — Lost, no updates for 10 sec
[1970/01/01 00:20:11] ERROR: src/temp.c:217 chain[0] sen[1] — Lost, no updates for 10 sec
[1970/01/01 00:20:11] ERROR: src/temp.c:217 chain[0] sen[2] — Lost, no updates for 10 sec
[1970/01/01 00:20:11] ERROR: src/temp.c:217 chain[0] sen[3] — Lost, no updates for 10 sec
[1970/01/01 00:20:11] ERROR: driver-btm-chain.c:967 chain[0] — Failed to read temp from all sensors!
[1970/01/01 00:20:11] INFO: chain[0] — Shutting down the chain
[1970/01/01 00:20:11] ERROR: src/chip139x.c:1049 chain[0] — Failed to receive chip replies
[1970/01/01 00:20:12] ERROR: src/chip139x.c:1049 chain[1] — Failed to receive chip replies
[1970/01/01 00:20:13] ERROR: src/chip139x.c:1049 chain[1] — Failed to receive chip replies
[1970/01/01 00:20:15] ERROR: src/temp.c:217 chain[1] sen[0] — Lost, no updates for 10 sec
[1970/01/01 00:20:15] ERROR: src/temp.c:217 chain[1] sen[2] — Lost, no updates for 10 sec
[1970/01/01 00:20:15] ERROR: src/temp.c:217 chain[1] sen[3] — Lost, no updates for 10 sec
[1970/01/01 00:20:15] ERROR: driver-btm-chain.c:967 chain[1] — Failed to read temp from all sensors!
[1970/01/01 00:20:15] INFO: chain[1] — Shutting down the chain
[1970/01/01 00:20:15] ERROR: src/chip139x.c:1049 chain[0] — Failed to receive chip replies
[1970/01/01 00:20:16] ERROR: src/chip139x.c:1049 chain[0] — Failed to receive chip replies
[1970/01/01 00:20:17] WARN: No working chains
[1970/01/01 00:20:17] INFO: Shutting down the miner
[1970/01/01 00:20:17] ERROR: src/chip139x.c:1049 chain[1] — Failed to receive chip replies
[1970/01/01 00:20:18] ERROR: src/chip139x.c:1049 chain[1] — Failed to receive chip replies
[1970/01/01 00:20:19] INFO: Stopping FPGA queue
[1970/01/01 00:20:19] INFO: chain[0] — Shutting down the chain
[1970/01/01 00:20:19] INFO: chain[1] — Shutting down the chain
[1970/01/01 00:20:19] INFO: chain[2] — Shutting down the chain
[1970/01/01 00:20:19] INFO: Power OFF

legendary

Activity: 1764

Merit: 4829

be constructive or S.T.F.U

What do you mean by resetting it manually?

At which point do you get this output?

[2020/08/17 17:53:09] WARN: chain[1] — 0 of 44 chips detected
[2020/08/17 17:53:10] INFO: chain[0] — 44 chips detected
[2020/08/17 17:53:18] WARN: chain[2] — 24 of 44 chips detected

Anyway, to answer your question, you need to go

Miner Configuration > Chain Frequency settings

Notice that there are two «Chain Frequency settings» tabs, you want the second to the left, scroll down and set the voltage and frequency you want.

Before you do that I suggest you go to

Miner Configuration > Profile Setting

Please note that your chances are slim to nothing, but it still worth the try.

full member

Activity: 228

Merit: 101

NEM (XEM) Top Coin

I updated my asic t17+ 55 ths to framework of asic.to successfully .My miner status and log is on below….you know that we can change voltage and frequency of chain manually in asic.to framework. i want to know with change of voltage or frequency of chains , can i solve this chip issue? any recommend setting is exists for asic.to? thanks.

my asic is this status

[2020/08/16 12:32:43] WARN: chain[2] — 0 of 44 chips detected
[2020/08/16 12:32:44] INFO: chain[1] — 44 chips detected
[2020/08/16 12:32:45] INFO: chain[0] — 44 chips detected

and after reset it manually it change to it:

[2020/08/17 17:53:09] WARN: chain[1] — 0 of 44 chips detected
[2020/08/17 17:53:10] INFO: chain[0] — 44 chips detected
[2020/08/17 17:53:18] WARN: chain[2] — 24 of 44 chips detected

Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty ([email protected]) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
  Normal zone: 480 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 202820K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 26556K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
   vector : 0xffff0000 — 0xffff1000 ( 4 kB)
   fixmap : 0xffc00000 — 0xfff00000 (3072 kB)
   vmalloc : 0xcf800000 — 0xff800000 ( 768 MB)
   lowmem : 0xc0000000 — 0xcf000000 ( 240 MB)
   pkmap : 0xbfe00000 — 0xc0000000 ( 2 MB)
   modules : 0xbf000000 — 0xbfe00000 ( 14 MB)
   .text : 0xc0008000 — 0xc090c424 (9234 kB)
   .init : 0xc0a00000 — 0xc0b00000 (1024 kB)
   .data : 0xc0b00000 — 0xc0b39fe0 ( 232 kB)
   .bss : 0xc0b39fe0 — 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80×30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 — 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 — Copyright 2005-2007 Rodolfo Giometti

PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs…
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 13516K (ccdcd000 — cdb00000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver — 3.2.6-k
e1000e: Copyright(c) 1999 — 2015 Intel Corporation.
ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on «pl35x-nand»:
0x000000000000-0x000002800000 : «BOOT.bin-env-dts-kernel»
0x000002800000-0x000004800000 : «ramfs»
0x000004800000-0x000005000000 : «configs»
0x000005000000-0x000006000000 : «reserve»
0x000006000000-0x000008000000 : «ramfs-bak»
0x000008000000-0x000010000000 : «reserve1»
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for ‘xlnx,zynq-ddrc-a05’
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn’t mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 — c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name «configs», size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 5/2, WL threshold: 4096, image sequence number: 2881768101
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread «ubi_bgt0d» started, PID 708
UBIFS (ubi0:0): background thread «ubifs_bgt0_0» started, PID 711
UBIFS (ubi0:0): recovery needed
UBIFS (ubi0:0): recovery completed
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name «configs»
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 2AF94D23-0760-4801-8C27-532C11A81FC1, small LPT model
ubi1: attaching mtd5
ubi1: scanning is finished
ubi1: attached mtd5 (name «reserve1», size 128 MiB)
ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi1: good PEBs: 1020, bad PEBs: 4, corrupted PEBs: 0
ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi1: max/mean erase counter: 177/36, WL threshold: 4096, image sequence number: 3563076859
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread «ubi_bgt1d» started, PID 720
UBIFS (ubi1:0): background thread «ubifs_bgt1_0» started, PID 723
UBIFS (ubi1:0): recovery needed
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name «reserve1»
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID A21581E4-693A-4BBF-A66A-FCE5ACD2EF7F, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
random: nonblocking pool is initialized
[2020/08/14 09:02:47] INFO: Detected 256 Mb of RAM
[2020/08/14 09:02:47] INFO: Switching to manual fan control (30 %)
[2020/08/14 09:02:47] INFO: Checking fans
[2020/08/14 09:02:51] INFO: fan[0] — OK
[2020/08/14 09:02:51] INFO: fan[1] — OK
[2020/08/14 09:02:51] INFO: fan[2] — OK
[2020/08/14 09:02:51] INFO: fan[3] — OK
[2020/08/14 09:02:57] INFO: Power ON
[2020/08/14 09:02:59] INFO: Starting FPGA queue
[2020/08/14 09:02:59] INFO: Initializing hash boards
[2020/08/14 09:02:59] INFO: chain[2] — Initializing
[2020/08/14 09:02:59] INFO: chain[1] — Initializing
[2020/08/14 09:02:59] INFO: chain[0] — Initializing
[2020/08/14 09:03:12] ERROR: src/chip139x.c:1044 chain[2] — Failed to receive chip replies
[2020/08/14 09:03:13] ERROR: src/chip139x.c:1044 chain[2] — Failed to receive chip replies
[2020/08/14 09:03:14] ERROR: src/chip139x.c:1044 chain[2] — Failed to receive chip replies
[2020/08/14 09:03:14] WARN: chain[2] — 0 of 44 chips detected
[2020/08/14 09:03:14] INFO: Shutting down the miner
[2020/08/14 09:03:14] INFO: Stopping FPGA queue
[2020/08/14 09:03:14] INFO: chain[0] — Shutting down the chain
[2020/08/14 09:03:15] INFO: chain[1] — Shutting down the chain
[2020/08/14 09:03:15] INFO: chain[1] — 44 chips detected
[2020/08/14 09:03:15] INFO: chain[2] — Shutting down the chain
[2020/08/14 09:03:16] INFO: Power OFF
[2020/08/14 09:03:25] INFO: Detected 256 Mb of RAM
[2020/08/14 09:03:25] INFO: Switching to manual fan control (30 %)
[2020/08/14 09:03:25] INFO: Checking fans
[2020/08/14 09:03:26] INFO: fan[0] — OK
[2020/08/14 09:03:26] INFO: fan[1] — OK
[2020/08/14 09:03:26] INFO: fan[2] — OK
[2020/08/14 09:03:26] INFO: fan[3] — OK
[2020/08/14 09:03:32] INFO: Power ON
[2020/08/14 09:03:34] INFO: Starting FPGA queue
[2020/08/14 09:03:34] INFO: Initializing hash boards
[2020/08/14 09:03:34] INFO: chain[2] — Initializing
[2020/08/14 09:03:34] INFO: chain[1] — Initializing
[2020/08/14 09:03:34] INFO: chain[0] — Initializing
[2020/08/14 09:03:48] ERROR: src/chip139x.c:1044 chain[2] — Failed to receive chip replies
[2020/08/14 09:03:49] ERROR: src/chip139x.c:1044 chain[2] — Failed to receive chip replies
[2020/08/14 09:03:50] ERROR: src/chip139x.c:1044 chain[2] — Failed to receive chip replies
[2020/08/14 09:03:50] WARN: chain[2] — 0 of 44 chips detected
[2020/08/14 09:03:51] INFO: chain[1] — 44 chips detected
[2020/08/14 09:03:52] INFO: chain[0] — 44 chips detected
[2020/08/14 09:03:59] ERROR: src/chip139x.c:1044 chain[2] — Failed to receive chip replies
[2020/08/14 09:04:00] ERROR: src/chip139x.c:1044 chain[2] — Failed to receive chip replies
[2020/08/14 09:04:01] ERROR: src/chip139x.c:1044 chain[2] — Failed to receive chip replies
[2020/08/14 09:04:01] WARN: chain[2] — 0 of 44 chips detected
[2020/08/14 09:04:11] ERROR: src/chip139x.c:1044 chain[2] — Failed to receive chip replies
[2020/08/14 09:04:12] ERROR: src/chip139x.c:1044 chain[2] — Failed to receive chip replies
[2020/08/14 09:04:13] ERROR: src/chip139x.c:1044 chain[2] — Failed to receive chip replies
[2020/08/14 09:04:13] WARN: chain[2] — 0 of 44 chips detected
[2020/08/14 09:04:13] ERROR: driver-btm-chain.c:488 chain[2] — Failed to detect ASIC chips
[2020/08/14 09:04:13] INFO: chain[2] — Shutting down the chain
[2020/08/14 09:04:13] ERROR: driver-btm-base.c:361 chain[2] — Initialization failed
[2020/08/14 09:04:17] INFO: Start-up temperature is 26 C (min -15 C)
[2020/08/14 09:04:17] INFO: Switching to manual fan control (100 %)
[2020/08/14 09:04:17] INFO: Changing voltage from 19500 to 18500 mV gradually
[2020/08/14 09:04:47] INFO: Raising freq from 50 to 500 Mhz gradually
[2020/08/14 09:04:56] INFO: Switching to automatic fan control (75 C)
[2020/08/14 09:04:56] INFO: Start mining!
[2020/08/17 17:29:15] INFO: Changing voltage from 19000 to 18800 mV gradually
[2020/08/17 17:29:38] INFO: Changing voltage from 18800 to 18600 mV gradually
[2020/08/17 17:30:01] INFO: Changing voltage from 18600 to 18400 mV gradually
[2020/08/17 17:30:24] INFO: Changing voltage from 18400 to 18200 mV gradually
[2020/08/17 17:30:46] INFO: Changing voltage from 18200 to 18000 mV gradually
[2020/08/17 17:31:06] INFO: Shutting down the miner
[2020/08/17 17:31:06] INFO: Setting freq to 50 Mhz gradually
[2020/08/17 17:31:11] INFO: Stopping FPGA queue
[2020/08/17 17:31:11] INFO: chain[0] — Shutting down the chain
[2020/08/17 17:31:18] INFO: Detected 256 Mb of RAM
[2020/08/17 17:31:18] INFO: Switching to manual fan control (30 %)
[2020/08/17 17:31:18] INFO: Checking fans
[2020/08/17 17:31:19] INFO: fan[0] — OK
[2020/08/17 17:31:19] INFO: fan[1] — OK
[2020/08/17 17:31:19] INFO: fan[2] — OK
[2020/08/17 17:31:19] INFO: fan[3] — OK
[2020/08/17 17:31:25] INFO: Power ON
[2020/08/17 17:31:27] INFO: Starting FPGA queue
[2020/08/17 17:31:27] INFO: Initializing hash boards
[2020/08/17 17:31:27] INFO: chain[2] — Initializing
[2020/08/17 17:31:27] INFO: chain[1] — Initializing
[2020/08/17 17:31:27] INFO: chain[0] — Initializing
[2020/08/17 17:31:42] WARN: chain[2] — 24 of 44 chips detected
[2020/08/17 17:31:43] ERROR: src/chip139x.c:1044 chain[1] — Failed to receive chip replies
[2020/08/17 17:31:44] ERROR: src/chip139x.c:1044 chain[1] — Failed to receive chip replies
[2020/08/17 17:31:45] ERROR: src/chip139x.c:1044 chain[1] — Failed to receive chip replies
[2020/08/17 17:31:45] WARN: chain[1] — 0 of 44 chips detected
[2020/08/17 17:31:46] INFO: chain[0] — 44 chips detected
[2020/08/17 17:31:54] WARN: chain[2] — 24 of 44 chips detected
[2020/08/17 17:31:57] WARN: chain[1] — 20 of 44 chips detected
[2020/08/17 17:32:05] WARN: chain[2] — 24 of 44 chips detected
[2020/08/17 17:32:05] ERROR: driver-btm-chain.c:488 chain[2] — Failed to detect ASIC chips
[2020/08/17 17:32:05] INFO: chain[2] — Shutting down the chain
[2020/08/17 17:32:06] ERROR: driver-btm-base.c:361 chain[2] — Initialization failed
[2020/08/17 17:32:08] WARN: chain[1] — 20 of 44 chips detected
[2020/08/17 17:32:08] ERROR: driver-btm-chain.c:488 chain[1] — Failed to detect ASIC chips
[2020/08/17 17:32:08] INFO: chain[1] — Shutting down the chain
[2020/08/17 17:32:09] ERROR: driver-btm-base.c:361 chain[1] — Initialization failed
[2020/08/17 17:32:12] INFO: Start-up temperature is 21 C (min -15 C)
[2020/08/17 17:32:12] INFO: Switching to manual fan control (100 %)
[2020/08/17 17:32:12] INFO: Changing voltage from 19500 to 19000 mV gradually
[2020/08/17 17:32:36] INFO: Raising freq from 50 to 700 Mhz gradually
[2020/08/17 17:32:49] INFO: Switching to manual fan control (95 %)
[2020/08/17 17:32:49] INFO: Start mining!
[2020/08/17 17:52:42] INFO: Detected 256 Mb of RAM
[2020/08/17 17:52:42] INFO: Switching to manual fan control (30 %)
[2020/08/17 17:52:42] INFO: Checking fans
[2020/08/17 17:52:43] INFO: fan[0] — OK
[2020/08/17 17:52:43] INFO: fan[1] — OK
[2020/08/17 17:52:43] INFO: fan[2] — OK
[2020/08/17 17:52:43] INFO: fan[3] — OK
[2020/08/17 17:52:49] INFO: Power ON
[2020/08/17 17:52:51] INFO: Starting FPGA queue
[2020/08/17 17:52:51] INFO: Initializing hash boards
[2020/08/17 17:52:51] INFO: chain[2] — Initializing
[2020/08/17 17:52:51] INFO: chain[1] — Initializing
[2020/08/17 17:52:51] INFO: chain[0] — Initializing
[2020/08/17 17:53:06] WARN: chain[2] — 24 of 44 chips detected
[2020/08/17 17:53:07] ERROR: src/chip139x.c:1044 chain[1] — Failed to receive chip replies
[2020/08/17 17:53:08] ERROR: src/chip139x.c:1044 chain[1] — Failed to receive chip replies
[2020/08/17 17:53:09] ERROR: src/chip139x.c:1044 chain[1] — Failed to receive chip replies
[2020/08/17 17:53:09] WARN: chain[1] — 0 of 44 chips detected
[2020/08/17 17:53:10] INFO: chain[0] — 44 chips detected
[2020/08/17 17:53:18] WARN: chain[2] — 24 of 44 chips detected
[2020/08/17 17:53:19] ERROR: src/chip139x.c:1044 chain[1] — Failed to receive chip replies
[2020/08/17 17:53:20] ERROR: src/chip139x.c:1044 chain[1] — Failed to receive chip replies
[2020/08/17 17:53:21] ERROR: src/chip139x.c:1044 chain[1] — Failed to receive chip replies
[2020/08/17 17:53:21] WARN: chain[1] — 0 of 44 chips detected
[2020/08/17 17:53:29] WARN: chain[2] — 24 of 44 chips detected
[2020/08/17 17:53:29] ERROR: driver-btm-chain.c:488 chain[2] — Failed to detect ASIC chips
[2020/08/17 17:53:29] INFO: chain[2] — Shutting down the chain
[2020/08/17 17:53:30] ERROR: driver-btm-base.c:361 chain[2] — Initialization failed
[2020/08/17 17:53:30] ERROR: src/chip139x.c:1044 chain[1] — Failed to receive chip replies
[2020/08/17 17:53:31] ERROR: src/chip139x.c:1044 chain[1] — Failed to receive chip replies
[2020/08/17 17:53:32] ERROR: src/chip139x.c:1044 chain[1] — Failed to receive chip replies
[2020/08/17 17:53:32] WARN: chain[1] — 0 of 44 chips detected
[2020/08/17 17:53:32] ERROR: driver-btm-chain.c:488 chain[1] — Failed to detect ASIC chips
[2020/08/17 17:53:32] INFO: chain[1] — Shutting down the chain
[2020/08/17 17:53:33] ERROR: driver-btm-base.c:361 chain[1] — Initialization failed
[2020/08/17 17:53:36] INFO: Start-up temperature is 20 C (min -15 C)
[2020/08/17 17:53:36] INFO: Switching to manual fan control (100 %)
[2020/08/17 17:53:36] INFO: Changing voltage from 19500 to 19000 mV gradually
[2020/08/17 17:54:00] INFO: Raising freq from 50 to 700 Mhz gradually
[2020/08/17 17:54:13] INFO: Switching to manual fan control (90 %)
[2020/08/17 17:54:13] INFO: Start mining!

Источник

Содержание

Т17е 50тн
FriD89
skarm
FriD89
MaDSerg
Numbric
FriD89
daddizz
obelix13
t17 нет инициализация хэш плат
Demiansikora
dyakoff
Fredrik
Demiansikora
sagri
mrcredovz

Т17е 50тн

FriD89

Пляшущий с бубном

Люди помогите, не могу запустить асик!

2021-05-23 18:48:07:driver-btm-api.c:486:check_chain_conf_same: Config are different, min = 1790, max = 1870, diff is too large.
2021-05-23 18:48:07:auto_adapt.c:273:is_sweep_failed_before: open sweep tag failed
2021-05-23 18:48:07:driver-btm-api.c:247:set_miner_status: ERROR_SOC_INIT
2021-05-23 18:48:07:driver-btm-api.c:176:stop_mining: stop mining: soc init failed!
2021-05-23 18:48:07:driver-btm-api.c:147:killall_hashboard: ****power off hashboard****

skarm

Люди помогите, не могу запустить асик!

Русский: 2021-05-23 18:48:07:драйвер-btm-api.c:486:check_chain_conf_same: Конфигурации разные, min = 1790, max = 1870, разница слишком велика.
2021-05-23 18:48:07:auto_adapt.c:273:is_sweep_failed_before: не удалось открыть тег развертки
2021-05-23 18:48:07:драйвер-btm-api.c:247:set_miner_status: ERROR_SOC_INIT
2021-05-23 18:48:07:драйвер-btm-api.c:176:stop_mining: остановка майнинга: сбой инициализации soc!
2021-05-23 18:48:07:драйвер-btm-api.c:147:killall_hashboard: ****отключение питания hashboard****

Я ж говорю, АСИКи — зло!

FriD89

Пляшущий с бубном

Я ж говорю, АСИКи — зло!

MaDSerg

Бывалый

Numbric

Свой человек

Люди помогите, не могу запустить асик!

FriD89

Пляшущий с бубном

daddizz

Пляшущий с бубном

obelix13

Знающий

Доброго времени суток.
Подскажите кто решил такую проблему на Т17+?

Источник

t17 нет инициализация хэш плат

Demiansikora

Пляшущий с бубном

2021-10-14 05:13:23 driver-btm-api.c:663:init_freq_mode: This is scan-user version
2021-10-14 05:13:23 driver-btm-api.c:2028:bitmain_soc_init: opt_multi_version = 1
2021-10-14 05:13:23 driver-btm-api.c:2029:bitmain_soc_init: opt_bitmain_ab = 1
2021-10-14 05:13:23 driver-btm-api.c:2030:bitmain_soc_init: opt_bitmain_work_mode = 0
2021-10-14 05:13:23 driver-btm-api.c:2031:bitmain_soc_init: Miner compile time: Thu Apr 23 16:29:07 CST 2020 type: Antminer T17
2021-10-14 05:13:23 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-10-14 05:13:23 driver-btm-api.c:1844:show_sn: no SN got, please write SN to /nvdata/sn
2021-10-14 05:13:23 driver-btm-api.c:1167:miner_device_init: Detect 256MB control board of XILINX
2021-10-14 05:13:23 driver-btm-api.c:1115:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2021-10-14 05:13:23 thread.c:885:create_read_nonce_reg_thread: create thread
2021-10-14 05:13:29 driver-btm-api.c:1099:init_miner_version: miner ID : 803cad482b10481c
2021-10-14 05:13:29 driver-btm-api.c:1105:init_miner_version: FPGA Version = 0xB013
2021-10-14 05:13:31 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2021-10-14 05:13:33 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2021-10-14 05:13:35 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2021-10-14 05:13:35 driver-btm-api.c:737:get_product_id: product_id[0] = 1
2021-10-14 05:13:35 driver-btm-api.c:737:get_product_id: product_id[1] = 1
2021-10-14 05:13:35 driver-btm-api.c:737:get_product_id: product_id[2] = 1
2021-10-14 05:13:35 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[0] = 1
2021-10-14 05:13:35 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[1] = 1
2021-10-14 05:13:35 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[2] = 1
2021-10-14 05:13:35 driver-btm-api.c:1919:bitmain_board_init: g_ccdly_opt = 1
2021-10-14 05:13:35 driver-btm-api.c:676:_set_project_type: project:2
2021-10-14 05:13:35 driver-btm-api.c:706:_set_project_type: Project type: Antminer T17
2021-10-14 05:13:35 driver-btm-api.c:717:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2021-10-14 05:13:35 driver-btm-api.c:718:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2021-10-14 05:13:35 driver-btm-api.c:717:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2021-10-14 05:13:35 driver-btm-api.c:718:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2021-10-14 05:13:35 driver-btm-api.c:717:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2021-10-14 05:13:35 driver-btm-api.c:718:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2021-10-14 05:13:37 driver-btm-api.c:1939:bitmain_board_init: Fan check passed.
2021-10-14 05:13:38 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2021-10-14 05:13:42 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2021-10-14 05:13:43 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2021-10-14 05:13:47 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2021-10-14 05:13:49 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2021-10-14 05:13:52 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2021-10-14 05:13:52 thread.c:880:create_pic_heart_beat_thread: create thread
2021-10-14 05:13:52 power_api.c:55 ower_init: power init .
2021-10-14 05:13:52 driver-btm-api.c:1949:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2021-10-14 05:13:52 power_api.c:46 ower_off: init gpio907
2021-10-14 05:14:24 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 .
2021-10-14 05:14:30 power_api.c:124:check_voltage_multi: retry time: 0
2021-10-14 05:14:32 power_api.c:86:get_average_voltage: chain[0], voltage is: 21.069404
2021-10-14 05:14:33 power_api.c:86:get_average_voltage: chain[1], voltage is: 20.346885
2021-10-14 05:14:35 power_api.c:86:get_average_voltage: chain[2], voltage is: 19.618242
2021-10-14 05:14:35 power_api.c:97:get_average_voltage: aveage voltage is: 20.344843
2021-10-14 05:14:35 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 20.34, more than 1.0v diff.
2021-10-14 05:14:36 power_api.c:124:check_voltage_multi: retry time: 1
2021-10-14 05:14:38 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.687539
2021-10-14 05:14:40 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.105849
2021-10-14 05:14:43 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.064931
2021-10-14 05:14:43 power_api.c:97:get_average_voltage: aveage voltage is: 17.952773
2021-10-14 05:14:43 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2021-10-14 05:14:43 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2021-10-14 05:14:53 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2021-10-14 05:15:03 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2021-10-14 05:15:13 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2021-10-14 05:15:16 driver-btm-api.c:352:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2021-10-14 05:15:16 driver-btm-api.c:352:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2021-10-14 05:15:17 driver-btm-api.c:352:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2021-10-14 05:15:17 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0xb4
2021-10-14 05:15:17 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2021-10-14 05:15:17 driver-btm-api.c:1693:check_clock_counter: freq 50 clock_counter_limit 6
2021-10-14 05:15:18 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2021-10-14 05:15:18 voltage[0] = 1690
2021-10-14 05:15:18 voltage[1] = 1690
2021-10-14 05:15:18 voltage[2] = 1730
2021-10-14 05:15:18 Voltage are different. Will exit.
2021-10-14 05:15:18 driver-btm-api.c:205:set_miner_status: ERROR_SOC_INIT
2021-10-14 05:15:18 driver-btm-api.c:146:stop_mining: stop mining: soc init failed!
2021-10-14 05:15:18 thread.c:930:cancel_read_nonce_reg_thread: cancel thread
2021-10-14 05:15:18 driver-btm-api.c:131:killall_hashboard: ****power off hashboard****

dyakoff

Бывалый

Не эксперт в асиках, но судя из лога, возможно в этом проблема:

no SN got, please write SN to /nvdata/sn

Fredrik

Свой человек

Demiansikora

Пляшущий с бубном

sagri

Свой человек

это похоже частая проблема 17 серии. ERROR_SOC_INIT
2021-10-14 05:15:18 Voltage are different. Will exit.

или БП накрывается или в ремонт

попробуй по одной плате подключать.
как вариант нашел что возможно проблема в EEPROM на хэш плате.

mrcredovz

Бывалый

target_vol = 17.00, actural_vol = 20.34, more than 1.0v diff.

Вольтаж не совпадает оценочный и актуальный. Должно быть не более 0.5 разницы. Попробуй почистить асик, подтянуть клеммы, перезагрузи несколько раз, прошей последней прошивкой.

Источник

Как устранить ошибку температуры в журнале Antminer T17

Система контроля температуры майнера полагается на чип датчика температуры хэш-платы для предоставления данных в реальном времени для обнаружения. Различная хэш-плата может иметь несколько термочувствительных чипов, обычно расположенных рядом с хэш-чипом. Если чип не обнаружен при запуске майнера, хэш-плата не сработает.

Следует отметить, что микросхема датчика температуры обычно не повреждается. Когда возникает температурная ошибка, некоторые обслуживающие персонал напрямую заменяют чип датчика температуры, но неисправность не может быть устранена.

На самом деле проблема не в самом чипе. Скорее всего, это вызвано неисправной микросхемой U1 или последней микросхемой, или это может быть вызвано пониженным напряжением источника питания.

Если весь журнал майнера указывает на ошибку температуры, тогда мы можем сначала обновить прошивку. Если ошибка все еще отображается, проверьте силу тока на входе. Пониженное напряжение источника питания также не позволяет всей машине считывать температуру.

Например, следующая подсказка:

2020/04/27 04:15:48] WARN: chain[1] — 3 sensor(s) reported their temps!

[2020/04/27 04:16:02] ERROR: src/temp.c:218 chain[1] sen[2] — Lost, no updates for 10 sec

[2020/04/27 04:16:02] WARN: chain[1] — 2 sensor(s) reported their temps!

[2020/04/27 04:16:29] ERROR: src/temp.c:218 chain[1] sen[1] — Lost, no updates for 10 sec

[2020/04/27 04:16:29] WARN: chain[1] — 1 sensor(s) reported their temps!

[2020/04/27 04:17:29] INFO: Setting voltage from 17500 to 17400 mV gradually

[2020/04/27 04:17:39] ERROR: src/temp.c:218 chain[1] sen[3] — Lost, no updates for 10 sec

[2020/04/27 04:17:39] WARN: chain[1] — 0 sensor(s) reported their temps!

[2020/04/27 04:17:39] ERROR: driver-btm-chain.c:950 chain[1] — Failed to read temp from all sensors!

Если температура не может быть считана ни одной хэш-платой, ее необходимо снять и проверить с помощью тестером чипов антминер. Эта ситуация обычно вызвана неправильным хеш-чипом. Замените поврежденный чип, чтобы устранить неисправность.

Обратите внимание: использование хэш-платы от разных майнеров может привести к тому, что некоторая хэш-плата не сможет определить температуру. Поскольку версия хэш-платы отличается, используемая микросхема измерения температуры также может быть другой. Майнер распознает только одну программу прошивки на плате управления, остальные будут нечитаемыми.

Видеоурок по осмотру и ремонту хэш платы на примере модели: S9

(Методы обнаружения и восстановления большинства майнеров в Antminer в основном одинаковы)

Нажмите для просмотра:Видеоурок по ремонту и диагностике неисправностей AntminerS9.

Связанные инструменты обслуживания:

Официальный термореактивный гель — 220г

Новая версия многофункционального испытательного стенда

Инструмент для стружки олова

Нажмите, чтобы увидеть больше инструментов для обслуживания майнеров

заявлять
Учебники по ремонту и Скачать файлы относятся к оригинальным произведениям, которые запрещаются полностью или частично без письменного разрешения.

Источник

Ошибки Видеокарты При Майнинге

Самое полное собрание ошибок в майнинге на Windows, HiveOS и RaveOS и их быстрых и спокойных решений

Can’t find nonce with device CUDA_ERROR_LAUNCH_FAILED

Ошибка майнера Can’t find nonce

Ошибка говорит о том, что майнер не может найти нонс и сразу же сам предлагает решение — уменьшить разгон. Особенно начинающие майнеры стараются выжать из видеокарты максимум — разгоняют слишком сильно по ядру или памяти. В таком разгоне видеокарта даже может запуститься, но потом выдавать ошибки как указано ниже. Помните, лучше — стабильная отправка шар на пул, чем гонка за цифрами в майнере.

Зарабатывай на чужих сделках на бирже BingX. Подробнее — тут.

Phoenixminer Connection to API server failed — что делать?

Ошибка Connection to API server failed

Такая ошибка встречается на PhoenixMiner на операционной систему HiveOS. Она говорит о том, что майнинг-ферма/риг не может подключиться к серверу статистики. Что делать для ее решения:

Введите команду net-test и запомните/запишите сервер с низким пингом. После чего смените его в веб интерфейсе Hive (на воркере) и перезагрузите ваш риг.
Если это не помогло, выполните команду dnscrypt -i && sreboot

Phoenixminer CUDA error in CudaProgram.cu:474 : the launch timed out and was terminated (702)

Ошибка майнера Phoenixminer CUDA error in CudaProgram

Эта ошибка, как и в первом случае, говорит о переразгоне карты. Откатите видеокарту до заводских настроек и постепенно поднимайте разгон до тех пор, пока не будет ошибки.

UNABLE TO ENUM CUDA GPUS: INVALID DEVICE ORDINAL

Ошибка майнера Unable to enum CUDA GPUs: invalid device ordinal

Проверяем драйвера видеокарты и саму видеокарту на работоспособность (как она отмечена в диспетчере устройств, нет ли восклицательных знаков).
Если все ок, то проверяем райзера. Часто бывает, что именно райзер бывает причиной такой ошибки.

UNABLE TO ENUM CUDA GPUS: INSUFFICIENT CUDA DRIVER: 5000

Ошибка майнера Unable to enum CUDA GPUs: Insufficient CUDA driver: 5000

Аналогично предыдущей ошибке — проверяем драйвера видеокарты и саму видеокарту на работоспособность (как она отмечена в диспетчере устройств, нет ли восклицательных знаков).

NBMINER MINING PROGRAM UNEXPECTED EXIT.CODE: -1073740791, REASON: PROCESS CRASHED

Ошибка майнера NBMINER MINING PROGRAM UNEXPECTED EXIT.CODE: -1073740791, REASON: PROCESS CRASHED

Ошибка code 1073740791 nbminer возникает, если ваш риг/майнинг-ферма собраны из солянки Nvidia+AMD. В этом случае разделите майнинг на два .bat файла (или полетника, если вы на HiveOS). Один — с картами AMD, другой с картами Nvidia.

NBMINER CUDA ERROR: OUT OF MEMORY (ERR_NO=2) — как исправить?

Ошибка майнера NBMINER CUDA ERROR: OUT OF MEMORY (ERR_NO=2)

Одна из самых распространённых ошибок на Windows — нехватка памяти, в данном случае на майнере Nbminer, но встречается и в майнере Nicehash. Чтобы ее исправить — надо увеличить файл подкачки. Файл подкачки должен быть равен сумме гб всех видеокарт в риге плюс 10% запаса. Как увеличить файл подкачки — читаем тут.

GMINER ERROR ON GPU: OUT OF MEMORY STOPPED MINING ON GPU0

Ошибка майнера GMINER ERROR ON GPU: OUT OF MEMORY STOPPED MINING ON GPU0

В данном случае скорее всего виноват не файл подкачки, а переразгон по видеокарте, которая идет под номером 0. Сбавьте разгон и ошибка должна пропасть.

Socket error. the remote host closed the connection, в майнере Nbminer

Socket error. the remote host closed the connection

Также может быть описана как «ERROR — Failed to establish connection to mining pool: Socket operation timed out».
Сетевой конфликт — проверьте соединение рига с интернетом. Перегрузите роутер.
Также может быть, что провайдер закрывает соединение с пулом. Смените пул, попробуйте VPN или измените адреса DNS на внешнего провайдера, например cloudflare 1.1.1.1, 1.0.0.1

Server not responded on share, на майнере Gminer

Server not responded on share

Такая ошибка говорит о том, что у вас что-то с подключением к интернету, что критично для Gminer. Попробуйте сделать рестарт роутера и отключить watchdog на майнере.

DAG has been damaged check overclocking settings, в майнере Gminer

Также в этой ошибке может быть указано Device not responding, check overclocking settings.
Ошибка говорит о переразгоне, попробуйте сначала убавить его.
Если это не помогло, смените майнер — Gminer никогда не славился работой с видеокартами AMD. Мы рекомендуем поменять майнер на Teamredminer, а если вам критична поддержка майнером одновременно Nvidia и AMD видеокарт, то используйте Lolminer.
Если смена майнера не поможет, переставьте видеодрайвер.
Если и это не поможет, то нужно тестировать эту карту отдельно в слоте X16.

ERROR: Can’t start T-Rex, failed to initialize device map: can’t get busid, code -6

Ошибки настройки памяти с кодом -6 обычно указывают на проблему с драйвером.

Если у вас Windows, используйте программу DDU (DisplayDriverUninstaller), чтобы полностью удалить все драйверы Nvidia.
Перезагрузите систему.
Установите новый драйвер прямо с сайта Nvidia.
Перезагрузите систему снова.
Если у вас HiveOS/RaveOS — накатите чистый образ системы. Чтобы наверняка.

TREX: Can’t unlock GPU

Полный текст ошибки:
TREX: Can’t unlock GPU [ID=1, GPU #1], error code 15
WARN: Miner is going to shutdown…
WARN: NVML: can’t get fan speed for GPU #1, error code 15
WARN: NVML: can’t get power for GPU #1, error code 15
WARN: NVML: can’t get mem/core clock for GPU #1, error code 17

Решение:

Проверьте все кабельные соединения видеокарты и райзера, особенно кабеля питания.
Если с первый пунктом все ок, попробуйте поменять райзер на точно рабочий.
Если ошибка остается, вставьте видеокарту в разъем х16 напрямую в материнскую плату.

CAN’T START MINER, FAILED TO INITIALIZE DEVIS MAP, CAN’T GET BUSID, CODE -6

Ошибка майнера CAN’T START MINER, FAILED TO INITIALIZE DEVIS MAP, CAN’T GET BUSID, CODE -6

В конкретном случае была проблема в блоке питания, он не держал 3 видеокарты. После замены блока питания ошибка пропала.
Если вы уверены, что ваш мощности вашего блока питания достаточно, попробуйте сменить майнер.

Зарабатывай на чужих сделках на бирже BingX. Подробнее — тут.

ОШИБКА 511 ГРАДУСОВ НА ВИДЕОКАРТА

Ошибка 511 градусов видеокарта

Ошибка 511 говорит о неисправности райзера или питания карты. Проверьте все соединения. Для выявления неисправности рекомендуется запустить систему с одной картой. Протестировать, и затем добавлять по одной карте.

GPU driver error, no temps в HiveOS — что делать?

Вероятнее всего, вы получили эту ошибку, майнив на HiveOS. Причин ее появления может быть несколько — как софтовая, так и аппаратная (например райзер).
Можно попробовать обойтись малой кровью и вбить в HiveOS команду:
hive-replace -y —stable
Система по новой накатит стабильную версию HiveOS.

Если ошибка не уйдет — проверьте райзер.

GPU are lost, rebooting

Это не ошибка, а ее последствие. Что узнать какая ошибка приводит к перезагрузке карт, сделайте следующее:

Включите сохранение логов (по умолчанию они выключены) командой

logs-on

И перезагрузите риг.
После того как ошибка повторится можно будет скачать логи командами ниже.
Вы можете использовать следующую команду, чтобы загрузить логи майнера прямо с панели мониторинга;

message file «miner.log» -f=/var/log/miner/minername/minername.log

Итак, скажем, например, мне нужны логи TeamRedMiner
message file «teamredminer.log» -f=/var/log/miner/teamredminer/teamredminer.log

Отправленная командная строка будет выделена синим цветом. Загружаемый файл будет отображаться белым цветом. Нажав на него, вы сможете его скачать.
Эта команда позволит скачать лог системы

message file «syslog» -f=/var/log/syslog

exitcode=3 в HiveOS

Если ошибка не уйдет — проверьте райзер.

exitcode=1 в HiveOS

Данная ошибка возникает когда есть проблема с датой в биосе материнской платы (сбитое время) и (или) есть проблема с интернетом.
Если сбито время, то удаленно вы не сможете подключиться.
Тем не менее, обновление драйверов Nvidia должно пройти командой:

nvidia-driver-update —list

gpu fault detected 146

Скорее всего вы пытаетесь майнить с помощью Phoenix miner. Решения два:

Откатитесь на более старую версию, например на 5.4с
(Рекомендуемый вариант) Используйте Trex для видеокарт Nvidia и TeamRedMiner для AMD.

Waiting interface to come up — не работает VPN на HiveOS

Waiting interface to come up

Начните с логов, чтобы понять какая именно ошибка вызывает эту проблему.
Команды для получения логов:
systemctl status openvpn@client
journalctl -u openvpn@client -e —no-pager -n 100

Как узнать ip адрес воркера hive os

Самое простое — зайти в воркера и прокрутить страницу ниже видеокарт. Там будет указан Remote IP — это и есть внешний IP.
Альтернативный вариант — вы можете проверить ваш внешний айпи адрес hive через консоль Hive Shell:
Выполните одну из команд:
curl 2ip.ru
wget -qO- eth0.me
wget -qO- ipinfo.io/ip
wget -qO- ipecho.net/plain
wget -qO- icanhazip.com
wget -qO- ipecho.net
wget -qO- ident.me

Repository update failed в HiveOS

Иногда встречается на HiveOS. Полный текст ошибки:

Some index files failed to download. They have been ignored, or old ones used instead.
Repository update failed
------------------------------------------------------
> Restarting autofan and watchdog
> Starting miners
Miner screen is already running
Run miner or screen -r to resume screen
Upgrade failed

Решение:

Выполнить команду apt update && selfupgrade -f
Если не сработала и она, то 99.9%, что разработчики HiveOS уже знают об этой проблеме и решают ее. Попробуйте выполнить обновление через некоторое время.

Rave os не запускается. Boot aborted Rave os

Перепроверьте все настройки ПК и БИОСа материнской платы:
— Установите загрузочное устройство HDD/SSD/M2/USB в зависимости от носителя с ОС.
— Включите 4G decoding.
— Установите поддержку PCIe на Auto.
— Включите встроенную графику.
— Установите предпочтительный режим загрузки Legacy mode.
— Отключите виртуализацию.

Если после данных настроек не определяется часть карт, то выполните следующие настройки в BIOS (после каждого пункта требуется полная перезагрузка):

— Отключите 4G decoding
— Перезагрузка
— Отключите CSM
— Перезагрузка
— Включите 4G decoding, установите PCI-E Gen2/3, а при отсутствии Gen2/3, можно выбрать Gen1

Failed to allocate memory Raveos

Эта же ошибка может называться как:
failed to allocate initramfs memory bailing out, failed to load idlinux c.32
или
failed to allocate memory for kernel boot parameter block
или
failed to allocate initramfs memory raveos bailing

Но решение у нее одно — вы должны правильно настроить БИОС материнской платы.

gpu_driver_fault, GPU #0 fault в RaveOS

gpu_driver_fault, GPU #0 fault в RaveOS

В большинстве случаев эта проблема решается уменьшением разгона (особенно по памяти) на конкретной видеокарте (на скрине это карта номер 0).
Если уменьшение разгона не помогает, то попробуйте обновить драйвера.
Если обновление драйверов не привело к решению проблемы, то попробуйте поменять райзер на этой карте на точно работающий.
Если и это не помогает, перепроверьте все кабельные соединения и мощность блока питания, хватает ли его для вашей конфигурации.

Gpu driver fault. All tasks have been stopped. Worker will be rebooted after 5 minutes в RaveOS

Gpu driver fault. All tasks have been stopped. Worker will be rebooted after 5 minutes

Что приводит к появлению этой ошибки? Вероятно, вы переразогнали видеокарту (часто сильно гонят по памяти), сбавьте разгон. На скрине видно, что проблему дает именно GPU под номером 1 — начните с нее.
Вторая частая причина — нехватка питания БП на систему с видеокартами. Учтите, что сама система потребляет не менее 100 вт, каждый райзер еще закладывайте 50 вт. БП должно хватать с запасом в 20%.

Miner restarted after error RaveOS

Смотрите логи майнера, там будет указана конкретная ошибка, которая приводит к miner restarted. После этого найдите ее на этой странице и исправьте. Проблема уйдет.

Miner restart limit reached. Worker rebooting by flag auto в RaveOS

Аналогично предыдущему пункту — смотрите логи майнера, там будет указана конкретная ошибка, которая приводит к рестарту воркера. Пофиксите ту ошибку — уйдет и эта проблема.

Miner cannot be started, ОС RaveOS

Непосредственно перед этой ошибкой обычно пишется еще другая, которая и вызывает эту проблему. Но если ничего нет, то:

Поставьте майнер на паузу, перезагрузите риг и в консоли выполните команды clear-miners clear-logs и fix-fs. Запустите майнинг.
Если ошибка не ушла, перепишите образ RaveOS.

Overclock can’t be applied в RaveOS

Эта ошибка означает, что значения разгона между собой конфликтуют или выходят за пределы допустимых. Перепроверьте их. Скиньте разгон на стоковый и попробуйте еще раз.
В редких случаях причиной этой ошибки также становится райзер.

Error installing hive miners

Можно попробовать обойтись малой кровью и вбить в HiveOS команду:
hive-replace -y —stable
Система по новой накатит стабильную версию HiveOS.

Если ошибка не уйдет — физически перезапишите образ. Если у вас флешка, то скорее всего она умерла. Купите SSD.

Warning: Nvidia settings applied with errors

Переразгон. Снизьте значения частот ядра и памяти. После этого перезагрузите риг.

Nvtool error или Danger: nvtool error

Скорее всего при установке драйвера появилась проблема с модулем nvtool
Попробуйте переустановить драйвер Nvidia командой через Hive shell:
nvidia-driver-update версия_драйвера —force
Или попробуйте обновить систему полностью командой из Hive shell:
hive-replace -y —stable

nvtool error

Перестал отображаться кулер видеокарты HiveOS

0% скорости вращения кулера.
Это может произойти по нескольким причинам:

кулер действительно не крутится
датчик оборотов отключен или сломан
видеокарта слишком агрессивно работает (высокий разгон)
неисправен райзер или одно из его частей

ERROR: parsing JSON failed

Необходимо выполнить на риге локально (с клавиатурой и монитором) следующую команду:
net-test

Данная команда покажет ваше текущее состояние подключения к разным зеркалам API серверов HiveOS.
Посмотрите, к какому API у вас наименьшая задержка (ping), и когда воркер снова появится в панели, измените стандартное зеркало на то, что ближе к вам.
После смены зеркала, в обязательном порядке перезагрузите ваш воркер.
Изменить сервер API вы можете командой nano /hive-config/rig.conf
После смены нажмите ctrl + o и ентер для того чтобы сохранить файл.
После этого выйдите в консоль командой ctrl + x, f10 и выполните команду hello

NVML: can’t get fan speed for GPU #5, error code 999 hive os

Проблема с скоростью кулеров на GPU 5
0% скорости вращения кулера / ошибки в целом
Это может произойти по нескольким причинам:
— кулер действительно не крутится
— датчик оборотов отключен или сломан
— видеокарта слишком агрессивно работает (высокий разгон)
Начните с визуальной проверки карты и ее кулера.

Can’t get power for GPU #2

Как правило эта ошибка встречается рядом вместе с другими:
Attribute ‘GPUGraphicsClockOffset’ was already set to 0
Attribute ‘GPUMemoryTransferRateOffset’ was already set to 2200
Attribute ‘GPUFanControlState’ (hive1660s_ETH:0[gpu:2]) assigned value
0.

20211029 12:40:50 WARN: NVML: can’t get fan speed for GPU #2, error code 999
20211029 12:40:50 WARN: NVML: can’t get power for GPU #2, error code 999
20211029 12:40:50 WARN: NVML: can’t get mem/core clock for GPU #2, error code 999

Решение:

Проверьте корректность установки драйвера на видеокарте.
Убедитесь что нет проблем с драйвером, если все в порядке, то попробуйте другой параметр разгона. Например уменьшить разгон по памяти.

GPU1 search error: unspecified launch failure

Уменьшите разгон и проверьте контакты райзера

Warning: Autofan: unable to set fan speed, rebooting

Найдите логи майнера, посмотрите какие ошибки майнер пишет в логах. Например:

kernel: [12112.410046][ T7358] NVRM: GPU at PCI:0000:0c:00: GPU-236e3bef-2e03-6cdb-0518-7ac01eb8736d
kernel: [12112.410049][ T7358] NVRM: Xid (PCI:0000:0c:00): 62, pid=7317, 0000(0000) 00000000 00000000
kernel: [12112.433831][ T7358] NVRM: Xid (PCI:0000:0c:00): 45, pid=7317, Ch 00000010
CRON[21094]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)

Исходя из логов, мы видим что есть проблема с видеокартой на слоте PCIE 0c:00 (под номером Gpu пишется номер PCIE слота) с ошибками 45 и 62
Коды ошибок (других, которые также могут быть там) и что с ними делать:

• 13, 43, 45: ошибки памяти, снизить MEM
• 8, 31, 32, 61, 62: снизить CORE, возможно и MEM
• 79: снизить CORE, проверить райзер

Ошибка Kernel-Power код 41

Проверьте все провода (от БП до карт, от БП до райзеров), возможно где-то идёт оплавление. Если визуальный осмотр показал, что все ок, то ошибка программная и вам нужно переустановить Windows.

Danger: hive-replace -y —stable (failed, exitcode=137)

Очень редкая ошибка, которая вылезла в момент удаленного обновления образа HiveOS. Она не встречается в тематических майнинг группах и сайтах. Не поверите что произошло.
На балконе, где стоял риг, поселилась семья голубей. Они засрали риг, в прямом смысле, из-за этого он постоянно уходил в оффлайн. После полной продувки материнской платы и видеокарт проблема решилась сама.

MALFUNCTION HIVEOS

Malfunction — неисправность. Причин и решений может быть несколько:

Вам следует переустановить видео драйвер;
Если драйвер не помог, тогда отключайте все GPU и поочередно вставляйте по 1 шт, и смотрите вызовет ли какая-то видеокарта подобную ошибку или нет. Если да, то возможно это райзер.
Неисправен носитель, на который записана Hive OS, запишите образ еще раз.

Не нашли своей ошибки? Помогите сделать мир майнинга лучше. Отправьте ее по этой форме и мы обновим наш гайд в самое ближайшее время.

Источник