I’ve managed to do a downgrade to 3.08 (https://downloads.frame.work/bios/Framework_Laptop_13_12th_Gen_Intel_Core_3.08d_EFI.zip). It seems to have worked without issues.
3 Likes
Almost a month since binning the update, and, shocker, we’re still in the dark.
What are you doing over there except high fiving each other for releasing 5 more generations since this one?
6 Likes
Constructive feedback is always welcome on these forums, but toxicity and passive aggression are not.
7 Likes
Can we please have an update on the status of this BIOS update. As noted in the release notes, this fixes a fair few bugs and security updates, so it’s pretty important. The USB related issues are particularly annoying in 3.08.
2 Likes
My (hopefully) constructive feedback:
-
Please test firmware releases before publishing them, even if they are published as “BETA”.
Don’t get me wrong - I really want to believe this is done already but given the QA process does not seem to be transparent (it would just be nice, doesn’t have to be, of course) and the 400MHz bug is something so obvious I as a regular user encountered it after less than 5 minutes post upgrade, I have a hard time understanding how testing is currently conducted. -
Please provide regular updates on topics like this one. Especially if someone comes out and mentions that this topic will be “prioritized”. I do not know the definition of “priority” applying at Framework but in our company it means shifting resources (whatever might be needed) the best way to solve a specific situation/problem as quickly as possible while communicating transparently to the customer on the progress going on, especially regularly. It’s over a month now since this got “prioritized” without any kind of update.
Otherwise, thank you for moving what I consider to be a very relevant mission and vision, forward and for all the hard work which I’m confident is happening in the background (even though it’s kept “top secret” for some reason).
8 Likes
We regret the delayed update for the upcoming release. To resolve user experience issues, we are actively validating fixes for battery limits and the 400MHz frequency. We aim to release version 3.10 by mid-May, which will include these fixes, security enhancements, and dual display support in BIOS/POST.
15 Likes
Yes, this version can be downgraded to 3.08.
3 Likes
While we can reproduce the issue under heavy load in low fail rate, we are working on a straightforward method to reproduce the 400MHz bug for efficient solution testing. To help us, could you indicate which application was active when the 400MHz bug occurred?
4 Likes
For me its sufficient to launch a virtual machine in vmware workstation (e.g. windows 7/10/11) or install a (bit bigger) windows update.
Sometimes its enough to launch native Protonmail Desktop Application and 10-15 tabs in Firefox, eventually in combination with a Youtube Video. But this way usually takes some time to trigger it I would say.
Mhhm thinking about it, launching visual studio which post launch compiles my spring boot app with maven likes to trigger it as well.
Thanks for starting to reproduce the 400 MHz bug already at least five weeks after it was mentioned first: 12th Gen Intel Core BIOS 3.09 Release BETA - Held - #24 by 1stivi
Things like this make it hard to stay constructive, imho.
EDIT: Holy cow, I just found that the 400 MHz bug is over 2 years old already!!
4 Likes
Cinebench 2024 on an otherwise cold laptop. Seemed to coincide with the point, where I’d say the system is under the most heat stress, as the fan is not yet on its highest speed, but the system is already hot. Did not seem to be reproducible once the system was already hot with the fan already spinning on higher RPM.
For me personally, on 3.09 I saw obvious thermal throttling under all-core heavy load. However, the frequency drops gradually as heat saturates, and it never just fell to 400MHz. I wonder if 400MHz and degraded cooling on 3.09 are two different issues? (downgrading to 3.08 restored better cooling)
Thank you so much for bringing this up, this feature is critical for me. From my experience, only 12th Gen currently supports it after 3.05->3.08 update, hence why I have a 12th Gen semi-permanently docked. I couldn’t get the same to work on 11th Gen/7x40/Core Ultra. I would love to see this feature enabled across all generations. (because why not 
)
2 Likes
Games of any sort make it very obvious for me. So for example:
- Turn your laptop on.
- Plug it in and turn power settings to max performance.
- Open Fallout 4.
- Walk around for like 5 minutes in game, it’ll suddently turn into a slideshow after the temp gets up.
I think this is a very realistic usecase for many users too. You finish work, crank the settings on your laptop and open a game.
4 Likes
@Quin_Chou Is it correct to see the EFI edition is “AccessDenied” ? The windows executable are still available. Ive managed to get the same EFI file still, sha256 matches.
Do you have secure boot enabled?
I’d assume @CodeAsm refers to the download link for the Framework_Laptop_12th_Gen_Intel_Core_3.09_EFI.zip file that seems to result in a “Access denied” message at the moment.
1 Like
We have the solution already but we are trying to find a
Sorry for the delayed reply. The link is now fixed. Due to an LFM issue in this version, we aim to release a new version by mid-May, with a beta release next week.
4 Likes
Thank you very much for the proactive update.
One question: Is the 0,4 GHz thing really fixed, like fixed-fixed? What I mean with this question is, that I noticed it even occurs after downgrading to 3.08 again, but only in a very limited manner I would say. I sometimes had the notebook become very sluggish in the past for some shorter time but never analyzed it too deeply. After my experience with 3.09 here I just checked the speed in the task manager and noticed, that even on 3.08, it sometimes gets stuck on 0,4 GHz for shorter amounts of time. It doesn’t stay for like many minutes like on 3.09 here though.
Is this solved completely in the new version?
You’re right, it’s very limited. We’re working to identify various reproduction steps to confirm it. Currently, we’ve been unable to reproduce the issue through various steps, even under heavy load. We expect our current validation to be reliable. We’ll release this version post-internal validation, and at the same time, review it for any missed items.
5 Likes
It would be good to hear an acknowledgement of the disaster that recent BIOS updates have been.
EDIT: posts towards the end of this thread do contain some relevant apologies by Framework developers.
1 Like