You are all amazing!
Please keep them coming using this as your guide, success or fail.
Ok, hereās a repost using the template:
Just a note for Linux users: you can also get this at runtime by running the following commands:
sudo dmidecode --string system-sku-number
sudo dmidecode --string system-serial-number
sudo dmidecode --string processor-version
sudo dmidecode --type 17 # RAM information
And if you want to find the CSME version without rebooting into the BIOS, you can run mei-amt-check
(the example output in the README doesnāt show versions when AMT is not provisioned, but a later update to the repo makes the program show versions regardless).
Great stuff, and excellent point!
You are all amazing!
Please keep them coming using this as your guide, success or fail.
For a more āgraphicalā approach: if on KDE, processor and serial number are also available from āInfo Centerā/āAbout this systemā and CSME version from āFirmware Securityā.
As someone that bugged you guys in the 3.06 BIOS thread, now that it is finally released, I at least owe you a test :
FAILURE SKU# and SYS SERIAL NUMBER: FRANMACPA4238500WT
SYS CONFIG: i5 1240P
RAM: GSKILL 2x16GB 3200
SSD: Samsung 980 Pro 1TB
Wi-Fi: (stock) Intel AX210NGW
External Devices/Other: -
EXPANSION CARD TYPES: 1x USB-C
BIOS VERSION: 3.05
DRIVER PACKAGE VERSION: N/A
OS VERSION: Fedora 39
FAIL RATIO: 10%
STEP TO REPRODUCE: EFI Shell via USB drive
Step 1 - Flash USB drive as instructed
Step 2 - Disable secure boot, set battery limit back to 80%
Step 3 - Remove all expansion cards except 1
Step 4 - Plugin power to top left port
Step 5 - Boot to Flash tool, start flashing
Step 6 - Failure: Error Status: Invalid Parameter (line number 97)
Step 7 - Remove SSD
Step 8 - Plugin Power adapter directly into mainboard port on bottom left
Step 9 - Boot to Flash tool & successful flash
Step 10 - Install SSD and confirm CSME version
Step 11 - Failure: CSME version has not been updated
Step 12 - Boot into Flash Tool
Step 13 - Search for binaries and use FWUpdLcl.efi /F FWupdate.bin
to flash manually
Step 14 - SUCCESS
OBSERVED RESULT: (Eventually) SUCCESS
EXPECTED RESULT: SUCCESS
ISSUE RECOVERY METHOD:
Error Status: Invalid Parameter (line number 97)
S
to get to shellframework-firmware-update/firmware
FWUpdLcl.efi /F FWupdate.bin
to manually updateEXTERNAL DEVICE MODE or NAME: Samsung USB-C drive 64GB
From looking at the BIOS I can confirm the following updates have been applied:
Component | Expected Version | Status |
---|---|---|
BIOS | 3.08 | OK |
Intel CSME | 16.1.30.2269 | OK |
Microcode | 4.29 | OK |
GOP | 21.0.1061 | OK |
EC | 4ea1c89 | OK |
PD | 0.1.2C | OK |
Mine worked on the first try. Here are the details of the system.
From looking at the BIOS I can confirm the following updates have been applied:
Component | Expected Version | Status |
---|---|---|
BIOS | 3.08 | OK |
Intel CSME | 16.0.15.1810 | ?? |
Microcode | 4.29 | OK |
GOP | 21.0.1061 | OK |
EC | 4ea1c89 | OK |
PD | 0.1.2C | OK |
Thanks to @jmariondev I noticed that my CSME update didnāt actually happen.
Following this step took care of it.
Component | Expected Version | Status |
---|---|---|
Intel CSME | 16.1.30.2269 | Updated |
My update was successful on the first try, though I had to manually choose the boot device between reboots. The machine kept wanting to boot back into the OS.
Notably, I also started the process at 90% battery and reset the BIOS settings to default before updating.
In line with the reply above me, I see all good versions except for ME which doesnāt seem to have updated:
Component | Expected Version | Status |
---|---|---|
BIOS | 3.08 | OK |
Intel CSME | 16.0.15.1810 | ?? |
Microcode | 4.29 | OK |
GOP | 21.0.1061 | OK |
EC | 4ea1c89 | OK |
PD | 0.1.2C | OK |
The BIOS update is in the Beta stage for a reason. Framework would have done internal testing before releasing the update to the community otherwise, it wouldnāt have been released at all. However, since they canāt test for every case, that is why it is currently a limited release (if you go to the driver and BIOS page for 12th gen, youāll notice it states " *No new BIOS available"). A limited release allows the team to see if there are any issues that didnāt pop up in their testing and address them before a wider release. Only BIOS updates that have become official are directly linked on the respective pages.
If you decided to run the Beta BIOS update, you choose to accept the risk that there may be issues with the process. Most importantly, you are under no obligation to perform the update if you arenāt comfortable with the potential risk and the laptop will continue to function fine without the BIOS update.
If you are having issues with the update, report them (as thatās the whole point of this thread). The team is doing their best to address any issues. However, bashing them is completely unwarranted.
Revised my reply after I read yours. My ME version didnāt update either
Just updating here - it looks like using 3.08b (as given to Ray above who had this same issue) worked without problems
Component | Expected Version | Status |
---|---|---|
BIOS | 3.08 | OK |
Intel CSME | 16.1.30.2269 | OK |
Microcode | 4.29 | OK |
GOP | 21.0.1061 | OK |
EC | 4ea1c89 | OK |
PD | 0.1.2C | OK |
I might have borked on the HDMI side and this could mean all went good in the first place. I do note if you have a EFI partition with a startup.nsh file, it will first try to run that instead of the USB stored startup.nsh, press the key is mentioned to skip yours, switch to FS1: i assume is your usb device and then type startup.nsh. (I use the startup.nsh as a backup for if my arch install is broken)
all EFI variables where still in place and working after the update. HDMI module has mod applied https://dozuki-prod-us-east-1-guide-pdfs.s3.amazonaws.com/pdf/framework/guide_193_en_814.pdf (if there is any newer, can I have the new forum post or details?)
So my laptop now works as I expected it to be
Seems to me the EFI updater simply seems to miss setting a nextboot
entry at some point.
It only did the first few steps and then booted me into my OS.
I use systemd-boot and had the FW updater on my nvmeās ESP.
After noticing the partial update, I just re-ran it several times (I think it was 3 boots in total where I had to re-select āEFI default loaderā in systemd boot) until it showed that everything was updated.
It did skip the CSME update as others mentioned above, possibly due to the interruption of the process, and I used the EFI shell executable I copied over from the Arch ISO to run FWUpdLcl.efi
as others mentioned above and now Iām all updated.
External 4k monitor with PD support works.
USB-A issue is fixed.
External nvme via thunderbolt pci passthrough also still works.
HDMI for movie nights also still works.
So all good here.
intresting, maybe this is due to firmware update and secure boot? I dont have secure boot turned on and the boot entries are still there
A> After opening the case to get serial info for this post. The screen stopped working all together, in or out of windows. I am able to connect to an external display (DP over USB-C) or remote into it and can see the screen is detected and appears functional to the system. The screen is dark and off.
If this only happened after opening the laptop, Iād open it up again and have another look at the display cable (correct routing around the hinges?, connectors plugged in completely?, any kinks?, etc).
well this keeps getting stranger.
I tried reseating the display cable and then it stopped detecting the internal screen all together. (now I was worried I did break it).
Tried reseating it again and very closely checked the routing, all looked good.
Booted again and screen was flipping from detected and not detected on the display settings and I saw the backlight come on for a moment a few times. Disconnected the second screen and hopped into the remote desktop app on my phone. Hoping it could figure it out. After a bit the backlight came on and showed my desktop with loads of green snow (pixels) flowing upwards, that slowly dissipated over time. yay?!
Rebooted to make sure its still working. I have no display at all until the windows screen but then everything is looking fine.
Iād really like a download link to the 3.06 bios so I can roll back and eliminate it as a variable for this screen issue!!!
Same boat. Use the same 3.08b file. Update was successful.
Computer was Batch 1 - i7-1260p.