Are you sure, Framework is affected?
I have not found anything relating this CVE to Insyde, also it is not listed in their security advisories: Insyde's Security Pledge | Insyde Software
1 Like
I’m pretty confident Framework isn’t affected. The article is regarding Phoenix built UEFI and not Insyde. The point of sharing was to illustrate how important firmware updates are. And how tardy Framework can be in addressing in these issues at times.
2 Likes
Yes, i did use the earlier efi update first, and when noticing csme not being updated (and apparently the retimer for 1 side) i ran the newer update, the efi still.many many reboots, and thinkering with the scripts myself to figure out whats wrong. Eventually it seems a normal updater on the left side usb, with a writable and large efi boot on my nvme was able to update. Mind you, it still had my windows and arch install on there. Im not using grub and allowed whatever boot edits it wanted to make. No secure boot.
I might have triggered the updates by hand without noticing succes at some times. But eventually all parts where updated.
1 Like
- Then I noticed that Fn key is not working. I wasn’t able to adjust volume or screen brightness as if the button itself was broken
- Finally, I’ve noticed that the ACPI1 metric is reporting temperature of 175°C which was nonsense, since the cooler was almost silent and the laptop was suspended for more than an hour before that.
- After hibernating the system (to disk) and resuming, everything went normal again.
This has been happening to me too—I’m not sure what causes it but occasionally the function keys are messed up with no way to fix, and I get the same wildly inaccurate temperature reading. Reboot seems to fix for me too.
Are any of you having boot issues since the unsuccessful update? Since I last posted (and failed), I have had two boot loops/failures. Both times, the LED, power button, and fans turned on, but the screen stayed blank, and then it would power off and repeat this state. I fixed it the first time by resetting the mainboard. I do not have time to do that again, and it’s not really a solution.
Yes, I am having the same boot loop issue. For me, it happens if I close the laptop lid and it goes to sleep—then it becomes impossible for me to hard power off, reboot, or anything, without opening up the machine and resetting the mainboard state. I have started carrying around a screwdriver with me, the first time this happened was at a conference and I had to take a taxi to a hardware store to get a screwdriver, so that I could have a working laptop at the conference!
I noticed it also happened once when I didn’t close the laptop lid. something about going to sleep causes it but I’m not sure what.
Moral of the story is I seem to have a pretty broken system now, and I don’t even have a way to fix it, because every attempt at the updater scripts I have tried has failed, and I don’t have windows on my machine. This is a pretty frustrating situation to say the least! Frequently unplugging and replugging the battery connector to reset the mainboard state is making me really nervous, because the guide says there is a high risk of bending the pins.
Has anyone been able to go from 3.04 to 3.08 on Linux?
It seems like the answer is no? 
3 Likes
Recurring BIOS/Boot Failure, No Display; 12th gen firmware troubles; no error; post code 0x21 I made a post for it. I also contacted support, and I urge you to do the same. Do any of the details differ?
3 Likes
Has anyone been able to go from 3.04 to 3.08 on Linux?It seems like the answer is no?
Well, apparently it had happened… But all these last message for the past week are surely preventing me to do anything before I have more information (and yet, this is the answer #562 on this topic 
)
And… it still fails once in a while. OEM kernel works much better than generic one, but I still experienced lethargic sleep with no way to wake the laptop up. This time it took 15 days (and a couple of dozens suspend/resume cycles) to fail.
At the recommendation of support, I just tried on my machine running Ubuntu 24.04 live. I was able to suspend and resume from suspend twice, and on the third try it got “stuck” in suspend and I couldn’t do anything to resume. However unlike in my regular OS (EndeavourOS), in this case I could hold the power button to hard power off, and then I was able to reboot. Under EndeavourOS, when I suspend and try to resume, it immediately powers off and then gets stuck in a boot loop that I can’t resolve without opening up the laptop and physically disconnecting the battery and CMOS coin cell.
1 Like
Yes, that is what I did to bring it back to life (always worked for me). Never seen anything like boot loop before.
Good news: I finally successfully upgraded my BIOS from 3.04, and it fixed the suspend issue for me! After some back and forth with support they suggested I try upgrading to 3.06 first, and I did so using the EFI shell updater here. That already fixed the suspend issue for me but YOLO, computer luck is in the air today, and I tried updating to 3.08 and it also worked using the EFI shell updater from this thread! Now my BIOS is fully up to date and suspend seems to be working great. Woohoo!
EDIT: wanted to note that the 3.08 shell updater did not work for me on battery power, but worked when I plugged in.
4 Likes
Is a stable EFI updater ever going to be released or has it been abandoned altogether and we should just write it off? At that point, if this has been abandoned, I would just prefer to know rather than wait another year for something that will never come.
It will be a huge disappointment and will impact my future purchase decisions but it will at least be honest. We have been waiting for close to 2 years for the promised features, 61Wh battery compatibility and numerous security patches and there has been no updates regarding the state of the EFI updater for several months now, so considering it abandoned seem the only logical conclusion at that point.
6 Likes
Id like to add that its one of the steps, to power the laptop with the external powersupply:
Its not noted in the top post however, that would be a good addition
3 Likes
It works! Hallelujah. Well, hopefully nothing goes wrong, but it’s seems so. If this problem affects most/all 3.04 users, I really hope they make a note/warning at the top of the page.
3 Likes
I also successfully upgraded to 3.08 using the 3.08d update at the top of this thread. I updated from 3.04 to 3.06 (having to do a few reboots and a few re-accessing the usb thumb drive) to get it for force the steps (as listed in the guide). And then, I updated to 3.08. The 3.06 bios update has a very verbose script and will report each of the 5 steps and can tell you when the update is complete. The update to 3.08 will just show a black screen and then reboot. If you boot from the USB thumb drive again, it will report if the bios update is complete.
For anyone else updating from 3.04 on a 12th gen system, read the guides, follow the steps. Format your USB thumb drives to FAT32 and eject them properly after copying the files. Shutdown and unplug the system for at least 90 seconds before rebooting and ensure all your ports work. Unplug any peripherals. I used USB2.0 thumb drives (both 16Gb). Keep your system plugged into wall power throughout the process until the upgrade is complete and don’t unplug your USB thumb drive until the update reports as completed.
2 Likes
I finally gave up and installed Windows on a spare SSD and just ran the windows installer. I was super patient, but got tired of not knowing when it might be released. Overall, it took me about an hour to open the laptop and swap in the spare drive. Install windows, update and install drivers, then install the BIOS update.
All went well.
4 Likes
Same here, going from 3.04.
I put Windows on a spare SSD, updated it and installed like it was going to be my main OS (with Framework drivers). Unplugged all expansion cards and peripherals.
Originally, it didn’t seem to update to 3.08 but it got there after a couple of reboots.
3 Likes
What a pain to think I will have to do this and to think I will have to do this again if they release a newer patch/version.
I am also quite tired of that situation. I hope very much there is journalistic pressure again so we can have some updates on the Linux bios situation on 12th gen.
4 Likes
Just fyi, the EFI updater was released for 11th and 13th gen. It essentially has the same structure there. And it causes the same problems of users misunderstanding what is updated and what not.
The only thing missing is reports of where CapsuleApp does not like the EFI partition somehow. Which fails to update the BIOS without a good error message, but not critically.
11th gen update was just dumbed down considerably. Doing that to the 12th gen update would remove the standalone update ability. But they do not care that this is missing for 11th gen.
I think they are being inconsistent in what they consider good enough for release…
2 Likes
Re: “LVFS will not update the CSME firmware”. What problem would be caused by not updating the CSME firmware? If I decide I do not care about CSME, can I use LVFS to upgrade?
1 Like