search

fwupd / firmware-lenovo

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

X280 unusable after N20ET68W => N20ET70W upgrade stuck #478

Open biredel opened 2 weeks ago

biredel commented 2 weeks ago

While deploying 1.53=>1.55 via Ubuntu-distributed fwupd 1.7.9-1~22.04.3, one ThinkPad X280 20KF updated within minutes. Another ThinkPad X280 20KE did not move the progress bar for 60 minutes, was reset and now fan does turn on, screen stays blank.

I'll have an hour to investigate the unusable 20KE this week, and intend to proceed updating two similar 20KE devices. Any diagnostic steps you would like me to perform and report?

(side note: I cannot find any Product Security Advisory mentioning CVE-2024-29979 or CVE-2024-29980 - currently the description lacks guidance on whether systems that do load intel microcode and do not depend on EFI network stack even need N20ET70W)

mrhpearson commented 2 weeks ago

Is the system able to boot at all? E.g. can you get to the BIOS setup screen? Or is the system effectively bricked?

If it's bricked you can try resetting it using the pinhole in the back - see if that recovers it (though it will reset everything). I'll have to ask FW team for guidance on anything else. I've not seen any other error reports I'm afraid.

Mark

biredel commented 2 weeks ago

The previously flawless now broken one would still flicker power on AC connect as usual. On turn on, dark, no beep after hitting Enter, initially silent and fan gradually spooling up to ~50%. After disconnecting batteries, additional beeps on turn on. Alternates between various melodies, recognized by the app as 0285 ("TCG-compliant functionality-related error (might be the TPM initialization failure)"), 010228 (?), 010288 ("0288: Computer display error"). fwupd report is now uploaded, says "failed to run update on reboot" because the outcome of the attempt was never stored on the disk it was retrieved from.

Unfamiliar with manual flashing, and old hardware anyway, so will likely stay that way for some time. But still have it around, so if there is anything you need to determine whether the firmware or updater is at fault, I can still do further tests (also on 20KE machines that installed 1.55 just fine).

Only possible clue I have for you is that during firmware update, AC power was provided through USB-C dock. Not like the firmware updater needs to turn on USB keyboard.. but given how the admin password input prompt is overwhelmed by regular typing speed, connected USB peripherals could plausibly confuse the firmware updater aswell?