If you have this issue after waking up laptop from sleep, then this issue should be fixed with new bios. Although as reported by Jarred it is not fully fixed. CPU frequency stuck at low values after suspend/resume on firmware 3.06 · Issue #91 · FrameworkComputer/SoftwareFirmwareIssueTracker · GitHub
1 Like
A strong word of warning to anyone considering BIOS updates from Framework.
If the Framework-provided BIOS update breaks (bricks) your laptop, and your laptop is “out of warranty”, Framework will not replace the mainboard.
There is an ongoing horror story with a broken BIOS which is known to brick laptops: Upgrading to BIOS 3.20 on Ryzen 7040 series may brick your machine
So far Framework has not responded and has not withdrawn the broken BIOS update.
2 Likes
That’s really concerning considering they also milk these updates by only fixing one bug in each one instead of fixing most known issues and then releasing the update, which means we have to keep applying bios updates more often for every little fix, increasing the chance something goes wrong.
It really feels like framework tasked only one guy to all the bios updates which is really hurting their reputation.
3.20? was like ages ago? we are on 4.05 on 7040 for FW16 these days
I believe the 13 has different firmware which releases independently.
different for the different cpu and mainboard generations/vendors. but the complaint there and the thread here, are both for the 7040 / ryzen type of fw16 and thats all the same. 3.20 came out before later 4.x and this threads 4.05 versions.