As random files on the internet do make me rather uncomfortable, I thought I’d try to look over them. You would want to check these yourself to be sure of them, but here are a few sha256sums, and where they came from, showing matches for Framework-associated files for everything except the FwUpdLcl binaries:
# From Framework 3.17 linux firmware (zip):
67738efe0459967e11fb26fca59c159a573dbb080e5c7152c66a2161da2a3c1c H2OFFT-Sx64.efi
04c89f19efee2a22660fd4650ff9add88e962d102b1b713e535f4e32a07c5185 efi/boot/bootx64.efi
# From Framework 3.19 windows firmware (exe with 7z x)
2c20f7d2a64a87b84ec928d86b8e9235c99dcb3d3888f6a53f2227c69ed27326 isflash.bin
95c79381f56f55f66e88f004de9a11ee0f6accccf89e503316940e1f9eb22cf0 FWUpdate.bin
# From Jared_Mauch1's 11th_Framework_3.19.zip
# matches 3.17
04c89f19efee2a22660fd4650ff9add88e962d102b1b713e535f4e32a07c5185 bootx64.efi
# matches 3.17
67738efe0459967e11fb26fca59c159a573dbb080e5c7152c66a2161da2a3c1c H2OFFT-Sx64.efi
# matches 3.19 isflash.bin
2c20f7d2a64a87b84ec928d86b8e9235c99dcb3d3888f6a53f2227c69ed27326 hx20.3.19.bin
# matches 3.19 FWUpdate.bin
95c79381f56f55f66e88f004de9a11ee0f6accccf89e503316940e1f9eb22cf0 ME.15.0.42.2235.bin
# No clear matches
936ef32556e8e0abd1dc9e7957cdc97db14682c050a31d53516f66476e1a5aae FWUpdLcl
fda2e3055e54c0fdaed0619079961a5cb80db24f64f6616fcba8ddc70ed28a07 FWUpdLcl.efi
I’m unable to find any source, authoritative or otherwise, for the FwUpdLcl binaries in the zip above. The Linux version is 15.0.0.1192, and I have not checked the EFI version. CSME 15.0 tools are available with a reasonably simple search, but not from a reputable source, and the version I found was the more recent 15.0.35.1951.
Neither worked for me alongside H2OFFT-Sx64.efi, which appeared to call them with the wrong command line options, though the screen moved too quickly for me to see the specific command line, if it was shown. As a failed return code there prevented the BIOS+EC update, I used bootx64.efi renamed as a standin for FwUpdLcl.efi, which allowed the update to proceed. Using the 15.0.35.1951 FwUpdLcl.efi on its own, I then had no problem updating CSME.
I now have a fwupdmgr security on Fedora 39 that returns HSI:3, and nothing has exploded yet. I would reiterate that all of this is very much at our own risk.
Thanks. Yeah, this is why I listed where I got things from except for the FwUpdLcl stuff, which as you mention someone can find from CSME tools as you said with some work.
I get why it might take a few days/week to repackage things, but for a device that is marketed as repairable and capable of upgrades, the idea of releasing an EFI updater and tools from Intel shouldn’t be significantly delayed IMO.
I also understand things often take much longer than anyone wants in real life.
I tried to go back a few months in this thread and I couldn’t find a definitive answer. I’m running Mint on my 11th Gen 13. If I throw another NVMe in here, install Windows and then run the 3.19 updater from Windows… Do I potentially break anything when I swap the drives back?
I really can’t think of any reason this wouldn’t work, and I can’t think of a reason why it would break, but I wanted to double-check with folks here to confirm.
@Matt_Hartley any plans to post the non-win64 binaries that as others have mentioned are findable or stored in the win64 exe?
One of the reasons that this device was interesting to me was it provided an x86_64 device I could use. Having made it through the HDMI and USB power draw issues, the BIOS updates are super important.
I’m hoping now that we’re almost 2 months later, even if it’s posting a similar set of files as an official version would happen.
Hi Jared, the moment I have word that it’s ready, it will appear here. We are a tiny team and we’re balancing a few other things at the same time. So it may be a bit, but we’re working on it.
11th gen linux user with my 61 Wh battery sitting on my desk hoping we can have 1 official avenue to update our bios in the near future, since the windows release has been out for a few months now.
I got fed up waiting for the linux bios update support on 3.19 and found a way using “Windows ToGo” aka booting win10 from an USB stick.
It’s fairly easy to do from linux, but it does require a windows VM to run Rufus.
Thankfully the quickemu project offers an easy way to download the win10 iso for the USB and the VM from the linux cli.
Thanks dfh for the pointers. If somebody has the time and ability, I would greatly appreciate a complete script for Linux update. I have some neurological damage, and can’t afford to risk an oopsie when I have to correlate several sources of information.
I have been using the old 3.06 BIOS on 11th Gen Intel for some years, and it’s not clear how bad that is, but I would definitely prefer to stay up to date.
I’m also totally unsure which of, so far I think I count 3, methods I should use, and how long to wait for the simplest to be available.
@Eric_Putney / @dfh - Pardon my stupidity but I want to make sure I’m on the same page. In the BIOS of my machine the Intel ME Version / SKU shows 15.0.42.2235 / CONSUMER.
The BIOS link posted by dfh shows 15.0.42.2235v2. Should the v2 show in the BIOS or no?
And the only reason I am going down this route is that I used the Windows OTG USB made via Rufus and it appears mine did update properly then.
The official BIOS update page says v2 “Update Intel CSME package to 5.0.42.2235v2 Corporate.” and without v2, also stated by Matt Hartley.
I would guess that they both mean v2 and that omitting it is just shorthand. Of course @Matt_Hartley can provide clarification on this.
Interesting, I’m not sure what you did that would have differed from what other folks have tried. What distro, and did you follow any special steps not outlined in this thread?
This is how I setup Rufus for this. It takes forever to write the ISO to the USB stick but that’s what I did.
As for the driver package, I did not. I generally presumed the drivers were Windows-specific so I didn’t bother.
And I actually just installed Linux Mint Edge on my Framework to reduce the odd hardware issues I was having and they appear to have gone away now. So updated BIOS, updated CSME, and updated OS. All seems good at this stage.
I was willing to be patient and accept the “we’re busy” explanation / excuse for some time. But we’re at 10 weeks here. The excuse doesn’t hold water any more.
The Linux community deserves to not be treated like second class citizens in the Framework world. We’re used to that from other OEMs, but we expect more and better from Framework. I’ve talked up Framework to many people because of your embracing the Linux community and doing well to support at least a couple of common distros. Kudos for that. But you are also going to get called out when you don’t do as well by your customer base as you could, would, and most importantly should.
Please take this as the well intentioned constructive criticism that I want it to be: this kind of delay in publishing a security update that we can use is not okay.
Sincerely,
A usually satisfied Framework Customer who would like you to do better in this case.
I had a suspion a lack of drivers could be bite me, since my Win2Go was missing a whole bunch of drivers. Eg. right mouse clicks weren’t working, no WiFi card, default graphics and what not.
I did a dedicated test re-flashing with my stock Win2Go version but that did not change CSME version.
During installation of the driver pack I saw an
Install Intel CSME driver
output in the Command Line window of the driver package installer and after a reboot my Insyde H2oFFT utility did something new when I ran another update:
After writing the new image a command line window popped up with a tool that called itself Intel FW Update and did some flashing/ updating.
And after I let the BIOS update finish, I am now running Intel ME Version 15.0.42.2235 / CONSUMER
Since I can’t re-test my instructions I’m curious if installing the Framework driver pack ** in Win2Go helps others too and if the indicators above (missing WiFi cards, no right-click on touchpad) are sufficient to figure out if you need the driver pack in the first place.
hoping we can have 1 official avenue to update our bios in the near future, since the windows release has been out for a few months now.
after I let the BIOS update finish, I am now running Intel ME Version 15.0.42.2235 / CONSUMER