Thank you for writing this and having patience with us users. I wish you, the devs and support the time and energy to continue. Im ofcourse looking forward to news, updates and especially a relatively stable bios update.
Have a wonderful day, you all.
Just a note that we are in release preparation for the next BIOS release at the moment for 11th Gen. We do have the Windows version of the next Beta release currently, but weâve been delayed on preparing the Linux version of it. Our goal is to always be able to release Windows and Linux versions simultaneously.
Starting with this release and going forward, we are revamping our BIOS release process overall. Our mission is focused on product longevity, and ongoing software support is a key part of that.
Weâll be sharing more detail on this, but some of the changes will include:
- When we launch a Beta, weâll be sharing the target schedule for promotion from Beta to final release. Our default schedule will be two weeks. If we see feedback from the community around new regressions or other issues with the release, weâll determine whether we need additional time in Beta or a follow on release before final. In each case, weâll make sure to communicate any schedule changes.
- Weâre working with our upstream suppliers on getting dedicated staffing into place for sustaining software development. This means weâll be able to resolve some of the delays weâve had thus far in timely BIOS releases. Note that with this, weâll have dedicated support in place within Framework, with the upstream supplier to us (Compal), and the upstream supplier to them (Insyde). However, there will still be suppliers further upstream of that (e.g. Intel or other silicon vendors) that we have less visibility or control over.
@nrp This is greatly appreciated. Lack of timeliness in communication has become my no.1 gripe with your product but hearing that you guys are restructuring your release process gives me hope here. Thank you.
I am most gratified to read this in particular
As it was beginning to feel like Framework was pivoting to new product release after new product release and leaving the rest of us behind (to me). So thank you again.
I love that youâre still supporting us 11th Gen folks. Much appreciated!
I am trying to update to 3.17 but having some issues going the USB route. Is LVFS preferable?
I downloaded the zip file and moved the extracted file to a USB (exFAT) but when I reboot (with secure boot disabled) and go into choose the device I want to boot from the USB is not listed.
I strongly suspect the issue is exFAT. Try it on a thumb drive formatted with plain FAT32.
11th Gen Intel Core BIOS 3.19 is ready for BETA release. But first, some background.
-
Weâve been delayed on BIOS updates due to issues we found in the update process, especially on Linux, and due to staffing constraints at our ODM partner. Weâre working with them to enable more consistent staffing for sustaining work on launched programs. Note that there is a matching firmware update in progress for 12th Gen Intel Core, and the release schedule has been slow due to these issues.
-
On general philosophy is to have complete firmware out of the box when we launch a product. In general, we donât plan to have new features that we add post-launch. Instead, post-launch updates are for issues that are found in the field or for security updates that we receive from our upstream firmware suppliers, which include the silicon vendor like Intel or AMD along with our BIOS supplier, Insyde.
-
Our target timeline to go from Beta launch in the community to final release is two weeks. We monitor the community thread to find if there are regressions in the release that would prevent promotion to final. Note that while both we and our ODM partner do testing on the release prior to the Beta, there is still the potential for issues we didnât catch, so we recommend only using Beta firmware if you are comfortable with that risk.
Note that because this is a Beta release.
We recommend only updating to it if you are comfortable with the risk of there being stability or functionality regressions. Our general Beta testing plan is to stay in the Beta period for two weeks and monitor feedback around any issues. If there are no substantial new issues found, we will then promote the release to final.
You can check your current BIOS version following the steps here to determine if you are on the latest release.
Downloads
Windows
https://downloads.frame.work/bios/Framework_Laptop_11th_Gen_Intel_Core_BIOS_3.19.exe
Instructions for Windows Installer:
- Run the .exe.
- If prompted to trust the Framework driver signature, click agree.
- Click yes to reboot.
- Wait for all 3 firmware progress bars to complete as the installer will install 3 different firmware updates and will then reboot into Windows.
Linux/Other/UEFI Shell update
In order to avoid delaying Beta testing further, weâre releasing the Windows updater first. We do intend to have an UEFI Shell based updater available for those on Linux or other OSâs.
Linux/LVFS
There will not be an LVFS update for this specific release because it has an Intel CSME update, which canât be delivered through LVFS. Use the UEFI Shell update method instead for this release.
Enhancements
- Update Intel CSME package to 5.0.42.2235v2 Corporate.
- Move to shared EC branch with 11th, 12th, 13th gen.
Fixes
- Insyde security patch to fix CVE-2017-5715.
- Fix SMBIOS type2 location on chassis string6.
- Add ACPI mutex in UCSI mailbox with EC to avoid race condition with other ec communication.
- Fixed LED blink green when EC power on.
- Fixed cannot power on EC chip.
- Reduce charger input current limit to 0 when switching between type-c port in a multiple adapter scenario.
Component Versions
This BIOS update is a bundle of updates to multiple embedded components in the system.
Not all of them use the same version number.
BIOS | 3.19 | Updated |
---|---|---|
EC | f6d6b92 | Updated |
PD | 3.4.0.2575 | Same as previous version |
Intel CSME | 15.0.42.2235 | Updated |
Known Issues
Vulnerabilities
IhisiServicesSmm | BRLY-SA-2023023/CVE-2023-22613 | |
---|---|---|
BdsDxe | BRLY-2022-021/CVE-2022-35897 | |
SetupUtility | BRLY-2022-020/CVE-2022-35407 | |
PiSmmCpuDxeSmm | BRLY-2022-028-RsbStuffing | |
IhisiServicesSmm | BRLY-SA-2023021/CVE-2023-22615 |
Big takeaway, please test, report back on this thread and @ me here so I can track anything you experience needing attention.
Thanks
Just tried it but to no avail.
Tried the LVFS route but I donât see uefi_capsule.conf in the /etc/fwupd/ unless I was supposed to create a new file. There is a file called fwupd.conf but it doesnât have a line with DisableCapsuleUpdateOnDisk.
Just a reminder ^^
Will they be fixed in the stable release or will there be another beta release to fix those?
Not going to speak for the firmware team specifically, however, if these are to be addressed in a release, I will share details when I have them.
@Matt_Hartley I am having an issue updating to 3.17.
I tried to update via UEFI but my usb is not listed as among the options to boot into. I also tried the LVFS route but got stuck on the edit uefi_capsule.conf file in the /etc/fwupd/ directory. There was no such file except one called fwupd.conf but it doesnât have a line with DisableCapsuleUpdateOnDisk.
Misread previously, 3.17 - understood.
What is the output of:
cat /etc/fwupd/uefi_capsule.conf | grep "DisableCapsuleUpdateOnDisk="
This assumes Ubuntu or Fedora, of course. Any distro based on one of these should be the same.
Generally speaking, this should get you going:
Great to hear! Does this firmware introduce compatibility with the 61Wh battery?
Need to do a check with the community - anyone that updated 11th Gen Intel Core BIOS 3.19 Beta Release to this seeing issues at all?
If so, please list them as follows:
-
Updating from which previous BIOS release? _______
-
How did the update go, any issues experienced? _________
-
Any bugs experienced (not feature requests, bugs)? _____________
@Matt_Hartley Is there an ETA for the UEFI and/or LVFS for 3.19?
Have not updated since I donât have WindowsâŚ
Not at the moment, but, I am also a full time Linux user. So, the second I get the word, it will appear here.