@Kieran_Levin, after a very short mental debate, I decided to try the manual retimer update, but it didn’t work. I booted the USB stick with the updater, hit ESC to get the EFI shell prompt, and typed updateretimers.nsh. It printed that it would wait 8 seconds, and then a line of post-update instructions. After the 8 seconds, it printed:
CapsuleApp: capsule image (winux.bin) not found
And then after another 5-10 seconds it returned me to the EFI shell prompt. framework_tool still shows:
Hi DSK,
Do you have a support ticket open? This not expected behavior, and seems to be specific to your hardware, so the best path to get this resolved is to go through support.
Did you change your filesystem path to the drive? You can do this by typing fs1: or fs0: (you can see the path on the top of the shell) before running the command?
Ah, no, i hadn’t done that. After doing so (fs1:, in my case), the update worked, and framework_tool now reports version 310 for both retimers. Thanks! Haven’t yet had the opportunity to try external monitors in all ports yet.
I tried this twice. The first time on battery it rebooted into an updating screen that quickly went away. The second time I tried with power applied to the left rear port and then it seems to have worked.
Hello, I have Ubuntu on the internal disk, and a Windows 11 made with Rufus that I use twice a year on a 250gb expansion card.
I follow this topic from time to time only… So, apparently regular installation guide for Windows, as indicated on the KB page would just work with such setup?
Update report from me. I’d run the original 3.08 EFI and everything other than the IME and the right side retimers had worked. Manually updated the IME some time ago.
Ran the 3.08d EFI updater which verified everything other than the right retimer was up to date. Manually updated the retimers with updateretimers.nsh and now seems to be up to date.
Something I think would help is to keep the original post in this thread more up to date as it’s currently pointing to the broken 3.08b EFI update not the safer 3.08d version.
It might also be worth checking any Framework bits on LVFS: Device List - are these safe or will they cause more potential problems for people? This was actually intermittently reporting Retimers updates as being available last week, possibly due one side not being up to date for me. I’m currently seeing update alerts on there for the fingerprint sensor.
I can’t help wondering if elements of this community alpha testing might have worked better using a repo under Framework · GitHub ? Especially keeping track of and deprecating older releases and tracking issues arising. Given the technical proficiency of the audience here you may even have had some PRs to try and help.
It’s good to see much more communication in here from Framework. Movement on this is much appreciated. Hopefully getting to a stable EFI release will allow for a smoother ride for future updates.
Thanks for the feedback everyone!
I have edited the top post to update the instructions and link for the EFI updater to the latest version, and based on the positive community feedback, marked this as beta.
I ran the script and left the computer running, when I came back a few min later it rebooted back to OS. I don’t know if there was any error during install process, but the BIOS still reports the old version 3.04
I tried running the update again, but get the error message, can’t update over same version and then get a green screen that the update was successful.
The only error message you are getting is from the ME Updater. Of the updates the script is trying to do on your device, it is the only one that executes instantly. While the main BIOS will be updated after a reboot. So your ME firmware will already be up-to-date from the first attempt, as it says. But that is very separate from the other parts of the update process.
And the next message shows that the updater proceeds and reaches the step where it tries to setup the capsule update including reboot (updating the main BIOS from 3.04 to 3.08). So your issue is somewhere around that part. And the red message shown has nothing to do with it.
Your issue will most likely be about your partitions / EFI System partition etc.
Because that part of the update does not work for you. It is supposed to set it up so that it continues with a fullscreen progress bar after the reboot. And sth. goes wrong with that, so you just land in your normal OS after the reboot.
But the failure message you have shown is not related to that. It is from another part of the update that already went fine and is to be expected.
I do not know.
I just pointed out, that the message you focused on has nothing to do with your problem. If there are other messages after the waiting message (the last line in your photo) those would probably point to a narrower reason.
Otherwise someone else needs to walk you through providing enough info so that Framework can find and solve the issue.
