I have an 11gen framework laptop running NixOS (boots from a microSD card). I’ve been trying unsuccessfully to update my BIOS. I currently have 3.19.
The Intel CSME part seems to have successfully worked because the version listed in the BIOS is now 15.0.47.2473. However nothing else got updated.
Whenever it goes to reboot after going through the step from booting from the usb stick with the unzipped BIOS update data, it goes to a screen that says something like “installing update” or something like last, which lasts for a second or two before it immediately reboots after doing nothing at all.
PS I also tried to use fwupdmgr sine the CSME part seems already updated, but that didn’t do anything either.
Turns out it was in part due to a faulty usb stick. Running a diff between the original unzipped files and what was on the disk showed a few bytes in Fwupdate.bin were different. Obviously quite bad.
FWIW, I also had this same problem. I suspect it is due in part to the fact that I’m booting NixOS off of a MicroSD card.
What worked for me, and this is totally unofficial/use at your own risk, was to follow the advice of ryneches and remove the -OD parameter to CapsuleApp, either by editing startup.nsh or by entering the command manually in the shell. This appears to have the effect of installing the Update Capsule (which updates everything other than the CMSE) onto the current bootable USB stick rather than trying to install it onto my boot device. Then, the next time it reboots, it runs the Update Capsule from the USB stick, and updates the BIOS and friends.
I suspect this way is “not recommend”, but it seems better than nothing.
Since updating, my Apple Thunderbolt 3 (USB-C) to Thunderbolt 2 adapter has ceased functioning and that’s how I connect to my LG 34UM95 display + keyboard & mouse.
It’s been working fine for since I got my FW13 almost 3 years ago, and suddenly it doesn’t even seem to be detected – no messages in kernel logs, no display when I boot, nothing…
I’ve been searching around but I can’t find any other reports, is it possible this is unrelated? The adapter and monitor both work fine with my other laptops, and I’ve tried just plugging in a TB2 network interface but that also gives no sign of life on my FW13.
I just updated my 13" 11th gen Intel Framework to 3.20. Everything works fine EXCEPT for any USB device. My USB Drive, Dock, the external monitors on that dock, my keyboard and mouse on my KVM don’t work. They don’t work on my Fedora 40 install and my Windows 11 install. On my windows 11 install, it says that there is a power surge on my USB device when I plug something in.
I’ve attempted to downgrade my bios using fwupdmgr downgrade, and it returns
Selected device: UEFI dbx No downgrades for UEFI dbx: current version is 371: 371=same
I just checked the BIOS version using sudo dnf install lshw dmidecode -y && sudo dmidecode | grep -A3 'Vendor:\|Product:' && sudo lshw -C cpu | grep -A3 'product:\|vendor:' and it said that I’m on 3.10, when I’m entirely sure the version I installed was 3.20.
thanks, i tried that twice (second time was just to make sure it wasn’t my fault that it wasn’t fixed the first time), but to no avail
i’m using the adapter with another laptop fine, and on that laptop it works to connect to the monitor; i can’t get the FW13 to recognize the monitor, during boot or inside the OS (Linux, in my case), and i’ve also tried connecting an old thunderbolt ethernet interface via the adapter, also to no avail.
in case it’s worth anything, the closest i can come to getting any recognition on the FW13 side is this message in the kernel’s ring buffer:
thunderbolt 0000:00:0d.2: can't suspend (nhi_runtime_suspend [thunderbolt] returned -110)
Since I upgraded to BIOS 3.20, I have really big booting problems.
The laptop often gets stuck to the Framework logo for a very long time (several minutes, more than 10 minutes), then some text shows up to the screen. After that, it reboots again and same circle.
I have made a video with my phone. How can I send it here?
This problem is a great handicap as I cannot use the laptop normally after I turn it on.
I have contacted the Framework support at the same time.
First of all, let me be clearer (what I said, wasn’t). I have always been able to boot successfully, but it is very difficulty and very long until I manage to. So it’s a really big problem.
Before what you say, they told me to reset BIOS to default, that did not work.
Then I tried the full mainboard reset, as you both said. The first reboot was normal, then I tried a reboot a few hours later and… same problem.
They told me to downgrade to BIOS version 3.19, but it won’t work. I guess the reason is this one : “Please Note: After updating to 3.20, you will not be able to downgrade to an earlier version.” (here : Framework Laptop BIOS and Driver Releases (11th Gen Intel® Core™)).
Now, I don’t know what to do. For the moment, I’ll write them the same informations and see what’s next.
So as a mainboard standalone user, as best I can tell BIOS 3.20 breaks all external display output. The framework still boots fine, but output over USB-C to HDMI, DisplayPort, anything doesn’t work. The system sees it but doesn’t actually output. I’ve only been able to get back in via major wrangling to turn on RDP blindly .
Does anyone actually have external displays working or is this broken for everyone?
Brian, check if your system is actually working but won’t output to any external display (See if keyboard CAPS LOCK works / networking, RDP etc). Mine is in this state. It’s very disappointing if this has slipped through testing because it was never tested without an internal display attached
Hi @RENE-CORAIL_Vincent
I took a look at your video, and it looks like your boot is getting stuck on a kernel hang after upgrading to 3.20.
Could you start by sharing your distribution and kernel version you are running on your laptop?
This looks like you are getting through the bios and booting into linux, and getting stuck somewhere in the Linux boot process. Lets start there.
I am following up with the incorrect instructions the customer support agent told you with regard to downgrading to 3.19.
Quick update: I thought I had nothing to lose, so I tried reflashing the update from Windows again. Now output over DisplayPort and HDMI seems to be working, but ONLY from the ports on the right of the mainboard? I briefly saw a INSIDEH2O update screen on reboot that seemed to want to flash (the EC?) but the update failed because no battery was connected (as expected - But I guess the low-level update was written with the assumption a battery would always be connected?). After the failure I can now use any display output reliably, but only on the RIGHT ports, which is better than nothing. All very weird. I’ll investigate further tomorrow.
Mainboard in a CoolerMaster case and having the same issue as others. Stuck on 3.17 and it wont let me flash to either 3.19 or 3.20 via UEFI. No errors and seems to reboot without issue, running Bluefin linux if that helps.
.