12th Gen Intel Core BIOS 3.08 Beta Release

@Matt_Hartley Thank you so much for your candid reply. It really does mean a lot.

Looking forward to you guys crushing this release, in due time :slight_smile:

6 Likes

Just wanted to report a success with the 3.08 Beta EFI upgrade on my 13 inch Intel.

I’m well aware that it has been removed for the moment, however, I have had a 61kWh battery waiting to be installed for months now so I really did want to do the update to enable full support for that, and took the risk.

Nothing unusual - disabled secure UEFI boot in existing BIOS; booted from USB-A stick formatted FAT with the update unzipped to it; watched and waited while it went through all the steps; booted back into Fedora 39; restarted to re-enable secure UEFI boot.

1 Like

I’m likely going to be doing the same thing. I have a 61Wh battery coming and only have Fedora 39 installed. Don’t want to reformat to install windows.

Worst comes to worst, I remove the SSD as others have said they have been doing

2 Likes

I installed this today via EFI method and got the line 97 error. I had the power plugged in on the same side as my flashdrive when I got the error.

Moving power to the opposite side and rebooting fixed the issue for me. I did not have to remove my SSD.

3 Likes

You might want to check your download here. I just downloaded the file (for clarity, it’s still on the servers but Framework say you shouldn’t use it) again which shows up with a SHA1 of 317771e616be990ff3c54b24f9864d41dbea8d23, this also matches the file I downloaded Jan 11 2024 (my post in this thread) which I still have.

For posterity, the SHA256 of the file is:

ddb2ef62f589e5c972d577e2e44b6ac2d7d040767189dfb4bcd04aa5d93751e6 *Framework_Laptop_12th_Gen_Intel_Core_3.08_EFI.zip
3 Likes

Upgrading using the EFI on USB-Stick method worked fine for me. SHA256SUM ddb2ef62f589e5c972d577e2e44b6ac2d7d040767189dfb4bcd04aa5d93751e6

  • FAILURE SKU# and SYS SERIAL NUMBER: FRANMACPA4231200S9
  • SYS CONFIG: i5-1240P
  • RAM: 2 Sticks of Crucial 16GB
  • SSD: WD Black SN770 1TB
  • Wi-Fi: Intel AX10NGW (stock).
  • External Devices/Other: USB-C Hub (Charger, LAN, Display, Display USB-Hub with keyboard and mouse)
  • EXPANSION CARD TYPES: On both sides: 1 USB-C (back), 1 USB-A (front)
  • BIOS VERSION: 3.06
  • DRIVER PACKAGE VERSION: -
  • OS VERSION: Arch, fully updated
  • FAIL RATIO: 0%. Worked on first try
  • STEP TO REPRODUCE: EFI Shell via USB drive
  • OBSERVED RESULT: Worked
  • EXTERNAL DEVICE MODE or NAME: For USB flash drives, Generic or the brand.
3 Likes

I confirm those hashes!
sha256: ddb2ef62f589e5c972d577e2e44b6ac2d7d040767189dfb4bcd04aa5d93751e6

3 Likes

The link to 3.08b above resolved “The Installer can only be un on Framework Laptop 12 Gen Intel Mainboards”. I had a Batch 2 1280p board on 3.06 Beta. Now 3.08 Beta.

2 Likes

Update to 3.0.8 (via Windows 10) was successful.

However, now with Linux, entering “deep” suspend (in the /sys/power/mem_sleep sense) consistently soft bricks the device. Once in this state, a mainboard reset is required.

If you use Linux, I would steer clear of 3.0.8 until this is resolved.

3 Likes

Strange. I updated a few weeks ago, but I don’t see that issue. Using deep sleep (not s2idle), Debian testing, kernel 6.6.13. No problems with sleep here.

1 Like

Interesting! It repros consistently for me with the Fedora-Workstation-Live-x86_64-39-1.5.iso (without installing; running off a USB stick). I was triggering deep suspend with something like:

# Do not run the following commands.
echo deep > /sys/power/mem_sleep
echo mem /sys/power/state

I’ve got a case open and have been discussing with the support team.

2 Likes

I have the opposite problem. On Debian with BIOS 3.05 and 3.08, the laptop would sometimes never come out of s2idle (I’d have to power the machine off with a 10-second power button press). The “deep” suspend has consistently worked.

2 Likes

Batch 1 , i7-1260p. Experiencing disconnects with a thunderbolt 3 Egpu. Running the 3.08b release.

2 Likes

Hi there. The BIOS seems pretty tested now.
Any information on a release candidat ?

6 Likes