tw0rak
|
|
June 07, 2019, 02:17:25 PM |
|
Hi guyz, Im asking for help - Im absolutely NOT new in this but I just cant flash S9 board from the SD. Everything tried and checked multiple times - jumper is in the right possition, both leds - red and green are shining SOLID and never start to blink. Doublechecked if there is that IMG uploaded with Diskimager, tripplechecked the jumper is right... After all this (never starts blinking) I have to disconnect it and there is still the same old (well better to say new) firmware. Any help?
EDIT: I have many S9s and just tried the same way at another one with very same results...I do not absolutely know how to continue...
|
|
|
|
ccgllc (OP)
Copper Member
Full Member
Offline
Activity: 658
Merit: 101
Math doesn't care what you believe.
|
|
June 07, 2019, 04:16:39 PM |
|
Not sure why. Suggest using a 16GB or small memory card. We followed the following steps which worked on over 100 controllers (from repetitive memory): 1) Pull controller from chasis 2) Flip jumper 4 (the one on the outside of the jumper block) 3) Attach power cable from standalone PSU 4) Power up PSU 5) Wait for a few minutes 6) Power down PSU 7) Flip jumper 4 back to normal Disconnect power 9) Reinstall controller
|
Mined for a living since 2017. Dabbled for years before that. Linux admin since 0.96 kernel and Slackware distributions on (4) floppies...
|
|
|
tw0rak
|
|
June 07, 2019, 06:33:59 PM Last edit: June 09, 2019, 12:20:32 PM by frodocooper |
|
Im probably doing sth wrong with the SD card - as if there is none in the slot, the board act the same.
wait a second...
EDIT: Yes - friday evening - thats the problem. I was using file S2S4S5S7-img.img - and now Ive used files for T9+ and... voila it works. Thanks for your patience!
Maybe another one:
Is it possible to do with the very latest bitmain firmware for S9? As I made it now at 3 miners w/o problem but this one Im not able to downgrade.
|
|
|
|
ccgllc (OP)
Copper Member
Full Member
Offline
Activity: 658
Merit: 101
Math doesn't care what you believe.
|
|
June 07, 2019, 08:29:56 PM Last edit: June 09, 2019, 12:21:11 PM by frodocooper |
|
Yes... the latest (anything tagged 2019) firmware is the reason one needs to go through the pain of reflashing via the SDHC port.
|
Mined for a living since 2017. Dabbled for years before that. Linux admin since 0.96 kernel and Slackware distributions on (4) floppies...
|
|
|
maxmad
Jr. Member
Offline
Activity: 55
Merit: 3
|
|
July 24, 2019, 11:18:09 PM Last edit: July 26, 2019, 03:18:30 AM by frodocooper |
|
Made 4 flashes through SD card using 2 different SD cards. Still the board has the same 201905311059 latest firmware. No way to downgrade. i want to use an older firmware to test if i can alive a dead hashing board https://bitcointalk.org/index.php?topic=5034849.0Jumper flipped, both led are flashing after some seconds but the board has still this latest firmware installed!
|
|
|
|
BitMaxz
Legendary
Offline
Activity: 3430
Merit: 3165
Playbet.io - Crypto Casino and Sportsbook
|
|
July 24, 2019, 11:58:15 PM Last edit: July 26, 2019, 03:18:51 AM by frodocooper |
|
Can you try to flash it to Braiin OS first through SD card after successfully flash it check the miner in the browser if the interface change to Braiins OS.
If successful then you can flash it back to bitmain image.
Then check it again if nothing change and the OS still BraiinsOS it means that your image from bitmain you download for SD card is corrupted you need to download the firmware again without using any 3rd party downloader browser should be enough to download the image/firmware for SD card.
Or maybe it's not flashing properly because the terminal has full of dirt/corroded. So check the SD card slot and maybe the terminal is corroded/full of rust that is why it's not flashing properly. If you have Laquer flo thinner you can clean them and resolder the terminal may solve your issue.
|
|
|
|
Artemis3
Legendary
Offline
Activity: 2030
Merit: 1573
CLEAN non GPL infringing code made in Rust lang
|
|
July 25, 2019, 02:28:20 PM |
|
Not sure why. Suggest using a 16GB or small memory card. Because SD, SDHC and SDXC each support different max capacities. If the port is SDHC, putting an SDXC card in there isn't going to work. A sure bet is always keep a small SD card (2gb max). But if someone mentioned 16gb it might mean it is SDHC. I never tried with such big capacity cards (wasteful). There is small chance you got a fake one, which are usually printed with large capacities (but are much smaller in reality). Best thing about low capacities is that nobody bothers faking them... To OP: Try booting BraiinsOS, (same jp4 jumper) if it boots, try installing it into the nand using its web ui. Move back jumper and see what happens... If it still boots Bitmain's firmware, then the nand my be damaged. Unlike Bitmain's, you don't have to install Braiins OS into the nand to use it, just leave it with the smallest (cheapest) SD card you can find and let it always boot from sd. I don't think a new controller is worth buying when any cheapo 1gb microsd card fixes it.
|
█████████████████████████ ██████████████████████████ ██████████████████████████ ███████████████████████████ | 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 | |
|
|
|
maxmad
Jr. Member
Offline
Activity: 55
Merit: 3
|
|
July 26, 2019, 12:37:57 AM Last edit: July 26, 2019, 03:20:32 AM by frodocooper |
|
OK Braiin OS installed to NAND. ( Using 16GB card, with 8GB there was an error "firmware.tar.gz" is missing ) Seems that the missing hashboard appeared and hashing. However in Braiin OS there is no temperature measurement! and after a while 2 hashing boards stop hashing Thu Jul 25 19:59:11 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:11.130] Accepted 06cba9a4 Diff 9.64K/4327 BC5 0 Thu Jul 25 19:59:11 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:11.522] sensors: 7/0 temperature read failed, using previous Thu Jul 25 19:59:11 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:11.522] sensors: 7/0 temperature (0.0,0.0) Thu Jul 25 19:59:11 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:11.522] sensors: no working sensors Thu Jul 25 19:59:17 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:17.432] Version submitting share mask 0x00c00000 with work version 0x20c00000 and pool version 0x20000000 Thu Jul 25 19:59:17 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:17.517] Accepted 6dddf4ae Diff 153K/4327 BC5 0 Thu Jul 25 19:59:18 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:18.203] Version submitting share mask 0x00800000 with work version 0x20800000 and pool version 0x20000000 Thu Jul 25 19:59:18 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:18.288] Accepted 0241bc1f Diff 29K/4327 BC5 0 Thu Jul 25 19:59:20 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:20.351] sensors: 5/0 temperature read failed, using previous Thu Jul 25 19:59:20 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:20.351] sensors: 5/0 temperature (0.0,0.0) Thu Jul 25 19:59:21 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:21.020] sensors: 6/0 temperature read failed, using previous Thu Jul 25 19:59:21 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:21.020] sensors: 6/0 temperature (0.0,0.0) Thu Jul 25 19:59:21 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:21.127] Version submitting share mask 0x00800000 with work version 0x20800000 and pool version 0x20000000 Thu Jul 25 19:59:21 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:21.310] Accepted 0d27c29e Diff 4.98K/4327 BC5 0 Thu Jul 25 19:59:24 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:24.932] sensors: 7/0 temperature read failed, using previous Thu Jul 25 19:59:24 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:24.932] sensors: 7/0 temperature (0.0,0.0) Thu Jul 25 19:59:24 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:24.933] sensors: no working sensors Thu Jul 25 19:59:33 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:33.471] Version submitting share mask 0x00000000 with work version 0x20000000 and pool version 0x20000000 Thu Jul 25 19:59:33 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:33.557] Accepted 020c7705 Diff 32K/4327 BC5 0 Thu Jul 25 19:59:33 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:33.765] sensors: 5/0 temperature read failed, using previous Thu Jul 25 19:59:33 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:33.765] sensors: 5/0 temperature (0.0,0.0) Thu Jul 25 19:59:34 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:34.432] sensors: 6/0 temperature read failed, using previous Thu Jul 25 19:59:34 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:34.432] sensors: 6/0 temperature (0.0,0.0) Thu Jul 25 19:59:38 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:38.344] sensors: 7/0 temperature read failed, using previous Thu Jul 25 19:59:38 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:38.344] sensors: 7/0 temperature (0.0,0.0) Thu Jul 25 19:59:38 2019 daemon.err cgminer[6079]: [2019-07-25 19:59:38.345] sensors: no working sensors Braiin OS seems very powerful firmware but missing temperatures sensors is very dangerous. So i tried to install 201711171757 bitmain firmware from official page with no luck
|
|
|
|
Artemis3
Legendary
Offline
Activity: 2030
Merit: 1573
CLEAN non GPL infringing code made in Rust lang
|
|
July 29, 2019, 01:31:20 PM |
|
OK Braiin OS installed to NAND. ( Using 16GB card, with 8GB there was an error "firmware.tar.gz" is missing ) Seems that the missing hashboard appeared and hashing.
However in Braiin OS there is no temperature measurement!
...
Braiin OS seems very powerful firmware but missing temperatures sensors is very dangerous.
So i tried to install 201711171757 bitmain firmware from official page with no luck Well you can also manually control the fan speeds. If you know it never got to dangerous temperatures with factory, it won't with Braiins OS unless you overclock it. It seems to be unable to detect the sensors but that's not so strange as you may think. It would be fine if you could get temperatures from one of the boards, then put that in the middle (which is the worst position). You can try factory from 2017 and 2018 if you think it makes a difference. But yes, factory loves to disable a board when it can't read its sensors, something bOS can override as you did see. Sensors failing but hash chips actually ok is not rare. If you are somehow still scared with bOS go the other route: Downclock. Something resembling 8.1v 500mhz does wonders. You could try 8.5v 600mhz or so, just make sure actual and ideal clock speed match or are very close, then keep lowering that voltage and when the values differ too much go back to the previous value. Downclocking is never dangerous, chips run cooler. And don't mind the suggested values, lower those voltages always until you find the sweet spot. I mean a downclocked board is better than no board, but its your choice...
|
█████████████████████████ ██████████████████████████ ██████████████████████████ ███████████████████████████ | 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 | |
|
|
|
maxmad
Jr. Member
Offline
Activity: 55
Merit: 3
|
|
July 29, 2019, 06:30:03 PM Last edit: July 30, 2019, 10:45:23 AM by frodocooper Merited by frodocooper (2) |
|
This is a good thought. However, if something will block the airflow, ie dust or even a fan failure, this will be catastrophic. The strange part is that bOS detects the sensors: Mon Jul 29 15:17:37 2019 daemon.err cgminer[6644]: [2019-07-29 15:17:37.036] AUTOMATIC fan control, target temperature 75 degrees (hot is 90 deg, dangerous is 95 deg) Mon Jul 29 15:17:37 2019 daemon.err cgminer[6644]: [2019-07-29 15:17:37.348] chain 5: found sensor TMP451 at chip_addr=f4, i2c_addr=98 Mon Jul 29 15:17:38 2019 daemon.err cgminer[6644]: [2019-07-29 15:17:38.853] chain 6: found sensor TMP451 at chip_addr=f4, i2c_addr=98 Mon Jul 29 15:17:40 2019 daemon.err cgminer[6644]: [2019-07-29 15:17:40.358] chain 7: found sensor TMP451 at chip_addr=f4, i2c_addr=98 Mon Jul 29 15:17:46 2019 daemon.err cgminer[6644]: [2019-07-29 15:17:46.153] set_pic_voltage: chain 5: setting voltage 8.70V (PIC=125) Mon Jul 29 15:17:47 2019 daemon.err cgminer[6644]: [2019-07-29 15:17:47.311] set_pic_voltage: chain 6: setting voltage 8.90V (PIC=91) Mon Jul 29 15:17:48 2019 daemon.err cgminer[6644]: [2019-07-29 15:17:48.469] set_pic_voltage: chain 7: setting voltage 8.90V (PIC=91) Mon Jul 29 15:17:48 2019 daemon.err cgminer[6644]: [2019-07-29 15:17:48.588] Probing for an alive pool Mon Jul 29 15:17:49 2019 daemon.err cgminer[6644]: [2019-07-29 15:17:49.188] Pool 0 difficulty changed to 8192 Mon Jul 29 15:17:49 2019 daemon.err cgminer[6644]: [2019-07-29 15:17:49.195] Pool 1 difficulty changed to 8192 Mon Jul 29 15:17:49 2019 daemon.err cgminer[6644]: [2019-07-29 15:17:49.535] Rejected untracked stratum share from pool 0 Mon Jul 29 15:17:49 2019 daemon.err cgminer[6644]: [2019-07-29 15:17:49.589] Network diff set to 9.01T Mon Jul 29 15:17:53 2019 daemon.err cgminer[6644]: [2019-07-29 15:17:53.758] sensors: 5/0 temperature read failed, using previous Mon Jul 29 15:17:53 2019 daemon.err cgminer[6644]: [2019-07-29 15:17:53.758] sensors: 5/0 temperature (0.0,0.0) Mon Jul 29 15:17:54 2019 daemon.err cgminer[6644]: [2019-07-29 15:17:54.424] sensors: 6/0 temperature read failed, using previous Mon Jul 29 15:17:54 2019 daemon.err cgminer[6644]: [2019-07-29 15:17:54.425] sensors: 6/0 temperature (0.0,0.0) Mon Jul 29 15:17:54 2019 daemon.err cgminer[6644]: [2019-07-29 15:17:54.590] API running in IP access mode on port 4028 (5) Mon Jul 29 15:17:54 2019 daemon.info cgminer_monitor.lua[1531]: state sick because low hashrate Mon Jul 29 15:17:54 2019 daemon.info cgminer_monitor.lua[1531]: /sys/class/leds/Red LED mode blink-slow Mon Jul 29 15:17:54 2019 daemon.info cgminer_monitor.lua[1531]: /sys/class/leds/Green LED mode off Mon Jul 29 15:17:55 2019 daemon.err cgminer[6644]: [2019-07-29 15:17:55.090] sensors: 7/0 temperature read failed, using previous
To bypass the error while trying to flash to factory, i used the SD recovery method. This time the flash was successful to NAND and S9 boot to factory OS. Then i installed the 201711171757 and all three boards were working again! Seems that 201711171757 is really a saver. I tested to flash to latest 2018 firmware 201812051512 with success and all boards properly worked. Including of temp sensors!
|
|
|
|
Artemis3
Legendary
Offline
Activity: 2030
Merit: 1573
CLEAN non GPL infringing code made in Rust lang
|
|
July 30, 2019, 01:38:40 AM Last edit: July 31, 2019, 02:16:45 AM by Artemis3 |
|
To bypass the error while trying to flash to factory, i used the SD recovery method. This time the flash was successful to NAND and S9 boot to factory OS.
Then i installed the 201711171757 and all three boards were working again! Seems that 201711171757 is really a saver.
I tested to flash to latest 2018 firmware 201812051512 with success and all boards properly worked. Including of temp sensors! I suggest you stay there then, that's asicboost enabled while still not locking you out of your miner.
|
█████████████████████████ ██████████████████████████ ██████████████████████████ ███████████████████████████ | 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 | |
|
|
|
AlecMe
|
|
September 19, 2019, 08:22:43 AM |
|
Hi all,
Anyone knows what could be the problem that can cause this:
"Chain[5] Chip[62] junction temperature=136"
Everything else at the end of the log seem to look ok:
"Done check_asic_reg Chain[5] Chip[244] pcb temperature=62 Chain[5] Chip[62] junction temperature=136 Special fix Chain[5] Chip[62] middle Temp = 77 Done read temp on Chain[5] Chain[6] Chip[244] pcb temperature=65 Chain[6] Chip[62] junction temperature=71 Special fix Chain[6] Chip[62] middle Temp = 80 Done read temp on Chain[6] Chain[7] Chip[244] pcb temperature=62 Chain[7] Chip[62] junction temperature=66 Special fix Chain[7] Chip[62] middle Temp = 77 Done read temp on Chain[7] Max pcb temp : 65 Set fixed fan speed=80 FAN PWM: 80 read_temp_func Done! CRC error counter=0"
|
|
|
|
mettalmag
Legendary
Offline
Activity: 1084
Merit: 1003
≡v≡
|
|
October 16, 2019, 09:31:06 PM |
|
4 out of 35 machines are at 0 hashrate I have no physical access right now but I will try that method and also thinking to try third party OS maybe
|
|
|
|
|