Just in case you haven’t seen this, you might want to hold off until later this month. 3.07 (which is what fwupd/lvfs tried to install) has known issues that should be addressed by then in a new version:
On your specific error, unfortunately it seems that your EFI partition doesn’t have enough space to stage the update. If repartitioning is not an option, you might need to go with the UEFI shell update or Windows option.
My charge limit is not working anymore since the latest BIOS update.
I limit my charge to 90. My OS (Linux) even confirms the setting is applied in the BIOS, but is not being respected. Here’s what I’ve tried to do to fix this:
Is this a known issue?
yeah, thats also why rollout is currently held:
Yes. Framework is aware of this bug (and they were aware of this bug before they shipped 3.07 as stable for a few days before changing it to “held”). They are aiming for a fix by the end of March, but, speaking as a software engineer, personally I’d expect that to be delayed because software usually takes longer than expected.
You can’t roll back to 3.05. One work-around I’ve seen mentioned is disabling and then re-enabling the limit every time you boot the laptop.
Turn on battery extender with BIOS setup screen. Set charge limit to 85 (not 90) with BIOS setup screen. Reboot. Set charge limit to 90 with BIOS setup screen. Reboot.
Now, I think you’ll probably find the 90% limit sticks as long as you mainly use the laptop with AC power connected.
Error is pretty clear. your /boot/efi partition is way too small to be able to update.
I have a gen1 and was working most of the time (only issues when suspending disconnected then resuming while connected but unplugging/plugging would solve it) and with the BIOS update I not only lost video output but USB as well.
It’s more than undiscovered bugs…
These days I read discussion threads on various computer forums and I discovered that automated BIOS updates often do more harm than good, often intentionally by manufacturers ranging HP, Dell/Alienware, Asus/ROG, Lenovo, etc etc.
Intentional/malicious problems like blocked S3 sleep([deep] not available even on Linux), reduced TDP(making gaming laptop to heavy office laptop), blocked undervolting/removed curve optimizer (decrease performance & increase heat), PCIe4.0 downgrade to PCIe3.0(more laggy I/O), louder coil whine (unstable voltage, components fail faster). These intentional BIOS “upgrade” often labeled as “critical” or “important” Windows update instead of the usual “optional” for drivers, making the user very difficult to disable it.
Automatic BIOS update with undowngradable firmware makes a breeding ground for planned obsolescence for various manufacturers. Users are outraged, craving for answers for ways to block BIOS updates.
Framework BIOS can be buggy sometimes but there are much worse instances out there
That’s not a point, it’s quite unprofessional from framework.
since the latest update my battery charge limit feature has not been working
7640u
anyone else having a similar experience?
The most ridiculous thing of this all continues to be the fact that this thread says it’s held, and the support page says it’s released and LVFS has it as released.
Either it’s held, or it’s released. Make up your mind.
Can BIOS 3.07 be removed from LVFS as Ubuntu keeps trying to upgrade this broken firmware?
I found right alt key not work correctly after update BIOS 3.07.
I check all keys by https://keyboardchecker.com/ , only right alt key malfunction and show AltGraph pressed.
I checked in Windows 23H2 and Pop_OS! 22.04 live CD,
so I didn’t think it’s OS or driver problem.
But I cannot sure the problem and BIOS upgrade (from 3.05 to 3.07) have 100% relation.
My FW13 7040 series bought at November 2023 (with Traditional Chinese (Cangjie & Zhuyin) keyboard option). I install drivers from framework website, and almost latest AMD driver (Adrenalin 25.3.1 (WHQL Recommended)).
There are two days left in March, is this going to end up like the “end of December” deadline for 3.07 beta that was released in March? Is there any plan from Framework to regain credibility on this mess?
I pretty much ignore the delivery commitments now - they are never met. In the meantime, and for this particular bug, I will be opening my laptop and checking the battery for bulge since we can no longer use the charging limit. If it is looking bad, I will submit a warranty claim. Suggest others do the same.
I tried it on my end and didn’t have the issue
After I read wikipedia ( QWERTY - Wikipedia ),
I change keyboard layout from
United States-International to US in Windows 23H2’s settings and solved.
Basically 1 day Now. I just purchased my 13" first week of March. Then immediately got the email about the batteries having an issue, before the machine even showed up. Okay, fine.
I figured I would just set the battery charging limit to 85% or so, and onward I would go. It worked a treat. Then installed the 3.07 BIOS update, thinking that it would help solidify the battery issue a bit more, just to do the right thing. No matter the toggle in the BIOS, the battery just charges to wherever it wants to. Sometimes it seems to respect the limit I’ve set (and set a few different values, a few different times), but most of the time it’s sitting at 100%.
Love the machine thus far; Regret updating the BIOS, which apparently cannot be rolled back. Real cute guys.
3.05 fixed the battery and charging (supports 9V charger). 3.07 breaks low power charging that 3.04->3.05 fixes
You can still return the laptop before the return window closes. If you still want to use FL13 you can buy another one and install 3.05 BIOS
Ahh. You can tell I am new here. I didn’t realize this was an historical thing already. It is certainly a ‘1st world problem’ to have, but it is disheartening. I suppose it IS more important to many to have correct charging on the charging side. Just seems a fine juggle. I do not plan on returning, I plan on them fixing the issue, hopefully in a quicker than historical manor?
Thank you.