Updated my post. I am asking about WiFi 6E (6GHz).
The 6Ghz radio is invisible on the current BIOS for 12th Gen (all tech details explained here).
I am happy to assist with beta testing for WiFi 6e DE region. Tnx!
I can only recommend NOT applying this update for now.
Windows 11 user with i7-1280p here.
After the update, as soon as the slightest load is applied, the CPU throttles to 0,4 GHz and stays there. This even survives reboots and makes the whole laptop basically NOT USABLE anymore.
The jet engine starts to bruise soon after the load arrives but its way too late already it seems. The only way to get back to usable CPU speeds is by waiting and letting it cool off.
As you can see in the screenshot, it took me like 2 minutes after a reboot to even make it with this performance level/clock speed.
I did both bios and retimer updates. The problem arrived after the bios update and didnāt go away with the retimer updates (not that this would be expected Iād say but it gives a clear indication on where the issue resides).
Iāll now have to look into downgrading this whole thing againā¦
Man does it suck to have such a powerful machine which did cost a decent sum of money - I even bought the 2.8k screen - not usable at all and now only lying around most of the time.
Edit: By the way, I tried the PTM thing before the upgrade to the new bios as well. It brought the temperature down a couple degrees but didnāt manage to tame the excessive fan blowing. Thermal Grizzly - PhaseSheet PTM - High Performance Thermal Pad with Phase Change Material | Durable, Non-Electrically Conductive | For CPU, GPU & Electronic Cooling: Amazon.de: Computer & Accessories
2 Likes
That sounds more like the PROCHOT bug and may be unrelated to the BIOS tbh.
2 Likes
Did you try this possible solution? Fan Noise is constant and loud at 15% load - #34 by Max_Klassen
1 Like
My 1240P had extremely conservative fan curve on 3.09 compared to 3.08, it was throttling but didnāt cause 0.4GHz. Maybe the two more cores you have made it go straight into some thermal fail-safe mode.
EFI downgrade seems reliable, worked for me, restored better cooling after downgrading. Remember to suspend disk encryption if you have it on.
1 Like
I am also noticing the fan curve issue now that Iāve spent some time using this update. If the chassis gets hot, the laptop slows to a crawl without the fans ever even turning on. Before this update, it would at least TRY to cool itself off 
3 Likes
We found a known issue that If the battery extender mode is disabled, and charge limit is set below 100%, the charge limit will not be enforced causing the battery to charge to 100%.
10 Likes
Interesting, thanks for sharing. So maybe another bug, great. I looked it up but beside a lot of discussions which seem to go nowhere, what is the solution for 12th gen intel framework? A common solution recommended is to āupdate the biosā - Wellā¦
In my opinion, the fan curve on 3.09 is much better! I ran a stress test, and the laptop has no problem keeping the CPU at around 90 degrees while sustaining 2.8 GHz. The fan kicks in at around 70ā80 degrees.
So, at least for my use case, this means less noise and sufficient performance.
For reference, i have PTM installed.
1 Like
Do you usually use your laptop docked?
For my use case, the problem seems that the fan doesnāt run at all until the CPU temperature sensor reaches ~ 60 Ā°C (checked with framework_tool --thermal which outputs Fan Speed: 0 RPM in this case). So, the the aluminium chassis of the laptop serves as additional heatsink and heats up more and more (at the bottom around the air intake and above the function key row it seems to get near the CPU (sensor) temperature quite fast, then the sides with the expansion cards get warm, and afterwards the aluminium between the keys of the keyboard and finally the palmrests). So, running the CPU at ~58 Ā°C for a few minutes will get the bottom and parts of the input cover into an uncomfortable temperature range (and certain parts into ātoastyā territory).
Only if the CPU is then stressed a little more and its temperature goes to ~ 65 Ā°C the fan kicks in with ~1800 - 2500 rpm (according to framework_tool --thermal) and only then the temperature of the chassis goes down again a little. However, as soon as the CPU is below ~ 55 Ā°C the fan is turned off again and the chassis stays at its elevated temperature.
I donāt notice the fan at 2500 rpm, so I wouldnāt mind if it already kicks in at 40 - 45 Ā°C to keep the chassis below CPU sensor temperatureā¦
If it is the PROCHOT issueā¦then the only option is a complete board replacement because it is unrelated to the BIOS. You can try downgrading the BIOS from 3.09 back to 3.08 and see if that solves the problem. If it does then great! If notā¦reach out to support and see what they say I guess.
1 Like
Great to see a new update which fixes security issues from 2023 
1 Like
Hi,
6ghz wifi 6e, AX210 framework 13 12th gen, is working fine (reg domain de) here with ubiquiti APs until kernel 6.12 ā 219714 ā [REGRESSION, BISECTED] 6GHz Wi-Fi auth unreliable AX210/AX1675* 2x2 [Typhoon Peak] (rev 1a) ā maybe ubuntu backported some of the 6.12 wireless changes. I am using U7 Pro Max though.
Heads up ā over at the FW13 Ryzen side, the just recently released AMD Ryzen BIOS 3.07 has the same (or very similar) charge limit bug as discovered in the 12th Gen Intel Core BIOS 3.09 Release BETA:
The kicker is that even though the bug was discovered, reported and confirmed during the AMD Ryzen BIOS 3.07 beta test phase, Framework decided NOT to fix the regression, resulting in many upset people:
So far the 12th Gen Intel Core BIOS 3.09 hasnāt been released, but itās entirely possible the Framework team may simply ignore the charge limit bug.
3 Likes
This BIOS update was the smoothest one so far! Congrats Framework team.
Iāve updated here (Linux Ubuntu). That process was SO much easier than previous attempts. Thanks!!!
I think every pig from here to San Francisco just flew to the moon.
But still having (or even making worse) the .4ghz bug is absolutely abhorrent, and should be the primary focus of a BIOS update, since itās been a known issue since pretty much day one. I like opening more than 5 tabs, when I canāt even open more than 5 tabs, this computer is useless to me.
If it really is a physical issue, then we should be entitled to another mainboard that doesnāt exhibit this behaviour. When is the recall happening?
1 Like
Iām wondering, can a mainboard be affected by this bug simply through updating bios or at some point in time? As far as I understood PROCHOT it is a hardware fault in the end which either exists or not but can not occur after some random amount of time? In my case it would correlate exactly with the bios update, how likely does that seem to be.
I really donāt know to be totally honest with you. Only Framework will have the data to make any kind of conclusions. Given that BIOS updates can contain microcode, it is conceivable they could induce such behaviorā¦but then every board would be affected I would think. So to me, it seems more likely that it spontaneously started occurring in your case but coincided with your BIOS update. Not a software engineer so thatās just my laymanās opinion.
1 Like
I see, thank you. I mean, in the end the 3.09 is still BETA as well, so they will have to find out the reason for it and fix it anyways before ever putting out a RELEASE. I might look into downgrading meanwhile so Iām able to re-use this thing again and not have it lying around for months until a RELEASE version eventually comes which has this fixed.
1 Like