Beta 3.07 has been released for more than a week now, do you know when firmware will be promoted to stable release?
We have finished the beta period, and have updated this post to show this release is now stable.
This release has been moved to the LVFS stable channel. and will propagate soon.
Great ! Update done without any problems, thanks ![]()
Updated without issues via LVFS, thanks! ![]()
Update does not show up in LVFS with Fedora 41:
Geräte mit keinen verfügbaren Firmware-Aktualisierungen:
• Bolt Receiver
• MX MCHNCL
• Radio
• Radio
• SSD 980 PRO 2TB
• System Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• USB3.0 Hub
• USB4 Retimer
Geräte mit der neuesten verfügbaren Firmware-Version:
• Fingerprint Sensor
• Thunderbolt Dock G4
• UEFI dbx
• Unifying Receiver
• Unifying Receiver
Keine Aktualisierungen verfügbar
dmidecode | grep -A3 'Vendor:\|Product:' && sudo lshw -C cpu | grep -A3 'product:\|vendor:'
Vendor: INSYDE Corp.
Version: 03.05
Release Date: 06/04/2024
Address: 0xE0000
product: 13th Gen Intel(R) Core(TM) i5-1340P
vendor: Intel Corp.
physical id: 4
bus info: cpu@0
version: 6.186.2
Is using a charger mandatory or is a docking station sufficient ?
Exact same problem here with my Intel® Core™ Ultra 5 125H.
–
Rod
This thread is specific to the 13th Gen Intel Core. I would not expect you to be seeing LVFS updates for the 13th Gen Intel Core laptop on your Core Ultra laptop.
DUH, my bad. I’m starting to have a bit of trouble keeping up with all the different generations, distros talk…etc. Probably time to back off, let things break, then figure out how to fix it.
–
Rod
Laptop 13 13th Gen, Ubuntu 24.10. Upgraded to BIOS 3.07 and immediately got the 400mhz CPU throttling “bug” (or so I found out after some searching). I was mystified. Went back to 3.05 I was on before and performance immediately went back to exactly what it was before the 3.07 upgrade, and I changed nothing else. I’m not feeling inclined to upgrade BIOS again. I shouldn’t have to try the CMOS reset or whatever else, when the only change is a BIOS upgrade, then things stop working properly, and then a downgrade immediately fixes the problems.
No update for me available, for some reason.
Running Ubuntu Jammy with an 13th Gen Intel(R) Core(TM) i5-1340P with firmware 3.03, but when I use the update commands I get the following:
fwupdmgr refresh --force
Updating lvfs
Downloading… [***************************************]
Successfully downloaded new metadata: 0 local devices supported
fwupdmgr get-updates
Devices with no available firmware updates:
• CT1000P3PSSD8
• System Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI dbx
No updatable devices
Still no update via lvfs.
That’s a bit disappointing. I hoped for a full linux support.
Thanks for the report, LVFS demoted this due to metadata changing in a few end user reports. we have moved it back to stable.
After resizing my way too small EFI partition I can confirm that the update worked flawlessly.
I’m happy again.
Great work framework.
Keep it that way.
P.S. to get the fwupdate-command to recognize the BIOS update I had to unplug the power adaptor. I plugged it in after download before rebooting.
can now confirm that the update via lvfs worked
Maybe there is a problem with the lvfs stable remote :
- version 3.06 and 3.07 are available only in testing
- this LVFS: Laptop 13 AMD Ryzen 7040 say that the versions 3.06 and 3.07 are “not be suitable for production systems”
Should I use the testing remote?
looks like things are better, thanks a lot ![]()
I was able to successfully update from 30.03.05 to 30.03.07 via fwupdmgr . Arch Linux, kernel 6.13.7-hardened. No issues with dropped boot entries, battery limits were remembered.
I’m experiencing several issues similar to those reported with AMD and Intel 12th gen processors. This version has a significantly quieter fan curve, where the fan activates much later under load or increased temperature. This results in higher idle and light-load temperatures compared to before. Furthermore, under full CPU load, temperatures can spike, occasionally causing the frequency to drop drastically to 0.4GHz, requiring a restart to return to normal.
Just a note, I successfully updated via fwupdmgr to version 3.07. =)
However, I had to activate lvfs testing.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.