http://[img][img][img][img][/img][/img][/img][/img]

Quote from: mikxxy on November 27, 2020, 11:27:22 PM

Quote from: mikeywith on November 27, 2020, 09:59:14 PM

Quote from: mikxxy on November 27, 2020, 09:12:36 PM

whats confusing as said is the T17+ and none with different amount of chips on each board, 44 and 64?, should they need a designatet FW depending on asic count on each hash bord? Awesom issued two different FW's 1.00 and 2.0.3? Ill try the first one on the faulty card, may be it will run?

That is strange, I don't think the firmware knows the number of chips i.e it isn't hard coded into it, it probably gets the information from the hash board itself, the reasoning behind my point is that using the same control board and the same firmware you can run different hashboards, for an example if you take S17 hash boards and put them in your S17 pro they will work just fine despite having different asic count.

But with that being said you should reach out to Patrike and explain the issue to him.

Yes im with you,. when i try run the bad controler in the second maschine it behaves exactly as in the previous setting, by not beeing able to detect correct asic valuse but in addition, now also giving error of not detecting any fans, even though the are spinning accordingly to pre setting of 30% (awesom FW), could it be affected by any virus in any of processors? A leds onboard are behaving as expected, boot sequenceas as it should, then it tries to initialize the hash bords iindefinitely. So what could by wrong with this controller?

Regarding the poped heat sink can it just be glued on and then reinforced by glueing the top of the heatsink to those in vicinity?

By joggling the controller back and forth, i started to catch on Awesom, detecting asic chains but the first one, also it warns if try to raise freq some steps above 500Mhz

Code:

N: chain[0] - Failed to reset pic (attempt = 2), resp: 0x90 0x90
[2020/11/27 23:45:34] WARN: chain[0] - Failed to reset pic (attempt = 3), resp: 0x90 0x90
[2020/11/27 23:45:35] WARN: chain[0] - Failed to start pic app (attempt = 1), resp: 0x01 0x01
[2020/11/27 23:45:36] WARN: chain[0] - Failed to start pic app (attempt = 2), resp: 0x01 0x01
[2020/11/27 23:45:36] WARN: chain[0] - Failed to start pic app (attempt = 3), resp: 0x01 0x01
[2020/11/27 23:45:38] WARN: chain[0] - Failed to reset pic (attempt = 1), resp: 0x01 0x01
[2020/11/27 23:45:39] WARN: chain[0] - Failed to reset pic (attempt = 2), resp: 0x01 0x01
[2020/11/27 23:45:41] INFO: chain[2] - 44 chips detected
[2020/11/27 23:45:41] WARN: chain[0] - Failed to reset pic (attempt = 3), resp: 0x01 0x01
[2020/11/27 23:45:41] WARN: chain[0] - Failed to start pic app (attempt = 1), resp: 0x01 0x01
[2020/11/27 23:45:42] WARN: chain[0] - Failed to start pic app (attempt = 2), resp: 0x01 0x01
[2020/11/27 23:45:42] WARN: chain[0] - Failed to start pic app (attempt = 3), resp: 0x01 0x01
[2020/11/27 23:45:43] INFO: chain[1] - 44 chips detected
[2020/11/27 23:45:44] WARN: chain[0] - Failed to reset pic (attempt = 1), resp: 0x01 0x01
[2020/11/27 23:45:46] WARN: chain[0] - Failed to reset pic (attempt = 2), resp: 0x01 0x01
[2020/11/27 23:45:47] WARN: chain[0] - Failed to reset pic (attempt = 3), resp: 0x01 0x01
[2020/11/27 23:45:48] WARN: chain[0] - Failed to start pic app (attempt = 1), resp: 0x01 0x01

Code:

2020/11/27 23:39:24] INFO: Initializing
[2020/11/27 23:39:22] INFO: eFUSE protection is active
[2020/11/27 23:39:00] INFO: Initializing
[2020/11/27 23:38:58] INFO: eFUSE protection is active
[2020/11/27 23:38:34] INFO: Initializing
[2020/11/27 23:38:34] INFO: Pool connection FAILED. Check INTERNET, POOL URL or WORKER
[2020/11/27 23:38:32] INFO: eFUSE protection is active
[2020/11/27 23:38:00] INFO: Mining
[2020/11/27 23:36:38] INFO: Initializing
[2020/11/27 23:36:36] INFO: eFUSE protection is active
[2020/11/27 23:36:30] INFO: Initializing
[2020/11/27 23:36:28] INFO: eFUSE protection is active
[2020/11/27 23:35:59] INFO: Initializing
[2020/11/27 23:35:59] INFO: Pool connection FAILED. Check INTERNET,