Author

Topic: Antminer S9 0 ASICs, but 63 real detected (Read 134 times)

legendary
Activity: 2436
Merit: 6643
be constructive or S.T.F.U
August 19, 2021, 10:56:22 PM
#6
I have tried various firmwares, all of which resulted in the same 0 ASIC error.

Then you have a faulty chip which is most likely in the first domain like chip 0 or so, although the 0 chip error could be the result of something that is power related (not something you can see with your naked eye), if you have time and the tools you can check the voltage across all chips to find out which one is toasted, but then you will need to order the chip to replace it, not sure if it's worth the trouble given that fact that this is an old S9 which is approaching it's final stages anyways.
legendary
Activity: 3472
Merit: 3217
Playbet.io - Crypto Casino and Sportsbook
August 19, 2021, 12:01:00 PM
#5
If you already did everything on software then it's a hardware issue.
Have you physically check the terminal for both PSU socket and ribbon cable? Check the hashboard if there are some burnt parts.

I suggest read the troubleshooting guide from ZeusBTC and maybe the first chip is dead that is why it shows 0 ASIC.
The guide can be found here https://www.zeusbtc.com/Repair.asp
newbie
Activity: 2
Merit: 0
August 19, 2021, 11:47:48 AM
#4
I have tried various firmwares, all of which resulted in the same 0 ASIC error. Currently there is only 1 hashboard attached to the control board. I have tried all of the hashboard ports on the control board all with the same results. I have 2 other hashboards that are in physically good condition. I hooked them to the control board but alas, no dice.

I've checked the MOSFETs on the hashboards, all of them passed test. I'm using a 500 watt ATX power supply + my bench power supply. Load seems pretty normal for an idle hashboard and controller. When the control board issues the reset command to the hashboard, the power usage drops a bit (about half an amp) then comes back up a second later. The controller is reading the PICs firmware version, so there is some kind of communication going on.

Thanks for your help!
legendary
Activity: 2436
Merit: 6643
be constructive or S.T.F.U
August 18, 2021, 11:58:54 PM
#3
According to your kernel logs, it has zero ASIC so how did you check that it is detected?

He probably got to the conclusion based on this part of the kernel log

Code:
real AsicNum = 63

The term "real AsicNum" isn't very clear, but it simply means the "normal asic number" which the control board is expecting to sense from each of the hash boards connected to it, so if it doesn't find all of them then -- troubles.

OP, is this miner running only with one hash board? have you tried a different firmware? some background/ history about the miner will help us troubleshoot more accuratly.
legendary
Activity: 3472
Merit: 3217
Playbet.io - Crypto Casino and Sportsbook
August 18, 2021, 06:03:16 PM
#2
According to your kernel logs, it has zero ASIC so how did you check that it is detected?

Next time use the pin threads under this section because most of the solutions about this issue are there look https://bitcointalksearch.org/topic/most-common-mining-issues-read-before-making-a-new-post-5103892

The only solution that I could suggest is to try to Test hash board one by one
Also, try to swap all ribbon cables and PSU cables, and maybe one of the cables is defective.
Also, check the fan and try to replug them.

Update your kernel logs here after you troubleshoot it one by one to find which hashboard is defective.
newbie
Activity: 2
Merit: 0
August 18, 2021, 02:53:07 PM
#1
Riddle me this...
My Antminer S9 is getting a zero ASIC error, though it seems like the controller is seeing some kind of ASIC.

the first couple lines in the kernel log (that aren't boot up related...) state.
Code:
AsicType = 1387
real AsicNum = 63
use critical mode to search freq...

However, when after bmminer tries to start up suddenly there are zero ASICs.
Code:
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
Chain[J6] has 0 asic

Does anyone have any ideas as to what the issue could be? The full log can be found herehttps://docs.google.com/document/d/1GHACCM_v8m1pIT8dm0osPPubY8-N_TckXzvML0tW21A/edit?usp=sharing Any help would be greatly appreciated.
Jump to: