fwupd / firmware-lenovo

Missing firmware for Lenovo Thinkpad hardware
118 stars 4 forks source link

Battery capacity reported as 0% after firmware upgrade on Lenovp T14s 2nd Gen #329

Open mlechner opened 1 year ago

mlechner commented 1 year ago

Describe the bug After upgrading the firmware on a Lenovo T14s 2nd Gen AMD the capacity of the battery is always 0% and stays there even Linux reports that the battery is being loaded. Working with the machine without plugged in power is not possible as Linux shuts down the computer because it thinks that the battery is empty. The Lenovo diagnostics show a capacity of 7% of the battery (stalled) even after having the machine on power for a while. There is no possibility to downgrade the firmware, as the action is denied to due missing battery capacity of at least 25% (well being always recorded as 0%).

Steps to Reproduce Install the latest firmware and may be this is reproducable. Recent situation is:

$ sudo fwupdmgr get-devices ├─Battery: │ Device ID: f95c9218acd12697af946874bfe4239587209232 │ Summary: UEFI ESRT device │ Current version: 1.1.9482 │ Minimum Version: 0.0.1 │ Vendor: Lenovo (DMI:LENOVO) │ Update State: Success │ Update Error: Cannot install update when system battery is not at least 25% │ GUID: 8f7a3473-a9a7-4aef-b4e0-256976c6816a │ Device Flags: • Internal device │ • System requires external power source │ • Supported on remote server │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ • Updatable $ sudo fwupdmgr refresh --force Updating lvfs Downloading… [***************************************] Successfully downloaded new metadata: 2 local devices supported $ sudo fwupdmgr get-updates ... Devices not currently updatable: • Battery — Cannot install update when system battery is not at least 25% • System Firmware — Cannot install update when system battery is not at least 25% No updates available $ sudo fwupdmgr reinstall --allow-reinstall --force Choose a device: 0. Cancel 1. f95c9218acd12697af946874bfe4239587209232 (Battery) 2. 349bb341230b1a86e5effe7dfe4337e1590227bd (System Firmware) 1 No releases found: Device Battery [f95c9218acd12697af946874bfe4239587209232] does not currently allow updates: Cannot install update when system battery is not at least 25%

Expected behavior After installation of the firmware the capacity should be reported correctly and loading should be possible

fwupd version information $ sudo fwupdmgr --version runtime org.freedesktop.fwupd 1.7.9 runtime com.dell.libsmbios 2.4 compile org.freedesktop.gusb 0.3.10 runtime org.kernel 5.19.0-38-generic compile com.hughsie.libjcat 0.1.9 compile org.freedesktop.fwupd 1.7.9 runtime org.freedesktop.gusb 0.3.10

Please note how you installed it (apt, dnf, pacman, source, etc): fwupdate is being installed using apt

**fwupd device information** $ sudo fwupdmgr get-devices --show-all-devices 20XGS01100 │ ├─ELAN0679:00 04F3:3196: │ Device ID: ae96d39c32c3b00e0001b41d12da9af669de08d9 │ Summary: Touchpad │ Current version: 0x0003 │ Bootloader Version: 0x0002 │ Vendor: HIDRAW:0x04F3 │ Update Error: Cannot install update when system battery is not at least 25% │ GUID: 838d5d10-c73f-52eb-824e-4271d4126b4d ← HIDRAW\VEN_04F3&DEV_3196&REV_00 │ 1488ce2e-a5af-53b9-91ed-7e79913d3e82 ← HIDRAW\VEN_04F3&DEV_3196 │ 6c590957-d579-5072-b2ba-12d86a8c0f0f ← HIDRAW\VEN_04F3&DEV_3196&MOD_0007 │ 4b808d27-c833-50cc-8177-9a401f5c08fe ← ELANTP\ICTYPE_14 │ 36e6d33d-9399-581b-a4a3-f5818f0b9a44 ← ELANTP\ICTYPE_14&MOD_0007 │ Device Flags: • Internal device │ • Updatable │ ├─USB2.0 Hub: │ │ Device ID: 91c9a317b30acf7c0cd967f2ce6925d518ef19a7 │ │ Summary: USB 3.x hub │ │ Current version: 50.33 │ │ Vendor: VIA Labs, Inc. (USB:0x17EF) │ │ Install Duration: 15 seconds │ │ Update Error: Cannot install update when system battery is not at least 25% │ │ GUID: dea51bff-550e-54e7-9b88-d05519771a15 ← USB\VID_17EF&PID_3071&REV_5033 │ │ e2c96871-8be3-530e-a796-5652cee64eeb ← USB\VID_17EF&PID_3071 │ │ 6f3f32bd-ac98-523e-9128-ef67941fb614 ← USB\VID_17EF&PID_3071&HUB_20 │ │ eae87a37-9a0a-56ae-81b0-dda2516a1202 ← USB\VID_17EF&PID_3071&SPI_C220&REV_5033 │ │ ff324851-023a-508e-8304-f6231f512a64 ← USB\VID_17EF&PID_3071&SPI_C220 │ │ Device Flags: • Cryptographic hash verification is available │ │ • Device stages updates │ │ • Device can recover flash failures │ │ • Updatable │ │ • Unsigned Payload │ │ │ └─USB2.0 Hub: │ Device ID: 41af0a4d70ae1190499dc16830f8f4e856f07aee │ Summary: USB 3.x hub │ Current version: 50.34 │ Vendor: VIA Labs, Inc. (USB:0x17EF) │ Install Duration: 15 seconds │ Update Error: Cannot install update when system battery is not at least 25% │ GUID: f6540363-8288-5dce-86dd-be3656cee148 ← USB\VID_17EF&PID_3071&REV_5034 │ e2c96871-8be3-530e-a796-5652cee64eeb ← USB\VID_17EF&PID_3071 │ 3545c1f3-4d81-59f7-b9d9-d25d5811e4be ← USB\VID_17EF&PID_3071&HUB_10 │ ea3fe2ba-bc38-5014-ad8c-049fcad898c4 ← USB\VID_17EF&PID_3071&SPI_C220&REV_5034 │ ff324851-023a-508e-8304-f6231f512a64 ← USB\VID_17EF&PID_3071&SPI_C220 │ Device Flags: • Cryptographic hash verification is available │ • Device stages updates │ • Device can recover flash failures │ • Updatable │ • Unsigned Payload │ ├─USB3.1 Hub: │ │ Device ID: 28fe7919e3b6101195936a2b7486d9f5a54afe92 │ │ Summary: USB 3.x hub │ │ Current version: 50.33 │ │ Vendor: VIA Labs, Inc. (USB:0x17EF) │ │ Install Duration: 15 seconds │ │ Update Error: Cannot install update when system battery is not at least 25% │ │ GUID: e2c96871-8be3-530e-a796-5652cee64eeb │ │ 804c86fc-4fc2-5426-8600-14a8691f1083 ← USB\VID_17EF&PID_3070&REV_5033 │ │ 2c08e9d9-1f25-5564-b4db-49867dd2c593 ← USB\VID_17EF&PID_3070 │ │ 6d51c3aa-707f-5d41-812d-5cb5c8a4a25d ← USB\VID_17EF&PID_3070&HUB_0004 │ │ f0dde254-4735-5228-87d9-a38da1be8684 ← USB\VID_17EF&PID_3070&SPI_C220&REV_5033 │ │ 1629f638-07cc-564e-b3af-cc281bbab269 ← USB\VID_17EF&PID_3070&SPI_C220 │ │ Device Flags: • Cryptographic hash verification is available │ │ • Device stages updates │ │ • Device can recover flash failures │ │ • Updatable │ │ • Unsigned Payload │ │ │ └─USB3.1 Hub: │ Device ID: 66048ba3beabcc7f5ac6a70cbc62a663c9fb82f4 │ Summary: USB 3.x hub │ Current version: 50.34 │ Vendor: VIA Labs, Inc. (USB:0x17EF) │ Install Duration: 15 seconds │ Update Error: Cannot install update when system battery is not at least 25% │ GUID: e2c96871-8be3-530e-a796-5652cee64eeb │ bf3a0660-00f1-52fc-9b18-2cfa0cbf4dc7 ← USB\VID_17EF&PID_3070&REV_5034 │ 2c08e9d9-1f25-5564-b4db-49867dd2c593 ← USB\VID_17EF&PID_3070 │ 816fc838-78d7-5deb-85ef-a95935318198 ← USB\VID_17EF&PID_3070&HUB_0010 │ 0905c21a-12cd-551c-b84a-3ef35d0c3318 ← USB\VID_17EF&PID_3070&SPI_C220&REV_5034 │ 1629f638-07cc-564e-b3af-cc281bbab269 ← USB\VID_17EF&PID_3070&SPI_C220 │ Device Flags: • Cryptographic hash verification is available │ • Device stages updates │ • Device can recover flash failures │ • Updatable │ • Unsigned Payload │ ├─Battery: │ Device ID: f95c9218acd12697af946874bfe4239587209232 │ Summary: UEFI ESRT device │ Current version: 1.1.9482 │ Minimum Version: 0.0.1 │ Vendor: Lenovo (DMI:LENOVO) │ Update State: Success │ Update Error: Cannot install update when the lid is closed, Cannot install update when system battery is not at least 25% │ GUID: 8f7a3473-a9a7-4aef-b4e0-256976c6816a │ Device Flags: • Internal device │ • System requires external power source │ • Supported on remote server │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ • Updatable │ ├─Fingerprint Sensor: │ Device ID: 96a0be68fa5cf5d60d3d2d392797c6844ab64d33 │ Summary: Match-On-Chip fingerprint sensor │ Current version: 01000276 │ Vendor: Goodix (USB:0x27C6) │ Install Duration: 10 seconds │ Serial Number: UID0CA92333_XXXX_MOC_B0 │ Update Error: Cannot install update when system battery is not at least 25% │ GUID: 6322b4f7-0571-5f07-8538-e041bbc70677 ← USB\VID_27C6&PID_6594&REV_0100 │ 14450e82-8667-54c3-98e1-098d8c6dc3b8 ← USB\VID_27C6&PID_6594 │ Device Flags: • Device can recover flash failures │ • Updatable │ • Signed Payload │ ├─Integrated Camera: │ Device ID: 301046452a49d84af6356d23e43a684b8f10660f │ Current version: 60.1 │ Vendor: Azurewave (USB:0x13D3) │ Serial Number: 0000 │ Update Error: Cannot install update when system battery is not at least 25% │ GUID: 4dc71255-84a9-5adc-8eab-c5982db48621 ← USB\VID_13D3&PID_5405&REV_6001 │ 9284c551-0b4c-51ee-905a-168b8787290c ← USB\VID_13D3&PID_5405 │ Device Flags: • Updatable │ ├─Ryzen 7 PRO 5850U with Radeon Graphics: │ Device ID: 4bde70ba4e39b28f9eab1628f9dd6e6244c03027 │ Vendor: AMD │ Update Error: Cannot install update when system battery is not at least 25% │ GUID: b9a2dd81-159e-5537-a7db-e7101d164d3f ← cpu │ 22f9ecf4-588d-5c0a-8326-6ebff3655c6d ← CPUID\PRO_0&FAM_19 │ 79759cdc-94db-5098-be7b-eb02521fbbec ← CPUID\PRO_0&FAM_19&MOD_50 │ 20b595b0-5892-5870-8e4c-688133ad6e34 ← CPUID\PRO_0&FAM_19&MOD_50&STP_0 │ Device Flags: • Internal device │ ├─System Firmware: │ │ Device ID: 349bb341230b1a86e5effe7dfe4337e1590227bd │ │ Summary: UEFI ESRT device │ │ Current version: 0.1.26 │ │ Vendor: Lenovo (DMI:LENOVO) │ │ Update State: Success │ │ Update Error: Cannot install update when the lid is closed, Cannot install update when system battery is not at least 25% │ │ GUID: 66d47c53-a746-4495-a444-e6b26a04906d │ │ 230c8b18-8d9b-53ec-838b-6cfc0383493a ← main-system-firmware │ │ Device Flags: • Internal device │ │ • System requires external power source │ │ • Supported on remote server │ │ • Needs a reboot after installation │ │ • Cryptographic hash verification is available │ │ • Device is usable for the duration of the update │ │ • Updatable │ │ │ └─UEFI dbx: │ Device ID: 362301da643102b9f38477387e2193e57abaa590 │ Summary: UEFI revocation database │ Current version: 267 │ Minimum Version: 267 │ Vendor: UEFI:Linux Foundation │ Install Duration: 1 second │ Update Error: Cannot install update when system battery is not at least 25% │ GUID: 1e9c3d61-4bd9-514e-ad87-0a9b61b9e77d ← UEFI\CRT_156645FC005F8617669DF76E1DE6FAE02B3856D24B624E47D97BD2B8ADFFB6E0 │ 304a9ede-aff2-58f6-b5e5-0e651b065f1a ← UEFI\CRT_156645FC005F8617669DF76E1DE6FAE02B3856D24B624E47D97BD2B8ADFFB6E0&ARCH_X64 │ c6682ade-b5ec-57c4-b687-676351208742 ← UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503 │ f8ba2887-9411-5c36-9cee-88995bb39731 ← UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503&ARCH_X64 │ Device Flags: • Internal device │ • Needs a reboot after installation │ • Updatable │ • Only version upgrades are allowed │ • Signed Payload │ ├─TPM: │ Device ID: c6a80ac3a22083423992a3cb15018989f37834d6 │ Current version: 1.258.0.0 │ Vendor: ST Microelectronics (TPM:STM) │ Update Error: Cannot install update when system battery is not at least 25% │ GUID: ff71992e-52f7-5eea-94ef-883e56e034c6 ← system-tpm │ 84df3581-f896-54d2-bd1a-372602f04c32 ← TPM\VEN_STM&DEV_0001 │ bfaed10a-bbc1-525b-a329-35da2f63e918 ← TPM\VEN_STM&MOD_ │ 70b7b833-7e1a-550a-a291-b94a12d0f319 ← TPM\VEN_STM&DEV_0001&VER_2.0 │ 06f005e9-cb62-5d1a-82d9-13c534c53c48 ← TPM\VEN_STM&MOD_&VER_2.0 │ Device Flags: • Internal device │ ├─UEFI Device Firmware: │ Device ID: a45df35ac0e948ee180fe216a5f703f32dda163f │ Summary: UEFI ESRT device │ Current version: 24577 │ Minimum Version: 1 │ Vendor: DMI:LENOVO │ Update State: Success │ Update Error: Cannot install update when the lid is closed, Cannot install update when system battery is not at least 25% │ GUID: 60480a51-c946-4860-b42d-85ccaf0402ec │ Device Flags: • Internal device │ • System requires external power source │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ • Updatable │ ├─UEFI Device Firmware: │ Device ID: 2292ae5236790b47884e37cf162dcf23bfcd1c60 │ Summary: UEFI ESRT device │ Current version: 252051731 │ Vendor: DMI:LENOVO │ Update State: Success │ Update Error: Cannot install update when the lid is closed, Cannot install update when system battery is not at least 25% │ GUID: 88440680-8493-43d8-b1cb-51992223a226 │ Device Flags: • Internal device │ • System requires external power source │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ • Updatable │ ├─UEFI Device Firmware: │ Device ID: d96de5c124b60ed6241ebcb6bb2c839cb5580786 │ Summary: UEFI ESRT device │ Current version: 65794 │ Minimum Version: 65794 │ Vendor: DMI:LENOVO │ Update State: Success │ Update Error: Cannot install update when the lid is closed, Cannot install update when system battery is not at least 25% │ GUID: 76c3fd5b-8e31-3f3c-ecbf-f396df737922 │ Device Flags: • Internal device │ • System requires external power source │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ • Updatable │ ├─UEFI Device Firmware: │ Device ID: f37fb01122dd62c773f4e84ec89737e059712d59 │ Summary: UEFI ESRT device │ Current version: 65562 │ Minimum Version: 65562 │ Vendor: DMI:LENOVO │ Update State: Success │ Update Error: Cannot install update when the lid is closed, Cannot install update when system battery is not at least 25% │ GUID: 4bea12df-56e3-4cdb-97dd-f133768c9051 │ Device Flags: • Internal device │ • System requires external power source │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ • Updatable │ ├─UEFI Device Firmware: │ Device ID: 36efb79c255f402f619fa9eb53cd659db51f2a04 │ Summary: UEFI ESRT device │ Current version: 0 │ Vendor: DMI:LENOVO │ Update State: Success │ Update Error: Cannot install update when the lid is closed, Cannot install update when system battery is not at least 25% │ GUID: 2c9769a8-bd83-4e1c-857b-471b64912ced │ Device Flags: • Internal device │ • System requires external power source │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ • Updatable │ └─UMIS RPETJ1T24MGE2QDQ: Device ID: 71b677ca0f1bc2c5b804fa1d59e52064ce589293 Summary: NVM Express solid state drive Current version: 1.5Q0630 Vendor: Union Memory (Shenzhen) (NVME:0x1CC4) Serial Number: SS0L25218X3RC1BG14TK Update Error: Cannot install update when system battery is not at least 25% GUID: 68f6ceaf-c264-5e51-b171-f8a563fc1c51 ← NVME\VEN_1CC4&DEV_6304&SUBSYS_1CC46304&REV_03 5402558e-8c55-5032-b8d9-033fdddbfc28 ← NVME\VEN_1CC4&DEV_6304&SUBSYS_1CC46304 9d365702-56b1-57b0-bbd8-a23da844f9a3 ← NVME\VEN_1CC4&DEV_6304&REV_03 ce3d77e5-ef0f-508f-882d-58d5f29c9f43 ← NVME\VEN_1CC4&DEV_6304 9e0612ee-a3cc-530c-a39c-aaa57d401715 ← UMIS RPETJ1T24MGE2QDQ Device Flags: • Internal device • System requires external power source • Needs a reboot after installation • Device is usable for the duration of the update • Updatable

Additional questions

superm1 commented 1 year ago

Did the update "fail" to install? If not I'm afraid this is more likely to be a firmware bug than a tool bug.

mlechner commented 1 year ago

I guess the update itself did not fail. So you mean, I have to report that to Lenovo, because there firmware seems to be broken? Is there some QM within fwupd? I mean is there a way to blacklist firmware upgrades in fwupd if they are known to have a serious bug?

maierd commented 1 year ago

I think I am facing the same issue. Ran the update this morning (nothing seems to have failed) and now the battery is stuck at 0% while it says "Estimating...". I am running Ubuntu 20.04

EDIT: Same as @oshmoun says, the diagnostics reports a failing health check, the battery seems to be stalled at 7% as well.

oshmoun commented 1 year ago

Confirming the same issue here, on Archlinux. I ran the diagnostics uefi tool. That reported a health test failure, suggesting the firmware is buggy (since the battery was just fine before the update)

superm1 commented 1 year ago

@hughsie I think this update needs to get pulled..

Folks was it the EC that got upgraded or the BIOS?

If you don't know, Can you please share upgrade history ?

hughsie commented 1 year ago

Agreed, I've moved the update back to testing.

oshmoun commented 1 year ago

If you don't know, Can you please share upgrade history ?

Sure, here is the output of fwupdmgr get-history

maierd commented 1 year ago

Here is my output of that command.

mlechner commented 1 year ago

And mine is here: 20230417_fwupdmgr_history.txt

superm1 commented 1 year ago

So all of those reports show the battery firmware upgraded and system firmware upgraded. Which one caused the problem? Can you perhaps downgrade the battery firmware?

@mrhpearson ^

maierd commented 1 year ago

I am not able to downgrade or install another firmware, as a battery level of at least 25% is required to do that. I am not aware of a way to "force" the downgrade regardless.

mrhpearson commented 1 year ago

Raised internal ticket as high priority: LO-2416

@hughsie or @superm1 - it looks like there are four battery updates and they're all in stable (15977, 15978, 15980, 15981). I don't have permissions to move them but I'm suspicious of these as they were only released to stable recently. Should we demote these?

superm1 commented 1 year ago

Until we know what's going on I think that's a good idea.

hughsie commented 1 year ago

I don't have permissions to move them

I think you do, if you change your vendor group. If not, yell.

Should we demote these?

I've moved them all to embargo.

oshmoun commented 1 year ago

Can you perhaps downgrade the battery firmware?

I could not find a way to downgrade, since fwupdmgr downgrade <battery-device-id> simply reports the following: No downgrades for UEFI Device Firmware: No releases found

Though I'm probably just not knowledgeable enough about this stuff, and would appreciate it if someone were to provide a rollback method :sweat_smile:

helios2k6 commented 1 year ago

Just wanted to comment that I am having this issue as well, after updating my battery firmware. Pop_OS 22.04 on my Lenovo X1 Carbon Gen 9. Battery stuck at 0% and I can't update any other firmware.

here's my history as well: history.txt

helios2k6 commented 1 year ago

Also I should add that if I unplug my A/C adapter, my laptop shuts off completely. The battery is entirely useless, making my Lenovo nearly useless as well.

helios2k6 commented 1 year ago

Also to note, the firmware update of my battery failed, yet the bug is present, meaning something might be going on with the update process.

maierd commented 1 year ago

Did someone find a way to downgrade the firmware?

mlechner commented 1 year ago

Am I right that it is unclear if the battery firmware upgrade to 1.1.9482 or the System Firmware uprade from 0.1.24 to 0.1.26 is causing the error? If the battery firmware is causing the bug, could it be a solution to replace the battery like described in the lenovo hardware maintenance manual (is the firmware stored on the battery-part itself or is it on a controller that stays in the machine (on the board?) even when replacing the battery?

mlechner commented 1 year ago

Did someone find a way to downgrade the firmware?

No success yet. Always stopped by battery capacity being reported below 25%.

helios2k6 commented 1 year ago

Am I right that it is unclear if the battery firmware upgrade to 1.1.9482 or the System Firmware uprade from 0.1.24 to 0.1.26 is causing the error? If the battery firmware is causing the bug, could it be a solution to replace the battery like described in the lenovo hardware maintenance manual (is the firmware stored on the battery-part itself or is it on a controller that stays in the machine (on the board?) even when replacing the battery?

I should have an answer for you in about a week on that. I'm sending my laptop in for repairs. We'll see what gets replaced.

superm1 commented 1 year ago

Did someone find a way to downgrade the firmware?

No success yet. Always stopped by battery capacity being reported below 25%.

You may be able to use --force to override the fwupd prevention of the update, but it won't stop the firmware doing a similar check.

mrhpearson commented 1 year ago

We are discussing with the FW team but don't have any guidance yet. At the moment I'm assuming it's the battery FW update that failed - the symptoms match what would happen if the system was unplugged mid-update. As yet I don't have a solution to recover the system - we've asked for it.

drilorin commented 1 year ago

Looking forward getting a way to downgrade / roll back the firmware. I'll help in any way I can.

mlechner commented 1 year ago

Lenovo will displace my battery and my board based on an existing support contract. I will see what that means regarding the firmware. Worst case may be that the new battery gets bricked immediately because the broken firmware is flashed to the new battery after replacement. I will share my experience here, if needed. Just for record here the offer (in german) from Lenovo:

"bezüglich Ihrer Supportanfrage werden wir einen Technikereinsatz unter der Nummer 0000000000 veranlassen. Wir gehen davon aus, dass das Firmwareupdate das Systemboard beschädigt hat. Ihr Gerät wird bei Ihnen vor Ort zeitnah instandgesetzt. Sie bekommen vorher noch einen Anruf zur Terminabsprache. Der Techniker wird folgende Bauteile zur Verfügung haben: Systemboard und Batterie ..."

translated: "regarding your support request, we will arrange for a technician to call the number 0000000000. We assume that the firmware update has damaged the system board. Your device will be repaired promptly at your site. You will receive a phone call beforehand to make an appointment. The technician will have the following components available: system board and battery ..."

ieure commented 1 year ago

Seeing similar problems with my daily driver X13 Gen 2 AMD after updating to 1.26. The X13 Gen 2 AMD has the same motherboard / uses the same BIOS as the T14s Gen 2 AMD.

My symptoms are:

It was working fine prior to 1.26, and there's no physical damage to the port. My system is out of warranty. :(

cd-dr commented 1 year ago

I have the same problem with my AMD T14S gen 2 as well. In my case the update was performed from windows. I was using bios ver. 1.26 for over a month without any issues. Yesterday windows installed the following two updates,

  1. Lenovo Ltd. - Firmware - 257.0.0.9482
  2. Lenovo Ltd. - Firmware - 1.0.26.0 Since then both in windows and gentoo the battery is stuck at 0% and shows not to be charging further.

But it seems to be actually charging, because I am able to use the computer on battery after starting the system on AC. Without AC charger the system refuses to boot showing 0190 critical low-battery error.

Eagerly waiting for some help on fixing this, since this is my only system.

superm1 commented 1 year ago

Those who are having this issue, if you feel comfortable can you try to open up your chassis and disconnect the battery, wait a minute or two and then reconnect it and see if it helps?

cd-dr commented 1 year ago

I tried both disabling from bios and later physically disconnecting it. It didn't do anything. I even tried draining the capacitors holding the power down and resetting. None of those worked.

mrhpearson commented 1 year ago

I've escalated this to the FW team as a critical issue.

Please do call support if you have hit this problem - even if you are out of warranty. It's important they know that people are being affected - I have no way of pulling FW updates from Windows.

Afraid I've not had any guidance on how to recover a system yet :(

cd-dr commented 1 year ago

Thanks @mrhpearson. Seems like there's already a few folks facing the same issue here at Lenovo forums.

mlechner commented 1 year ago

Today the Lenovo support replaced the battery and everything works nice as before. I wonder that the firmware still seems to be 0.1.26 See my get-devices: 20230503_getdevices.txt And my get-history: 20230503_gethistory.txt

ChiWei-Chen commented 1 year ago

@ieure could you check if the battery firmware version is also 257.0.0.9482 ?

mrhpearson commented 1 year ago

As a note - there is a battery FW update coming soon with the fix. We expect it in the next couple of weeks as it's under internal testing right now (and it will be delivered on LVFS of course) It will be apparently be possible to update to it using fwupdate - will publish details once they are confirmed by the battery team. This should recover any impacted systems and hopefully avoid the need to ship batteries to support for recovery.

helios2k6 commented 1 year ago

Am I right that it is unclear if the battery firmware upgrade to 1.1.9482 or the System Firmware uprade from 0.1.24 to 0.1.26 is causing the error? If the battery firmware is causing the bug, could it be a solution to replace the battery like described in the lenovo hardware maintenance manual (is the firmware stored on the battery-part itself or is it on a controller that stays in the machine (on the board?) even when replacing the battery?

I should have an answer for you in about a week on that. I'm sending my laptop in for repairs. We'll see what gets replaced.

I can confirm that replacing the battery will fix the issue on a Thinkpad X1 Carbon Gen 9. Obviously, not an ideal scenario, as the battery will go out of warranty after 1 year and require you to buy a replacement directly.

drilorin commented 1 year ago

Hi there, any news on this issue?

ChiWei-Chen commented 1 year ago

Hi, I can see the FW is in embargo and going through the internal process, it would be moved to stable once it's completed.

WarTP commented 1 year ago

There is a firmware patch available in this thread, which seems to work fine, for anyone who does not want to wait on the official rollout.

https://forums.lenovo.com/t5/ThinkPad-T400-T500-and-newer-T-series-Laptops/how-to-uninstall-Lenovo-Ltd-Firmware-257-9482/m-p/5221798?page=6#5986468

oshmoun commented 1 year ago

Thanks for the hint. Assuming that fw is legit, then hopefully this makes Lenovo expedite the process and make the fw available sooner rather than later.

YounesOMK commented 1 year ago

the exact same problem, i can't downgrade since the battery is below 25%, Any official updates on this?

koreyspace commented 1 year ago

Same issue here on my Lenovo X1 Carbon Gen 9

mrhpearson commented 1 year ago

FW team are preparing the battery FW update for release - it should be available soon. Once that's available the battery operation should return to normal and unblock this.

mrhpearson commented 1 year ago

Just to note that the FW has been released on LVFS. Fwupd should find it - let me know if it's not showing up.

We're clarifying with the FW team exactly how to install it if it won't go through the regular install. The notes we have say

fwpudate -a <Device ID> firmware.cab
fwupdmgr install --force XXX

But that was before release so I'd like to confirm it's correct still (I think it will be) Mark

oshmoun commented 1 year ago

Just to note that the FW has been released on LVFS. Fwupd should find it - let me know if it's not showing up.

We're clarifying with the FW team exactly how to install it if it won't go through the regular install. The notes we have say

fwpudate -a <Device ID> firmware.cab
fwupdmgr install --force XXX

But that was before release so I'd like to confirm it's correct still (I think it will be) Mark

Thanks for the update, but fwupdmgr is not having much success finding the updated FW for me. I'm assuming that the firmware needs to be downloaded and installed manually, judging by the commands you provided. In which case could you please confirm, just to be extra extra cautious, that this is the firmware that needs to be downloaded and installed?

mrhpearson commented 1 year ago

For extra extra caution I'm going to recommend holding off until either Chi-Wei or I get the thumbs up from the FW team on updating uncharged batteries. But yes - that looks like the right FW to me. Does fwupdate not find it if you use the battery device-id?

oshmoun commented 1 year ago

But yes - that looks like the right FW to me. Does fwupdate not find it if you use the battery device-id?

Thanks for the confirmation. I went ahead and attempted a manual install, but that didn't work either, here's what I tried, alongside the output:

$ fwupdmgr download https://fwupd.org/downloads/b25fbb18e9dab0cc28a811ffc03a44ce68bf41992996c45c598d886a5ce9396a-Lenovo-ThinkPad-T14s-Gen-2i-BatteryFirmware-258.0.0.9482.cab
Downloading…             [**********************************     ]
$ fwupdmgr install --force b25fbb18e9dab0cc28a811ffc03a44ce68bf41992996c45c598d886a5ce9396a-Lenovo-ThinkPad-T14s-Gen-2i-BatteryFirmware-258.0.0.9482.cab
Decompressing…           [ -                                     ]
No supported devices found
mrhpearson commented 1 year ago

Can you let me know what fwupdmgr get-devices shows for the battery device please? Mark

oshmoun commented 1 year ago

Can you let me know what fwupdmgr get-devices shows for the battery device please? Mark

gladly :smile:

├─UEFI Device Firmware:
│     Device ID:          f95c9218acd12697af946874bfe4239587209232
│     Summary:            UEFI ESRT device
│     Current version:    16852234
│     Minimum Version:    1
│     Vendor:             DMI:LENOVO
│     Update State:       Success
│     Problems:           • System power is too low to perform the update
│     GUID:               8f7a3473-a9a7-4aef-b4e0-256976c6816a
│     Device Flags:       • Internal device
│                         • System requires external power source
│                         • Needs a reboot after installation
│                         • Device is usable for the duration of the update
│                         • Updatable
│   

It is not reported as a battery for some reason, probably because of the bad fw. However, this is definitely the battery device, at least according to fwupdmgr get-history:

├─Battery:
│ │   Device ID:          f95c9218acd12697af946874bfe4239587209232
│ │   Previous version:   1.0.9478
│ │   Update State:       Success
│ │   Last modified:      2023-04-17 07:49
│ │   GUID:               8f7a3473-a9a7-4aef-b4e0-256976c6816a
│ │   Device Flags:       • Internal device
│ │                       • Updatable
│ │                       • System requires external power source
│ │                       • Needs a reboot after installation
│ │                       • Reported to remote server
│ │                       • Device is usable for the duration of the update
│ │ 
│ └─(null) Update:
│       New version:      1.1.9482
│       License:          Unknown
│       Description:      
│       The vendor did not supply any release notes.
mrhpearson commented 1 year ago

OK - your device has a different GUID than the FW posted on LVFS - so the FW is correctly being rejected.

Can you confirm you have a T14s G2 Intel - and if so I'll have to check with the FW team why your GUID isn't being used. I checked my fwupd metadata cache and I can't find that GUID listed so right now I don't think there is FW for it available

Definitely don't recommend forcing any updates until we have it clarified.