# 11th Gen Intel Core BIOS 3.20 Release and Driver Bundle Update

**URL:** <https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613>\
**Category:** Framework Laptop 13\
**Tags:** bios-announcement\
**Created:** [June 25, 2024, 11:42pm UTC](https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613 "2024-06-25T23:42:41Z")\
**Posts on this page:** 20\
**Page:** 4

<div class="post-metadata">

**Author:** ![dimitris](https://avatars.discourse-cdn.com/v4/letter/d/db5fbb/32.png) [@dimitris](https://community.frame.work/u/dimitris)\
**Post date:** [July 14, 2024, 8:35pm UTC](https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613/75 "2024-07-14T20:35:27Z")

</div>

@anon81945988 @Usernames the BIOS update clears the boot wait timeout to zero, along with the battery charge limit. F2 is still possible but you have to be “aggressive” pressing it frequently even before the FW logo appears. Once you manage to get into the BIOS screen(s) (might take a few attempts) you can change that timeout (plus, if applicable, battery charge limit and secure boot enforcement) to make things easier going forward. I’ve made a habit of setting it to 3 seconds.

---

<div class="post-metadata">

**Author:** ![Stefan\_Konig](https://avatars.discourse-cdn.com/v4/letter/s/439d5e/32.png) [@Stefan\_Konig](https://community.frame.work/u/Stefan_Konig)\
**Post date:** [July 15, 2024, 7:03am UTC](https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613/77 "2024-07-15T07:03:29Z")

</div>

@anon81945988, thank you so much! Following the guide at [Fully Resetting the Mainboard State - Framework Guides](https://guides.frame.work/Guide/Fully+Resetting+the+Mainboard+State/113) fixed it. So the firmware upgrade was just a coincidence. Thanks!

---

<div class="post-metadata">

**Author:** ![Dave\_Olson](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/dave_olson/32/5356_2.png) [@Dave\_Olson](https://community.frame.work/u/Dave_Olson)\
**Post date:** [July 15, 2024, 5:47pm UTC](https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613/79 "2024-07-15T17:47:36Z")

</div>

If you can’t boot into the BIOS using F2 and you’re using Ubuntu, you can reboot into the BIOS using the terminal by entering: sudo systemctl reboot --firmware-setup

---

<div class="post-metadata">

**Author:** ![Second\_Coming](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/second_coming/32/29330_2.png) [@Second\_Coming](https://community.frame.work/u/Second_Coming)\
**Post date:** [July 15, 2024, 11:39pm UTC](https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613/81 "2024-07-15T23:39:23Z")

</div>

> [@anon81945988](#):
>
> Hi have just noticed this when waking from sleep but not when using from boot.
> 
> Ubuntu 24.04 \> Closed lid \> Opened a couple of hours or so later and battery indicator flashing between charging and not. LED white
> 
> Edit: It seems it may only happen after a prolonged ‘sleep’ my last single hour didn’t provoke it ??

Yeah, can’t say I know what’s happening…but there’s some flakiness somewhere, that IMO, has room for improvement.

---

<div class="post-metadata">

**Author:** ![letscho](https://avatars.discourse-cdn.com/v4/letter/l/58956e/32.png) [@letscho](https://community.frame.work/u/letscho)\
**Post date:** [July 15, 2024, 8:24pm UTC](https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613/82 "2024-07-15T20:24:42Z")

</div>

I updated to BIOS 3.20 from 3.19 of 11th Gen and everything looked fine. Directly after the update I could boot into Arch Linux (which worked fine for months) and then I put it to sleep.

However, when I wanted to use it the next day it was not booting anymore, it does not even go into the BIOS, the screen is black.  
The power light is shining and the side LED is green sometimes. Then the laptop turns itself on and off repeatedly with blank screen.

After following the guide [Fully Resetting the Mainboard State - Framework Guides](https://guides.frame.work/Guide/Fully+Resetting+the+Mainboard+State/113) to reset the mainboard I was able to boot again, but after 10s it turned itself off again into the cycle described above.

Any ideas what could be the issue here? I asked already for a replacement RTC battery.

---

<div class="post-metadata">

**Author:** ![Rupert\_Woods](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/rupert_woods/32/2193_2.png) [@Rupert\_Woods](https://community.frame.work/u/Rupert_Woods)\
**Post date:** [July 16, 2024, 3:07pm UTC](https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613/84 "2024-07-16T15:07:09Z")

</div>

If you think it’s the RTC battery, contact Framework Support, they replaced my RTC Battery, free of charge out of warranty.

---

<div class="post-metadata">

**Author:** ![Joghurt](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/joghurt/32/27795_2.png) [@Joghurt](https://community.frame.work/u/Joghurt)\
**Post date:** [July 16, 2024, 11:38pm UTC](https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613/85 "2024-07-16T23:38:49Z")

</div>

Various posts in this forum recommend “mem\_sleep\_default=deep” for increased battery life on the 11th Gen Framework. I also used this setting for years now without problems.

But after updating my BIOS from 3.17 to 3.20, I thought I had bricked my laptop. After putting it to sleep, it would only turn on the fan on high speed, the display would stay black (backlight didn’t turn on), and after 15s or so, would turn off again, only to turn back on after 5s and repeating this forever. Turning it off manually by holding the power button would not help. While it would stay off, the next time I tried to power it on, the same effect happened without me ever being able to boot.

The only way to fix it is resetting the mainboard state by removing the battery and the CMOS battery. The laptop will then show the same effect once (15s high fan speed without backlight), but after turning itself off it will then boot up normally. Phew!

Through trail-and-error I managed to find that this would always happen whenever “mem\_sleep\_default=deep” is in the kernel command line, and never without. “sleep=deep” alone does not cause the issue.

---

<div class="post-metadata">

**Author:** ![letscho](https://avatars.discourse-cdn.com/v4/letter/l/58956e/32.png) [@letscho](https://community.frame.work/u/letscho)\
**Post date:** [July 20, 2024, 9:36pm UTC](https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613/86 "2024-07-20T21:36:05Z")

</div>

Thank you so much for pinning down the issue on the sleep mode!

I have exactly the same problem as you described. Now with s2idle sleep it works fine.  
Which distro are you using?  
Did you already create a bug report for this issue?

I changed the CMOS battery, but had the same issues.

---

<div class="post-metadata">

**Author:** ![Joghurt](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/joghurt/32/27795_2.png) [@Joghurt](https://community.frame.work/u/Joghurt)\
**Post date:** [July 20, 2024, 10:18pm UTC](https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613/87 "2024-07-20T22:18:29Z")

</div>

> Which distro are you using?

Debian Testing, but I don’t think it matters, the problem seems to lie on the firmware level, not the kernel

> Did you already create a bug report for this issue?

No, I’m not actually sure how to do that. I was assuming Framework monitors this thread (they moved my initial report to this one), and are aware of this issue. I might be wrong though, where can I file a bug report? Just sending a message to support?

---

<div class="post-metadata">

**Author:** ![Alan\_Martin](https://avatars.discourse-cdn.com/v4/letter/a/0ea827/32.png) [@Alan\_Martin](https://community.frame.work/u/Alan_Martin)\
**Post date:** [July 22, 2024, 9:21pm UTC](https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613/88 "2024-07-22T21:21:15Z")

</div>

Regarding “Please Note: After updating to 3.20, you will not be able to downgrade to an earlier version.”

Why this restriction? It seems to go against Framework’s philosophy of giving choice & control to the user, and it takes away a useful troubleshooting/recovery option for those who have issues.

---

<div class="post-metadata">

**Author:** ![Kieran\_Levin](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/kieran_levin/32/110_2.png) [@Kieran\_Levin](https://community.frame.work/u/Kieran_Levin)\
**Post date:** [July 22, 2024, 11:20pm UTC](https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613/90 "2024-07-22T23:20:27Z")

</div>

Thanks for the report! We will update our release notes.  
As a note S3 is not officially supported by intel on 11th Gen and beyond.

---

<div class="post-metadata">

**Author:** ![Alan\_Martin](https://avatars.discourse-cdn.com/v4/letter/a/0ea827/32.png) [@Alan\_Martin](https://community.frame.work/u/Alan_Martin)\
**Post date:** [July 22, 2024, 11:58pm UTC](https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613/91 "2024-07-22T23:58:16Z")

</div>

Yes, I am concerned about doing an update and something going wrong and not being able to undo.

I also think that Framework should say _why_ downgrades are blocked, and not just warn that they are.

---

<div class="post-metadata">

**Author:** ![Phillip\_Elvey](https://avatars.discourse-cdn.com/v4/letter/p/87869e/32.png) [@Phillip\_Elvey](https://community.frame.work/u/Phillip_Elvey)\
**Post date:** [July 23, 2024, 8:35am UTC](https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613/93 "2024-07-23T08:35:49Z")

</div>

Hi all, having a, “Am I being really stupid?” moment…

Got the notification that BIOS version 3.20 is available for my machine - hooray!

I’m running Ubuntu 24.04, so going to use the EFI updater.  
I download the file from this link here:  
[https://downloads.frame.work/bios/Framework\_Laptop\_13\_11th\_Gen\_Intel\_Core\_BIOS\_3.20\_EFI.zip](https://downloads.frame.work/bios/Framework_Laptop_13_11th_Gen_Intel_Core_BIOS_3.20_EFI.zip)  
extract it a USB pen drive,  
Reboot, disable Secure Boot  
Reboot and boot from USB drive.

At first, shows updating correctly - hooray!  
I reboot again after the update, and then go in to the BIOS to re-enable Secure Boot  
I notice that the BIOS shows version is still/only 3.17 (now due to this situation I’m not sure what version it was previously…)

VERY STRANGE…

So I go back to the webpage, download the file again to be 200% sure I’m getting the right file, repeat the process all over again, except this time it will not update, saying “Cannot update to the same version as already installed”

But after I boot back into Ubuntu and check the BIOS version again, it is still showing 3.17 !!!

Anyone else had this issue?  
Is it possible that a mistake has been made with packaging the wrong firmware file into the EFI ZIP package??

Here is the output of dmidecode:

> Vendor: INSYDE Corp.  
> Version: 03.17  
> Release Date: 10/27/2022  
> Address: 0xE0000  
> product: 11th Gen Intel(R) Core™ i7-1165G7 @ 2.80GHz  
> vendor: Intel Corp.  
> physical id: 4  
> bus info: cpu@0  
> version: 6.140.1

Thoughts…?

---

<div class="post-metadata">

**Author:** ![Destroya](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/destroya/32/47793_2.png) [@Destroya](https://community.frame.work/u/Destroya)\
**Post date:** [July 23, 2024, 9:49pm UTC](https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613/94 "2024-07-23T21:49:42Z")

</div>

Can you try upgrading to 3.19 first to see if you are having the same issue?

---

<div class="post-metadata">

**Author:** ![Second\_Coming](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/second_coming/32/29330_2.png) [@Second\_Coming](https://community.frame.work/u/Second_Coming)\
**Post date:** [July 23, 2024, 10:47pm UTC](https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613/95 "2024-07-23T22:47:42Z")

</div>

> [@Phillip\_Elvey](#):
>
> Cannot update to the same version as already installed”

Check this…and the next few messages after that. It’s a ‘seen’/known issue that somehow still exist:

> [@11th Gen Intel Core BIOS 3.20 Release and Driver Bundle Update](http://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613/33):
>
> I just tried to update to 3.19, but get exactly the same behavior. Meanwhile, I was reviewing [Getting started guide with a bare motherboard](http://community.frame.work/t/getting-started-guide-with-a-bare-motherboard/20115) and suspect this has to do with the (lack of a) battery. I know the rtc is good, because the mainboard keeps time properly between shutdowns. I just found the error.log on the boot USB, which says Error 331: Full FW Update using same version is not allowed. Include -allowsv in command line to allow it. I opened startup.nsh and appended the “-allowsv” fl…

---

<div class="post-metadata">

**Author:** ![Phillip\_Elvey](https://avatars.discourse-cdn.com/v4/letter/p/87869e/32.png) [@Phillip\_Elvey](https://community.frame.work/u/Phillip_Elvey)\
**Post date:** [July 24, 2024, 8:20am UTC](https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613/96 "2024-07-24T08:20:10Z")

</div>

Evening again,  
Cracked it! Reading the posts you linked @Second_Coming, especially about updating the bare motherboard configs, made me think “I wonder if I need to have the power connected?” Apologies if I’ve just plain missed this in the main instructions, but I don’t remember reading it. Anyhow, yesterday I was trying without AC power connected. Today I tried with AC power connected, and also on the LH side of the laptop (usually I have it on the right) - this was from a comment made on the bare motherboard thread which stated the AC needs to be connected on the LH side…  
When I did this, I tried to execute the update from the USB again - it told me once again that it couldn’t update to the same version, HOWEVER, when it re-booted it on the initial splash screen it showed the green progress bar which I didn’t get previously, and took 5-10 mins to complete the update. Then when finally booted up again, now shows BIOS version 3.20.  
Apologies for changing 2 variables in one try, but it was either having the AC power connected, or having it connected AND on the LH side of the laptop.

---

<div class="post-metadata">

**Author:** ![Phillip\_Elvey](https://avatars.discourse-cdn.com/v4/letter/p/87869e/32.png) [@Phillip\_Elvey](https://community.frame.work/u/Phillip_Elvey)\
**Post date:** [July 24, 2024, 8:08pm UTC](https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613/98 "2024-07-24T20:08:20Z")

</div>

@anon81945988 I’m not using the Windows update so I didn’t read those instructions. I’m using Ubuntu so only read the section on the EFI updater. I re-read those this morning, and there isn’t a mention of any need to have AC power connected - perhaps that should be added @Destroya ?

---

<div class="post-metadata">

**Author:** ![Ashley\_Herman](https://avatars.discourse-cdn.com/v4/letter/a/ce7236/32.png) [@Ashley\_Herman](https://community.frame.work/u/Ashley_Herman)\
**Post date:** [July 25, 2024, 5:24am UTC](https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613/99 "2024-07-25T05:24:16Z")

</div>

Hi! I’m finally updating my BIOS to the latest version but getting an error. Here’s what I’m doing:

1. I downloaded the files [here] ([Framework Laptop BIOS and Driver Releases (11th Gen Intel® Core™)](https://knowledgebase.frame.work/framework-laptop-bios-releases-S1dMQt6F)) to a USB then unmount and reboot from the USB by pressing F12. I select the USB option from the menu.
2. It starts to run the setup script but very quickly crashes with this message: “Security issue on line 1” …(or 11 - can’t recall).
3. I type “exit” to get out of the terminal and reboot my machine and go to the internet for help.

Anyone else experiencing this issue?

Another possibly relevant information: I recently updated from Ubuntu 22-\>24 and found that I was having issues with my WiFi no longer working, which is what prompted me to get around to installing framework updates because I was thinking there may be an issue with my driver. I’m doing this all on ethernet.

Please help!!

---

<div class="post-metadata">

**Author:** ![pierce](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/pierce/32/18894_2.png) [@pierce](https://community.frame.work/u/pierce)\
**Post date:** [July 25, 2024, 7:19pm UTC](https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613/101 "2024-07-25T19:19:34Z")

</div>

> [@Ashley\_Herman](#):
>
> crashes with this message: “Security issue on line

It looks like you have Secure Boot enabled; it must be disabled for the EFI updater to work. (This was mentioned in instructions for previous updates, for example 3.17, not sure why it was not mentioned in the latest instructions.)

---

<div class="post-metadata">

**Author:** ![name\_of\_user](https://avatars.discourse-cdn.com/v4/letter/n/c4cdca/32.png) [@name\_of\_user](https://community.frame.work/u/name_of_user)\
**Post date:** [July 26, 2024, 9:38pm UTC](https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613/102 "2024-07-26T21:38:52Z")

</div>

I noticed that the battery icon is showing a lightning bolt but is “using battery power” when I moused over it. UPower status shows “pending-charge”:

native-path: BAT1  
vendor: NVT  
model: Framewo  
serial: 0177  
power supply: yes  
updated: Fri 26 Jul 2024 10:26:29 PM (6 seconds ago)  
has history: yes  
has statistics: yes  
battery  
present: yes  
rechargeable: yes  
state: pending-charge  
warning-level: none  
energy: 53.0222 Wh  
energy-empty: 0 Wh  
energy-full: 53.0376 Wh  
energy-full-design: 55.0088 Wh  
energy-rate: 0 W  
voltage: 17.517 V  
charge-cycles: 13  
percentage: 99%  
capacity: 96.4166%  
technology: lithium-ion  
icon-name: ‘battery-full-charging-symbolic’  
History (rate):  
1722029189 0.000 pending-charge

Had been having many problems since new (11th Gen Intel) with battery not charging, CMOS battery dying, and not powering on unless the main battery is disconnected, even needed to replace the main battery on support’s recommendation (but problems remained).

I updated BIOS from 3.06 to 3.17, then 3.20 today and all seemed normal until I check battery status. Concerned that I may be repeating previous sagas with dead battery, not charging and not powering on with connected battery (making this a desktop).

Any advice would be appreciated.

[Previous page](https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613.md?page=3)

[Next page](https://community.frame.work/t/11th-gen-intel-core-bios-3-20-release-and-driver-bundle-update/53613.md?page=5)
