MrChromebox/firmware

Intermittent Bricking - Lenovo IP Flex 5 Chrome 14IAU7

Opened this issue · 16 comments

All installed and working perfectly, running Debian Testing on a 2TB internal card. But, randomly the machine will not boot, no keyboard backlight, nothing. Even the technician at the Lenovo Service Center is stumped. Sometimes, if I disconnect the battery and the keyboard ZIF cable, it will boot on the power supply. But, other times it boots ok with battery and keyboard cable connected. The technician is suspecting a hardware problem, but cannot isolate any component issue. But, with a mrchromebox bios, I suspect that maybe its some sort of suspend or hibernate issue. I really don't know where to begin to debug the issue.

does a hard reset (Refresh+Power) revive the device when it won't boot?

it's the circular arrow, typically where F3 would be

image

I don't know what you mean by maintenance mode, there is no such thing on Chromebooks. Do you mean Recovery Mode (ESC+Refresh+Power)?

@MrChromebox I report the same soft-brick at boot, present in latest 3 releases (from 2408 of MrCB) on Lillipup and I happened to capture a screenshot of this issue:
6e56b10d-f966-47fc-a9a4-ae8451002e33

on boot, after the rabbit logo, Screenshot presents:
"SecureBoot status: Disabled
Booting from 'Garuda' failed: verify it contains a 64-bit UEFI OS.
Press any key to continue booting..."

All attempts to try to boot from here fail. Pressing any key goes to "UEFI Interactive shell v2.2. EDK II. UEFI 2.4" and there's a line saying "map: no mapping found". But typing "bcfg boot dump -b" lists all my entries nicely though.

Seems not easy to guess when it decides to soft-brick, as sometimes is from restart, sometimes seems from booting by opening the lid.
To get past it, I attempt many shutdowns (no restart, cold boots) till luck gets you to the normal grub loader instead. Somehow I feel if I wait minute(s) before attempting a cold boot works to pass around the problem.

Sadly we can't rollback with your script, from what I understand it's what you prefer for avoiding entropy with too many issues, which is OK! Nevertheless we hope you can find if it can be fixed and wish its an easy thing! 👍

@marcosilva85 when it dumps you to the shell, type exit and press enter as per the instructions. then go to the boot menu. Is the internal storage listed as a boot device?

@MrChromebox no, the NVMe does not show in there.

Usually it lists 4 entries with NVMe at bottom, but with this issue active it only shows "Garuda, Fedora, UEFI Shell" (and sadly the first ones then do not boot, only UEFI shell )

then that's the issue, the NVMe isn't coming up on a warm boot sometimes

@MrChromebox yeah can be that, sadly!
but even when I try to restart the laptop from that state, expecting the NVMe to show up, the issue just persists... its difficult to come up with a quick solution to boot when it gets into this state, regrettably

I also just came across #671 which seems it might be present in different devices,
Any way you could figure out a fix for this ?

@marcosilva85 your issue seems unrelated to this ticket, and #671 is for a device with UFS storage, not NVMe. Please open a separate one for LILLIPUP

I have kept my laptop running with power to avoid the issue. However, I can offer an anecdote that may be helpful. Each time my laptop bricked, I took it into the local Lenovo service center, and each time it "miraculously" booted. I don't know why. I would try for an hour at home, no luck. But, at the center it seemed to boot after only a few tries, within 5 minutes. The first time this happened, the bootup process froze and the last message in the bootup sequence said something about Bluetooth, if I recall correctly. I connected to a power outlet at the service center, but sometimes just the battery. All this suggest to me anyway that maybe there was some WiFi or Bluetooth signal at the Lenovo service center that was helpful to the boot process. I asked the service center tech if they were running boot on WiFi or some such signal that might affect my laptop, and he said no, not that he was aware of. Sorry I cannot be of further assistance, as I will just continue to stay powered on until we have a fix.

@gdbaldw what board are we even dealing with here? which firmware type?

ChromeOS Device Firmware Utility Script [2024-11-01]
(c) Mr Chromebox mrchromebox@gmail.com


** Device: Lenovo Lenovo Flex 5i Chromebook 14"
** Board Name: TAEKO
** Platform: Intel AlderLake/RaptorLake-U/P
** Fw Type: Full ROM / UEFI
** Fw Ver: MrChromebox-2408.1 (09/14/2024)
** Fw WP: Disabled

I replaced the stock 128GB NVMe with a 1TB NVMe 2230.

do you have a SuzyQ cable available? That's really the only way to debug an intermittent booting issue

do you have a SuzyQ cable available? That's really the only way to debug an intermittent booting issue

I have. Yes.

unzip and flash this via SuzyQ: sudo flashrom -p raiden_debug_spi:target=AP -w coreboot_edk2-taeko-mrchromebox_20241113.rom --fmap -i COREBOOT -N

then log to file using minicom via /dev/ttyUSB1. one log of the working case and one non-working would be ideal.

coreboot_edk2-taeko-mrchromebox_20241113.zip