Standalone FW13 with intel 1135 has no display after BIOS update attempt

Hi,

I have just attempted an update from BIOS version 3.22 to version 3.24 on a standalone FW13 motherboard inside the Cooler Master case (hence, no battery), and now the system doesn’t power any of the USB peripherals, does not send any signal, ramps the fan to 100%, and, after a good minute or two, shuts itself down.

The exact steps I have followed (this just happened, I will be as factual and thorough as possible):

  • Enabled Standalone operation in the bios, cleared TPM, reset CA to factory, updated bios date (since it was in january of 2001, perhaps indicative of a BIOS battery issue?), disabled secure boot
  • Formatted a USB key to FAT32 from my desktop, before I decompressed the “BIOS 3.24 (EFI Shell update)” archive obtained from the knowledgebase
  • Plugged my devices in the following manner :
    • Power on the lower-left port (the charger is a 100W PD UGreen Nexode)
    • Display (HDMI framework expansion slot) on the upper-left port
    • USB key on the lower-right port
    • keyboard on upper-right port
  • Booted on the USB key from the F12 boot menu
  • Waited until the green progress bar with the framework logo completed
  • The system seemed to have rebooted, then had 100% fan speed, no power to the keyboard or even the USB key (its LED light remained completely off)
  • Waited for a while (hard to say how long, probably 8-10 minutes)
  • Tried to force shutdown by pressing then maintaining the power button
  • Device did not shut down
  • After an additional 5 minute, decided to unplug the system
  • Unplugged everything for more than 90 seconds (as instructed in the knowledgebase) before reattempting
  • Tried restarting with USB key and keyboard ports swapped
  • Tried restarting without the USB key plugged into the system

With the above all of the above done, symptoms remain the same:

  • No display signal
  • Fan ramp up to 100%
  • Keyboard does not light up as expected
  • After some time, the system shuts itself down

Additional informations :

  • I did not have a lithium ion battery connected to this system during the BIOS flash (I did not see the “This update requires a battery present to complete the update.” line in the documentation before attempting the BIOS update)
  • NVMe and RAM are known to be at the very least in a kinda working state since I have installed linux mint on this system without much issue
  • Outside of the initial green progress bar, I did not get any of the instruction screens talked about and screenshoted into the knowledgebase guide

What are your opinions? What can be done?

PS: See this post for my rant about the knowledgebase documentation :slight_smile:

Okay what the hell the thing just booted normally into linux now (BIOS 3.23)

Though I get the following LED CODE:
BRGGGGRRGGGGGRBGGBGBGG

If I understand this correctly, only the RGGGGRRGGGGG interests me, and it tells me that all is good but no battery/touchpad/audio-board is detected. Which would be what I expect to find :thinking:

Bro, what did you do to get it going again? Just let it sit there and discharge the mainboard battery or something? I just did the same BIOS update to 3.24 since 3.22 didn’t seem like it was taking the Secure Boot 2023 CA updates. No picture out but it powers on, gets past POST and sits there with the regular white light and the fan going for a while.

Hi, sorry I don’t check-in all that often.

So, if I remember correctly, the system got back to working fine for some time, and then it got back to a point where it would just have fan spin and that would be it.

What I ended up doing, was to swap my laptop’s 1165 board with the standalone 1135 board. Both boards now work flawlessly.

I think that 1135 board will never be able to work in standalone mode ever again, but it works flawlessly inside my FW13 chassis, so I’m happy with that arrangement.

PS: My standalone 1165 board sometimes seems to not post after a reboot (usually after an OPNsense update), I just unplug it and boot it back and I never have any real issues :person_shrugging:

Had a similar issue with the BIOS around v3.19? The UEFI script screws itself up for some reason in true Standalone mode and will start the update on the one side of the chipset but then just sit there with a black screen and never recover itself no matter what happens.

The only “fix” was tearing apart a Framework Laptop 13 temporarily installing the half flashed board the UEFI broke, booting the UEFI USB drive again (because the laptop screen was the only output that worked after the 1st BIOS update screwed itself up) and then it would finish the BIOS update.

Take the standalone board back out of the laptop, put the original laptop mainboard back in and then it would work as a standalone board just like before.

This sounds almost identical to what happened in this case and the fix was being lucky enough to have a laptop chassis to plug it into.

Yep, In my case, it happened when going from 3.22 to 3.24.

It is written way too late and nowhere near in-your-face enough that the mainboard must have an actual battery connected to it when updating BIOS. Display and power cables have to be put in very specific places for them to work properly during flashing, and they have to be put from one side to the next.

Reflecting on this, I think I’m okay with this quirk if it’s a first-gen-only issue, but I’m kinda pissed at the lack of visibility of this crucial information