-
#1
Приветствую Ребята.
Появилась проблема с асиком innosilicon T2T.
Стоял на минималках все прекрасно работало, но как только запустил на максимальных и он тупо перестал работать. Крутится как на картинке и все. Больше не какой информации. Что можете порекомендовать? Сразу в сервис?
-
CFD96548-A887-4D56-B2D2-2E853B76F965.jpeg
133,5 КБ · Просмотры: 176
-
066F59A8-6DCD-4C79-9CD8-B00178FFD165.jpeg
173,9 КБ · Просмотры: 163
-
CF5DAE21-2563-4240-B541-6362B894196A.jpeg
174 КБ · Просмотры: 123
-
AC60A3C0-EDD4-4A76-8650-4749793C59A7.jpeg
158,7 КБ · Просмотры: 115
-
52DF68DB-BA1F-4209-BAAC-AC18CE46FDBE.jpeg
148,2 КБ · Просмотры: 160
-
#2
До заводских настроек сбрось, для начала.
-
#3
До заводских настроек сбрось, для начала.
Делал
-
#4
Логи с него можно снять?
Выложи, почитаем, может подскажем что, а то по фоткам ТАКОЕ сейчас наговорят….
-
#5
Innosilicon RUSSIA
Сообщество владельцев асик майнеров компании innosilicon в РФ. Обсуждение работы и решение проблем.
t.me
Там тебе помогут
-
#6
Приветствую Ребята.
Появилась проблема с асиком innosilicon T2T.
Стоял на минималках все прекрасно работало, но как только запустил на максимальных и он тупо перестал работать. Крутится как на картинке и все. Больше не какой информации. Что можете порекомендовать? Сразу в сервис?
Если есть такой же блок питания- перекинь. Была такая же проблема. БП работает, но не так, как надо. Пришлось менять.
-
#7
Логи с него можно снять?
Выложи, почитаем, может подскажем что, а то по фоткам ТАКОЕ сейчас наговорят….
Нет, логи снять не могу, только могу запустить мтест.
-
#8
Нет, логи снять не могу, только могу запустить мтест.
Проверяй БП. Контрольная плата хэш-платы видит, а запустить не может.
Там вверху ссылку дали на группу в телеге, спроси ещё там.
Проблема с асиком innosilicon t2t
Приветствую Ребята. Появилась проблема с асиком innosilicon T2T. Стоял на минималках все прекрасно работало, но как только запустил на максимальных и он тупо перестал работать. Крутится как на картинке и все. Больше не какой информации. Что можете порекомендовать? Сразу в сервис?
miningclub.info
проверь шины питания до хэш-плат, нет ли там под болтами окислов, на БП, шлейфы поперетыкай.
Вольтметром проверь просадку напряжения на шинах, при включении.
-
#9
Проверяй БП. Контрольная плата хэш-платы видит, а запустить не может.
Там вверху ссылку дали на группу в телеге, спроси ещё там.
Проблема с асиком innosilicon t2t
Приветствую Ребята. Появилась проблема с асиком innosilicon T2T. Стоял на минималках все прекрасно работало, но как только запустил на максимальных и он тупо перестал работать. Крутится как на картинке и все. Больше не какой информации. Что можете порекомендовать? Сразу в сервис?
miningclub.infoпроверь шины питания до хэш-плат, нет ли там под болтами окислов, на БП, шлейфы поперетыкай.
Вольтметром проверь просадку напряжения на шинах, при включении.
Такая же проблема,стоял на фактори,переключил на фактори +,и теперь бесконечно грузит
-
#10
Приветствую Ребята.
Появилась проблема с асиком innosilicon T2T.
Стоял на минималках все прекрасно работало, но как только запустил на максимальных и он тупо перестал работать. Крутится как на картинке и все. Больше не какой информации. Что можете порекомендовать? Сразу в сервис?
Такая же проблема. Появилась после проверки шлейфов.
в /error пишет
ERROR MESSAGE:
CONN_FAIL.chain(ff).chip().msg()
ErrNetwork 30 ошибка
-
#11
Здравствуйте Подскажите что может быть отказала 1 плата .
Вот логи
-
лог.txt
35,3 КБ · Просмотры: 56
-
#13
Enter main… [Jun 11 2020 23:35:04]
Oct 16 22:48:04 InnoMiner miner_test[8028]: conf parameter:-s 1
Oct 16 22:48:04 InnoMiner miner_test[8028]: args[0]:
Oct 16 22:48:04 InnoMiner miner_test[8028]: args[1]:-s
Oct 16 22:48:04 InnoMiner miner_test[8028]: args[2]:1
Oct 16 22:48:04 InnoMiner miner_test[8028]: opt = s
Oct 16 22:48:04 InnoMiner miner_test[8028]: optarg = 1
Oct 16 22:48:04 InnoMiner miner_test[8028]: optind = 3
Oct 16 22:48:04 InnoMiner miner_test[8028]: arg[optind] = 1
Oct 16 22:48:04 InnoMiner miner_test[8028]: Input test chain:0!
Oct 16 22:48:04 InnoMiner miner_test[8028]: nums_arg:3
Oct 16 22:48:04 InnoMiner miner_test[8028]: ******************************************
Oct 16 22:48:04 InnoMiner miner_test[8028]: Name : Ax SW Pre-Fin Test
Oct 16 22:48:04 InnoMiner miner_test[8028]: SVN Version : $Rev: 708 $
3:35:04
Oct 16 22:48:04 InnoMiner miner_test[8028]: Release Version: V2.15.8
Oct 16 22:48:04 InnoMiner miner_test[8028]: Version Func : Normal
Oct 16 22:48:04 InnoMiner miner_test[8028]: ******************************************
Oct 16 22:48:04 InnoMiner miner_test[8028]: max range: 0x2000.[soc_hub_hardware_init]
Oct 16 22:48:04 InnoMiner miner_test[8028]: total: 3 dev will mmap.
Oct 16 22:48:04 InnoMiner miner_test[8028]: mmap spihy:0x10000000 => vir:0xb6d3e000 size:0x10000 ok.
Oct 16 22:48:04 InnoMiner miner_test[8028]: mmap vid_vidhy:0x602f0000 => vir:0xb6d2e000 size:0x10000 ok.
Oct 16 22:48:04 InnoMiner miner_test[8028]: mmap apb_syshy:0x60000000 => vir:0xb6d1e000 size:0x10000 ok.
Oct 16 22:48:04 InnoMiner miner_test[8028]: total: 3 dev mmap done.
Oct 16 22:48:04 InnoMiner miner_test[8028]: GPIO value: 7, Ctrl board/vid type: 3
Oct 16 22:48:04 InnoMiner miner_test[8028]: final vid type: 3
Oct 16 22:48:04 InnoMiner miner_test[8028]: iic power ID: 1
Oct 16 22:48:05 InnoMiner miner_test[8028]:
Chain numbers: 3
Oct 16 22:48:05 InnoMiner miner_test[8028]: chain0: set spi speed 0
Oct 16 22:48:09 InnoMiner miner_test[8028]: chain0: set power on vid: 5
Oct 16 22:48:09 InnoMiner miner_test[8028]: chain0: set vid to 5
Oct 16 22:48:09 InnoMiner miner_test[8028]: chain0: expect iic voltage is 15.00V
Oct 16 22:48:17 InnoMiner miner_test[8028]: [ERROR]:Check receive buffer ready timeout!
Oct 16 22:48:17 InnoMiner miner_test[8028]: [ERROR]:chain0: ERROR — failed to recv spi data cmd:0x400
Oct 16 22:48:17 InnoMiner miner_test[8028]: [WARNING]:chain0: RESET failed 1 times
Oct 16 22:48:17 InnoMiner miner_test[8028]: [ERROR]:Check receive buffer ready timeout!
Oct 16 22:48:17 InnoMiner miner_test[8028]: [ERROR]:chain0: ERROR — failed to recv spi data cmd:0x400
Oct 16 22:48:17 InnoMiner miner_test[8028]: [ERROR]:chain0: RESET failed 2 times
Oct 16 22:48:17 InnoMiner miner_test[8028]: [ERROR]:chain0: cann’t find right chip type!!!
Oct 16 22:48:17 InnoMiner miner_test[8028]: chain0: Begin to Check …
Oct 16 22:48:17 InnoMiner miner_test[8028]: [ERROR]:Check receive buffer ready timeout!
Oct 16 22:48:17 InnoMiner miner_test[8028]: [ERROR]:chain0: ERROR — failed to recv spi data cmd:0x100
Oct 16 22:48:19 InnoMiner miner_test[8028]: [ERROR]:Check receive buffer ready timeout!
Oct 16 22:48:19 InnoMiner miner_test[8028]: [ERROR]:chain0: ERROR — failed to recv spi data cmd:0xb00
Oct 16 22:48:19 InnoMiner miner_test[8028]: [ERROR]:Check receive buffer ready timeout!
Oct 16 22:48:19 InnoMiner miner_test[8028]: [ERROR]:chain0: ERROR — failed to recv spi data cmd:0xa01
Oct 16 22:48:19 InnoMiner miner_test[8028]: [WARNING]:0A01 command Error!
Oct 16 22:48:20 InnoMiner miner_test[8028]: [ERROR]:Check receive buffer ready timeout!
Oct 16 22:48:20 InnoMiner miner_test[8028]: [ERROR]:chain0: ERROR — failed to recv spi data cmd:0x900
Oct 16 22:48:20 InnoMiner miner_test[8028]: [ERROR]:Check receive buffer ready timeout!
Oct 16 22:48:20 InnoMiner miner_test[8028]: [ERROR]:chain0: ERROR — failed to recv spi data cmd:0xd00
Oct 16 22:48:20 InnoMiner miner_test[8028]: [ERROR]:Write t/v sensor Value Failed!
Oct 16 22:48:21 InnoMiner miner_test[8028]: [ERROR]:Check receive buffer ready timeout!
Oct 16 22:48:21 InnoMiner miner_test[8028]: [ERROR]:chain0: ERROR — failed to recv spi data cmd:0xa01
Oct 16 22:48:21 InnoMiner miner_test[8028]: [WARNING]:0A01 command Error!
Oct 16 22:48:21 InnoMiner miner_test[8028]: [ERROR]:Check receive buffer ready timeout!
Oct 16 22:48:21 InnoMiner miner_test[8028]: [ERROR]:chain0: ERROR — failed to recv spi data cmd:0xa01
Oct 16 22:48:21 InnoMiner miner_test[8028]: [WARNING]:0A01 command Error!
Oct 16 22:48:21 InnoMiner miner_test[8028]: [ERROR]:Check receive buffer ready timeout!
Oct 16 22:48:21 InnoMiner miner_test[8028]: [ERROR]:chain0: ERROR — failed to recv spi data cmd:0xa01
Oct 16 22:48:21 InnoMiner miner_test[8028]: [WARNING]:0A01 command Error!
Oct 16 22:48:22 InnoMiner miner_test[8028]: [ERROR]:Check receive buffer ready timeout!
Oct 16 22:48:22 InnoMiner miner_test[8028]: [ERROR]:chain0: ERROR — failed to recv spi data cmd:0xa01
Oct 16 22:48:22 InnoMiner miner_test[8028]: [WARNING]:0A01 command Error!
Oct 16 22:48:22 InnoMiner miner_test[8028]: [ERROR]:Check receive buffer ready timeout!
Oct 16 22:48:22 InnoMiner miner_test[8028]: [ERROR]:chain0: ERROR — failed to recv spi data cmd:0xa01
Oct 16 22:48:22 InnoMiner miner_test[8028]: [WARNING]:0A01 command Error!
Oct 16 22:48:23 InnoMiner miner_test[8028]: Miner: iic power back current: 195
Oct 16 22:48:23 InnoMiner miner_test[8028]: Miner: iic power back vlotage: 1
Oct 16 22:48:23 InnoMiner miner_test[8028]: Miner: iic power: 0.0W
Oct 16 22:48:23 InnoMiner miner_test[8028]: chain0 power off
Oct 16 22:48:27 InnoMiner miner_test[8028]: ———- Error ID description ———-
Oct 16 22:48:27 InnoMiner miner_test[8028]: E0: Cannot find chip type, means the chain broken
Oct 16 22:48:27 InnoMiner miner_test[8028]: E1: Chip good cores < 20%
Oct 16 22:48:27 InnoMiner miner_test[8028]: E2: Board total good cores < 80%
Oct 16 22:48:27 InnoMiner miner_test[8028]: E3: Chip soft bist job results are all wrong
Oct 16 22:48:27 InnoMiner miner_test[8028]: E4: Board PLL unlock first chip number
Oct 16 22:48:27 InnoMiner miner_test[8028]: E5: Chip Temperature = -9999 or 9999
Oct 16 22:48:27 InnoMiner miner_test[8028]: E6: Chip Voltage exceed -10% ~ +10%
Oct 16 22:48:27 InnoMiner miner_test[8028]: E7: PLL Configure Error
Oct 16 22:48:27 InnoMiner miner_test[8028]: E8: Board soft bist job results total error > 10% (T1 : > 20%)
Oct 16 22:48:27 InnoMiner miner_test[8028]: E9: Board total chip num is wrong
Oct 16 22:48:27 InnoMiner miner_test[8028]: E10: Chip command return fail
Oct 16 22:48:27 InnoMiner miner_test[8028]: E11: Cannot find correct freq or voltage(after fin)
Oct 16 22:48:27 InnoMiner miner_test[8028]: E12: Chip command crc return error
Oct 16 22:48:27 InnoMiner miner_test[8028]: E13: chips voltage wrong after pll
Oct 16 22:48:27 InnoMiner miner_test[8028]: E14: Core Bist error
Oct 16 22:48:27 InnoMiner miner_test[8028]: E15: Write cache error
Oct 16 22:48:27 InnoMiner miner_test[8028]: E16: High speed DDR Training error
t 16 22:48:27 InnoMiner miner_test[8028]: E17: Dag Preparation timeout
Oct 16 22:48:27 InnoMiner miner_test[8028]: E18: Power Board error
Oct 16 22:48:27 InnoMiner miner_test[8028]: E19: Low speed DDR Training error
Oct 16 22:48:27 InnoMiner miner_test[8028]: ================ Chain0 Result ================
Oct 16 22:48:27 InnoMiner miner_test[8028]: [34B blob data]
Oct 16 22:48:27 InnoMiner miner_test[8028]: [31B blob data]
Oct 16 22:48:27 InnoMiner miner_test[8028]: ——————————————
Oct 16 22:48:27 InnoMiner miner_test[8028]: Chain0 Result Summary
Oct 16 22:48:27 InnoMiner miner_test[8028]: ——————————————
Oct 16 22:48:27 InnoMiner miner_test[8028]:
Oct 16 22:48:27 InnoMiner miner_test[8028]:
Oct 16 22:48:27 InnoMiner miner_test[8028]: Test Failed!
Oct 16 22:48:27 InnoMiner miner_test[8028]:
Oct 16 22:48:27 InnoMiner miner_test[8028]:
Oct 16 22:48:27 InnoMiner miner_test[8028]:
Oct 16 22:48:27 InnoMiner miner_test[8028]: ERROR type:
Oct 16 22:48:27 InnoMiner miner_test[8028]: E0: 1
Oct 16 22:48:27 InnoMiner miner_test[8028]:
==========================================
Oct 16 22:48:27 InnoMiner miner_test[8028]: ———TEST OVER!!!———-
Подскажите пожалуйста в чем дело))
как я понял Errorr type E0
Cannot find chip type, means the chain broken
Не удается найти тип чипа, значит, цепь оборвалась (гугл переводчик)
плата сгорела?
-
#14
Такая же проблема. Появилась после проверки шлейфов.
в /error пишет
ERROR MESSAGE:
CONN_FAIL.chain(ff).chip().msg()ErrNetwork 30 ошибка
Ошибка 30 это невозможно подключиться к пулу, поменяй настройки пула должно заработать.
-
#15
Приветствую Ребята.
Появилась проблема с асиком innosilicon T2T.
Стоял на минималках все прекрасно работало, но как только запустил на максимальных и он тупо перестал работать. Крутится как на картинке и все. Больше не какой информации. Что можете порекомендовать? Сразу в сервис?
День добрый, удалось решить проблемму? В чем дело оказалосью Только что столкнулся с такой же. Работал на factory и все было ок, поставил performance и все зависло. Сбрасывал на заводские — не помогло. Пулы прописаны верно. Возврат обратно на factory уже ни к чему не приводит.
-
#16
Добрый день. При ремонте хеш-платы T2t заменили три чипа — 1,2 и 31. После замены выдаёт ERROR 34b blob data. Что это может быть? И как можно вылечить? Есть подозрение, что это ошибка прошивки и один из сипов ругается, что объём данных слишком большой… Кто-нибудь может что-то подсказать
Содержание
- ERROR — failed to recv spi data DRAGONMINT T1 about cpuminer HOT 2 CLOSED
- Comments (2)
- Related Issues (20)
- Recommend Projects
- React
- Vue.js
- Typescript
- TensorFlow
- Django
- Laravel
- Recommend Topics
- javascript
- server
- Machine learning
- Visualization
- Recommend Org
- Microsoft
- Topic: Innosilicon A4+ setup tutorial (Read 6587 times)
- t17 ошибка в логах
- Demiansikora
- Valwhatsminer
- Zoomy
ERROR — failed to recv spi data DRAGONMINT T1 about cpuminer HOT 2 CLOSED
hello friend from 2021. I hope you solved this problem, I have the same problem with these miners, if you find a solution please help me.
asddas80 commented on January 16, 2023
same problem . I don`t konw wath to do
- not support «X-Mining-Hashrate»?
- does not connect to Bitcoin via RPC HOT 1
- Google Chrome warns http://yyz.us/bitcoin/ is a harmful website. HOT 1
- stratum+tcp:// Syntax Error HOT 2
- What do I do with this to use it?
- Build error on mac error: possibly undefined macro: AC_MSG_ERROR
- proxy authentication
- Proxy Authentication
- Avalon6 speed increasing above both avalon4-freq-max and avalon4-freq
- add new pool
- confirm custom transaction
- error: possibly undefined macro: AC_MSG_ERROR
- I try to mine litecoin on wallet
- X13 Not compatible with BitcoinDiamond X13BCD
- Ubuntu 16.04, cgminer 4.11.0, not find pthread library
- hi cgminer
- Is support scrypt hassing algorithem
- question about project license HOT 2
- windows iot
Recommend Projects
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
Recommend Topics
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
server
A server is a program made to process requests and deliver data to clients.
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Recommend Org
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Источник
Topic: Innosilicon A4+ setup tutorial (Read 6587 times)
To telnet, you need to type in terminal:
telnet «miner-ip» 8100
example:
telnet 192.168.1.10 8100
username: root
password: t1t2t3a5
then type:
vi /innocnfg/www/conf/miner.conf
There you can change fanspeed with vi editor.
— press «i» to enable edit mode
— change speed
— presss «esc» then «:wq» to save the changes
Hello need help , command list how can open kernel log, one board starts work and after 5 minutes i see hashrate but on pool it didn’t mining, in miner interface everything looks great. thank.
[email protected]/tmp:
/tmp/log/innominer.log
-sh: /tmp/log/innominer.log: Permission denied
these are the biggest issues, i have.
In the miner configuration selection, what are your frequency setting at, 1100, 1152 or 1044?
if the hashrates are not at 157 -170 all the time then what does it mean, issues are at somewhere, i cant see to narrow it to make them all run at the same rate.
if a card get the same accepted/rejected shares like one maybe two boards having all the shares and the other do not have any, then what does it mean, issues are at somewhere, i cant see to narrow it to make them all run at the same rate to producing shares.
Does anyone have a solution?
Hello all. Long time user but have never posted.
I recently bought 6 A4+ from alibaba. I knew it was a risk but I got them at a good price. I got videos of the miners hashing at 630+ for each one before shipping. I am using 220 volt power supplies each being 1000 watts or more. The first thing I did was update the firmware on each machine. I immediately noticed that hash boards were missing on the overview page of some of the miners. I did not check the hash boards before updating firmware. Some miners had hash boards present that eventually went away. I went from 4 hash boards initially being down to now 8. I’ve tried using previous bin files to change firmware on miners which brought back 2 hash boards. Now I am down 6 boards. Two of the miners only accept swu files so I cannot go backwards on the firmware on those miners. Does anyone have a previous swu firmware file to try?
I am hoping to get advice from you guys for a process to go through to diagnose these hash boards to see if they are actually dead or if they can be revived. My supplier has video proof that they worked before shipping and is offering to send me more hash boards for free. I want to keep this guy’s trust though so I want to try everything I can before taking him up on this offer. Any help would be appreciated.
I have a very similar problem but with a A4+ LTC master. How did u flash the bin Firmware? My A4+ has an alternative control board that doesn´t have a TF card slot and the web interface only accept SWU files.
If you get the firmware please let me know, i been looking around for a while now
I have 2 of the LTC masters I suppose. I ordered 6 A4+ and 4 of them are the normal web interface and use .bin firmware updates but two of them have very different web interfaces and only accept .swu files for firmware updates. The web interface for the LTC master is cleaner and you can tell it is more modern but I cannot find older firmwares to try to get the hash boards to be recognized. I may end up connecting the hashboards and fans from the LTC master into one of my A4+ control boards. My supplier is sending me 6 hashboards to replace the ones that are not working. I was able to get two of them to come back online by flashing the A4+ to an older firmware.
On one of the LTC masters, it shows 4 hash boards and only one is hashing. The other 3 say «alive» next to them but have no hashrate. I don’t know what to do with that but will try connecting them to an A4+ with an older firmware to see what happens.
Let me know if you get any solution. In case you want to sell the control board of your inno miner i would like to get one, since mine came with an lternative control board, no TF card slot, so i cannot flash an older firmware.
Been looking for some one to take a deep look at the logs but can´t find anyone willing to do so, and i can´t figure it out by myself. The fan speed always shows at 10% and the vendor insist that the problem is a broken fan, but both are working just fine so i have no idea what to do.
Источник
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
Новичок
[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
кто знает что происходит со вторым чайником
Zoomy
Свой человек
[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
кто знает что происходит со вторым чайником
Источник
newbie
Activity: 1
Merit: 0
hello friend from 2021. I hope you solved this problem, I have the same problem with these miners, if you find a solution please help me.
newbie
Activity: 3
Merit: 0
do you have it set on low efficiency setting or high turbo or balanced setting
try balanced setting if you have yet to try it.
yeah sucks I have tried that too looks like I am 2 boards down… What about a new controller ? or is it the hashboards not doing properly as in communicating with the controller?
legendary
Activity: 3122
Merit: 2174
Evil beware: We have waffles!
if I can’t remedize it will I have ti buy new hashboards?
Considering that Halong Mining, makers of the T1, are out of business good luck with that…
legendary
Activity: 3640
Merit: 5167
hi, I am getting this error now also tried all your steps… is this looking like a new hashboard or boards for me in this case I assume ?
if I can’t remedize it will I have ti buy new hashboards?
do you have it set on low efficiency setting or high turbo or balanced setting
try balanced setting if you have yet to try it.
newbie
Activity: 3
Merit: 0
Jun 18 15:45:21 dragonMint cgminer[1339]: vid type detected: 0
Jun 18 15:45:21 dragonMint cgminer[1339]: fan speed set to 100
Jun 18 15:45:22 dragonMint cgminer[1339]: T1: checking T1 chain
Jun 18 15:45:22 dragonMint cgminer[1339]: chain0: spi speed set to 390K
Jun 18 15:45:22 dragonMint cgminer[1339]: 0: detected 63 chips
Jun 18 15:45:22 dragonMint cgminer[1339]: collect core success
Jun 18 15:45:22 dragonMint cgminer[1339]: chain1: spi speed set to 390K
Jun 18 15:45:22 dragonMint cgminer[1339]: ERROR - failed to recv spi data
Jun 18 15:45:22 dragonMint cgminer[1339]: failed to reset chain 1!
Jun 18 15:45:22 dragonMint cgminer[1339]: chain2: spi speed set to 390K
Jun 18 15:45:22 dragonMint cgminer[1339]: ERROR - failed to recv spi data
Jun 18 15:45:22 dragonMint cgminer[1339]: failed to reset chain 2!
Anyone have any ideas on this issue? The log comes from a T1 with only the left board hashing.
It’s exactly as you’ve said — the chain isn’t working. When the controller can no longer talk to the mining board, it has communication errors. The driver tries to reset the comms channel and then tries to re-init the board. If it doesn’t succeed it shuts down and tries restarting cgminer. If it can’t communicate with the board during the extensive init sequence on driver startup, the board will never come up.
hi, I am getting this error now also tried all your steps… is this looking like a new hashboard or boards for me in this case I assume ?
if I can’t remedize it will I have ti buy new hashboards?
newbie
Activity: 14
Merit: 7
Oh no. Sorry to hear it didn’t work man.
I swapped the controller cable from a working T1 and the board is still dead. I’m starting to think it might just be a bad board.
Unfortunately I’ll probably just have to send it off for warranty work.
full member
Activity: 538
Merit: 172
tim-bc, when you staggered turning on the miners one at a time was it only on that circuit/pdu? I have other miners currently running on other circuits and I’m wondering if I need to pull everything and then power them on again one by one.
It seemed to help the first time that all of the dragonmint were restarted, I only lost 1 board. But, after the last time it happened I have done all the steps and I still have 6 boards lost 
newbie
Activity: 14
Merit: 7
I changed the performance back to «balanced» cause it’s obvious it doesn’t like the overclock, and I’m still getting the dead board unfortunately. I thought it may be a bad PSU so I swapped it out with a PSU (myRig) from one of my working T1’s and same thing, dead board. Updated to the latest firmware and same result.
Tomorrow I’m going to try swapping the cable from the controller to the board and try to rule that one out.
legendary
Activity: 3682
Merit: 1441
Ruu o/
Hey guys wondering if anyone has figured out a possible solution? I tried switching my T1’s to performance mode and I’m getting the «Error — failed to recv spi data» on two of my machines. On one all hash boards are down and on the other one board is down.
In performance mode you’re overclocking them. There is no guarantee that you’ll have enough power at that level, nor that the chains will be stable. You need extra power and aggressive cooling to make it likely to work, but even then it’s not guaranteed.
newbie
Activity: 14
Merit: 7
Hey guys wondering if anyone has figured out a possible solution? I tried switching my T1’s to performance mode and I’m getting the «Error — failed to recv spi data» on two of my machines. On one all hash boards are down and on the other one board is down.
tim-bc, when you staggered turning on the miners one at a time was it only on that circuit/pdu? I have other miners currently running on other circuits and I’m wondering if I need to pull everything and then power them on again one by one.
full member
Activity: 538
Merit: 172
Hey. Did you ever get all boards up and running again tim-bc?
I got most of the dead boards (10 out of 11) back again. But in my case, it seems like the issue was mostly due to them all booting at the exact same time.
newbie
Activity: 5
Merit: 0
Hey. Did you ever get all boards up and running again tim-bc?
I have the same error in the miner logs, T1 was delivered to me from Halong with one PCB inop so sent it off to MyRig for repair.
They returned it and it was still broken.
It lights up on startup, then the chain fails to come online, just as you mentioned. Tried changing the cable as philipma1957 mentioned, same board with the problem.
Will just have to send it off to MyRig again I guess — shame though at £20/time from the UK, for a miner that has never functioned since delivery from Halong!
Thanks.
full member
Activity: 538
Merit: 172
So I found that the issue with upgrading the firmware was with the network (I was already trying to apply from local), I could move the miners to another network and upgrade them just fine. But when doing so I noticed some boards were OK even without an upgrade. This made me read back to what you said about inrush of current.
I realized that instead of trying to turn all of the T1 back up at once by pdu/breaker, I should try staggering them instead, turning one on every 15-30 seconds. This was very effective and almost all of the miners are working well again. Thanks again for your help Con!
legendary
Activity: 3682
Merit: 1441
Ruu o/
full member
Activity: 538
Merit: 172
Also make sure you’re on the latest firmware
It does seem to help, I upgraded one and it went back from 1 board to 2. The only problem is that most of the miners get stuck around 30% when upgrading. https://i.stack.imgur.com/Tg9de.png Any idea why?
legendary
Activity: 3682
Merit: 1441
Ruu o/
Thank you for the extensive reply, Con. My only question is why would this issue start to occur after a reboot?
In my case I was watching about a dozen of the T1, all of them 16 TH for a couple weeks, until they were all rebooted (power off for 5-10 mins, then back on). After this, 4 miners came back up with only 1 board and there are 4 more that only have 2. Tried rebooting them all but exact same results.
I made sure to check pool stats to confirm the hashrate drop. Any idea why those faulty boards were still able to keep hashing until the miners were rebooted?
Inrush of current, thermal changes, hot vs cold, who knows. The 10nm chips are very fussy. Might be worth powering them down to let them cool and then start again. Also make sure you’re on the latest firmware; some earlier ones weren’t as reliable at starting them. They’re a royal pain in the arse to start reliably…
full member
Activity: 538
Merit: 172
Thank you for the extensive reply, Con. My only question is why would this issue start to occur after a reboot?
In my case I was watching about a dozen of the T1, all of them 16 TH for a couple weeks, until they were all rebooted (power off for 5-10 mins, then back on). After this, 4 miners came back up with only 1 board and there are 4 more that only have 2. Tried rebooting them all but exact same results.
I made sure to check pool stats to confirm the hashrate drop. Any idea why those faulty boards were still able to keep hashing until the miners were rebooted?
legendary
Activity: 3640
Merit: 5167
check cable connection from hash board to controller
you could swap a cable from a good board to see if the problem flows the cable or stays with the dead board.
legendary
Activity: 3682
Merit: 1441
Ruu o/
It’s exactly as you’ve said — the chain isn’t working. When the controller can no longer talk to the mining board, it has communication errors. The driver tries to reset the comms channel and then tries to re-init the board. If it doesn’t succeed it shuts down and tries restarting cgminer. If it can’t communicate with the board during the extensive init sequence on driver startup, the board will never come up.
full member
Activity: 538
Merit: 172
Jun 18 15:45:21 dragonMint cgminer[1339]: vid type detected: 0
Jun 18 15:45:21 dragonMint cgminer[1339]: fan speed set to 100
Jun 18 15:45:22 dragonMint cgminer[1339]: T1: checking T1 chain
Jun 18 15:45:22 dragonMint cgminer[1339]: chain0: spi speed set to 390K
Jun 18 15:45:22 dragonMint cgminer[1339]: 0: detected 63 chips
Jun 18 15:45:22 dragonMint cgminer[1339]: collect core success
Jun 18 15:45:22 dragonMint cgminer[1339]: chain1: spi speed set to 390K
Jun 18 15:45:22 dragonMint cgminer[1339]: ERROR - failed to recv spi data
Jun 18 15:45:22 dragonMint cgminer[1339]: failed to reset chain 1!
Jun 18 15:45:22 dragonMint cgminer[1339]: chain2: spi speed set to 390K
Jun 18 15:45:22 dragonMint cgminer[1339]: ERROR - failed to recv spi data
Jun 18 15:45:22 dragonMint cgminer[1339]: failed to reset chain 2!
Anyone have any ideas on this issue? The log comes from a T1 with only the left board hashing.
Any one know hot to solve the next dragonmint t1 failed:
the hash board was working well but today don’t work again, I tested that change cables, PSU.. and dont do that the hashboard mine again
Apr 01 18:55:43 dragonMint cgminer[1332]: chain0: spi speed set to 390K
Apr 01 18:55:43 dragonMint cgminer[1332]: ERROR — failed to recv spi data
Apr 01 18:55:43 dragonMint cgminer[1332]: failed to reset chain 0!
Apr 01 18:55:43 dragonMint cgminer[1332]: platform re-init: chain_num(3), chip_num(63)
Apr 01 18:55:43 dragonMint cgminer[1332]: sys : platform[4] miner_type[1] chain_num[3] chip_num[63]
Apr 01 18:55:44 dragonMint dm-monitor[1269]: [INFO:2019-04-01 18:55:44.204] b9 pin:957,a10 pin:943
Apr 01 18:55:44 dragonMint dm-monitor[1269]: [INFO:2019-04-01 18:55:44.204] b9:0,a10:1,val:0x00000002
Apr 01 18:55:44 dragonMint dm-monitor[1269]: [INFO:2019-04-01 18:55:44.204] b9 pin:957,a10 pin:943
Apr 01 18:55:44 dragonMint dm-monitor[1269]: [INFO:2019-04-01 18:55:44.204] b9:0,a10:1,val:0x00000002
Apr 01 18:55:44 dragonMint dm-monitor[1269]: [INFO:2019-04-01 18:55:44.204] zl uart vid
Apr 01 18:55:44 dragonMint dm-monitor[1269]: [INFO:2019-04-01 18:55:44.204] zl uart vid
Apr 01 18:55:44 dragonMint cgminer[1332]: init 0 T1 chain fail
logs with just Prohashing specified:
Jun 25 12:28:23 dragonMint nginx[1298]: 78.90.68.197 — — [25/Jun/2018:12:28:23 +0000] «POST /api/summary HTTP/1.1» 200 28 «http://31.171.242.41:3119/» «Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36»
Jun 25 12:28:23 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:23.856] b9 pin:957,a10 pin:943
Jun 25 12:28:23 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:23.856] b9:1,a10:1,val:0x00000003
Jun 25 12:28:23 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:23.856] b9 pin:957,a10 pin:943
Jun 25 12:28:23 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:23.856] b9:1,a10:1,val:0x00000003
Jun 25 12:28:23 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:23.856] cow vid vid
Jun 25 12:28:23 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:23.856] cow vid vid
Jun 25 12:28:25 dragonMint nginx[1298]: 78.90.68.197 — — [25/Jun/2018:12:28:25 +0000] «POST /api/getHashRates HTTP/1.1» 200 237 «http://31.171.242.41:3119/» «Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36»
Jun 25 12:28:28 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:28.857] b9 pin:957,a10 pin:943
Jun 25 12:28:28 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:28.857] b9:1,a10:1,val:0x00000003
Jun 25 12:28:28 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:28.857] b9 pin:957,a10 pin:943
Jun 25 12:28:28 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:28.857] b9:1,a10:1,val:0x00000003
Jun 25 12:28:28 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:28.857] cow vid vid
Jun 25 12:28:28 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:28.857] cow vid vid
Jun 25 12:28:33 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:33.857] b9 pin:957,a10 pin:943
Jun 25 12:28:33 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:33.857] b9:1,a10:1,val:0x00000003
Jun 25 12:28:33 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:33.857] b9 pin:957,a10 pin:943
Jun 25 12:28:33 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:33.857] b9:1,a10:1,val:0x00000003
Jun 25 12:28:33 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:33.858] cow vid vid
Jun 25 12:28:33 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:33.858] cow vid vid
Jun 25 12:28:34 dragonMint nginx[1298]: 78.90.68.197 — — [25/Jun/2018:12:28:34 +0000] «POST /api/summary HTTP/1.1» 200 28 «http://31.171.242.41:3119/» «Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36»
Jun 25 12:28:38 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:38.858] b9 pin:957,a10 pin:943
Jun 25 12:28:38 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:38.858] b9 pin:957,a10 pin:943
Jun 25 12:28:38 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:38.858] b9:1,a10:1,val:0x00000003
Jun 25 12:28:38 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:38.858] cow vid vid
Jun 25 12:28:38 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:38.858] b9:1,a10:1,val:0x00000003
Jun 25 12:28:38 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:38.858] cow vid vid
Jun 25 12:28:43 dragonMint cgminer[1446]: No servers were found that could be used to get work from.
Jun 25 12:28:43 dragonMint cgminer[1446]: Please check the details from the list below of the servers you have input
Jun 25 12:28:43 dragonMint cgminer[1446]: Most likely you have input the wrong URL, forgotten to add a port, or have not set up workers
Jun 25 12:28:43 dragonMint cgminer[1446]: [2018-06-25 12:27:43.413] Invalid config option —T1VID4: Value out of range
Jun 25 12:28:43 dragonMint cgminer[1446]: [2018-06-25 12:27:43.413] Invalid config option —T1VID5: Value out of range
Jun 25 12:28:43 dragonMint cgminer[1446]: [2018-06-25 12:27:43.414] Invalid config option —T1VID6: Value out of range
Jun 25 12:28:43 dragonMint cgminer[1446]: [2018-06-25 12:27:43.414] Invalid config option —T1VID7: Value out of range
Jun 25 12:28:43 dragonMint cgminer[1446]: [2018-06-25 12:27:43.414] Invalid config option —T1VID8: Value out of range
Jun 25 12:28:43 dragonMint cgminer[1446]: Pool: 0 URL: stratum+tcp://prohashing.com:3333 User: USERNAME Password: a=sha-256 n=327 w=1400 p=0.13
Jun 25 12:28:43 dragonMint cgminer[1446]: No servers could be used! Exiting.
Jun 25 12:28:43 dragonMint systemd[1]: cgminer.service: Service hold-off time over, scheduling restart.
Jun 25 12:28:43 dragonMint systemd[1]: cgminer.service: Scheduled restart job, restart counter is at 8.
Jun 25 12:28:43 dragonMint systemd[1]: Stopped Cgminer.
Jun 25 12:28:43 dragonMint systemd[1]: Starting Cgminer…
Jun 25 12:28:43 dragonMint systemd[1]: Started Cgminer.
Jun 25 12:28:43 dragonMint cgminer[1455]: [2018-06-25 12:28:43.663] Invalid config option —T1VID4: Value out of range
Jun 25 12:28:43 dragonMint cgminer[1455]: [2018-06-25 12:28:43.663] Invalid config option —T1VID5: Value out of range
Jun 25 12:28:43 dragonMint cgminer[1455]: [2018-06-25 12:28:43.663] Invalid config option —T1VID6: Value out of range
Jun 25 12:28:43 dragonMint cgminer[1455]: [2018-06-25 12:28:43.663] Invalid config option —T1VID7: Value out of range
Jun 25 12:28:43 dragonMint cgminer[1455]: [2018-06-25 12:28:43.663] Invalid config option —T1VID8: Value out of range
Jun 25 12:28:43 dragonMint cgminer[1455]: Started cgminer 4.10.0
Jun 25 12:28:43 dragonMint cgminer[1455]: Loaded configuration file /etc/cgminer.conf
Jun 25 12:28:43 dragonMint cgminer[1455]: Error in configuration file, partially loaded.
Jun 25 12:28:43 dragonMint cgminer[1455]: Probing for an alive pool
Jun 25 12:28:43 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:43.859] b9 pin:957,a10 pin:943
Jun 25 12:28:43 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:43.859] b9 pin:957,a10 pin:943
Jun 25 12:28:43 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:43.859] b9:1,a10:1,val:0x00000003
Jun 25 12:28:43 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:43.859] cow vid vid
Jun 25 12:28:43 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:43.859] b9:1,a10:1,val:0x00000003
Jun 25 12:28:43 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:43.859] cow vid vid
Jun 25 12:28:45 dragonMint nginx[1298]: 78.90.68.197 — — [25/Jun/2018:12:28:45 +0000] «POST /api/summary HTTP/1.1» 200 28 «http://31.171.242.41:3119/» «Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36»
Jun 25 12:28:48 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:48.859] b9 pin:957,a10 pin:943
Jun 25 12:28:48 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:48.859] b9:1,a10:1,val:0x00000003
Jun 25 12:28:48 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:48.859] b9 pin:957,a10 pin:943
Jun 25 12:28:48 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:48.859] b9:1,a10:1,val:0x00000003
Jun 25 12:28:48 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:48.859] cow vid vid
Jun 25 12:28:48 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:48.859] cow vid vid
Jun 25 12:28:53 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:53.860] b9 pin:957,a10 pin:943
Jun 25 12:28:53 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:53.860] b9:1,a10:1,val:0x00000003
Jun 25 12:28:53 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:53.860] b9 pin:957,a10 pin:943
Jun 25 12:28:53 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:53.860] b9:1,a10:1,val:0x00000003
Jun 25 12:28:53 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:53.860] cow vid vid
Jun 25 12:28:53 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:53.860] cow vid vid
Jun 25 12:28:55 dragonMint nginx[1298]: 78.90.68.197 — — [25/Jun/2018:12:28:55 +0000] «POST /api/getHashRates HTTP/1.1» 200 237 «http://31.171.242.41:3119/» «Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36»
Jun 25 12:28:56 dragonMint nginx[1298]: 78.90.68.197 — — [25/Jun/2018:12:28:56 +0000] «POST /api/summary HTTP/1.1» 200 28 «http://31.171.242.41:3119/» «Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36»
Jun 25 12:28:58 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:58.861] b9 pin:957,a10 pin:943
Jun 25 12:28:58 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:58.861] b9:1,a10:1,val:0x00000003
Jun 25 12:28:58 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:58.861] b9 pin:957,a10 pin:943
Jun 25 12:28:58 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:58.861] b9:1,a10:1,val:0x00000003
Jun 25 12:28:58 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:58.861] cow vid vid
Jun 25 12:28:58 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:28:58.861] cow vid vid
Jun 25 12:29:03 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:03.861] b9 pin:957,a10 pin:943
Jun 25 12:29:03 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:03.861] b9:1,a10:1,val:0x00000003
Jun 25 12:29:03 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:03.861] b9 pin:957,a10 pin:943
Jun 25 12:29:03 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:03.861] b9:1,a10:1,val:0x00000003
Jun 25 12:29:03 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:03.861] cow vid vid
Jun 25 12:29:03 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:03.861] cow vid vid
Jun 25 12:29:06 dragonMint nginx[1298]: 78.90.68.197 — — [25/Jun/2018:12:29:06 +0000] «POST /api/summary HTTP/1.1» 200 28 «http://31.171.242.41:3119/» «Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36»
Jun 25 12:29:08 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:08.862] b9 pin:957,a10 pin:943
Jun 25 12:29:08 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:08.862] b9 pin:957,a10 pin:943
Jun 25 12:29:08 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:08.862] b9:1,a10:1,val:0x00000003
Jun 25 12:29:08 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:08.862] cow vid vid
Jun 25 12:29:08 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:08.862] b9:1,a10:1,val:0x00000003
Jun 25 12:29:08 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:08.862] cow vid vid
Jun 25 12:29:13 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:13.863] b9 pin:957,a10 pin:943
Jun 25 12:29:13 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:13.863] b9:1,a10:1,val:0x00000003
Jun 25 12:29:13 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:13.863] b9 pin:957,a10 pin:943
Jun 25 12:29:13 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:13.863] b9:1,a10:1,val:0x00000003
Jun 25 12:29:13 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:13.863] cow vid vid
Jun 25 12:29:13 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:13.863] cow vid vid
Jun 25 12:29:17 dragonMint nginx[1298]: 78.90.68.197 — — [25/Jun/2018:12:29:17 +0000] «POST /api/summary HTTP/1.1» 200 28 «http://31.171.242.41:3119/» «Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36»
Jun 25 12:29:18 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:18.863] b9 pin:957,a10 pin:943
Jun 25 12:29:18 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:18.863] b9 pin:957,a10 pin:943
Jun 25 12:29:18 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:18.863] b9:1,a10:1,val:0x00000003
Jun 25 12:29:18 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:18.863] cow vid vid
Jun 25 12:29:18 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:18.863] b9:1,a10:1,val:0x00000003
Jun 25 12:29:18 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:18.863] cow vid vid
Jun 25 12:29:23 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:23.864] b9 pin:957,a10 pin:943
Jun 25 12:29:23 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:23.864] b9 pin:957,a10 pin:943
Jun 25 12:29:23 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:23.864] b9:1,a10:1,val:0x00000003
Jun 25 12:29:23 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:23.864] cow vid vid
Jun 25 12:29:23 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:23.864] b9:1,a10:1,val:0x00000003
Jun 25 12:29:23 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:23.864] cow vid vid
Jun 25 12:29:25 dragonMint nginx[1298]: 78.90.68.197 — — [25/Jun/2018:12:29:25 +0000] «POST /api/getHashRates HTTP/1.1» 200 237 «http://31.171.242.41:3119/» «Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36»
Jun 25 12:29:27 dragonMint nginx[1298]: 78.90.68.197 — — [25/Jun/2018:12:29:27 +0000] «POST /api/summary HTTP/1.1» 200 28 «http://31.171.242.41:3119/» «Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36»
Jun 25 12:29:28 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:28.864] b9 pin:957,a10 pin:943
Jun 25 12:29:28 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:28.865] b9:1,a10:1,val:0x00000003
Jun 25 12:29:28 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:28.864] b9 pin:957,a10 pin:943
Jun 25 12:29:28 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:28.865] b9:1,a10:1,val:0x00000003
Jun 25 12:29:28 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:28.865] cow vid vid
Jun 25 12:29:28 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:28.865] cow vid vid
Jun 25 12:29:33 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:33.865] b9 pin:957,a10 pin:943
Jun 25 12:29:33 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:33.865] b9 pin:957,a10 pin:943
Jun 25 12:29:33 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:33.865] b9:1,a10:1,val:0x00000003
Jun 25 12:29:33 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:33.865] cow vid vid
Jun 25 12:29:33 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:33.865] b9:1,a10:1,val:0x00000003
Jun 25 12:29:33 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:33.865] cow vid vid
Jun 25 12:29:38 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:38.866] b9 pin:957,a10 pin:943
Jun 25 12:29:38 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:38.866] b9:1,a10:1,val:0x00000003
Jun 25 12:29:38 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:38.866] b9 pin:957,a10 pin:943
Jun 25 12:29:38 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:38.866] b9:1,a10:1,val:0x00000003
Jun 25 12:29:38 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:38.866] cow vid vid
Jun 25 12:29:38 dragonMint dm-monitor[1272]: [INFO:2018-06-25 12:29:38.866] cow vid vid
Jun 25 12:29:43 dragonMint systemd-timesyncd[1267]: Network configuration changed, trying to establish connection.
Jun 25 12:29:43 dragonMint systemd-timesyncd[1267]: Synchronized to time server 77.85.205.151:123 (0.dragonmint.pool.ntp.org).
Jun 25 12:29:43 dragonMint cgminer[1455]: No servers were found that could be used to get work from.
Jun 25 12:29:43 dragonMint cgminer[1455]: Please check the details from the list below of the servers you have input
Jun 25 12:29:43 dragonMint cgminer[1455]: Most likely you have input the wrong URL, forgotten to add a port, or have not set up workers
Jun 25 12:29:43 dragonMint cgminer[1455]: [2018-06-25 12:28:43.663] Invalid config option —T1VID4: Value out of range
Jun 25 12:29:43 dragonMint cgminer[1455]: [2018-06-25 12:28:43.663] Invalid config option —T1VID5: Value out of range
Jun 25 12:29:43 dragonMint cgminer[1455]: [2018-06-25 12:28:43.663] Invalid config option —T1VID6: Value out of range
Jun 25 12:29:43 dragonMint cgminer[1455]: [2018-06-25 12:28:43.663] Invalid config option —T1VID7: Value out of range
Jun 25 12:29:43 dragonMint cgminer[1455]: [2018-06-25 12:28:43.663] Invalid config option —T1VID8: Value out of range
Jun 25 12:29:43 dragonMint cgminer[1455]: Pool: 0 URL: stratum+tcp://prohashing.com:3333 User: USERNAME Password: a=sha-256 n=327 w=1400 p=0.13
Jun 25 12:29:43 dragonMint cgminer[1455]: No servers could be used! Exiting.
Jun 25 12:29:43 dragonMint systemd[1]: cgminer.service: Service hold-off time over, scheduling restart.
Jun 25 12:29:43 dragonMint systemd[1]: cgminer.service: Scheduled restart job, restart counter is at 9.
Jun 25 12:29:43 dragonMint systemd[1]: Stopped Cgminer.
I just edited out my correct username for privacy reasons 
Код Расшифровка ошибки
0 ОК
21 1 или более хеш-плат не обнаружены
22 Аномальная связь по управлению питанием
23 Все хэш-платы не могут быть включены
24 Некоторые платы не включаются
25 Не удалось поднять частоту хэш-платы
26 Не удалось установить напряжение
27 Тест чипа BIST не пройден
28 Ненормальная связь платы хешрейта не может быть автоматически восстановлена во время работы
29 Ненормальная связь по питанию во время работы не может быть восстановлена автоматически
30 Подключение к майнинговому пулу прервано
31 Повреждение отдельных микросхем, что приводит к искусственно завышенной вычислительной мощности
32 Hashboard перегрелся
33 Невозможно прочитать температуру чипа
34 Неправильное подключение кабеля связи платы управления
35 Аномальный источник питания
36 Некоторые чипы не работают должным образом
37 Тип платы управления / версия прошивки / количество микросхем не совпадает
38 Наконец, у некоторых чипов низкая вычислительная мощность.
39 Аномальные параметры старения
40 Проверьте, совпадают ли направления переднего и заднего ветра, согласуются ли они с другими машинами, и если они не совпадают, измените направление вентилятора.
41 Измерьте температуру воздухозаборника горной машины. если она превышает 40 градусов, необходимо улучшить температурную обстановку в шахте.
42 Если определенная плата вычислительной мощности часто перегревается, проблемную плату вычислительной мощности можно заменить (ремонт головоломки).
43 Ошибка, не удается прочитать температуру чипа, не удается прочитать температуру чипа, номер платы вычислительной мощности»1.Проверьте, не ослаблены ли винты на обоих концах клеммы питания и подключения кабеля SPI
44 Замените источник питания
45 Замените плату управления
46 Замените проблемную плату вычислительной мощности (ремонт головоломки)
47 Ошибка включена, неверное подключение кабеля связи платы управления, неправильное подключение кабеля SPI платы управления, номер платы вычислительной мощности «1.Проверьте, соответствует ли способ (последовательность) подключения кабеля SPI платы вычислительной мощности другим машинам той же модели
48 Замените плату управления»
49 Ошибка, неправильный источник питания, неправильный источник питания,, «1.Обратите внимание, что если нет явных отклонений в вычислительной мощности всей машины (ни одна плата не упала), нет необходимости иметь с этим дело.
50 Проверьте, не ослаблены ли винты на обоих концах клеммы питания и подключения кабеля SPI
51 Замените источник питания»
52 Ошибка, некоторые чипы работают неправильно, и количество ядер на чипе ненормально. Номер платы вычислительной мощности: Номер чипа, «1.Обратите внимание, что если нет явных отклонений в вычислительной мощности всей машины (ни одна плата не упала), нет необходимости иметь с этим дело.
53 Перезапустите майнер, чтобы узнать, по-прежнему ли сообщается о той же ошибке
54 Замените проблемную плату вычислительной мощности (ремонт головоломки)
55 ErrInvVidtype, тип платы управления/версия прошивки/количество микросхем не соответствует, тип платы управления/версия прошивки/количество микросхем не соответствует, «видтип, тип майнера, подтип, номер микросхемы», «После накопления нескольких единиц (>10) обратитесь к разработчику программного обеспечения, чтобы решить эту проблему сразу»
56 ErrBadRearChips, последние несколько чипов имеют низкую вычислительную мощность, а последние несколько чипов имеют низкую вычислительную мощность, в настоящее время не нуждаются в обработке
57 ErrInvTuneParam, параметры старения являются ненормальными, начальная частота старения и напряжение неверны, и в настоящее время старение не нуждается в обработке.
58 ,,,,,
59 ,,,,,»внимание：
60 Каждый раз, когда вы выполняете шаг решения, вам необходимо снова включить питание, чтобы убедиться, что оно вернулось в нормальное состояние.
61 После замены каждой детали, если проблема не решена, замененные детали следует вернуть на исходную машину.
62 Установлено, что отремонтированная плата вычислительной мощности требует добавления кода ошибки и простого описания проблемы».
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
Мы нашли 52 сервисных центра осуществляющих ремонт асиков, майнеров инносиликон в России. Уточните в каком городе вы хотите найти сервисный центр.
Уточните в каком городе вы хотите найти сервисный центр.
Заявка во все сервисы
Сервисные центры по ремонту асиков, майнеров Innosilicon
Фильтры
Более 20 лет на рынке ремонта — главный гарант качества работ и профессионализма!
Ремонт асиков, майнеров инносиликон
Гарантия на комплектующие до 2-x лет, Диагностика ваших устройств от 15 минут, Самые Выгодные цены по городу, Скидки пенсионерам!!!
Ремонт асиков, майнеров инносиликон
Ремонт асиков, майнеров инносиликон
Честный ремонт по разумной цене!
Ремонт асиков, майнеров Innosilicon
Сервис-центр КомпрайЭкспресс — это профессиональный ремонт и обслуживание компьютерной техники
Ремонт асиков, майнеров Innosilicon
Ремонт цифровой техники
Ремонт асиков, майнеров инносиликон
Все ремонтируют здесь! Мастерские по всему городу!
Ремонт асиков, майнеров Innosilicon
Атлант Сервисный Центр
Ремонт асиков, майнеров Innosilicon
Наши цены без сюрпризов, а качество услуг вас приятно удивит!
Ремонт асиков, майнеров инносиликон
Все ремонтируют здесь! Мастерские по всему городу!
Ремонт асиков, майнеров Innosilicon
Не всегда нужно обращаться в сервис, вы можете задать вопрос и получить консультацию экспертов.
- Асики, Майнеры Innosilicon
Модель: A10 Pro ETH Miner - Не работает один модуль в /stat отмечен как true
- Асики, Майнеры Innosilicon
Модель: T2T-30T - Не видет 2 платы
- Асики, Майнеры Innosilicon
Модель: T2T-25T - После получасовой сесии уходит в перегрев. Хэш держит нормальный. Чипы целые
- Асики, Майнеры Innosilicon
Модель: A10 Pro ETH Miner - не работает одна плата
- Асики, Майнеры Innosilicon
Модель: t2thm - После 20-30 минут начинает перезагружаться, выдает ошибку 33, после второй-третьей перезагрузки первый чип начинает показывать температуру 392, + еще один чип на плате рандомно показывает 392 + еще один рандомно около 100. Перезагружаешь асик, снова все ок. Меняли первый чип, не помогло.
- Асики, Майнеры Innosilicon
Модель: T2TH - [ERROR]:Check receive buffer ready timeout!
Jun 10 20:59:46 InnoMiner miner_test[1478]: [ERROR]:chain1: ERROR — failed to recv spi data cmd:0x400
Jun 10 20:59:46 InnoMiner miner_test[1478]: [WARNING]:chain1: RESET failed 1 times
Jun 10 20:59:46 InnoMiner miner_test[1478]: [ERROR]:Check receive buffer ready timeout!
Jun 10 20:59:46 InnoMiner miner_test[1478]: [ERROR]:chain1: ERROR — failed to recv spi data cmd:0x400
Jun 10 20:59:46 InnoMiner miner_test[1478]: [ERROR]:chain1: RESET failed 2 times
Jun 10 20:59:46 InnoMiner miner_test[1478]: [ERROR]:chain1: cann’t find right chip type!!!
- Асики, Майнеры Innosilicon
Модель: t2th (37th) - Есть неисправность на одной из хеш плат. В веб-интерфейсе выдаёт ошибку SETPLL_PLANB_FAIL.chain(2).chip(1).msg(105MHz)
- Асики, Майнеры Innosilicon
Модель: T2TZ - Добрый день !
Вы закупаете контрольные платы для Т2Тz ?
- Асики, Майнеры Innosilicon
Модель: T2T 33T - ERROR CODE:
24
ERROR MESSAGE:
ENCORE_FAIL.chain(3).chip(1).msg()
DESCRIPTION:
部分算力板无法上电
SOLUTION:
1.检查电源端子两端螺丝及SPI排线连接是否有松动
2.更换电源
3.更换控制板
4.更换有问题的算力板（拼板返修）
注：
1.每执行一个解决步骤需要重新上电确认是否恢复正常
2.更换每个部件之后如果问题没有解决，换下的部件应装回原来的机器
3.确定返修的算力板都要求贴上错误码及简单问题描述вот такая ошибка, плата не запускается
- Асики, Майнеры Innosilicon
Модель: T2T-30T - 2 чипа вышли из работы. Их нужно заменить. Сколько стоит?