The BIOS version does not show as updated to 3.20 on the BIOS main page or in the return of dmidecode.
There doesn’t appear to be any 6Ghz bands available on Wifi even when standing right next to the AP (Using the provided Intel AX210). iw phy still shows all 6GHz frequencies as being disabled.
This is the output of the “successful” BIOS update.
I ran the intel provided script to check if the CSME was updated to 15.0.47.2473 and it was.
It appears that some portions of the BIOS update was successful whereas other things were not. I’m not sure what the CapsuleApp errors are at the end of the BIOS update, so may be related to that?
Hello,
i had a problem with this update that grub-boot was gone.
Did anyone else have this?
I have Dualboot Windows / Linux (Debian) with grub, after the UEFI Update the computer direct boots to Windows and grub is gone.
It seems I was wrong. It still needs to be plugged in and then turned on if left off for a couple hours or more. If I turn it off and then immediately turn it on then it works.
I’m seeing an issue with booting as well across two 11th gen 13" laptops after upgrading to 3.20. It seems likely to be related to the RTC battery. Neither will boot normally, the fans just spin and the power button light comes on with the screen off until it turns all the way off and tries again. One just wouldn’t boot at all until I took out the RTC battery and now it’s normalish, just takes a long time to boot. The other I haven’t tried removing the RTC battery yet, but won’t boot unless I plug it into a phone charger (but not a laptop charger). From reading the docs, it seems this is due to the phone charger trickle charging the RTC battery.
The booting issue happens immediately upon suspending or shutting down. I can close the laptop lid then open it right back up and it won’t come back up unless I power it all the way down. It seems unlikely to be an OS issue, but I’m running Linux.
If S3’s been unsupported, but I’ve gotten away with using it, and 3.20 breaks it; you figure I should stay on 3.19? I’ve gotten attached to passable power usage during sleep.
What the heck was Intel smoking, anyways? (Aside from their own CPUs, eh?)
it sounds like if I upgrade to 3.20, (a) I will lose the ability to use suspend to RAM and (b) I won’t be able to downgrade to 3.19 to get it back.
I like suspend to RAM, because it’s the only way I can get sleep power consumption down in the vicinity of half a watt, roughly 1% per hour. Suspend to idle sucks. It uses more power and sometimes it fails mysteriously.
So the “should” part of my question is, are there any 3.20 BIOS changes that are desirable enough for me to lose suspend to RAM?
I’m not having any issues yet, because I haven’t upgraded to 3.20 yet. I’m still running 3.19.
I doubt the OS matters, aside from it being Linux. I’m on Fedora 40. I can’t try 3.20 to see if it works, because downgrading is impossible, so I’m just going by what others have said.
Try selecting your bootloader directly with F3 on startup (rather than F12).
Once you’ve booted your preferred OS, re-run the commands you used to install your bootloader. That will rewrite the UEFI NVRAM entries that inform the firmware about it.
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.
