Bitcoin Forum
May 21, 2024, 06:11:49 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Need EEPROM file for 42801  (Read 203 times)
irfan655 (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
December 03, 2023, 12:06:57 PM
 #1

I found error on my all hashboards ..just order the EEPROM programmer from zeus mining Now i need file to write the code on 3 hashboard...
Code:
Irfan Haider:
[2015/01/01 00:00:16] INFO: Antminer S19 (88) (Vnish 1.2.0-rc5)
[2015/01/01 00:00:16] INFO: Initializing PSU
[2015/01/01 00:00:17] INFO: PSU model: 0x73
[2015/01/01 00:00:17] INFO: Switching to manual fan control (30%)
[2015/01/01 00:00:17] INFO: Checking fans
[2023/11/27 05:56:29] INFO: fan#1 - OK
[2023/11/27 05:56:29] INFO: fan#2 - OK
[2023/11/27 05:56:29] INFO: fan#3 - OK
[2023/11/27 05:56:29] INFO: fan#4 - OK
[2023/11/27 05:56:29] INFO: Power ON
[2023/11/27 05:56:29] INFO: Setting voltage to 17000 mV
[2023/11/27 05:56:30] INFO: chain#1 - Connected
[2023/11/27 05:56:30] INFO: chain#2 - Connected
[2023/11/27 05:56:30] INFO: chain#3 - Connected
[2023/11/27 05:56:30] ERROR: Invalid board info crc (actual:0a, stored:1c) /eeprom_v4.c:131/
[2023/11/27 05:56:30] ERROR: chain#1 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:56:30] ERROR: Invalid board info crc (actual:1d, stored:ee) /eeprom_v4.c:131/
[2023/11/27 05:56:30] ERROR: chain#2 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:56:31] ERROR: Invalid board info crc (actual:0d, stored:fc) /eeprom_v4.c:131/
[2023/11/27 05:56:31] ERROR: chain#3 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:56:31] ERROR: Failed read eeprom! /driver-btm-base.c:3930/
[2023/11/27 05:56:31] ERROR: Miner initialization failed /driver-btm-base.c:4132/
[2023/11/27 05:56:31] INFO: Shutting down the miner
[2023/11/27 05:56:31] INFO: chain#1 - Powering off the chain
[2023/11/27 05:56:31] INFO: chain#2 - Powering off the chain
[2023/11/27 05:56:31] INFO: chain#3 - Powering off the chain
[2023/11/27 05:56:31] INFO: Power OFF
[2023/11/27 05:56:57] INFO: Antminer S19 (88) (Vnish 1.2.0-rc5)
[2023/11/27 05:56:57] INFO: Initializing PSU
[2023/11/27 05:56:58] INFO: PSU model: 0x73
[2023/11/27 05:56:58] INFO: Switching to manual fan control (30%)
[2023/11/27 05:56:58] INFO: Checking fans
[2023/11/27 05:57:01] INFO: fan#1 - OK
[2023/11/27 05:57:01] INFO: fan#2 - OK
[2023/11/27 05:57:01] INFO: fan#3 - OK
[2023/11/27 05:57:01] INFO: fan#4 - OK
[2023/11/27 05:57:01] INFO: Power ON
[2023/11/27 05:57:01] INFO: Setting voltage to 17000 mV
[2023/11/27 05:57:02] INFO: chain#1 - Connected
[2023/11/27 05:57:02] INFO: chain#2 - Connected
[2023/11/27 05:57:02] INFO: chain#3 - Connected
[2023/11/27 05:57:02] ERROR: Invalid board info crc (actual:0a, stored:1c) /eeprom_v4.c:131/
[2023/11/27 05:57:02] ERROR: chain#1 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:57:03] ERROR: Invalid board info crc (actual:1d, stored:ee) /eeprom_v4.c:131/
[2023/11/27 05:57:03] ERROR: chain#2 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:57:03] ERROR: Invalid board info crc (actual:0d, stored:fc) /eeprom_v4.c:131/
[2023/11/27 05:57:03] ERROR: chain#3 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:57:03] ERROR: Failed read eeprom! /driver-btm-base.c:3930/
[2023/11/27 05:57:03] ERROR: Miner initialization failed /driver-btm-base.c:4132/
[2023/11/27 05:57:03] INFO: Shutting down the miner
[2023/11/27 05:57:03] INFO: chain#1 - Powering off the chain
[2023/11/27 05:57:03] INFO: chain#2 - Powering off the chain
[2023/11/27 05:57:03] INFO: chain#3 - Powering off the chain
[2023/11/27 05:57:03] INFO: Power OFF
[2023/11/27 05:57:29] INFO: Antminer S19 (88) (Vnish 1.2.0-rc5)
[2023/11/27 05:57:29] INFO: Initializing PSU
[2023/11/27 05:57:30] INFO: PSU model: 0x73
[2023/11/27 05:57:30] INFO: Switching to manual fan control (30%)
[2023/11/27 05:57:30] INFO: Checking fans
[2023/11/27 05:57:33] INFO: fan#1 - OK
[2023/11/27 05:57:33] INFO: fan#2 - OK
[2023/11/27 05:57:33] INFO: fan#3 - OK
[2023/11/27 05:57:33] INFO: fan#4 - OK
[2023/11/27 05:57:33] INFO: Power ON
[2023/11/27 05:57:33] INFO: Setting voltage to 17000 mV
[2023/11/27 05:57:34] INFO: chain#1 - Connected
[2023/11/27 05:57:34] INFO: chain#2 - Connected
[2023/11/27 05:57:34] INFO: chain#3 - Connected
[2023/11/27 05:57:34] ERROR: Invalid board info crc (actual:0a, stored:1c) /eeprom_v4.c:131/
[2023/11/27 05:57:34] ERROR: chain#1 - failed to parse eeprom data /chain-info.c:80/

[2023/11/27 05:57:35] ERROR: Invalid board info crc (actual:1d, stored:ee) /eeprom_v4.c:131/
[2023/11/27 05:57:35] ERROR: chain#2 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:57:35] ERROR: Invalid board info crc (actual:0d, stored:fc) /eeprom_v4.c:131/
[2023/11/27 05:57:35] ERROR: chain#3 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:57:35] ERROR: Failed read eeprom! /driver-btm-base.c:3930/
[2023/11/27 05:57:35] ERROR: Miner initialization failed /driver-btm-base.c:4132/
[2023/11/27 05:57:35] INFO: Shutting down the miner
[2023/11/27 05:57:35] INFO: chain#1 - Powering off the chain
[2023/11/27 05:57:35] INFO: chain#2 - Powering off the chain
[2023/11/27 05:57:35] INFO: chain#3 - Powering off the chain
[2023/11/27 05:57:35] INFO: Power OFF
[2023/11/27 05:58:01] INFO: Antminer S19 (88) (Vnish 1.2.0-rc5)
[2023/11/27 05:58:01] INFO: Initializing PSU
[2023/11/27 05:58:02] INFO: PSU model: 0x73
[2023/11/27 05:58:02] INFO: Switching to manual fan control (30%)
[2023/11/27 05:58:02] INFO: Checking fans
[2023/11/27 05:58:05] INFO: fan#1 - OK
[2023/11/27 05:58:05] INFO: fan#2 - OK
[2023/11/27 05:58:05] INFO: fan#3 - OK
[2023/11/27 05:58:05] INFO: fan#4 - OK
[2023/11/27 05:58:05] INFO: Power ON
[2023/11/27 05:58:05] INFO: Setting voltage to 17000 mV
[2023/11/27 05:58:06] INFO: chain#1 - Connected
[2023/11/27 05:58:06] INFO: chain#2 - Connected
[2023/11/27 05:58:06] INFO: chain#3 - Connected
[2023/11/27 05:58:07] ERROR: Invalid board info crc (actual:0a, stored:1c) /eeprom_v4.c:131/
[2023/11/27 05:58:07] ERROR: chain#1 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:58:07] ERROR: Invalid board info crc (actual:1d, stored:ee) /eeprom_v4.c:131/
[2023/11/27 05:58:07] ERROR: chain#2 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:58:07] ERROR: Invalid board info crc (actual:0d, stored:fc) /eeprom_v4.c:131/
[2023/11/27 05:58:07] ERROR: chain#3 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:58:07] ERROR: Failed read eeprom! /driver-btm-base.c:3930/
[2023/11/27 05:58:07] ERROR: Miner initialization failed /driver-btm-base.c:4132/
[2023/11/27 05:58:07] INFO: Shutting down the miner
[2023/11/27 05:58:07] INFO: chain#1 - Powering off the chain
[2023/11/27 05:58:07] INFO: chain#2 - Powering off the chain
[2023/11/27 05:58:07] INFO: chain#3 - Powering off the chain
[2023/11/27 05:58:07] INFO: Power OFF
philipma1957
Legendary
*
Offline Offline

Activity: 4130
Merit: 7907


'The right to privacy matters'


View Profile WWW
December 03, 2023, 10:31:45 PM
 #2

did the unit work when you ran it with stock firmware?
did flashing with vnsh ever work?

if no maybe the vnsh flashed board is bad.

▄▄███████▄▄
▄██████████████▄
▄██████████████████▄
▄████▀▀▀▀███▀▀▀▀█████▄
▄█████████████▄█▀████▄
███████████▄███████████
██████████▄█▀███████████
██████████▀████████████
▀█████▄█▀█████████████▀
▀████▄▄▄▄███▄▄▄▄████▀
▀██████████████████▀
▀███████████████▀
▀▀███████▀▀
.
 MΞTAWIN  THE FIRST WEB3 CASINO   
.
.. PLAY NOW ..
BitMaxz
Legendary
*
Offline Offline

Activity: 3262
Merit: 2974


Block halving is coming.


View Profile WWW
December 03, 2023, 11:33:45 PM
 #3

did the unit work when you ran it with stock firmware?
did flashing with vnsh ever work?

if no maybe the vnsh flashed board is bad.

I got a PM from him a few days ago check the message below he already tried flashing the unit with different firmware including custom firmware according to him the result is the same.

So I suggested him to flash the hashboard with working EEPROM it requires a hashboard code editor which is why he decided to buy this tool from Zeusbtc and now he is asking for working EEPROM I PM him and maybe someone had working EEPROM for this unit that he can get for free if not then he doesn't have any choice but to buy a working EEPROM from Zeusbtc if he wants to repair it by himself or contact zeusbtc to get help.

Hello there i need help with my 2 s19.. when electricity gone and came back the miner start abnormally i start checking but the log show me EEPROM error everytime i try custom frimware as well but the both s19 didn't hash need help please..there is no repair center in my country i will do everything to solve this problem..

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
ZeusBtc.com
Jr. Member
*
Offline Offline

Activity: 41
Merit: 22


View Profile WWW
December 04, 2023, 01:37:57 AM
 #4

If you still need help, please contact Zeusbtc's technician at any time, and he will provide you with a solution based on the fault phenomenon.
irfan655 (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
December 04, 2023, 09:36:48 AM
 #5

did the unit work when you ran it with stock firmware?
did flashing with vnsh ever work?

if no maybe the vnsh flashed board is bad.
Yes i try with stock frimware as well as vnish ..but still getting EEPROM error .. i order the device for programming idk if i can find the eeprom file..
mikeywith
Legendary
*
Offline Offline

Activity: 2226
Merit: 6405


be constructive or S.T.F.U


View Profile
December 04, 2023, 10:33:20 PM
 #6

Code:
[2023/11/27 05:56:30] ERROR: Invalid board info crc (actual:0a, stored:1c) /eeprom_v4.c:131/
[2023/11/27 05:56:30] ERROR: chain#1 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:56:30] ERROR: Invalid board info crc (actual:1d, stored:ee) /eeprom_v4.c:131/
[2023/11/27 05:56:30] ERROR: chain#2 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:56:31] ERROR: Invalid board info crc (actual:0d, stored:fc) /eeprom_v4.c:131/
[2023/11/27 05:56:31] ERROR: chain#3 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:56:31] ERROR: Failed read eeprom! /driver-btm-base.c:3930/
[2023/11/27 05:56:31] ERROR: Miner initialization failed /driver-btm-base.c:4132/

I don't have any experience with the miner in question but here is a piece of info that might help you move further, it's possible that all 3 boards have a good running hex / EEPROM but they simply are not interchangeable/compatible, which was the case with the 17 series, you couldn't just mix and match different hashboards,  so the first thing you try would be to extract the hex file from one of the boards and write it to the other two, try all 3 boards.

If that fails, then I would find it pretty odd that all 3 hashboards have the same issue and the likelihood of this problem will be the control board.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
irfan655 (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
December 05, 2023, 02:38:26 AM
 #7

Code:
[2023/11/27 05:56:30] ERROR: Invalid board info crc (actual:0a, stored:1c) /eeprom_v4.c:131/
[2023/11/27 05:56:30] ERROR: chain#1 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:56:30] ERROR: Invalid board info crc (actual:1d, stored:ee) /eeprom_v4.c:131/
[2023/11/27 05:56:30] ERROR: chain#2 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:56:31] ERROR: Invalid board info crc (actual:0d, stored:fc) /eeprom_v4.c:131/
[2023/11/27 05:56:31] ERROR: chain#3 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:56:31] ERROR: Failed read eeprom! /driver-btm-base.c:3930/
[2023/11/27 05:56:31] ERROR: Miner initialization failed /driver-btm-base.c:4132/

I don't have any experience with the miner in question but here is a piece of info that might help you move further, it's possible that all 3 boards have a good running hex / EEPROM but they simply are not interchangeable/compatible, which was the case with the 17 series, you couldn't just mix and match different hashboards,  so the first thing you try would be to extract the hex file from one of the boards and write it to the other two, try all 3 boards.

If that fails, then I would find it pretty odd that all 3 hashboards have the same issue and the likelihood of this problem will be the control board.
I changed the control board but it seems that problem is still with the hashboards i would try your way waiting for the device..Just asking  if i can change the OS will this error not be removed!!! Like brainOS or HiveOS ???Any possibility
mikeywith
Legendary
*
Offline Offline

Activity: 2226
Merit: 6405


be constructive or S.T.F.U


View Profile
December 06, 2023, 08:12:31 PM
 #8

I changed the control board but it seems that problem is still with the hashboards i would try your way waiting for the device..Just asking  if i can change the OS will this error not be removed!!! Like brainOS or HiveOS ???Any possibility

I don't know about Hiveor os BOs, but I remember one of the devs of Vnish telling me that they don't even read EEPROM at all, so if what they say is correct (assuming my understand was correct as well) then I suppose if it's only an EEPROM related issue, by passing it by Vnish should be doable, but then again, even with the stock firmware it's easy to test this, you would just leave a single hashbaord plugged and see if it hashes right away, if it does -- you confirm it's compatibility issue, if it doesn't -- then it's not.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
irfan655 (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
December 07, 2023, 05:58:21 AM
 #9

Code:
I don't know about Hiveor os BOs, but I remember one of the devs of Vnish telling me that they don't even read EEPROM at all, so if what they say is correct (assuming my understand was correct as well) then I suppose if it's only an EEPROM related issue, by passing it by Vnish should be doable, but then again, even with the stock firmware it's easy to test this, you would just leave a single hashbaord plugged and see if it hashes right away, if it does -- you confirm it's compatibility issue, if it doesn't -- then it's not




I tried vnish as well but it give me EEPROM error running single hashboard .. i try with other two as well still getting that error ... Do you think there any issues with the PSU !!
 
mikeywith
Legendary
*
Offline Offline

Activity: 2226
Merit: 6405


be constructive or S.T.F.U


View Profile
December 07, 2023, 10:07:31 PM
 #10

I tried vnish as well but it give me EEPROM error running single hashboard .. i try with other two as well still getting that error ... Do you think there any issues with the PSU !!

According to what I know, the main piece of info that is stored on the EEPROM is the voltage for all the hash boards, now with the claim that Vnish ignores those, I think it should work without a valid hex, unless there are other things that the software needs to read, anyway, send me the kernel log you got from Vnish and I will try to forward it to one of their devs to see if they have a clue.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
irfan655 (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
December 08, 2023, 04:24:54 AM
Last edit: December 08, 2023, 04:43:33 AM by irfan655
 #11

According to what I know, the main piece of info that is stored on the EEPROM is the voltage for all the hash boards, now with the claim that Vnish ignores those, I think it should work without a valid hex, unless there are other things that the software needs to read, anyway, send me the kernel log you got from Vnish and I will try to forward it to one of their devs to see if they have a clue.
Quote
Code:
Irfan Haider:
[2015/01/01 00:00:16] INFO: Antminer S19 (88) (Vnish 1.2.0-rc5)
[2015/01/01 00:00:16] INFO: Initializing PSU
[2015/01/01 00:00:17] INFO: PSU model: 0x73
[2015/01/01 00:00:17] INFO: Switching to manual fan control (30%)
[2015/01/01 00:00:17] INFO: Checking fans
[2023/11/27 05:56:29] INFO: fan#1 - OK
[2023/11/27 05:56:29] INFO: fan#2 - OK
[2023/11/27 05:56:29] INFO: fan#3 - OK
[2023/11/27 05:56:29] INFO: fan#4 - OK
[2023/11/27 05:56:29] INFO: Power ON
[2023/11/27 05:56:29] INFO: Setting voltage to 17000 mV
[2023/11/27 05:56:30] INFO: chain#1 - Connected
[2023/11/27 05:56:30] INFO: chain#2 - Connected
[2023/11/27 05:56:30] INFO: chain#3 - Connected
[2023/11/27 05:56:30] ERROR: Invalid board info crc (actual:0a, stored:1c) /eeprom_v4.c:131/
[2023/11/27 05:56:30] ERROR: chain#1 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:56:30] ERROR: Invalid board info crc (actual:1d, stored:ee) /eeprom_v4.c:131/
[2023/11/27 05:56:30] ERROR: chain#2 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:56:31] ERROR: Invalid board info crc (actual:0d, stored:fc) /eeprom_v4.c:131/
[2023/11/27 05:56:31] ERROR: chain#3 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:56:31] ERROR: Failed read eeprom! /driver-btm-base.c:3930/
[2023/11/27 05:56:31] ERROR: Miner initialization failed /driver-btm-base.c:4132/
[2023/11/27 05:56:31] INFO: Shutting down the miner
[2023/11/27 05:56:31] INFO: chain#1 - Powering off the chain
[2023/11/27 05:56:31] INFO: chain#2 - Powering off the chain
[2023/11/27 05:56:31] INFO: chain#3 - Powering off the chain
[2023/11/27 05:56:31] INFO: Power OFF
[2023/11/27 05:56:57] INFO: Antminer S19 (88) (Vnish 1.2.0-rc5)
[2023/11/27 05:56:57] INFO: Initializing PSU
[2023/11/27 05:56:58] INFO: PSU model: 0x73
[2023/11/27 05:56:58] INFO: Switching to manual fan control (30%)
[2023/11/27 05:56:58] INFO: Checking fans
[2023/11/27 05:57:01] INFO: fan#1 - OK
[2023/11/27 05:57:01] INFO: fan#2 - OK
[2023/11/27 05:57:01] INFO: fan#3 - OK
[2023/11/27 05:57:01] INFO: fan#4 - OK
[2023/11/27 05:57:01] INFO: Power ON
[2023/11/27 05:57:01] INFO: Setting voltage to 17000 mV
[2023/11/27 05:57:02] INFO: chain#1 - Connected
[2023/11/27 05:57:02] INFO: chain#2 - Connected
[2023/11/27 05:57:02] INFO: chain#3 - Connected
[2023/11/27 05:57:02] ERROR: Invalid board info crc (actual:0a, stored:1c) /eeprom_v4.c:131/
[2023/11/27 05:57:02] ERROR: chain#1 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:57:03] ERROR: Invalid board info crc (actual:1d, stored:ee) /eeprom_v4.c:131/
[2023/11/27 05:57:03] ERROR: chain#2 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:57:03] ERROR: Invalid board info crc (actual:0d, stored:fc) /eeprom_v4.c:131/
[2023/11/27 05:57:03] ERROR: chain#3 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:57:03] ERROR: Failed read eeprom! /driver-btm-base.c:3930/
[2023/11/27 05:57:03] ERROR: Miner initialization failed /driver-btm-base.c:4132/
[2023/11/27 05:57:03] INFO: Shutting down the miner
[2023/11/27 05:57:03] INFO: chain#1 - Powering off the chain
[2023/11/27 05:57:03] INFO: chain#2 - Powering off the chain
[2023/11/27 05:57:03] INFO: chain#3 - Powering off the chain
[2023/11/27 05:57:03] INFO: Power OFF
[2023/11/27 05:57:29] INFO: Antminer S19 (88) (Vnish 1.2.0-rc5)
[2023/11/27 05:57:29] INFO: Initializing PSU
[2023/11/27 05:57:30] INFO: PSU model: 0x73
[2023/11/27 05:57:30] INFO: Switching to manual fan control (30%)
[2023/11/27 05:57:30] INFO: Checking fans
[2023/11/27 05:57:33] INFO: fan#1 - OK
[2023/11/27 05:57:33] INFO: fan#2 - OK
[2023/11/27 05:57:33] INFO: fan#3 - OK
[2023/11/27 05:57:33] INFO: fan#4 - OK
[2023/11/27 05:57:33] INFO: Power ON
[2023/11/27 05:57:33] INFO: Setting voltage to 17000 mV
[2023/11/27 05:57:34] INFO: chain#1 - Connected
[2023/11/27 05:57:34] INFO: chain#2 - Connected
[2023/11/27 05:57:34] INFO: chain#3 - Connected
[2023/11/27 05:57:34] ERROR: Invalid board info crc (actual:0a, stored:1c) /eeprom_v4.c:131/
[2023/11/27 05:57:34] ERROR: chain#1 - failed to parse eeprom data /chain-info.c:80/

[2023/11/27 05:57:35] ERROR: Invalid board info crc (actual:1d, stored:ee) /eeprom_v4.c:131/
[2023/11/27 05:57:35] ERROR: chain#2 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:57:35] ERROR: Invalid board info crc (actual:0d, stored:fc) /eeprom_v4.c:131/
[2023/11/27 05:57:35] ERROR: chain#3 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:57:35] ERROR: Failed read eeprom! /driver-btm-base.c:3930/
[2023/11/27 05:57:35] ERROR: Miner initialization failed /driver-btm-base.c:4132/
[2023/11/27 05:57:35] INFO: Shutting down the miner
[2023/11/27 05:57:35] INFO: chain#1 - Powering off the chain
[2023/11/27 05:57:35] INFO: chain#2 - Powering off the chain
[2023/11/27 05:57:35] INFO: chain#3 - Powering off the chain
[2023/11/27 05:57:35] INFO: Power OFF
[2023/11/27 05:58:01] INFO: Antminer S19 (88) (Vnish 1.2.0-rc5)
[2023/11/27 05:58:01] INFO: Initializing PSU
[2023/11/27 05:58:02] INFO: PSU model: 0x73
[2023/11/27 05:58:02] INFO: Switching to manual fan control (30%)
[2023/11/27 05:58:02] INFO: Checking fans
[2023/11/27 05:58:05] INFO: fan#1 - OK
[2023/11/27 05:58:05] INFO: fan#2 - OK
[2023/11/27 05:58:05] INFO: fan#3 - OK
[2023/11/27 05:58:05] INFO: fan#4 - OK
[2023/11/27 05:58:05] INFO: Power ON
[2023/11/27 05:58:05] INFO: Setting voltage to 17000 mV
[2023/11/27 05:58:06] INFO: chain#1 - Connected
[2023/11/27 05:58:06] INFO: chain#2 - Connected
[2023/11/27 05:58:06] INFO: chain#3 - Connected
[2023/11/27 05:58:07] ERROR: Invalid board info crc (actual:0a, stored:1c) /eeprom_v4.c:131/
[2023/11/27 05:58:07] ERROR: chain#1 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:58:07] ERROR: Invalid board info crc (actual:1d, stored:ee) /eeprom_v4.c:131/
[2023/11/27 05:58:07] ERROR: chain#2 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:58:07] ERROR: Invalid board info crc (actual:0d, stored:fc) /eeprom_v4.c:131/
[2023/11/27 05:58:07] ERROR: chain#3 - failed to parse eeprom data /chain-info.c:80/
[2023/11/27 05:58:07] ERROR: Failed read eeprom! /driver-btm-base.c:3930/
[2023/11/27 05:58:07] ERROR: Miner initialization failed /driver-btm-base.c:4132/
[2023/11/27 05:58:07] INFO: Shutting down the miner
[2023/11/27 05:58:07] INFO: chain#1 - Powering off the chain
[2023/11/27 05:58:07] INFO: chain#2 - Powering off the chain
[2023/11/27 05:58:07] INFO: chain#3 - Powering off the chain
[2023/11/27 05:58:07] INFO: Power OFF
Artemis3
Legendary
*
Offline Offline

Activity: 2030
Merit: 1563


CLEAN non GPL infringing code made in Rust lang


View Profile WWW
December 10, 2023, 02:46:29 PM
 #12

Braiins OS doesn't touch EEPROMs but it reads them to identify the miner. What you could do is force the model but this is very dangerous and needs to be done with extreme care.

In theory the model to set in bosminer.toml with for this (if your hashboard model is correct) would be:

model = 'Antminer S19J88'

[model_detection]
use_config_fallback = true

Of course if you can get your eeproms fixed that would be the better solution.

██████
███████
███████
████████
BRAIINS OS+|AUTOTUNING
MINING FIRMWARE
|
Increase hashrate on your Bitcoin ASICs,
improve efficiency as much as 25%, and
get 0% pool fees on Braiins Pool
irfan655 (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
December 11, 2023, 03:09:01 AM
 #13

Braiins OS doesn't touch EEPROMs but it reads them to identify the miner. What you could do is force the model but this is very dangerous and needs to be done with extreme care.

In theory the model to set in bosminer.toml with for this (if your hashboard model is correct) would be:

model = 'Antminer S19J88'

[model_detection]
use_config_fallback = true

Of course if you can get your eeproms fixed that would be the better solution.

Hello can you please tell me how to do that I'm not good at computer.. and i will try to fix the EEPROM with the device first ..
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!