12th Gen Intel Core BIOS 3.06 Beta

May I suggest moving the thread from tracking to normal, so that you will only get notified when mentioned? Then you can check in once a month or whatever your chosen frequency is. Shutting down discussion/debate/complaining will not change anything and will only make the discontented more discontent and more vocal. I for one do not feel heard and very little in this thread has given me cause for comfort other than knowledge that Framework is introducing some new process to fix this mess.


Then how am I supposed to find out then Framework actually does respond here? Changing the tracking doesn’t change the fact that when I come back to this thread, there are dozen of comments that are not actually relevant to what I am looking for, which is concrete updates about this problem.

I am not suggesting shutting down the discussion here at all: I am suggesting the discussion be moved to the topic it desserves, to actually talk about the actual thing you and many others are worried about instead of burying it in this thread.

There are, by the way, other threads where similar complaints are being made and I think those would be better served by being moved in the own thread.

But what do I know, I’m just a bystander and not a moderator. :stuck_out_tongue:


I imagine they would do the yellow highlight on their messages, so you could just as easily skim through the thread and stop when you see the highlighted message. Asking others to voice their complaints elsewhere in a likely less visible thread at the very least gives the impression of minimizing the complaints.

I’m also only following this thread because nothing gets updated here:


True. I guess I should restrict myself to asking @moderators to do their job and spin off that discussion in its own thread where, I think, it would actually be more visible.

But then it seems they are not interested in doing so immediately and you do not seem interested in letting this drop, so i’ll just be muting this thread and hope that somehow I will learn about the BIOS updates in some other way than this unfortunate thread.

Update on post-launch BIOS updates
As I shared in an earlier post, we’ve been working with our upstream suppliers to get dedicated staffing place for post-launch BIOS updates. Until now, we’ve been doing releases like this 3.06 Beta with borrowed resourcing from those suppliers, which meant that when we found regressions in it, we couldn’t get the necessary support to resolve them and ship a final version. Now, we have a negotiated contract for a dedicated team to provide ongoing software work post-launch.

The contract is the starting point. From here, our supplier needs to reallocate or hire the new team members, and we need to work with that team to get them up to speed on our hardware and codebase. The first project this team is working on will be 12th Gen BIOS. After that, they will be rotating between releases on 11th Gen, 12th Gen, 13th Gen, Ryzen 7040 Series, and future products as needed.

Our overall release process will be:

  1. We identify field issues through customer support or security issues through our automated analysis or notices from our upstream providers.
  2. We roadmap the development work to resolve these issues with the sustaining software team, some of which may depend on other work from suppliers further upstream.
  3. We do internal testing and validation on a new software release.
  4. We release a Community Beta.
  5. After a two week Beta period, if we have sufficient test feedback and do not see launch blocking regressions, we promote the release to final both as an .exe for Windows and via LVFS on Linux. Some releases may have firmware updates that can’t be done via LVFS, and those can use a manual EFI update process instead.
  6. If the Beta does uncover blocking issues, we’ll communicate that, and go back to step 2.

Finally, something worth reading.

Although this process seems like it should have been something initiated 1 year, 2 months and 21 days ago.


However valid that feeling is, it was profoundly unhelpful to say


Thank you for the update.

@nrp thank you very much for the update.

I read your earlier update and the additional background provided in this post adds much needed context and detail. Understanding that there will be a rotation, that you have a vendor who is now contractually obligated directly to you, and the specificity of the Beta to Stable roadmap make all the difference to me at least.


@nrp I appreciate that you always show your kindness and love in your communication.


How long is each cycle for each product? e.g. Does it mean we’ll be able to see regular periodic updates going forward?

Edit: I’m asking because this, together with the complexity of the issues / bugs / features, and the runway, will contribute to how many BIOS updates per model we’ll see annually, and the timeliness of the fixes.


@NRP thank you, thank you thank you. Honestly the BIOS updates have been the worst part of the Framework experience and its good to see there will be contracts and a process to get this normalized in the future.
Its one of the few reasons I cant recommend everyone gets a Framework as you need to have the patience and skills to be able to work with trying to communicate the bugs and get them addressed so they can hopefully get involved in the once a year updates that seem to have been possible in the past.
As an EUC Architect for a Fortune 200, I know the importance of regular firmware updates especially during that first 12 month period as bugs and comparability issues are discovered as your userbase finds more random crazy things to plug into and new ways to use their notebooks.
I look forward to seeing this rough edge get addressed. :slight_smile:


Thank you for the update @nrp
Very happy to see the bios issue progress in a meaningful fashion.

1 Like

Is the contract only negotiated or did they sign it already? (Since they still need to reallocate or hire new team members)

1 Like

In the above public released statement has this so please why did they lie about it then.

…“Thunderbolt is unbelievably complex technology. When we ran certification testing the first time around, we passed hundreds of test cases… and failed dozens. We’ve worked with our manufacturing partner and chip suppliers over the last two years to address each test failure through firmware modifications, and now have fully compliant firmware and hardware!”

I don’t see how that was a lie. Thunderbolt is just a certification by Intel. The hardware was already there to begin with on 12th gen, just that testing needed to be done in order to ensure it met Intel’s standards. The BIOS update introduce tweaks to improve behaviour of various components to meet the specified standards. Even as a beta update, that promise has been fulfilled.


My questions from August haven’t been answered yet that I know of. Do we have answers to these yet?

Re-posting them here for convenience:

  • For how long do mainboards receive security updates after launch?
  • How quickly should we expect updates after disclosure of vulnerabilities?

If there isn’t any answer available for those questions, then I have a followup:

  • Is the company’s policy on firmware support going to get any more fleshed out in the foreseeable future?

Crickets …