An unfortunate update: I got hit with the 400MHz bug again. It seems this update only makes it less frequent but doesn’t actually solve the issue.
EDIT: it’s really bad now. I have resorted to disabling all but two performance cores and pegging the fan at 100% when running “heavy” workloads. That seems to be the only way to keep it from locking up.
I don’t know why we’re crossing our fingers hoping a (pre-alpha state) firmware will fix a fundamental design/chip flaw.
This computer was not fit for purpose from day one, and they’ve had almost exactly 3 years to investigate, test and fix this, but haven’t made an inch of progress.
I implore Framework to issue a recall or a favourable upgrade path out of this 400mhz prison.
PCEI is the CPU temperature, similar to cpu@4c on AMD(also defaults 103 °C and 105° C as the fan curve hasn’t been updated). When the temperature is error, the fan resorts to pre-update sensors, F75303_Local andF75303_CPU
The issue with that is that PECI reading goes 99->100->Error
So the CPU gets hot, fans spin up, it heats up a bit more, fans go way down again. I can’t imagine this is the desired behavior
This is not the desired behavior, here’s another one.
I think it is doing what you described earlier, i.e. it falls back to the other sensors. Those read much lower, so the fan speed drops sharply. Presumably it would rise again once those go up, but usually it’ll run into the 400MHz lock before that.
Neither of the things you are suggesting will happen. It didn’t happen for the RTC battery issue, it won’t happen for this.
Either stomach the 400mhz bug, try to get a replacement board from framework, purchase an upgrade at full price and sell your defective board or just sell and get out of the ecosystem entirely.
I’m not trying to be harsh or defend framework, just listing actual available options. Personally, I sold my Framework 13.
I had to go back to 3.08, the 400MHz problem was constant when using Google Meet
For those experiencing the 400mhz bug what OS are you running? Asking I have a 12th gen Intel and only experienced this once in the first week of ownership. Not since.
Windows 11 for me.
I’m getting this on Arch. Kernel 6.12.
My laptop was working great for a long time. Then i upgraded to the 61Wh battery and updated the BIOS to use it. That’s when the 400MHz issue would starting popping up occasionally. Since about a month ago it’s happening constantly.
@Daniel_Gstohl are you using thermald on that Arch install? Also are all the thermal pads on the board making contact with the components they should be? Lastly what do you thermals look like when the 400mhz bug is not showing its face?
Yes, it’s running thermald. All the thermal pads and paste should be good, I replaced it in an attempt to fix the issue but no dice.
Thermals are about 50-60 on the F75303_CPU sensor. PECI jumps around alot, sitting at about 65 at idle but spiking to 80-90 at the slightest load.
This is too high, repaste the thermal interface.
Sorry didn’t see you already did that. Check the idle power consumption and weed out problematic background tasks.
“Idle” was maybe not exactly true. If i kill everything I can get the CPU sensor to 50 and PECI to 55. The second i open firefox, PECI momentarily peaks at 85 and drops to 60 again
Can you get a reading of power consumption when opening Firefox pages?
None of those readings are what I would call normal. Either you cooling solution is compromised, the thermal paste is applied poorly, or you have a likely problem with the board. I recently upgraded to the 61Wh and upgraded my BIOS as well, and nothing comparable to note.
Thank you for your advise. My system is now fully updated. I was also running into the same issues you described.
Maybe any news/eta on when the new version with the “real” fix will become available, now that the buggy version got promoted to stable?
Agree, I was surprised to find framework’s email this morning proposing me to install the BIOS update 3.17